Insight RSA Demo Update

Insight RSA 5.
50 Demo
Course description
These demonstrations provide a detailed overview of the prerequisites, installation,
and configuration of HP SIM (Systems Insight Manager) and Insight RSA (Insight
Remote Support Advanced) for a Windows-based CMS (Central Management
Server). As of Insight A.05.50, the CMS can be installed on a VMware ESX or ESXi
virtual machine, so several demos have also be included for that type of installation.
The demos will also provide information on the prerequisites, installation, and
configuration of some of the more common managed endpoint servers.
Note
These demos should be considered idealized configurations that will likely differ
for your particular configuration. You should therefore always refer to the most
current product documentation when performing an installation.
The demos are presented as follows:

Install, configure, and verify the operation of the Insight RSA CMS (Central
Management Server).
Discover and configure Insight RSA to monitor and collect information from
managed:
HP-UX Servers
Linux Servers
SMS (Storage Management Servers)
Windows Servers
P4000 SAN Solutions
Tape Libraries
September 2010 1
Insight RSA 5.50 Demo
Use Installation Advisor to verify event protocols and collect logs for support.
Verify the event monitoring and collections are operational.
The Resources page, located at the end of the demo modules, include links to
technical, software, and general information related to Insight Remote Support.
2 September 2010
Demo 1 CMS Installation Options

Note
Please refer to the latest documentation for the up to date list of prerequisites.
Note
The initialization and registration of Remote Support Software Manager
(RSSWM) can only be performed by a user who is logged onto the Hosting
Device via the system console or Remote Desktop Connection session. Do not
attempt to initialize or register via a non-console mode Terminal Services or
Remote Desktop Connection session. For Windows 2003, you need to use the
/console switch (c:\windows\system32\mstsc.exe /console). For Windows
2008, you need to use the /admin switch (c:\windows\system32\mstsc.exe
/admin).
Note
The CMS needs to be any HP ProLiant x86 or x64 with Insight Management
Support.
Verifying hardware and software requirements

1. Go to the System Information screen of the CMS, and click Start All Programs
Accessories System Tools System Information.
2. Verify that the server has the minimum required memory as defined by the
Release Notes.
3. Expand Components Storage Drives and ensure that the minimum required
free space as defined in the Release Note is available.
4. Expand Internet Settings Internet Explorer, and go to Summary. Verify that
the Internet Explorer version is 7.0 or later or Firefox version 3.6 or later.
5. Expand Components Network, and click Adapter. Verify that the server is
assigned a static IP address.
6. Expand Software Environment, and click Services. Ensure that the SNMP Service
and SNMP Trap Service is installed and running.
September 2010 3
Creating an administrator account

For security reasons it is always best to set up a user with administrator rights on the
CMS. You can use that user when a user with administrator rights is required.
1. Right-click the My Computer icon, and click the Manage option. The Computer
Management window appears.
2. Expand Local Users and Groups, right-click Users, and select New User.
3. In the New User screen, enter the new user details. As appropriate, set the
password options.
4. Click Create, and then click Close.
5. In the right pane of the screen, right-click the new user created, and click
Properties.
6. Click the Member Of tab in the new users Properties screen. Click Add, and
then enter Administrators, Remote Desktop Users, and Distributed COM
Users in the "Enter the object names to select" field.
7. Click Check Names, and then click OK OK to close the dialog box.
8. Log off from the current user and login with the newly created user.
Setting up Advanced Proxy Settings

1. Open Add Remove programs dialog box, and click Add/Remove windows
components.
2. Select Application Server, and click Details. Ensure that Internet Information
Service (IIS) is selected.
Note
IIS is only required if the Remote Support Network Components need to be
installed.
3. Also, ensure that Internet Explorer Enhanced Security Configuration is not

selected. If it is selected, clear it, and click Next to uninstall it.
4. Go to Internet Explorer properties to enter your proxy server details.
4 September 2010
After you have configured the proxy settings, you can verify the connectivity to HP
backend by using the following methods:
To test the connectivity between the Remote Support Client on the CMS and the
HP Support Center, use the URL:
https://services.isee.hp.com/version/index.html. The response should be a
version number, for example 05.16.08.133.
To test the connectivity between the CMS and the Software Management server
within the HP Support Center, use the URL:
https://rsswm.software.hp.com:443/site. The response should provide the status
of the Software Management server.
Installing the .NET Framework

1. .NET Framework version 2.0 is required to run Insight Remote Support. To install
.NET Framework 2.0, go to the folder where you have saved the setup file. If you
do not have the setup files, you can download .NET Framework 2.0 from
http://msdn.microsoft.com/en-us/netframework/aa731542.aspx.
Note
If you install .NET Framework 3.x on a system that does not have version 2.0
installed, the installer will automatically install version 2.0 for you. This will
complete .NET Framework 2.0 requirement for Insight Remote Support
Advanced. Do not uninstall .NET Framework 2.0 from a .NET Framework 3.x
installation as Insight Remote Support Advanced will not function without it.
2. Click the dotnetfx.exe file to start the installation and click Next.
3. Accept the license agreement and click Install.
4. Click Finish once the installation is complete.
Installing Java
1. Now, we will download and install Java which is one of the prerequisites. Go to
http://java.sun.com/getjava to download and install Java.
2. Follow the onscreen prompts to complete the Java installation.
3. Once the installation is complete, go to the Internet Explorer properties to verify
if the installation was successful by opening Internet Explorer and viewing
Properties.
September 2010 5
Verifying SNMP settings

1. Go to Start Administrative Tools Services to set the SNMP Services
parameters required for the CMS to securely send and receive traps.
2. Double-click SNMP Service.
3. On the Traps tab, make sure a community string is listed and local host and
127.0.0.1 exists as a trap destination.
4. Go to the Security tab, and ensure that Accept SNMP packets from any host is
selected.
5. Restart the service for the changes to take effect.
Installing ProLiant Support Pack (PSP)

Caution
Do not install PSP on a CMS that is hosted on a VMware ESX or ESXi Server.
1. Do not install PSP on a CMS that is hosted on a VMware ESX or ESXi Server.
2. Now, we will install the PSP which is one of the prerequisites. Go to the folder
where you have saved the PSP setup file, you can also download it from
www.hp.com.
3. Click the executable file, and then click Extract to extract the files. Once the files
are extracted, run the setup.exe file to start the installation.
4. Select Local Host, and click Next. Set the Bundle Filter options, and click OK.
5. Click Configure Now for the HP System Management Homepage. You can
assign who has access to the System Management Homepage and their level of
access on the Operating System Groups screen.
6. HP recommends using Trust by Certificate on the Trust Mode screen. This option
permits secure tasks from the HP SIM server to be run on only those systems that
have the required certificate. Selecting Trust by Name permits secure tasks from
the HP SIM server to be run on only those systems where the HP SIM server
FQDN or IP address have been defined. Selecting Trust All permits secure tasks
from the HP SIM server to be run on any system. Select the appropriate trust
mode and click Next.
7. Select IP Binding, if needed, and click Next.
8. Select IP Restricted Login, if needed, and click Next.
9. Now, we will configure the HP Insight Management Agents. To do so, click
Configure Now for the HP Insight Management Agents.
10. At the SNMP Settings screen, you can define how frequently the IM Agent
collects data. The frequency can be between 5 seconds and 60 minutes. For full
functionality between the IM Agents and HP SIM, select Enable SNMP Sets and
then click Save.
6 September 2010
11. Now, we will configure the Version Control Agent for Windows. To do so, select
Configure Now for the Version Control Agent for Windows.
12. Enter the details on the Version Control Agent Setup screen, and click Save.
13. Now, click Configure Now for the HP Insight Management WBEM Providers for
Windows Server 2003/2008.
14. Enter the account name and click Save.
15. Select Reboot System After Installation, and click Install. Now the PSP will install
and the system will reboot after installation.
September 2010 7
Demo 2 Installing and configuring HP Systems

Insight Manager
Note
This demonstration uses the SQL Express Database and a typical installation of
HP SIM. Refer to the HP SIM Installation & Configuration Guide for details
associated with using other databases or a custom installation.
Installing HP SIM
1. Login to the CMS using the administrator account you previously created.
2. Go to the location where you have saved the HP SIM setup file. Open the
executable file to extract the contents.
3. Select the folder where you want the extracted files. Once all the files are
extracted, the installation will start.
4. Click Next on the installation screen to begin installation.
5. Select the Install and Use SQL Express option, enter the password for the HP
SIM service account, and click Next.
6. On the Select Installation Type screen, select Typical, and click Next to continue.
7. You will again be prompted for the service account credentials. Key in the
credentials and click Next.
8. Click Install on the Summary screen.
9. On the Status screen, you can see the current status of the component being
installed.
10. Once all the components are installed, click Next.
11. On the Registration screen, you can enter the registration key or click Register
Later to complete the registration at a later time.
12. Click Finish to complete the installation and reboot the server.
Accessing HP SIM
1. Open the Internet Explorer.
2. Enter https://<Fully Qualified Domain Name (FQDN)>:50000 in the Address
field and press Enter.
3. At the Internet Explorer window, click File Send Shortcut to Desktop.
4. At the CMS desktop, a new HP Systems Insight Manager shortcut is created.
Note
For the purpose of all the demonstrations, click this shortcut to access HP SIM.
8 September 2010
Configuring HP SIM using the First Time Wizard

