HP Systems Insight Manager 5.3 Technical Reference Guide

ManualsBrandsHP ManualsSoftwareHP Systems Insight Manager for HP-UX

HP Systems Insight Manager 5.3 Technical

Reference Guide

HP Part Number: 356920-402

Published: January 2009

Edition: 5.3

Summary of content (758 pages)

PAGE 1
HP Systems Insight Manager 5.3 Technical Reference Guide HP Part Number: 356920-402 Published: January 2009 Edition: 5.
PAGE 3
Table of Contents 1 Legal notices............................................................................................29 Warranty.............................................................................................................................................29 Restricted rights legend..........................................................................................................................29 Copyright notice...................................................................
PAGE 4
Configuring managed systems...........................................................................................................50 Configuring the WMI Mapper Proxy..................................................................................................51 Configuring privilege elevation on HP-UX............................................................................................51 Configuring e-mail settings................................................................................
PAGE 5
Discovery and identification.......................................................................91 Automatic discovery..............................................................................................................................91 Internet Protocol...............................................................................................................................91 Event-based automatic discovery..................................................................................
PAGE 6
Displaying the systems...............................................................................................................115 Exporting Insight Manager (WIN32) files....................................................................................115 Batch-adding systems using the CLI...................................................................................................115 Hosts file extensions..........................................................................................
PAGE 7
Command line interface............................................................................................................149 System groups...............................................................................................................................149 Managing system groups from the GUI........................................................................................149 Managing system groups from the CLI using mxngroup.........................................................
PAGE 8
Trusted certificates...............................................................................................................................180 Importing trusted certificates............................................................................................................181 Exporting trusted certificates............................................................................................................181 Exporting the system certificate from HP SIM.................................
PAGE 9
Copying event collections................................................................................................................208 Command line interface............................................................................................................208 Deleting event collections................................................................................................................209 Command line interface.........................................................................
PAGE 10
System status types.........................................................................................................................228 WBEM operational status types.......................................................................................................229 Software status types......................................................................................................................230 Cluster table view page..................................................................
PAGE 11
Hierarchical displays............................................................................................................248 Save as..............................................................................................................................249 View..................................................................................................................................249 Performing a basic search...............................................................................
PAGE 12
Discovery and identification.......................................................................................................275 Discovering storage using SNMP.....................................................................................................276 Using HP SIM with SNMP storage solutions.......................................................................................276 Viewing a storage event........................................................................................
PAGE 13
Cluster Monitor Cluster tab..............................................................................................................299 Cluster Monitor Nodes tab..............................................................................................................299 Cluster Monitor Network tab...........................................................................................................300 Cluster Monitor Resources tab.................................................................
PAGE 14
Viewing tool definition files.............................................................................................................339 Removing and restoring custom tools................................................................................................340 Removing a tool.......................................................................................................................340 Restoring a tool.................................................................................
PAGE 15
Managing Communications.................................................................................................................393 Communication status.....................................................................................................................393 Manage Communications table columns...........................................................................................394 Selection............................................................................................
PAGE 16
Installing the HP ProLiant Support Pack..............................................................................................422 System Type Manager rules.............................................................................................................422 Installing and configuring version control..........................................................................................424 HP Version Control Agent.............................................................................
PAGE 17
Entitlement Information..............................................................................................................446 Management Processor.............................................................................................................447 Host Server..............................................................................................................................447 Storage Server.......................................................................................
PAGE 18
About integration...........................................................................................................................466 About software repositories.............................................................................................................466 About multiple system management..................................................................................................467 Accessing the Version Control Agent...........................................................
PAGE 19
HP Serviceguard Manager overview................................................................................................491 Software Distributor overview..........................................................................................................492 Webmin overview..........................................................................................................................492 Workload Manager overview...........................................................................
PAGE 20
Snapshot comparison..........................................................................................................................511 System reporting.................................................................................................................................512 Running an existing report in HTML format........................................................................................512 Selecting the sort order.............................................................
PAGE 21
R_HPUXFileSystem...............................................................................................................534 R_HPUXVolumeGroup..........................................................................................................535 R_HPUXLogicalVolume.........................................................................................................535 R_HPUXPhysicalVolume........................................................................................................
PAGE 22
Creating and scheduling the task................................................................................................566 Creating a task to delete events older than 30 days...........................................................................567 Creating the collection..............................................................................................................567 Scheduling the task..............................................................................................
PAGE 23
Exporting an SSH key.....................................................................................................................600 Deleting an SSH key......................................................................................................................600 Configuring SSH bypass properties.......................................................................................................601 Audit log.................................................................................
PAGE 24
Storage system...................................................................................................................................647 Switch...............................................................................................................................................649 System...............................................................................................................................................650 System Page..............................................
PAGE 25
CIM_Process table.........................................................................................................................682 CIM_Processor table......................................................................................................................683 CIM_Product table.........................................................................................................................685 CIM_RemoteServiceAccessPoint table.....................................................
PAGE 26
HPVM_Host table..........................................................................................................................715 IPAddress table..............................................................................................................................715 IPProtocolEnd_NetworkPort table......................................................................................................715 IPXAddress table.........................................................................
PAGE 27
List of Tables 4-1 13-1 13-2 13-3 13-4 13-5 13-6 13-7 16-1 Version support matrix for components used for installation...................................................................69 Version support matrix for components used for installation...............................................................306 Supported hardware for Integrity management processor license collections.......................................367 Product License Information......................................................
PAGE 28
PAGE 29
1 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.
PAGE 30
PAGE 31
2 Introduction Online help HP SIM provides an online help system that helps you understand management features. To view the online help, click the question mark icon on any page or use the Help menu to view the online help. HP SIM help categories • Product overview • Getting started Describes procedures for how to begin using and administering HP SIM. See “Getting started” for more information.
PAGE 32
PAGE 33
3 Product overview HP SIM is the foundation for the HP unified server-storage management strategy. HP SIM is a hardware-level management product that supports multiple operating systems on HP ProLiant, Integrity and HP 9000 servers, HP StorageWorks MSA, EVA, XP arrays, and third-party arrays.
PAGE 34
Security • Role-based security HP SIM enables effective delegation of management responsibilities by giving system administrators granular control over which users can perform specific management operations on specific systems. • Manage SSH keys The SSH keys feature enables you to view and manage, from the CMS, the public SSH keys stored in the known_hosts file. The SSH keys enable the CMS to authenticate a secure connection with a managed system.
PAGE 35
The type of data collected depends on what filters are selected, or what WBEM providers are installed. • Snapshot comparisons HP SIM enables you to compare configuration snapshots of up to four different servers, or compare configuration snapshots of a single server over a period of time. You can use snapshot comparisons to save a picture of a standard configuration for comparisons to other systems.
PAGE 36
• Licensing • Manual Log Purge The PMP tools operate in conjunction with HP SIM and installs with Insight Management Agents. For more information, see http://www.hp.com/go/ice. • HP Vulnerability and Patch Management Pack HP Vulnerability and Patch Management Pack identifies and provides advice to resolve security vulnerabilities. It delivers advanced patch management through automated acquisition, optimized deployment, and continuous enforcement of security patches.
PAGE 37
• What's new? • Product architecture • Assistance • Legal notices • Getting started What's new? • Support for display of IPv6 addresses HP SIM can display IPv6 address on the System page and data collection reports for the systems that are IPv6 enabled. • Improved Linux identification HP SIM uses SSH to gather basic system hardware information.
PAGE 38
SIM software, the CMS maintains a database for storage of persistent objects that can reside locally or on a separate system. Typically, applications for the MSA tools also reside on the CMS. However, these applications are not required to reside on the CMS. They can reside anywhere on the network. Because the CMS is a system within the management environment, it manages itself as part of the domain.
PAGE 39
• HP SIM SMI-S Providers website at http://www.hp.com/go/hpsim/providers for information about device support and SMI-S providers • Videos that showcase HP SIM and the Essentials at http://h18013.www1.hp.com/products/servers/ management/hpsim/infolibrary.html • HP SIM forum at http://forums1.itrc.hp.com/service/forums/categoryhome.do?categoryId=455 for discussions about HP SIM • HP SIM tools and scripts forum at http://forums1.itrc.hp.com/service/forums/ categoryhome.
PAGE 40
PAGE 41
4 Getting started If you are getting started with HP SIM, you must first familiarize yourself with the software and set it up for your environment by reviewing the information in the “Product overview” section. Then, complete the following steps: • Sign in to the GUI. See “Signing in” for details. • Familiarize yourself with the HP SIM Home page. See “Navigating the Home page” for details. • If this is a new installation, perform the initial setup.
PAGE 42
NOTE: You must be connected to the Internet to register HP SIM. NOTE: After you upgrade or complete a fresh installation of HP SIM, you are reminded to register each time you sign in. You are reminded once per day only, and only if you have not previously registered or applied a product license. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. If the Registration window is not already open, select Options→Registration. Click Register Now. The Product selection Web page appears.
PAGE 43
Manually signing in to HP SIM There are several reasons to manually sign in to HP SIM. • If automatic sign-in fails, the sign-in page appears This might occur if the user is logged in to the operating system using an account that is not an HP SIM 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 HP SIM.
PAGE 44
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 HP SIM, or is a member of a user group configured in HP SIM.
PAGE 45
credentials to a rogue system disguised as your HP SIM system, or you might import a certificate from a rogue system disguised as your HP SIM system and give your sign-in credentials to that rogue system. If your browser is not configured with the SSL system certificate of the HP SIM system, a security alert regarding a certificate of untrusted origin might appear when first browsing to HP SIM using SSL.
PAGE 46
Logging in remotely using an SSH client 1. 2. Open an SSH client application on any network client. Log in to the CMS through the SSH client software, using a valid user name and password. HP SIM grants authorizations based on your operating system user login. Related topics • Getting started • Signing out • Using command line interface commands • Networking and security Signing out Be sure to sign out from HP SIM to prevent unauthorized access to your active session while you are away.
PAGE 47
NOTE: The default settings in Firefox block the First Time Wizard. You must disable the pop-up blocker in Firefox to see the First Time Wizard. The First Time Wizard includes the following options: • Introduction Describes the purpose of the First Time Wizard. You can cancel the First Time Wizard and disable the wizard from automatically starting when an administrative user signs in. • Managed Environment Specifies all operating systems managed by the CMS.
PAGE 48
• Performing initial setup • Administering systems and events • Protocols • Data collection • Discovery and identification • Events • About administering events Configuring the managed environment From this page, select the operating systems that the CMS will manage. There are four options: Windows, Linux, HP-UX, and Other. The selections made here configure HP SIM to hide collections, tools, and reports for operating systems you do not manage.
PAGE 49
1. 2. 3. 4. Select Run discovery once after wizard finishes to have the System Automatic Discovery task run immediately after First Time Wizard finishes. To schedule the task to run at a specific time, select Schedule. To configure the System Automatic Discovery task to run on a regular schedule, enter how often the task should run. The default frequency is once per day. If you clear the Automatically execute discovery every option, the task is disabled after it is created.
PAGE 50
• Configuring managed systems • Configuring the WMI Mapper Proxy • Configuring privilege elevation on HP-UX • Configuring e-mail settings • Configuring automatic discovery Related topics • Using the First Time Wizard • Operating-system-specific collections, reports, and tools • Discovery and identification • Configuring automatic discovery general settings • Configuring HP SIM with storage systems Configuring managed systems The Configure Managed Systems page in the First Time Wizard ena
PAGE 51
6. 7. Select Set trust relationship to "Trust by Certificate" to set a trust relationship between managed systems and the CMS. This enables HP SIM users to connect to HP SMH, Onboard Administrator, iLO (version 2 and later), and HP VCA using the HP SIM certificate for authentication. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous.
PAGE 52
1. To configure privilege elevation for ESX systems, select Enable privilege elevation for VMware ESX. To configure privilege elevation for Linux and HP-UX systems, select Enable privilege elevation for Linux & HP-UX. 2. Select the elevation tool type from the menu. If a password is required for the tool, select A password is required for this privilege elevation tool. 3. 4. 5. (Optional) Edit the Privilege elevation tool command.
PAGE 53
NOTE: If you did not enter a valid SMTP host, HP SIM display an error message: The email could not be sent: Could not connect to the SMTP host. NOTE: If the Server Requires Authentication option is selected, and you enter incorrect account information, an The email could not be sent: Authentication error message displays.
PAGE 54
• Finishing the First Time Wizard • Performing initial setup • Administering systems and events • Protocols • Data collection • Discovery and identification • Events • About administering events Finishing the First Time Wizard When you click Finish in the First Time Wizard, the Finish page appears with a message stating Your settings are being applied, please do not close the window. For HP-UX systems, TDEF files are updated and the minor version of HP-UX tools is upgraded.
PAGE 55
• Events • About administering events Operating-system-specific collections, reports, and tools Operating-system-specific collections The following collections are removed if the associated operating system is not selected on the Managed Environment page of the First Time Wizard or from the Managed Environment page in the HP SIM UI (Options→Managed Environment).
PAGE 56
The following reports have no data for HP-UX and are removed if HP-UX is the only selection.
PAGE 57
• Configuring the WMI Mapper Proxy • Configuring privilege elevation on HP-UX • Configuring e-mail settings • Configuring HP SIM with storage systems Related topics • First Time Wizard summary • Finishing the First Time Wizard Setting up managed systems Overview Setting up managed systems involves installing the required Management Agents software and configuring the supported protocols to communicate with the HP SIM software.
PAGE 58
Setting up Linux managed systems manually 1. Install and configure SSH. a. 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. b. On the CMS, copy the SSH-generated public key from the CMS to the managed system, and place it in the authorized keys file of the execute-as user (root or administrator).
PAGE 59
4. 5. Sign in to the HP SIM GUI. See “Signing in” for assistance. Add the default WBEM user name and password to the Global Protocol Settings page in the HP SIM GUI. Note: An account for at least one of the WBEM user name and password combinations must exist on each managed system. Note: You can perform this step once for all managed systems. a. b. c. Select Options→Protocol Settings→Global Protocol Settings.
PAGE 60
For the latest WBEM Services bundle, go to http://www.hp.com/go/hpsim/providers. 2. Ensure the managed system software is installed. To verify that the minimum required software is installed, log in to the remote system, and run the following command: $ swlist –l bundle T1471AA B8465BA OpenSSL To verify that the optional providers and HP System Management Homepage are installed, run commands such as: $ swlist –l bundle LVMProvider WBEMP-LAN-00 SysMgmtWeb SysFaultMgmt OnlineDiag 3.
PAGE 61
5. The Step 3: Configure or Repair Agents page enables you to select options to configure the target system. • Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or HP-UX system to send WBEM indications or events to HP SIM.
PAGE 62
NOTE: This indication will appear as an Informational Event in the Event List of HP SIM. If you do not receive test WBEM indications in the Event List, see “Troubleshooting”. NOTE: This indication is supported only on HP-UX and Windows managed systems with WBEM provider installed. • Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to manage the system This option deploys a WBEM certificate to the managed system and is only valid for HP-UX systems.
PAGE 63
HP-UX systems do not require a Read Write community string. The Read Write community string is added on Windows systems only. b. c. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems SNMP Trap Destination List. This setting enables the target systems to send SNMP traps to this instance of HP SIM.
PAGE 64
• Configure Version Control Agent (VCA) Select this option to configure the HP VCA to point to the HP VCRM, where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, HP-UX, and Linux. To configure HP VCA: 1. 2. 3. 4.
PAGE 65
NOTE: This option is not available if you selected any options on the “Step 2: Install Providers and Agents (Optional)” page. • b. c. d. e. 8. In In In In Use the following credentials for all systems. the the the the User name field, enter the system administrator name. Password field, enter the system administrator password. Password (Verify) field, re-enter the system administrator password. Domain field, enter the Windows domain if you are using a domain account.
PAGE 66
i. Stop the DMI daemon on the managed system: /sbin/init.d/Dmisp stop ii. iii. Edit /var/dmi/dmiMachines by adding the host name of the CMS to the end of this file. Save the file. Start the DMI daemon: /sbin/init.d/Dmisp start e.
PAGE 67
c. From the CMS: To subscribe to WBEM Events, you must have root access. If the Global Protocol Setting does not match the managed system or does not contain root access, the subscription for WBEM Indications fails. You can verify what access WBEM has by running the following command line: mxnodesecurity –l –p wbem –n If the managed system does not have a root level user credential configured, you can add it for the individual system.
PAGE 68
NOTE: a tool. 2. 3. The Step 1: Verify Target Systems page appears if you select the targets before selecting Select target systems. For more information, see “Creating a task”. Click Next. The Step 2: Install Providers and Agents (Optional) page appears. You can install Insight Management Agents or providers, either WBEM or SNMP, on managed systems so that HP SIM can collect inventory and status information from these systems and receive event notifications from the systems.
PAGE 69
Table 4-1 Version support matrix for components used for installation Supported systems HP WBEM Provider HP ProLiant Agent OpenSSH Version Control Agent System Management Home Page Unknown 2.2.1.0 (32-bit) 8.2.0.0 (32-bit) 5.1p1-3 2.1.10.801 2.1.15.210 ProLiant systems 2.2.1.0 (32-bit) with 32-bit Windows operating system ( 2003, 2008 ) 8.2.0.0 (32-bit) 5.1p1-3 2.1.10.801 2.1.15.210 ProLiant systems 2.2.1.0 (64-bit) with 64-bit Windows operating system (2003, 2008) 8.2.0.0 (64-bit) 5.
PAGE 70
1. 2. 3. Select System type: server. Select System subtype 1: HP ProLiant. Enter operating system description as Microsoft Windows Server 2003, x64 Enterprise Edition Service Pack 1 or the correct operating system description of your system. If you want to configure the agents after installation, select the force reboot option. This allows the newly installed component to be completely initialized before you configure it. NOTE: 5. Installation with reboot typically takes about 8 minutes. Click Next.
PAGE 71
NOTE: This indication will appear as an Informational Event in the Event List of HP SIM. If you do not receive test WBEM indications in the Event List, see “Troubleshooting”. NOTE: This indication is supported only on HP-UX and Windows managed systems with WBEM provider installed. • Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to manage the system This option deploys a WBEM certificate to the managed system and is only valid for HP-UX systems.
PAGE 72
HP-UX systems do not require a Read Write community string. The Read Write community string is added on Windows systems only. b. c. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems SNMP Trap Destination List. This setting enables the target systems to send SNMP traps to this instance of HP SIM.
PAGE 73
• Configure Version Control Agent (VCA) Select this option to configure the HP VCA to point to the HP VCRM, where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, HP-UX, and Linux. To configure HP VCA: 1. 2. 3. 4.
PAGE 74
a. Select one of the following options: • Use sign-in credentials. These credentials must be a privileged account on the managed system. NOTE: This option is not available if you selected any options on the “Step 2: Install Providers and Agents (Optional)” page. • b. c. d. e. 9. In In In In Use the following credentials for all systems. the the the the User name field, enter the system administrator name. Password field, enter the system administrator password.
PAGE 75
5. control, see HP Version Control Installation Guide at http://h18013.www1.hp.com/products/servers/ management/agents/documentation.html. Run the Configure or Repair Agents feature. For more information, see “Configuring the managed system software using the Configure or Repair Agents feature from the CMS”. Performing initial setup The initial setup involves setting up managed systems, configuring discovery, configuring event handling, adding users, and defining authorizations.
PAGE 76
7. Configure paging settings You can configure paging settings so that users receive pages that notify them of certain events. See “Configuring modem settings for paging on Windows systems” for information about paging settings. 8. Set up automatic event handling Automatic event handling enables you to define an action that HP SIM performs when an event is received. You can set up automatic event handling to use the e-mail and paging settings that you specified in the previous sections.
PAGE 77
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. HP SIM ships with default shared collections only. See “Monitoring systems, clusters, and events” for information about customizing and creating new collections.
PAGE 78
• Introductory page (default) • Plug-in (if installed) page Some HP SIM partner applications use this option to point to their home page. However, if no partner application is using this, selecting this option displays the HP SIM default introductory page. • Any specific system, cluster, or event collection view The default introductory page is available only when it is set as the Home page. If you want to view this page when it is not set as your home page, reselect it as the Home page. 4. 5.
PAGE 79
as the alarm is relevant. To have the panel remain collapsed, you must clear the offending event or system status or reconfigure the status display to no longer display alarms. • Legend of status icons To display a list of status icons, click Legend in the System Status panel. Legend information appears in a separate window and remains open until you close it. See “System status types” for more information about default user templates.
PAGE 80
The following error messages might appear: • HP Systems Insight Manager is not configured to display any status. To resolve this issue, close the window, customize the display of the System Status panel, and relaunch. • This window does not have a connection with the main HP Systems Insight Manager window. To resolve this issue, close the window. NOTE: The status panel pop-up window might not appear if you have a pop-up blocker configured and running on your system.
PAGE 81
Setting the web browser language or locale When you configure your web browser and select the language you prefer, the HP SIM GUI displays the date and time in the language requested by the browser, although the overall HP SIM GUI appears in English or Japanese. The browser locale also sets the language and encoding in the Secure Shell (SSH) command shell in which the tool command executes.
PAGE 82
5. 6. 7. 8. Click Apply. Reboot the system. Open a command prompt window. Execute the chcp 932 (Japanese) and chcp 437 (English) commands to toggle between the two languages. Configuring HP-UX and Linux language settings 1. 2. Ensure that support for the desired languages and character map encodings are installed on the managed systems (for SSA tools) and execution systems (for MSA tools, usually the CMS).
PAGE 83
variable on a Linux or HP-UX system. Also, some properties define what to use for unsupported languages on each operating system.
PAGE 84
manpages Viewing manpages on UNIX systems You can use the man utility on HP-UX and Linux systems to format and display CLI command line usage manpages. Use the following format to specify a manpage to view: # man [ sectionNumber ] ManpageName . HP-UX • CLI command line usage manpages are specified as section 1M. • CLI Extensible Markup Language (XML) usage manpages are specified as section 4.
PAGE 85
Command Functionality Available manpages mxauth Enables administrative rights users to manage HP SIM authorizations. mxauth(1M, 8), mxauth(4) mxcert Creates a new certificate, imports a signed mxcert(1M, 8) or trusted certificate, removes a certificate, lists certificates, generates a certificate signing request, notes whether to require trusted certificates, upgrades certificate from HP SIM 4.x, and synchronizes public certificate with the System Management Homepage share directory.
PAGE 86
Command Functionality Available manpages mxquery Adds, lists, modifies, or removes queries in HP Systems Insight Manager. mxquery(1M, 8), mxquery(4) Note: The use of categories in mxquery has been deprecated in favor of mxcollection. Using cat works for mxquery in this release, but you should use mxcollection for creating and manipulating collections (previously known as queries).
PAGE 87
• mxquery • mxreport • mxstm • mxtask • mxtool • mxtoolbox • mxuser • mxwbemsub On a Windows CMS, if you are not a member of the local Administrators group, add the options –-user username and --pass password when running any of the listed CLI commands. For example, to list information about one or more authorizations in compact or table form, enter mxauth [-lt] ––user username ––pass password.
PAGE 88
• Getting Started with HP SIM 5.0 in a smaller Windows environment See the Getting started with HP SIM in a smaller Windows environment white paper at http:// h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html. • Installing the HP System Management Homepage individually (without using HP SIM) See the System Management Homepage Installation Guide at http://h18013.www1.hp.com/products/ servers/management/agents/documentation.html.
PAGE 89
• Technical documentation See Technical documentation at http://docs.hp.com/en/index.html. • Transitioning to HP SIM See the Migrating from Compaq Insight Manager (WIN32) to HP SIM white paper at http:// h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html. • Understanding HP SIM Security See the Understanding HP SIM 5.3 security white paper at http://h18013.www1.hp.com/products/ servers/management/hpsim/infolibrary.html.
PAGE 90
PAGE 91
5 Discovery and identification Discovery is the process of finding systems in the management domain so that they can be managed from the CMS by HP SIM. You can perform discovery only if you have administrative rights. Automatic discovery The process that HP SIM uses to find and identify systems on your network and populate the database with that information. A system must first be discovered to collect data and track system health status.
PAGE 92
NOTE: With the exception of the SNMP Authentication Failure trap, all traps trigger an automatic discovery. First discovery You can start a discovery in the following ways: • Execute discovery immediately from the Discovery page, select the System Automatic Discovery task, click Edit to configure the task for your environment, and then click Run Now. The discovery process starts immediately. The discovery progress is updated as the systems are discovered, until the discovery process is complete.
PAGE 93
• Specify the WBEM settings for the system on the System Protocol Settings page. You can override the default user name and passwords by selecting use values specified below and entering appropriate user names and passwords. • Specify the SNMP settings for this system to be unique or match the global discovery settings. The current system default settings appear. If you override the default and specify a different value, that community string must be supported on the system.
PAGE 94
Configuring automatic discovery When you access the Discovery page, a table displays a list of all available discovery tasks. You can configure multiple instances of discovery with each instance having its own schedule and set of inclusion ranges. When a discovery task is executed, the Last Run column is updated to display its progress, including the percentage of completion.
PAGE 95
• View HP Storage Essentials discovery status When you install HP Storage Essentials, its discovery status appears with a link to the HP Storage Essentials discovery log. • Configure HP Storage Essentials global application settings When you install HP Storage Essentials, the Discovery page includes a link to the HP Storage Essentials global application settings configuration page.
PAGE 96
a. b. c. d. 4. 5. 6. To set system credentials, click Credentials. See “Configuring credentials for discovery tasks” for more information. To create an associated Configure or Repair Agents task, click Configure/Repair. See “Configuring Configure or Repair Agents for discovery tasks” for more information. To configure system types, click System Types. See “Configuring system types for discovery tasks” for more information. NOTE: 7. (Required) In the Name field, enter a name for the task.
PAGE 97
Sign-in credentials For a single system: 1. 2. 3. Enter the user name and password. To use other credentials if the assigned credentials fail, check If these credentials fail, try other credentials that may apply. Click the Learn more link for additional information. By default this box is not selected, unless you have upgraded HP SIM. Click OK. For groups of systems: 1. Enter as many default user names and passwords as needed by clicking Add.
PAGE 98
For groups of systems: 1. Enter as many default user names and passwords as needed by clicking Add. To delete user name and password pairs, click Delete beside the pair you want to delete. If you selected to delete a user name and password pair for a group of systems, select how you want to delete them. Select from the following: 2. 3.
PAGE 99
a. b. c. d. e. f. 2. Select Configure newly managed systems when they are first discovered.. To specify credentials to configure the managed system for WBEM / WMI, SNMP, and SSH, select from the following: • Use the sign in credentials already entered in HP SIM administrative privileges. • Use these credentials Select this option to use another user name and password pair other than the one entered into HP SIM.
PAGE 100
Editing a discovery task 1. 2. 3. Select Options→Discovery. The Discovery page appears with the Automatic tab selected. Select the task to be edited and then click Edit. The Edit Discovery section appears. Select from the following: • Discover a group of systems a. b. c. (Default) Select this option to discover more than one system. (Required) In the Name field, enter a name for the task. In the Schedule section, select Automatically execute discovery every, and then enter how often the task runs.
PAGE 101
Related procedures • Discovery and identification • IP ranges Disabling or enabling an existing discovery task You can disable or enable an existing discovery task. If you disable a task, the Schedule column displays a message that the task is disabled. You might want to disable a task if you know your network is not going to change, or if you want to limit network traffic. If a task is enabled, the Schedule column displays the schedule for the task.
PAGE 102
Running a discovery task You can manually select and run any existing discovery task at any time. For example, if you add a new system that has not been discovered, you can manually run a discovery task to discover and manage the system. You can also stop a task that is running. 1. 2. Select Options→Discovery. The Discovery page appears. Select the discovery task that you want to run, and then click Run Now. The task runs immediately. The Run Now button changes to Stop when a task is running.
PAGE 103
• Management Processor Usually a small firmware-based system that is embedded in a server or other server-related hardware (such as an enclosure), and typically provide only management capabilities. The iLO card is an example of a management processor. • Notebook • Partition Certain systems and operating environments can be flexibly configured into partitions, each of which can run a separate instance of the operating system.
PAGE 104
• In Windows NT and Windows 2000, one community name on the system must be set to Read Create. You are not required to use this community string in HP SIM (a community string set to Read is all that is required). The Management Agents connect to themselves using Simple Network Management Protocol and require one string set to Read Create. • The HP SIM system must be allowed to make SNMP requests to the managed systems. Ensure that the SNMP security settings are not preventing these requests.
PAGE 105
HP ProLiant BL p-Class C-GbE2 Interconnect Integrated Lights-Out Switch y Integrated Lights-Out 2 (iLO 2) Proliant BL e-Class Integrated Administrator BladeSystem c7000 Onboard Administrator HP ProLiant BL1000 HP ProLiant BL1500 HP ProLiant BL2000 HP ProLiant BL2500 ProLiant BL 10e ProLiant BL 10e G2 HP ProLiant BL1000 HP BladeSystem e-Class/CCI Storage devices discovered by HP SIM For information on the prerequisites for these systems, go to http://h18006.www1.hp.com/storage/ smisproviders.html.
PAGE 106
HDS Array 9200 9920-E 9500V 9960 9970V 9980V StorageWorks EVA 4000 6000 8000 4100 6100 8100 Network Appliance NAS Netapp FASxxx StorageWorks NAS DL310-SS DL380G4-SS DL58x-SS ML310-SS ML35x-SS ML370-SS NAS 2xxx/4xxx/9xxx Fibre Channel 394757-B21 and 394588-B21 (Mezzanine) A5158A A6795A A6826A A7298A A7387A A7388A A9782A A9784A FCA2101 FCA2214 FCA2214DC FCA2355 FCA2404 (AB232A FCA2404DC FCA2408 A7538A A7560A AB378A AB379A AB465A AB466A AB467A FC1142 (AE311A) FC1242
PAGE 107
download from the openPegasus website does not include the hardware specific data for HP SIM to manage Linux x86 systems. NOTE: WMI is the implementation of WBEM from Microsoft. See WMI for more information. To install the HP Insight Management WBEM Provider from the Manage Communications page, select Quick Repair→Install Providers and Agents→Install WBEM/WMI Provider (HP Insight Management WBEM Provider) for Windows. NOTE: The WBEM providers cannot be installed on HP-UX or Linux systems.
PAGE 108
• Desktop Management Interface (DMI) An industry-standard protocol, primarily used in client management, established by the Desktop Management Task Force (DMTF). DMI provides an efficient means of reporting client system problems. DMI-compliant computers can send status information to a central management system over a network. For HP-UX and Linux-based systems, you can download DMI from the HP Software Depot (http:// www.software.hp.com/).
PAGE 109
1. From the HP-UX managed system, run /ect/opt/resmon/lbin/send_test_event monitor name . For example, /etc/opt/resmon/lbin/send_test_event disk_em. Possible monitor names: 2. 3. • dm_memory • lpmc_em • disk_em • dm_chassis • dm_core_hw • ia64_corehw • fpl_em Confirm that the test indication is shown in the HP SIM event table view after you trigger it.
PAGE 110
• Automatically discover VM guest(s) when the host is identified. This option adds all VM guest systems to the HP SIM database when the a VM host (HPVM VMWare ESX or Microsoft Hyper-V) system is discovered and identified. This option is selected by default. If this option is not selected when a VMWare ESX or Microsoft Hyper-V host is discovered, then guests are not discovered automatically.
PAGE 111
Discovery filters Discovery filters prevent or enable certain system types from being added to the database through automatic discovery. When you want to discover systems of a certain type, using filters is much easier than specifying the IP addresses of each individual system. Discovery filters do not apply to manually added systems. You can access discovery filters in one of the following ways: • From the Discovery page, select Options→Discovery.
PAGE 112
Related procedures • Creating a new hosts file • Editing a hosts file • Deleting a hosts file • Adding systems in a hosts file to the HP SIM database • Creating a task to import a hosts file for HP SIM integration • Batch-adding systems using the CLI Related topic ▲ Discovery and identification Creating a new hosts file NOTE: For keywords that contain more than one word, such as "management processor," enclose the full keyword in double quotation marks.
PAGE 113
mySystem.mydomain.com/ Precede comment lines with the # character: # This is a comment line 1.2.3.4 mySystem.mydomain.com mySystem #This is an end-of-line comment See “Hosts file extensions” for information about hosts file extensions.
PAGE 114
Deleting a hosts file NOTE: 1. 2. 3. 4. 5. 6. Delete hosts files only if you no longer need them or if you are creating a new hosts file. Ensure that the selected hosts file is not in use. A hosts file is not in use when: • There are no references to it in the Ping exclusion ranges, templates and/or hosts files section of the general settings page. • There are no references to it in the Ping inclusion ranges, templates, and/or hosts files section of every existing discovery task.
PAGE 115
Importing the .dat file NOTE: If the hosts file contains a cluster name or address, the HP SIM discovery IP range must include the cluster members because the imported hosts file might not include the cluster members. See “Creating a new discovery task” for information about changing the IP range. 1. 2. 3. 4. 5. 6. 7. 8. Select Options→Discovery. The Discovery page appears Under the For all automatic discoveries section, click Manage hosts files. The Manage Hosts Files page appears. Select hosts files.
PAGE 116
2. From the command line, run: mxnode -a -f mysystems.xml Where mysystems.xml is the name of the file you created. Related procedure ▲ Creating a new hosts file Hosts file extensions 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.
PAGE 117
# 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.
PAGE 118
Default values If a parameter is missing in the hosts file, the default is applied.
PAGE 119
Related procedure ▲ Managing hosts files Related topic ▲ Discovery and identification IP ranges You can specifically include or exclude IP addresses individually for discovery or as part of a range. Because the IP address range entries also affect cluster discovery, IP ranges must include the addresses of the cluster and its nodes. Enter one system or range per line.
PAGE 120
• Operating system name, type, and version • Associations, such as iLO in server During identification, remote enclosures have a generic name (format: Encl_SerialNumber) assigned to them until one server from every enclosure is discovered and identified. Then, the enclosures contain the name of the enclosure assigned to the enclosure.
PAGE 121
Related topic ▲ Discovery and identification Managing system types The STM is a utility that modifies the default behavior of identification. STM enables you to customize the type and product name of third-party systems using rules based on responses to SNMP and DMI (Windows only) lists from systems on your network. IMPORTANT: For most HP systems, the system type and product name cannot be modified. Identification can be customized based on SNMP System OIDs for all other fields.
PAGE 122
To access the Manage System Types page, select Options→Manage System Types. System type You can filter the list on the Manage System Types page by system type by selecting a type from the System Type dropdown list. Click the down arrow, and then select a system type.
PAGE 123
Related topics • Managing system types • About System Type Manager About System Type Manager Manufacturers assign unique OIDs to their SNMP-instrumented products. STM enables you to customize identification by creating rules that map these OIDs to product categories and names of your choosing. HP SIM discovers and applies information from the rule when an unknown system matches a rule that you specify.
PAGE 124
Creating STM rules The following procedure instructs you how to create a new SNMP rule through STM. The STM is a utility used to modify the default behavior of identification. STM enables you to customize the type and product name of systems using rules based on responses to SNMP and DMI (Windows only) collections from systems on your network. NOTE: NOTE: DMI rules can only be created from the command line interface.
PAGE 125
a. b. c. d. e. 4. 5. In the Object identifier field, enter the object identifier. In the Community string field, enter the community string if other than public, which is the default. to retrieve data, the community string of the target system and the HP SIM server must match to retrieve data. In the Target hostname or IP address field, enter the IP address of the system you want to search. Click Get response to show the Response SNMP data type and the Response value.
PAGE 126
Command line interface Use the mxstm command to add SNMP and DMI (Windows only) rules from the command line. For assistance with this command, see the HP-UX or Linux manpage by entering man mxstm at the command line. See “Using command line interface commands” for more information about the command and how to access the manpage.
PAGE 127
Related topics • Managing system types • About System Type Manager • Navigating the Manage System Types page Additional information for creating STM rules Manufacturers assign unique OIDs to their SNMP-instrumented products. In addition, systems supply information about themselves using variables described in files called MIBs. These values are enumerated using an industry-standard structure.
PAGE 128
Type = String(64) Value = "Win32 DMI Service Layer" End Attribute Start Attribute Name = "Version" ID = 3 Description = "Version number of this component." Access = Read-Only Storage = Common Type = String(64) Value = "2.32" End Attribute Start Attribute Name = "Serial Number" ID = 4 Access = Read-Only Storage = Common Type = String(64) Value = "unsupported" End Attribute ... Adding new DMI rules (from Windows CMS only) You can create a new DMI-based rule using the command line utility (mxstm).
PAGE 129
6 Users and authorizations NOTE: Users that have been added to the Central Management Server (CMS) cannot view or manage systems until authorizations have been configured for them. NOTE: Command line tools provided by HP-UX and Linux (such as ls and df) are run as root by default. For security reasons, you might want them to run as a specific user to avoid inadvertently allowing unauthorized access to a user.
PAGE 130
HP SIM enables you to configure authorizations for specific users or user groups. Authorizations give the user access to view and manage systems. Each authorization specifies a user or user group, a toolbox, and a system or system group. The specific set of tools that can be run on a system that is specified in the assigned toolbox. It is important that you plan which systems each user will manage manage and which specific set of tools each user is authorized to execute on managed systems.
PAGE 131
Users and user groups Administering users involves adding, editing, deleting, and reporting. After you have added a user or user group, you can assign predefined authorizations from the Authorizations tab. Users and user groups must exist in the operating system. For Microsof Windows ®, this includes Active Directory. When a user group is configured in HP SIM, any user that is a member of the user group in the operating system can sign-in to HP SIM without having to be configured as a user in HP SIM.
PAGE 132
arrow is pointing up, the list is sorted in ascending order. If the arrow is pointing down, the list is sorted in descending order. • Run SE user security configuration By default, users created in HP SIM can access HP Storage Essentials with limited read privileges. to edit user roles and give users additional privileges, click the Run SE user security configuration link.
PAGE 133
9. Under the Sign-In IP Address Restrictions section, in the Inclusion ranges field, enter the IP addresses of the systems you want this user to be able to use as a client browsing this CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IP addresses separated by a dash (-). The IP addresses must be entered in the standard dotted decimal notation, for example, 15.1.54.133. Any spaces surrounding the semicolons or dashes are ignored.
PAGE 134
sign in IP address restrictions, or authorizations are changed, this change is immediately reflected for all current members of the group. With configuration rights, the user inherits the highest setting. With sign-in IP address restrictions, the user inherits all entries. With authorizations, the user inherits all authorizations. NOTE: A user's group membership is determined at sign-in.
PAGE 135
Related procedures • Editing user accounts and user groups • Deleting user accounts and user groups • User and user group reports Related topics • Users and authorizations • Users and user groups • Default user templates Editing user accounts and user groups In the event a user account or user group must be modified, you can edit it from the Users tab on the Users and Authorizations page.
PAGE 136
are ignored. Spaces are not allowed within a single IP address in the dotted decimal notation. Enter 0.0.0.0 to prevent a user from logging in through a remote system. Important: If browsing from the CMS, ensure all IP addresses of the CMS are properly included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also included. h. i. j. k. l. m. 4. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from management by this user or user group.
PAGE 137
When deleting a user group, all members of the group lose membership in that group, which causes those users' authorizations, configuration rights, and login IP address restrictions to be updated based on their new group memberships. Users that are no longer members of any user group are deleted from HP SIM. CAUTION: Deleting a user or user group prevents the user or group from signing-in and removes all associated authorizations and tasks that are owned by that user or user group.
PAGE 138
• Pager Configured • IP Sign-In Restrictions • Full Name To generate and print a user account or user group report: 1. 2. Select Options→Security→Users and Authorizations→Users. Click Report. The Users Report window appears. 3. To print the report, select File→Print. The user report is printed. Command line interface Users with administrative rights can use the mxuser command to create user and user group reports from the CLI.
PAGE 139
Toolboxes The Toolboxes section enables you to configure groups of tools. The following toolboxes are created during the installation process:: • The All Tools toolbox contains all tools in the Central Management Server (CMS). • The Monitor Tools toolbox contains tools that display the state of the managed systems but not tools that change the state of the managed systems. For example, the Monitor Tools toolbox permits viewing installed software but does not permit installing software.
PAGE 140
NOTE: The toolbox name must start with an alphabetic character followed by alphanumeric characters, embedded blank characters, underscore (_), or dash (-) and must be less than or equal to 16 characters in length. To add a toolbox: 1. 2. 3. 4. 5. Select Options→Security→Users and Authorizations→Toolboxes, and then click New. The New Toolbox section appears. In the Name field, enter a name for the new toolbox. This field is required. In the Description field, enter a description for the toolbox.
PAGE 141
1. 2. Select Options→Security→Users and Authorizations→Toolboxes. Select the toolbox to edit, and then click Edit. The Edit Toolbox section appears. Note: For users with operator rights and user rights to clear, delete, assign events, and add comments to events, you must select Configuration Tool from the Show tools in category dropdown list. Then, select Clear Events, Delete Events, Assign Events, and Comment Events as necessary, and then click 3. to add them to the Toolbox contents.
PAGE 142
Related topics • Users and authorizations • Toolboxes Toolbox report For detailed information about a toolbox, you can generate and print a toolbox report. NOTE: To sort the report information in ascending or descending order, click the appropriate column heading. The column heading that includes the arrow is the column by which the report is sorted. If the arrow is pointing up, the report is sorted in ascending order. If the arrow is pointing down, the report is sorted in descending order.
PAGE 143
• System This column displays the systems on which the user or user group has authorizations. A system group appears in bold type. • Auto This column displays Auto if the authorization is set to automatically update when the collections that the authorization is based upon are updated. A system group is a group of systems based on a system collection that is used for authorizations.
PAGE 144
• You can define separate authorizations in HP Storage Essentials on the Users page. • By default, HP SIM users have limited read access to all HP Storage Essentials managed systems and features. You can modify access privileges on the Roles page. • Use the Organizations page to control the HP Storage Essentials managed systems that are visible to HP SIM users.
PAGE 145
b. c. In the Select Systems list box, the two default system groups (All Managed Systems and CMS) appear. Select one of these groups, or to select systems for the authorization, click Add to display the Add Systems section. In the Add systems by selecting from section, select one of the following: i. Collection Select a collection and click View contents. If you want to use the entire collection as your selection, select Select "collection name" itself.
PAGE 146
You can continue to add systems and collections and can enable automatic updates for each selected collection. Since automatic updates for any authorization apply to all authorizations using the same selected collection, changing the setting for one affects any other authorization using the same collection. Therefore, during system selections, if you select a group already associated with an automatically updating authorization, the option Automatically track changes.
PAGE 147
Users with administrative rights can use the mxauth command to add authorizations from the CLI. NOTE: Users must have the User can configure CMS security access such as creating, modifying or removing other users option selected when their account is set up for them to be able to use the mxngroup and mxauth commands. Users with operator rights can use the mxexec command to launch command tools on systems from the CLI. For assistance with this command, see the associated manpage.
PAGE 148
Command line interface Users with administrative rights can use mxngroup to update system groups from the command line interface (CLI). However, if there are edits to the system group from the CLI, there is no affect on the source collection. See “Using command line interface commands” for information about accessing the manpage.
PAGE 149
NOTE: To sort the report information in ascending or descending order, click the appropriate column heading. The column heading that includes the arrow is the column by which the report is sorted. If the arrow is pointing up, the report is sorted in ascending order. If the arrow is pointing down, the report is sorted in descending order.
PAGE 150
NOTE: Any additional changes to the system collection do not affect the system group or authorizations unless updated by one of the following options. The content of the system group is updated with the current contents of the collection when: • Another authorization is created using the collection • An authorization using the system group is updated • Using mxngroup from the CLI In the first two cases, the current contents of the collection appear for verification.
PAGE 151
7 Directory Services The Directory Groups tool is used to determine a system's membership in a Windows domain, organizational unit (OU), or group. Before using the Directory Groups tool, you must first configure the directory server parameters on the Directory Server Configuration page. After you configure the directory server, the Directory Groups tool must be configured with the distinguished name (DN) of the desired container objects in the directory.
PAGE 152
Related procedure ▲ Configuring directory groups Related topics • Users and authorizations • Directory Services Configuring directory groups After configuring the directory server parameters, you must configure the containers and groups that contain the computer objects of interest. A container is like a branch, where systems in the container are child objects of the container object in the directory tree.
PAGE 153
• Users and authorizations • Directory Services Configuring directory groups 153
PAGE 154
PAGE 155
8 HP SIM credentials In HP SIM, there are three different types of credentials: • System Credentials Credentials used by identification to access managed systems. These credentials include WBEM, WS-MAN, and SSH credentials, Sign-in, SNMP community string, and Single Sign-On credentials. • Global Credentials • Trusted Systems Credentials used to manage the public SSH keys, stored in the known_hosts file, from the CMS and to set trust relationships.
PAGE 156
• WS-MAN This tab enables you to set WS-MAN credentials for all selected systems or set the credentials individually for each system. • SSH This tab enables you to configure SSH credentials for all selected systems or set the credentials individually for each system. • Single Sign On This tab enables you to set the trust by certificate relationship. The System Credentials page is launched as a tool and accesses the task wizard for system selection.
PAGE 157
Related procedures • Sign-in credentials • SNMP credentials • WBEM credentials • WS-Man credentials • SSH credentials • Single sign on credentials • Quick Launch menu Related topics ▲ HP SIM credentials Sign-in credentials Sign-in credentials are protocol independent. For performance reasons, a maximum of 10 systems can be edited individually at one time. 1. 2. 3. 4. 5. 6. Select Options→Security→Credentials→System Credentials. Select target systems.
PAGE 158
1. 2. 3. 4. 5. 6. 7. Select Options→Security→Credentials→System Credentials. Select target systems. See “Creating a task” for more information. Click Run Now. The System Credentials page appears. To edit system credentials, select systems and click Edit system credentials. Click Show advanced protocol credentials. Select the Single Sign On tab. Select from: • Configure Single Sign-On for each selected system as follows (Optional) Select Set Trust relationships to "Trust by Certificate".
PAGE 159
6. Select from: • Replace each selected system's SNMP community string with the following replace sign-in credentials for selected systems. a. b. • Use this option to Enter the Read community string. To use other credentials if the assigned credentials fail, check If these credentials fail, try other credentials that may apply. Click the Learn more link for additional information. By default this box is not selected, unless you have upgraded HP SIM.
PAGE 160
i. Use sign-in credentials entered in HP SIM. These credentials must be for an account with administrator or root access on the selected system ii. Use the following credentials for all systems Enter the user name, password, and domain credentials to use for all selected systems. These Configure or Repair Agents credentials apply to the WBEM, SSH, and Single Sign On protocols. You need to enter them only once and they pre-populate on each tab. • b.
PAGE 161
a. b. Enter the user name and password. To add additional port number, user name, and password sets, click Add. To delete port number, user name, and password sets, click Delete beside the set you want to delete. HP SIM verifies that the port numbers entered are unique and valid port numbers. By default, the port number is blank. Port numbers are not available on the discovery task pages. c. d.
PAGE 162
a. b. • Replace WS-MAN credentials individually as follows individually for selected systems. a. b. 8. Enter the user name and password. To use other credentials if the assigned credentials fail, check If these credentials fail, try other credentials that may apply. Click the Learn more link for additional information. By default this box is not selected, unless you have upgraded HP SIM. Use this option to specify sign-in credentials Enter the user name and password for the individual systems.
PAGE 163
9 Networking and security HP SIM provides the following security options: • User and Authorizations. • Server Certificate. • Global Credentials. • Systems Credentials. • Trusted Certificate • SSH Host Keys • Sign-In Event Settings • System Link Configuration • Privilege Elevation Select Options→Security→Users and Authorizations. Select Options→Security→Certificates→Server Certificate. Select Options→Security→Credentials→Global Credentials.
PAGE 164
At the HP SIM server, you must also specify the user authorization for the managed system and have executed a System Identification task. If you have enabled the Require option on the Trusted System Certificates page, you must import the certificates of trusted managed systems into HP SIM, or a root CA certificate. See “Trusted certificates” and “Server certificates” for complete details. Certificates HP SIM allows secure and authorized management from the CMS.
PAGE 165
About login Single Sign On Single Sign On allows a link within an HP SIM page to establish an authenticated browser session to a managed system that supports Single Sign On without requiring users to re-enter their user names and passwords. However, if you are trying to establish an authenticated browser session with another instance of HP SIM running on another system, you must re-enter your user name and password. Single Sign On links exist wherever there is a link to another system.
PAGE 166
NOTE: For more information, go to http://h18013.www1.hp.com/products/servers/management/ hpsim/infolibrary.html, and select the appropriate guide for your operating system. • A cookie blocker is installed. NOTE: HP SIM can be configured to log an event in the HP SIM Event Database when a sign-in attempt fails or succeeds and when a sign-out occurs. Sign-in authentication on Linux and HP-UX HP SIM uses PAM to authenticate users who sign in to the web server interface on Linux and HP-UX.
PAGE 167
• Installing OpenSSH • Managing SSH keys About secure task execution HP SIM tasks that cause state or configuration changes on managed systems use STE to issue commands to the system. STE enables an HP SIM system to securely request execution of a task from a managed system, ensuring that the user requesting the task has the appropriate rights to perform the task. The request includes a digital signature to uniquely identify the HP SIM system making the request.
PAGE 168
Note: In the case of systems with multiple network interfaces, selecting the Use the system name provides only one link per destination to the system, whereas Use the system IP address provides multiple links to the system. 3. To save and apply the changes, click OK. Related topics • Networking and security • Server certificates • Installing OpenSSH • Managing SSH keys Configuring sign-in events Configure sign-in events to create actionable events for sign-in and sign-out activities.
PAGE 169
1. 2. 3. Open the globalsettings.props file. • On a Windows operating system, the globalsettings.props file is located in the install directory\config folder. • On an HP-UX or Linux operating system, the globalsettings.props file is located in the /etc/opt/mx/config directory. Change EnableSessionKeepAlive=true to EnableSessionKeepAlive=false. Select File→Save. The updates are saved. 4. Close the globalsettings.props file. To change the default timeout: 1.
PAGE 170
URIEncoding="utf-8" useBodyEncodingForURI="true" compression="on" keystoreFile="C:\Program Files\HP\Systems Insight Manager\config\certstor\hp.keystore" keystorePass="pBHQs0Mty09f4kO6NVJz" sslProtocol="TLS" />. Related topic ▲ Networking and security Configuring privilege elevation From this page, you can enable privilege elevation for Linux, HP-UX, and ESX managed systems. This enables you to sign in as an unprivileged user and elevate the privilege to run on these operating systems. 1.
PAGE 171
HP SIM provides the following security certificate options: • Export server certificate Select Options→Security→HP Systems Insight Manager Server Certificate, and then click Export. • Edit server certificate and then click Edit. • Create new server certificate Select Options→Security→HP Systems Insight Manager Server Certificates, and then click New. • Import server certificate Select Options→Security→HP Systems Insight Manager Server Certificates, and then click Import.
PAGE 172
certificate in accordance with your security practices to return to the same level of functionality you had before. NOTE: On Windows and Linux, this process also affects the local HP System Management Homepage certificate and private key on HP-UX systems, it affects the WBEM Services certificate and private key. NOTE: Valid characters for each of these fields include letters a through z (lowercase), A through Z (uppercase), numbers 0 through 9, and the following special characters: ‘ ( ) + , - .
PAGE 173
3. 4. Click OK. If you click Cancel, you return to the Server Certificate page without creating a new server certificate. A warning appears, reminding you about the effects of changing the certificate and private key. If you click OK in the warning box to continue, a new 1,024-bit key-pair and a new self-signed certificate are generated. The old key-pair and certificate are not retrievable unless a backup was created manually before this process.
PAGE 174
e. f. 3. In the State (S) field, enter the name of your state. This field can contain up to 128 characters. In the Country (C) field, enter the name of your country. This field can contain up to two alphanumeric characters, using the two-letter country codes. Click OK. A warning message appears, indicating that the certificate is about to be modified. You can click Cancel to abort the modify operation.
PAGE 175
Related topics • Server certificates • Networking and security • Installing OpenSSH • Managing SSH keys Exporting a server certificate Export the HP SIM server certificate to a file to facilitate deployment of the certificate to your browsers. This certificate enables a browser to properly identify the HP SIM server. The HP SIM server certificate is a public document, so it does not need to be kept private.
PAGE 176
3. 4. To create a PKCS #10 signing request that is downloaded through a standard browser, click Create. In Internet Explorer, use the File Download dialog box. In Mozilla, save the text in the new browser window to a file. Send the certificate file to a CA. Note: The existing self-signed certificate is still valid, so the SSL web server remains operational for browsing until the signed certificate is received from the CA.
PAGE 177
NOTE: On Windows and Linux, this process also affects the local HP System Management Homepage certificate and private key on HP-UX systems, it affects the WBEM Services certificate and private key. NOTE: HP SIM supports only importing certificates that have a public key size of 2,046 bits or less. To import the signed certificate reply from a CA: 1. 2. 3. Select Options→Security→HP Systems Insight Manager Server Certificate, and then click Import. The Import Server Certificate section appears.
PAGE 178
• Installing OpenSSH • Managing SSH keys Replicating trusted certificates System administrators that have the HP SIM Require or First Time Accept features enabled can replicate the trusted certificates list to other HP SIM systems. If you do not use the Require or First Time Accept features of HP SIM as a two-way trust solution, this procedure is not necessary.
PAGE 179
Using the Replicate Agent Settings feature NOTE: This section assumes agents are already configured to trust the source CMS. NOTE: This process configures the agents to trust only the new target CMS. If trust for the original source CMS is still necessary, perform steps 5, 6, and 13 (or 16) using the source CMS. 1. 2. 3. 4. 5. 6. 7. 8. 9. Log in to the HP SMH on the target CMS. Select Settings→Security→Trust Mode. Select Trust by Certificate, and then click Save Configuration.
PAGE 180
• Invalid Certificate Format appears in the debug log files followed by the system this error message corresponds to. The certificate was being sent from a program residing on a port that one of the HP SIM HP Insight Management Agent should reside on. Another possible cause of this error is that the certificate sent to the CMS was corrupt. To correct this issue, verify that the Insight Management Agent running on the client system has not been tampered with and is running as expected.
PAGE 181
Related topics • Requiring trusted certificates • Administering systems and events • Server certificates • Requiring trusted certificates • Setting up trust relationships • Replicating trusted certificates • Possible certificate errors • Installing OpenSSH • Managing SSH keys Importing trusted certificates If you have selected Require on the Trusted System Certificates page, you must import certificates that represent the managed systems you want to trust to the Trusted Certificates List.
PAGE 182
NOTE: The system certificate can be exported as a Base64 encoded certificate. The exported certificate can be imported into a browser or a system's or the Trusted Management Systems List. Exporting the system certificate from HP SIM To export the system certificate from HP SIM using Microsoft Explorer: 1. Select Options→Security→Credentials→Trusted Systems, and then click Export. The File Download dialog box appears. 2. 3. Select the location for the file to be saved.
PAGE 183
• Networking and security • Installing OpenSSH • Managing SSH keys Deleting trusted certificates CAUTION: The delete process is irreversible. Use this feature with caution! To delete certificates from the Trusted System Certificates List: 1. 2. 3. 4. Select Options→Security→Credentials→Trusted Systems. Select the certificates to be deleted. Click Delete. A dialog box appears.
PAGE 184
1. From the Administer tab, select Options→Security→Credentials→Trusted Systems. The Trusted Certificates page appears. 2. Select Require. This setting restricts the CMS from accepting any connections other than SSL connections with managed systems. The managed systems must have a certificate in the Certificate List. This option does not affect browsing to the CMS.
PAGE 185
NOTE: For Trust By Certificate, the certificate from the HP SIM system can be installed during the initial support pack deployment. See “Initial ProLiant Support Pack Install” for more information. Importing the HP SIM certificate over the network If you prefer importing the HP SIM certificate from a file, see Importing the HP SIM certificate from a file for more information. 1. From a web browser, navigate to the managed server using the address: https://managed-server:2381.
PAGE 186
6. 7. Paste the contents of the certificate file into this box, and then click Add Cert. A confirmation window appears with three links at the top. Click Options, and scroll down to the Trusted Certificates section. The Trusted Certificates: list appears with the server name and links to View Certificate and Remove Certificate for the HP SIM certificate that was just added.
PAGE 187
1. 2. Select Options→Security→Certificates→Trusted Certificates, and then click Import. The Import Trusted System Certificate section appears. Next to the Certificate Filename field, click Browse. The Choose file dialog box appears. 3. Navigate to the location of the certificate to be imported, and then select the file name. Click Open. The certificate is imported. Note: If you are setting up a trusted certificate on a cluster, see “Cluster” for more information.
PAGE 188
PAGE 189
10 Monitoring systems, clusters, and events You can monitor systems, clusters, and events using the tools in the System and Event Collections panel. These tools enable you to locate more information about systems and events and quickly select systems to perform tasks. From System and Event Collections panel, you can quickly access the System Overview page, the All Systems page, and the All Events page. You can also save searches in private collections under Systems or Events.
PAGE 190
be migrated into three new collections: MyServersEvents-combination, MyServersEvents-systems, and MyServersEvents-events. • Combination collections This form of collections enables you to bind together a system collection and an event collection. These collections enable you to reuse and recombine system and event collections you have created. Locked collections Locked collections are collections that you cannot edit and support certain system types.
PAGE 191
• Performing an advanced search for clusters • Saving collections • Customizing the system table view page • Deleting systems from the HP SIM database • Moving system or cluster collections • Copying system or cluster collections • Moving event collections • Copying event collections • Printing a system collection view Related topics • System table view page • Cluster table view page • Event table view page • Customizing event collections • Customizing system or cluster collection
PAGE 192
Selecting a collection displays a view of its contents. From the System and Event Collections panel, you can launch several types of collection view pages.
PAGE 193
In addition to using the collections provided by HP SIM, you can create, edit, or delete your own collections. Collections must follow specific naming conventions. See “Collection naming conventions” for more information about naming collections. Collections can be used to organize large numbers of systems into smaller, more meaningful groups. For example, your organization might have five system administrators who are responsible for 100 different systems in 6 different buildings.
PAGE 194
Displaying collection type Select the type of collection you want to customize by selecting Systems from the Show collections of dropdown box. Expanding or collapsing collections You can select to view all collections included in the Shared or Private collections, or to view only the Shared or Private collection titles. Click click to expand all system and cluster collections in the table, or to collapse all system and cluster collections in the table.
PAGE 195
Related procedures • Performing an advanced search for systems • Editing system or cluster collections • Creating system or cluster collections • Deleting system or cluster collections • Setting properties for a system or cluster collection • Moving system or cluster collections • Copying system or cluster collections Related topics • Monitoring systems, clusters, and events • Default shared collections • System status types • Software status types Creating system or cluster collection
PAGE 196
a. b. c. • In the Search for dropdown list, select systems or clusters. Enter the search criteria for the collection. See “Performing an advanced search for systems” for more information about system search criteria, or see “Performing an advanced search for clusters” for more information about cluster search criteria. Click one of the following: • [View] • Save As Collection To save the collection. See “Saving collections” for more information about saving collections.
PAGE 197
1. 2. 3. In the System and Event Collections panel, click Customize. The Customize Collections page appears. In the Show collections of dropdown list, select Systems. All available system or cluster collections appear. Select a system or cluster collection to edit, and then click Edit. The Edit Collection section appears. Depending on how you created the collection, the following appears: a. If you created the collection using the Choose members individually option, complete the following steps: i.
PAGE 198
Related procedures • Performing an advanced search for systems • Creating system or cluster collections • Deleting system or cluster collections • Setting properties for a system or cluster collection • Moving system or cluster collections • Copying system or cluster collections Related topics • Monitoring systems, clusters, and events • Customizing system or cluster collections • Navigating the System and Event Collections panel Saving collections Perform the following procedure to save a
PAGE 199
• System table view page • Cluster table view page Moving system or cluster collections This procedure enables you to move a collection from one collection to another. Users with administrative rights can move a shared collection. To move a collection: 1. 2. In the System and Event Collections panel, click Customize. The Customize Collections page appears. In the Show collections of dropdown list, select Systems. All available system or cluster collections 3. 4. appear.
PAGE 200
When you copy a collection that was created based on attributes, you copy the collection attributes into the new collection. If you edit the original collection after you copy it to the new collection, the newly copied collection does not reflect these edits. When you copy a combination collection, the newly created collection has the same system collection and event collection. If you edit the original collection after you copy it to the new collection, the newly copied collection is not updated.
PAGE 201
Deleting system or cluster collections NOTE: Users with administrative rights can delete a shared collection. Users with operator rights can view shared collections, but, can only delete their own private collection. 1. 2. 3. 4. Click Customize in the System and Event Collections panel. The Customize Collections page appears. In the Show dropdown list, select Systems. All available system or cluster collections appear.
PAGE 202
Note: To conserve system resources, try to limit the display of status to only those collections that you view the most. 6. In the Default View field, select the default view from the dropdown list. Command line interface Users with administrative rights can use the mxcollection command to set properties for collections from the CLI. See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
PAGE 203
Displaying collection type Select Events from the Show collections of dropdown box to customize event collections. Expanding or collapsing collections You can select to view all collections included in the Shared and Private collections, or to view only the Shared and Private collection titles. Click click to expand all system and cluster collections in the table, or to collapse all system and cluster collections in the table.
PAGE 204
Creating event collections NOTE: By default, all newly created collections are private. NOTE: Users with administrative rights can create a new shared event collection. Users with operator rights or user rights view shared collections, but can create only their own collections. 1. 2. 3. 4. Click Customize in the System and Event Collections panel. The Customize Collections page appears. In the Show collections of dropdown list, select Events. All available event collections appear. Click New.
PAGE 205
Command line interface Users with administrative rights can use the mxcollection command to create new collections from the CLI. See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
PAGE 206
1. 2. 3. Click Customize in the System and Event Collections panel. The Customize Collections page appears. In the Show collections of dropdown list, select Events. All available event collections appear. Select the event collection to edit, and then click Edit. The Edit Collection section appears. Depending on how the collection was created, the following appears: a. If you created the collection with the Choose members individually option, complete the following steps: i.
PAGE 207
• Deleting event collections • Moving event collections • Copying event collections • Setting properties for an event collection Related topics • Monitoring systems, clusters, and events • Customizing event collections • Navigating the System and Event Collections panel Moving event collections This procedure enables you to move a collection from one collection to another. Users with administrative rights can move a shared collection. To move a collection: 1. 2.
PAGE 208
Copying event collections You can copy a collection as a new collection. When you copy a collection that was created by members, you copy the collection and its members into the new collection. If you edit the original collection after you copy it to the new collection, the newly copied collection is not updated. For example, if the original collection has two members, the same two members copy to the new collection.
PAGE 209
Deleting event collections NOTE: Users with administrative rights can delete a shared collection. Users with operator rights or user rights can view shared collections, but can only delete their own private collections. 1. Click Customize in the System and Event Collections panel. The Customize Collections page appears. 2. In the Show dropdown list, select Events. All available event collections appear. Click 3. 4.
PAGE 210
See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
PAGE 211
1. 2. 3. 4. 5. 6. 7. Tabs Quick Launch View as Table information System view columns System table view page buttons Customizing the view From this page, you can view systems in a list, table, or tree, and save system collections, delete systems, and print the system collection. If a collection includes more than 500 members, the first 500 members appear on the first page. Systems selected on one page remain selected as you navigate to a different page in the collection.
PAGE 212
displays the HS status icon and the System Name for each system in a tree format. See “Navigating the tree view page” for more detailed information about the tree view. See “Navigating the icon view page” for more information about the icon view. System health status summary The summary shows how many systems in the view have a status of: Critical, Major, Minor, Normal, Disabled, and Unknown. See “System status types” for more information.
PAGE 213
NOTE: The status of a complex is collected only when VSE Manager is registered with HP SIM. In addition, the status update is collected every 30 minutes from the nPar or Complex outside of HP SIM. Management processor The MP column displays the status icon of the management processor if the system has an iLO board installed. Otherwise, the Informational icon appears. Clicking the status icon displays the management processor login page.
PAGE 214
HP Virtual Machine Management Pack If HP Virtual Machine Management Pack is installed, the VM status column displays the cumulative status of all virtual machine hosts and virtual machine guests. Clicking the status icon on the VM status column displays in the HP Virtual Machine Management Pack page for the selected system, providing more information about the status of the virtual machine.
PAGE 215
The following system types are containers: • Rack • Enclosure • Cluster When servers and management processors in racks and enclosures are discovered and identified, associations are made between the systems and the racks and enclosures where systems reside. This association appears in the System Name column on the system table view page by showing name in system type container name.
PAGE 216
System table view page buttons Three buttons at the bottom of the system table view page are available to users with administrative rights. These buttons are not available when using a tool and selecting an individual target system. • Save As Collection When a system is highlighted, this button is used to save the selection with a new name. Changes are saved on a per-user basis. If you click Save As Collection, the collection is saved as a combination of the system and event collections.
PAGE 217
Navigating the tree view page When a collection is selected that was created based on individual members, the tree view appears in the workspace. The tree view is initially collapsed. Systems might appear in multiple locations because they can be in multiple containers. Users can view only systems that they are authorized to view. Therefore, if a user is not authorized to view a particular system in the tree, that branch does not appear. The following sections are available on the tree view page: 1. 2. 3.
PAGE 218
the target verification page of the Task Wizard. You cannot schedule tools launched from this menu. Customize this menu by clicking the Customize link in the Quick Launch menu. Expanding the tree view Branch nodes can be expanded by clicking the toggling expansion icon. However, the system name is not an expansion control, but a hyperlink to a page that displays more information about that particular system. When a branch is collapsed, the icon appears as systems, and the icon toggles to .
PAGE 219
icon to the left of the rack is Critical, and you click the icon, a table view of all systems in the rack with the status of Critical appear. Selection states for collections In the tree view, you cannot simultaneously select a collection and members of the same collection. When a collection is selected, the members appear and their selection boxes are disabled. The selection states for a collection are as follows: • The initial state; nothing is selected.
PAGE 220
Navigating the icon view page The icon view lists the system name of all discovered systems, as well as the system health status for each system. The legend shows how many systems in the view are Critical, Major, Minor, Normal, Disabled, and Unknown. Select the checkbox next to system name to select a system. You can select more than one system, or to select an entire collection, select the checkbox, Select "collection name" itself. This page includes the following sections: 1. 2. 3. 4. 5.
PAGE 221
page” for more detailed information on the tree view. See “Navigating the system table view page” for more information about the system table view. System health status summary This summary shows how many systems in the view have a status of Critical, Major, Minor, Normal, Disabled, and Unknown. See “System status types” for more information about system status types. Icon view buttons The following buttons at the bottom of the icon view page are available to users with administrative rights.
PAGE 222
that particular server, including server blade name, slot number, and the enclosure in which the server is located. You can also click a server name to display information about the server. The System Page appears. The following systems appear in the picture view for racks and enclosures: • Servers or desktops • Interconnect switch • Power supply enclosure Interconnect bays that have no server, desktop, or interconnect switch identified appear in the picture view for enclosures.
PAGE 223
4. Select Add to new rack from the Add to Rack dropdown list and click Go. The Edit Rack page appears. When a new rack is created from an enclosure view, the enclosure is automatically added to the Selected enclosures section. Note: The Add to Rack dropdown list also lists the racks that you previously created. To add an enclosure to an existing rack, select the rack name and click Go. 5. To create a rack, you must add the following details: • Rack Name. list. • Rack Height. • Data Centre ID.
PAGE 224
enclosure is already assigned to another rack. You can confirm your intention to remove the enclosure from the existing rack, and it is added to the new rack. You can click Cancel to discard the rack and close the window. Editing a rack From the picture view of a rack, you can edit the rack to add or remove enclosures. To edit a rack: 1. To access the picture view, navigate to All Racks and select the rack to be edited and click Edit Rack. The Rack View page appears.
PAGE 225
SNMP Status Polling obtains the status for the host server. HP SIM can distinguish between the following management processor products: • Remote Insight Board PCI • Remote Insight Board EISA • Remote Insight Lights-Out Edition (RILOE) The system table view page provides the following information about management processors: • The server entry displays a Status icon in the MP column. The tool tip for the icon displays the status of the management processor.
PAGE 226
Two default collections are related to racks and enclosures and are listed under the System Type collection: • All Racks • All Enclosures On the system table view page, racks appear in the following formats: • Encl1 in Rack1 • Rack1 To view the Picture View page, click a rack hyperlink on the system table view page or from the System and Event Collections panel.
PAGE 227
Deleting systems from the HP SIM database NOTE: Deleting multiple systems from the database at one time can cause performance delays. NOTE: The CMS cannot be deleted. NOTE: You cannot delete clusters that contain cluster members. To delete a cluster with its cluster members, you must first go to the system table view page by selecting the All Systems collection in the System and Event Collections panel. Then, select the cluster along with all of its members, and then click Delete.
PAGE 228
Related topics • System table view page • Navigating the system table view page System status types The following table describes the HP SIM, system health status types: Status icon 228 Monitoring systems, clusters, and events Status type Description Critical HP SIM 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.
PAGE 229
NOTE: HP Insight Management Agent for Servers for Windows continues to use the terms Normal, Degraded, Failed, and Inaccessible. Minor and Major statuses are only associated with systems running these agents. Related topic ▲ System table view page WBEM operational status types HP SIM reports WBEM operational status for storage and server elements, such as storage switch ports and filled memory slots.
PAGE 230
Status icon Status type Description Starting, Stopping, Dormant, Power Mode, This status provides useful information about Other the port. No attention is required. • Starting indicates that the element is starting. • Stopping indicates that element is stopping. • Dormant indicates that the element is inactive. • Other indicates that additional information is available, but it does not fit into the previously listed categories.
PAGE 231
Related topic ▲ System table view page Cluster table view page To access Cluster collections in the System and Event Collections panel, click Systems and then select one of the available cluster collections. Users with administrative rights can manage all shared cluster collections from the cluster collection view. Users can manage their own private collections from this page, as well as: • Save collections • Delete clusters Click Delete from the cluster table view page. A confirmation box appears.
PAGE 232
NOTE: Not all users can view all clusters. The results of the collection depend on the clusters that were assigned to the user who created the collection. Each user can only view the clusters that are assigned to him or her by a user with administrative rights. A user with administrative rights assigns managed clusters using user authorizations. See “Creating new authorizations” for more information. The cluster table view page is divided into the following sections: 1. 2. 3. 4. 5. 6. 7.
PAGE 233
Cluster status summary The status summary shows how many clusters in the view have a status of: Critical, Major, Minor, Normal, Disabled, and Unknown, with a total showing how many clusters are in the view. Cluster collection columns Sort columns by clicking the column header for ascending or descending order. Place your cursor over a column name for a brief description of the column. See “Customizing the cluster table view page” for more information about customizing columns.
PAGE 234
Cluster Address The Cluster Address column contains the IP address for the cluster. NOTE: HP Serviceguard clusters do not have an IP address. Therefore, this column is blank for this type of cluster. Cluster Type The Cluster Type column shows the cluster type.
PAGE 235
• Saving collections • Printing a cluster collection view Related topics • Cluster table view page • Using Cluster Monitor • HP Serviceguard Manager overview Customizing the cluster table view page When you modify the columns to display on the cluster table view page and select Apply to all cluster table views, these columns become the default columns displayed for any cluster collection selected if that collection does not already have customized columns defined. 1.
PAGE 236
Related procedures • Saving collections • Printing a cluster collection view • Customizing the cluster table view page Related topics • Cluster table view page • Navigating the cluster table view page Printing a cluster collection view 1. 2. From the cluster table view page, click Print. When the report appears, select File→Print in the browser menu.
PAGE 237
The event table view page contains the following tabs: • System(s) • Events This tab displays the events for all systems included under the System(s) tab. From this tab, you can apply additional filters to modify the event table display. This tab lists all systems in the collection. When switching between the System(s) tab and the Events tab, the Events tab "remembers" the selected events and event filter (if viewing a system collection).
PAGE 238
From this page, you can clear, delete, and assign events, enter comments on the event, and view printable reports. Tabs The event table view page contains the following tabs: • System(s) • Events This tab displays the events for all systems included under the System(s) tab. From this tab, you can apply additional filters to modify the event table display. This tab lists all systems in the collection.
PAGE 239
Event status summary This summary shows how many events in the view have a status of Critical, Major, Minor, Normal, and Informational. See “Event severity types” for more information about event status types. Event collection columns To sort collection results by a particular column, click the column header for ascending or descending order. Place your cursor over a column name for a brief description of the column.
PAGE 240
State This column displays whether the event is in the Cleared or Not Cleared state. Events start in the Not Cleared state. A Cleared state means the user is no longer interested in this event. Event states also include In Progress, which indicates that not all the data for the event has been logged. You cannot remove or clear In Progress events. Pending state events are changed to Not Cleared when the CMS is restarted.
PAGE 241
This column appears when the system is a rack or enclosure and the rack or enclosure system filter is selected. Case Status When you install HP Insight Remote Support Pack and HP SIM together on a Windows CMS, support case status updates are provided by the Remote Support Pack. The Case Status column is available when you view the All HP Service Events collection or select the event search criteria for service case status.
PAGE 242
• Print specific selections; you can print the entire list only • Print the table view page if you close the browser immediately after issuing a print request Buttons are disabled if you do not have appropriate rights. However, the Print button appears for all users. Customizing The Customize link is located in the upper right corner of the event table view page. Click this link to configure what columns appear and in what order.
PAGE 243
Clearing events from the collection You must have administrative rights to clear events. NOTE: For users with operator and user rights to clear events, they must have the Clear Events tool selected in their toolbox categories. See “Editing toolboxes” for more information. To clear an event: 1. 2. On the event table view page, select the event that you want to clear. Click Clear. For the events selected, the state changes from Not Cleared to Cleared in the State column.
PAGE 244
IMPORTANT: of the event. Assigning events to certain users does not facilitate any tracking, and the user is not notified CAUTION: If selected events have selected have previously been assigned, selecting a new assignee and clicking OK overrides the previous assignment. NOTE: 1. 2. 3. 4. You can enter a maximum of 50 characters in the assignee field. On the event table view page, select the events you want to assign to a user. Click Assign To. The Assign to section appears.
PAGE 245
Related topics • Navigating the event table view page • Event table view page • Event details section Printing an event collection view 1. 2. On the event view page, click Print. A printable window appears. When the report appears, select File→Print in the browser menu.
PAGE 246
Related topics • Event table view page • Navigating the event table view page Event details section When you click a link in the Event Type column on the event table view page, the Event Details section appears, providing detailed information about a particular event. Events are generated by SNMP traps, HTTP events, or internally generated events. NOTE: You can generate events from WBEM if you have subscribed to WBEM events on the managed system.
PAGE 247
NOTE: System name and IP address are not provided for the Unauthorized User Account Modified Event. It is an event internally generated by the HP SIM server.
PAGE 248
Tool search The Tool Search link is also available in the Search panel. Click this link to search for available tools in HP SIM. The only tools displayed are the tools you are authorized to use. See “Tool search” for more information about running tool searches.
PAGE 249
• and name is • and version is In this case, as selections are made in the higher-level selection boxes, the available selections in lower-level boxes are updated. Save as When you click Save As Collection, the Save As Collection section displays. Enter a name for the search in the Name field, and then select where to save it. See “Saving collections” for more information. View When you click View, the results of the search appear below the search frame.
PAGE 250
Note: Searching using common system attributes can be time-consuming if there are a large number of systems because the search looks at several attributes in the database multiplied by the number of discovered systems. 3. (Optional) After the search results appear, you can do one of the following: • Save the search results. Click Save As Collection, enter a name for the search, and then select where to save the collection. See “Saving collections” for more information.
PAGE 251
6. To add additional criteria, click Add. To conduct the system search immediately, click View. To delete search criteria, click Delete. To save the search as a collection, click Save As. See “Basic and advanced search” for more information about Go and Save as. Note: Criteria are reordered after clicking View or Save As. If criteria types are the same, they are placed together with "OR", if they are different, they are placed together with "AND". 7. If you clicked View, search results appear.
PAGE 252
Related topic ▲ Performing an advanced search for systems Deleting system search results from a search view NOTE: 1. 2. Deleting multiple systems from the list can cause performance delays. After the search results appear, select systems to delete from the search, and then click Delete. A dialog box appears, stating, Are you sure you want to delete these systems? To delete the systems, click OK, or to return to the Search Results page without deleting the systems click Cancel.
PAGE 253
6. 7. To add additional criteria, click Add, or to conduct the event search immediately, click View. to delete search criteria, click Delete, or to save the search as a list, click Save as. See “Basic and advanced search” for more information about Go and Save as. If you clicked View, search results appear. You can choose to delete or print the results. See “Deleting system search results from a search view” for more information about deleting selections.
PAGE 254
Related procedures • Performing an advanced search for events • Printing event search results Related topic ▲ Searching for systems and events Performing an advanced search for clusters Use the following procedure to perform an advanced search for clusters. The following image shows the Advanced Search page for clusters. To perform an advanced search for clusters: 1. 2. 3. Click Advanced Search in the Search panel. Select clusters from the Search for dropdown list.
PAGE 255
Printing cluster search results 1. 2. After the Search Results appears, click View. The results appear. Click Print. The results are printed. Note: The Print dialog box might be hidden. If so, go to the Windows Task Bar to display the box.
PAGE 256
When you select multiple criteria, the system must meet all criteria for the system to be included in the collection. For example, if you select systems within a specified IP range and with more than 32 MB of RAM, the collection does not return a system in the specified IP range if the system has less than 32 MB of RAM. Complex collections with many individual system selections or with many different selection criteria take more system resources to execute.
PAGE 257
system setting Systems with a specific client attribute defined. Client attributes are typically used and set by one of the HP ProLiant Essential plug-ins and is typically reserved for use by one of those plug-ins. system subtype Enables you to search on the product subtype field in the HP SIM database (for example, Power Enclosure, enclosure, and VM Host).
PAGE 258
Software and firmware criteria The software/firmware criteria searches for custom support packs in the selected repository and installed software/firmware components for matches in the HP SIM database. This enables you to check software and firmware installed on the target system using the HP SIM database. NOTE: Information retrieved from the database appears in the language in which it was stored. Data retrieved from the repository appears in the language corresponding to the browser locale.
PAGE 259
Cleared state criterion You can run a search on the following event statuses: • Any. Includes all events, whether Cleared, Not Cleared, or In Progress. • Cleared. Includes events that are cleared. • Not Cleared. Includes events that are not cleared. • In Progress. Includes events from tasks in the progress: When the event is complete, these events become Uncleared.
PAGE 260
NOTE: While you can select a specific version of a trap (for example, Array Accelerator Bad Data, Version 1, it is better to select both versions because you might have older or newer agents on some managed systems. Selecting all versions ensures that all agent versions are included in the event collection. The Automatic Sign-In Server Failure event type indicates that a general error occurred on the server-side of authentication during automatic sign-in. This event can occur for several reasons.
PAGE 261
Default shared collections Shared system collections All users can view shared collections, but only users with administrative rights can create, edit, or delete shared collections. The following shared default system collections are based on System Type: • All Systems Includes all discovered systems in the database. • All Servers Includes all discovered servers in the database. • All VSE Resources Includes all discovered VSE resources in the database.
PAGE 262
• All Storage Arrays • All Tape Libraries Includes all discovered storage arrays in the database. Includes all discovered tape libraries in the database. • All Racks • All Enclosures • All Clients • All Networking Devices Includes all discovered networking systems in the database, which includes routers, switches, repeaters, and remote access systems. • All Printers • All Management Processors • All Virtual Machine Hosts Includes all discovered racks in the database.
PAGE 263
• Microsoft Windows 2000 system. • Microsoft Windows NT system. • Novell NetWare • SCO UNIX • Microsoft Windows XP • Microsoft Windows 95, 98, ME or ME operating system. • HP Tru64 UNIX • HP OpenVMS Includes all systems in the database that have an OpenVMS operating system. • Red Hat Linux Includes all systems in the database that have a Red Hat Linux operating system. • SuSE Linux • Linux • HP NonStop Server • Undeployed • Microsoft Windows Server 2008 2008 operating system.
PAGE 264
• Server Status Polling List current statuses. • Non Server Status Polling List Includes all discovered servers, clusters, management processors, and their Includes all discovered non servers and their current statuses. The following collection is added if HP Storage Essentials installed: Storage Essentials Managed Includes all storage systems that are managed by HP Storage Essentials.
PAGE 265
Storage Essentials Includes all HP Storage Essentials events.
PAGE 266
PAGE 267
11 Storage integration HP SIM discovers SNMP and SMI-S storage devices. • For information about using storage devices with HP SIM, see “Storage integration using SNMP” and “Storage integration using SMI-S”. • For information about the configuration steps for discovering storage devices, see “Discovering storage using SNMP” and “About storage discovery using SNMP” for SNMP devices and “Configuring HP SIM with storage systems” for SMI-S devices.
PAGE 268
About SMI-S SMI-S replaces multiple disparate managed object models, protocols, and transports with a single object-oriented model for each type of component in a storage network. The specification was created by SNIA to standardize storage management solutions. SMI-S enables management applications (such as HP SIM ) to support storage devices from multiple vendors quickly and reliably because they are no longer proprietary. SMI-S detects and manages storage elements by type, not by vendor.
PAGE 269
The following components can be provided in several different ways: • Embedded agent The hardware device has an embedded SMI-S agent. No other installation of software is required to manage the device. • SMI solution The hardware or software ships with an agent installed on a host. The agent must connect to the device and obtain unique identifying information. This is the method used by all HP storage devices and most SAN devices.
PAGE 270
• Viewing storage system reports • Viewing storage array capacity • Changes to HP SIM storage functionality when HP Storage Essentials is installed • Using HP SIM with SNMP storage solutions Configuring HP SIM with storage systems Configuring HP SIM with storage systems For optimal interaction between HP SIM and storage systems, complete the following procedures.
PAGE 271
Related procedures • Configuring HP SIM with storage systems • Viewing storage system reports • Viewing storage array capacity Related topics • Navigating the System and Event Collections panel • Storage integration using SMI-S Viewing storage system reports HP SIM provides predefined and customized storage system reports. If HP Storage Essentials is installed, no data appears in the HP SIM storage system reports.
PAGE 272
Related topics • Reporting • Storage integration using SMI-S • Printing reports • Reference information • Reporting views Viewing storage array capacity HP SIM enables you to view capacity details for either a single storage array or all arrays. Viewing storage capacity for all arrays To view storage capacity for all arrays, run the Storage Device Capacity-All Storage Arrays report. For instructions, see “System reporting”. Viewing storage capacity for a single array 1. 2.
PAGE 273
• HP SIM determines device health status by polling the SMI-S providers of storage systems. If HP Storage Essentials discovers a storage array, storage switch, or tape library by a method other than SMI-S, HP SIM lists the device's status as Unknown. • System properties edited in HP SIM are not transferred to HP Storage Essentials. • The Suspend or Resume Monitoring command has no effect on HP Storage Essentials systems.
PAGE 274
• Large Business • Enterprise Business Varying combination of internal disks, RAID, and some SAN or NAS Mostly large SAN or NAS, but some RAID and internal disks might be present HP SIM can retrieve the information for the internal disk drives for monitored systems. This does not mean that HP SIM actively manages and configures each system previously indicated. HP SIM can: • Discover and identify storage systems that are directly attached to a server.
PAGE 275
• • • • Firmware version • Controller characteristics RAID details • RAID type • RAID configuration SAN and NAS • Network addresses • Manufacturer • Model IS and MNHA • Part number • Total number of disks • Disk details • Servers being serviced by this system Related procedures • Discovering storage using SNMP • Using HP SIM with SNMP storage solutions Related topics • System Page • About storage discovery using SNMP • System Page About storage discovery using SNMP Discove
PAGE 276
Related topic ▲ System Page Discovering storage using SNMP The HP SIM 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 HP SIM must be permitted to access the web server.
PAGE 277
• HP StorageWorks Command View ESL ESL • HP StorageWorks Tape Libraries • HP StorageWorks Management Appliance Search for Web Agent == Management module hp_OpenView_Storage_Management_Appliance or Web Agent == Management Module OpenSANManager Search for Web Agent == HP StorageWorks Command View Search for system type == storage device Event collection and launch To receive events, the Command View software must be configured to send SNMP events to the HP SIM CMS.
PAGE 278
Where PID is the process ID returned by the previous command. 5. Restart the SNMP daemon by entering the following at a shell command prompt: snmpd Loading the HSV MIB on the CMS for EVA 1. 2. 3. On a Windows operating system, go to a command prompt. Navigate to \Program Files\HP\System Insight manager\mibs directory. For more information about MIBs, see “Registering a MIB”. Run mxmib -a cpqhsv110v3.cfg.
PAGE 279
12 Managing with tasks HP SIM enables you to manage systems and events by scheduling and executing tasks. Tasks are actions performed using an HP SIM tool. Task instances are an executed single instance of a task. Users can: • Create a variation of a task. • Schedule a task. • Modify a task.
PAGE 280
NOTE: HP does not recommend scheduling a polling task based on periodic event collection. The task would run on the set of systems for each event in the associated collection. NOTE: If you remove a hardware status polling task, systems continue to be discovered, but the status on them is not updated. If you remove the Daily System Identification task, you would no longer detect changes in management on systems.
PAGE 281
In some installations there might be high volumes of events. If so, consider using this task and event collections as models and creating an event collection for events older than 30 days (for example), and then creating a task to delete events older than 30 days. Hardware Status Polling for Non Servers This task collects status information through management protocols (SNMP, WBEM, and so on) for systems that are not Server, Cluster, or Management Processor type.
PAGE 282
• Running a scheduled task • Editing a scheduled task Related topic ▲ Navigating the All Scheduled Tasks page Creating a task NOTE: Scheduled task results are retained for 30 days or a maximum of ten results for a given task. Run Now task results are retained for one day (24 hours). These are default values. To customize these values, see “Configuring task results settings”. 1. Select a tool from the HP SIM menu.
PAGE 283
Selecting View Contents displays the Table View or Tree View of the selected item and the Apply button is disabled. Note: When View Contents is selected, the Target Selection Page displays a barbershop pole and the message "Loading Data..." while the Table View or Tree View loads. After you select items from the displayed Table View or Tree View, the Apply button is enabled.
PAGE 284
7. 8. Click Next and specify tool parameters. If the tool does not require parameters, Next is replaced with Schedule and Run Now. The Schedule option is present if the tool can be scheduled. Select one of the following options: • Click Previous to return to the previous screen. • Click Schedule to schedule when the task runs. For more information about scheduling options, see “Scheduling a task”. • Click Run Now to run the task immediately.
PAGE 285
3. Under the When would you like this task to run? section, select one of the following options: • Periodically Select from intervals of minutes, hours, days, weeks, or months. With periodic scheduling, you can configure the task to run until a certain date and time or to execute only a set number of times. Periodic scheduling allows time filters to be applied. These filters specify the hours of the day when a scheduled task can operate.
PAGE 286
Running a scheduled task 1. 2. From the tool menus, select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks appear in the workspace. Select a task from the list, and then click Run Now. Note: If an instance of the task is running, the Run Now button is disabled. Editing a scheduled task 1. 2. 3. Select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks page appears. From the All Scheduled Tasks page, select the task to be edited. Click Edit.
PAGE 287
Viewing task results 1. 2. 3. 4. From the menu, select Tasks & Logs→View Task Results. Select a task. To stop or delete a task instance, select a task instance from the View Task Results page. Click Stop or Delete. The Task Results page displays a list of task instances created by all tasks. Viewing task instance results From the Task Results page, select a task instance by selecting a row from the Task Instances list.
PAGE 288
• The Stderr tab This tab displays information if the executable experienced an error. This tab does not appear for discovery task results. • Files Copied tab This tab displays what files are in the process of being copied or have been copied to the target system. This tab is not present for tools that do not perform any file copies to their target systems. To view target details: 1. From the Task Instance Results section, select a target system from the table below the Summary Status.
PAGE 289
Stopping a task attempts to interrupt In Progress commands. Canceling stops pending systems from starting and enables Running or In Progress commands to complete. Related procedures • Running a scheduled task • Editing a scheduled task • Deleting a scheduled task • Printing reports • Viewing task results Related topics • Scheduling a task • Task results list • Navigating the All Scheduled Tasks page Configuring task results settings HP SIM removes old tasks and jobs created by those tasks.
PAGE 290
Deleting task results 1. 2. Select Tasks & Logs→View Task Results and then select a task from the table. Click Delete. The task instance is deleted from the database. Note: If the task instance is running, a message appears, stating that you must stop the running task instance before it can be deleted. Task status types HP SIM reports the following summary status for tasks: • Failed. The task instance or task target instance failed and needs immediate attention. • Killed.
PAGE 291
• Owner. This field displays the user name that owns the task. • Command. This field displays the command used to run the task. • Target. This field displays the name of the target collection or systems that the task executed on. If you run a custom command tool or a MSA tool, this field displays the CMS system name. With custom command and MSA tools, the executables reside on the CMS and are run from the CMS to the remote system.
PAGE 292
Edit 1. 2. Select View All Scheduled Tasks. Select a task, and click Edit. The previously configured task information appears. 3. Edit the task, and then click Done. For more information, see “Editing a scheduled task”. Delete 1. 2. Select View All Scheduled Tasks. Select a task, and click Delete. For more information, see “Deleting a scheduled task”. Enable/Disable If the selected task is currently enabled, this button reads Disable and clicking it disables the task.
PAGE 293
13 Tools that extend management HP SIM provides you with the following powerful management tools: • Cluster Monitor • Command Line Tools • Custom Tools Use to create and manage custom tools that run on the CMS and on target systems. These tools can reference environment variables set by the tool to access system or event information. • Device Ping • Disk Thresholds Use to define the Normal, Minor, and Major ranges for disk utilization on monitored nodes and to set and remove disk thresholds.
PAGE 294
• Version Control Use to facilitate Software Update and tasks related to it. Uses HP Insight Management Agent, including HP Version Control Repository Manager HP Version Control Agent and other agents. • Webmin Use as a web-based interface for system administration for UNIX and Linux. Using HP SIM, you can set up user accounts, Apache, DNS, file sharing, and so on.
PAGE 295
• Installing RPM • Querying RPM • Uninstalling RPM • Verifying RPM • Accessing HP System Management Homepage • Editing system properties for a single system • Suspending or resuming system monitoring for a single system • Installing Software and Firmware • Accessing the Version Control Agent • Accessing the Version Control Repository Manager Related topics • Command line tools • Custom tools • Using Cluster Monitor • Device ping • Disk thresholds • Configuring DMI access • S
PAGE 296
Customizing the Quick Launch menu 1. 2. Click Customize in the Quick Launch menu. The Customize Quick Launch page appears. Select a menu category from the Available tools from dropdown list. All available tools from that menu are listed. 3. Select tools to add to the Selected tools list and click . To remove tools from the Selected tools list, highlight the tools to remove and click Click 4. or . to arrange tools in the list.
PAGE 297
Related procedure ▲ Searching for tools Searching for tools 1. Click Tool Search in the Search panel. The Tool Search page appears. The HP SIM menu structure appears on the main page. 2. 3. Click the icon to expand the tree, or enter text in the Search for box. After you locate a tool, click the tool link to be taken to the tool page. Related topic ▲ Tool search Using Cluster Monitor 1. Access the Cluster Monitor page by using one of the following methods: • Method 1: 1.
PAGE 298
The Cluster Monitor page appears for that cluster. 2. Select from the following tabs available on the Cluster Monitor page. Every tab includes a Problem Info section that provides details about problems reported on the tab. For example, on the Cluster tab, this section includes status information if the cluster has a status of anything other than Normal. Each tab also includes a Last Update field that displays the last time the information on the tab was updated.
PAGE 299
then select Polling again. The new polling values appear. Regardless of when you click OK after setting the polling or thresholds values, these values are saved and do not reset to the original value, which is the same when setting thresholds. 6. Click OK to save the changes.
PAGE 300
Cluster Monitor Network tab Use the Cluster Monitor Network tab to view the following information for MSCS clusters: • Status The network status (Critical, Major, Minor, Normal, Disabled, or Unknown). For more information about network status types, see “System status types”. • Name The server cluster object that carries internal communication between nodes and provides client access to cluster resources. • Mask The subnet mask associated with the network within the cluster.
PAGE 301
for load balancing and other administrative purposes. When a failure takes place, the entire group fails over, prompting the cluster software to transfer all group resources and data to a different node in the cluster. The resources and data in a transferred (failed-over) group are still accessible under the same network name and IP address, even after they are moved to a different node.
PAGE 302
Cluster Monitor states NOTE: The cluster condition is Other when all nodes of a cluster are down. List Normal Degraded Node The node status is an active cluster member. The node status is down, The node status is down is trying to reform or or is trying to form or rejoin a cluster, is rejoin a cluster. operating as an active member of a cluster but cannot host resources or resource groups, or is up but cluster activity is paused. The node status is Unavailable or could not be determined.
PAGE 303
Cluster Monitor polling rate NOTE: You can specify only one polling rate (interval) for all nodes in all clusters. You cannot specify different rates for different nodes, so the polling fields appear on the configuration page only when you select All in both Cluster and Node dropdown lists. CPU polling rate The CPU polling rate determines how often Cluster Monitor checks CPU utilization as reported by the appropriate HP Insight Management Agent on monitored nodes.
PAGE 304
CPU utilization thresholds Use the CPU resource to collect utilization data for CPUs in a cluster. To access the Cluster Monitor - Node Resource Settings page where the thresholds are set, select Options→Cluster Monitor→Node Resource Settings. The threshold values you enter in the Settings for the Selected Resource section define the Normal, Minor, and Major ranges for CPU utilization on the selected node. For each CPU, there are four thresholds in pairs.
PAGE 305
The Configure or Repair Agents tool enables you to repair Simple Network Management Protocol settings and trust relationships that exist between HP Systems Insight Manager and target systems if you have 7.2 agents or later installed. If you have 7.1 agents or earlier installed, you can update Web Agent passwords on target systems. This tool adds the security and trap community strings and trust settings to the target systems, but it does not replace existing settings.
PAGE 306
You can install Insight Management Agents or providers, either WBEM or SNMP, on managed systems so that HP SIM can collect inventory and status information from these systems and receive event notifications from the systems. Installation is supported only on ProLiant or Itanium-based servers with a Windows operating systems. From the Step 2: Install Providers and Agents (Optional) page: a. b. c. d. e.
PAGE 307
Supported systems HP ProLiant Agent OpenSSH Version Control Agent System Management Home Page ProLiant systems 2.2.1.0 (64-bit) with 64-bit Windows operating system (2003, 2008) 8.2.0.0 (64-bit) 5.1p1-3 2.1.10.801 2.1.15.210 ProLiant systems Not supported with 32-bit Windows operating systems (2000) 7.60 (32-bit) 5.1p1 2.1.8 2.1.8.780 Itanium-based 6.1.0.0 systems with Windows operating system (2003) 5.1.10 5.1p1-3 2.1.7.770 2.1.8.179 4.
PAGE 308
NOTE: 5. Installation with reboot typically takes about 8 minutes. Click Next. The Step 3: Configure or Repair Agents page appears. NOTE: The Step 3: Configure or Repair Agents page changes to show the configuration options available with the installed plug-ins. 6. Configure the target system by selecting one of the following options: • Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or HP-UX system to send WBEM indications or events to HP SIM.
PAGE 309
NOTE: This indication will appear as an Informational Event in the Event List of HP SIM. If you do not receive test WBEM indications in the Event List, see “Troubleshooting”. NOTE: This indication is supported only on HP-UX and Windows managed systems with WBEM provider installed. • Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to manage the system This option deploys a WBEM certificate to the managed system and is only valid for HP-UX systems.
PAGE 310
HP-UX systems do not require a Read Write community string. The Read Write community string is added on Windows systems only. b. c. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems SNMP Trap Destination List. This setting enables the target systems to send SNMP traps to this instance of HP SIM.
PAGE 311
• Configure Version Control Agent (VCA) Select this option to configure the HP VCA to point to the HP VCRM, where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, HP-UX, and Linux. To configure HP VCA: 1. 2. 3. 4.
PAGE 312
a. Select one of the following options: • Use sign-in credentials. These credentials must be a privileged account on the managed system. NOTE: This option is not available if you selected any options on the “Step 2: Install Providers and Agents (Optional)” page. • b. c. d. e. 9. In In In In Use the following credentials for all systems. the the the the User name field, enter the system administrator name. Password field, enter the system administrator password.
PAGE 313
NOTE: a tool. 2. 3. The Step 1: Verify Target Systems page appears if you select the targets before selecting Select target systems. For more information, see “Creating a task”. Click Next. The Step 2: Install Providers and Agents (Optional) page appears. Most of the options apply only to ProLiant or Itanium-based Systems with Windows operating systems. For Linux systems, select Install Linux PSP or ESX Agents.
PAGE 314
5. Configure the target system by selecting from the following options: • Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or HP-UX system to send WBEM indications or events to HP SIM.
PAGE 315
is composed of over 30 characters to include letters and numbers, and is visible only to the user with administrator privileges for that system. This Read Write community string is required by the Web Agent to perform certain threshold setting capabilities. This community string is used locally only on the target system and is not used by HP SIM over the network. Linux and HP-UX systems do not require a Read Write community string. The Read Write community string is added on Windows systems only. b. c.
PAGE 316
NOTE: For systems with Management HTTP Server 4.x and earlier, Configure or Repair Agents adds the Administrator password in the Management HTTP Server store and modifies the SNMP settings but cannot change trust relationship information. Select the checkbox beside Import Secure Sockets Layer (SSL) certificate for HP SIM to trust the HP SMH of the managed system. This option is only valid for HP-UX and Linux operating systems.
PAGE 317
7. From the Step 4: Enter credentials page, enter the following credentials. The credentials used in this step must work for all selected target systems. HP recommends using domain administrator credentials. Credentials entered here are not saved by HP SIM except to run a scheduled task later. a. Select one of the following options: • Use sign-in credentials. These credentials must be a privileged account on the managed system.
PAGE 318
The WMI Mapper makes it possible to retrieve WMI instrumented data on a Windows machine through WBEM requests. The Windows version of HP SIM installs this WMI Mapper locally so that it can make WMI requests across the network to the systems without the need to install the WMI Mapper on the managed Windows systems. The WMI Mapper is included in a Typical installation of the HP SIM on a Windows CMS (optional in a Custom installation) . For HP-UX and Linux-based systems, the WMI Mapper is not available.
PAGE 319
Related procedures • Setting protocols and credentials for a system or groups of systems • Setting protocols for a single system • Setting global protocols • Deploying OpenSSH to multiple systems using RDP • Installing OpenSSH Related topics • Global protocols • Configuring or repairing agents Learn more: Install Linux PSP or ESX Agents • Linux PSP or ESX Agents Are a collection of SNMP agents used by HP SIM to gather information from managed systems and send traps to HP SIM.
PAGE 320
HP Version Control Repository Manager HP VCRM is an HP Insight Management Agent that manages a directory of HP software and firmware components. You can use HP VCRM without HP VCA to provide a listing of available software and firmware to load on the local machine. HP VCRM is part of the HP Foundation Pack. HP VCRM is designed to be used in a one-to-many configuration with a HP VCA installed on each managed HP system to manage installed HP software and firmware.
PAGE 321
• Windows CMS • HP-UX and Linux CMS Learn more: Configuring SNMP Select Set read community string to specify a community string. By default, the first HP SIM community string that is not public appears. If no community string exists in HP SIM, you must enter one. NOTE: If you configure only HP-UX systems with default SNMP installations, you do not need to set this option. HP-UX enables read by default (get-community-name is set to public by default on HP-UX systems).
PAGE 322
Learn more: Configuring VCA Configure Version Control Agent (VCA) Select this option to configure the HP VCA to point to the HP VCRM, where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, HP-UX, and Linux.
PAGE 323
5. The Step 3: Configure or Repair Agents page enables you to select options to configure the target system. • Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or HP-UX system to send WBEM indications or events to HP SIM.
PAGE 324
NOTE: This indication will appear as an Informational Event in the Event List of HP SIM. If you do not receive test WBEM indications in the Event List, see “Troubleshooting”. NOTE: This indication is supported only on HP-UX and Windows managed systems with WBEM provider installed. • Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to manage the system This option deploys a WBEM certificate to the managed system and is only valid for HP-UX systems.
PAGE 325
HP-UX systems do not require a Read Write community string. The Read Write community string is added on Windows systems only. b. c. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems SNMP Trap Destination List. This setting enables the target systems to send SNMP traps to this instance of HP SIM.
PAGE 326
• Configure Version Control Agent (VCA) Select this option to configure the HP VCA to point to the HP VCRM, where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, HP-UX, and Linux. To configure HP VCA: 1. 2. 3. 4.
PAGE 327
NOTE: This option is not available if you selected any options on the “Step 2: Install Providers and Agents (Optional)” page. • b. c. d. e. 8. In In In In Use the following credentials for all systems. the the the the User name field, enter the system administrator name. Password field, enter the system administrator password. Password (Verify) field, re-enter the system administrator password. Domain field, enter the Windows domain if you are using a domain account.
PAGE 328
• • • Successfully configured SSH for host based authentication. • Successfully configured SSH for user based authentication. Minor • SNMP is not installed on this system, so no SNMP settings were altered. To install SNMP, go to Control Panel and add the Windows component of Simple NetWork Management Protocol. • SNMP READ-ONLY community string not updated because it already exists with different rights. • Unable to create an SNMP READ-WRITE community string needed by the HP Web Agent.
PAGE 329
Related topic ▲ Configuring or repairing agents Custom tools Custom tools are executed on the CMS and on target systems. They can be scripts, batch files, or executables that can reference environment variables set by the tool in order to access system or event information. For example, creating a custom tool to launch Notepad. You can create or launch SSA, MSA, and WLA tools. You can create the following types of custom tools: • Remote tool A tool that runs on selected target systems.
PAGE 330
Use custom tools that run on target SSA systems create a temporary .XML tool definition file under /var/tmp, the loads the tool with the mxtool -af filename. You enter only data in required fields. WARNING! If you define a custom tool to run as root, any user authorized to run the tool might gain full access to the managed system, depending on how you define the command, and what its capabilities are.
PAGE 331
Related topic ▲ Environment variables for custom tools Creating a remote tool 1. 2. 3. 4. Select Tools→Custom Tools→New Custom Tool. The New Custom Tool page appears. Select Remote tool. Click Next. The Describe how the new custom tool will work page appears with the tool type and description displayed. Under Tool Parameters, enter the following information: a. In the Name field, enter the command name. Custom tool names must be at least one character, and no more than 255 characters in length.
PAGE 332
5. 6. Specify the user account on the target system by selecting one of the following options: • Logged-in user • Special user For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not run on targets with an unknown operating system. • Specific user The tool uses the user account that is logged in. The tool uses the specified user account.
PAGE 333
1. 2. 3. 4. Select Tools→Custom Tools→New Custom Tool. The New Custom Tool page appears. Select CMS tool. Click Next. The Describe how the new custom tool will work page appears with the tool type and description displayed. Under Tool Parameters, enter the following information: a. In the Name field, enter the command name. Custom tool names must be at least one character, and no more than 255 characters in length. The first character of the name must be alphabetic.
PAGE 334
5. 6. Specify the user account on the target system by selecting one of the following options: • Logged-in user • Special user For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not run on targets with an unknown operating system. • Specific user The tool uses the user account that is logged in. The tool uses the specified user account. In the Command with parameters field, enter parameters. The interface supports nine parameters.
PAGE 335
1. 2. 3. 4. 5. 6. 7. 8. 9. Select Tools→Custom Tools→New Custom Tool. The New Custom Tool page appears. Select Web page tool. Click Next. The Describe how the new custom tool will work page appears with the tool type and description displayed. Under Tool Parameters, enter the following information: a. In the Name field, enter the command name. Custom tool names must be at least one character, and no more than 255 characters in length. The first character of the name must be alphabetic.
PAGE 336
The following options are available for managing custom tools: • “New” • “Edit” • “View tool definition” • “Run Now/Schedule” • “Delete” New Use create a custom tool and open the Select the tool to create page. Edit Use to edit an existing custom tool. Select the tool, and then click Edit. The Edit Custom Tool Details section appears. You can edit all fields and add or delete environment variables. View tool definition Use to display the XML code for the tool.
PAGE 337
4. 5. Specify the user account on the target system by selecting one of the following options: • Logged-in user • Special user For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not run on targets with an unknown operating system. • Specific user The tool uses the user account that is logged in. The tool uses the specified user account.
PAGE 338
b. c. d. 4. 5. Subsequent characters can be letters, digits, spaces, or any of the following: "-", ".", "(", ")" or "_". In the Description field, enter the information for the tool. In the Help comments field, enter comments for the tool. In the Menu placement field, enter the full path (from the root of the HP SIM console) and the file name of the tool (for example, c:\custom code\romflash.bat).
PAGE 339
c. d. 4. 5. 6. 7. 8. In the Help comments field, enter comments for the tool. In the Menu placement field, enter the full path (from the root of the HP SIM console) and the file name of the tool (for example, c:\custom code\romflash.bat). Specify the user account on the target system by selecting one of the following options: • Logged-in user • Special user For UNIX and Linux systems, root; for Windows systems, Administrator. The tool does not run on targets with an unknown operating system.
PAGE 340
Removing and restoring custom tools Removing a tool The Remove a Tool tool removes a tool from the menu for all users in HP SIM. The tool name must match the name in the tool definition file. CAUTION: This tool can remove any tool, including tools supplied by HP. To remove a tool from HP SIM: 1. 2. 3. Select Options→Remove a Tool. The Remove a Tool page appears. Under Parameters, add information using standard tool parameters. Tool name is the only required field.
PAGE 341
• 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.
PAGE 342
RELATIONSHIP%d. The relationship string with the associated system, and %d is the iteration number. For example: IF, RELATEDDEVICECOUNT = 2 Then, RELATIONSHIP0=ServerToEnclosure RELATIONSHIP1=VMGuestToVMHost Related procedure ▲ Creating a CMS tool Related topics • Custom tools • Managing custom tools Examples of using parameter strings in custom tools The URL strings for web-aware tools and command line tools must be provided as absolute URLs beginning with http:// or https://.
PAGE 343
Related topics • Command line tools • Managing custom tools Custom tools reference Tool types • SSA tools These are executed on a target system and are only aware of the target system environment. Therefore, when executing an SSA tool, the DTF sends the tool information to each HP SIM agent to execute the tool. An example of an SSA tool is a tool that wraps a common UNIX command, such as ls, cat, or cp. • MSA tools These are executed on a CMS, and can handle a list of target systems.
PAGE 344
Parameter Description %n Network name (host name, IP address, or system name in that order). %a Network address (IP address). %l Link name in format specified by System Link Configuration setting (name, IP address, or full DNS name). %p IP address of WBEM proxy, if any, for this target, in the form :. %g Database GUID of the target system (or system group, if the %x toggle was in the string). %b System type of the target system.
PAGE 345
passed. To do this, the tool specifies in a system filter expression the system attributes that must be possessed by all systems it can run on. NOTE: If a tool cannot be launched for selected systems, an error message appears with information about why the tool cannot be launched.
PAGE 346
An include filter includes one or more system filter expressions using the attributes names allowed for it. For example, an os filter could consist of: The include filter does not need to include all attributes allowed.
PAGE 347
This tool could be launched on any collection of systems using Linux or HP-UX. Tool filtering depends on the attributes having a value defined on the systems selected.
PAGE 348
Document type definition The DTD file defines the constraints for an XML file. These constraints include the valid element tags, attributes, and the cardinality of elements in an XML file. The tool DTD file is named toollist.dtd and is included in the following paragraph. Note that because of manpage formatting, the DTD contents might not appear the same as in the file.
PAGE 349
specifies whether the results of the command will be kept in this system's job log. This attribute applies only to tools when they are run as scheduled tasks, not when they are run as "run now" tasks. When job-log="true" the job and target status for the tool will be kept for a relatively lengthy system-defined period in the database after the job completes.
PAGE 350
(NOTE: The role-enabled and role elements are deprecated elements and should not be used with this product. These are provided for backward compatibility with previous products. The toolbox-enabled element and the toolbox element should be used in their stead.) If more than one of these elements are specified, the element must appear in the order as listed in this definition. The msa-command-tool element must contain an msa-block element.
PAGE 351
MSA command, the parameters for the command and an execution system on which the command executes. -->