Systems Insight Manager 7.
© Copyright 2010, 2012 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents I Introduction...............................................................................................12 1 About this document.............................................................................13 User Guide.......................................................................................................................13 HP SIM User Guide layout..................................................................................................13 2 Product overview..............
Discovery of Gen8 servers..................................................................................................40 7 Manage Communications......................................................................41 Configuring the managed system software using the Configure or Repair Agents feature from the CMS................................................................................................................................41 Sending test traps and indications...........................
Editing Enhanced reports...........................................................................................66 E-mailing reports......................................................................................................66 Deleting reports........................................................................................................66 15 HP SIM tools.......................................................................................68 Target selection...........................
Dependencies...............................................................................................................97 Warning......................................................................................................................97 Changing the database associated with the CMS..............................................................97 20 Understanding HP SIM security.............................................................98 Securing communication.............................
Strong security............................................................................................................106 Configuring managed systems......................................................................................106 How to: lockdown versus ease of use on Windows systems....................................................107 Moderate...................................................................................................................107 Strong.........................
About storage security using SNMP....................................................................................130 Discovery and identification..........................................................................................130 Prerequisites for managing storage systems.........................................................................131 Using storage solutions.....................................................................................................
mxmib.......................................................................................................................148 mxmib MIB keyword customization...........................................................................149 SNMP Trap Settings page............................................................................................152 A Important Notes.....................................................................................154 System and object names must be unique..........
Ports used by HP SIM............................................................................................................177 Privilege elevation.................................................................................................................178 Property pages.....................................................................................................................178 Reporting....................................................................................................
Check Event Configuration.....................................................................................................195 Status polling.......................................................................................................................195 F Host file extensions.................................................................................196 Default values......................................................................................................................
Part I Introduction
1 About this document User Guide HP Systems Insight Manager provides this user guide to help you understand management features. HP SIM User Guide layout • Introduction Describes the features, basic concepts, and using the graphical user interface (GUI) in HP SIM. • Setting up HP SIM Describes how to set up HP SIM by explaining requirements for systems to be managed by HP SIM, credentials, discovery, automatic event handling, and users and authorizations.
2 Product overview HP SIM features • Automatic discovery Automatically discovers and identifies systems attached to the network. Use discovery filters to prevent discovery of unwanted system types. • Health monitoring Colored status icons enable you to see at a glance the operational health of your systems, and quickly drill down to find the failing component if any are not ok. • Fault management and event handling HP SIM provides proactive notification of actual or impending component failure alerts.
NOTE: HP SIM uses several management protocols to communicate to managed systems. The protocols used, include WBEM/WMI, SNMP, HTTP/HTTPS, SSH and WS-MAN. All of these protocols can be configured to access data from non-root/non-administrator users. For Linux systems, one of the protocols used during discovery, is SSH. During discovery, HP SIM executes the command, /usr/sbin/dmidecode, on the remote Linux system to fetch certain information.
Tools and tasks Tools are actions you perform on the managed systems from within HP SIM's GUI or CLI. Many tools ship with HP SIM, but you can also add your own custom tools. Tasks are instances of running tools. To create a task, select target systems (systems or events that the task will work on) and then select the tool from the HP SIM menu. Tasks can be run immediately or scheduled, and you can view task results by selecting Tasks & Logs→View Task Results .
To download, go to http://www.hp.com/go/firefox. • For Linux: Firefox 3.0.10 or later NOTE: Browser settings: • For all Windows Internet Explorer browsers, you must have the SSL 3.0 or Transport Layer Security (TLS) 1.0 browser security options enabled for HP SIM to work properly, which allows only stronger ciphers for the SSL connection. • To use automatic sign-in with Firefox, you must configure Firefox with a list of sites with automatic sign-in.
IMPORTANT: Automatic sign-in fails if the SPN registered more than once. If you change the name of the HP SIM service account, you must first delete the SPN associated with the old service account name, and then register the new service account name: setspn -d HTTP/ setspn -a HTTP/ NOTE: Local accounts cannot be used for HP SIM service account if automatic sign-in is desired.
Failures encountered during automatic sign-in are logged as normal sign-in failures in both the audit log and the event log. If automatic sign-in is not attempted, no failure is detected or logged by HP SIM. If automatic sign-in is configured, you can manually sign in to HP SIM. • If automatic sign-in fails, the manual sign-in page appears This might occur if you are logged in to the operating system using an account that is not an HP SIM account.
To speed the search process, as you enter system information in the search box, a dropdown list appears listing systems that begin with the text you are entering. You can select from the dropdown list or continue to enter the information. If you do not need to view this panel at all times, you can collapse it by clicking the minus sign ( ) in the top right corner of the panel. To expand the panel, click the plus sign ( ). 4.
Part II Setting up HP SIM
3 Setting up managed systems Setting up managed systems involves installing the required Management Agents software and configuring the supported protocols to communicate with the HP SIM software. Configure or Repair Agents Managed systems must be able to communicate status to the HP Systems Insight Manager CMS in order to launch commands to the managed systems. To configure the managed systems to communicate with the CMS, you must configure common configurations and trust relationships.
3. 4. 5. 6. 7. Select Install Linux PSP or ESX Agents to install Linux PSP and ESX Agents which are a collection of SNMP agents used by HP SIM to gather information from managed systems and send traps to HP SIM. Select Install WBEM / WMI Provider (HP Insight Management WBEM Provider) for Windows to install WBEM or WMI providers on Windows managed systems. Select Install SNMP Agent (Insight Management Advisor) for Windows to install the SNMP agent on Windows managed systems.
◦ Send a sample WBEM / WMI indication to this instance of HP SIM to test that events appear in HP SIM in the Event List or All Event User Interface for the selected system NOTE: SIM. This indication will appear as an Informational Event in the Event List of HP NOTE: This indication is supported only on HP-UX and Windows targets with WBEM provider installed.
NOTE: If you configure only HP-UX systems with default SNMP installations, you do not need to set this option. HP-UX enables read by default (get-community-name is set to public by default on HP-UX systems). NOTE: If you select this option, the Read Only community string is added to the target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the managed systems do not always enable SNMP communication between themselves and a remote host.
NOTE: For this option to work, the user name and password provided in Step 4: Enter credentials must be an administrative level account. For Linux or HP-UX targets, it must be the root account and password. ◦ Each user has to be authenticated on the managed system NOTE: If you do not want all users that have sign-in access to HP SIM to run the tool and you would like to control which users need to have access, this option is more secure.
NOTE: Do not set this option if you have Insight Management Agents 7.2 or later installed. NOTE: If the remote system is running HP-UX, this option is not executed on the remote system because it is not applicable on HP-UX systems. If you are configuring only HP-UX target systems, you do not need to set this option. If you select this option, you must complete the following steps: a. In the Password field, enter the new administrator password. b.
14. Click Run Now or click Schedule to run this task at a later time. The Task Results page appears. If the Management HTTP Server is installed on target systems, the login credentials are updated in the Management HTTP Server password file. As with other HP SIM tools, you can configure the Configure or Repair Agents tool to run on a schedule or manually. Only one instance of Configure or Repair Agents tool can run at a time. The Configure or Repair Agents tool can update multiple target systems.
Setting up HP-UX servers to be managed by HP SIM Procedure 3 Setting up HP-UX managed systems 1. Understand the basic managed system software for HP-UX. For HP-UX, the following software, shown with minimum recommended versions, is required for essential HP SIM functionality to operate. This software is installed by default as part of the latest HP-UX 11i v2 and 11i V3 operating environments, but it might need to be installed or updated on HP-UX 11i v1 or older HP-UX 11i v2 environments.
Manually setting up an HP-UX managed system Although chapters 4-7 explain how to finish configuring managed systems from the HP SIM GUI, this section describes how to perform some of these same steps from the command line for HP-UX systems. You do need to first supply credentials and discover the systems, as described in Chapter 4 “Credentials” (page 34) and Chapter 6 “Discovery” (page 37). Then you can do the following actions from the command line, if desired.
2. Verify that SysFaultMgmt provider is installed. Depending on the System Fault Manager configuration, run the following: cimprovider –lm SFMProviderModule The EMSWrapperProvider appears. or cimprovider –ls The EMSWrapperProvider appears. NOTE: For more information regarding System Fault Manager, see HP System Fault Management Diagnostics. 3. From the CMS: To subscribe to WBEM Events, you must have root access.
Installing and configuring SSH Procedure 5 Installing and configuring SSH on a Linux system 1. Verify that SSH is installed on the managed system: rpm -qa | grep ssh If SSH is not installed, see your Linux provider for information about installing SSH. 2. On the CMS, copy the SSH-generated public key from the CMS to the managed system, and place it in the authorized keys file of the execute-as user (root or administrator).
6. If the HP Server Management Drivers and Agents daemons are installed on your system, start them: /etc/init.
4 Credentials In HP SIM, credentials are used to enable the CMS to communicate with managed systems, through WBEM, WS-MAN, SSH, and SNMP. However, the Sign-in credential is used unless you configure the other protocols. The Sign-in credential is protocol independent and can be tied to systems through the discovery credential. In HP SIM, there are three different types of credentials: • System credentials Credentials used by identification to access managed systems.
15.3.110.117 15.3.105.51 15.3.110.
5 WMI Mapper Proxy Windows systems use a variation on the WBEM management protocol called WMI. For HP SIM to communicate with Windows systems, the WBEM protocol it uses must be converted to the WMI protocol and vice versa. This is the function of the WMI Mapper Proxy. This proxy is typically installed on the same system as HP SIM when HP SIM is installed on a Windows system.
6 Discovery Discovery is the process of finding systems in the management domain so that they can be managed from the CMS by HP SIM. HP SIM can automatically discover and identify systems attached to the network using information from management protocols such as SNMP, WMI, WBEM, SSH, and SSL. Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs. Use discovery filters to prevent discovery of unwanted system types.
4. Physical Servers This discovery task is for discovery of physical servers (blade servers and standalone servers). The management processors for these servers must be discovered prior to this discovery task being run. 5. Virtual Machines This discovery task is for discovery of virtual machines associated with servers discovered in the previous category. NOTE: If discovery tasks are run out of order, errors are likely.
• Enable or disable a discovery task Select a task and click Disable to disable the schedule of an enabled task. If a task is disabled, the button changes to Enable. To resume automatic execution of the task, click Enable. • Delete an existing discovery task Select a task from the table and click Delete. • View Task Results This button displays the task results for the current discovery task. • Run a discovery task Select the task you want to run and click Run Now.
matches the current filter. If discovery filters are disabled, automatic discovery discovers systems according to the General Settings for All Discoveries section on the Discovery page. If you do not discover the HP systems that you expect to find, ensure that the Insight Management Agent are installed and running correctly on the target systems.
7 Manage Communications Use the Manage Communications feature to troubleshoot communication problems between the CMS and targeted systems. For each failed communication function, troubleshooting information is available. You can reconfigure communication settings, launch agents, and push certificates to target systems.
Sending test traps and indications To verify that SNMP traps and WBEM indications can be sent, send test traps and indications. You can send test traps and indications from Configure or Repair Agents on Windows and HP-UX systems, with the WBEM provider installed, from the Step 4: Configure or Repair Agents page, under Configure WBEM / WMI..
8 Automatic event handling Automatic event handling enables you to define an action that HP SIM performs when an event is received. Users who want to access this feature must have administrative rights. NOTE: • Automatic Event Handling events older than 24 hours are filtered out from AEH tasks. Managing Tasks Enables you to view definitions, copy tasks, edit tasks, view task results, disable or enable tasks, or delete existing Automatic Event Handling tasks.
Example automatic event handling tasks HP SIM ships with three example automatic event handling tasks that are disabled by default. When the Automatic Event Handling - Manage Tasks page appears, you can select one of the example tasks and click View Definition. • example - all desktop information events This task is triggered when an informational event is received from the discovered desktop systems, and this task clears the event. The same task can be edited to change the action of the system criteria .
9 Users and Authorizations HP SIM enables you to configure authorizations for specific users or user groups. Authorizations give the user access to view and manage systems. Each authorization specifies a user or user group, a toolbox, and a system or system group. The specific set of tools that can be run on a system is specified in the assigned toolbox. You must plan which systems each user will manage and which specific set of tools each user is authorized to execute on managed systems.
10 Managed environment The Managed Environment feature enables you to select the operating systems that you will manage. There are four options: Windows, Linux, HP-UX, and Other. The selections made here configure HP SIM to hide collections, tools, and reports for operating systems you do not manage. NOTE: These settings can be changed at any time, and the hidden collections, tools, and reports can be made visible again.
Part III HP SIM basic features
11 Basic and advanced searches Basic search The Search feature enables you to quickly retrieve details about a system using its name or common system attributes. For example, you could search for a system name, IP address, or a word such as server, HP-UX, or storage. The search field only allows the following characters: letters, numbers, tilde (~), dash (-), period (.), underscore (_), apostrophe ('), and space.
View When you click View, the results of the search appear below the search frame. This functionality enables you to preview the results of the search before saving it, or to run a search without saving it. Searching for tools The Tool Search feature provides a quick way to search and filter textually, based on tool names, tool locations in the HP SIM cascading menu structure, and tool descriptions. For additional information, see the HP SIM online help.
12 Monitoring systems Viewing system collections In HP SIM monitoring systems involves HP SIM polling Insight Management Advisor or firmware on the managed systems to retrieve status information, and then displays this information as status icons. There are several types of status that can be displayed, such as Health Status (HW), Software Versioning Status (SW), or Management Processor status (MP). Other status icons might be added by plug-ins to HP SIM.
• Property pages The Property page Status tab displays WBEM properties that help determine the status of the target system, such as determining memory status and process status. Computer system status is determined by information collected live through the WBEM protocol and the information provided by the WMI provider. You can access Property pages in the following ways: • ◦ From the System Page on the System tab, click Properties. The Property pages appear for the target system.
Table 3 Health status types (continued) Status icon Status type Description Warning The system has a potential problem or is in a state that might become a problem. Normal The system is operating normally. The system is accessible. Disabled The system is suspended, which enables a system to be excluded from status polling, identification, data collection, and automatic event handling.
WBEM operational status types HP SIM reports WBEM operational status for storage and server elements, such as storage switch ports and filled memory slots. These status icons appear on the Property pages, System Page, and in the status details that appear when you mouseover the health status column on the System Page.
shared cluster collections from the cluster collection view. Users can manage their own private collections, as well as: • Save collections Click Save As Collection from the cluster table view page. • Delete clusters Click Delete from the cluster table view page. A confirmation box appears. To delete the cluster, click OK, or to cancel the deletion, click Cancel. NOTE: Clusters that contain cluster members cannot be deleted.
After setting the Ignore status on the components, the change will not be reflected until after the next status polling task runs. Example of setting system properties Setting customer company and contact information individually If the customer company or contact information is different between multiple systems, the preferred configuration method is through the Set System Properties or Edit System Properties page using the procedures outlined below.
13 Event management Events are typically sent to the CMS from agents running on the managed systems. However, some events are generated directly from the CMS itself. Managed systems must be configured to send events to the CMS. After the CMS receives the event, if it passes the filters, any actions configured to happen upon its receipt are run, and the event is stored in the HP SIM database for later viewing.
• Status Change Event Settings Enables you to control if a status change event is generated when health status changes. To access, select Options→Events→Status Change Event Settings. • Subscribing to WBEM Events Enables you to subscribe to WBEM events. Select Options→Events→Subscribe to WBEM Events. • Unsubscribing to WBEM Events Enables you to unsubscribe to WBEM events. Select Options→Events→Unsubscribe to WBEM Events.
13. Select Send e-mail. a. In the To address field, enter the e-mail address to which you want the notification sent (multiple addresses can be added so that a group is notified). A CC address can also be added so that a manager or supervisor is also notified. b. In the Subject field, enter your subject. For example, HP Systems Insight Manager Events. c. In the Message Format section, change the option to Pager/SMS.
User Action: Replace the storage system side panel. Status: sidePanelRemoved Example of a Pager/SMS page From: Doe, John Sent: Wednesday, April 28, 2004 5:04 PM To: Doe, Jane Cc: Smith, Jim; Jones, Beth Subject: System A: Storage System side panel is removed (Ver. 3): Pager SMS Format E-mail testing System A, Storage System side panel is removed (Ver.
Where quanit1 is the system name. Example - Creating a task to send an e-mail when a system reaches a critical state The following instructions set up an automatic event handling task to be run when a discovered system goes to a Critical status. Procedure 11 Creating a task to send an e-mail when a system reaches a critical state 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 60 In the Search panel, click Advanced Search.
d. e. In the Message Format field, select from the following formats based on the encoding preference of the recipient: • Standard. This default message format sends a text e-mail message to the recipients. • Pager/SMS. An e-mail message formatted with the same information and format as a pager message is sent to the recipients. • HTML. An e-mail message that looks like the HTML Event Details page is sent to the recipients.
10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. Click OK to save the collection. Then select systems from the Search dropdown list. From the first selection box (criteria selection), select system type from the dropdown list. From the second selection box (comparison selection), select is from the dropdown list. In the third selection box (value selection), the available values for a given criteria or comparison combination are given. Select server.
14 Reporting in HP SIM Standard reports Standard reports are shipped with HP SIM. The reports are based on common user scenarios and do not need any additional configuration or enablement. These reports are installed, configured, and available for use as soon as HP SIM is installed and configured. Standard reports are tied to existing systems collections in HP SIM, for instance, All Systems or All Servers. Report results appear based on logged in user authorization of systems.
Format for generated report: ◦ HTML (Recommended for viewing) Enables viewing an existing report in HTML format. ◦ XML Enables viewing an existing report in XML format. ◦ CSV Enables viewing an existing report in CSV format. • Copy HP SIM enables you to copy report configurations from an existing report configuration. You can edit the newly copied configurations to create a new report. NOTE: You must be signed in to HP SIM with administrative rights or operator rights to copy report configurations.
The reporting engine main page contains the Reports by Product table that displays the products registered with HP SIM along with the available reports. The Reports by Product table displays reports for HP SIM by default. Only products that have been registered with HP SIM have Predefined reports displayed. Table 6 Reports by Product columns Name Description Product/Report Name Displays the name of the products along with the total number of reports in parenthesis registered with HP SIM for reports.
New Enhanced reports A report configuration is a customer-defined set of preferences that pulls specified criteria from the database tables and places it in a report in the specified format. The report configurations can be saved and used to run a report at a later date with live data. An additional create new report option is to select the type of report to use. You can select the following options in any combination. • Include Chart • Include Table The report type graph supports three sub types.
If you click OK, the report is deleted and the product and report page is refreshed to show the correct status of the reports.
15 HP SIM tools Target selection Targets are systems that a tool acts upon. Targets can be single systems, collections, or groups of systems that are chosen just for the task at hand. You can select the targets either before or after selecting the tool. You can verify and modify the selection using the task wizard. After the targets are verified, they appear in the title area of the tool. NOTE: Some tools cannot work on multiple systems.
• Delete a task • Stop an executing task • Track task status Task information is available by selecting one of the following: • Tasks & Logs→View All Scheduled Tasks • Tasks & Logs→View Task Results HP SIM provides system-delivered (default) tasks. These tasks can be disabled or have their schedules modified but they cannot be removed or reassigned to another user. HP SIM requires these tasks (for example, Data Collection) to provide a complete picture of the systems being monitored.
Part IV HP SIM advanced features
16 Collections in HP SIM Collections in HP SIM Systems and events are grouped into collections based on information from the HP SIM database. After a collection is defined, you can display the results or associate the collection with a task. You can also save an edited or unedited collection as a collection with another name. You can use collections to organize large numbers of systems into smaller, more meaningful groupings.
• Run a system search and save the search criteria as the attributes defining a collection. Saving a collection from the Advanced Search page For more information on saving collections, see the Systems Insight Manager online help. Types of collections • By member When you create a collection, you can select exactly which specific systems or collections you want to include. From the, Customize Collections page, click New. The New Collection section appears. Select Choose members individually.
Because collections by attribute use a database query, collections that are complex take more system resources every time they are accessed. Keeping collections simple minimizes performance impact. • Combination collections Combination collections enable you to bind together a system collection and an event collection and to reuse and recombine system and event collections that you have created. NOTE: There are two kinds of combination collections.
set properties on members of these collections. Setting properties on systems that might not be part of the collection in the future would be of very limited value. • Edit Any collection can be edited. However, collections cannot change type. For example, you can change the criteria for a collection that is defined by attribute, but you cannot change the collection type so the collection is a collection by member or a combination collection.
There are two instances of SystemC in the view of the hierarchy because CollectionC is the same throughout the application. Any place that CollectionC is referenced, it will always contain the same systems. However, SystemD appears only under CollectionB. CollectionB and Copy of CollectionB are distinct and independent collections. • Move Move enables you to easily move a collection exactly where you want it in the hierarchy.
a certain collection, and that collection is made not visible, then the task will not run on that collection. You can change the visibility setting at any time. ◦ Status Displayed property You can set the Status Displayed property to enable you to easily view the aggregate status of a particular collection in the System and Event Collections panel. You can set this property only on individual systems or on collections by attribute, for example, the lowest displaying collection aggregate status.
• – Unknown – Informational Default View property When you select a collection in the System and Event Collections panel, the contents of that collection are displayed in the workspace. By default, different types of collections are displayed in different ways. Collections by attribute and combination collections default to a table view, but they can also be displayed as icons or a tree. Collections by members default to a tree view, but they can also be displayed as icons or a table.
17 HP SIM custom tools General concepts Custom tools are tools that can be created by the user to run on the CMS or on target systems. For example: • Remote tool A tool that runs on selected target systems. It might copy files to the target systems or run specific X-Window applications on the target systems. You can schedule this tool. • CMS tool A tool that runs on the CMS. It is usually a script or batch file and can pass in environment variables.
Table 8 Tool types (continued) Name Description CMS uses SSH to send one or more files to the target system, which then executes the tool. An example of an SSA tool would be a tool that wraps a common Unix command such as ls. cat, or cp. Multiple-system-aware command tool An MSA tool executes typically on the CMS and can work with multiple target systems. When launched, the MSA process is created once and then passed to all targets on the list. An XWindows tool is an example of an MSA tool.
• 5, Critical • 100, Informational NOTICEQUERYNAME. The collection name based on how the notice was generated. This value can say one of the following: • This system or event meets the following search criteria: +QueryName; • This system or event now meets the following search criteria: +QueryName; • This system or event no longer meets the following search criteria: +QueryName; DEVICENAME. The name of the system that caused the notice. DEVICEIPADDRESSCOUNT.
IF, RELATEDDEVICECOUNT = 2 Then, RELATEDDEVICEIP0=111.111.111.111 RELATEDDEVICEIP1=222.222.222.222 RELATIONSHIP%d. The relationship string with the associated system, and %d is the iteration number. For example: IF, RELATEDDEVICECOUNT = 2 Then, RELATIONSHIP0=ServerToEnclosure RELATIONSHIP1=VMGuestToVMHost Custom tool menu placement To place custom tools in the following menu locations, use a string in the form base|submenu|subsubmenu.
NOTE: When using the %i parameter, the current selection index (1, 2, 3, and so on) is substituted for this parameter during the substitution process. If the end of the repetition clause is reached and no %z parameter is encountered, the selection index and current election are automatically incremented to avoid an infinite loop during the substitution phase. In the above example, if there were two selected target systems, the expanded URL string would look like this: https://deploy.hp.
Run Now/Schedule Use to run the tool immediately or to schedule the tool to run (if the tool can be scheduled). If the tool can be run, the schedule a task page appears. You can schedule when and how often the tool runs. Delete Use to delete a tool. Deleting a tool removes it from the Manage Custom Tools page and from the system. If a tool is dependent on a task, an alert appears with the list of tasks associated with the tool.
NOTE: Your text editor must be able create a text-only file with no embedded formatting. 4. Following the leading XML version and tool-list tags, type the tool name tag of to define the type and name of the tool. The revision string is used to keep track of different versions of the tool as will be seen later.
9. To finish the TDEF, enter the final tool list tag as shown below. The fully composed TDEF for a SSA copy tool to deploy the HP Security Patch to a managed node and then execute, should display as follows: 10. Save the file. HP recommends using a file name that indicates its function, in this case,DeployHPSecurityPatchv.1.xml Make sure that the file name ends with the .XML extension. Note that file names on Linux and HP-UX operating systems are case-sensitive.
hostname. The element can have a value of true or false. If the element is true, it will be associated with the Toolboxes under HP SIM User and Authorization. This allows a trusted user to disable the tool in the Toolbox if the value is false. This tool launches in a separate browser window using the "target-frame" of WJAFrame. For additional parameters, see “mxtool command parameters” (page 203). NOTE: In the previous example, hostname.
For more information about specific MSA tool requirements and attributes, see “MSA-specific attributes” (page 201). Example Enabling Remote Desktop tool Remote Desktop is a Microsoft feature that enables you to remotely access any Windows 2003 server. Unfortunately, Remote Desktop is disabled by default during installation, which can lead to problems accessing the system without physically being present in front of the server.
Adding a TDEF to HP SIM After you create a custom TDEF, to function, you must add it into HP SIM. Add a TDEF to HP SIM using the mxtool -a command, as described in the following procedures: Procedure 14 Adding a TDEF to HP SIM 1. At a terminal or command line prompt, type mxtool -a -f . NOTE: For more information about mxtool command parameters, see “mxtool command parameters” (page 203). 2. To use the web launch tool previously created, type: mxtool -a -f /tools/webjetadmin.
Modifying a TDEF Modifying a TDEF allows users to customize the XML to align with their business. Each TDEF included can be modified to fit with each customers business needs. To modify a TDEF to execute as a different user, perform the following steps: Procedure 16 Modifying a TDEF 1. Modify the Windows HP SIM tools to use the new user account as follows: a. Navigate to the tools directory. Example: C:\Program Files\HP\HP SIM\tools b. Search the tools directory for the tool to modify.
18 Federated Search Select Reports→Federated Search.... Federated Search is a web-based HP SIM plug-in that enables you to search quickly across a number of Systems Insight Manager CMS systems. Federated Search finds systems using basic system criteria such as name, system type, subtype, and operating system. The search tool can also search software inventory information to find, for example, firmware versions across all Windows systems.
4. Configure the remote CMS. The main CMSs SSL certificate is exported to the secondary CMS, and the secondary CMS is configured to trust the main CMS. To have this configuration performed, you must provide credentials for a full-rights HP Systems Insight Manager user on the secondary CMS. The credentials supplied are used for this one transaction and are not permanently stored. NOTE: To avoid remote CMS connection errors, make sure a firewall is not blocking ports 50001 and 50002 on the remote CMS.
19 CMS Reconfigure Tool The CMS Reconfigure Tool feature provides a set of commands that enable you to quickly make common reconfiguration changes to HP SIM, HP Insight Control, HP Virtual Connect Enterprise Manager, and HP Matrix OE. The challenge in attempting to make operating system or CMS configuration changes is the difficulty in knowing exactly what steps need to be performed on a particular operating system/CMS installed environment.
When this command is run, and the new password is typed and confirmed, all services are stopped. The password entered is then updated on services that are configured to run using the installing user's credentials. Services running as local system will not be changed. NOTE: This command does not work with HP Insight Control server deployment. See the HP Insight Control Server Deployment User Guide for more information.
3. 4. Open the Windows command prompt and navigate to ..\Program Files\HP\ Operations Orchestration\Central\tools . Execute change-db-props.bat to change the Operations Orchestration database password. Enter the following and press Enter: C:\Program Files\HP\Operations Orchestration\Central\tools>change-db-props.bat The command, change-db-props must be executed passing only the user name and not domain, even if this is a domain account. 5.
• The host is still in the same domain. • All credentials are known. • The new host name can be resolved by the DNS server. • The new IP address is valid (assigned through DHCP if enabled on the CMS) and is the IP address assigned to the CMS. • If the SQL database is a local database running on the CMS server, reconfigure the CMS database information using the sqlredirect command. Warning Verify that all HP SIM or HP Insight Control operations are complete before running this command.
Procedure 22 Changing the database authorizations for Matrix OE and HP Operations Orchestration 1. Update the gwlmdb.properties file by executing the following command from the command line: vseinitconfig -a 2. 3. Open a Windows command prompt and navigate to ..\Program Files\HP\Operations Orchestration\Central\tools. Execute the following commands from the command prompt: mxpassword -m -x MxDBUserPassword= mxpassword -m -x io.db.password= 4. Execute change-db-props.
with the new database, and the username credential that HP SIM or HP Insight Control uses to access the new database. NOTE: This is not supported on VCEM or Matrix Operating Environment. NOTE: The parameters —s,—a and —b and their arguments are required. The parameter —p and its argument is optional. This command does the following: • Stops all installed HP SIM or HP Insight Control services. • Redirects the CMS to use the new SQL database.
20 Understanding HP SIM security This chapter provides an overview of the security features available in the HP SIM framework. HP SIM runs on a CMS and communicates with managed systems using various protocols. You can browse to the CMS or directly to the managed system. Securing communication Secure Sockets Layer (SSL) SSL is an industry-standard protocol for securing communications across the Internet.
In HP SIM, the Privilege Elevation feature enables tools to be run against HP-UX, Linux, and ESX managed systems by first signing in as a non-root user, and then requesting privilege elevation to run root-level tools. This can be configured under Options→Security→Privilege Elevation. WBEM All WBEM access is over HTTPS for security. HP SIM is configured with a user name and password for WBEM agent access. Using SSL, HP SIM can optionally authenticate the managed system using its SSL certificate.
The SSO certificate is created during the upgrade. To reestablish the trust relationships with the managed systems you might need to import the newly generated main certificate into the managed systems. Also, you might need to import the trusted certificates back into HP SIM's trust store. Certificate expiration and Certificate Revocation Check (CLR Check) HP SIM provides the support for certificate revocation check. By default, the revocation check is enabled for both client and server certificates.
Ways of enabling online mode There are two ways of enabling online mode. One is through Proxy settings, and the other is directly. In the former method, you must save the host address and the port of the proxy server. The latter method assumes that the certificate server is reachable from the CMS server without the need for the proxy settings. Example, the certificate server is located in the same intranet as the CMS server.
0 — Disable • Proxy settings: The proxy host and port can be configured using the below properties. The proxy settings can be cleared off or removed if both these properties are removed, or set as empty in the globalsettings.properties file.
Passwords Password fields displayed by HP SIM do not display the password. Passwords between the browser and the CMS are transmitted over SSL. Password warnings There are several types of warnings that can be displayed by the browser or by the Java plug-in on the browser, most having to do with the SSL server certificate. • Untrusted system This warning indicates the certificate was issued by an untrusted system.
Internet zone, causing improper operation. Ensure systems are being placed into the correct Internet zone when browsing. You might need to configure Internet Explorer, or use a different name format when browsing. System link format To facilitate navigation to managed systems, HP SIM provides the System Link Configuration option to configure how links to managed systems are formed. Go to Options→Security→System Link Configuration.
account. For automatic sign-in to HP SIM, a domain account must be used. On UNIX, HP SIM is installed and runs as daemons running as root. Windows Cygwin The version of Cygwin provided with the SSH server for Windows, for CMS and the managed systems, has been modified with security enhancements to restrict access to the shared memory segment. As a result, it does not interoperate with the generally available version of Cygwin.
NOTE: On a Windows system, the operating system account must have administrator-level access on the CMS for all of the commands to work properly. How to: configuration checklist General • Access to the CMS must be restricted, both at the network operating system-level and at the physical-level. • A strict separation between the contents provided by unrelated sites must be maintained on the client side to prevent the loss of data confidentiality or integrity.
• The CMS requires a user name and password to access WMI data on Windows systems. By default, a domain administrator account can be used for this, but you should use an account with limited privileges for WMI access. You can configure the accounts accepted by each Windows managed system by using the Computer Management tool: 1. Select the WMI Control item. 2. Right-click WMI Control, and then select Security. 3. Select the Security tab, select Root namespace, and then click Security> 4.
IMPORTANT: When using the Trust by certificate option, the HP SIM SSL certificate must be redistributed if a new SSL certificate is generated for HP SIM. SSH on the managed system normally operates in a mode similar to trust by certificate in that it requires the SSH public key from the CMS. Note that the SSH public key is not the same as the SSL certificate. The command mxagentconfig is used on the CMS to copy the key to the managed system.
5. For SSH, turn on the option to accept SSH connections only from specified systems. Select Options→Security→Trusted Systems, click SSH Host Keys, and then enable the The central management server will accept an SSH connection only if the host key is in list below. Afterwards, you must manually import each managed system's public SSH key into the list of keys in HP SIM. To configure this in previous versions of HP SIM, add or modify the following line in the Hmx.
21 Privilege elevation Privilege elevation enables users without root privileges to run tools requiring root privileges on HP-UX, Linux, and VMware ESX managed systems. To use this feature with HP SIM, a privilege elevation utility such as su, sudo, or Powerbroker must be installed on the managed system.
Enable secure communication HP SIM ensures that the user certificate contained in the smart card is trusted by a valid and known Certificate Authority (CA). It allows users to login to the CMS only if the certificate is trusted, and is not expired or revoked by the CA issuer, and also it ensures that the user is a valid SIM user. Microsoft Active Directory users Two-factor authentication is not supported for local CMS users.
Smart cards and Cryptographic Service Provider (CSP) HP SIM does not directly communicate with the Cryptographic Service provider rather it leverages the capabilities from the browser. It is expected that browsers need to be configured manually to communicate with the Smart card's CSP. Browsers must be able to recognize smart cards and prompt for PIN when user connects to HP SIM.
22 Contract and warranty The Contract and Warranty Status is available when you have a Windows CMS, and the HP Insight Remote Support Pack is installed. You can view Contract and Warranty status updates for HP systems that have contract and warranty data collection enabled. Click the Contract and Warranty Status icon to view the Contract and Warranty Details page for the system.
Collecting contract and warranty data The following tasks are used to collect contract and warranty data: • Initial contract and warranty collection. This task collects contract and warranty data from newly discovered systems. If the required system properties are not entered for a new system or automatically collected by HP SIM during identification, contract and warranty data will not be collected. • Monthly contract and warranty collection This task collects contract and warranty data every month.
• End Date The end date of an active contract. If no end date is available, this field is blank. • Contract Status The possible values are: • ◦ A: Active ◦ F: The start date is in the future ◦ X: Expired ◦ E: There is no end date ◦ I: The agreement is informal. This status might mean that the agreement is not finalized. ◦ B: Delivery blocked ◦ C: Cancelled Active Obligation This value is true if there is an active support contract for a system.
• Extension The number of days that this warranty has been extended. • Wty: HP HW Maintenance Onsite Support The warranty start and end date is listed for each warranty item along with the following information: ◦ Status The possible values are: ◦ – A: Active – F: The start date is in the future – X: Expired – E: There is no end date – I: The agreement is informal. This status might mean that the agreement is not finalized.
Monitoring contract and warranty status Contract and warranty status is shown by the following status types: Table 9 Contract and Warranty status Status Icon Icon Meaning Description Major The contract or warranty is expired Minor • Contract information is temporarily unavailable. • The contract expires in 30 days. Warning The contract expires in 90 days. Normal The system has a valid contract or warranty. Unknown No contract information was found.
23 License Manager License Manager enables you to view and manage product licenses within the HP SIM user interface. To access additional information about Updates, Upgrades, and Technical support, contact your HP services or HP partner representative or access the HP Support Center at www.hp.com/go/ hpsc.
NOTE: The new management processor license collection is supported on management processor and management processor devices. Deployment is supported on management processor and management processors with newer firmware versions. In some instances, licenses are managed and controlled by the licensed system (remote licensing). In this case, License Manager provides the facility to collect and deploy licenses to those systems.
Table 11 License types (continued) License Type Description Demo (seats and time) Offers full, unlimited functionality for a limited time and a specific number of seats. The license determines the number of days the key enables the product to function. The days begin counting from the day of first use. The key can permit more than one instance of the product to run. Demo keys can authorize up to 255 seats for up to 255 days. Demo (time) Offers full, unlimited functionality for a limited time.
Table 12 License types reported by management processor products (continued) License Type Description the product to run. Demo keys can authorize use for up to 65,535 days. Licensed System(s) License Systems in License Manager enables you to list the systems licensed for the selected product. Products can elect to not display all or some licensing details. Some products provide licenses to enable other products. The license keys generated by these products can be manually added.
2 3 4 • Key. The license keys received from the target systems. Each key retrieved from a system is on a separate line. Some products have more than one license key. License details are contained in the key, and each key might enable more than one product. Product. The name of the product associated with the use of this key. Response Status. The status of the request for license data for the selected system. Successful task A. Licensing information from the remote system. B.
Assigning and Unassigning licenses HP SIM enables you to assign and Un assign product licenses for plug-ins, if applicable for that plug-in, and to assign licenses to remote target systems when licenses are managed remotely. Remember that management processor licenses must be applied directly to the management processor and NOT its host server.
Add License page 1 Select the complete key string and press Carl + C to copy it. Position the cursor in any of the five fields forming the input box and press Carl + V, or right-click your mouse to paste the license key. If the Add License function was selected after you copied the key, press Carl + V to paste the key. 2 3 The license key displays with five characters in each field. Enter the full path and file name in the Specify a file name and path field. Click Browse. a.
Assigning or Applying Licenses page 1 System Name 2 The name of the system where the task was executed. Serial Number 3 A number the licensing product chooses to identify remote systems. (Check product information for specific details). Unique Identifier 4 A unique string that further identifies a system. Systems can be licensed by any combination of system name, serial number, or unique identifier. Status 5 The status of the use of the license on the named system.
License unlicensed systems (optional) page 1 System license status 2 Displays the status of system licenses, such as Not licensed, or assigned duration license. System selected to be licensed 3 System Name 15.146.233.1 is selected to have a license assigned to it. Licenses currently available 4 Displays all of the currently available licenses to be assigned. License selected 5 A license is selected to be assigned to system 15.148.233.1.
24 Storage integration using SMI-S About storage systems Storage systems are SAN-attached Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters). HP SIM uses WBEM SMI-S providers to discover and collect data from storage systems. To view the latest information about HP SIM device support and for information about obtaining and installing SMI-S providers, see http://www.hp.com/go/hpsim/ providers .
• Receive storage system events and associate them with the system that generated the event (through Command View) running on a system, or from a tape library management card. • Context launch appropriate management application from the context of the event or the context of the system running the Command View that generated the event. IMPORTANT: To discover an XP P9500 array, you can either discover it with a CVAE server or discover it with embedded SMI-S.
• • • ◦ Firmware version ◦ Controller characteristics RAID details ◦ RAID type ◦ RAID configuration SAN and NAS ◦ Network addresses ◦ Manufacturer ◦ Model IS and MNHA ◦ Part number ◦ Total number of disks ◦ Disk details ◦ Servers being serviced by this system Introduction to SMI-S for HP SIM The Storage Management Initiative Specification (SMI-S) is a Storage Networking Industry Association (SNIA) standard that enables interoperable management for storage networks and storage dev
WBEM WBEM is a set of management and Internet standard technologies developed to unify the management of enterprise computing environments. WBEM includes the following specifications: • xmlCIM: Defines XML elements, conforming to DTD, which can represent CIM classes and instances • CIM Operations over HTTP: Defines a mapping of CIM operations onto HTTP; used as a transport mechanism SLP SLP enables computers and other devices to find services in a LAN without prior configuration.
HP SIM displays storage systems as follows: • Internal drives These systems must appear in the Properties pages and the inventory database as components of their respective systems. • Tape libraries These devices are identified and included in the All Systems, All Storage Systems, and All Tape Libraries collections. • SAN The Command View systems for these devices are identified and available from the Tools & Links tab of the System Page for the systems serving the Command View systems.
Configuring the SNMP trap destination on Windows 2000 Procedure 27 Configuring the SNMP trap destination on Windows 2000 1. Select Start→Settings→Control Panel→Network→Services→SNMP Service. The SNMP Service Properties dialog box appears. 2. 3. 4. 5. Click Traps. Enter a community name, such as public. Click Add to list. At the bottom of the dialog box, click Add. The SNMP Service Configuration dialog box appears. 6.
3. Select (4) to import the management server's certificate into the CVAE provider's truststore for event indications. Enter the following: • Enter alias: Use the management server's DNS name (for example: hostname.hp.com). • Enter truststore-password: indtrust • Enter authenication-filename (absolute path): Enter path to management server's certificate file. For additional information, refer to the HP Storageworks P9000 and XP Event Notification whitepaper.
Viewing storage system collections HP SIM enables you to view storage system information for collections and individual storage systems. Procedure 31 Viewing storage system collections 1. 2. In the System and Event Collections panel, expand Systems, Shared, Systems by Type, and Storage Systems. Select one of the following: • All Storage Systems • All Storage Hosts • All Storage Switches • All Storage Arrays • All Tape Libraries The system table view page for that collection appears.
• Storage Ports—All Storage Hosts Lists port information for all storage host HBAs. • Storage Ports—All Storage Switches Lists port information for all storage switches. • Changer Devices—All Tape Libraries Lists the name, firmware version, and status for all tape libraries. • Media Access Devices—All Tape Libraries Lists the name, firmware version, and status for all tape libraries.
25 Managing MSCS clusters Cluster Monitor is a core component of HP SIM, and adds the ability to monitor and manage multi-node clusters. Cluster Monitor also manages multiple cluster platforms in a heterogeneous environment. Procedure 34 Managing clusters 1. Access the Cluster Monitor page by using one of the following methods: • Method 1: 1. Select Tools→System Information→Cluster Monitor. Note: If no MSCS clusters are discovered, Cluster Monitor is not listed in the menu. 2.
Cluster fields Table 13 Cluster fields Name Description Name Name or alias for the cluster Status Status of the cluster: Normal (the cluster condition is functioning normally, every node condition and resource condition is normal), Degraded (the cluster condition is degraded if at least one node condition is failed or degraded or at least one resource condition is degraded), Failed (the cluster condition is failed if every node condition is failed or at least one resource condition is failed), and Othe
Resource fields Table 16 Resource fields Name Description Name Physical or logical entity that is capable of being owned by a node, brought online and taken offline, moved between nodes, and managed as a server cluster object Status Status of the resource: Normal (the resource state is online), Degraded (the resource state is Unavailable, Offline, Online Pending, or Offline Pending), Failed (the resource state is failed), and Other (unable to determine the resource condition) Group Collection of reso
the Major threshold value. It remains in the Major range until it falls to or below the Major reset value. The Minor and Major reset thresholds behave similarly. You can specify different thresholds for each CPU in each node of a cluster. Cluster resources supported by HP SIM HP SIM supports the following Cluster Monitor resources: • Disk and CPU resources Monitor disk capacity and CPU utilization, respectively. You can set minor and major thresholds for nodes in a cluster.
Disk polling rate The Disk polling rate determines how often Cluster Monitor checks the free disk space as reported by the appropriate Insight Management Agent on monitored nodes. Adjust the polling rate by configuring the Cluster Monitor node resource settings. MSCS status polling rate The polling rate you enter determines how often Cluster Monitor checks the MSCS status of monitored clusters. Adjust the status polling rate by configuring the Cluster Monitor's cluster resource settings.
26 HP SIM Audit log HP SIM logs all tasks performed by all HP SIM users on all systems. The information is stored in the Audit Log file on the CMS. Several features of the HP SIM Audit Log are configurable. For example, you can specify which tools log data and the maximum Audit Log file size. The HP SIM Audit Log is configured through the log.properties file, and tool logging is enabled or disabled through the XML tool definition files. On Windows, the audit log can be found at the /logs/mx.
104611: 2008-04-24 11:17:45 PDT,JOB,PROGRESS,START,JOB,44641_cup12.hp.com,VERBOSE,partner,,, Running Tool:ls Expanded Command Line:ls Targets: cup11.hp.com 104612: 2008-04-24 11:17:45 PDT,JOB,PROGRESS,START,JOB,44641_cup12.hp.com:cup11.hp.com, DETAIL,partner,,, Running Tool:ls 104613: 2008-04-24 11:17:45 PDT,JOB,SUCCESS,DONE,JOB,44641_cup12.hp.com:cup11.hp.
27 HP Version Control and HP SIM About the Version Control Agent The HP VCA is an Insight Management Agent installed on a system that enables you to view HP software and firmware installed on the system. You can configure: HP VCA to point to a repository managed by HP VCRM, enabling easy version comparison and software updates from the repository to the system where HP VCA is installed. HP VCA provides version control and system update capabilities for a single HP system.
About the Version Control Repository Manager HP VCRM is an HP Insight Management Agent that manages a directory of HP software and firmware components. You can use HP VCRM without HP VCA to provide a listing of available software and firmware to load on the local machine. HP VCRM is part of the HP Foundation Pack. HP VCRM is designed to be used in a one-to-many configuration with a HP VCA installed on each managed HP system to manage installed HP software and firmware.
About software repositories Updating ProLiant Support Packs and components using HP VCRM from a single or multiple repositories saves time and is key to standardizing software maintenance and update procedures on distributed systems. For maximum manageability and flexibility across operating system platforms, each repository you create must conform to the following conditions: • It must be located on a local drive with write access. • It must be updated automatically by the HP VCRM.
28 Compiling and customizing MIBs HP SIM; provides the capability of managing systems through SNMP and by receiving incoming SNMP trap events. HP SIM ships with many MIBs pre-configured. For a complete list, see “Out-of-the-box MIB support in HP SIM” (page 211).You can use tools provided by HP SIM to integrate third-party (non-HP) SNMP v1/v2 MIBs into HP SIM and to provide support for processing and displaying traps from other systems.
directory by default so any MIB that you intend to register should be copied to the \mibs directory. While mcompile does provide some capability to specify a different directory to search for MIBs, as a best practice HP strongly recommends you place all MIBs in the \mibs directory.
In this example, TRAP-TYPE and sysName are readily resolved as in the example above. hpSwitchBladeType2-Mgmt is resolved by mcompile checking HP-SWITCH-PL.MIB. agSlotNumber is resolved from BLADETYPE2-SWITCH.MIB and ipCurCfgGwIndex is resolved from BLADETYPE2-NETWORK.MIB. To illustrate further how imports are resolved — the following procedure is how mcompile would attempt to resolve the import for hpSwitchBladeType2-Mgmt: Procedure 36 How MIB imports are resolved 1. 2. 3. 4. 5.
The initial command to register the file uses the .cfg extension, but all subsequent commands refer to the file by its .mib extension. IMPORTANT: mxmib is order sensitive. While the command enables you to compile MIBs whose dependencies have not been compiled, for optimal results, HP recommends that you register MIBs with HP SIM in order of dependency.
--#CATEGORY This provides a categorization of the trap for ease of viewing and use in forming HP SIM lists. You can use predefined categories or, if none of these fit your need, you can create a category befitting your circumstances. The HP SIM SNMP Trap Settings page provides a GUI to change the CATEGORY after MIB compilation. The predefined categories in HP SIM are shown below.
• SYSTEM AND ENVIRONMENTAL • Tandem EMS Events • TruCluster Events • Unassigned • Unisys Configuration Agent Events • UNKNOWN • WYSE Events • ZESA • ZHRM --#MSG_FORMATTER This keyword has a number of HP SIM specific commands. These commands are parsed and executed when a paging or e-mail Automatic Action on Event rule is created and exercised within HP SIM. You might view these commands as a paging or e-mail command language.
--#SEVERITY CRITICAL --#TIMEINDEX 99 --#MSG_FORMATTER "$V1V#Computer: # $V3V#Drive Status: # $V9V#Serial Number: #" ::= 3029 The e-mail or pager output would appear as: Event Notice ID: 3029 Computer: CRONUS Drive Status: FAILED Serial Number: WS7000134715 Event Description: Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of an HP Drive Array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status.
Fields can be modified as follows: • The Description field is the long description stating the nature of the trap. The Description field is used on the Event detail page and can be included in paging and e-mail notifications. This field corresponds to the DESCRIPTION keyword in the CFG files. • The Event Type field is the short description and is used as the display string when viewing a list of events. The event type can also be used as part of a paging or e-mail notification.
A Important Notes System and object names must be unique System and object names must be unique in HP SIM. For example, the name of a Virtual Connect Domain must not be identical to the name of a Virtual Connect Switch, or they can be confused in HP SIM. The Virtual Connect Domain is a virtual system with no physical network address. The Virtual Connect Switch is a physical system that is network addressable.
Database firewall settings When using MSDE (or Microsoft SQL Server 2005 Express Edition), Microsoft SQL, or Oracle database server located on a remote Windows XP SP2 server, the firewall settings on the remote server must be turned off. To do this: 1. Select Start→Control Panel→Windows Firewall. 2. Select Off. Annotating the portal UI Annotation refers to adding a small amount of textual information, such as the name of the Central Management Server (CMS), near the product name when browsing to the CMS.
To view the EULA, use a text editor to open the eula_license.xml file, and search for third-party software . HP addresses security bulletins for the software components listed in the EULA with the same level of support afforded HP products. HP is committed to reducing security defects and helping you mitigate the risks associated with security defects when they do occur. HP has a well defined process when a security defect is found that culminates with the publication of a security bulletin.
This creates a temporary directory. For example, makeself-32350-20091024210345, is where the HP SIM RPMs will be located. You can use the rpm --checksig command to verify the HP signature of the RPMs. After verifying the RPM, enter ./sysmgmt.bin to install HP SIM. If you install HP SIM sysmgmt.bin without installing the HP public key, you will receive the following warning: Installing hpsim* ... warning: hpsim-C.06.00.00.00.%20091027-1.i386.
Configure or Repair Agents Configure or Repair Agents tasks that combine Critical, Unknown, and Unmanaged targeted systems appear to hang at 0% but will eventually complete. Data collection reports Data Collection reports might report the network interface for HP-UX systems incorrectly. This is due to an issue with SNMP agents on HP-UX.
B Troubleshooting Adobe HP SIM requires Adobe 10 plugin on remote browsing machines. Adobe 11 is not compatible with HP SIM and might produce errors. Agentless Management Service AMS re-installation through Configure or Repair Agents on an RHEL 6.2 target might fail, even though the force install option is selected. Uninstall AMS from target and then install through Configure or Repair Agents, it will install it successful.
This parameter is a global setting and is currently configured to 60 seconds. For all practical purposes this interval is sufficient. However if there is a case due to slow responding systems, if this interval is found to be insufficient, then you can change the default value through the command line interface: go to and execute the following command: mxglobalsettings -s bladeInsertDiscoveryWaitTime=120, where 120 represents the new value in seconds.
If you receive a Page Not Found browser error when launching HP Insight Control performance management tools from within HP SIM, the CMS name link might not have resolved correctly on the network. Solution: Note the name being used in the browser window, verify that the name resolves on the network, and that it is not being affected by any proxy settings in the browser.
4. • Click OK until all dialog boxes are closed. The company DNS servers could be having problems. HP recommends that you contact your company's network support group. Complex You cannot delete a complex and all associated systems when you first select either the system or complex alone and then try to delete. Solution: You must select all associated systems from the list for the deletion to work correctly.
C7000 containing 15 BL servers (single sided) and 1 Double dense server = 17 servers C7000 containing 10 Double dense servers = 20 servers Therefore with number of servers exceeding the number of available slots, the B side of each blade beyond the 8th double dense blade or beyond the 16th blade will be missing from HP SIM.
a system is listed in this table; even one with no working credentials is listed with an Access Type of None. To resolve this issue, restart HP SIM to remove any extraneous database records, and re-run the discovery or identification task. Data Collection Capacity information is not available from providers for passively managed storage arrays.
------------------------------------------------------------If you see that data collection failed because of a WBEM connection, it might be caused by a failed WMI Mapper proxy. Solution: Complete the following steps: Procedure 43 Issue with data collection failing because of WBEM connection 1. Physically verify all of the configured Pegasus WMI Mapper proxies. From the Administrative tools→Services menu on the server hosting the Pegasus WMI Mapper proxy, be sure the Pegasus WMI Mapper is running. 2.
Discovery A managed system must not have Hyper-V host, SMI-S Storage CIMOM proxy, and SCVMM installed together. If they are all installed, HP SIM will not be able to set all the subtypes. ------------------------------------------------------------To discover an XP P9500 array, you can either discover it with a CVAE server or discover it with embedded SMI-S. Do not use both methods of discovery together because there are chances for Data collection and WBEM subscriptions to fail.
------------------------------------------------------------If an HP Logical Server that is created in Insight Dynamics is given the same name as the operating system host name of the blade on which it is applied, then the logical server is deleted when the blade is rediscovered. Solution: To avoid this, be sure the logical server name is different from the host name of the blade.
complex or the management processor; the reason is the partition still has vPar defined within the partition. iLO Deployment to an iLO with Trust Platform Module (TPM) enabled on the server will fail. You can only deploy iLO firmware if TPM is disabled. Linux servers When a Linux server is discovered as an unmanaged system: 1.
5. Select Toolbox is enabled. 6. Under Show Tools in Category, select Configuration Tool from the dropdown list. 7. Select Delete Events and Clear Events, and move them to the Toolbox contents window. 8. Click OK Next, create an authorization on the systems that you want to enable the user to clear or delete events. 1. Select Options→Security→Users and Authorizations. 2. Select the Authorizations tab, and click New. 3. In the Select field, select the users or user groups to which to assign the toolbox. 4.
default, daisy chained enclosures are displayed as c7000 enclosure models. As a result, when c7000 and c3000 enclosures are daisy chained, and the Onboard Administrator is discovered, the c3000 Tower Model enclosure is displayed as a c7000 enclosure. To ensure that the daisy chained enclosures are displayed accurately, you must discover the Onboard Administrator on each of these enclosures.
After you have selected the Install Linux PSP or ESX agents and Register VM host options in a Configure or Repair Agents task for ESX 3.5 U4 or later, the VM-host registration task fails because the system shows as Not Responding in Vcenter. Vcenter takes about five minutes for a system to reach a Normal status and therefore fails when HP SIM tries to register the VM host. Re-run the VM-host registration task at a later time when the server is in a Normal state in Vcenter.
NOTE: This applies to both x86 and x86_64 if the user elects to install the XWindows support. NOTE: These must be the 32-bit version even under x86_64 architecture as HP SUM and several of the RPMs require 32-bit libraries installed. NOTE: The versions below are needed as a minimum. Later versions of these can most likely be used as well. • libuuid-2.17.2-6.el6.i686.rpm • freetype-2.3.11-5.el6.i686.rpm • libSM-1.1.0-7.1.el6.i686.rpm • libICE-1.0.6-1.el6.i686.rpm • libXi-1.3-3.el6.i686.
• Ensure WMI is enabled and running on all Windows target servers. • For Linux, ensure the SSH port is not blocked. • In some rare cases, external storage enclosures can cause HP Smart Update Manager to report a discovery failure. To resolve this problem, disconnect the external storage until the firmware updates are completed. • For Linux, ensure that the target server can be contacted through SSH and that the scp command is available to securely send files to the target server.
the VMware ESX Host subtype, the WBEM cimserver on the ESX host must be up and working correctly.
Installation HP-UX install/execution of partner plug-ins (for example, HP Insight Dynamics - VSE for Integrity) might fail due to failed communication with HP SIM. Reviewing the install logs, daemon service logs and command line command output of partner commands may show long execution time with failed results describing a failure to connect to HP SIM or the message java.net.NoRouteToHostException: No route to host (errno:242). Local partner communication to HP SIM occurs using the ‘localhost’ hostname.
When a subscription license for a particular product has expired, license manager's opening table will still show that product has no system limit. The true disposition of licenses for the corresponding product can be determined by opening Manage Licenses. If an expected subscription license is not listed, it has expired and is no longer available.
Onboard Administrator When an Onboard Administrator system is deleted, health status of the bare metal server systems remain stale. ProLiant OA must be rediscovered to obtain updated health status of the bare metal server systems. OpenSSH OpenSSH installation fails on a Windows XP SP3 system. Solution: Verify that the Network access: Sharing and security model for local accounts under Local Policies→Security Options is set to Classic - local users are authenticate as themselves.
1. The wbemportlist.xml file used by HP SIM must be altered to add the additional or alternate WBEM port to be used. The file is located in C:\Program Files\HP\Systems Insight Manager\Config\Identification. This example shows where the new lines (in red) must be added to the tag in the xml file:
------------------------------------------------------------The Property pages for the VMWare ESX (Non-Embedded) operating system are not available due to limitations in the WBEM agents. Reporting It has been observed that when HP SIM is upgraded from 6.2 to any later version, Enhanced Reports cease to work. If you encounter this issue, you must perform the following steps to solve the problem. Procedure 47 Correcting issue with Enhanced Reports not working after an upgrade from HP SIM 6.2 1.
2. 3. Restart Windows SNMP service. Start the HP SIM service. SSH communication Domain support for SSH communication: • Hyper-V systems SSH communication between a CMS and a managed system works propertly only when the managed system is in a workgroup. If the managed system is in a domain, then the communication between the managed system and the CMS fails over SSH. • Windows systems SSH communication between a CMS and a managed system fails if both are in a domain.
Tools The message /tmp/Acmd42947.bat[26]: /usr/dt/bin/dtterm: not found might appear when running the following tools on HP-UX 11.31: • Retrieve Bastille Configuration file • Deploy Bastille Configuration • Consolidated Logging Wizard • Configuration Synchronization Wizard To eliminate this problem: 1. Remove the above tools using the CLI command mxtool -r -t . 2. Edit the tool definition XML files, replacing instances of dtterm and hpterm with xterm.
00010203-0405-0607-0809-101112131415 UniqueIdentifier in SIM 03020100-0504-0706-0809-101112131415 Virtual Connect Enterprise Manager Unable to browse to VCEM menu when logged in as read only user. To resolve this issue, install VCEM and other dependent components from Integrated installer component>selection screen.
Table 18 Minimal versions (continued) Product Version Server ROM (see supported server matrix for Virtual Connect) ProLiant Support Pack / SNMP agents 8.1 ProLiant Support Pack / WMI providers 2.2 Systems Insight Manager 5.3 or later Virtual machines HP Insight Management WBEM Providers and SNMP agents must not be installed on a virtual machine guest operating system.
events. If you do not unsubscribe for the WBEM events, HP SIM will no longer receive indications from the managed system.
C Protocols used by HP SIM HP SIM uses many different management protocol standards. This capability enables HP SIM to provide management support for a wide array of manageable systems. SNMP The Internet Engineering Task Force (IETF), the standards-rating body for the worldwide Internet, has defined a management protocol, SNMP, which has accumulated a major share of the market and has the support of over 20,000 different products. SNMP has its roots in the Internet community.
community string specified for that system in HP SIM match. The community string, "public," is a commonly used default. However, you can specify any community string needed for your security requirements. NOTE: Community strings on the managed system and the HP SIM community strings for the system must match to manage the system through SNMP. Some SNMP management agents also provide IP address filtering. Be sure the HP SIM IP address is in the allow list for any given SNMP agents.
Without HTTPS enabled, HP SIM does not discover any WBEM-based features on a system. Support for non-HP systems has been expanded starting with HP SIM 6.0. NOTE: HP SIM supports WBEM over HTTPS to ensure user supplied WBEM name and password pairs are protected. NOTE: OpenWBEM is not supported. Remote Method Invocation (RMI) Java RMI is used within the CMS only for inter-process communication.
Management standard Description Functionality when enabled ICMP ICMP is a required protocol tightly Provides system reachability (ping) integrated with IP. ICMP messages are check during system discovery and delivered in IP packets and are used before other operations for out-of-band messages related to network operation. HP SIM can use ICMP messages to ping a managed system. However, some routers block ICMP messages so HP SIM provides an alternative ping using TCP.
Management standard Description Functionality when enabled WS-Management A DMTF standard for exchanging Identification, inventory, and events management information using web services. You can use WS-Management to transport CIM as an alternative to CIM-XML. WMI WMI is Microsoft's implementation of Identification, inventory, and events WBEM. WMI runs over Distributed Component Object Model (DCOM), which in turn, uses RPC.
D Data Collection After HP SIM collects data initially during the identification process, you can schedule a Data Collection task to specify systems and run the task with different schedules. In addition to the default Initial and Bi-Weekly Data Collection tasks built in to HP SIM, you can set new data collection tasks targeting specific managed systems.
Bi-weekly data collection The Bi-Weekly Data Collection task runs the Overwrite existing data set (for detailed analysis) option on all systems in the system default collection. The default schedule is to run every two weeks on Saturday at 12:00 a.m. You can view the Data Collection Report for a system after data has been collected by selecting it from the system table view page. This action displays the System Page, where you can select the Tools & Links tab and then click Data Collection Report.
E Default system tasks Polling tasks track the health status of systems in associated collections. Hardware status polling must occur periodically to determine when systems go offline or when hardware degrades. You can customize polling tasks for specific systems to run at scheduled times. You can also create polling tasks with different collections to meet your needs. You can configure polling tasks to take place based on the receipt of an event. Event polling tasks are associated with event collections.
NOTE: If you discover more than 500 systems, HP suggests you change the interval to something greater than 10 minutes (for example, 15 minutes for every 1,000 systems). • This task collects status information for SNMP, or WBEM systems that are Server, Cluster, or Management Processor types. By default, this task polls every 5 minutes and at start-up.
Old Noisy Events Includes events that are transient and happen frequently, but do not generally indicate hardware failures. For example, link up, link down, and authentication events. These events fill the event database tables, but do not add value to the hardware event history. Events Older Than 90 Days This task deletes events older than 90 days and can help maintain HP SIM by limiting the total number of events. By default, this task is disabled.
Version Status Polling for Systems no Longer Disabled This task runs the software version tool when a system changes from a disabled state to an enabled state so that the status of the software loaded on the system is kept current in HP SIM. Check Event Configuration This task checks event configuration on all systems and is scheduled to run every day. The Weekly Check Event Configuration task can be edited. Status polling Polling tasks track system health status for systems in the system list.
F Host file extensions Hosts files are used during discovery to manually add multiple systems to the HP SIM database. Hosts files typically contain IP addresses, system names, system name aliases, and user comments. The hosts file that you create can contain additional information about systems. The information appears as one or more comments that precede the hosts file entry for the system. Unless other values are specified, the default values are used.
# Sorted by: IP address # Date: 28-Mar-00 2:29:31 PM # Author: administrator The system EngProliant uses all current defaults. There are no additional comments. 16.26.176.92 EngProliant.compaq.com EngProliant #user comments The system testServer in the following example defaults for TYPE. The defaults for SNMP Timeouts and Retries were restored for this system but only apply to testServer. The SNMP write community string default was changed and only applies to testServer.
Default values If a parameter is missing in the hosts file, the default is applied.
Table 22 Hosts file default parameters (continued) Keyword Value Description SNMP_MON Public Read only (Default) SNMP_CON No default To use a hosts file to specify systems for an automatic discovery, add the hosts file name to the Ping inclusion ranges, system (hosts) names, templates, and/or hosts files section of the Discovery page under the Configure general settings section.
G System Type Manager rules System Type Manager enables you to extend HP SIM's SNMP-based discovery so that it is able to identify new types of systems. You do this by creating a System Type Manager rule that maps a System Object ID (OID), and optionally an additional MIB variable, to the desired type. Manufacturers assign unique System OIDs to their SNMP-instrumented products. Systems supply information about themselves using variables described in files called MIBs.
H Custom tool definition files Custom tool definition files are XML files that describe how HP SIM should run tasks based on a program, script, or UTL added by the user. This appendix describes the wuyntax of these tool definition files (tdef). Tool type-specific requirements SSA-specific attributes An SSA tool executes on a selected target and is only aware of the target system environment.
Table 24 MSA-specific attributes Attribute Syntax1 Description msa-block (commnad/parameters) Specifies an MSA command, the parameters for the command, and an execution node on which the command executes. command (parameters) Specifies the command for an MSA tool. If the command accepts parameters, you must specify the command as a “Parameterized strings” (page 203). This element may have two attributes: command-type and log.
Table 25 WLA-specific attributes (continued) Syntax1 Attribute Description Target-format (parameters) An optional parameterized string that provides a way for web-launch applications to pass long lists of targets. The gets expanded in exactly the same manner as the URLs defined for the tool (for example, ).
Table 27 Global attribute parameters Parameter Description %t Job ID for the task being executed %u Name of the user running this task %e Name of the user this task will execute as %s Management server hostname of the core CMS running the tool (the HP SIM server name) %# Substitute the value input by the user for the parameter referenced by the number (#) provided, as a list index position (one-based positive whole integer... %1, %2, %3, and so on).
Table 29 Multiple selected target parameters (not supported for Custom Command Tools) NOTE: Parameter Description %( ... %) Repeated pattern (only repeats if a current selection exists). If a current target selection does not exist, the text between the delimiters is removed on expansion. This allows the text to be optional and dependent upon the target selection list. %i Selection index (one-based).
Table 31 Defined name values Names values Description product-name 32 character string Product-version 24 character number Insert-separator Insert a separator line in the menu structure before ("true") or after ("after") this tool. Values: true | after | false (default: false) I18n-attrs String. Name of a resource bundle for storing localized tool parameters. See the section on tool internationalization. Tool-id String.
Table 33 Web-launch tools (continued) Names values Descripti the tool's URL into workspac instead, load the URL into specified frame. Tool Filtering attributes Common filtering values available to use for TDEFs.
• Two adjacent period characters are interpreted as if they delimited the number zero, so "1.0.3" is equal to "1..3". • A beginning period character is interpreted as if preceded by a zero, so ".9" is equal to "0.9". • Trailing zero numbers are disregarded, so "1.0.0" is equal to "1" Environment Variables Specific environment variables (EVs) available to use for TDEFs. In addition to this list, operating system environment variables are also available (for Windows systems) to be passed into TDEFs.
Table 35 Environment Variables (continued) Names values Description DeviceMACAddress%d Based on the MAC address count, %d is an integer that references the actual MAC address variable.
Table 36 New Command Line Tool parameter entry guidelines (continued) Parameter field Data entry required? Parameter string assignment Entry guidelines command. Refer to the HP SIM Installation and User Guide for more information. CAUTION! If root is specified, any user authorized to run this tool may gain full access to the managed system depending on the definition of the command and its capabilities. File path to save tool No %8 Path name of new tool. Example: /var/opt/mx/ tools/mytool.
I Out-of-the-box MIB support in HP SIM The following table represents the key MIBs that ship with HP SIM. Those MIBs that are marked as preloaded are registered as part of every HP SIM installation. The remaining MIBs are in the MIB directory for you to compile, if necessary, for managing those types of systems in your environment. Table 37 MIBs supported in HP SIM MIB name Supports Pre-loaded asmib.mib ARC Serve X atmf.mib ATM device X avsnmpv1.mib Availant Manager X bkupexec.
Table 37 MIBs supported in HP SIM (continued) 212 MIB name Supports Pre-loaded cisco-port-security-mib.mib cisco products X cisco-process.mib cisco products X cisco-products.mib cisco products X cisco-rttmon.mib cisco products X cisco-stack-mib.mib cisco products X cisco-stackmaker.mib cisco products X cisco-stp-extensions.mib cisco products X cisco-syslog.mib cisco products X cisco-tc.mib cisco products X cisco-tcp.mib cisco products X cisco-udldp.
Table 37 MIBs supported in HP SIM (continued) MIB name Supports Pre-loaded cpqsanapp.mib SAN Appliance X cpqsanevent.mib SAN Appliance X cpqscsi.mib HP Proliant Storage X cpqservice.mib HP Service X cpqsinfo.mib HP Proliant System and Environmental X cpqsm2.mib HP Proliant remote management cpqsrvmn.mib HP Proliant System and Environmental X cpqstdeq.mib HP Proliant System and Environmental X cpqstsys.mib HP Proliant Storage X cpqthrsh.mib HP Proliant threshold X cpqups.
Table 37 MIBs supported in HP SIM (continued) 214 MIB name Supports Pre-loaded hs_agent.mib SWCC X lsf001.mib LSF product X msa2000traps.mib MSA2000 Array(HPMSA) X nsadimm.mib HP Netserver X nsaevent.mib HP Netserver X nsainfo.mib HP Netserver X nsapci.mib HP Netserver X nsascsi.mib HP Netserver X nsavolcp.mib HP Netserver X old-cisco-chassis.mib cisco products X old-cisco-flash.mib cisco products X old-cisco-interfaces.mib cisco products X old-cisco-ip.
Table 37 MIBs supported in HP SIM (continued) MIB name Supports Pre-loaded zsmp.mib Tandem's Subsystem Control Facility (SCF) X ztmx.mib Tandem SNMP Trap Multiplexer X ztsa.
J Support and other resources Related documents Documentation and support For support, software updates, and additional information on HP SIM and other products used with HP SIM, see the following websites: • HP SIM website at http://www.hp.com/go/hpsim/ for general product information and links to software downloads, documentation, and troubleshooting information • HP Software Depot website at http://www.software.hp.
Glossary A administrative rights user A user who is authorized for the All Tools toolbox on all systems, including the CMS. This type of user has been given special privileges to administer the HP SIM software. administrator A user who manages users, resource pools, and self-service requests through HP Insight Orchestration console. agent A program that regularly gathers information or performs some other service without the user's immediate presence.
cluster A parallel or distributed computing system made up of many discrete systems that form a single, unified computing resource. Clusters vary in their features, complexity, and the purposes for which they are best suited. cluster monitor resource A program that provides a monitoring or management function for clustered nodes in a cluster. CMS A system in the management domain that executes the HP SIM software. All central operations within HP SIM are initiated from this system.
event Information sent to certain users that something in the managed environment has changed. Events are generated from SNMP traps. HP SIM receives a trap when an important event occurs. Events are defined as: • Warning. Events of this type indicate a state that might become a problem. • Informational. Events of this type require no attention and are provided as useful information. • Normal. Events of this type indicate that this event is not a problem. • Minor.
to manage all HP server platforms. HP SIM can also be extended to deliver unparalleled breadth of system management with plug-ins for HP storage, power, client, and printer products. Plug-ins for rapid deployment, performance management, and workload management enable systems administrators to pick the value added software required to deliver complete lifecycle management of their hardware assets.
management protocol A set of protocols, such as WBEM, HTTP, or SNMP, used to establish communication with discovered systems. Minor status Status information collected from the system that indicates one or more of the monitored subsystems are not operating properly which is impacting the system. Action should be taken as soon as possible to prevent further failure.
The server deployment is installed separately from HP SIM. It requires a license for each server managed. You must register your server deployment product to purchase licenses or obtain a 10-node 30-day license before installing server deployment (a 10-node 7-day evaluation license is built into the software). The server deployment is installed from its own DVD. See http:// www.hp.com/servers/rdp for information about server deployment including a link to obtain evaluation licenses or register your product.
See also enclosure. Shared Resource Domain A collection of compartments—all of the same type—that share system resources. The compartments can be nPartitions, virtual partitions, processor sets (pSets), or Fair Share Scheduler (FSS) groups. A server containing nPartitions can be an SRD—as long as nPartition requirements are met. A server or an nPartition divided into virtual partitions can be an SRD for its virtual partition compartments.
subnet On TCP/IP networks, subnets are all systems whose IP addresses have the same prefix. For example, all systems with IP addresses that start with 10.10.10. would be part of the same subnet. system Systems on the network that communicate through TCP/IP. To manage a system, some type of management protocol (for example, SNMP, or WBEM) must be present on the system. Examples of systems include servers, workstations, desktops, portables, routers, switches, hubs, and gateways.
system status panel The section of the GUI on the left of the screen that displays status information and system or event alarms. system type One of 12 supplied types. You can add your own based on one of these types. For example, use Server type to create MyServer type. It is still a server and is reported on in the same way, but it has your designation.
user group A group of users defined on the CMS operating system that has been added to HP SIM. Members of the user group in the operating system can sign-in to HP SIM. user rights user A user who cannot configure the CMS. However, the user can view and run predefined reports on the CMS and all managed systems. V HP VCA log A listing of all the software maintenance tasks completed by the HP VCA and reports resulting from those tasks.
Index A about, 144, 145 default polling tasks, 192 searches, 48 storage solutions (SNMP), 127, 130 version control agent, 143 accessing automatic event handling, 56 discovery filters, 39 accessing the GUI, 16 adding SNMP rules, 200 agents, 22 All c-Class Racks collection discontinued, 169 All p-Class Racks collection discontinued, 169 all scheduled tasks task results list, 68 applying time filters, 57, 60 array controllers duplicate entries, 164 attributes cluster monitor, 139 audit log, 141 authentication
communication errors, 160 community strings, 51 complex deleting, 162 discovering, 162 System Page, 162 Configure or Repair Agents, 14 not starting, 162 Windows Vista, 162 Configure or Repair Agents task, 162 configuring, 162 fails, 162 configuring audit log, 141 Configure or Repair Agents task, 162 storage system discovery, 133 tool definition files, 141 contract and warranty default tasks, 192 status, 113, 114 system properties, 55 CPU resource, 138, 139 CPU utilization, 138 creating automatic event handl
disabling, 39 editing, 39 discovery tasks creating, 37 deleting, 37 disabling, 37 editing, 37 enabling, 37 general settings, 37 running, 37 stopping, 37 disk capacity, 138 disk resource, 138, 139 DL100 series systems identifying, 173 DL160 G5, 173 DL180 G5, 173 DMI, 185 DTMF, 185 E e-mail paging examples, 58 e-mail settings, 56 editing custom tools, 78 discovery filters, 39 discovery task, 37 tasks, 68 Emulex 1050C HBA card identified as two single port HBAs, 173 Emulex Host Bus Adapter identifying, 173 en
temperature graph, 169 HP Insight Control virtual machine management, 166 HP Insight Dynamics, 166 HP Insight Remote Support, 175 HP Insight Remote Support Pack contract and warranty status, 113, 114 default tasks, 192 system properties, 55 HP Logical Server, 166 HP Network-attached Storage systems discovering, 173 HP ProLiant SNMP Agent, 169 HP ProLiant Support Pack, 173 HP ProLiant WBEM Providers, 178 HP Serviceguard package, 166 HP SIM installation errors, 175 upgrading, 181 HP Smart Update Manager, 171
events, 56 hosts files, 37 licenses, 118 SSH keys, 14 Matrix infrastructure orchestration discovering, 169 McDATA 4Gb SAN Switch for HP BladeSystem associating with enclosure, 169 MIB, 200 internet management, 185 rules, 200 vendor, 185 mib, 176 Microsoft Windows 2008 MSCS cluster, 166 ML370 G5 server, 169 modem settings, 56 monitoring health, 14 Mozilla, 175, 181 response time, 160 MSA custom tools, 201 MSA G3 health status, 169 MSCS clusters, 136 MSCS cluster services discovery, 166 MSCS resource, 139 MSD
thresholds, 138 response time, 160 ROM BIOS, 181 RPM Package Manager tools no longer work, 180 rules SNMP, 200 System Type Manager, 200 running custom tools, 78 discovery task, 37 events task, 61 S saving collections, 61 scheduling clear events task, 61 custom tools, 78 event tasks, 61 tasks, 68 search, 19 search criteria, 190 searching advanced, 48 basic, 48 hierarchical displays, 48 security, 14, 179 role-based, 14 security alerts, 16 server protocols, 187 server connections increase size, 160 setting up
system monitoring resume, 54 suspend, 54 system page, 131, 185, 190 protocols, 187 system properties examples, 55 set for multiple systems, 55 system resource, 139 system status, 180 system status panel, 19 system tab protocols, 187 system table view page, 48, 69, 131, 190 overview, 50 System Type Manager SNMP rules, 200 systems deleting, 50 Systems Insight Manager collections, 71 T target selection troubleshooting, 180 task instance, 68 task results viewing, 61, 69 tasks, 14 collections, 71 command line,
X XP P500 WBEM indications, 183 xw25p Blade Workstation identifying, 169 234 Index