1. Once the server reboots, click the HP Systems Insight Manager icon on the
desktop to launch and configure HP SIM.
2. You will see a Security Alert window, click View Certificate, and then click Install
Certificate to install the certificate.
3. Now, you will see the login screen. Enter your service account credentials to
login.
4. If you did not register HP SIM at the end of the installation, you will see the
Registration screen again. Enter the registration key or click Register Later to
complete the registration at a later time.
5. From the First Time Wizard Introduction screen, select the Do not automatically
show this wizard again check box, and then click Next.
6. The Managed Environment screen allows you to identify the operating systems of
the devices HP SIM will be managing. By selecting the check boxes, HP SIM will
streamline what tools, collections, and reports are available. Select the type of
systems that apply to your environment, and click Next.
7. On the Discovery screen, select the option Run discovery once after wizard
finishes, and enter the IP address of your CMS so that it can be discovered in
HP SIM. You can add other servers as and when needed.
8. On the Credentials screen, you can set Sign-in and SNMP credentials for the
System Automatic Discovery task. You can also specify WBEM credentials. For
the purpose of this demo, we are using a read community string of public for
SNMP. Enter the community string used in your environment and click Next.
9. The Configure Managed Systems screen enables you to configure managed
systems as they are discovered and to specify parameters for running the
Configure or Repair Agents task. These steps are optional and can be
configured at any time from the Options menu. Also, enter the community string
used in your environment. Additionally, select Set traps to refer to this instance of
HP Systems Insight Manager and Configure secure shell (SSH) access and Host
based authentication, and Set trust relationship to "Trust by Certificate". Click
Next.
10. For the purpose of this demo, accept the default selections on the WBEM/WMI
Mapper Proxy screen and click Next. If any other software on the CMS is using
port 5989, you can change the port HP SIM uses here.
11. On the Privilege Elevation screen, you can enable privilege elevation for Linux,
HP-UX, and ESX managed systems. This enables you to sign in as an
unprivileged user and elevate the privilege to run on these operating systems.
For the purpose of this demo, we will be creating a privileged account on your
HP-UX servers, so you can skip this step by simply clicking Next.
September 2010 9
12. On the E-mail screen, review the available options for configuring email
notifications and enter an SMTP host name, which is the email address the CMS
will use when sending notifications. The senders email address field is used to
identify the sender in all HP SIM emails.
13. Review the information on the Summary screen, and click Finish.
Creating and running an HP SIM task Applying System

Properties to the CMS
1. From the main menu of HP SIM, select Options System Properties Set
System Properties.
2. In the Add targets by selecting from section, make sure the Collection option is
selected. In the associated dropdown box, select All Systems. Select the Select
"All Systems" itself check box and click Apply Next.
3. To add a new site, click Manage Sites and then click New. In the New Site
Information section, enter the following information and click Apply.
Site Name
Address 1
City
State or province
Country or region
Time zone
Postal code
4. To add a new contact, click Manage Contacts and then click New. In the New
Contact Information section, enter the following information and click OK:
Contacts first name
Contacts last name
Contact phone
Contact email
10 September 2010
Important
! It is important to note that Customer Contact Information is to be entered as a
part of the Insight RS installation process. Customers may be contacted by HP
to:
Verify system failure
Diagnose the problem
Recommend a fix
Confirm delivery type i.e. Engineer onsite, CSR etc.
Confirm time to initiate repair
Complete and accurate contact information is imperative for timely resolution of
customer issues. If the customers contact information changes, then it is their
responsibility to update the information in the Insight RS software as soon as
possible.
5. Make sure you select the newly created Site Name and Primary customer
contact from the dropdown, and then click Schedule.
6. Assign a task name, select the Not scheduled option and the Run now check
box, and click Done.
7. At this point, you will verify that the system properties are applied to your CMS
and add its serial number.
8. From the All Systems table of HP SIM, click the system name of your CMS.
9. Click the Tools & Links tab, and select the Edit System Properties link.
10. On the Edit System Properties screen, verify that all system property values are
there and key in entitlement information.
11. Now, schedule the task you created so that the system properties are
automatically applied when any new devices are discovered in HP SIM.
12. From the main menu of HP SIM, click Task & Logs View All Scheduled Tasks.
Highlight the task that you had created, and click Edit.
13. Ensure that All Systems exists in the Verify Target Systems table, and then click
Next. Scroll down, and click Schedule.
14. On the Step 3: Schedule Task screen, select the When new systems or events are
added to the collection option, and click Done.
Configuring system links within HP SIM

Perform the following steps to configure HP SIM to use the full DNS name when
creating links to a managed device. This is required as WEBES uses the full DNS
name.
1. From the HP SIM main menu, select Options Security System Link
Configuration, and select the Use the systems full DNS name option.
2. Click OK.
September 2010 11
Demo 3 Installing and configuring HP Systems

Insight Manager on a VMware ESX Server
When the CMS is a located on a Windows 2003 virtual machine of VMware ESX or
ESXi, HP SIM is installed using the steps demonstrated in the previous lesson. The
primary differences are, you must:
Manually edit several of the CMS' system properties
Discover and configure the ESX server in HP SIM
Manually edit several of the CMS' system properties

If the CMS exists on a VMware ESX virtual machine, HP SIM is not able to determine
hardware information about the device. As a result, you must manually enter the
system subtype and product model in the Edit System Properties screen of the CMS.
1. From the All Systems table of HP SIM, click the system name of your CMS.
2. Click the Tools & Links tab, and then click the Edit System Properties link.
3. Click on the drop box of the System Subtype 1 field and select HP ProLiant.
4. Click on the Product model field, and type in ProLiant.
5. At this point, if the Contract and Warranty information has not been completed,
input the contract and warranty information, making sure to create and select
site and contacts to associate with the CMS.
Discover and configure the ESX server in HP SIM

1. On the CMS, start the WEBES Director: Start Programs Hewlett-Packard
Service Tools Web-Based Enterprise Services Start Director.
2. Open HP SIM.
3. From the main menu of HP SIM select Options Discovery Manual
discovery to discover a single system.
4. Enter the FQDN of the VMware ESX server and click [Add System] followed by
[OK].
5. Upon completion, click on the All Systems link in the System and Event
Collections area of HP SIM. You should see the system name of your server.
6. Click on the system name of your VMware ESX server.
7. From the All Systems screen of HP SIM, click on your CMS system name and
click the Tools & Links tab.
8. Click on the Edit System Properties link.
9. Verify all of the system properties, applied by the Automatically Set System
Properties task, in the last section, have been set properly.
12 September 2010
10. Enter Serial Number for the system.

11. Click OK to save the changes to save the system properties of your CMS.
12. Click on the System tab and then on the System Management Homepage link.
13. Click [Yes] on the Security Alert Screen.
14. On the SMH login screen, make sure the Automatically Import Management
Server Certificate checkbox is checked and then login with the ESX's credentials.
15. Click on Settings SNMP Configuration.
16. Scroll down to the bottom of the SNMP Configuration page and click [Send
Trap].
17. Close SMH.
18. From HP SIM, click on the Events tab of your lab groups ESX Server.
September 2010 13
Demo 4 Installing and Configuring Insight RSA

software
Installing initial Insight RSA component software
Note
If you are not using a Web proxy server, you must open your firewall to allow
communication over port 443. The Remote Support Client uses port 443 to send
encrypted data to HP and to receive acknowledgements and information in
response to requests from the Remote Support Client software.
The Remote Support Client communicates directly with the HP Support Center through
the firewall or web proxy server (if a web proxy server is in use). The Remote Support
Client supports connecting directly to the Internet or connecting through a proxy
server and supports all proxy servers conforming to the HTTP/1.0 Specification.
Kerberos authentication is not supported by either the SWM or the Remote Support
Client.
Because the Remote Support Software Manager does not support proxies using
proxy auto-configuration scripts or NT LAN Manager (NTLM) authentication (also
known as Integrated Windows Authentication), it is recommended that you also not
use these for the Remote Support Client communications. You may choose to use a
different proxy server for SWM that does not use NTLM and a separate proxy server
for the Remote Support Client.
Note
It is now required that the CMS uses DNS resolution to determine the IP
addresses for the HP Support Center.
Note
If you receive errors citing cookies issues when attempting to access the Remote
Support Configuration and Service screen, refer to the links below:
For information about updating cookies settings for Internet Explorer see:
http://support.microsoft.com/kb/196955
For information about updating cookies settings with Mozilla see
http://www.mozilla.org/projects/security/pki/psm/help_21/using_priv_help.html
1. Click Start All Programs Hewlett-Packard Remote Support Software

Manager Initialize Remote Support Software Manager.
2. Read the license agreement, and then click Agree. At the HP Insight Remote
Support Product Installation popup, select the check box and click Next.
14 September 2010
3. From the optional components list in the table, select the check box for the
components you want to install and click Next.
4. The prerequisites are verified. In case of any issues, resolve the problem and
then click Next to continue. The selected components are copied to the disk.
5. The installation process begins. This may take some time. When all the
components get installed, click Next.
6. For the Update Strategy, leave the Automatic or on-line updates option selected
by default and click Next.
7. Read the privacy settings screen, select the Select All check box, and then click
Next.
8. Enter the HP SIM credentials, and then click Next.
9. Select the I use a web proxy server check box and verify the information.
10. Enter the Business Name, Country or Region and Email Address fields, and click
Next.
Note
For any fields labeled Business Name or Company Name, be consistent and
enter the exact same name in all these fields.
11. The system will check connectivity to the HP Support Center. This is
accomplished by the Remote Support Software Manager pulling down a test
package from the data center. This applies the Remote Support Software
Manager URLs and proxy settings. When the initialization and configuration of
this product is complete, click Finish.
12. The system will begin downloading and installing the CMS compulsory
packages.
13. The Remote Support Software Manager user interface will automatically open to
the packages screen. Click the Preferences link under the left navigation area of
the Software Manager UI. You can change the default Global Automation Level
of Automatic Install to either Automatic Download or Manual.
14. Click the Company link under the left navigation area of the Software Manager
UI. This was automatically populated based on your input during the Initialize
Remote Support Software Manager steps.
15. Click the Contacts link under the left navigation area of the Software Manager
user interface. By default, this gets populated for you based upon your inputs
during the Initialize Remote Support Software Manager steps. Edit the settings
for Edit the settings for receiving emails associated with the availability of
software updates and/or status and connectivity reporting and click Submit.
16. Click the Contacts link under the left navigation area of the Software Manager
UI. This was automatically populated for you based upon your input during the
September 2010 15
Initialize Remote Support Software Manager steps. Select the appropriate

