HP Systems Insight Manager 6.
© Copyright 2010, 2011 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...............................................................................................14 1 About this document.............................................................................15 User Guide.......................................................................................................................15 Systems Insight Manager User Guide layout..........................................................................15 2 Product overview.....................
Credentials..........................................................................................32 Example XML file to add more than 10 WBEM username and password pairs...........................32 5 WMI Mapper Proxy .............................................................................34 6 Discovery............................................................................................35 Recommended discovery tasks..........................................................................
Example of setting system properties.....................................................................................52 Setting customer company and contact information individually...........................................52 Example of setting system properties for multiple systems.........................................................52 13 Event management..............................................................................54 Event management configuration.................................
Run Now/Schedule.......................................................................................................80 Delete..........................................................................................................................80 Creating custom tools through the Systems Insight Manager CLI...............................................80 Creating a custom SSA tool............................................................................................80 Example Web launch tool....
User accounts and authentication....................................................................................98 File system....................................................................................................................98 Background processes...................................................................................................98 Windows Cygwin.........................................................................................................98 HP-UX and Linux....
About SMI-S...............................................................................................................121 Key components..........................................................................................................121 CIM......................................................................................................................121 WBEM..................................................................................................................121 SLP............
27 HP Version Control and Systems Insight Manager..................................135 About the Version Control Agent........................................................................................135 Additional resources....................................................................................................135 About the Version Control Repository Manager...............................................................136 About integration..................................................
Installation...........................................................................................................................164 License Manager..................................................................................................................166 Locale.................................................................................................................................166 Managed Environment..................................................................................
Check Event Configuration.....................................................................................................183 Status polling.......................................................................................................................183 F Host file extensions.................................................................................184 Default values......................................................................................................................
Tables 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 28 29 30 31 32 33 34 35 36 Status types.....................................................................................................................17 Health status types...........................................................................................................49 Software status types........................................................................................................
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 Creating a task to delete all cleared events..........................................................................60 Creating the Software Distributor tool.................................................................................80 Adding a TDEF to Systems Insight Manager.........................................................................85 Removing a TDEF from Systems Insight Manager.........
Part I Introduction
1 About this document User Guide HP Systems Insight Manager provides this user guide to help you understand management features. Systems Insight Manager User Guide layout • Introduction Describes the features, basic concepts, and using the graphical user interface (GUI) in Systems Insight Manager.
2 Product overview Systems Insight Manager 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.
address ranges, or to control the frequency that each task runs. Use discovery filters to prevent discovery of unwanted system types. Inventory Data collection gathers data that can be used for reporting and to populate various fields in the user interface. Systems Insight Manager collects various information such as system type and sub-type, supported protocols, and available memory.
Tools can be run from the Systems Insight Manager menus and can be added to a Quick Launch list that is available from many pages within Systems Insight Manager. Collections Collections are groups of systems and events that can be used for viewing information, or as a way to specify the targets for a tool. They can be created through the Customize link in the System and Event Collections panel either by selecting specific systems to be included, or by specifying attributes to be matched.
to Systems Insight Manager, SMH, Integrated Lights-Out (iLO), Onboard Administrator, and all web servers you browse to. Each time you receive an Untrusted Connection warning in Firefox, you must add a permanent security exception to avoid seeing the warning again for that host. Note that if you browse to a single system using its short host name, fully qualified Domain Name Service (FQDN), and IP address (for example, three different ways), you must add three security exceptions.
Configuring the browser • Supported in Internet Explorer 7 and Firefox. Internet Explorer 6 is not supported. • The browsing system must be remote; browsing locally from the CMS does not perform automatic sign-in. • The browsing system and the CMS must be members of the same Windows domain. • You must be logged in to the browsing system with a domain account that is configured as a user account in Systems Insight Manager, or is a member of a user group configured in Systems Insight Manager.
If automatic sign-in is configured, you can manually sign in to Systems Insight Manager. • If automatic sign-in fails, the manual sign-in page appears This might occur if you are logged in to the operating system using an account that is not an Systems Insight Manager account. • If automatic sign-in is not attempted This might occur if the browser is not properly configured for automatic sign-in, or the feature is disabled in Systems Insight Manager.
times, you can collapse it by clicking the minus sign ( ) in the top right corner of the panel. To expand the panel, click the plus sign ( ). 4. System and Event Collections panel System and event collections enable you to view all known systems and events in a specific management environment. A collection can be private, visible only to its creator, or shared, visible to all users. All default collections are shared. You can add additional collections by clicking the Customize link.
Part II Setting up Systems Insight Manager
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 Systems Insight Manager software. Setting up Windows servers to be managed by Systems Insight Manager To be fully managed by Systems Insight Manager, HP ProLiant servers running Windows should have the Insight Management Agents or HP WBEM Providers installed. These agents are part of the ProLiant Support Pack.
4. On a. b. c. d. the Enter Windows credentials page, complete the following: In the User name field, enter the Windows administrator user name for the target system. In the Password field, enter the administrator password. In the Password (Verify) field, re-enter the Windows administrator password. In the Domain field, enter the Windows domain. This field can be left blank if the system is not part of a domain.
• Product Name. Displays the name of the product. • Trusted?. Displays whether the system trust relationship has been configured. To configure a trust relationship, click configure. This section displays systems authorized by the current user name. If the current user is not authorized to view the systems, a message appears, indicating that the user does not have authorization rights on the system. 7. Under Select a Support Pack to Install, select a support pack to install.
Setting up HP-UX servers to be managed by Systems Insight Manager 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 Systems Insight Manager functionality to operate.
Manually setting up an HP-UX managed system Although chapters 4-7 explain how to finish configuring managed systems from the Systems Insight Manager 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 32) and Chapter 6 “Discovery” (page 35). 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.
line for Linux systems. You do need to first supply credentials and discover the systems, as described in chapters 4 and 6. Then you can do the following actions from the command line, if desired. 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.
4. Edit the snmpd.conf file. For Red Hat Linux, open the following file in the vi editor: vi /etc/snmp/snmpd.conf For SuSE SLES 8, open the following file in the vi editor: vi /usr/share/snmp/snmpd.conf a. Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS: trapsink IPaddress where IPaddress is the IP address of the CMS. b.
4 Credentials In Systems Insight Manager, credentials are used to enable the CMS to communicate with managed systems, through WBEM, WS-MAN, SSH, and SNMP. However, the Sign-in credential is used unless you configure the other protocols. The Sign-in credential is protocol independent and can be tied to systems through the discovery credential. In Systems Insight Manager, 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 Systems Insight Manager 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 Systems Insight Manager when Systems Insight Manager 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 Systems Insight Manager. Systems Insight Manager can automatically discover and identify systems attached to the network using information from management protocols such as SNMP, WMI, WBEM, SSH, and SSL. Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs.
NOTE: If discovery tasks are run out of order, errors are likely. Typical errors due to running discovery tasks in an improper order include: • Association errors For example, a server not associated with a management processor or virtual machine not associated with a virtual machine host.
• Run a discovery task Select the task you want to run and click Run Now. When a task is running, the Run Now button changes to a Stop button. • Stop a discovery task from running Select the running task and click Stop. See the HP Systems Insight Manager online help for more information on each of these options. Discovery credentials One of the best ways to configure credentials for your managed systems is to do so as part of a discovery task. You can enter one or more sets of credentials.
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.
In addition, you must enter administrator level user credentials for the target system. 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 Systems Insight Manager performs when an event is received. Users who want to access this feature must have administrative rights. • Managing Tasks Enables you to view definitions, copy tasks, edit tasks, view task results, disable or enable tasks, or delete existing Automatic Event Handling tasks. • Creating a New Task Enables you to create a new Automatic Event Handling task.
Example automatic event handling tasks Systems Insight Manager 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.
9 Users and Authorizations Systems Insight Manager 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 Systems Insight Manager 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 Systems Insight Manager 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 Systems Insight Manager cascading menu structure, and tool descriptions. For additional information, see the Systems Insight Manager online help.
12 Monitoring systems Viewing system collections In Systems Insight Manager monitoring systems involves Systems Insight Manager polling HP Insight Management Agents 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 Systems Insight Manager.
status icon and software status icon. The System Status section contains more information on the system status. You can access the System Page one of the following ways: • ◦ Select Tools→System Information→System Page, and then select a target system. ◦ Click the system name in the System Name column on the system table view page.
Table 2 Health status types Status icon Status type Description Critical Systems Insight Manager can no longer communicate with the system. The system was previously discovered but cannot be pinged. The system might be down, powered off, or no longer accessible on the network because of network problems. Major A major problem exists with this system that should be addressed immediately. For systems running Insight Management Agents, a component has failed.
Table 3 Software status types (continued) Status icon Status type Description Informational The CMS could not reach the HP Version Control Agent on the system, so the status of the system is unknown. Unknown The VCA cannot communicate with HP Version Control Repository Manager (VCRM). The Unknown status appears for server systems only under the following circumstances: • The VCA is not installed on the managed server.
Table 4 WBEM operational status (continued) Status icon Status type Description In service, Stopped The element is suspended. • In Service indicates that the element is being configured. • Stopped indicates that element is stopped. Unknown, No contact No management information about the element could be obtained. • Unknown indicates that the element status is not available. • No Contact indicates that the element exists, but Systems Insight Manager has never been able to communicate with it.
The Suspend or Resume Monitoring tool enables you to suspend monitoring of a single system or multiple systems, which enables systems to be excluded from status polling, identification, data collection, and the automatic event handling features of Systems Insight Manager. The available suspend lengths include the predetermined increments of 5 minutes, 15 minutes, 1 hour, 2 hours, 4 hours, 8 hours, 1 day, 2 days, 3 days, 4 days, 5 days, 6 days, and 7 days. You can turn on the suspend tool indefinitely.
as a property for the target systems. If the value of the selected property is blank, that property is not set for the systems All properties are optional. NOTE: This tool can be used for a single system. However, some of the properties that are available from the System Page are not available when selecting this option. For example, the serial number is not available here, whereas it is available from the System Page.
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 Systems Insight Manager 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.
in improper cooling of the drives in the storage system due to air flow changes caused by the missing side panel. 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. 58 In the Search panel, click Advanced Search. The Advanced Search page appears.
20. 21. 22. 23. 24. 25. 26. 27. task. Enabling this option creates a system reachable event whenever the system is reachable again. Click OK to apply changes. To create the task, select Options→Events→Automatic Event Handling→New Task. The Automatic Event Handling - New Task page appears. On the Step 1, Select name page, enter a name for the task in the Task name box, such as Send E-mail for Critical Status. Click Next. The Step 2, Select event collection page appears.
The following task has the following segments: • Creating an event collection that contains the events you want to delete • Creating and scheduling the task to delete all cleared server events and run the task Procedure 12 Creating a task to delete all cleared events 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. In the Search panel, click Advanced Search. The Advanced Search page appears. Select events from the Search for dropdown list.
14 Reporting in Systems Insight Manager Standard reports Standard reports are shipped with Systems Insight Manager. 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 Systems Insight Manager is installed and configured. Standard reports are tied to existing systems collections in Systems Insight Manager, for instance, All Systems or All Servers.
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 Systems Insight Manager enables you to copy report configurations from an existing report configuration. You can edit the newly copied configurations to create a new report.
The Reports by Product table displays reports for Systems Insight Manager by default. Only products that have been registered with Systems Insight Manager have Predefined reports displayed. Table 5 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 Systems Insight Manager for reports.
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. • Bar • Pie • Line (Trend) The Include Chart section dynamically changes to display the selection items that are required to create the corresponding report. Depending on the type of chart selected, additional details are presented as follows.
15 Systems Insight Manager 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.
• Modify a task • 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 Systems Insight Manager 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.
Part IV Systems Insight Manager advanced features
16 Collections in Systems Insight Manager Collections in Systems Insight Manager Systems and events are grouped into collections based on information from the Systems Insight Manager 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 HP Systems Insight Manager online help. Types of collections • By member When you create a collection, you can select exactly which specific systems or collections you want to include. From the, Customize Collections page, click New. The New Collection section appears. Select Choose members individually.
Because collections by attribute use a database query, collections that are complex take more system resources every time they are accessed. Keeping collections simple minimizes performance impact. • Combination collections Combination collections enable you to bind together a system collection and an event collection and to reuse and recombine system and event collections that you have created. NOTE: There are two kinds of combination collections.
set properties on members of these collections. Setting properties on systems that might not be part of the collection in the future would be of very limited value. • Edit Any collection can be edited. However, collections cannot change type. For example, you can change the criteria for a collection that is defined by attribute, but you cannot change the collection type so the collection is a collection by member or a combination collection.
There are two instances of SystemC in the view of the hierarchy because CollectionC is the same throughout the application. Any place that CollectionC is referenced, it will always contain the same systems. However, SystemD appears only under CollectionB. CollectionB and Copy of CollectionB are distinct and independent collections. • Move Move enables you to easily move a collection exactly where you want it in the hierarchy.
to run with a certain collection, and that collection is made not visible, then the task will not run on that collection. You can change the visibility setting at any time. ◦ Status Displayed property You can set the Status Displayed property to enable you to easily view the aggregate status of a particular collection in the System and Event Collections panel. You can set this property only on individual systems or on collections by attribute, for example, the lowest displaying collection aggregate status.
• – Unknown – Informational Default View property When you select a collection in the System and Event Collections panel, the contents of that collection are displayed in the workspace. By default, different types of collections are displayed in different ways. Collections by attribute and combination collections default to a table view, but they can also be displayed as icons or a tree. Collections by members default to a tree view, but they can also be displayed as icons or a table.
17 Systems Insight Manager 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 7 Tool types Name Description Single-system-aware command tool OR Remote Tool in the An SSA tool executes on a selected target and is only GUI aware of the target system environment. In executing an SSA tool, the Systems Insight Manager Distributed Task Facility (DTF) of the 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.
• 2, Warning • 3, Minor • 4, Major • 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.
Then, RELATEDDEVICENAME0=DeviceName0 RELATEDDEVICENAME1=DeviceName1 RELATEDDEVICEIP%d. The IP address of the associated system, where %d is the iteration number. For example: 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.
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. If the end of the repetition clause is reached and no %z parameter is encountered, the selection index and current election are automatically incremented to avoid an infinite loop during the substitution phase.
Run Now/Schedule Use to run the tool immediately or to schedule the tool to run (if the tool can be scheduled). If the tool can be run, the schedule a task page appears. You can schedule when and how often the tool runs. Delete Use to delete a tool. Deleting a tool removes it from the Manage Custom Tools page and from the system. If a tool is dependent on a task, an alert appears with the list of tasks associated with the tool.
NOTE: Your text editor must be able create a text-only file with no embedded formatting. 4. Following the leading XML version and tool-list tags, type the tool name tag of to define the type and name of the tool. The revision string is used to keep track of different versions of the tool as will be seen later.
9. To finish the TDEF, enter the final tool list tag as shown below. The fully composed TDEF for a SSA copy tool to deploy the HP Security Patch to a managed node and then execute, should display as follows: 10. Save the file. HP recommends using a file name that indicates its function, in this case,DeployHPSecurityPatchv.1.xml Make sure that the file name ends with the .XML extension. Note that file names on Linux and HP-UX operating systems are case-sensitive.
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. If the element is true, it will be associated with the Toolboxes under Systems Insight Manager User and Authorization. This allows a trusted user to disable the tool in the Toolbox if the value is false. This tool launches in a separate browser window using the "target-frame" of WJAFrame.
NOTE: When the XWindows tool is launched, the system running the browser must be running an XWindows server for the tool's GUI to be visible. For more information about specific MSA tool requirements and attributes, see “MSA-specific attributes” (page 189). Example Enabling Remote Desktop tool Remote Desktop is a Microsoft feature that enables you to remotely access any Windows 2003 server.
Adding a TDEF to Systems Insight Manager After you create a custom TDEF, to function, you must add it into Systems Insight Manager. Add a TDEF to Systems Insight Manager using the mxtool -a command, as described in the following procedures: Procedure 14 Adding a TDEF to Systems Insight Manager 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 191). 2.
NOTE: If a task or task results are tied to a tool, by default the tool cannot be removed. The -x force option is used in this case. 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.
18 Federated CMS Search Select Reports→Federated Search.... Federated CMS Search is a web-based Systems Insight Manager plug-in that allows you to search quickly across a number of HP Systems Insight Manager CMS systems. Federated CMS 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.
NOTE: Any time communication with a secondary CMS is initiated, the certificate returned must already be installed. 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.
19 CMS reconfigure tools The CMS reconfigure tools feature provides a set of commands that enable you to quickly make common reconfiguration changes to Systems Insight Manager. 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 Systems Insight Manager partner services are stopped in preparation. 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. Stored credentials in Systems Insight Manager for accessing the CMS are also updated.
2. Update the gwlmdb.properties file by executing the following command from the command prompt: vseinitconfig -a 3. 4. Open a 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. For example: C:\Program Files\HP\Operations Orchestration\Central\tools>change-db-props.bat Administrator 5. 6. 7. Restart the RSCentral Windows service.
2. Enter the following, and then press Enter: > mxreconfig -m host 3. Follow the prompts that appear to complete the host name and IP address change. 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. Warning Verify that all Systems Insight Manager operations are complate before running this command.
Dependencies All of the following must be true: • Systems Insight Manager is installed and configured on a Windows operating system host, using Microsoft SQL. • All credentials are know. • The database credentials provided by the user during this command are valid for the CMS database. Reconfiguring the CMS to use a different database Use the mxreconfig —m sqlredirect command to reconfigure the CMS to use a different database.
20 Understanding Systems Insight Manager security This chapter provides an overview of the security features available in the Systems Insight Manager framework. Systems Insight Manager runs on a CMS and communicates with managed systems using various protocols. You can browse to the CMS or directly to the managed system. Securing communication Secure Sockets Layer (SSL) SSL is an industry-standard protocol for securing communications across the Internet.
In Systems Insight Manager, the Privilege Elevation feature enables tools to be run against HP-UX, Linux, and ESX managed systems by first signing in as a non-root user, and then requesting privilege elevation to run root-level tools. This can be configured under Options→Security→Privilege Elevation. WBEM All WBEM access is over HTTPS for security. Systems Insight Manager is configured with a user name and password for WBEM agent access.
SSH keys An SSH key-pair is generated during initial configuration. The CMS public key is copied to the managed system using the mxagentconfig tool. This key-pair is not the same as for SSL and requires a manual process to regenerate a new pair. See the manpages or online documentation for mxagentconfig for more details. See the Secure Shell (SSH) in HP SIM white paper located at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.
• Host name mismatch> If the name in the certificate does not match the name in the browser, you might get this warning. This can be resolved by browsing using the system's name as it appears in the certificate, for example, marketing1.ca.hp.com or marketing1. The Systems Insight Manager certificate supports multiple names to help alleviate this problem. See the “System link format” (page 97) section below for information on changing the format of names created in links by Systems Insight Manager.
Operating-system dependencies User accounts and authentication Systems Insight Manager accounts are authenticated against the CMS host operating system. Any operating system features that affect user authentication affect signing into Systems Insight Manager. The operating system of the CMS can implement a lock-out policy to disable an account after a specified number of invalid sign in attempts. Additionally, an account can be manually disabled in the Microsoft Windows domain.
Systems Insight Manager database Access to the database server should be restricted to protect Systems Insight Manager data. Specify appropriate non-blank passwords for all database accounts, including the system administrator (sa) account for SQL Server. Changes to the operating data, such as authorizations, tasks, and collection information, can affect the operation of Systems Insight Manager.
Configuring the CMS • Inspect SSL server certificate and update if desired • Configure passwords and SNMP community strings (See the “Configuring managed systems” (page 100) section below) • Configure user accounts, based on operating system accounts that will access Systems Insight Manager • Review and configure toolboxes if defaults are not appropriate • Review and configure authorizations for users • Configure system link configuration format • Review audit log Strong security NOTE: How-to
How to: lockdown versus ease of use on Windows systems Moderate The Insight Management Agents should be configured to trust by certificate. This requires distributing the Systems Insight Manager certificate, which includes the public key, to all the managed systems. After the systems have been configured to trust the Systems Insight Manager system, they will accept secure commands from that particular system only.
Procedure 23 Setting security to strong 1. Generate certificates from your certificate server for each managed system and the Systems Insight Manager system. To do this, first generate a certificate signing request (CSR) from the various systems. This generates a PKCS#7 file. This file should then be taken to the certificate server and signed, and then the resulting file (generally a PKCS#10 response) should be imported into the each managed system and the Systems Insight Manager system.
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 Systems Insight Manager, a privilege elevation utility such as su, sudo, or Powerbroker must be installed on the managed system.
22 Contract and warranty The Contract and Warranty Status is available when you have a Windows CMS, and the HP Insight Remote Support Pack is installed. You can view Contract and Warranty status updates for HP systems that have contract and warranty data collection enabled. Click the Contract and Warranty Status icon to view the Contract and Warranty Details page for the system.
NOTE: If you receive an incorrect response for a particular HP brand system after clicking the CW icon on the system table view page, there might be an entitlement issue with the system. This is not a Remote Support or an Systems Insight Manager issue. Please contact HP support. You must have a valid serial number, product ID, and any contract or Care Pack numbers that are applicable.
Contract • CCRN (Customer Contract Reference Number). The reference used for the contract as renewed over time. • Active Contract This value is true if an active contract exists. • Start Date The start date of an active contract. • 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.
Warranty • Warranty Type The type of warranty, for example, Base Warranty, Bundled Warranty, or HP Care Pack. • Start Date The start date of an active warranty. • Extension The number of days that this warranty has been extended.
◦ – B: Delivery blocked – C: Cancelled Service Level The level of service specified in the warranty. This includes the amount of time HP has to react to an issue, the time to resolution for a set of issues, and the type of response HP will use to react to an issue. ◦ Deliverables A description of services offered with this warranty, for example, onsite support or parts and materials.
23 License Manager License Manager enables you to view and manage product licenses within the Systems Insight Manager user interface. To access additional information about Updates, Upgrades, and Technical support, contact your HP services or HP partner representative or access the IT Resource Center (ETC) at www.itrc.hp.com.
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 10 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 11 License types reported by management processor products (continued) License Type Description Permanent Offers full, unlimited functionality. Demo (time) Offers full, unlimited functionality for a limited time. The license determines the number of days the key allows 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 use for up to 65,535 days.
License Collection Results table 1 2 3 4 • System Name. The names of the systems where the task was executed. 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.
NOTE: This displays if the system is of a different type such as; a switch, a printer, a cluster, a complex, or a system not running a Windows OS. K. Cannot collect keys stored on this node. Systems Insight Manager host and specified system must be running Microsoft Windows. NOTE: This happens when, for example CMS or a remote system is not running a Windows variant operating system. L. License Manager does not know how to assign licenses for this product.
For management processor targets: • When a license is assigned to a management processor, a license record is created and stored in the License Manager database. • If the selected management processor is already licensed, you cannot replace that license with a new license from License Manager. You must first delete the existing license at the management processor console and then insert the new license (directly or using License Manger).
1 Product The name of the product. 2 License Version The license version of the product. 3 Licenses Type The type of license for example, Demo, Beta, Duration, Site, and Maintenance. 4 Licenses Purchased The number of licenses purchased for a product. 5 Days Max The maximum number of days the licenses can be used. 6 Back Returns to the Add License page. 7 Add Licenses Now Adds the keys to the database.
7 System IP Address The IP Address of the licensed system. 8 All Features Supported A 'Yes' or 'No' value. Systems can be licensed with a bundle license. The Yes in this column implies that all products licensed by bundle license fully support the system indicated. No, indicates that some licenses do not support this system. You must determine which products do not support the selected system.
1 System license status System 15.146.233.1 displays the status as having a assigned duration license. 2 Licenses currently available Displays that the Duration license has been reduced by the number of licenses assigned to system 15.146.233.1.
24 Storage integration using SMI-S About storage systems Storage systems are SAN-attached Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters). Systems Insight Manager uses WBEM SMI-S providers to discover and collect data from storage systems. To view the latest information about Systems Insight Manager device support and for information about obtaining and installing SMI-S providers, see http://www.hp.com/go/hpsim/providers .
• Receive storage system events and associate them with the system that generated the event (through Command View) running on a system, or from a tape library management card. • Context launch appropriate management application from the context of the event or the context of the system running the Command View that generated the event.
• • 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 Systems Insight Manager The Storage Management Initiative Specification (SMI-S) is a Storage Networking Industry Association (SNIA) standard that enables interoperable management for storage networks and storage devices.
SLP SLP enables computers and other devices to find services in a LAN without prior configuration. SLP is designed to scale from small, unmanaged networks to large enterprise networks. Profiles SMI-S is organized around profiles, which describe objects relevant for a class of storage subsystem. SMI-S includes profiles for arrays, Fibre Channel HBAs, Fibre Channel switches, and tape libraries. Other storage devices (for example, NAS heads) are expected to be added in the future.
Systems Insight Manager 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.
5. At the bottom of the dialog box, click Add. The SNMP Service Configuration dialog box appears. 6. Enter the host name or IP address of the enterprise management station, and then click Add. The SNMP trap destination is added. 7. Click OK to save the changes and close the dialog box. Configuring the SNMP trap destination on Windows 2000 Procedure 25 Configuring the SNMP trap destination on Windows 2000 1. Select Start→Settings→Control Panel→Network→Services→SNMP Service.
Discovery The Systems Insight Manager discovery process for systems running Command View includes the following: • CV XP on port 80 (http) • CV VA/SDM on port 4096 (http) • CV TL on port 4095 (http) • Discovery of Command View EVA is encapsulated within the discovery of the HP StorageWorks Storage Management Appliance on ports 2301 or 2381 Systems Insight Manager must be permitted to access the web server. NOTE: To access the links to Command View, select Tools→System Information→System Page→Links.
2. 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. Viewing individual storage systems Procedure 30 Viewing individual storage systems 1. 2. 3. In the System and Event Collections panel, expand Systems, Shared, Systems by Type, and Storage Systems. Expand the storage system collection that contains the system you want to view.
• Storage Ports—All Storage Hosts Lists port information for all storage host HBAs. • Storage Ports—All Storage Switches Lists port information for all storage switches. • Changer Devices—All Tape Libraries Lists the name, firmware version, and status for all tape libraries. • Media Access Devices—All Tape Libraries Lists the name, firmware version, and status for all tape libraries.
25 Managing MSCS clusters Cluster Monitor is a core component of Systems Insight Manager, and adds the ability to monitor and manage multi-node clusters. Cluster Monitor also manages multiple cluster platforms in a heterogeneous environment. Procedure 32 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 12 Cluster fields Name Description Name Name or alias for the cluster Status Status of the cluster: Normal (the cluster condition is functioning normally, every node condition and resource condition is normal), Degraded (the cluster condition is degraded if at least one node condition is failed or degraded or at least one resource condition is degraded), Failed (the cluster condition is failed if every node condition is failed or at least one resource condition is failed), and Othe
Resource fields Table 15 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 Systems Insight Manager Systems Insight Manager supports the following Cluster Monitor resources: • Disk and CPU resources Monitor disk capacity and CPU utilization, respectively.
Adjust the CPU polling rate by configuring the Cluster Monitor node resource settings. Disk polling rate The Disk polling rate determines how often Cluster Monitor checks the free disk space as reported by the appropriate Insight Management Agents 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.
26 Systems Insight Manager Audit log Systems Insight Manager logs all tasks performed by all Systems Insight Manager users on all systems. The information is stored in the Audit Log file on the CMS. Several features of the Systems Insight Manager Audit Log are configurable. For example, you can specify which tools log data and the maximum Audit Log file size. The Systems Insight Manager Audit Log is configured through the log.
Example audit log Example Audit Log: User "partner" from CMS cup12.hp.com runs tool "ls" on cup11.hp.com from cup12.hp.com 104611: 2008-04-24 11:17:45 PDT,JOB,PROGRESS,START,JOB,44641_cup12.hp.com,VERBOSE,partner,,, Running Tool:ls Expanded Command Line:ls Targets: cup11.hp.com 104612: 2008-04-24 11:17:45 PDT,JOB,PROGRESS,START,JOB,44641_cup12.hp.com:cup11.hp.com, DETAIL,partner,,, Running Tool:ls 104613: 2008-04-24 11:17:45 PDT,JOB,SUCCESS,DONE,JOB,44641_cup12.hp.com:cup11.hp.
27 HP Version Control and Systems Insight Manager About the Version Control Agent The VCA is an Insight Management Agent installed on a system that enables you to view HP software and firmware installed on the system. You can configure: VCA to point to a repository managed by VCRM, enabling easy version comparison and software updates from the repository to the system where VCA is installed. VCA provides version control and system update capabilities for a single HP system.
About the Version Control Repository Manager VCRM is an Insight Management Agent that manages a directory of HP software and firmware components. You can use VCRM without VCA to provide a listing of available software and firmware to load on the local machine. VCRM is part of the HP Foundation Pack. VCRM is designed to be used in a one-to-many configuration with a VCA installed on each managed HP system to manage installed HP software and firmware.
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 VCRM. • It must be managed by VCRM. After a repository is created, it must be populated with ProLiant Support Packs and components before being updated on target HP systems.
28 Compiling and customizing MIBs Systems Insight Manager; provides the capability of managing systems through SNMP and by receiving incoming SNMP trap events. Systems Insight Manager ships with many MIBs pre-configured. For a complete list, see “Out-of-the-box MIB support in Systems Insight Manager” (page 199).
mcompile The mcompile tool verifies the syntax of all MIBs to be loaded into the system. mcompile resolves all MIB dependencies and, where necessary, converts SNMP v2 MIBs into v1 format for loading into the Systems Insight Manager database. mcompile is located in the \lbin directory and should be run from the \mibs directory. mcompile looks for all MIB files in the \mibs directory by default so any MIB that you intend to register should be copied to the \mibs directory.
FROM RFC1213-MIB hpSwitchBladeType2-Mgmt FROM HP-SWITCH-PL-MIB agSlotNumber FROM BLADETYPE2-SWITCH-MIB ipCurCfgGwIndex FROM BLADETYPE2-NETWORK-MIB 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.
and the full CFG filename must be listed on individual lines. Each line in the file is processed as it would be by running the mxmib -a command individually on each individual MIB file. • -l lists all the MIBs registered in Systems Insight Manager. Supplying no arguments to mxmib defaults to running mxmib -l. • -t lists the traps in the specified MIB . • -d unregisters a MIB, , from the Systems Insight Manager database. The initial command to register the file uses the .
• MAJOR Events of this type indicate an impending failure. • CRITICAL Events of this type indicate a failure and signal the need for immediate attention. --#ENABLE The ENABLE flag can be set to TRUE or FALSE and can effectively enable or disable a trap from being processed by Systems Insight Manager. The usage for the keyword is either TRUE to indicate that the trap should be processed or FALSE to indicate that this trap should not be processed.
• ProLiant Rack Events • ProLiant Remote Management Events • ProLiant Storage Events • ProLiant System and Environmental Events • ProLiant UPS Events • RFC 1215 SNMP Trap Events • SAN Appliance Events • Server Net Events • ServiceGuard Events • STORAGE • SWCC Events • 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 Syste
Table 16 Varbind keywords and descriptions Keyword Description Comments $VnV#Some text# Includes value for varbind and descriptive text (in this case, Some text#) Label will reflect the value selected. This will vary on a trap-to-trap basis. $VnD#Some text# Includes the varbind description that Label will reflect the valve selected. This is only available within Systems Insight will vary on a trap-to-trap basis.
Drive Status: FAILED Serial Number: WS7000134715 Using the $Hdr keyword in conjunction with $! to further customize the display could be as follows: --#MSG_FORMATTER "$! $Hdr#The # $V1V#system # $Hdr#had the following # $V3V#Drive Status:# $Hdr#. The system Serial Number # $V9V#is # $Hdr#.#" The e-mail or pager output would be: The system Cronus had the following Drive Status: failed.
A Important Notes System and object names must be unique System and object names must be unique in Systems Insight Manager. 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 Systems Insight Manager. 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.
Insight Remote Support Advanced compatibility IMPORTANT: If a version prior to A.05.40 of Insight Remote Support Advanced is installed, you must update it to version A.05.40 or higher to preserve configuration information and avoid some manual configuration steps. The latest version of Insight Remote Support Advanced is available at: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do? productNumber=RSADVANCED.
mxglobalsettings -s ANNOTATION_SIGN_IN_PAGE_HTML=alwayson.company.com mxglobalsettings -s "ANNOTATION_BANNER_HTML=- alwayson.company.com" mxglobalsettings -s "ANNOTATION_BROWSER_TITLE_TEXT=- alwayson.company.com" Security bulletins HP software products contain multiple third-party components, such as OpenSSL. HP discloses that the non-HP owned software components listed in the HP Systems Insight Manager end user license agreement (EULA) are included with HP Systems Insight Manager.
How to check RPM signatures within the sysmgmt.bin To check RPM signatures in the sysmgmt.bin before installing Systems Insight Manager, complete the following procedure: chmod +x sysmgmt.bin ./sysmgmt.bin --keep --confirm (and type y to extract the archive and n to execute ./mxbundle.server.postinstall) This creates a temporary directory. For example, makeself-32350-20091024210345, is where the Systems Insight Manager RPMs will be located.
On a Windows NT 4.0 system running Internet Explorer 6 Service Pack 1, remotely browsing into a CMS causes a DLL failure after being connected for hours. This issue occurs on a Windows CMS and on an HP-UX CMS. Complex systems displaying inconsistency with the number of nPars within the complex When viewing the complex through the System Page or Report, the number of nPars represent the total number of nPars that can potentially be in the complex, regardless of the state of the individual nPars.
B Troubleshooting Authentication On a Linux or ESX system, you might receive the following error when running the mxagentconfig command or through Configure or Repair Agents: Configuration failed to complete due to the following exception: Could not access the file or directory sshd_config.orig on the target system esxhost1. Remote system reported following error message: Permission denied. Check whether the directory or file exists or whether the user has the operating system permission to access it.
------------------------------------------------------------When browsing to Systems Insight Manager using Microsoft Internet Explorer 6.0.3790.0 on Windows 2003, the billboard in lower corner of the Home page is blank. 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.
5. Be sure the primary DNS suffix is set correctly. If not, set it, and click OK until all dialog boxes are closed. • The proxy settings on the client browser is configured to proxy local systems. HP recommends the following workaround: 1. In Internet Explorer, select Tools→Internet Options→Connections→LAN Settings and then select Use a proxy server for your LAN. 2. Click Advanced. 3. Add the DNS suffix for the CMS to the Exceptions list. 4. Click OK until all dialog boxes are closed.
servers. A double dense blade contains 2 servers per blade: an A and a B server.
Systems Insight Manager might report duplicate entries for array controllers if the data is collected using both WBEM and SNMP protocols on a HP Insight Management WBEM Providers for Windows Server 2003/2008 target. Solution: To see the correct data in report, you can perform data collection by disabling one of the protocols. You can also access SMH to see the correct number of array controllers.
On Windows: C:\program files\hp\systems insight manager\ config\identification The folders listed above are the default folders and should be used unless you have changed the installation folder location. • You might have failed to set up and specify appropriate WMI Mapper proxy servers. • You might have failed to specify appropriate WBEM credentials.
Solution: Remove all systems associated with the MSCS cluster (this includes the cluster alias, the cluster nodes, and any VMs that might be running on the cluster), and then re-discover the cluster (and any VMs) without discovering the service. For example, add the IP address of the cluster service to the ping exclusion range on the general discovery settings page.
Solution: If you want Systems Insight Manager to display the same name as the host name of the full DNS name, you must use the modify command to modify it. ------------------------------------------------------------If an iLO or Onboard Administrator was discovered prior to enabling/configuring Single Sign-on (SSO), re-identification is required for SSO communication to work between Systems Insight Manager and the iLO/OA.
To solve this issue: 1. Stop the SNMP daemon. 2. Add the following line to the /etc/snmp/snmpd.conf file: rocommunity public 3. Restart SNMP. Event When you subscribe for WBEM events from either the command line (mxwbemsub) or the GUI (Options→Events→Subscribe to WBEM Events), you might receive the error message String index out of range. 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.
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. If the restore operation exceeds 4 minutes on Onboard Administrator, a message appears stating that the save/restore operation could not be completed, however, the operation does complete.
HP Insight Control virtual machine management After you have selected the Install Linux PSP or ESX agents and Register VM host options in a Configure or Repair Agents task for ESX 3.5 U4 or later, the VM-host registration task fails because the system shows as Not Responding in Vcenter. Vcenter takes about five minutes for a system to reach a Normal status and therefore fails when Systems Insight Manager tries to register the VM host.
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.
• 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.
Unable to identify ESX 3.x classic servers to have the appropriate system types and subtypes, or no virtual machines can be discovered from the ESX 3.x hosts. Symptoms: • The host is not identified correctly in Systems Insight Manager with the type Server and subtype as VMware ESX Host, Virtual Machine Host • The host is discovered correctly in Systems Insight Manager with the appropriate types and subtypes. However, no guests are discovered. The Vman page shows the host, but no guests.
nsswitch.conf to resolve hostnames, and having dns resolve before files (/etc/hosts) will give the wrong IP Address for localhost. The default for HP-UX is set as: hosts: dns [NOTFOUND=return] nis [NOTFOUND=return] files To resolve this issue, change the configuration to: hosts: files dns [NOTFOUND=return] nis NOTFOUND=return] files Also, be sure the /etc/hosts file contains the loopback entry: 127.0.0.1 localhost loopback.
During a custom Systems Insight Manager installation, Insight Remote Support lays down core components and then runs a configuration. If you cancel the configuration after Insight Remote Support core components are completely installed, but before the configuration is complete, subsequent Systems Insight Manager installations will not reinstall Insight Remote Support. Solution: You must configure Insight Remote Support by clicking Start→Programs→Insight Remote Support→Initialize Insight Remote Support.
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 Systems Insight Manager Traps with same name. Change the loading of MIBs. The IF-MIB.mib is loaded first and then the RFC1215.mib. The IF-MIB.mib will be listed in mibcore.list and rfc1215 in preload.list. By doing this the LinkUp and linkDown traps from IF-mib.
Ports used by Systems Insight Manager. By default, Systems Insight Manager uses sport 5989 to communicate with the WBEM server of the systems it monitors. To use a different port for this purpose, complete the following: 1. The wbemportlist.xml file used by Systems Insight Manager must be altered to add the additional or alternate WBEM port to be used. The file is located in C:\Program Files\ HP\Systems Insight Manager\Config\Identification.
Insight Manager Installdir>/config/globalsettings.props file or by running the CLI command: mxglobalsettings --a EnhancedReportsLogicalFonts= where font name can be Dialog or SansSerif. The default value is Dialog. Security If Systems Insight Manager is installed after SMH is installed, the SMH 2048-bit key pair is replaced with the Systems Insight Manager 1,024-bit key pair.
clog_windows.xml 3. Add the tools again using mxtool -a -f 4. Run the tool. ------------------------------------------------------------If a user is created with the operator template, then the user is automatically given authorizations to run any CMS tool created with the Run as option set to root/Administrator. Solution: To avoid granting users access to CMS tools, when creating new users, the operator template must not be used and authorization must be configured separately.
3. 4. 5. 6. 7. Upgrade the agents and WMI providers on the servers that will be used for virtual identifiers. (See the version table below for proper versions). Upgrade the firmware for the Onboard Administrator to version 2.25 or later. On the virtual connect Ethernet module, upgrade the virtual connect firmware to version 1.3 or later. Do not enable virtual identifiers at this time. On the virtual connect Ethernet module, enable virtual identifiers.
WMI Mapper 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, Systems Insight Manager will no longer receive indications from the managed system.
C Protocols used by Systems Insight Manager Systems Insight Manager uses many different management protocol standards. This capability enables Systems Insight Manager to provide management support for a wide array of manageable systems. SNMP The Internet Engineering Task Force (IETF), the standards-rating body for the worldwide Internet, has defined a management protocol, SNMP, which has accumulated a major share of the market and has the support of over 20,000 different products.
NOTE: Systems Insight Manager does not receive traps from the application using port 162 unless the application is configured to forward traps to the port assigned to Systems Insight Manager. NOTE: If the SnmpTrapPortAddress entry is deleted, Systems Insight Manager defaults to port 162. Systems Insight Manager attempts SNMP communications based on the number of SNMP retries you specify and only stops when the communication is successful or the number of retries is exceeded.
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. When a system is turned off, the Magic Packet — capable network interface card (NIC) is still powered on and monitoring traffic.
Management standard Description Functionality when enabled ICMP ICMP is a required protocol tightly Provides system reachability (ping) integrated with IP. ICMP messages are check during system discovery and delivered in IP packets and are used before other operations for out-of-band messages related to network operation. Systems Insight Manager can use ICMP messages to ping a managed system. However, some routers block ICMP messages so Systems Insight Manager provides an alternative ping using TCP.
Management standard Description Functionality when enabled WS-Management A DMTF standard for exchanging Identification, inventory, and events management information using web services. You can use WS-Management to transport CIM as an alternative to CIM-XML. WMI WMI is Microsoft's implementation of Identification, inventory, and events WBEM. WMI runs over Distributed Component Object Model (DCOM), which in turn, uses RPC.
D Data Collection After Systems Insight Manager 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 Systems Insight Manager, you can set new data collection tasks targeting specific managed systems. To create a Data Collection task from the toolbar, select Options→Data Collection.
been collected by selecting it from the system table view page. This action displays the System Page, where you can select the Tools & Links tab and then click Data Collection Report .
E Default system tasks Polling tasks track the health status of systems in associated collections. Hardware status polling must occur periodically to determine when systems go offline or when hardware degrades. You can customize polling tasks for specific systems to run at scheduled times. You can also create polling tasks with different collections to meet your needs. You can configure polling tasks to take place based on the receipt of an event. Event polling tasks are associated with event collections.
NOTE: If you discover more than 500 systems, HP suggests you change the interval to something greater than 10 minutes (for example, 15 minutes for every 1,000 systems). • This task collects status information for SNMP, or WBEM systems that are Server, Cluster, or Management Processor types. By default, this task polls every 5 minutes and at start-up.
Old Noisy Events Includes events that are transient and happen frequently, but do not generally indicate hardware failures. For example, link up, link down, and authentication events. These events fill the event database tables, but do not add value to the hardware event history. Events Older Than 90 Days This task deletes events older than 90 days and can help maintain Systems Insight Manager 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 Systems Insight Manager. 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.
F Host file extensions Hosts files are used during discovery to manually add multiple systems to the Systems Insight Manager 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.
# # # # Title: Systems in database 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 21 Hosts file default parameters (continued) Keyword Value Description SNMP_RET 0 System default (Default) Greater than 0 SNMP_MON Public Read only (Default) SNMP_CON No default To use a hosts file to specify systems for an automatic discovery, add the hosts file name to the Ping inclusion ranges, system (hosts) names, templates, and/or hosts files section of the Discovery page under the Configure general settings section.
G System Type Manager rules System Type Manager enables you to extend Systems Insight Manager's SNMP-based discovery so that it is able to identify new types of systems. You do this by creating a System Type Manager rule that maps a System Object ID (OID), and optionally an additional MIB variable, to the desired type. Manufacturers assign unique System OIDs to their SNMP-instrumented products. Systems supply information about themselves using variables described in files called MIBs.
H Custom tool definition files Custom tool definition files are XML files that describe how Systems Insight Manager should run tasks based on a program, script, or UTL added by the user. This appendix describes the wuyntax of these tool definition files (tdef). Tool type-specific requirements SSA-specific attributes An SSA tool executes on a selected target and is only aware of the target system environment.
Table 23 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 191). This element may have two attributes: command-type and log.
Table 24 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 26 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 Systems Insight Manager 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 28 Multiple selected target parameters (not supported for Custom Command Tools) 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 29 Task Wizard names values (continued) Names values Description PageIndex By default, the task wizard displays the target selection page as the first page during task creation. When a tool defines its own custom parameter pages, they may instruct the task wizard where to place the target selection page. n = value starting at 1. TargetSelection lockTargetSelection A tool may wish to show the target selection page without allowing the user to change the target.
Table 31 All tools values (continued) Names values Description Menu-sort-key String. Integer sort key used to sort among the other menu items in the group. The lower the number, the earlier the item appears in the menu. If a group of menus consists of menus without sort keys, then those without keys are sorted alphabetically and put at the end Trail-blazer A trailblazer is a definition used only to establish the presence of cascades in the menu system and to apply a sorting order to them.
Table 33 Tool filtering attributes (continued) Filter name Description DeviceSubtype Long list: Bring up the Options menu, then select Discovery and then Identification. Select Manage System Types to see the list. Protocol Acceptable values are as follows (see text below for version details) SNMP: 1.0 WBEM: 1.1 SMH: 1.0 or 2.0 (This is the HP System Management Homepage running on a device) SSH: The OSRevision and Protocol Support node attributes have values that are interpreted as version numbers.
Table 34 Environment Variables (continued) Names values Description NoticeQueryName Displays the event list that generated the event.
Table 35 New Command Line Tool parameter entry guidelines Parameter field Data entry required? Parameter string assignment Entry guidelines Tool name Yes %1 As when using the CLI, the name of the new tool should be descriptive of the tool's function. Tool command Yes %2 This is the new command used to call the tool, and it may include parameters. Prompt No %3 If the Tool command includes the %1 parameter, then this field entry is required to specify the destination prompt.
I Out-of-the-box MIB support in Systems Insight Manager The following table represents the key MIBs that ship with Systems Insight Manager. Those MIBs that are marked as preloaded are registered as part of every Systems Insight Manager 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 36 MIBs supported in Systems Insight Manager MIB name Supports Pre-loaded asmib.mib ARC Serve X atmf.
Table 36 MIBs supported in Systems Insight Manager (continued) MIB name Supports Pre-loaded cisco-ping.mib cisco products X 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.
Table 36 MIBs supported in Systems Insight Manager (continued) MIB name Supports Pre-loaded cpqrecov.mib HP Proliant Cluster X cpqrpm.mib HP Proliant UPS X 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.
Table 36 MIBs supported in Systems Insight Manager (continued) MIB name Supports Pre-loaded hpovsam_im.mib HP STORAGE X hpprfmib.mib HP Netserver X hpsgcluster.mib HP ServiceGuard X hpswa.mib HP Netserver X hptat.mib HP Netserver X 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.
Table 36 MIBs supported in Systems Insight Manager (continued) MIB name Supports Pre-loaded v5_3sw.mib Fibre Channel Switch X wbt3mib.mib WYSE Events X xp1024trapmib.mib Hitachi RAID450 SNMP Agent X zesa.mib ZESA X zhrm.mib ZHRM X zsmp.mib Tandem's Subsystem Control Facility (SCF) X ztmx.mib Tandem SNMP Trap Multiplexer X ztsa.
J Support and other resources Related documents Documentation and support For support, software updates, and additional information on Systems Insight Manager and other products used with Systems Insight Manager, see the following websites: • Systems Insight Manager website at http://www.hp.com/go/hpsim/ for general product information and links to software downloads, documentation, and troubleshooting information • HP Software Depot website at http://www.software.hp.
Glossary A administrative rights user A user who is authorized for the All Tools toolbox on all systems, including the CMS. This type of user has been given special privileges to administer the Systems Insight Manager 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 Systems Insight Manager software.
E enclosure A physical container for a set of server blades. It consists of a backplane that routes power and communication signals and additional hardware for cabling and thermal issues. It also hosts the CPU or server power supplies. event Information sent to certain users that something in the managed environment has changed. Events are generated from SNMP traps. Systems Insight Manager receives a trap when an important event occurs. Events are defined as: • Warning.
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. HP Systems Insight Manager database The database that stores vital information about Systems Insight Manager, including users, systems, and toolboxes.
security to HP Web-enabled System Management Software. This version is available in the ProLiant Support Pack.10 or earlier. Management Information Base The data specification for passing information using the SNMP protocol. An MIB is also a database of managed objects accessed by network management protocols. management instrumentation Agents running on systems that provide management information for HTTP, or SNMP protocols.
public key the public half of a public and private key pair. The public key can be freely distributed without fear that it can be used to impersonate the user. It can only be used for authentication in conjunction with a private key. R HP Insight Control server deployment The HP Insight Control server deployment is a multiserver deployment tool that enables IT administrators to easily deploy large numbers of servers in an unattended, automated fashion.
Secure Sockets Layer A standard protocol layer that lies between HTTP and TCP and provides privacy and message integrity between a client and server. A common usage of SSL is to provide authentication of the server, so clients can be assured they are communicating with the server it claims to be. It is application protocol independent. Secure Task Execution A feature of Systems Insight Manager that securely executes a task from a managed system.
spoofing The act of a website posing as another site to gather confidential or sensitive information, alter data transactions, or present false or misleading data. SSH client Connects to SSH servers to perform remote task execution and file copy. SSH server Listens for and services requests coming in on the proper TCP/IP port, usually port 22. status type The classification of status messages (for example, Critical, Major, Minor, Normal, Warning, and Unknown).
• Type of management protocol on the system (SNMP, WBEM, HTTP, and SSH) • Type of HP system (server, client, switch, router, and so on) • Network name of system system properties Properties can be set for a single system or for multiple systems at the same time and include options such as system name, system type, system sub-type, operating system version, asset number, contact information, and whether or not the system properties can be changed or updated by the discovery process.
• Minor. A warning condition exists that can escalate into a more serious problem. • Normal. These events are not a problem. • Informational. No attention required. This status is provided as useful information unknown status Systems Insight Manager cannot obtain management information about the system using SNMP. Although no management instrumentation information is available, the system can be pinged. It might have an invalid community string or security setting.
X Window System A cross-platform windowing system that uses the client/server model to distribute services across a network. It enables applications or tools to run on a remote computer. XML document A collection of data represented in XML.
Index A about, 136 default polling tasks, 180 searches, 45 storage solutions (SNMP), 119, 122 version control agent, 135 accessing automatic event handling, 54 discovery filters, 37 accessing the GUI, 18 adding SNMP rules, 188 agents, 24 All c-Class Racks collection discontinued, 159 All p-Class Racks collection discontinued, 159 all scheduled tasks task results list, 65 applying time filters, 55, 58 array controllers duplicate entries, 154 attributes cluster monitor, 131 audit log, 133 authentication error
communication errors, 151 community strings, 48 complex deleting, 153 discovering, 153 System Page, 153 Configure or Repair Agents, 16 Windows Vista, 153 Configure or Repair Agents task, 153 configuring, 153 fails, 153 configuring audit log, 133 Configure or Repair Agents task, 153 storage system discovery, 125 tool definition files, 133 contract and warranty default tasks, 180 status, 104, 105 system properties, 52 CPU resource, 130, 131 CPU utilization, 130 creating automatic event handling tasks, 54, 58
editing, 37 discovery tasks creating, 35 deleting, 35 disabling, 35 editing, 35 enabling, 35 general settings, 35 running, 35 stopping, 35 disk capacity, 130 disk resource, 130, 131 DL100 series systems identifying, 163 DL160 G5, 163 DL180 G5, 163 DMI, 173 DTMF, 173 server, clearing, 59 storage (SNMP), 119 storage solutions (SNMP), 123 events task running, 59 scheduling, 59 examples, 24 clearing server events, 59 command line tool parameters, 78 e-mail paging, 56 system properties, 52 web launch tool param
HP Insight Orchestration discovering, 159 HP Insight Remote Support, 164 HP Insight Remote Support Pack contract and warranty status, 104, 105 default tasks, 180 system properties, 52 HP Logical Server, 156 HP Network-attached Storage systems discovering, 163 HP ProLiant SNMP Agent, 159 HP ProLiant WBEM Providers, 168 HP Serviceguard package, 156 HP Smart Update Manager, 161 HP Storage Essentials affect on reports, 126 discovery, 35 system properties, 52 HP Systems Insight Manager collections, 68 HP Version
hosts files, 35 licenses, 109 SSH keys, 16 McDATA 4Gb SAN Switch for HP BladeSystem associating with enclosure, 159 MIB, 188 internet management, 173 rules, 188 vendor, 173 mib, 167 Microsoft Windows 2008 MSCS cluster, 156 ML370 G5 server, 159 modem settings, 54 monitoring health, 16 Mozilla, 166, 169 response time, 151 MSA custom tools, 189 MSCS clusters, 128 MSCS cluster services discovery, 156 MSCS resource, 131 MSDE, 170 installing, 164 multiple-system-aware custom tools, 189 mxagentconfig, 151, 153, 16
rules SNMP, 188 System Type Manager, 188 running custom tools, 75 discovery task, 35 events task, 59 S saving collections, 59 scheduling clear events task, 59 custom tools, 75 event tasks, 59 tasks, 65 search, 21 search criteria, 178 searching advanced, 45 basic, 45 hierarchical displays, 45 security, 16, 169 role-based, 16 security alerts, 18 server protocols, 175 server connections increase size, 151 setting up managed systems, 24 managed systems - HP-UX, 24 managed systems - Linux, 24 managed systems -
system resource, 131 system status panel, 21 system tab protocols, 175 system table view page, 45, 66, 123, 178 overview, 47 System Type Manager SNMP rules, 188 systems deleting, 47 Systems Insight Manager installation errors, 164 upgrading, 170 T task instance, 65 task results viewing, 59, 66 tasks, 16 collections, 68 command line, 169 creating, 65 Daily Identification, 154 data collection, 178 default, 180 deleting, 65 editing, 65 instance, 65 invalid characters, 169 paging, 55 polling, 180 scheduling, 6
