Systems Insight Manager 7.
© Copyright 2010, 2013 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...............................................................................................13 1 About this document.............................................................................14 User Guide.......................................................................................................................14 HP SIM User Guide layout..................................................................................................14 2 Product overview..............
Discovery filters.................................................................................................................40 Discovery of Gen8 servers..................................................................................................41 7 Manage Communications......................................................................42 Configuring the managed system software using the Configure or Repair Agents feature from the CMS...........................................................
New Enhanced reports.............................................................................................67 Editing Enhanced reports...........................................................................................67 E-mailing reports......................................................................................................67 Deleting reports........................................................................................................67 15 HP SIM tools.................
Changing the HP SIM and HP Insight Control database credentials.....................................97 Changing the database authorizations for Matrix OE and HP Operations Orchestration....97 Reconfiguring the CMS to use a different database................................................................98 Dependencies...............................................................................................................98 Warning.......................................................................
Configuring SSL for SQL Server................................................................................109 Configuration of client to enable trust........................................................................110 How to test your client connection.............................................................................110 HP SIM database property settings to enable SSL for SQL Server..................................110 SQL Server and MSDE.................................................
25 Storage integration using SMI-S..........................................................134 About storage systems......................................................................................................134 Storage integration using SNMP........................................................................................134 Storage events.................................................................................................................135 Storage inventory details...........
Example audit log............................................................................................................148 Log content.....................................................................................................................149 28 HP Version Control and HP SIM..........................................................150 About the Version Control Agent........................................................................................150 Additional resources.............
iLO.....................................................................................................................................182 Linux servers........................................................................................................................182 Enclosure table view page.....................................................................................................182 Event....................................................................................................
WBEM................................................................................................................................204 Remote Method Invocation (RMI)............................................................................................205 Remote Wake-Up.................................................................................................................205 Internet Control Message Protocol (ICMP)...............................................................................
Related documents................................................................................................................235 Documentation and support..............................................................................................235 HP SIM documentation.....................................................................................................236 Typographic conventions.......................................................................................................
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.
Basic concepts Discovery and identification HP SIM can automatically discover and identify systems attached to the network using information from management protocols such as Simple Network Management Protocol (SNMP, SNMPv3), Windows Management Instrumentation (WMI), WBEM, Secure Shell (SSH), Secure Sockets Layer (SSL), HTTP/HTTPs, and WS-MAN. Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs.
generated and e-mailed on a scheduled basis. The type of data collected depends on the management software (SNMP agents or WBEM/WMI providers) that is installed. Automatic event handling Automatic event handling enables you to define an action that HP SIM performs when an event is received. These actions can include running a program or script, forwarding the event to another management system, clearing the event, or notifying a user through e-mail or pager.
Signing in and using the graphical user interface HP SIM provides a browser-based GUI. Supported browsers include: • • For Windows: ◦ Microsoft Internet Explorer 8 or later ◦ Firefox 3.x, 6.x, 9.x, 10.x, and Firefox ESR For HP-UX: Firefox 3.5.09.00 or later To download, go to http://www.hp.com/go/firefox. • For Linux: Firefox 9 or later NOTE: Browser settings: • For all Windows Internet Explorer browsers, you must have the SSL 3.0 or Transport Layer Security (TLS) 1.
Configuring the CMS • HP SIM must be running on a Windows CMS that is a member of a Windows domain. The browsing system must be a member of the same domain. • The HP SIM service account must be a domain account; local accounts can not be used. • The CMS must be registered with an SPN in the domain, which requires a domain administrator to configure. From any system that is a member of the domain, the domain administrator can run the setspn.exe utility from the Windows Support Tools.
about:config in the Firefox address bar. From the list of Preference Names, select network.negotiate-auth.trusted-uris and either double-click or right-click, and select Modify. Here, you can specify a comma-separated list of URLs or domains, enter the list of URLs used to access HP SIM. For example: https://cms_fqdn, where cms_fqdn is the FQDN of the CMS. Behavior When automatic sign-in occurs, an intermediate sign-in page appears. If you click Cancel from this page, the manual sign-in page appears.
1. Banner area The banner provides a link to the Home page, a link to Sign Out of HP SIM, and displays the user that is currently signed in. Click the minimize icon in the top right corner to minimize the banner. To maximize the banner, click the maximize icon. 2. System Status panel This panel provides uncleared event status, system health status information, and an alarm to notify you about certain events or statuses. You can customize the System Status panel for your environment.
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.
2. 3. 4. 5. 6. 7. Select Install Agentless Management Service (AMS) on HP ProLiant Gen8 servers running Windows, Linux, or ESX to send all host operating system-specific data to the iLO4 firmware. 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.
11. Configure the target systems by selecting one of the following options: • Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or HP-UX system to send WBEM indications or events to HP SIM.
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 35) and Chapter 6 “Discovery” (page 38). 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/WMI, WS-MAN, SSH, SNMP, and SNMPv3. 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.43.212.150 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, SNMPv3, 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.
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 HP Insight Management Advisor 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. Creating a New Task Enables you to create a new Automatic Event Handling task. Select Options→Events→Automatic Event Handling→New Task.
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. In the Search panel, click Advanced Search. The Advanced Search page appears.
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.
On the Customize Collections page, some collections show their contents and others do not. For example, in the above image, All Systems, HP BladeSystems, and Storage Systems are not collections by member because the expansion icon ( ) is located beside the collection name, and when you click the icon, the contents of the collection are displayed. Because collections by attribute are dynamic, determining their content and displaying it in this interface would be very time consuming.
If CollectionB is copied to CollectionF, the hierarchy would look like the following: The new instance of CollectionB receives a new name, but its contents are copied directly. The contents, CollectionC and CollectionD, are copied by reference. Both CollectionB and Copy of CollectionB refer to the exact same instances of CollectionC and CollectionD.
• ◦ The All Systems and All Events collections cannot be deleted. ◦ After a collection is deleted, it cannot be recovered. Set Properties Collections have properties, and these properties define the way collections behave in the System and Event Collections panel and elsewhere in HP SIM. ◦ Visible property It might be the case that there are system or event collections, that are either shipped with HP SIM or are user-defined, that you do not use, but at the same time, do not want to delete.
In the System and Event Collections panel, where the status is displayed, the status will "bubble up" to the higher levels of the hierarchy (the root of the tree) so that the most urgent statuses are always visible at any level. Statuses are merged so that the most significant is always displayed. NOTE: • Statuses at the top of the following list take priority over those at the bottom.
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 Launching applications using custom tools Use custom tools in HP SIM to combine RIBCL, CPQLOCFG, and system collection to manage Group Administration of iLO systems.
You can substitute any number of selected targets by using the repeat block construct, %( ... %). Anything inside the repeat block delimiters is repeated until the selection list is exhausted, starting with the current selection and selection index. For example, https://%{deploy.server%}/deploy/deployimage.jsp? device1=%n%z%(&device%i=%n%z%) 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.
View tool definition Use to display the XML code for the tool. This tool is not enabled if you select more than one tool. 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.
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.
8. Type the following attribute element code, which states where the tool will be located in the HP SIM menu. 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.
Example Web launch tool A web launch tool launches an application requiring a URL. The example below launches the application WebJetAdmin for a device selected within the HP SIM window as long as that device is a printer. The element (in bold below) provides the URL of the managed node where WebJetAdmin is installed. The parameter %n is used to substitute the managed node hostname. The element can have a value of true or false.
For more information about specific MSA tool requirements and attributes, see “MSA-specific attributes” (page 219). 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 221). 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.
NOTE: If the SQL database associated with the CMS is installed locally (on the same server), and you have changed the host name and/or IP address, you must run mxreconfig -m sqlredirect before running mxreconfig -m host -c . Where: • -c Old name of the CMS. NOTE: If you configured sites in Matrix Recovery Management, an additional step must be applied: Run the mxreconfig -m host -c command.
used to logon to the database associated with Insight Management software must be changed, then this command must be used. Dependencies • CMS is installed and configured on a Windows operating system host, using Microsoft SQL. • All credentials are known. • The database credentials provided by the user during this command are valid for the CMS database. Warning Verify that all Insight Management software operations are complete before running this command.
NOTE: If HP Capacity Advisor Data Service is not running after executing dbauth, you must update the hosts file under Windows\System32\drivers\etc and add , where is the hostname of CMS. Be sure to save the file and restart HP Capacity Advisor Data Service if it was stopped. Reconfiguring the CMS to use a different database Use the mxreconfig —m sqlredirect -s -b -a [-p ] command to reconfigure the CMS to use a different database.
Procedure 23 Changing the database associated with the CMS 1. 2. Open a command prompt on the CMS and navigate to the install directory of HP SIM. Type the following and then press Enter. mxreconfig —m sqlredirect -s -b -a Where: • -a Name of the database user with administrative privileges, must include domain name. • -b Name of the new database. • -s Name of the new database server 3.
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) Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL), are cryptographic protocols that provide communication security.
Web agent and be configured to trust by certificate to validate the digital signature. SSL can optionally authenticate the system to HP SIM, using the system's certificate, to prevent HP SIM from inadvertently providing sensitive data to an unknown system. NOTE: For SSO to web agents, the Replicate Agent Settings and Install Software and Firmware tools each provide administrator-level access to the web agents.
higher. In the case of fresh install scenarios, the HP SIM certificate will be a 2,048-bit self-signed certificate. HP SIM SSO certificate For Single Sign-On operations, HP SIM uses SSO certificate only; this is the self-signed 1,024-bit certificate. HP SIM does not support any other third party certificate or CA-signed certificate for SSO.
Enabling or disabling certificate revocation check HP SIM enables you to disable certificate revocation check for both server and client certificates. Disabling revocation check for client certificate does not affect Two-Factor authentication, where the client certificate (called as user certificate) is always checked for revocation.
Warning or error If the certificate revocation check cannot be performed successfully, then HP SIM logs that as a warning, but it does not cease the connection with the peer system. The connection will be ceased only if HP SIM identifies the certificate as revoked. In Two-Factor authentication, if the revocation check did not succeed or if the certificate is revoked, then the user is not allowed to log-in to the CMS.
The SSH keys of the trusted systems do not expire. These keys can be removed manually from the trust store. Passwords Passwords configured on the HP SIM System Credentials and Global Credentials pages are stored in the database encrypted using 128-bit Blowfish. These passwords can be further managed using the CLI command mxnodesecurity. A few passwords might be stored in a file on the CMS that are also encrypted using the same 128-bit Blowfish key.
For WMI, the default Windows server install requires a local administrator account. However, this can be configured to allow access from any specific account. Browser SSL All communication between the browser and the CMS or any managed server occurs using HTTPS over SSL. Any navigation using HTTP (not using SSL) is automatically redirected to HTTPS. Cookies Although cookies are required to maintain a logged in session, only a session identifier is maintained in the cookie.
Browser session By default, HP SIM does not time-out a user session while the browser is displaying the HP SIM banner. This is known as monitor mode, and allows a continuous monitoring of the managed systems without any user interaction. The session times-out after 20 minutes if the browser is closed or navigates to another site. An active mode is also supported where the session times out after 20 minutes if the user does not interact with HP SIM, by clicking a menu item, link or button.
IMPORTANT: If creating operating system accounts exclusively for HP SIM accounts, give users the most limited set of operating system privileges required. Any root or administrator accounts should be properly guarded. Configure any password restrictions, lock-out policies, and so on, in the operating system. File system Access to the file system should be restricted to protect the object code of HP SIM. Inadvertent modifications to the object code can adversely affect the operation of HP SIM.
Installing a certificate on a server with Microsoft Management Consold (MMC) To use SSL encryption, you must install a certificate on the server where SQL Server is running. Complete the following steps to install the certificate by using the MMC snap-in. Procedure 24 Configuring the MMC Snap-in 1. Open the certificates snap-in: a. Open the MMC console by clicking Start→Run. The Run window opens. b. Enter MMC. c. From the Console menu, select Add/Remove Snap-in. d. Click Add, and then click Certificates.
2. Certificate requirement: For SQL Server to load an SSL certificate, the certificate must meet the following conditions: a. The certificate must be in either the local computer certificate store or the current user's certificate store. b. The current system time must be after the Valid from property of the certificate and before the Valid to property of the certificate. c. The certificate must be meant for server authentication.
a. b. c. 4. hp.Database.ssl=authenticate hp.Database.username=username hp.Database.password=password Append the following value at the end of the value set in the connection-url tab of the hpsim-ds.xml file, located in the ~/HP Systems Insight Manager/ jboss/server/ hpsim/deploy/ folder. ;ssl=authenticate 5. 6. Restart the SQL Server services. Start HP SIM. NOTE: This feature is supported only on Windows CMS with MS SQL Server as database.
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. Directory structure users Two-factor authentication is not supported for local CMS users.
Administrators can still be able to access all CLIs (such as mxuser, mxnode, and so on) when HP SIM runs on two-factor authentication mode. 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.
22 HP SIM quiesce HP SIM Quiesce is an independent entity which performs the operation of pausing and resuming the operations of HP SIM. It helps to allow in-progress tasks to complete and block new tasks from starting, so that a clean backup or export of the CMS management data can be taken. The task criticality is used during the quiesce operation, which is part of Unattended Backup. When the system is quiesced, you cannot start any new tasks, or delete or modify existing tasks.
23 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. 124 Contract and warranty Warning The contract expires in 90 days. Normal The system has a valid contract or warranty. Unknown No contract information was found.
24 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 Ctrl + C to copy it. Position the cursor in any of the five fields forming the input box and press Ctrl + V, or right-click your mouse to paste the license key. If the Add License function was selected after you copied the key, press Ctrl + 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.
25 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 .
• 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 32 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 36 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.
26 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 39 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 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 Other (the cluster condition cannot be de
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.
27 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.
28 HP Version Control and HP SIM About the Version Control Agent The HP VCA is an Insight Management Agents 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 Agents 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.
NOTE: When software/firmware for a component is not available in the baseline, then it will be shown blank. If junk or blank values are found to be listed in the Software Firmware Baselines section, it is because the description for the component is not found by the providers. You can verify this by going through the Data Collection reports. The junk values are unique identifiers for the component which do not have descriptions. The junk values are numbers in sequential order prefixed with a hyphen (-).
29 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 229).You can use tools provided by HP SIM to integrate third-party (non-HP) SNMP v1/v2/v3 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 41 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.
30 Proxy authenticator HP SIM supports user authentication against the underlying operating system as well as Light Weight Directory Access Protocol (LDAP) server (including Active Directory). However, HP SIM does not support an already existing enterprise SSO solution like Java Open Single Sign On (JOSSO), Central Authentication Service (CAS), Shibboleth, Security Assertion Markup Language (SAML) and so on.
HP SIM allows HTTP as well as HTTPS connections with the authenticator, HP highly recommends you provide support only through certificate-based authentication with the authenticator to avoid any security vulnerability that might arise in the absence of it. Settings to be made in HP SIM The following section covers various properties that can be customized to work with Proxy authenticator.
Serial Property Number (S/N) Mandatory In Override-able Via SecuritySettings.props URL parameter Default value Comments HP recommends you ensure this URL is not re-used multiple times, as it might create potential security risks. Also, HP recommends you provide a random token as part of the URL to ensure uniqueness and periodic expiry of the tokens at the authenticator. 5 proxy.auth.request.inputs Yes Yes N/A A comma separated list of URL request parameters.
Serial Property Number (S/N) Mandatory In Override-able Via SecuritySettings.props URL parameter Default value Comments authenticator connection for authentication. These values must be numeric and the value set is considered in milliseconds. 11 proxy.auth.request. No No 60000 Socket-timeout for the Proxy authenticator. These values must be numeric and the value set is considered in milliseconds.
Configuring trust check in HP SIM for Proxy authenticator server Perform the following to enable trust check with the Proxy authenticator: Procedure 42 Configuring trust check for Proxy authenticator server 1. 2. Create a keystore in a secure folder. Import certificate(s) as trusted certificate(s) in the keystore. a. If the authenticator's certificate is self-signed, import it in the keystore. b. If the authenticator's certificate is CA-signed, import only the CA certificate. c.
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. Click Turn Windows Firewall on or off.
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 recommends you use Adobe 11. Agentless Management Service HP Agentless Management Service may exhibit slow performance on SLES 10 if the latest HP iLO Channel Interface driver is not installed on HP ProLiantGen8 servers. HP recommends you upgrade SLES10 HP iLO Channel Interface driver to V1.2 or later. ------------------------------------------------------------AMS re-installation through Configure or Repair Agents on an RHEL 6.
in Onboard Administrator is refreshed. The time taken could be lesser than this at times, but 60 seconds is a conservative time interval which could be relied upon. In HP SIM 7.2, upon reception of Blade insertion trap from Onboard Administrator, rather than immediately kicking off reidentification HP SIM waits for a configurable interval of time and then initiates re identification.
Solution: Enable Play Animations in Web Pages in Internet Explorer. To access this, select Tools→Internet Options→Advanced, and then select Play Animations in Web Pages under the Multimedia section. ------------------------------------------------------------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.
1. 2. 3. 4. • In Internet Explorer, select Tools→Internet Options→Connections→LAN Settings and then select Use a proxy server for your LAN. Click Advanced. Add the DNS suffix for the CMS to the Exceptions list. 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.
------------------------------------------------------------The Remote Registry service is not started by default on the workstations like windows7 and Windows Vista. If this service is not started, then Configure or Repair Agents on these target systems will fail. To start the service, follow the steps below: Procedure 47 Starting Remote Registry service 1. Enter services.msc in run. This displays the list of services. 2.
------------------------------------------------------------HP ProLiant BL e-Class blade servers or the HP bc1000 blade PC container view is empty but the table view displays all blades correctly. Solution: This happens when the Integrated Administrator is discovered before blades are discovered. Therefore, run identification on the Integrated Administrator management processor. 1. Select Options→Identify Systems. 2. Select the ProLiant BL e-Class Integrated Administrator. 3. Click Run Now.
When the number of objects to be collected on any given storage array exceeds 1000, it is possible that data collection will fail for the array with a default timeout value of 10800 seconds. ------------------------------------------------------------After a HP SIM upgrade, the Data Collection task might fail when executed.
3. If you are unable to restart the proxy or if the Pegasus WMI Mapper was uninstalled, delete it from the CMS WMI Mapper Proxy settings found in the Options→Protocol Settings→WMI Mapper Proxy page. 4. Be sure you have at least one running Pegasus WMI Mapper Proxy configured in HP SIM. 5. Verify credentials for the systems. 6. Run identification on all systems.
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. However, if you use both methods of discovery and observe that Data Collection or WBEM subscription is failing please delete the system and run discovery again.
------------------------------------------------------------If you: • Configure an HP Serviceguard package as an HP virtual machine which is hosted by two different HP virtual machine hosts, AND • Complete a failover of the package from one HP virtual machine host to the other one, AND • Re-identify the package in HP SIM, you might find that the package is not associated with the correct HP virtual machine host.
iLO If after discovery runs, you can see the CMS, but not the iLO associated with it, check the following: • Be sure both the IP of the CMS and the iLO are discovered. • Be sure to enter the iLO credentials on the Options→Security→Credentials→Global Credentials. After setting the credentials, rerun discovery. • Run Configure or Repair Agents to be sure SNMP is configured on iLO and set correctly at the CMS.
Solution: Verify if the name of the local host resolves to a fully qualified name through DNS. The command needs the FQDN name to work properly. ------------------------------------------------------------To enable non-administrative users to delete or clear events, you can create a toolbox with the Clear Events and Delete Events tools. 1. Select Options→Security→Users and Authorizations. 2. Click the Toolboxes tab and click New 3. In the Name field, enter a name for the new toolbox. 4.
------------------------------------------------------------While restoring the Onboard Administrator configuration, initially the following message appears if the network communication to Onboard Administrator is slow. Save/Restore operation is taking more than the expected time. Please wait while the save/restore operation completes.
Insight Control virtual machine management virt fails to update the change in VM name when performed from Virtual Connect. It is observed that when a VM name is updated from vCenter that is registered on the hosts, the updated name does not reflect on the 'All Systems Page". However, the change is updated in the host system page after few minutes. For the VM name to be updated and reflected in the All Systems system list page, initiate an identification task on the host System Page.
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.
To get basic hardware data, such as model, serial number, and UUID, from non-HP x86 servers running VMware ESX Server or Linux, you must configure the root user as the Sign-in credential in HP SIM. This is because the Privilege Elevation feature is not used for identification of servers and running dmidecode requires the root privilege. In addition, to identify the VMware ESX server as the VMware ESX Host subtype, the WBEM cimserver on the ESX host must be up and working correctly.
Solution: Uncheck Simple File Sharing by navigating to Tools→Folder Options→View or set the security policy Network access: Sharing and security model for local accounts to Classic: Local users authenticate as themselves. Installation To install HP SIM, Framework 3.5 SP1 must be installed on all supported Windows systems. When installing HP SIM 7.2 on a Windows 2012 system, the correct version of Framework is installed.
c. d. e. 4. Grant the following Object Privilege to all tables and views: • INSERT • UPDATE • DELETE • SELECT Grant CREATE SESSION privilege for database user. Grant truncate privilege for: • associated_device_data • consolidatedNodeAuths Restart the HP SIM service. License Manager Collection of Lights-out 100 licenses from Lights-out 100 targets are supported beginning with in HP SIM 6.1 and deployment on LO100 targets on G6 servers with latest firmware versions.
2. Run mxtool -mf -x force' where for each TDef is as follows: iux_tools.xml swm-msa-tools.xml swm-ssa-tools-up.xml swm-ssa-tools.xml hpux\iux_tools.xml hpux\swm-msa-tools.xml HP MIBs The LinkUp and LinkDown traps in IF-MIB.mib are redundant traps; these are also present in rfc1215.mib. As per the current framework, the redundant traps are not allowed in HP SIM Traps with same name. Change the loading of MIBs. The IF-MIB.mib is loaded first and then the RFC1215.mib. The IF-MIB.
MX_JOB_KEEP_RUN_NOW_HOURS=8 Recommended value is 8 for greater than 1500 systems After the MX.PROPERTIES file has been modified, restart the HP SIM service to initiate the changes. Ping HP recommends you do not disable ping in hardware status polling tasks. If the ping protocol from hardware status polling task is disabled, then other polling protocol statuses like SNMP, WBEM, OOB, WSMAN, and so on will be affected.
Privilege elevation When “DISPLAY_LAST_LOGIN” = 1 in HP-UX, even non-interactive logins, such as used by sudo, emit the Last login string. This extraneous data in stderr/stdout can affect tools. This value can be changed using HP SMH in the Auditing and Security Attributes Configuration section of the HP SMH home page. This can be done for the user whose rights have been elevated (typically “root”) or set as the system-wide default for all users.
Sign-in User is not able to sign-in to HP SIM when HP SIM is installed on RHEL6.1 64-bit operating system. For HP SIM to work on RHEL6.1 64-bit operating system, the 32-bit library (32-bit(i686) version of PAM-level Red Hat Packager Manager (RPM)) must be installed as part of the operating system installation. This is a prerequisite for HP SIM installation. SNMP settings Configuring SNMP settings through Configure or Repair Agents displays corrupt message in task results.
When HP SIM is upgraded, you must clear the Firefox browser cache to avoid issues with the target selection wizard. Perform the following procedure to clear the cache: 1. In the Firefox browser, select Tools→Options. The Options window appears. 2. Select Advanced, and then select the Network tab. 3. Under Offline Storage, click Clear Now. 4. Click OK to close the Options window. Tasks The Initial ProLiant Support Pack Install task does not work on Windows 2000 target systems.
Upgrade After upgrade from 7.1 to 7.2 with any intermediate patches, sometimes, you cannot run Enhanced Reports due to irresponsive buttons. Workaround: 1. Delete all contents under System Insight Manager\jboss\server\hpsim\work\ jboss.web\localhost\_\org\apache\jsp\mxportal\NewReport. 2. Run Enhanced Reports. ------------------------------------------------------------When upgrading an HP SIM 6.3 Simplified Chinese system to an HP SIM 7.
for any given hardware platform, if not some serious issues, such as loss of software licenses will occur. When setting up an environment for virtual identifier support the following steps must be taken for proper operations of the management tools. 1. Upgrade HP SIM to version 5.2 Update 2 or later. 2. For any server that will have a profile with a virtual identifier, upgrade the ROM BIOS to the latest version to ensure it contains virtual identifier support.
VMware The name of the temperature sensors might be incorrect. This is a known issue in the VMWare provider and will be addressed in a future release of VMWare providers. WBEM WBEM is no longer supported on HP servers. The last servers to support WBEM were the G6 servers. Therefore, HP SIM will not identify the operating system details properly for RHEL 5.7 Xen and KVM servers. WBEM indications Current P9500 embedded SMI-S does not support WBEM indications.
If you have created subscriptions on a Windows managed system and then elect to change the WMI Mapper proxy or install a WMI Mapper on the managed system, you must first unsubscribe for WBEM events, change the proxy, re-identify the systems, and then resubscribe for WBEM events. If you do not unsubscribe for the WBEM events, HP SIM will no longer receive indications from the managed system.
C HP SIM Dynamic Ports There are three main processes in HP SIM: • mxdomainmgr • mxdtf • mxinventory These processes communicate with each other using Secure RMI connections (TCP). HP SIM does not use any specific port. It uses anonymous ports based on the underlying Java RMI implementation which uses the User ports (for example, 1024 – 49151 on Microsoft Vista, Microsoft 2008 and above operating systems). HP SIM processes use different ports on every restart.
Microsoft Windows Vista, Microsoft Windows 2008 and Above To comply with Internet Assigned Numbers Authority (IANA) recommendations, Microsoft increased the dynamic client port range for outgoing connections in Windows Vista, Windows Server 2008, and all of its later operating systems. The default port range is now 49152 through 65535. On these Operating Systems, to avoid port conflicts, HP SIM installer, as part of the installation process, sets the following ports for dynamic ports.
D 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 Simple Network Management Protocol (SNMP) is one of the standard protocols for managing devices on a network.
From a standards perspective, Microsoft SNMP supports only SNMPv1 and SNMPv2c. Microsoft doesn’t support SNMPv3 and has no plans to support it. Since the default port 162 will be used by the Microsoft SNMP Trap service, HP SIM supports an additional port 50005 which can receive all versions of SNMP trap. Thus on Microsoft Windows platform, HP SIM supports dual SNMP stack, one leveraging Microsoft SNMP Trap service another built-in Java stack.
NOTE: HP SIM does not receive traps from the application using port 162 unless the application is configured to forward traps to the port assigned to HP SIM If the SnmpTrapPortAddress entry is deleted, HP SIM defaults to port 162. HTTP HP SIM also takes advantage of the industry standard HTTP protocol (used to transfer information over the World Wide Web) for transportation of management information.
Remote Method Invocation (RMI) Java RMI is used within the CMS only for inter-process communication. Remote Wake-Up Remote Wake-Up refers to the ability to remotely turn on a system that is in a soft-off power state. Systems that support the Advanced Configuration and Power Interface (ACPI) should be awakened transparently by any network activity to the system. Alternatively, a system might support the Magic Packet technology.
Management standard Description Functionality when enabled some routers block ICMP messages so HP SIM provides an alternative ping using TCP. MIB Part of the SNMP specification, the MIB is a model of the information to be managed through SNMP. It is equivalent to the CIM defined by WBEM. System identification, inventory and events SNMP SNMP is widely used for management System identification, Inventory and but the widely implemented versions events 1 and 2 have weak security.
Management standard Description Functionality when enabled Mapper on a managed system in the secure network. This mapper allows standard CIM-XML requests through the firewall, and they are mapped to WMI requests on the managed system. Configuring protocol settings in HP SIM You can use HP SIM to set protocol settings for all systems, for a group of systems, or for an individual system.
E 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.
F 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.
G 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 24 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.
H 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.
I 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 syntax 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 26 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 221). This element may have two attributes: command-type and log.
Table 27 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 29 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 31 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 33 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.
Tool Filtering attributes Common filtering values available to use for TDEFs. Table 36 Tool filtering attributes Filter name OSName Description Acceptable values include: HPUX (no space or hyphen in the value) Linux WINNT (all windows flavors) VMware ESX OSVendor Acceptable values include: Microsoft SuSE RedHat HP OSRevision Acceptable values are as follows (see text below for version number details) (for Windows) 5.2, 6.0, 6.1 (for Linux) 3, 4, 4.1, 5.5, 10.2, 11 (for HP-UX) 11.
In addition to these "automatic" EV's, user-defined environment variables may be set as part of scripting in the TDEFs. Table 37 Environment Variables Names values Description NoticeLabel The short string type of event (like Discovered Device) NoticeState Shows whether the event has been cleared NoticePlainText Plain text description of the event and also includes whether it is set to In Progress, Cleared, or Not Cleared NoticeRawData The raw data of the event that was sent and in a string format.
Table 37 Environment Variables (continued) Names values Description Path Path variable received from the operating system (received in context of the windows service account) SystemRoot Variable received from the operating system (received in context of the windows service account) WinDIR Variable received from the operating system (received in context of the windows service account) ComputerName Variable received from the operating system (received in context of the windows service account) Tool
Table 38 New Command Line Tool parameter entry guidelines (continued) Parameter field Data entry required? Parameter string assignment Entry guidelines command and its capabilities. File path to save tool No %8 Path name of new tool. Example: /var/opt/mx/ tools/mytool.
J 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 39 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 39 MIBs supported in HP SIM (continued) 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 39 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 39 MIBs supported in HP SIM (continued) 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 39 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.
K Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service/Contact HP Uni
• If the question is related to HP Insight Remote Support (HP Insight RS), then HP SIM will be supported as it pertains in Insight RS with a Hardware Warranty or Hardware Contract • The customer purchases an HP SIM Care Pack (Part #: UR389E) Support includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for assistance in resolving software implementation or operations problems.
HP SIM documentation For more information regarding HP SIM, see the HP HP SIM Information library at http:// www.hp.com/go/insightmanagement/sim/docs for access to HP SIM manuals and release notes. Typographic conventions find(1) Book Title Linked Title http:// www.hp.com Command user input computer output Enter term variable value attrib HP-UX manpage. In this example, “find” is the manpage name and “1” is the manpage section. Title of a book or other document.
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. See the server deployment documentation for network environment setup, prerequisites for the deployment server, and installation instructions. HP Insight Control server provisioning HP Insight Control includes the rights for Insight Control server provisioning, which is a new feature replacing HP Insight Control server deployment.
and other components with other server blades. Server blades tend to be more cost-efficient, faster to deploy, and easier to adapt to growth and change than traditional rack-mounted or tower servers. 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.
storage systems SAN-attached Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters). 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.
system search Logical grouping of systems into a collection based on information in the HP SIM database. After a search is defined, you can display the results from the system view page or associate it with a management task. 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.
user A network user with a valid login on the CMS that has been added to HP SIM. user accounts Accounts used to sign-in to HP SIM. These accounts associate a local Windows user account or a domain account with privilege levels and paging attributes inside HP SIM. 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.
Index A about, 151, 152 default polling tasks, 210 searches, 49 storage solutions (SNMP), 134, 137 version control agent, 150 accessing automatic event handling, 57 discovery filters, 40 accessing the GUI, 18 adding SNMP rules, 218 Agentless Management Service AMS, 172 agents, 23 All c-Class Racks collection discontinued, 183 All p-Class Racks collection discontinued, 183 all scheduled tasks task results list, 69 applying time filters, 58, 61 array controllers duplicate entries, 177 attributes cluster monit
communicating with systems, 35 communication errors, 173 community strings, 52 complex deleting, 175 discovering, 175 System Page, 175 Configure or Repair Agents, 16 not starting, 175 Windows Vista, 175 Configure or Repair Agents task, 175 configuring, 175 fails, 175 configuring audit log, 148 Configure or Repair Agents task, 175 storage system discovery, 140 tool definition files, 148 contract and warranty default tasks, 210 status, 120, 121 system properties, 56 CPU resource, 145, 146 CPU utilization, 145
XP P9500, 179 discovery filters accessing, 40 disabling, 40 editing, 40 discovery tasks creating, 38 deleting, 38 disabling, 38 editing, 38 enabling, 38 general settings, 38 running, 38 stopping, 38 disk capacity, 145 disk resource, 145, 146 DL100 series systems identifying, 187 DL160 G5, 187 DL180 G5, 187 DMI, 202 Dotnet, 189 DTMF, 202 E e-mail paging examples, 59 e-mail settings, 57 editing custom tools, 79 discovery filters, 40 discovery task, 38 tasks, 69 Emulex 1050C HBA card identified as two single
HP Insight Control power management 24-hour graph, 183 incompatible server, 183 license, 183 temperature graph, 183 HP Insight Control virtual machine management, 179 HP Insight Dynamics, 179 HP Insight Remote Support, 189 HP Insight Remote Support Pack contract and warranty status, 120, 121 default tasks, 210 system properties, 56 HP Logical Server, 179 HP Network-attached Storage systems discovering, 187 HP ProLiant SNMP Agent, 183 HP ProLiant WBEM Providers, 193 HP Service Pack for ProLiant, 187 HP Servi
PA-RISC, 182 management protocols, 23 managing automatic event handling tasks, 57 cluster collections, 54 CMS communications, 42 custom tools, 79, 219 discovery task, 38 events, 57 hosts files, 38 licenses, 125 SSH keys, 16 Matrix infrastructure orchestration discovering, 183 McDATA 4Gb SAN Switch for HP BladeSystem associating with enclosure, 183 MIB, 218 internet management, 202 rules, 218 vendor, 202 mib, 191 Microsoft Windows 2008 MSCS cluster, 179 ML370 G5 server, 183 modem settings, 57 monitoring heal
storage array capacity, 142 storage systems, 141 views, 64 reports, 64 data collection, 16 inventory, 16 storage systems, 141 requirements GUI, 18 resources cluster monitor, 145, 146 thresholds, 145 response time, 173 ROM BIOS, 196 RPM Package Manager tools no longer work, 195 rules SNMP, 218 System Type Manager, 218 running custom tools, 79 discovery task, 38 events task, 62 S saving collections, 62 scheduling clear events task, 62 custom tools, 79 event tasks, 62 tasks, 69 search, 20 search criteria, 208
storage systems, 141 viewing, 134 viewing array capacity, 142 WBEM event indications, 140 subscribing WBEM indication events, 140 support, 235 system status, 52 WBEM status, 54 system collections customizing, 51 managing, 51 printing, 51 system key, 20 system monitoring resume, 55 suspend, 55 system page, 138, 202, 208 protocols, 205 system properties examples, 56 set for multiple systems, 56 system resource, 146 system status, 194 system status panel, 20 system tab protocols, 205 system table view page, 49
custom tools, 219 Windows managed systems, 23 Windows 2000, 195 Windows 2008, 175 Windows 2008 64-bit, 196 Windows Vista Configure or Repair Agents, 175 User Account Control features, 196 Windows XP, 196 Windows XP SP2, 175 Windows XP SP3, 191 WMI Mapper service, 198 WMI Mapper Indications service, 198 WMI Mapper proxy, 198 X XP P500 WBEM indications, 198 xw25p Blade Workstation identifying, 183 254 Index