enable email check boxes, and then click Submit.
17. Click the Bandwidth link under the left navigation area of the Software Manager
UI. You can change the bandwidth allocated to the Software Manager
according to your environment.
18. Click the Packages link. Only CMS compulsory packages were installed during
the initialization steps. Install any additional packages that you may need by
clicking the corresponding Install link, such as:
Unreachable Device Notification
Advanced Configuration Collector Depot for HP-UX 11i servers
Any Remote Support End-Point server software you may need
19. Close the Software Management UI.
16 September 2010
Demo 5 Registering the Remote Support client

1. The Remote Support Client of the CMS must be registered with the HP Data
Center before events from managed systems can be transmitted by the Remote
Support Client to the HP Data Center.
2. Open HP SIM from the desktop of your CMS.
3. From the main menu of HP SIM, select Options Remote Support Configuration
and Services.
4. Click Continue on the Privacy Information screen.
5. Complete CMS Location information and the CMS Administrator information
Contact Information required. In the HP Account or Service Provider Contact
Information, enter HP if Insight RSA is installed by an HP employee. If it is being
installed by a Service Provider or the customer, they should use their company
name.
6. Enter your proxy server information.
7. Make sure the Enable systems for Remote Support Services upon discovery
check box is selected. Click Submit Updates and Register to initialize the
registration. After approximately 1 minute, the Remote Support Configuration
and Services screen will disappear and then return without the highlighted
"Remote Support Configuration and Services" message at the top of the page.
8. Click Test Data Submittal at the bottom of the screen. This validates connectivity
to the data center using the Insight RSA client. You should see a response of
Action state: Successfully created the test event.
September 2010 17
Demo 6 Configuring CMS entitlement

In these steps, we will configure entitlement for the CMS in HP SIM.
1. To entitle the CMS, select Options Remote Support Configuration and
Services.
2. Click the Entitlement tab. Select the check box associated with your CMS in the
Remote Support System List table. From the Action List dropdown box, select
Entitle Checked and then click Run Action.
3. Once the Action Status Message indicates "Finished entitlement check", click
Refresh to update the information displayed on the screen. A green circle with a
check mark should appear in the "ENT" column of the line associated with the
system name of your CMS.
18 September 2010
Demo 7 Configuring Service Providers

Note
If all your support is provided by HP, do not make any changes to this page.
Note
If you do not know your Service Provider ID, contact your Service Provider.
1. To add a Service Provider, click Options Remote Support Configuration and

Services and click the Service Providers tab.
2. Click Add Provider.
3. Enter the Provider ID and click Look Up.
4. Once the Service Provider details show up, click Accept.
5. To associate a service provider with a managed device, select the check box for
the device in the Associate Providers table.
6. Select the support provider from the Select Support Provider drop down menu.
This should be the provider that provides support for the managed device.
7. You can also select the sales provider using the Select Sales Provider drop down
menu. This should be the provider you prefer to work with for IT solutions.
8. Click Update Selected Items for the changes to take effect.
September 2010 19
Demo 8 Configuring HP-UX Servers

Insight RSA Managed HP-UX Server prerequisites
There are two primary types of Insight RSA perquisites for a managed HP-UX Server,
and the following links will provide a demo of how to meet those prerequisites:
System hardware and software prerequisites, includes minimum hardware
requirements, patches, ancillary software, and specific software versioning.
There are two methods for determining if the hardware and software perquisites
are met:
Installation Advisor software, included in the Remote Support Software
Manager as of Insight RSA A.05.40, provides two scripts that can be used
to determine if the prerequisites are met.
Managed Systems Guide - The HP-UX Managed System Requirements for
Insight Remote Support section of the HP Insight Remote Support Advanced
A.05.40 Managed Systems Guide has a detailed list of the prerequisites
and the commands that can be used to determine if the requirements are
met.
Creating a Non-privileged User on the HP-UX Server, is security best practices
for creating a user with specific management rights instead of using root.
Installation Advisor software

The Installation Advisor provides utilities that verify monitored systems are
communicating properly, utilities that collect all relevant log files if a problem is
encountered, and utilities to configure monitored endpoint devices to communicate
properly. The Installation Advisor may not provide a complete survey of your
customers HP-UX endpoint, in that case, consult the HP-UX Managed Systems
Requirements for Insight Remote Support > Software and Patch Requirements for HP-
UX 11.23, stopping at the beginning of section titled Software and Patch
Requirements for HP-UX 11.31 of the "HP Insight Remote Support Advanced Managed
Systems Guide".
The RSSWM copies the Installation Advisor, as a archived file to the CMS. In this
demo, we will ftp the Installation Advisor from the CMS to your lab groups HP-UX
server and then run the scripts necessary to verify prerequisites have been met.
ftp Installation Advisor Files from CMS to HP-UX server

1. From a DOS command window on your CMS, change to the c:\Program
Files\HP\Installers\InstallationAdvisor directory using the following command:
cd c:\Program Files\HP\Installers\InstallationAdvisor
2. From the DOS window on your CMS, ftp to your lab groups HP-UX server and
login as root.
ftp <IP address of your lab groups HP-UX server>
20 September 2010
3. Create a directory on the HPUX server off of the /tmp directory called
installationAdvisor.
mkdir /tmp/installationAdvisor
4. Change to the newly created /tmp/installationAdvisor directory on the HP-UX

server:
cd /tmp/installationAdvisor
Note
Make sure to ftp the file as an ASCII not a binary file.
5. ftp the InsightRsHpuxPrereqCheckv24.sh and InsightRsHpuxSetup.sh files to your

lab groups HP-UX Server:
mput InsightRsHpux*
Note
There are two HP-UX specific files that get copied and mput will ask permission to
copy both.
6. Exit ftp:
Bye
Run Installation Advisor Scripts on your HP-UX Server

1. Access your lab groups HP-UX Server
2. Change to the directory were you ftpd the Installation Advisor files:
cd /tmp/installationAdvisor
3. Now we have to make the files executable.

chmod +x *.sh
4. Run the InsightRsHpuxPrereqCheckv24.sh script.

./InsightRsHpuxPrereqCheckv24.sh
5. View the script output for any deficiencies. If deficiencies are reported, resolve
and rerun the script.
6. Run the InsightRsHpuxSetup.sh script
./InsightRsHpuxSetup.sh
September 2010 21
7. View the script output for any deficiencies. If deficiencies are reported, resolve
and rerun step 6.
Important
! If in the process of meeting the prerequisites you have to install or update
software, you must remove and reinstall System Fault Management, using the
following commands because SFM must be the last prerequisite installed.
/usr/sbin/swremove SysFaultMgmt
/usr/sbin/swinstall x autoselect_dependencies=false s
10.99.0.252:/hpvl_depot/ignite/RSP SysFaultMgmt
Discovering managed HP-UX devices and configuring entitlement

1. From the main menu of HP SIM, select Options Discovery. Ensure that
Manual Discovery option is selected, and then click Edit. Enter IP address of
your HP-UX server in the Enter the systems name or IP address field. Click Save,
and then click Run Now.
2. Click the All Systems link in the System and Event Collections area of HP SIM.
You should see your HP-UX server in the table.
We had created a task that automatically applies the location information we
supplied to all discovered system. As you will see in this section, all of the location
information has been applied to the HP-UX server except for the entitlement
information, which we will now add.
3. From the All Systems list of HP SIM, click the system name of your virtual HP-UX
server. Click the Tool & Links tab, and then click the Edit System Properties link.
4. Enter the entitlement information in the Contract and Warranty Information
section and click OK.
5. Click Options Remote Support Configuration and Services, and then click the
Entitlement tab.
6. Select the check box on the line associated with your HP-UX server, from the
Action List pull-down menu, select Entitle Checked, and then click Run Action.
7. When the Action Status Message indicates Finished entitlement check, click
Refresh and you should see a green circle with a white check mark appear in
the Entitlement ENT column for your HP-UX server.
22 September 2010
Verifying Insight RSA Management of a HP-UX Server is

operational
1. In All Systems, click the system name of your managed HP-UX Server and go to
the Tools & Links tab.
2. Click System Credentials. Select the system name, and then click Edit system
credentials.
3. Click Show advanced protocol credentials and go to the WBEM/WMI tab.
4. Enter the username and password, and then click OK.
5. Now, go to Options Events Subscribe to WBEM events.
6. Verify that your managed HP-UX Server is listed, and then click Next.
7. On the Task Confirmation screen, click Run Now and verify that the task
completed successfully.
8. Now, to send a test WMI event, open the System Management Homepage of
your managed HP-UX Server.
9. Go to Settings, and then click Send Test Indication.
10. Select the event type, and then click Send.
11. Return to HP SIM and go to the Events tab for your managed HP-UX Server.
12. Verify that the test event has been received.
September 2010 23
Demo 9 Configuring Linux Servers

Prerequisites for Insight RSA management of Linux Servers
Note
Always refer to the documentation for the latest list of prerequisites.
Installing PSP on the Linux Server

1. Open a terminal window on Linux Server by selecting Applications
Accessories Terminal.
2. Unpack the PSP file.
3. Untar the file using the tar xvf command.
4. Scroll through the files that were untarred in the Linux terminal window and
locate the line with an install***.sh in it, and note the name of the file and the
full path to that file.
5. Change the current directory to the path determined in step 4 with the following
command: cd <install path>.
6. Execute the install. This opens the HP ProLiant Linux Deployment Utility, which
lists the components that will be installed as part of the PSP. These include all the
management agents required by the solution. Some of the components are
configurable. These are:
HP System Management Homepage for Linux.
HP SNMP Agents for Red Hat Enterprise Linux 5.
HP Version Control Agent for Linux.
7. After configuring the components, select the Reboot server after successful
completion of ProLiant Support Pack if components require it check box. Then
start the installation by clicking the Install.
Configuring sudo
1. From a terminal window, enter: visudo.
2. Scroll down until you find the statement Defaults requiretty.
3. The line should be commented out as follows: Place the cursor at the beginning
of the Defaults requiretty line. Enter the letter i to allow you to edit the file.
4. Enter # and a space to comment the line. Press the Esc key to exit the insert
mode. Press the colon key (:), followed by wq! to save the file and exit.
5. Close the Terminal window.
24 September 2010
Discovering Linux servers and configuring Insight RSA

management of Linux Servers
Using HP SIM Discovery to discover your Managed Linux Server
1. From the main menu of HP SIM select Options Discovery, and using the IP
address of your Linux server, run a discovery task.
2. Upon completion, click on the All Systems link in the System and Event
collections area of HP SIM. You should now see your Linux server listed.
Using the HP SIM Configure and Repair Agents feature to set up Trust by
Certificate on the Managed Linux Server
1. From the HP SIM All Systems collection, select the name of your Linux server.
2. From the HP SIM menu, select Configure Configure or Repair Agents.
3. Skip the Install Providers and Agents section as agents are already installed on
the Linux server. Click Next.
4. On the Configure or Repair Settings screen, clear everything except for Trust by
Certificate. Click Next.
5. On the Enter credentials screen, select the Use the following credentials for all
systems option and enter the user credentials for your Linux server.
6. Click Run Now.
7. Verify completion of the task.
8. Verify the trust was set up by connecting to the System Management Homepage
for your managed Linux server. Click on All Systems the name of our
managed Linux server System Management Homepage.
9. On the System Management Homepage, go to Settings Security and verify
that the trust mode is set to Trust by Certificate and the Trusted Management
Server Certificates screen shows that the SIM server certificate is in the trusted
certificate list.
September 2010 25
Configuring the snmpd.conf file

Note
An appropriate view must be defined in the snmpd.conf file for OSEM to be able
to do SNMP-Gets. The following steps are used to configure an appropriate view
for Red Hat 3, 4, and 5. SuSE does not need to have the view statement.
1. On the System Management Homepage for your Linux server, click the Settings
tab, and then select the SNMP Configuration link.
2. Within the SNMP Configuration File window scroll down to the section headed
Third create a view for us to let the group have rights to. Add the following view
statement:
view systemview included .1 80
3. Also, comment out the existing view statements.

4. Click the Change button below the SNMP Configuration File window.
5. Scroll down towards the bottom of the SNMP Configuration screen, select the
restart option, and then click set.
6. Close the System Management Homepage window.
Input managed Linux Servers Serial Number into HP SIM and Verify
Entitlement
1. From the All Systems list of HP SIM, click on the system name of your Linux
server.
2. Click the Tool & Links tab associated with your Linux server, and then click the
Edit System Properties link. Scroll down to the Contract and Warranty
Information section of the screen and enter the entitlement information. Click OK.
3. From the main menu of HP SIM, select Options Remote Support
Configuration and Services, and then click the Entitlement tab.
4. Select the check box associated with your Linux Server. From the Action List pull-
down menu select Entitle Checked and then click Run Action. When the Action
Status Message indicates Finished Entitlement check, click Refresh and you
should see a green circle with a white check mark appear in the Entitlement
(ENT) column for your lab Linux server.
26 September 2010
Verifying Insight RSA monitoring of a Linux Server is operational

1. From the All Systems list of HP SIM, click on the system name of your Linux
server.
2. From the System tab, click the System Management Homepage link.
3. Click the Settings tab, and then select the SNMP Configuration link.
4. Scroll down to the bottom of the SNMP Configuration screen, and then click
Send Trap.
5. Close the System Management Homepage.
6. Click the Events tab of your managed Linux server. You should see a generic
trap and type 3 and 4 events.
7. Click either the Type 3 or Type 4 event. Review the contents of the event details.
8. Click the Generic trap event, and the Event Details screen for the Generic trap
appears.
September 2010 27
Demo 10 Configuring Storage Management

Servers
Managed system prerequisites for a Windows-based Storage
Management Servers
Prerequisites for a Command View Server
1. Verify the Management Agents for Servers are installed on the server by
selecting Start Control Panel HP Management Agents.
2. Now, we will verify that the Data source selected in SMH. Open SMH and go to
the Settings tab.
3. Under Select SMH Data Source, click Select.
4. Notice that for servers with WBEM providers installed, the SMH data source
defaults to WBEM. For this demonstration, we will be using SNMP as the data
source. Select SNMP and click Select.
5. We will now verify if SNMP service is installed and operational by clicking on
Start Administrative Tools Services, and then locate and click SNMP
Service.
6. Double-click the SNMP Service, and verify that the service is Started.
7. Go to the Agent tab, and verify the contact information.
8. Click the Traps tab of the SNMP Service Properties window, and enter the IP
Address of your CMS as a trap destination.
9. Click the Security tab of the SNMP Service Properties window, and make sure
the Accept SNMP packets from any host option is selected.
10. Restart the service for the changes to take effect.
The Event Log Monitoring Collector (ELMC) provides error condition detection of the
event log for monitored end point systems and communicates these events to WEBES
remotely for analysis. In the next few steps we will share the folder on the CMS so
that we can copy and install ELMC on the Command View Server.
1. First share the folder containing the ELMC setup file on the CMS.
2. Now, connect to your Command View Server and access the folder that you
had shared in the previous step by using the IP address of your CMS.
3. Copy the exe file and paste it on a local folder on the Command View Server.
4. Now, run the setup file to start the installation. The InstallShield Wizard appears
and the installation starts.
5. Once the installation is complete, the InstallShield Wizard disappears.
28 September 2010
MC3 is a required component on the SMS. The mc3.exe file is located in the
C:\Program Files\HP\CM\Installers directory of the CMS.
1. Share the setup file on the CMS in the same way as we did for ELMC.
2. Access the shared folder from your SMS and copy the mc3.exe file to your SMS.
3. Click the mc3.exe file in that directory, and accept all defaults to install MC3.
4. Open the Control Panel and select Add or Remove Programs to verify that HP
Mission Critical Common Components (MC3) is installed.
Discovering and configuring managed Windows-based Storage

Management Servers
Discovery of a Storage Management Server (SMS)
1. From the main menu of HP SIM, select Options Discovery. Ensure that
Manual Discovery option is selected, and then click Edit. Enter IP address of the
Command View Server. Click Save and then click Run Now.
2. Click All Systems, you should now see your Command View Server listed.
In the next few steps we will configure HP SIM settings for the Command View
Server.
3. Click the system name of the Command View Server. From the main menu of HP
SIM, select Tools & Links System Credentials and click Edit System
Credentials.
4. Select the WBEM/WMI tab and enter the Command View Server's login
credentials and click OK.
5. Click View all credentials to verify the credentials that we just entered are visible.
6. Return to the Tools & Links tab of your Command View Server.
7. Select the Edit System Properties link, scroll down to the Contract and Warranty
Information section of the screen and enter the entitlement information. Click OK.
September 2010 29
Configure Command View credentials in WEBES SEA

HP SIM provides Web-Based Enterprise Service (WEBES) with all the information it
needs. Perform the following steps to verify if all the information has been backfilled
by HP SIM:
1. Go to Start All Programs Hewlett-Packard Service Tools System Event
Analyzer System Event Analyzer.
Note
If the security certificate warning appears, click Continue to this website.
2. Click the Protocols button in the top toolbar and click the WMI WBEM
(Windows) link.
3. Notice that the WBEM credentials have already been populated by HP SIM.
4. Now, close the System Event Analyzer window.
It is a best practice to secure communications between the CMS and Command View
Server. In the next few steps, you will establish security between the CMS and
Command View Server with a security certificate.
1. Open a new Internet Explorer window to access the Command View User
Interface (UI).
2. Using the Command View UI, select the Server Options link in the upper right
corner of the page. This opens the Management Server Options page.
3. Select System Insight Manager/Replication Solutions Manager trust
relationships. This opens the SIM/RSM Trust Relationships page. Click Install
Certificate. Enter the FQDN or IP address of the CMS, and click Install
Certificate.
4. Now, we will verify if the certificate for SMI-S is loaded, to do so click Server
Options, and then click Other application trust relationships.
5. Verify that the SMI_EVA_Provider certificate is loaded for the local SMS, and
then close the Command View UI.
6. Open and log into HP SIM again, and select Options Identify Systems.
7. In the Step 1: Verify Target Systems screen, the Command View Server should be
listed, and then click Run Now. Make sure you see messages indicating that
SMI-S CIMOM is installed.
8. Click the All Systems collection link in HP SIM and you should see the EVA has
been discovered.
9. Click the EVA system name, select the Tools & Links tab, and then click the Edit
System Properties link.
10. Scroll down to the Contract and Warranty Information section of the screen and
then enter the entitlement information. Click OK.
30 September 2010
11. Now, select Options Remote Support Configuration and Services, and then
click the Entitlement tab. If the security dialog box appears, click OK.
12. Select the Command View EVA server and the EVA itself. From the Action List
pull-down menu select Entitle Checked, and then click Run Action.
the 'ENT column for the EVA and Command View Server.
Verifying Insight RSA monitoring of a Windows-based Storage

Management Server is operational
Verify that the Command View Server is communicating with the CMS through
SNMP.
1. In HP SIM, click the system name of your Command View Server. Click System
Management Homepage to open the System Management Homepage (SMH)
for the server.
2. In the SMH window, click the Settings tab, and then click SNMP & Agent
Settings.
3. Click Send Test Trap from the Management Agents Configuration screen. Click
OK on the prompt asking you "Are you sure you want to send a test trap".
4. Close Systems Management Homepage, and go back to HP SIM.
5. Click the system name for your Command View Server, and then click the Events
tab. You should see a Generic Trap event in the list of events.
6. You can also click the event to view the details.
7. Now, we will verify if Command View Server event log information is sent to the
CMS by performing the following steps.
8. Open a command prompt and enter the following command: wccproxy test
9. Close the DOS window.
10. Return to your CMS and verify if the trap appears as a Type 4 event within HP
SIM.
September 2010 31
Demo 11 Configuring Windows Servers

Insight RSA Managed Windows Server Prerequisites
Note
Always refer to the documentation for the latest list of prerequisites.
1. You should always ensure that the latest PSP is installed on your Managed
Windows Server. You can download it from www.hp.com.
2. Any configurable PSP components should be configured. Refer to the Installing
ProLiant Support Pack (PSP) section of Installing and Configuring the CMS/CMS
prerequisites.
3. Click the executable file, and then click Extract to extract the files. Once the files
are extracted, run the setup.exe file to start the installation.
4. Select Localhost, and click Next. Set the Bundle Filter options, and click OK.
5. On the components screen, you can also configure any of the components like
System Management Homepage, Version Control Agent etc.
6. Select Reboot System After Installation, and click Install. Now the PSP will install
and the system will reboot after installation.
7. Once the PSP is installed, you should configure the WBEM settings through the
System Management Homepage interface.
Note
Ensure that a WBEM/WMI account is configured on the Managed Windows
server. An account with this name should be present on both the CMS and the
Managed Windows Server.
8. Open System Management Homepage from the icon on the desktop.

9. Click Settings and then click Select under SMH Data Source.
10. Ensure that WBEM is selected as the data source.
Note
If you wish to use SNMP as the data source, refer to the prerequisites demo for
the Command View Server for steps to configure SNMP.
32 September 2010
Discovering a managed Windows Server and configuring its

entitlement
Discover a Managed Windows Server
1. From the main menu of HP SIM, select Options Discovery.
2. Make sure that the Manual Discovery option is selected, and click Edit.
3. Enter the IP address of your Managed Windows Server and click Save.
4. Click Run Now to run the discovery. Click All Systems, you should now see your
Managed Windows Server listed.
Configuring Entitlement details for the Managed Windows Server

1. Click the system name of your Managed Windows Server, select the Tools &
Links tab, and then click the Edit System Properties link. Scroll down to the
Contract and Warranty Information section of the screen and enter the
entitlement information and click OK.
2. Now, select Options Remote Support Configuration and Services, and then
click the Entitlement tab.
3. Select the Managed Windows Server. From the Action List pull-down menu select
Entitle Checked, and then click Run Action.
the ENT column for the server.
September 2010 33
Verifying remote monitoring of a Windows Server is operational

1. In All Systems, click the system name of your Managed Windows Server and go
to the Tools & Links tab.
2. Click System Credentials. Select the system name, and then click Edit system
credentials.
3. Click Show advanced protocol credentials and go to the WBEM/WMI tab.
4. Enter the username and password, and then click OK.
5. Now, go to Options Events Subscribe to WBEM events.
6. Verify that your Managed Windows Server is listed, and then click Next.
7. On the Task Confirmation screen, click Run Now and verify that the task
completed successfully.
8. Now, to send a test WMI event, open the System Management Homepage of
your Managed Windows Server.
9. Go to Settings, and then click Send Test Indication.
10. Select the event type, and then click Send.
11. Return to HP SIM and go to the Events tab for your Managed Windows Server.
12. Verify that the test event has been received.
34 September 2010
Demo 12 Configuring P4000 SAN Solutions

P4000 SAN Solutions Prerequisites
HP LeftHand Networks Service Console (also known as Health Check) is being
replaced by HP Insight Remote Support A.05.50 as the remote support solution for
the LeftHand and HP P4000 platforms.
Centralized Management Console (CMC) requirements

CMC is used to configure P4000 SAN Solutions
Hardware requirements: CMC 8.5, Windows version has the following
requirements:
35MB disk space for complete install
50MB RAM during run-time
Software requirements: You require CMC 8.5. This can be downloaded from
www.hp.com/go/P4000downloads. This is also included in the SAN/iQ
Management SW DVD package. The documentation for CMC 8.5 is available
as part of the SAN/iQ and HP P4000 SAN Solutions documentation at
http://www.hp.com/support/manuals.
For more information, you can download IRSA HP StorageWorks P4000 SAN
Solutions Migration Guide from
http://www.hp.com/go/insightremoteadvanced-docs.
HP StorageWorks P4000 SAN Solution requirements

Software Requirements: HP Insight Remote Support has a minimum requirement
of HP P4000 SAN/iQ version 8.5, therefore only platforms supported by
version 8.5 and higher will be able to migrate to HP Insight Remote support. In
addition to SAN/iQ version 8.5, patch 10076 is required for Remote Support.
To download the patch:
1. Go to http://www.hp.com/support/storage.
2. Select either LeftHand NSM Storage Systems or P4000 SAN Solutions.
3. Select the option that represents your product.
4. Select Download drivers and software.
5. Select your product.
6. Select Cross operating system (BIOS, Firmware, Diagnostics, etc.).
7. Download the patch version 10076.
Note
Before installing the patch, always check for the latest patch available at
http://www.hp.com/support/storage and install accordingly.
September 2010 35
SNMP Configuration: SNMP must be enabled on the CMS to communicate with

the P4000 SAN Solution. You need to add the IP address of your P4000 SAN
Solution to the CMS trap receiver list or allow the CMS to receive traps from all
the IP addresses. If you do not modify the SNMP defaults that CMC uses, then
P4000 SAN Solution and the CMS can communicate without any modification.
To configure the SNMP service:
1. On the CMS, click Start Control Panel Administrative Tools Services.
2. Check that SNMP Service and SNMP Trap Service are listed as installed
Services under the Name column. Both of these Services should have the Status
as Started and Startup Type as Automatic. If either of these Services are not
installed, you should install them at this time.
3. Double-click SNMP Service to open the SNMP Service Properties window.
4. Select the Traps tab. Here, ensure that a community string is listed and localhost
exists as a trap destination.
5. Select the Security tab. You can select any of the following options:
Accept SNMP packets from any host
Accept SNMP packets from these hosts and click Add to add your
managed system to the list.
6. Click OK to accept your changes and exit the SNMP Service Properties
configuration window.
Install and Configure CMC

Install the Centralized Management Console (CMC) on the computer that you will
use to administer the SAN. While installing the CMC, you require administrative
privileges. To install CMC:
Note
For this demonstration, you will be installing the CMC on the CMS.
1. Insert the HP StorageWorks Management DVD in the DVD drive. The installer
should launch automatically.
Note
You can also download CMC from www.hp.com/go/P4000downloads.
2. Click Agree to accept the END USER LICENSE AGREEMENT.

3. At the HP LeftHand Management Software for Windows screen, select the
Centralized Management Console link.
4. At the HP LeftHand Centralized Management Console screen, click Install CMC.
The HP LeftHand Centralized Management Console Installer screen appears.
Click Next.
36 September 2010
5. Select the I accept the terms of the License Agreement option and click Next.
6. When prompted, select the Complete installation option and click Next.
7. Follow the instructions on further screens and click Next. Click Install to start the
installation. Finally, click Done to complete the installation. The CMC welcome
screen launches.
Next, you need to start the Find Nodes wizard to discover the SAN systems on the
network. You can search the SAN systems using either IP addresses or host names, or
by using the subnet mask and gateway of the storage network. To do this:
From the Welcome screen, click the Find Nodes Wizard icon. The Welcome to the
Find Nodes Wizard screen appears.
1. At the Welcome screen, click Next. The Search for nodes globally or individually
screen appears. Here, you can search using either of the following two options:
By Subnet Mask: Searches using the subnet mask and gateway of the
storage network.
By IP address or Hostname: Searches using either IP addresses or host
names.
2. For this demonstration, leave the By IP address or Hostname option selected and
click Next.
3. At the Add IP Address or Hostname popup, enter the IP address or host name of
your SAN system and click OK.
4. At the Search by node IP address or host name screen, make sure the node is
listed. Select the node and click Finish Close.
5. At the Summary screen, ensure that your SAN system is discovered. Finally, click
Close to close the Find Nodes Wizard.
September 2010 37
Configuring the P4000 SAN Solution

Upgrading the SAN/iQ Software on the P4000 SAN Solution
To upgrade SAN/iQ 8.5 on the P4000 SAN Solution, you will be using the
Centralized Management Console (CMC). If your P4000 SAN Solution already has
the latest SAN/iQ installed, you do not need to perform this procedure.
1. At the CMC, expand your P4000 SAN Solution from the left pane.
2. Enter the user name and password of your P4000 SAN Solution and click Log
In. The Gathering Network Data popup appears showing the progress of
gathering data from the network. This may take some time.
3. After the data gathering process finishes, select your SAN system node from the
left pane of the CMC.
4. Under the Details tab, your P4000 SAN Solution is listed under the Nodes table.
Highlight your P4000 SAN Solution by clicking on it. Next, right-click on it and
select Install Software.
5. At the Install Software screen, browse to the location where the installation file of
SAN/iQ 8.5 upgrade file is stored. Select the file and click Open Install File.
6. The upgrade file path appears in the File Name field. Next, click Install.
7. A warning message appears to ensure that the data protection level for your
volumes and snapshots is Network RAID-10 (2-Way Mirror) or higher. Click
Install.
8. The installation process begins. The Install Status screen appears showing the
installation progress. A popup appears after the installation is complete. Click
OK and close the Install Status screen.
9. Click the Registration tab. At the Registration tab, verify that SAN/iQ is updated
and the version is 8.5.
Note
In the latest SAN/iQ software upgrade guide, there are different steps required
depending upon what version you are upgrading from. Depending upon the
previous version of SAN/iQ software you have, perform the steps specific to that
version in the SAN/iQ software upgrade guide available at
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c0207306
3/c02073063.pdf. Remember that any failure to follow the steps provided in the
guide could result in loss of access to data.
Note
When installing or upgrading SAN/iQ 8.5, do not modify the default SNMP
settings. The default settings are used by Insight Remote Support. Also,
communication between the P4000 SAN Solution and the CMS will not function
properly if the SNMP settings are modified.
38 September 2010
Installing the SAN/iQ 8.5 Patch 10076 on the P4000 SAN Solution
In addition to SAN/iQ version 8.5, patch 10076 is required for Remote Support. To
install this patch perform the following steps:
1. Under the Details tab of CMC, your P4000 SAN Solution is listed under the
Nodes table. Highlight your P4000 SAN Solution by clicking on it. Next, right-
click on it and select Install Software.
2. At the Install Software screen, browse to the location where the patch installation
file is stored. Select the file and click Open Install File.
3. The patch file path appears in the File Name field. Next, click Install.
4. A warning message appears to ensure that the data protection level for your
volumes and snapshots is Network RAID-10 (2-Way Mirror) or higher. Click
Install.
5. The installation process begins. The Install Status screen appears showing the
installation progress. A popup appears after the installation is complete. Click
OK and close the Install Status screen.
Configuring the P4000 SAN Solution Communications

In the following steps you will be verifying your SNMP settings. If you did not modify
the SAN/iQ SNMP settings while installing/upgrading SAN/iQ, you should not
need to make any updates while performing the following step.
1. Open the CMC application. From the left pane, expand your SAN system and
select SNMP. Open the SNMP General tab.
2. At the SNMP General tab, verify that the Agent Status is Enabled and the CMS
host IP address is listed under the Access Control table. If the Access Control
shows default, this means that any device can access the P4000 device through
SNMP.
Note
The SNMP settings on the P4000 SAN Solution need to match the SNMP
settings on the CMS.
3. Next, from the left pane, select Alerts.

4. At the Alert Setup tab, verify that alerts are configured with the trap option for
each SAN system.
5. Now, you need to add the CMS IP address to the P4000 SAN Solution's SNMP
trap send list. The CMS IP address is required to configure SNMP traps on each
SAN system. From the left pane, select SNMP.
6. Select the SNMP Traps tab and then click the SNMP Traps Tasks.
7. From the dropdown, select Edit SNMP Traps.
8. At the Edit SNMP Traps dialog box, click Add.
September 2010 39
9. At the Add IP or Hostname dialog box, enter the IP address or hostname into the
IP or Hostname field. Also, verify that the Trap Version is v1, and click OK.
10. Click OK to close the Edit SNMP Traps dialog box.
Discovering and Configuring P4000

1. From the HP SIM main menu, click Options Discovery.
2. At the Discovery screen, click New to create a P4000 SAN Solution discovery
task.
3. From the New Discovery section, select the Discover a single system option.
4. Enter the name of the Discovery task and your P4000 SAN Solution IP address
and click Save.
5. To run the discovery task, select your P4000 SAN Solution discovery task and
click Run Now. Scroll down and verify that the Summary Status is set to
Complete.
6. Next, you will be editing the P4000 SAN Solution properties. Click All Systems
and select your P4000 SAN Solution.
7. Click the Tools & Links tab and click Edit System Properties.
8. Scroll down to the Contract and Warranty Information section and enter
entitlement information. Click OK.
9. Next, from HP SIM, you will check entitlement for your P4000 SAN Solution.
Click Options Remote Support Configuration and Services.
10. At the Remote Support Configuration and Services screen, click the Entitlement
tab.
11. At the Entitlement tab, select your P4000 SAN Solution and select Entitle
Checked from the Action List dropdown. Click Run Action.
12. When the entitlement check is complete, make sure the Action Status Message
shows "Finished Entitlement Check" and click Refresh.
Verify Operations
In the steps below, you will verify that the P4000 SAN Solution is communicating
with the CMS.
1. Before verifying, you need to restart the DESTA_Service service.
a. To stop DESTA_Service, click Start All Programs Hewlett Packard
Service Tools Web-Based Enterprise Services and click Stop Director.
b. The command window appears showing that the DESTA_Service service is
stopping.
40 September 2010
c. Now, to restart DESTA_Service, again click Start All Programs Hewlett

Packard Service Tools Web-Based Enterprise Services and click Start
Director.
d. The command window appears showing that the DESTA_Service service is
starting.
2. After restarting the DESTA_Service service, you need to check that the P4000
SAN Solution is listed under the Managed devices.
a. Click Start All Programs Hewlett-Packard Service Tools System
Event Analyzer System Event Analyzer.
Note
If the security certificate warning appears, click Continue to this website.
b. Next, enter the username and click Logon.

c. At the System Event Analyzer page, click the Configure Webes Managed
Entities icon.
d. At the Managed Entities screen, select your P4000 SAN Solution link.
e. At the Managed Entity Properties screen, verify the settings.
3. Next, you will send the test trap to verify the communication between your
P4000 SAN Solution and the CMS.
a. From the CMS, double-click the HP LeftHand Centralized Management
Console icon. The CMC starts.
b. From the CMC, expand the SAN system from the left pane. Enter the
username and password and click Log In.
c. Next, expand your P4000 SAN Solution and select SNMP.
d. Click the SNMP Traps tab. From the SNMP Trap Tasks dropdown, select
Send Test Trap. Click OK.
e. From the left pane, select Configuration Summary to verify that the test event
was posted to the CMS logs.
4. Finally, you need to verify that the SNMP test trap is reflected in the CMS.
5. Open HP SIM and select your P4000 SAN Solution from the All Systems table.
6. Click the Events tab. The SNMP test trap is listed under the Events table.
September 2010 41
Demo 13 Configuring Tape Libraries

Install Command View TL
Perform the following steps to install HP StorageWorks Command View TL:
Note
In this demonstration, we will install the Command View TL software on the CMS.
This software can be installed on any other host as well.
1. From the CMS, click Start My Computer and browse to the location where the
installation file is saved.
2. Double-click the installer file to start the installation of the Command View TL
software and click Run. The installation process begins.
3. At the welcome screen, click Next.
4. At the Customer Information screen, enter your user name and company name
and select one of the installation option and click Next.
5. At the Setup Type screen, select the Setup type as Custom and click Next.
6. At the Select Features screen, clear the SMIS Tape Provider check box.
7. At the Start Copying Files screen, review the settings you have done and click
Next.
8. First, the new files get copied to the disk. The products get installed and
registered. The required services get started.
9. When the installation completes, click Finish.
10. If the security warning appears, select the Always trust content from this
publisher check box and click Run. When asked to block the unsafe
applications, click No.
11. After the installation and setup is complete, HP Command View TL launch
window appears.
Discovering and Configuring VLS on the CMS

1. From the HP SIM home page, click All Systems. From the HP SIM main menu,
click Options Discovery.
2. At the Discovery screen, click New to create a new Discovery task for HP
StorageWorks VLS.
3. From the New Discovery section, select the Discover a single system option,
enter a name for the Discovery task, and enter the system name or IP address.
4. Scroll down and make sure that the read community string is "public". Click OK.
5. Next, click Save to save the settings.
42 September 2010
6. From the table, select your VLS discovery task and click Run Now. Wait for some
time; you can now see that the status is set to Complete.
7. Click the All Systems link in the System and Event Collections area of HP SIM.
You should see your VLS in the table.
In this section, we will now add the entitlement information.
8. From the All Systems list of HP SIM, click the system name of your VLS. Click the
Tool & Links tab, and then click the Edit System Properties link.
9. Enter the entitlement information in the Contract and Warranty Information
section and click OK.
Next, you need to perform entitlement check on your VLS.
10. From the HP SIM main menu, click Options Remote Support Configuration
and Services.
11. At the Remote Support Configuration and Services screen, click the Entitlement
tab.
12. Select your VLS check box. From the Action List dropdown, select Entitle Checked
and click Run Action.
13. Make sure the Action Status Message shows "Finished Entitlement Check" and
then click Refresh to refresh the table.
Note
To discover and configure the HP StorageWorks MSL Tape, you need to follow
the same procedure.
Configure Command View TL

To generate a trap event for HP StorageWorks VLS
1. Launch Command View TL and click Actions Add Library.
2. Next, enter the IP address or host name of your VLS and click OK.
3. Your VLS IP address gets listed under the Library table.
4. Right-click your VLS IP address and select Manage Library.
Note
If the security certificate error appears, click Continue to this website.
5. The Command View VLS web interface opens. Enter the username and
password and click Login.
6. To generate an SNMP trap, click the Notifications tab and click Edit SNMP
Settings.
7. At the Edit SNMP Settings tab, enter your CMS hostname or IP address.
September 2010 43
8. Enter the Community String as Public, ensure that the trap version is 1, and click
Add.
9. For the entry you have just added in the table, click Test Snmp. The status shows
that the SNMP test trap sent successfully.
To generate a trap event for a HP StorageWorks MSL
1. Launch Command View TL and add your MSL to it.
2. Right-click your MSL IP address and select Manage Library.
3. The Command View MSL web interface opens. Log into the Command View
MSL web interface as Administrator.
4. Click the Configurations tab and click the Network Management tab.
5. At the Network Management tab, verify that SNMP is selected.
6. Enter the IP address of the CMS into the IPv4 target address field. Verify that
version SNMPv1 is selected.
7. Select Critical and Warnings as the filter level and click Submit.
Verify Operation
You need to verify that the SNMP test trap is reflected in the CMS.
Note
The verification operation provided in this demonstration only applies to VLS and
not to ESL, MSL, or EML.
1. Next, go to HP SIM and click your VLS link from the All Systems table.
2. Click the Events tab. You can see the SNMP test trap listed here.
44 September 2010
Demo 14 Installation Advisor

Verifying Event Protocols
Using LaunchWHC to verify that event protocols are configured properly
1. First, check the version of WEBES is higher than version 5.6 patch 1. For this,
click Start Control Panel Add or Remove Programs.
2. Click HP WEBES and verify that the version is higher than 5.6 patch 1.
Note
When you install HP SIM 6.0, the default version 6.1 of WEBES gets installed.
3. Next, open a command window. For every device you are monitoring, execute
the desta.bat LaunchWHC <hostname> command.
This command will generate output about the connection protocols used to
communicate with the device and their states. Ignore any output related to MC3
providers.
The first section of the output shows the listing of device protocols used. You need to
scan the output to verify that no problems were reported for any of the protocols
used. In this simulation, it indicates that no problems were found with the SNMP
Protocol.
When warnings or errors are reported for protocols that are in use:
If a failure with a particular protocol is reported, determine if the protocol is
really appropriate for the device.
If the protocol is appropriate for the device, use the remote support
documentation to troubleshoot and repair the protocol. The Installation Advisor
contains utilities to help configure and set up protocols on monitored HP-UX
devices.
If the protocol is not appropriate for the device, you can remove the protocol
using the Remote Support Standard and Advanced user interfaces.
After repairing or removing the protocol for the device, you can re-run Desta.bat
LaunchWHC hostname to verify that no more problems are reported.
September 2010 45
Collect logs for support

HP Insight Remote Support software comprises of many different software
components, each with many different log files. This can make it challenging to get
all the relevant log files to HP Support. The following steps will help you in gathering
appropriate log files:
1. Browse to the C:\Program Files\HP\Installers\InstallationAdvisor folder. This is
the location where your collectRsLogs.bat file is placed.
2. Double-click the collectRsLogs.bat file to execute it.
3. A command window appears displaying the execution of the batch file.
Note
Ignore any output about services not running. These are not relevant to the log
file collection.
4. When the execution is complete, press any key to continue. This closes the
command prompt window.
5. This will create a zip file in the C:\temp\Tools_Check folder. This folder will be
created if it does not exist.
6. To view the logs generated, browse to the C:\temp\Tools_Check folder.
7. Here, you can view all the log zip files generated till date. The latest zip file can
be attached to a support case and should provide HP Support with all the
supporting data they need to troubleshoot your case.
46 September 2010
Demo 15 Collections
Configuring and running data collection for HP-UX servers
Note
A valid contract level of Proactive Services or higher is required for HP-UX
server collections.
First, we will transfer the HP-UX ACC package from the CMS to the HP-UX server.
1. From a DOS command window of the CMS, change to the
c:\ProgramFiles\HP\Installers\UC\ACC\HPUX directory.
2. Use ftp to connect to your HP-UX server from the CMS DOS command window
and login as root.
3. Create a directory on the HPUX server in the /tmp directory called hpuxCfg.
4. Change to the newly created /tmp/hpuxCfg directory on the HP-UX server.
5. Make sure you are in binary mode for ftp.
6. ftp the most current version of the rs-acc-hpux-11.X-IAA.05.xx.xx.xxx.depot.gz
file to your HP-UX Server (where xx is the current version number available).
7. Exit ftp.
Installing ACC on the HP-UX Server

1. From your HPUX Server telnet session, change to the /tmp/hpuxCfg directory.
2. Unzip the depot using the gunzip command.
3. On your HP-UX Server, install the files from the depot using the swinstall
command.
Setting up trust relationship between the CMS and HP-UX Server

In the following steps, you will open an ftp session from your CMS to the HP-UX
server and copy the certificate from your HP-UX server to your CMS. Then you will
install your HP-UX Servers certificate to the CMS.
1. From a DOS window on your CMS create a directory with the following
command.
mkdir c:\temp\certs
2. Change to the created directory.

cd c:\temp\certs
3. ftp to your HP-UX Server, and login as root.

4. Change to the /opt/hpsmh/sslshare directory.
cd /opt/hpsmh/sslshare
September 2010 47
5. Set ftp to binary transfer:

bin
6. Get the cert.pem file from your HP-UX Server and copy it your CMS.
get cert.pem <Your HP-UX Servers system name>_cert.pem
For example, if your HP-UX Servers system name is HPUX-01, at the ftp prompt
you would input: get cert.pem HPUX-01_cert.pem
7. Quit ftp.
bye
8. Close your CMS DOS window. From the Main Menu of HP SIM, select Options
Security Credentials Trusted Systems.
9. Click the Trusted Certificates tab.
10. Make sure the Always Accept option of the Trusted System Certificates screen is
selected and then click Import.
11. Click Browse to find the certificate in the c:\temp\certs\ directory. Highlight the
certificate file on the Choose File screen, and then press Open.
12. The certificate should now appear in the Certificate filename field.
13. Click OK in the Trusted Certificates screen.
14. The Trusted Certificates screen will appear with the certificate information
appearing as a line in the table.
15. From the HP SIM main menu, select Options Identify Systems.
16. Click Run Now in the Step1: Verify Target Systems screen.
17. When the task status reports Completed, look through the StdOut section and
verify that SMH trust status is true by scrolling down the StdOut detail.
Note
If the SMH trust status is false, open the HP-UX Servers SMH page from HP SIM,
close it, and then run the Identify Systems again for the HP-UX server. The SMH
trust status should now be true.
48 September 2010
We will now run a server advanced configuration collection and verify if it has run
correctly.
Note
Please note that before you can run the Server Advanced Configuration
Collection task, you should go to Remote Support Configuraion & Services
Server Services Server Advanced Configuration. Select the HP-UX server and
save all changes.
1. Within HP SIM, select Task & Logs View All Scheduled Tasks.
2. In the list of available tasks, select Server Advanced Configuration Collection
task, and click Run Now.
3. The Task Results Status will eventually report Complete when the collection has
finished running. This task takes approximately 9-12 minutes to run.
Now, we will verify if the collection was successful.
and Services, and click the Server Services tab.
5. Highlight the row associated with your HP-UX server and move your mouse over
the green circle with white check mark in the CC column. You should see hover
text indicating the collection was successful.
6. Click the green circle with white check mark in the CC column to display
collection information. A small window will appear, providing you access to the
collected information.
7. Click the provided link, and then click Open to unzip the file. A number of files
are displayed.
8. Click the HPUX_FSC_File_System_Configuration file, click Open on the File
Download window, click Yes on the Security Alert window, and then click Yes on
the Security Warning window. At this point, we have verified the collection was
successful and has made it to the CMS.
We will now run a server availability collection and also verify if it has run correctly.
9. In HP SIM, select Task & Logs View All Scheduled Tasks.
10. In the list of available tasks, select Server Availability Collection task, and click
Run Now. The Task Results Status will eventually report "complete" when the
collection has finished running.
and Services, and click the Server Services tab.
12. Highlight the row associated with your HP-UX server, and move your mouse over
the green circle with white check mark in the AC column. You should see hover
text indicating that the collection was successful.
September 2010 49
13. Click the green circle with white check mark in the AC column to display
collected information. Click the provided link and then click Open to unzip the
file.
14. A number of files are displayed. Click the index file, click Open on the File
the Security Warning window.
15. It would open a new Internet Explorer window. At this point, we have verified
the Server Availability Collection was successful and has made it to the CMS.
We will now run a server performance collection and also verify if it has run
correctly.
16. By default, the Server Performance Collection is set to monitor a system for eight
hours and report performance statistics for that monitored period. For this
exercise, we will set the run time to 12 minutes and you will able to enter your
email address.
17. From HP SIM, click your HP-UX Server in the All Systems table to display the
System tab screen. Click the System Management Homepage.
18. Click the HP Proactive Analysis Client link under Integrated Agents on the top
left-hand side of the SMH home page.
19. A new window pops up titled Proactive Analysis Client. Locate Analysis PAC in
the left-hand pane and click Set dynamic interval.
20. Set Dynamic Duration to 0 hours and 12 minutes. Click Save and close SMH.
21. Now, to run the collection, select Task & Logs View All Scheduled Tasks.
22. Select Server Performance Collection from the list of tasks, and click Run Now.
Important
! Please ensure that the collection interval is changed back to 8 hours after this
exercise.

and Services, and click Server Services.
24. Highlight the row associated with your HP-UX server, and move your mouse over
the green circle with white check mark in the PC column. You should see hover
text indicating that the collection was successful.
25. Click the green circle with white check mark in the AC column to display
collected information. Click the provided link, and then click Open to unzip the
file.
50 September 2010
26. A number of files are displayed. Click the index file. Click Open on the File
the Security Warning window.
27. It would open a new Internet Explorer window. At this point, we have verified
that the Server Performance Collection was successful and has made it to the
CMS.
September 2010 51
Configuring and running data collection for EVAs

Before running the collection, we will provide authentication details for storage
devices so that the Remote Support Configuration Collector (RSCC) application will
be able to authenticate to each device when requesting a configuration collection.
1. From the main menu of the CMSs HP SIM, select Options Remote Support
Configuration and Services Storage Services.
2. In the Storage Services tab, you can provide authentication details for individual
devices or groups of devices. For the purposes of this exercise, you will provide
authentication details for individual devices.
3. In the lower half of the screen, make sure the check box for the EVA is selected.
From the Connection pull-down menu, select Element Manager Server. In the
User/Read field, enter the Command View user name. In the Pass/Write field,
enter the Command View password. When you move the cursor from the
Pass/Write field and you will be prompted to re-enter the password.
4. Click Test to verify that the CMS can communicate with Command View. The
status message will indicate the result. Click Save All Changes.
5. Now, to run the collection, select Tasks & Logs View All Scheduled Tasks.
Scroll down and select Storage Configuration Collection. Next, click Run Now.
6. Verify successful completion of the task under the Task Results section and close
HP SIM.
Now, we will verify if the Storage configuration collection is operational.
and Services, and click the Storage Services tab.
2. Highlight the row associated with your EVA and move your mouse over the
green circle with white check mark in the CC column. You should see hover text
indicating that the collection was successful.
are displayed.
5. Click the index.xml file, click Open on the File Download window, click Yes on
the Security Alert window, and then click Yes on the Security Warning window.
At this point, we have verified the collection was successful and has made it to
the CMS.
52 September 2010
Configuring and running data collection for SANs

Unlike the Storage Collection, the devices that make up the SAN are not
automatically populated under the SAN Configuration Collection upon successful
Entitlement. In this simulation, you will be creating a custom SAN configuration
collection.
Creating a Custom SAN Configuration Collection

1. Click the Customize link under the System and Event Collections panel.
2. On the Customize Collections screen, expand the Remote Support Services
RSP SAN. Select the SAN Configuration Collection option, and click New.
3. Under the New Collection section, select the Choose members individually
option, and select All Systems from the pull-down menu.
4. Move the SAN devices from the Available Items list to the Selected Members list.
Use the Ctrl key to select each device, and click the double arrow to move from
one list to the other. Click Save As Collection. Note that the fiber switch should
be discovered and entitled in HP SIM before creating a custom collection.
5. In the Save As Collection section, enter a name for the collection in the
Collection Name field, select the Existing collection option, scroll down, select
SAN Configuration Collection, and click OK. Click OK again on the information
window.
6. Once a SAN collection has been created, you must provide authentication
details for the devices in the collection so that the Remote Support Configuration
Collector application will be able to access each device when configuration
data is being collected.
Now, you will be Configuring Authentication Details for the Collection Devices.
and Services SAN Services.
2. Select the SAN collection that you had created earlier from the RSP SAN
Collection pull-down menu.
3. For the Command View Server, make sure the connection type is "WinHost" and
then key in the command view EVA credentials. Verify successful communication
by clicking Test.
4. For the SAN switch, select the connection type and enter the credentials. Verify
successful communication by clicking Test.
5. Click Save All Changes to save the changes.
Now, we will run a SAN Configuration Collection.
1. In HP SIM, select Tasks & Logs View All Scheduled Tasks, and select SAN
Configuration Collection from the list of tasks, and click Run Now.
2. Verify successful completion of the task under the Task Results section.
September 2010 53
Now we will verify if the SAN configuration collection is operational.

and Services, and click the SAN Services tab.
2. Highlight the row associated with your EVA and move your mouse over the
green circle with white check mark in the CC column. You should see hover text
indicating that the collection was successful.
are displayed.
5. Click the index.xml file, click Open on the File Download window, click Yes on
the Security Alert window, and then click Yes on the Security Warning window.
6. At this point, we have verified that the collection was successful for the EVA.
Similarly we can verify if the collection was successful by clicking on the green
circle with white tick for the other devices in the SAN.
54 September 2010
Configuring and Running P4000 SAN Solutions Collection

From HP SIM, you need to add the P4000 SAN Solution collection credentials to
Remote Support.
1. Click Storage Services P4000 Family Configuration Collections.
2. At the P4000 Family Configuration Collections tab, click New Credential Group.
3. Enter the description, username, and password. When the text "confirm
password" appears in the password field, enter the password again.
4. Select a Credential group and click Save All Changes.
5. When the RSCC Update complete dialog box appears, click OK.
6. To add each device to the daily collection schedule, click Tasks & Logs and
select View All Scheduled Tasks.
7. From the table, select your P4000 SAN Solution task and click Edit.
8. At the Step 1: Select Target Systems screen, select P4000 Family Configuration
Collection from the dropdown and click Apply Schedule.
9. From the Step 2: Schedule Task screen, refine the schedule and click Done.
10. At the All Scheduled Tasks screen, click Run Now.
11. To run the configuration collection, select Options Status Polling HP Service
P4000 Family Configuration Collection.
12. At the Step 1: Select Target Systems screen, select P4000 Family Configuration
Collection from the dropdown, click Apply, and then click Run Now.
13. The configuration collection runs and shows the status as Complete.
Next, you need to verify if the P4000 SAN Solution Collection was successful.
1. Click Options Remote Support Configuration and Services.
2. Click Storage Services P4000 Family Configuration Collections.
3. Click the check mark to view the collection data. In the new window that opens,
click the link in the popup to download the file.
4. In the file download window click Open. In the new window that displays, click
the index.xml file.
5. Again, click Open to open the file.
6. In the Internet Explorer window, right-click the yellow security bar and click
Allow Blocked Content to view the contents. On the security warning dialog box,
click Yes.
This verifies that the P4000 SAN Solution Collection is operational.
September 2010 55
Configuring and Running Server Basic Configuration Collection

Configuring the server basic configuration collection
1. Log in to HP SIM and click Options Remote Support Configuration and
Services Server Services Basic Collections.
2. Select the check box for the managed device on which you want to run the
collection and click Save All Changes. When the update is complete, click OK.
Running the Server Basic Configuration Collection

1. Click Tasks & Logs View All Scheduled Tasks.
2. Select the Server Basic Configuration Collection option and click Run Now.
Once the task finishes, the status would change to Complete.
Verify if the Server Basic Configuration Collection was successful.

1. Click Options Remote Support Configuration and Services.
2. Click the Server Services Basic Collections.
3. Move your mouse pointer to the check mark in the CC column, you should see
hover text indicating that the collection was successful.
4. Click the check mark to view the collection data. In the new window that opens,
click the provided link to open the file. Next, click the link in the popup to
download the file.
5. In the file download window click Open. In the new window that displays, click
the xml file starting with IBI_SNMP.
6. Again, click Open to open the file.
7. In the Internet Explorer window, right-click the yellow security bar and click
Allow Blocked Content to view the contents. On the security warning dialog box,
click Yes.
This verifies that the server basic configuration collection is operational.
56 September 2010
Verify Collections with the Installation Advisor

Using InsightRsDataCollectionCheck to verify and/or trigger data collections
1. To test that monitored systems can run data collections, browse to the
C:\Program Files\HP\Installers\InstallationAdvisor folder.
2. Double-click the InsightRsDataCollectionCheck.exe file to execute it. This will
bring up the following user interface that lists all devices configured to send
collections.
3. When the application opens it verifies the results of previously run collections.
The date that the collections were run is displayed in the Collection Time
column. You can select all the managed devices listed or a specific managed
device.
4. At the HP Remote Support Collection Verification screen, select your managed
device.
5. Click Run Collection and Verify Results of Selected Devices to run a new
collection on every selected device and analyze the results.
6. Click Yes to proceed.
Note
If a collection on a device takes more than five minutes to run (which is typical of
many mission-critical Remote Support Advanced collections), the utility will
indicate that the collection took too long and move on to the next device. The
collection will continue to run in the background.
7. After the collection completes, click Refresh. This will display the results and the
time at which the collection is completed.
Any collection that came back empty, was timed out, or was not able to be run will
be highlighted in red. The specific problem will be listed in the collection_error
column.
September 2010 57
Resources
Technical Documentation
Remote Support Information Library, available at:
http://www.hp.com/go/insightremoteadvanced-docs (Select the Remote
Support link) provides:
HP Insight Remote Support Advanced CMS Configuration and Usage Guide
HP Insight Remote Support Advanced CMS Prerequisites and Managed
Systems Configuration Guide
HP Insight Remote Support Advanced Important Information: Implementing
Remote Support for EVAs
HP Insight Remote Support Advanced CMS Registration, Configuration, and
Usage Guide
HP Insight Remote Support Advanced Release Notes
HP Insight Remote Support Advanced: Software Manager Troubleshooting
Guide
HP Insight Remote Support Advanced Security
The HP SIM Information Library, available at:
http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrar
y.html provides:
Product literature
Success stories
HP Enterprise library
HP SIM Videos
Reference documentation for installing and configuring HP SIM, using HP
SIM, migrating to HP SIM, and integrating HP SIM with other products
Advanced management features and Man pages
Archives
Analysis Tools link http://h18023.www1.hp.com/support/svctools
Software Information
HP Software Depot:
http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?product
Number=RSADVANCED
PSP (ProLiant Support Pack) home page: http://www.hp.com/servers/psp
58 September 2010
General Information
HP Insight Management WBEM Providers documentation and downloads
http://h18013.www1.hp.com/products/servers/management/wbem/document
ation.html?jumpid=reg_R1002_USEN
In case of installation issues, go to Insight RS Technical Support at
http://www.hp.com/go/rstechsupport and use the support contact information.
Installation Queries
For any queries related to installation, refer to Insight RS Technical Support link.
September 2010 59

Insight RSA Demo Update

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Insight RSA Demo Update

Caricato da

Copyright:

Formati disponibili

Insight RSA 5.

The demos are presented as follows:

Demo 1 CMS Installation Options

Verifying hardware and software requirements

Creating an administrator account

Setting up Advanced Proxy Settings

3. Also, ensure that Internet Explorer Enhanced Security Configuration is not

Installing the .NET Framework

Verifying SNMP settings

Installing ProLiant Support Pack (PSP)

Demo 2 Installing and configuring HP Systems

Configuring HP SIM using the First Time Wizard

Creating and running an HP SIM task Applying System

Configuring system links within HP SIM

Demo 3 Installing and configuring HP Systems

Manually edit several of the CMS' system properties

Discover and configure the ESX server in HP SIM

10. Enter Serial Number for the system.

Demo 4 Installing and Configuring Insight RSA

1. Click Start All Programs Hewlett-Packard Remote Support Software

Initialize Remote Support Software Manager steps. Select the appropriate

Demo 5 Registering the Remote Support client

Demo 6 Configuring CMS entitlement

Demo 7 Configuring Service Providers

1. To add a Service Provider, click Options Remote Support Configuration and

Demo 8 Configuring HP-UX Servers

Installation Advisor software

ftp Installation Advisor Files from CMS to HP-UX server

4. Change to the newly created /tmp/installationAdvisor directory on the HP-UX

5. ftp the InsightRsHpuxPrereqCheckv24.sh and InsightRsHpuxSetup.sh files to your

Run Installation Advisor Scripts on your HP-UX Server

3. Now we have to make the files executable.

4. Run the InsightRsHpuxPrereqCheckv24.sh script.

Discovering managed HP-UX devices and configuring entitlement

Verifying Insight RSA Management of a HP-UX Server is

Demo 9 Configuring Linux Servers

Installing PSP on the Linux Server

Discovering Linux servers and configuring Insight RSA

Configuring the snmpd.conf file

3. Also, comment out the existing view statements.

Verifying Insight RSA monitoring of a Linux Server is operational

Demo 10 Configuring Storage Management

Discovering and configuring managed Windows-based Storage

Configure Command View credentials in WEBES SEA

Verifying Insight RSA monitoring of a Windows-based Storage

Demo 11 Configuring Windows Servers

8. Open System Management Homepage from the icon on the desktop.

Discovering a managed Windows Server and configuring its

Configuring Entitlement details for the Managed Windows Server

Verifying remote monitoring of a Windows Server is operational

Demo 12 Configuring P4000 SAN Solutions

Centralized Management Console (CMC) requirements

HP StorageWorks P4000 SAN Solution requirements

SNMP Configuration: SNMP must be enabled on the CMS to communicate with

Install and Configure CMC

2. Click Agree to accept the END USER LICENSE AGREEMENT.

Configuring the P4000 SAN Solution

Configuring the P4000 SAN Solution Communications

3. Next, from the left pane, select Alerts.

Discovering and Configuring P4000

c. Now, to restart DESTA_Service, again click Start All Programs Hewlett

b. Next, enter the username and click Logon.

Demo 13 Configuring Tape Libraries

Discovering and Configuring VLS on the CMS