HP Systems Insight Manager 5.2 Technical Reference Guide HP Part Number: 356920-401 Published: February 2008 Edition: 5.
© Copyright 2003-2008 Hewlett-Packard Development Company, L.P.
Table of Contents 1 Legal notices............................................................................................29 Warranty.............................................................................................................................................29 Restricted rights legend..........................................................................................................................29 Copyright notice...................................................................
Signing in using Secure Sockets Layer...........................................................................................46 Logging in to the CLI........................................................................................................................47 Logging in to the CMS directly.....................................................................................................47 Using an SSH client to log in remotely.................................................................
CMS locale...............................................................................................................................84 Target locale..............................................................................................................................84 Using command line interface commands................................................................................................85 manpages......................................................................................
Deleting a hosts file........................................................................................................................119 Adding systems in a hosts file to the HP SIM database........................................................................119 Creating a task to import a hosts file for HP SIM integration................................................................120 Importing the .dat file......................................................................................
Command line interface............................................................................................................154 Deleting authorizations...................................................................................................................154 Command line interface............................................................................................................154 Authorizations report.................................................................................
Requesting the HP SIM certificate...........................................................................................183 Onboard Administrator configuration.....................................................................................183 HP StorageWorks Command View EVA configuration...............................................................183 HP SIM configuration...........................................................................................................
Selection............................................................................................................................210 Health status.......................................................................................................................210 Management processor........................................................................................................211 Software status................................................................................................
Cluster Address...................................................................................................................232 Cluster Type........................................................................................................................232 Cluster Description...............................................................................................................232 Buttons.....................................................................................................
Software and firmware criteria....................................................................................................256 Cleared state criterion...............................................................................................................257 Server role criteria....................................................................................................................257 Assignee criteria...................................................................................
Hardware Status Polling for Systems No Longer Disabled....................................................................279 Initial Data Collection.....................................................................................................................279 Initial Hardware Status Polling.........................................................................................................279 Software Version Status Polling.......................................................................
Command line interface.................................................................................................................305 Configuring or repairing agents............................................................................................................305 Overview......................................................................................................................................305 Windows CMS.........................................................................
License manager.................................................................................................................................357 About licenses...............................................................................................................................358 Collecting license information..........................................................................................................359 Viewing licensed systems.......................................................
Configuring the firewall on a Windows system........................................................................387 Configuring the firewall on an HP-UX system...........................................................................387 Configuring the firewall on a Linux system...............................................................................388 Installing and configuring protocols..................................................................................................
RPM Package Manager.......................................................................................................................419 Installing RPM................................................................................................................................420 Uninstalling RPM............................................................................................................................420 Querying RPM....................................................................
Ports..................................................................................................................................445 LUNs......................................................................................................................................445 System tab for a storage switch........................................................................................................445 Product Description.........................................................................
Configuration management........................................................................................................480 Workload management.............................................................................................................481 Remote server management.......................................................................................................481 HP Integrity Essentials for Windows..................................................................................
HP Service Essentials Remote Support Pack.............................................................................................496 Overview......................................................................................................................................496 Remote Support Software Manager.............................................................................................497 Remote Support tool.................................................................................
R_Inventory.........................................................................................................................519 R_lockdownStatus................................................................................................................520 R_LogicalDisks....................................................................................................................520 R_MediaAccessDevices..........................................................................................
Clearing events.............................................................................................................................552 Deleting events .............................................................................................................................553 Configuring event filters for registered SNMP traps.............................................................................553 Configuring SNMP traps.....................................................................
Command line interface............................................................................................................585 System properties................................................................................................................................585 Editing system properties for a single system......................................................................................586 Examples......................................................................................
Menu................................................................................................................................................633 OpenSSH..........................................................................................................................................633 Operating system................................................................................................................................634 Paging notification............................................
CIM_iSCSISession table..................................................................................................................670 SCSIProtoEnd_iSCSISession table.....................................................................................................670 SCSIProtoEnd_NetworkPort table......................................................................................................670 CIM_LogicalDevice table.............................................................................
HP_NParCabinet table...................................................................................................................702 HP_NParCell table.........................................................................................................................702 HP_NParComplex table..................................................................................................................703 HP_NParIOChassis table.......................................................................
List of Tables 4-1 12-1 12-2 Version Support Matrix for components used for install.........................................................................71 Version Support Matrix for components used for install.....................................................................307 Version Support Matrix for components used for install.....................................................................
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.
2 Introduction Online help HP Systems Insight Manager (HP SIM) provides an online help system to help you become familiar with its management features. It provides general information about using and administering HP SIM. Click the question mark icon on any page or use the Help menu to view the online help. HP SIM help categories The HP SIM help system covers the following categories: • Product overview Provides you with an overview of the features in HP SIM. See “Product overview” for more information.
3 Product overview HP Systems Insight Manager (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.
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 Secure Shell (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.
system software, and enables system software updates across groups of servers. For HP-UX systems, Software Distributor is integrated into HP SIM. • HP Service Essentials Remote Support Pack HP SIM includes a new HP Service Essentials Remote Support Pack plug-in. This plug-in leverages elements of the HP Service Essentials Remote Support Pack (Remote Support Pack) technology and provides integrated HP SIM and Remote Support Pack capability.
• ProLiant ML310 G4 servers • Integrity rx7620 servers • Integrity rx7640 servers • Integrity rx8620 servers • Integrity rx8640 servers • Integrity Superdome servers Note: The Integrity Superdome includes support for the Intel Itanium 2 Montecito, M9M, and MX2 processors. • Ultra 160 SCSI Adapter • HP NC370i NIC • rx8620 Gigabit LoM (5701) NIC • rx8640 Gigabit LoM (5703) NIC • LAN/SCSI Combo Card (Castor, AB290A) The following new operating systems are supported on PMP 4.
physical-to-ProLiant (P2P) migrations. SMP Universal enables you to simplify the server consolidation process. To purchase additional licenses, see http://www.hp.com/go/migrate. • HP BladeSystem Integrated Manager in HP Systems Insight Manager HP SIM delivers a blade environment designed to consolidate access to blade deployment, configuration, and monitoring tools. Picture views are available of racks and enclosures. The HP BladeSystem Integrated Manager is automatically installed with HP SIM.
• Automatic installation of HP SIM is now supported for x64 bit operating systems • Replaced Postgres SQL with HPSMDB First Time Wizard • Streamlined the application by enabling you to specify the operating systems that are managed in your environment, resulting in collections, reports, and tools for the selected operating systems only. • Ability to automatically configure managed systems as discovery runs. • Ability to test email configurations as e-mail settings are configured.
NOTE: The iCAP provider is available on HP-UX 11i v3 (11.31), HP-UX 11i v2 (11.23) and HP-UX 11i v1 (11.11) which can only be installed on HP 9000 and Integrity servers. • Added Horizontal discovery of node partitions (nPars) for cell-based Integrity servers or HP 9000 servers. • Added Horizontal discovery of virtual partitions (vPars) for cell-based HP-UX 9000 servers or procedure-based HP-UX 9000 servers.
Related topics • Tool search • Quick Launch menu • Discovery and identification • Assistance • Features Product architecture HP Systems Insight Manager (HP SIM) leverages a distributed architecture that is divided into three types of systems: Central Management Server (CMS), managed systems, and web-browser clients. The CMS with the managed systems together are called the HP SIM management domain . Central management server Each management domain has a single CMS.
• Legal notices • Getting started Assistance Additional resources For additional HP Systems Insight Manager (HP SIM) resources, see: • HP SIM website at http://www.hp.com/go/hpsim/ for general product information and links to software downloads, documentation, and troubleshooting information • HP Technical Documentation website at http://www.docs.hp.com/ for access to HP SIM manuals and release notes • HP Software Depot website at http://www.software.hp.
• Operating system type and revision level • Detailed questions NOTE: For continuous quality improvement, calls may be recorded or monitored. Technical FAQs http://h18013.www1.hp.com/products/servers/management/hpsim/techsupport.
4 Getting started If you are getting started with HP Systems Insight Manager (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.
NOTE: 1. 2. 3. 4. 5. 6. You must be connected to the Internet to register HP SIM. The Registration window appears automatically during installation on Windows systems, and when you sign-in to HP SIM if you have not already registered. If the Registration window is not already open, select Options→Registration. Click Register Now. The HP Systems Insight Manager License page appears. Click Receive for free. The HP Systems Insight Manager Registration page appears. Enter the requested information.
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 is displayed 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.
NOTE: Browsing locally from the CMS itself does not perform automatic sign-in; you must enter your credentials on the sign-in page. • There must be no proxy servers between the browser and the CMS. Use the proxy bypass list in the browser, or use no proxy at all. • The browser must be configured to support automatic sign-in. In Internet Explorer, enable Integrated Windows Authentication under Tools→Internet Options→Advanced tab.
After you have an SSL session established with HP SIM, all communications between the browser and HP SIM are secure through SSL. Logging in to the CLI You can access the HP SIM CLI directly from the Central Management Server (CMS) or from any network client using SSH client software. NOTE: On an HP-UX or Linux CMS, you can log in to the operating system as any valid HP SIM user and use the CLI.
• Using command line interface commands • Networking and security Signing out Be sure to sign out from HP Systems Insight Manager (HP SIM) to prevent unauthorized access to your active session while you are away. If you are monitoring HP SIM, your session remains active and continually refreshes, unless you close the browser or navigate to another website. If you navigate to another browser, HP SIM signs you out after 20 minutes. As long as you are actively working in HP SIM, your session stays active.
• SNMP Enter the read community strings to use for all newly discovered systems. Community strings establish the authentication that enables communication between HP SIM and a managed system. This information is required to discover systems that use the SNMP management protocol. See “Global protocols” for more information about WBEM and SNMP. • Discovery Use the wizard to enable discovery, set up the discovery schedule, and enter the IP address ranges or host names of the systems you want to discover.
NOTE: These settings can be changed at any time, and the hidden collections, tools, and reports can be made visible again. To change these settings from the HP SIM menu, select Options→ Managed Environment. 1. 2. Select the operating systems for the CMS to manage. Click Next to go to the next First Time Wizard step, or click Previous to return to the previous step.
2. • FC HBA • SCSI HBA • IOTree • LVM (root required only for Physical Volume Group information) In the WMI Mapper Proxy section, enter the mapper proxy Hostname and Port Number. If a WMI Mapper Proxy has already been discovered, it appears here. If you have selected not to manage Windows systems on the previous page, this section is not displayed. 3. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous to return to the previous step.
• Configuring the managed environment • Entering WBEM settings • Enabling automatic system discovery • Configuring managed systems • Configuring e-mail settings • First Time Wizard summary • Setting global protocols Related topics • Using the First Time Wizard • Finishing the First Time Wizard • Operating-system-specific collections, reports, and tools • Global protocols • Protocols Enabling automatic system discovery HP Systems Insight Manager (HP SIM) uses automatic discovery to fi
• 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 enables you to configure managed systems as they are discovered and to specify parameters for running the Configure or Repair Agents.
• Using the First Time Wizard • Operating-system-specific collections, reports, and tools • Global protocols • Protocols Configuring e-mail settings To use the First Time Wizard to configure HP SIM to send e-mail notifications through automatic event handling: 1. 2. 3. Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS uses to send e-mail notifications.
See “Performing initial setup” and “Setting up managed systems” for more information about setting up HP SIM and managed systems.
• Performing initial setup • Administering systems and events • Protocols • Data collection • 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 Systems Insight Manager (HP SIM) UI (Options→Managed Environment).
• I-O Devices - HP-UX • Logical Memory Details - HP-UX • Operating System Details - HP-UX The following reports have no data for HP-UX and are removed if HP-UX is the only selection. • Batteries • System License Info • Logical Disk Drives • Installed Controllers • Physical Disk Drives Operating-system-specific tools The following section lists HP SIM tools (by menu path) that by operating system.
• Configure→Management Processor→HP Integrity or HP 9000 iLO and all tools listed here (New User, Modify User, Delete User, LAN Access, LDAP Settings, Firmware Upgrade, iLO Control, and Deploy SSH Public Key). • Tools→Integrated Consoles→Webmin. Other ▲ Tools→Command Line Tools→Unix/Linux and all tools listed here (bdf, cat, cp, df, find, ls, my, ps, rm).
Configuring the managed system software The HP SIM Configure or Repair Agents tool is a quick and easy way to configure Linux, HP-UX and Windows managed systems to communicate with HP SIM from a Linux CMS. NOTE: It is possible to manually configure Linux systems. See Setting up Linux managed systems manually. To run Configure or Repair Agents remotely against multiple systems simultaneously, you must have authorizations to run the Configure or Repair Agents tool.
d. Edit the snmpd.conf file using any text editor. For Red Hat Linux, run the following command for opening this file in the vi editor: vi /etc/snmp/snmpd.conf For SUSE SLES 8, run the following command for opening this file in the vi editor: vi /usr/share/snmp/snmpd.conf i. Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS: trapsink IPaddress where IPaddress is the IP address of the CMS. ii.
HP-UX CMS Installing the required software on an HP-UX system Use the following checklist as a guideline to assist you with setting up managed systems from an HP-UX Central Management Server (CMS): 1. Understand the basic managed system software for HP-UX. For HP-UX, the following software, shown with minimum recommended versions, is required for essential HP Systems Insight Manager (HP SIM) functionality to operate.
Configuring the managed system software The HP SIM Configure or Repair Agents tool is a quick and easy way to configure Linux, HP-UX and Windows managed systems to communicate with HP SIM from an HP-UX CMS. NOTE: It is possible to manually configure HP-UX systems. See Setting up HP-UX managed systems manually. To run Configure or Repair Agents remotely against multiple systems simultaneously, you must have authorizations to run the Configure or Repair Agents tool.
5. From the Step 2: Enter credentials page: a. In the User name field, enter the system administrator name. b. In the Password field, enter the system administrator's password for the user name previously entered. c. In the Password (Verify) field, re-enter the system administrator's password exactly as it was entered in the Password field. d. In the Domain field, enter the Windows domain if you are using a domain account.
7. The Step 3: Configure or Repair Agents page enables you to select options to configure the target system. The following options are available: • 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. For this section, the following must be considered: • Create subscription to WBEM events so that WBEM events will be sent to the CMS.
To enter the credentials for HP SIM to use to access the managed systems: 1. 2. 3. 4. In the User name field, enter a user name. In the Password field, enter the password for the user's name previously entered. In the Password (Verify) field, re-enter the password exactly as it was entered in the Password field. In the Domain field, enter the Windows domain if the target belongs to a domain.
Note: SSH can be configured only if the OpenSSH service is running on the managed systems. OpenSSH can be installed on Windows systems, by running the Install Open SSH as done in step three or by selecting the tool under Deploy→Deploy Drivers→Firmware and Agents→Install Open SSH. • Set Trust relationship to "Trust by Certificate". Select this option to configure systems to use the Trust by Certificate trust relationship with the System Management Homepage.
The Task Results page displays the following information: • Status. This field displays the details for each target system within a task instance. • Exit Code. This field represents the success or failure of an executable program. If the return value is zero or a positive value, the executable ran successfully. If a negative value is returned, the executable failed. This exit code does not indicate that all configuration attempts were successful. It is possible for some to succeed and for some to fail.
trap-dest: hostname_or_ip_address ii. Stop the SNMP Master agent and all subagents with the command: /sbin/init.d/SnmpMaster stop iii. Restart the SNMP Master agent and all subagents with the command: /usr/sbin/snmpd d. Configure DMI on the managed system by adding the Domain Name Service (DNS) host name of the CMS. Note: DMI must only be configured for HP-UX 11.0. i. Stop the DMI daemon on the managed system: /sbin/init.d/Dmisp stop ii. iii.
The EMSWrapperProvider displays. or cimprovider –ls The EMSWrapperProvider displays. Note: For more information regarding SFM, see HP System Fault Management Diagnostics. 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.
To run Configure or Repair Agents remotely against multiple systems simultaneously, you must have authorizations to run the Configure or Repair Agents tool. You must have full CMS configuration privileges to modify the HP SIM community strings in the system security file. In addition, you must enter administrator level user credentials for the target system. To configure agents remotely: 1. Select Configure→Configure or Repair Agents. The Step 1: Select Target Systems page appears.
6. You can install Insight Management Agents or providers, either Web-Based Enterprise Management (WBEM)or SNMP, on managed systems so 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 Windows operating system. From the Step 3: Install Providers and Agents (Optional) page: a. b. c. d.
Example: Installing Insight Management Agents on a ProLiant Windows 64-bit system: 1. 2. 3. Select system Type: server. Select system subtype 1: 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 installing, select the force reboot option. This allows the newly installed component to be completely initialized before configuring it.
8. The Step 4: Configure or Repair Agents page enables you to select options to configure the target system. The following options are available: • 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. For this section, the following must be considered: • Create subscription to WBEM events so that WBEM events will be sent to the CMS.
system and will be configured as the WBEM user in the System Protocol settings. This configuration step is not necessary if HP SIM is configured with a user with administration rights. This user is not created by HP SIM. The user should already exist as either a domain user or one local to the managed system. The user will be added to the "DCOM Users” group on the managed system and will be given read-only access to WMI information, plus read-write permissions to the HPQ name space.
• Configure secure shell (SSH) access. Select this option to configure SSH access on managed systems. If this option is selected, you must select one of the following options: • Host based authentication for SSH Note: For this option to work, the user name and password provided in step 2 must be an administrative level account. For Linux or HP-UX targets, it must be the "root" account and password.
a. b. 9. In the Password field, enter the new administrator password. In the Confirm Password field, re-enter the new administrator password exactly as you entered it previously. Click Run Now. The Task Results page appears. Note: Click Schedule to run this task at a later time. Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of which might have different results. The log results indicate whether the repair attempt was successful.
NOTE: The First Time Wizard starts the first time a user with administrative rights signs in to HP SIM. If the wizard is canceled before completion, it restarts each time a user with administrative rights signs in. You can cancel and disable the wizard from automatically starting by selecting the Do not automatically show this wizard again checkbox. The wizard can be manually started by selecting Options→First Time Wizard.
Related topics • Signing in • Signing out • Navigating the Home page • Configuring HP SIM with storage systems Navigating the Home page Graphical user interface features This section describes the GUI features. The following figure is a sample screen shot of the GUI. The GUI includes the following six regions: 78 1. Banner The banner provides a link to the Home page, a link to Sign Out of HP SIM, and displays the user that is currently signed-in.
5. Menus The HP SIM menus provide access to tools, logs, software options, and online help. The Options menu is primarily for users who administer the HP SIM software. If you lack authorization to use these tools, you might not be able to access certain menus. 6. Workspace The workspace displays the results of your latest request. It can contain a collection, tool, or report. Some tools launch a separate browser window or X Window terminal instead of displaying in the workspace.
NOTE: This option is used by some HP SIM partner applications 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 Note: The default introductory page is only available 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.
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.
The following are error messages that might be displayed: • 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 re-launch. • 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 be displayed if you have a pop-up blocker configured and running on your system.
The CMS also has another locale independent from any user sessions (see “Configuring HP SIM”), the CMS Locale. Some of the features inherit this locale, such as logging files and e-mail messages sent by Automatic Event Handling, which are neutral from any session.
Configuring Windows 2000 locale settings for Japanese 1. 2. 3. 4. 5. 6. Select Start→Settings→Control Panel→Regional Options→General. Click Set default. The Select System Locale window appears. From the dropdown list, select Japanese. Click OK. Click Apply. Reboot the system. After rebooting the system, open a command prompt window and execute the chcp 932 (Japanese) and chcp 437 (English) to toggle between the two languages.
or each execution system (for MSA tools, usually the CMS), HP has defined the format of some properties that can be added to the globalsettings.props file. These properties provide the character map encoding to use for each language on each operating system, what Code Page code to use for each language on a Windows target and execution system, and the string that defines that encoding in the LANG environment variable on a Linux or HP-UX system.
NOTE: The Windows path varies if HP SIM is not installed in the default location. See the Infrasctucture management using the HP SIM command line interface white paper at http:// h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html and the HP SIM 5.2 Command Line Interface Reference Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/ infolibrary.html for more detailed information on CLI commands.
and Windows, and 8 for Linux systems. The CLI XML usage manpage section number is 4 for all operating systems. Command Functionality Available manpages mcompile Compiles an SNMP Management Information Base (MIB) file into an intermediate format configuration (CFG) file for importing into HP SIM using the mxmib command.
Command Functionality Available manpages mxnodesecurity Adds, modifies, or removes security mxnodesecurity(1M, 8), credentials for SNMP and Web-Based mxnodesecurity(4) Enterprise Management (WBEM) protocols. Also verifies the certificate used for WBEM. mxoracleconfig Enables you to configure HP SIM to use an mxoracleconfig(1M, 8) Oracle database. This command does not initiate the database. mxpassword Adds, lists, modifies, or removes passwords mxpassword(1M, 8) stored in HP Systems Insight Manager.
• mxcollection • mxexec • mxglobalprotocolsettings • mxglobalsettings • mxlog • mxmib • mxngroup • mxnode • 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.
• Configuring or Repairing Agents For more information, see “Configuring or repairing agents”. • Creating custom tool definition files for HP SIM See Creating custom tool definition files for HP SIM white paper at http://h18013.www1.hp.com/ products/servers/management/hpsim/infolibrary.html. • Deploying HP SIM on MSCS Clusters See the Deploying HP SIM 5.x on MSCS Clusters white paper at http://h18013.www1.hp.com/ products/servers/management/hpsim/infolibrary.html. • Getting Started with HP SIM 5.
• MIB Support - Out of the Box See the HP Insight Management MIB update kit for HP SIM at http://h18013.www1.hp.com/products/ servers/management/hpsim/dl_windows.html#windows. • Moving HP SIM to a new system See the Moving HP SIM 5.1 to a new Windows system white paper at http://h18013.www1.hp.com/ products/servers/management/hpsim/infolibrary.html. • Receiving HP driver, support, and security alerts, plus software updates customized to your HP products See http://www.hp.com/go/subscribe-gate1.
• Viewing the entire HP Version Control Agent Online Help in a PDF See the HP Version Control Agent Online Help at http://h18013.www1.hp.com/products/servers/ management/agents/documentation.html. • Viewing the entire HP Version Control Repository Manager Online Help in a PDF See the HP Version Control Repository Manager Online Help at http://h18013.www1.hp.com/products/ servers/management/agents/documentation.html.
5 Discovery and identification Discovery is the process of finding systems in the management domain so that they can be managed from the Central Management Server (CMS) by HP Systems Insight Manager (HP SIM). There are two types of discovery: • 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.
adds any systems that send SNMP traps, WBEM indications, or other events to HP SIM that do not have a matching IP address in the database. The option, Ping exclusion ranges, templates, and/or hosts files, allows the entry of any IP addresses that you want excluded from event-based automatic discovery. If SNMP is disabled on the Global Protocols Settings page under Options→Protocol Settings→Global Protocol Settings, then SNMP traps are ignored. If WBEM is disabled, WBEM indications are also ignored.
Settings→Global Protocol Settings page. Configure default community strings and WBEM passwords on the Global Protocol Settings page. See “Global protocols” for additional information. Status indicators let you know when discovery is running, and the column, Last Run, displays running, the percentage of completion, the number of pings attempted, and the systems processed. A processed system is one in which the IP address has been either identified or found unresponsive.
• Specify the Web-Based Enterprise Management 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 are displayed.
• Discovery filters • Data collection • Status polling • Protocols • Discovery and identification Configuring automatic discovery When you access the Automatic tab on 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.
NOTE: Two discovery tasks cannot be running at the same time. The second task displays 0% completion until the first task is completed. • Stop a discovery task from running task” for more information. • View HP Storage Essentials discovery status When HP Storage Essentials is installed, its discovery status is displayed with a link to the HP Storage Essentials discovery log.
3. 4. 5. In the Name field, enter a name for the task. This field is required. In the Schedule section, select Automatically execute discovery every, and then 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. In the Ping inclusion ranges, system (hosts) names, templates, and/or hosts files field, specify the IP addresses to include for pinging.
Editing a discovery task When editing an existing discovery task, because all fields are prepopulated with existing information, you can edit only the fields that you want to edit. To edit an existing discovery task: 1. 2. 3. 4. 5. 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. In the Name field, enter a name for the task. This field is required.
Related procedures • Configuring automatic discovery general settings • Creating a new discovery task • Editing a discovery task • Deleting a discovery task • Running a discovery task Related topics ▲ Discovery and identification Deleting a discovery task You can delete discovery tasks that are no longer necessary. You cannot delete the Default Discovery task. If you select the Default Discovery task, the Delete button is disabled. To delete a discovery task: 1. 2. 3. Select Options→Discovery.
System types There are many different system types in HP Systems Insight Manager (HP SIM). All of these types are available on the General Settings for All Discoveries page, with the exception of clusters, complexes, racks, and enclosures. These types are not listed because they are not discovered directly. For example, a cluster is typically discovered through a cluster node.
• Router • Server A computer on a network that is dedicated to a particular purpose. For example, saving files, running print jobs, or housing a database server. • Shared Resource Domain A collection of compartments, all of the same type, that share system resources. The compartments can be npars, vpars, psets, or fss groups. • Storage Device A disk drive array that usually supports RAID levels and is accessed over a Fibre Channel Storage Area Network (SAN).
Windows, install the Initial ProLiant Support Pack). See “Initial ProLiant Support Pack Install” for information about installing the Initial ProLiant Support Pack. • Virtual Connect Domain The system that represents the virtual connect configuration and is used to manage virtual connect information and licensing. • Workstation work.
StorageWorks XP10000 StorageWorks XP12000 StorageWorks XP48 StorageWorks XP512 StorageWorks XP 2400 (Kodiak) StorageWorks VA StorageWorks VA7100 StorageWorks VA7110 StorageWorks VA7400 StorageWorks VA7410 StorageWorks EVA StorageWorks EVA3000 StorageWorks EVA5000 StorageWorks EVA4000 StorageWorks EVA6000 StorageWorks EVA8000 StorageWorks MSA MSA1000 MSA1500 MSA 1500 active/active MSA 1510i MSA1000 active/active MSA 1500cs 500 G2 Modular Smary Array iSpitfire ThunderBolt StorageWorks T
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 (AE312A) FC2142SR (A8002A) FC2242SR (A8003A) FCA2684 FCA2684DC AB378A AB379A FC1143 (AB429A) FC1243 (AB379A) FC2143 (AD167A) FC2243
NOTE: The WBEM providers cannot be installed on HP-UX or Linux systems. NOTE: A Common Information Model Object Manager (CIMOM) acts as the interface for communication between WBEM providers and management applications such as HP SIM. The CMS must have the correct credentials to authenticate to WBEM and WMI. There are two ways to authenticate HP SIM to a client: • • Basic authentication to WBEM Services or WMI using user name and password.
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/). • OpenSSH A set of network connectivity tools providing encrypted communication sessions over a computer network using SSH. It was created as an open source alternative to the proprietary SSH software suite offered by SSH Communications Security.
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.
• Select Discover systems in an enclosure when Onboard Administrator is discovered. This option adds systems identified by the Onboard Administrator even if the systems are not in the configured discovery range. This option is selected by default. • Select Automatically discover VM guest(s) when the host is identified. This option adds all HP Integrity Virtual Machine (HPVM) guest systems to the HP SIM database when the HPVM host system is discovered and identified. This option is selected by default.
Discovery filters Discovery filters are a mechanism to prevent or enable certain system types from ever 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.
Related procedures • Creating a new discovery template file • Editing a discovery template • Deleting a discovery template Related topic ▲ Discovery and identification Creating a new discovery template file You can create new discovery template files instead of entering addresses directly into the Ping inclusion ranges, system (hosts) names, templates, and/or hosts files or Ping exclusion ranges, templates and/or hosts files fields. To create a new discovery template file: 1. 2. 3. 4. 5.
Related topics • IP ranges • Discovery and identification • Managing discovery templates Editing a discovery template You can edit an existing discovery template file. All fields are optional except for the Discovery template name field. Edit only the fields that you want to change. To edit a discovery template file: 1. 2. 3. 4. 5. Select Options→Discovery. The Discovery page appears with the Automatic tab selected. In the For all automatic discoveries section, select Manage templates.
Related procedures • Creating a new discovery template file • Editing a discovery template Related topics • Discovery and identification • Managing discovery templates Adding a system manually Use manual discovery to add a system to the HP Systems Insight Manager (HP SIM) database between scheduled discoveries. To add a system using manual discovery: 1. 2. 3. 114 Select Options→Discovery, and then click the Manual tab. The System Information section appears. Enter the system name or IP address.
• • Specify additional system properties to use only if Identification fails on this system. Includes: • System type • System subtype Click the down arrow and select the appropriate System subtype. You can input up to eight different system subtypes. • Product model Click the down arrow and select the appropriate System type. Enter the system model number here. This field is free form.
However, if systems are connected through a WAN, try a higher value, for example, 10 seconds. • Retries The number of additional times after the first attempt is made to communicate with a system before the attempts stop. • Read-only community string and Write community string Note: The Write community string is optional and is required only for firmware updates on a GbE switch.
• Delete a hosts file Select the hosts file to delete, and then click Delete. A confirmation box is displayed. See “Deleting a hosts file” for more information. • Add a hosts file to the HP SIM database Select the hosts file to add, and then click Add system now. See “Adding systems in a hosts file to the HP SIM database” for more information.
4. 5. 6. Under Initialize contents with, select one of the following: • Template file. Loads the contents into the Contents window. • Systems loaded from the central management server, sorted by:. From the dropdown list, select one of the following: IP address, System name, System type and then by IP address, or System type and then by system name. This option loads the systems managed by HP SIM into the Contents window. • Systems loaded from hosts file.
3. In the Replace contents with section, select one of the following: • Template file. Loads the contents into the Contents window. • Systems loaded from the central management server, sorted by:. From the dropdown list, select one of the following: IP address, System name, System type and then by IP address, or System type and then by system name. This option loads the systems managed by HP SIM into the Contents window. • Systems loaded from hosts file.
Related procedures • Creating a new hosts file • Editing a hosts file • Deleting a hosts file Related topics • Discovery and identification • Managing hosts files Creating a task to import a hosts file for HP SIM integration Users with administrative rights who are using both HP Systems Insight Manager (HP SIM) and its companion Windows management application, Insight Manager (WIN32), can import Insight Manager (WIN32) system database files for easy transition from the Windows client/server enviro
See http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/win32sim.pdf for more information about exporting the Insight Manager (WIN32) .dat file. Related procedure ▲ Creating a new hosts file Batch-adding systems using the CLI You can batch-add systems by host name using the command line interface (CLI). To do this, you must first create an .xml file, and then run the mxnode command from the command line. 1. Create and save an .xml file. For example,
To change the default globally so that it affects the next file entry and all subsequent entries, use a statement similar to the following example. The default is changed to "router" for the next entry. Router remains the default for all entries until another #$IMXE_DEFAULT statement changes that value. If a single instance of TYPE is changed by a #$IMXE statement, the default is not used only for the next entry and then reverts to back "router".
16.26.160.24 BldRtr5.compaq.com BldRtr5 For the system AcctServer, only the TYPE was changed from the current defaults. #$IMXE: TYPE=Server 16.26.176.36 AcctServer.compaq.com AcctServer #user comments The global default for TYPE was changed from Unknown to Router. All subsequent entries will be identified as routers until a TYPE statement is used to specify another type or restore the default. #$IMXE_DEFAULT: TYPE=Router 16.25.176.38 FloorRtr2a.compaq.
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.
appears as a Management Protocol along with all other supported management protocols on the system page System tab of the System page.
Identifying systems To identify systems in between discoveries, select Options→Identify Systems. The Identify Systems page appears. From this page, select target systems to add. See “Creating a task” for more information about selecting targets. Related procedure ▲ Adding a system manually Related topic ▲ Discovery and identification Managing system types The System Type Manager (STM) is a utility that modifies the default behavior of identification.
To access the Manage System Types page, select Options→Manage System Types. System type The list on the Manage System Types page can be filtered by system type by selecting a type from the System Type dropdown list. Click the down arrow, and then select a system type for which to filter the list.
Related topics • Managing system types • About System Type Manager About System Type Manager Manufacturers assign unique System Object Identifiers (OIDs) to their Simple Network Management Protocol (SNMP)-instrumented products. System Type Manager (STM) enables you to customize identification by creating rules that map these OIDs to product categories and names of your choosing.
Related topics • Managing system types • Navigating the Manage System Types page Creating STM rules The following procedure instructs you how to create a new SNMP rule through System Type Manager (STM). The STM is a utility used to modify the default behavior of identification.
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 Systems Insight Manager (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.
11. In the Subtype field, click the down arrow, and then select the system subtype. 12. In the Product name field, enter the product name for the new rule. 13. In the Custom management page field, enter a URL. The URL displays this web page as a system link on the System Page of systems identified using this rule. Enter the special keywords $ipaddress and $hostname anywhere in this URL. They are replaced by the actual IP address or host name of the system when the link is placed on the System Page. 14.
Deleting STM rules 1. 2. 3. 4. Select Options→Manage System Types. The Manage System Types page appears. Select the rule to delete. Click Delete. A confirmation box is displayed. Click OK to delete the rule, or click Cancel to cancel the deletion process.
Access = Read-Only Storage = Common Type = String(64) Value = "Intel Corporation" End Attribute Start Attribute Name = "Product" ID = 2 Access = Read-Only Storage = Common 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.
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.
HP Systems Insight Manager (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.
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 Windows, this includes Active Directory.
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.
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.
a group's configuration rights, 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.
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.
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. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from management by this user or user group.
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.
• Pager Configured • IP Login 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 command line interface (CLI).
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.
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.
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.
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.
• System This column displays the systems on which the user or user group has authorizations. A system group is displayed 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.
• 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.
b. c. In the Select Systems list box, the two default system groups (All Managed Systems and CMS) are displayed. 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.
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.
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.
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.
is generated for only for the user selected. If (none) is selected in the Select name dropdown list, a report is generated for everything selected in the Authorizations box. 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.
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 are displayed for verification.
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.
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.
• Users and authorizations • Directory Services Configuring directory groups 159
8 Networking and security HP Systems Insight Manager (HP SIM) provides the following security options: • User and Authorizations. • Server Certificate. • Trusted Certificate. • Login Event Settings. • System Link Configuration. Select Options→Security→Users and Authorizations. Select Options→Security→Certificates→Server Certificate. Select Options→Security→Certificates→Trusted Certificate. Select Options→Security→Login Event Settings. Select Options→Security→System Link Configuration.
Certificates HP SIM allows secure and authorized management from the Central Management Server (CMS). User authorizations for managed systems and the CMS can be configured, helping ensure that only authorized users perform state-changing operations. Communication between the CMS, managed systems, and the browser is secured using SSL and certificates, helping to authenticate systems and protect user credentials and management data.
IMPORTANT: If you browse to a managed system using any method other than the links within HP SIM, Single Login is not supported, and you are required to enter the appropriate user name and password for each managed system. NOTE: Single Login does not work on a Virtual Cluster System. However, it does work on the physical systems which compose the cluster. Signing in Signing in to HP SIM allows access to HP SIM and determines what authorizations you have in HP SIM.
Configuring PAM on a Linux system The administrator of a Linux CMS can customize the PAM that HP SIM uses. The file /etc/pam.d/mxpamauthrealm contains the authentication steps for the HP SIM web server interface. The default for this file is: • #%PAM-1.0 • auth required /lib/security/pam_unix.so • account required /lib/security/pam_unix.so • session required /lib/security/pam_unix.
NOTE: STE requires a Trusted Management Servers List at each managed system to ensure that only specified HP SIM systems can execute tasks on the system. NOTE: On the managed system, only a Trust by Certificate ensures that the request came from the specified HP SIM system. Other options, such as Trust by Name or Trust All, do not verify the digital signature of the HP SIM system and; therefore, these options cannot reliably verify the sender of the request.
Configuring sign-in events Configure sign-in events to create actionable events for sign-in and sign-out activities. NOTE: Configuring sign-in events does not affect the HP Systems Insight Manager (HP SIM) Audit Log. Sign-in events are always logged in the HP SIM Audit Log. To configure sign-in events: 1. 2. 3. Select Options→Security→Sign-in Event Settings. The Sign-in Event Settings page appears. Select from the following options: • All sign-in and sign-out activities.
Linux and HP-UX: /opt/mx/jboss/server/hpsim/deploy/jbossweb-tomcat50.sar/conf/web.xml 2. 3. Edit the value from the default of 20 minutes to the number of minutes you want. Save the globalsettings.Props and the web.xml files. The updates are saved. 4. Close the web.xml file.
HP SIM provides the following security certificate options: • Export server certificate click Export. • Edit server certificate Edit. • Create new server certificate then click New. • Import server certificate click Import.
Creating a server certificate Users with administrative rights can create a new self-signed certificate when they replace the HP Systems Insight Manager (HP SIM) Secure Sockets Layer (SSL) server certificate and private key in the following situations: • The integrity of the HP SIM server certificate private key is compromised • The existing HP SIM server certificate expires This self-signed certificate is configured to expire 10 years from the date of creation.
a. b. The Common Name (CN) field holds the parameter that the browser uses for name comparison when browsing to the Central Management Server (CMS). This field can be updated with other name formats, such as fully qualified names, and can contain up to 255 characters. (Optional) In the Alternative Names field, enter multiple system names separated by a comma. If a name identical to the CN is specified in the Alternative Names field, it is not duplicated in the certificate.
1. 2. Select Options→Security→Certificates→Server Certificates, and then click Edit. The Edit Server Certificate section appears. Edit the following fields as necessary: Note: The Common Name (CN) field and the key pair cannot be modified, so the trust relationships with any System Management Homepages remain in tact. However, the browser trust must be re-established by importing the modified certificate and deleting the old certificate from the browser. a.
systems. Replace the previous server certificate with the new server 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 System Management Homepage certificate and private key on HP-UX systems, it affects the Web-Based Enterprise Management (WBEM) Services certificate and private key. To import a server certificate: 1. 2. 3. Create a certificate signing request (CSR).
Related topics • Server certificates • Networking and security • Installing OpenSSH • Managing SSH keys Creating a certificate signing request Create a certificate signing request (CSR) to replace the HP Systems Insight Manager (HP SIM) Secure Sockets Layer (SSL) server certificate and private key. The CSR includes any alternative names that exist in the certificate.
Related procedures • Importing a server certificate • Creating a certificate signing request • Importing a CA-signed certificate Related topics • Server certificates • Networking and security • Installing OpenSSH • Managing SSH keys Importing a CA-signed certificate After creating a certificate signing request (CSR) and having it signed by a Certificate Authority (CA), you can import the signed certificate. The only importable certificate format is PKCS #7.
Synchronizing certificates When the HP Systems Insight Manager (HP SIM) server certificate is created or modified, the public and private certificate key-pair of the System Management Homepage certificate is overwritten with the HP SIM public and private key-pair. NOTE: This feature is available in the unlikely event that the certificates become unsynchronized for an unknown reason.
CMS, but you can view the certificate displayed by the browser to ensure its authenticity before signing in. 9. 10. 11. 12. 13. Sign-in with administrative rights to HP SIM on the target CMS. Select Options→Security→Certificates→Server Certificate. To create a new server certificate, click New. On the target CMS system, select Start→Settings→Control Panel→Administrative Tools→Services. Restart the HP SIM service.
Related procedures • Creating a Replicate Agent Settings task • Exporting a server certificate • Editing a server certificate • Creating a server certificate • Importing a server certificate • Synchronizing certificates • Creating a certificate signing request • Submitting a certificate signing request • Importing a CA-signed certificate Related topics • Networking and security • Installing OpenSSH • Managing SSH keys Possible certificate errors Possible certificate error messages in
The Trusted System Certificate List page includes the following options: • Always Accept If Always Accept is selected, SSL always accepts the certificate presented by a system in the SSL connection. This setting is the default and is vulnerable to man-in-the-middle attacks, but it is the easiest option to use. • Require If Require is selected, you must set up the trust by manually installing the system’s certificate into the HP SIM Trusted System Certificate List.
Related procedures • Exporting trusted certificates • Deleting trusted certificates Related topics • Trusted certificates • Setting up trust relationships • Server certificates • Networking and security • Installing OpenSSH • Managing SSH keys Exporting trusted certificates Export the HP Systems Insight Manager (HP SIM) server certificate to a file to facilitate deployment of the certificate into your browser, enabling the browser to properly identify the HP SIM server.
4. Click Next. The Export File Format dialog box appears. 5. Select Base-64 encoded X.509 for the export file format. Click Next. The File to Export dialog box appears. 6. In the File name field, enter the file you want to export. Click Next. The Completing the Certificate Export Wizard dialog box appears. 7. Click Finish. You can click Back to return to the previous page or click Cancel to cancel the export operation. A message appears indicating that the export is completed. 8. Click OK.
Requiring trusted certificates Trusted system certificates are certificates that represent managed systems. Enabling the Trusted System Certificate option enables HP Systems Insight Manager (HP SIM) to authenticate the remote managed system. For ease of use, this option is disabled; this scenario is typical and maintains a high level of security. For maximum security, this option should be enabled, which requires extra configuration.
Configuration of the managed system For Single Login and Secure Task Execution (STE) to function properly, the managed system must be running a supported agent and be configured to trust the HP SIM server. The trust mode is configured from the System Management Homepage (SMH). The following trust modes are available: Trust By Certificate. The Trust by Certificate mode sets the System Management Homepage to accept configuration changes only from HP SIM servers with trusted certificates.
3. 4. 5. 6. 7. Browse to the managed system, and using a text editor (such as Notepad), open the HP SIM server certificate created in step 1. Highlight the entire contents of the file, including the Begin Certificate and End Certificate lines. Copy the highlighted contents of the certificate file to the clipboard. Return to the managed system browser and then select the HP SIM Certificate Data box. Paste the contents of the certificate file into this box, and then click Add Cert.
systems you want the HP SIM server to trust into the Trusted System Certificates List of HP SIM. For the managed system certificate, you can use the system certificate, or, if applicable, the certificate the Certificate Authority (CA), used to sign the system certificate. NOTE: If Require is disabled on the Trusted Certificates page, then Trusted System Certificates List is not used, all certificates are accepted, and you can omit this section.
• Networking and security • Creating a Replicate Agent Settings task • Installing OpenSSH • Managing SSH keys Trusted certificates 185
9 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.
previous versions of HP SIM that included system attributes, this collection would 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. See the Collections in HP Systems Insight Manager white paper at http://h18013.
Related topics • System table view page • Cluster table view page • Event table view page • Customizing event collections • Customizing system or cluster collections • Searching for systems and events • Navigating the System and Event Collections panel • Reference • Default shared collections • Service notification events Navigating the System and Event Collections panel The System and Event Collections panel contains the following features: 1. 2. 3. 4.
only users with administrative rights rights can edit or delete these collections and their contents. Private collections can only be viewed, edited, or deleted by the user that created the collection. Collections can be placed in Private or Shared collections. To place a collection in the Shared folder, you must have administrative rights. Private collections can be placed into a shared collection, but shared collections cannot be placed into a private collection.
Related procedures • Customizing system or cluster collections • Customizing event collections Related topics • Monitoring systems, clusters, and events • Navigating the tree view page • System types Customizing system or cluster collections The System and Event Collections panel contains a Systems collection. The Systems collection contains additional system, cluster, and System Functions collections. NOTE: Cluster collections are only created by attributes, not by members.
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.
NOTE: Users with administrative rights can create a shared collection. Users with operator rights can view shared collections, but can only create their own private collections. To create a new system or cluster collection: 1. 2. 3. 4. 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 are displayed. Click New. The New Collection section appears.
Command line interface Users with administrative rights can use the mxcollection command to create new collections from the command line interface (CLI). See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
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 are displayed. Select a system or cluster collection to edit, and then click Edit. The Edit Collection section appears. Depending on how the collection was created, the following appears: a. If the collection was created using the Choose members individually option, complete the following steps: i.
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
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. are displayed.
collection is not updated. See the Collections in HP Systems Insight Manager white paper at http:// h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information about collections. To copy a collection: 1. 2. 3. 4. 5. 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 are displayed.
and so on) an error message appears. However, if the collections contents are based on attributes, the collection can be deleted even if it is not empty. Command line interface Users with administrative rights can use the mxcollection command to delete existing collections from the command line interface (CLI). See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
Related procedures • Performing an advanced search for systems • Editing system or cluster collections • Creating system or cluster collections • Deleting system or cluster collections Related topics • Monitoring systems, clusters, and events • Customizing system or cluster collections • Navigating the System and Event Collections panel Customizing event collections The System and Event Collections panel contains an Events collection.
Customize collections table When the Customize Collections page appears, if the collection and system status is displayed in the System and Event Collections panel, a table is displayed that includes the names of all the collections. Available buttons The following options are available on the Customize Collections page for events: • New This enables you to create a new event collection. If you have administrative rights, you can save the new collection as a shared collection.
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 only create 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 are displayed. Click New.
Command line interface Users with administrative rights can use the mxcollection command to create new collections from the command line interface (CLI). See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
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 are displayed. 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 the collection was created with the Choose members individually option, complete the following steps: i.
• 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.
collection has two members, the same two members are copied to the new collection. If the original collection is edited to add another member after it is copied, the newly copied collection is not modified. When you copy a collection that was created based on attributes, you are copying the collection attributes into the new collection. If the original collection is edited after it is copied to the new collection, the newly copied collection does not reflect these edits.
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 are displayed. Click 3. 4.
See “Using command line interface commands” for more information about accessing the manpage, which includes detailed information for this command.
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 are displayed on the first page. Systems selected on one page remain selected as you navigate to a different page in the collection.
View as This View as dropdown list is used to select either table, which displays the system results in a table form, icons, which displays only the HS status icon and the System Name for each system, and tree, which 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.
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 Integrated Lights-Out (iLO) board installed. Otherwise, the Informational icon is displayed. Clicking the status icon displays the management processor login page.
HP ProLiant Essentials Virtual Machine Management Pack If HP ProLiant Essentials 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 ProLiant Essentials Virtual Machine Management Pack page for the selected system, providing more information about the status of the virtual machine.
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 is displayed in the System Name column on the system table view page by showing name in system type container name.
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.
Navigating the tree view page When a collection is selected that was created based on individual members, the tree view is displayed 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 is not displayed. The following sections are available on the tree view page: 1.
a tool from this list bypasses the target verification page of the Task Wizard, regardless of the Task Wizard settings. Tools launched with this menu cannot be scheduled. The menu can be customized 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.
status 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 are displayed. 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 are displayed and their selection boxes are disabled. The selection states for a collection are as follows: • The initial state; nothing is selected.
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.
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 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.
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 are displayed 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 are displayed in the picture view for enclosures.
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 were 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.
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.
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.
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 are displayed in the following formats: • Encl1 in Rack1 • Rack1 The Picture View page can be displayed by clicking a rack hyperlink on the system table view page or from the System and Event Collections panel.
Deleting systems from the HP SIM database NOTE: Deleting multiple systems from the database at one time can cause performance delays. NOTE: The Central Management Server (CMS) cannot be deleted. NOTE: Clusters that contain cluster members cannot be deleted. 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.
Related topics • System table view page • Navigating the system table view page System status types The following table describes the HP Systems Insight Manager (HP SIM), system health status types: Status icon 226 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.
NOTE: HP Insight Management Agent for Servers for Windows continues to use the terms Normal, Degraded, Failed, and Inaccessible. Minor and Major status are only associated with systems running these agents. Related topic ▲ System table view page WBEM operational status types HP Systems Insight Manager (HP SIM) reports WBEM operational status for storage and server elements, such as storage switch ports and filled memory slots.
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.
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.
user at a time can edit a collection. If another user wants to edit the same collection, a List Edit Warning box appears. The user can cancel the editing request or edit the collection and save it as a new collection. 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.
settings. Tools launched with this menu cannot be scheduled. The menu can be customized by clicking the Customize link in the Quick Launch menu. 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.
Serviceguard cluster, a new cluster table view page appears, showing the servers in the cluster. From this list, click a server name to access the System Page for that server. If the cluster is of any other type, the System Page for that cluster appears. See “System tab for clusters” for more information. 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.
Related procedures • Customizing the cluster table view page • Deleting clusters from the database • Saving collections • Printing a cluster collection view Related topics • Cluster table view page • 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 th
1. 2. 3. On the cluster table view page, select one or more clusters to delete from the database by highlighting them in the display. Click Delete. A dialog box appears, stating, Are you sure you want to delete these systems? To delete the clusters, click OK, or to return to the cluster table view page without deleting the clusters, click Cancel.
• Print event collection results • Customize the view Click Customize to customize which columns are displayed and in what order. See “Customizing the event table view page” for more information. Click Print to print the collection results. 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.
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, additional filters can be applied to modify the event table display. This tab lists all of the systems in the collection.
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. Table information The area includes information about the systems or events.
• Comments • System Type • Rack Name • Enclosure Name • Case Status • Case ID Selection Select the checkbox in this column to select an event. You can select more than one event. Select the checkbox in the column heading or select Select "collection name" itself to select or clear all displayed events. 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.
over a comment field to display a window that shows the entire comment to appear. See “Entering comments on events” for more information. System Type This column displays system types such as enclosure or rack, if the system type filter was selected for the event list display. Rack Name This column displays the name of the rack. NOTE: This column is displayed when the system is a rack or enclosure and the rack or enclosure system filter is selected.
• Change the Orientation to Landscape in the Print dialog box (see Printing Problems in “Troubleshooting” for a workaround to this issue) • Cancel printing after the print job has been executed; however, you can access the operating system's print queue and cancel the print job • Print to a file • 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 approp
• Assigning events to users • Entering comments on events • Printing an event collection view Related topics • Event table view page • Navigating the event table view page 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.
Assigning events to users You must have administrative rights to assign events from shared collections. For users with operator and user rights to assign events, they must have the Assign Events tool selected in their toolbox categories. See “Editing toolboxes” for more information. IMPORTANT: Assigning events to certain users, does not facilitate any tracking at all and the user is not notified of the event.
NOTE: Comments that are added to events in HP Systems Insight Manager (HP SIM) are not transferred to HP Storage Essentials. Related procedures • Customizing the event table view page • Clearing events from the collection • Deleting events from the database • Assigning events to users • Printing an event collection view Related topics • Navigating the event table view page • Event table view page • Event details section Printing an event collection view 1. 2.
Status icon Security level Description Minor Events of this type indicate a warning condition that can escalate into a serious problem. Normal Events of this type indicate that this event is not a problem. Unknown Events of this type indicate that this event is of unknown severity or caused by an unknown problem. Warning Currently in a state that might become a problem. Note: In HP SIM 5.0, only WBEM indications map to this level.
• Trap Details • Date and time the event occurred • Event Description • Trap Information • Discovered System Details • Discovered Date • Event Details • User name • Name of the remote system from which the user was browsing • IP address of the system from which the user was browsing 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.
2. icon for the system health status. If more than 12 systems are found, an ellipsis appears at the bottom of the list. Continue typing to narrow the list further. Perform one of the following: a. Use the mouse or the up and down arrows on your keyboard to select a system. Press Enter to navigate to the System Page of the selected system. or b. Do not select a system. Press Enter or click Search. The Search Results page appears and lists all matching systems. NOTE: Press Esc to hide the dropdown menu.
Advanced search To access the Advanced Search page, click the Advanced Search link in the Search panel. You can create a system, event, or cluster search by selecting systems, events, or clusters in the Search for box at the top of the Advanced Search page. Then you can specify the criteria to be used in the search. The result of running a search is a collection. The criteria selected can also be saved as a collection definition, so that search can be run again at a later date.
Note: Press Esc to hide the dropdown list. 2. • To view the System Page for a single system, select it with the mouse or select it with the up and down arrows on your keyboard, and then press Enter. • If you want to search for multiple systems or a system attribute, do not select a system in the dropdown list. Press Enter or click Search. The Search Results page appears and lists all matching systems.
1. 2. 3. Click Advanced Search in the Search panel. Select systems from the Search for dropdown list. From the first selection box (criteria selection), click the down arrow, and then select the search criteria. Note: Some search criteria show no values until systems with values for that criteria have been discovered. In this case, the criteria is not displayed until values are available. 4. From the second selection box (comparison selection), click the down arrow, and then select the comparison option.
Related procedures • Saving collections • Deleting system search results from a search view 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.
5. 6. 7. In the third selection box (value selection), select one of the values for a specific criteria or comparison combination from the dropdown list, or enter the required information in the input box. 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.
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.
Printing cluster search results 1. 2. After the Search Results is displayed, click View. The results are displayed. 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.
and memory range. Event collections include both system criteria and event criteria. However, event criteria do not apply to system collections. 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.
system name Systems with a specific set of system names. system setting Systems with a specific client attribute defined. Client attributes are typically used and set by one of the HP ProLiant Essential plugins and is typically reserved for use by one of those plugins. system subtype Enables you to search on the product subtype field in the HP Systems Insight Manager (HP SIM) database (for example, Power Enclosure, enclosure, and VM Host)..
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 is displayed in the language in which it was stored. Data retrieved from the repository is displayed in the language corresponding to the browser locale.
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.
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 is used to indicate that a general error occurred on the server-side of authentication during automatic sign-in. This event can occur for several reasons.
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 Virtual Server Environment (VSE) resources in the database.
• 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 clients in the database. Includes all discovered printers in the database. Includes all discovered management processors in the database. Includes all discovered virtual machine hosts.
• Microsoft Windows XP Windows XP. • Microsoft Windows 95, 98, ME Includes all systems in the database that have an operating system equal to Windows 95, 98, or ME. • HP Tru64 Unix UNIX. Includes all systems in the database that have an operating system equal to HP True64 • HP OpenVMS Includes all systems in the database that have an operating system equal to OpenVMS. • Red Hat Linux Linux.
to the Remote Support software, but they are not monitored and do not trigger a response. See the Remote Support Pack documentation for instructions on enabling or disabling remote monitoring for your systems. Shared event collections All users can view shared event collections, but only users with administrative rights can create, edit, or delete shared collections. The following shared event collections are based on Event by Severity: • All Events database. • Important Events events.
• Service notification events • Changes to HP SIM storage functionality when HP Storage Essentials is installed Collection naming conventions Use the following guidelines for naming Systems or Events: • All collection names must be unique, except for private collections. • The terms Systems, Events, and all shared collections are reserved names in HP Systems Insight Manager (HP SIM). Do not use them as collection names. • Multiple spaces in collection names are collapsed to a single space.
10 Storage integration HP Systems Insight Manager (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.
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.
These components may 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 enable management of the device. • SMI solution: The hardware or software ships with an agent that is installed on a host. The agent needs to connect to the device and obtain unique identifying information. This is the method used by all HP storage devices and most SAN devices.
• Storage integration • Viewing storage systems • 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 Systems Insight Manager with storage systems For optimal interaction between HP SIM and storage systems, complete the following procedures.
1. 2. In the System and Event Collections panel, expand Systems, Shared, Systems by Type, and Storage Systems. Select one of the following: • All Storage Systems • All Storage Hosts • All Storage Switches • All Storage Arrays • All Tape Libraries The system table view page for that collection appears. See “Navigating the system table view page” for more information. Viewing individual storage systems To view an individual storage system: 1. 2. 3.
• Storage Ports—All Storage Hosts lists port information for all storage host HBAs. • Storage Ports—All Storage Switches lists port information for all storage switches. • Changer Devices—All Tape Libraries lists the name, firmware version, and status for all tape libraries. • Media Access Devices—All Tape Libraries lists the name, firmware version, and status for all tape libraries. NOTE: See “System reporting” for instructions on viewing existing reports.
• If a storage system is managed by HP Storage Essentials, storage-specific details do not appear in its System tab, and an SE System Properties link appears in the HP Storage Essentials Pages section on the Tools & Links tab. Click the SE System Properties link to view the Storage Essentials device page for this storage system. • For storage hosts, HP Storage Essentials adds the System Application Discovery Settings link to the Tools & Links Page.
NOTE: For additional information about HP Storage Essentials, see your HP Storage Essentials documentation. Related topics • Storage integration using SMI-S • HP Storage Essentials overview Storage integration using SNMP Overview Storage devices can be broken down into real-time access and backup systems. Real-time access systems can be subdivided into internal disks, redundant disks (RAID), tape libraries, storage area networks (SAN), and network attached storage (NAS).
• • • • • The type of disk in slot • Disk manufacturer • Disk model • Disk part number • Disk characteristics • Firmware version • Controller ID that is managing this disk Controller details • Total number of controllers • Controller type • Controller manufacturer • Model number • Part number • Slot ID that this card is installed in • Firmware version • Controller characteristics RAID details • RAID type • RAID configuration SAN and NAS • Network addresses • Manufact
to the details gathered for the internal drives. For SAN systems, HP SIM discovers the Command View servers that manage the devices on the SAN. HP SIM displays storage systems as follows: • Internal drives These systems must appear in the Properties pages and the inventory database as components of their respective systems. • Tape libraries These devices are identified and included in the All Systems, All Storage Systems, and All Tape Libraries collections.
Related procedure ▲ Using HP SIM with SNMP storage solutions Related topics • System Page • About storage discovery using SNMP • Discovery and identification Using HP SIM with SNMP storage solutions Viewing a storage event There are two ways to view a storage event: • Select Tools→System Information→System Page. • Click the system name in the System Name column on the system table view page.
1. Select Start→Settings→Control Panel→Network→Services→SNMP Service. The SNMP Service Properties dialog box appears. 2. 3. 4. 5. Click Traps. Enter a community name, such as public. Click Add to list. At the bottom of the dialog box, click Add. The SNMP Service Configuration dialog box appears. 6. Enter the host name or IP address of the enterprise management station, and then click Add. The SNMP trap destination is added. 7. Click OK to save the changes and close the dialog box.
11 Managing with tasks HP Systems Insight Manager (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.
When a polling task is set up to run as the result of a change in an event collection, the polling task is applied to all systems generating events that match the given collection. 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.
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. By default, this task polls every 10 minutes and at start-up. NOTE: If you discover more than 500 systems, HP suggests you change the interval to something greater than 10 minutes (for example, 15 minutes for every 1000 systems).
To configure task wizard settings: 1. 2. 3. Select Options→Task Wizard Settings. The Task Wizard Settings page appears. Select Bypass target verification page when all targets are valid. If the target verification page includes the options to run now or schedule, select Run Now or Schedule. If you select Run Now when a tool is selected, the tool runs immediately. If you select Schedule when a tool is selected, the Schedule Task page appears.
the Search Results table will be selected (checked) by default and the Apply button will be enabled as long as there is at least one item from the Search Results table selected. Only items that are selected will be added when you click Apply. Note: The maximum number of Device Names displayed is six. 5. If you click Search, a Basic Search using common attributes will be performed using the characters typed into the Text Field.
4. To filter target selections, complete the following. a. Click Add Event Filter. b. From the Add filters by selecting from dropdown box, select an event fiter. If you do not select an event filter, an error message appears. c. Click Apply to apply the filter to the target systems (or, click Cancel to cancel adding a filter). The Filtered by table appears below the list of selected target systems.
Applying a time filter Use time filters to decide when a task should or should not run by applying them to a task. Time filters can be created, copied, edited, and deleted. Time filters can be created by any user and are accessible to all users. 1. 2. 3. Select a tool from the tool menu, follow the steps to get to the Schedule button, and then click it. For more information, see “Creating a task” and “Scheduling a task”. To apply a time filter to a task, select the Use Time Filter checkbox.
4. 5. 6. • When new systems or events are added to the collection This option is only available if you select a Collection of Systems or Events as your target. The task runs only when new systems or events meet the collection criteria. You can also apply a time filter to this type of scheduling. For more information about time filters, see “Applying a time filter”.
Command-line interface Use the mxexec command to execute tools immediately; use the mxtask command to schedule tasks for later. Perform these tasks from the CLI. For assistance with these commands, see the HP-UX or Linux manpage for the command by entering man mxexec at the command line or see the Windows command line help. For more information about how to access the manpage, see “Using command line interface commands”.
Deleting a scheduled task Deleting a task removes the task and its associated task instances from the All Scheduled Tasks page and the system. CAUTION: NOTE: If you delete a task, the task is permanently deleted from the database and cannot be restored. You cannot delete system delivered (default) tasks. To delete a scheduled task: 1. 2. 3. Select Tasks & Logs→View All Scheduled Tasks. Select a task from the All Scheduled Tasks list. Click Delete.
• Executed As • Start Time • End Time This field displays the time when the task was completed or cancelled. • Duration This field displays the amount of time it took to run the task. This field displays the user context where the tools were executed from. This field displays the time when the task was started. NOTE: The list of task instances is based on user privileges and access levels. Users with administrative rights can view all task instances known to the system.
1. 2. From the menu, select Tasks & Logs→View Tasks Results. Click View Printable Report. A Print Report Question appears, asking to generate a report containing the selected target system or all target systems associated with the task instance. 3. 4. Select the report to print. Click OK to print the report.
Command line interface Use the mxtask command to execute tools immediately and to schedule tasks for later time. Perform this task from the command line interface (CLI). For assistance with this command, see the HP-UX or Linux manpage by entering man mxtask at the command line or see the Windows command line help. for information about accessing the manpage, see “Using command line interface commands”.
1. 2. From the menu, select Tasks & Logs→View Task Results. Click the task row and then select one of the following options: • Stop. Click Stop to stop a running task instance. For more information, see “Stopping a task”. • Delete. Select a task instance, and then click Delete. For more information, see “Deleting task results”. Note: If a task instance is running, a message appears informing you to stop the task instance before attempting to delete it. 3.
• “Delete” • “View task results” NOTE: If multiple users are accessing a task simultaneously, the changes made by the last user who edited the task are saved. For example, if User1 and User2 sign-in to HP SIM with administrative rights and User1 is editing a task while User2 is deleting the task, when User1 tries to save the edited task a message appears indicating that the task does not represent an object in the system and User1 cannot save the edited task.
Related topics • Managing with tasks • Task status types 292 Managing with tasks
12 Tools that extend management HP Systems Insight Manager (HP SIM) provides you with the following powerful management tools: • Cluster Monitor • Command Line Tools Use as part of a Distributed Task Facility (DTF). Available in HP SIM to run on single-system aware (SSA) systems • Custom Tools Use to create and manage custom tools that run on the Central Management Server (CMS) and on target systems.
• 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, Domain Name Service (DNS), file sharing, and so on.
• Installing RPM • Querying RPM • Uninstalling RPM • Verifying RPM • Accessing the 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 • Cluster Monitor • Device ping • Disk thresholds • Configuring DMI access • Storag
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. (Optional) Select Show original menu structure (and order) in the Quick Launch menu.
Related procedure ▲ Searching for tools Searching for tools To perform a tool search 1. Click Tool Search in the Search panel. The Tool Search page appears.
2. The HP Systems Insight Manager (HP SIM) menu structure is displayed on the main page. You can either 3. click the icon to expand the tree or enter text in the Search for box. After you locate the tool you are searching for, click the tool link to be taken to the appropriate tool page. Related topic ▲ Tool search Cluster Monitor Use Cluster Monitor to monitor Microsoft Cluster Server (MSCS) clusters. To use Cluster Monitor: 1.
Configuring cluster resource settings Configure the cluster resource settings to customize Cluster Resources for your environment. NOTE: When using the keyboard to input an alphanumeric character to highlight an option with the arrow keys in any dropdown list in the Cluster Monitor, press the Enter key to select the item. To configure cluster resource settings: 1. 2. 3. 4. Select Options→Cluster Monitor→Cluster Resource Settings. The Cluster Monitor - Cluster Resource Settings page appears.
Cluster Monitor Cluster tab The Cluster Monitor Cluster tab displays the following information for MSCS clusters: • Status Displays the cluster status. Cluster statuses include Critical, Major, Minor, Normal, and Unknown. See “System status types” for more information about status types. • Name • IP Address • Quorum Resource that maintains essential cluster data and guarantees that all nodes have access to the most recent database changes. The cluster name or alias.
an error has occurred and the exact state of the network could not be determined or the network state is unavailable). • Role Role the network name plays in the cluster: network name for the cluster, network name for computer systems in the cluster, or network name for groups in the cluster. • Description Description of the network. You can sort the information located on the Network tab by clicking a column heading. This sorts the information by that column in ascending or descending order.
MSCS status Monitoring MSCS status HP Systems Insight Manager (HP SIM) monitors Microsoft Clustering Service (MSCS) status on each monitored Windows cluster and displays it as a cluster attribute in the Cluster Monitor. It is a contributor to the cluster status shown in the CS column on the cluster table view page. Cluster Monitor polls the cluster on a set interval to retrieve the status value. See “Cluster Monitor polling rate” for information about MSCS Resource Settings.
NOTE: For additional information about the Microsoft Cluster Service, see Microsoft's documentation. Related topic ▲ Cluster Monitor Cluster Monitor resources and associated settings NOTE: Although Cluster Monitor is used for MSCS clusters only, the CPU and Disk thresholding functionality for Cluster Monitor works for any cluster in which the cluster nodes are running HP Insight Management Agents.
Adjust the status polling rate be configuring the Cluster Monitor's cluster resource settings. See “Configuring cluster resource settings” for more information. System status polling rate The system polling rate determines how often Cluster Monitor checks node status as reported by the appropriate HP Insight Management Agent running on the nodes. System is a node-level attribute. You can adjust the polling rate by configuring Cluster Monitor node resource settings.
NOTE: For additional information about the individual commands, see the associated manpage on an HP-UX and Linux system or the Windows command line help where the command tool is installed. NOTE: Command line tools provided by HP-UX and Linux, such as the ls and df commands, are run as root by default. For security reasons, you might want them to run as a specific user to avoid permitting unintended capabilities to a user. To launch a command line tool: 1.
Related procedures • Windows CMS • HP-UX and Linux CMS • Setting up managed systems Windows CMS Configuring managed systems from a Windows Central Management Server To run Configure or Repair Agents remotely against a system, you must have authorization to run the Configure or Repair Agents tool. You must have administrator privileges for Windows systems on the target systems to configure or repair the agent settings. You must have root privileges for HP-UX and Linux systems.
c. d. In the Password (Verify) field, re-enter the system administrator's password exactly as it was entered in the Password field. In the Domain field, enter the Windows domain if you are using a domain account. Note: The credentials used in this step must work for all target systems that have been selected. HP recommends using domain administrator credentials. Credentials entered here are not saved by HP SIM except to run a scheduled task later. 5. Click Next.
Supported systems HP WBEM Provider Itanium-based systems Not supported with Windows operating system (2003) HP ProLiant Agent Open SSH Version Control Agent 5.1.10 3.71 2.1.7.770 System Management Homepage version 2.1.7 is also installed, if necessary, with these agents. NOTE: If you want to install a 64-bit agent or provider, be sure the target system is identified as a 64-bit system in HP SIM. If your system is not correctly identified, go to System Page →Edit System Properties.
8. The Step 4: Configure or Repair Agents page enables you to select options to configure the target system. The following options are available: • 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. For this section, the following must be considered: • Create subscription to WBEM events so that WBEM events will be sent to the CMS.
system and will be configured as the WBEM user in the System Protocol settings. This configuration step is not necessary if HP SIM is configured with a user with administration rights. This user is not created by HP SIM. The user should already exist as either a domain user or one local to the managed system. The user will be added to the "DCOM Users” group on the managed system and will be given read-only access to WMI information, plus read-write permissions to the HPQ name space.
• Configure secure shell (SSH) access. Select this option to configure SSH access on managed systems. If this option is selected, you must select one of the following options: • Host based authentication for SSH Note: For this option to work, the user name and password provided in step 2 must be an administrative level account. For Linux or HP-UX targets, it must be the "root" account and password.
a. b. 9. In the Password field, enter the new administrator password. In the Confirm Password field, re-enter the new administrator password exactly as you entered it previously. Click Run Now. The Task Results page appears. Note: Click Schedule to run this task at a later time. Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of which might have different results. The log results indicate whether the repair attempt was successful.
4. From the Step 2: Enter credentials page: a. In the User name field, enter the system administrator name. b. In the Password field, enter the system administrator's password for the user name previously entered. c. In the Password (Verify) field, re-enter the system administrator's password exactly as it was entered in the Password field. d. In the Domain field, enter the Windows domain if you are using a domain account.
6. The Step 3: Configure or Repair Agents page enables you to select options to configure the target system. The following options are available: • 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. For this section, the following must be considered: • Create subscription to WBEM events so that WBEM events will be sent to the CMS.
system and will be configured as the WBEM user in the System Protocol settings. This configuration step is not necessary if HP SIM is configured with a user with administration rights. This user is not created by HP SIM. The user should already exist as either a domain user or one local to the managed system. The user will be added to the "DCOM Users” group on the managed system and will be given read-only access to WMI information, plus read-write permissions to the HPQ name space.
• Configure secure shell (SSH) access. Select this option to configure SSH access on managed systems. If this option is selected, you must select one of the following options: • Host based authentication for SSH Note: For this option to work, the user name and password provided in step 2 must be an administrative level account. For Linux or HP-UX targets, it must be the "root" account and password.
a. b. 7. In the Password field, enter the new administrator password. In the Confirm Password field, re-enter the new administrator password exactly as you entered it previously. Click Run Now. The Task Results page appears. Note: Click Schedule to run this task at a later time. Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of which might have different results. The log results indicate whether the repair attempt was successful.
NOTE: Windows Management Instrumentation (WMI) is the implementation of WBEM from Microsoft. See WMI for more information. NOTE: The WBEM providers cannot be installed on HP-UX or Linux systems. NOTE: A Common Information Model Object Manager (CIMOM) acts as the interface for communication between WBEM providers and management applications such as HP Systems Insight Manager. The CMS must have the correct credentials to authenticate to WBEM and WMI.
To install the SNMP provider from the Manage Communications page, select Quick Repair→Install Providers and Agents→Install SNMP Agents (HP ProLiant Insight Management Agents) for Windows. To configure the read community string on the CMS, select Options→Protocol Settings→System Protocol Settings from the HP SIM menu. To configure the read community string for multiple systems, select Options→Protocol Settings→Global Protocol Settings and set the read community string.
NOTE: If the Insight Management Agents are not installed, software inventory cannot be collected by the VCA. However, the VCA can still be used to install software. HP Version Control Agent The HP Version Control Agent (VCA) is an HP Insight Management Agent that is installed on a system to enable you to view the HP software and firmware that is installed on that system.
Related topic ▲ WBEM indications Learn More - Configuring a non-administrative account for HP SIM to access WMI data Configure a non-administrative account for HP SIM to access WMI data. This option is applicable to Windows systems with HP WBEM providers. The configuration of the managed system will be updated to allow the specified user to access WMI information over the network.
Learn More - Configuring SSH If you select Configure secure shell (SSH) access, you must select one of the following: • Host based authentication for SSH Note: For this option to work, the user name and password provided in step 2 must be an administrative level account. For Linux or HP-UX targets, it must be the "root" account and password.
Single-system aware (SSA), muliple-system aware (MSA), and Web-launch aware (WLA) tools can be created and launched. You can create the following types of custom tools: • Remote tool A tool that runs on selected target systems. It might copy files to the target systems or run specific X-Window applications on the target systems. This tool can be scheduled. • CMS tool A tool that runs on the CMS. It is usually a script or batch file and can pass in environment variables.
Otherwise, the tool runs as the HP Systems Insight Manager (HP SIM) user and that user's SSH public key must be configured on the managed system using the mxagentconfig command. Menu placement A string in the form base|submenu|subsubmenu can be used to place custom tools in specific menu locations.
To create a custom 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 in length, and no more than 255 characters in length.
5. 6. Specify the user account on the target system that will be used for the tool. Select one of the following options: • Logged-in user • Special user ("root" for UNIX and Linux systems, "Administrator" for Windows systems) Execution of the tool will substitute Administrator for targets running Windows and root targets with targets running Linux and HP-UX. The tool will not run on targets with an unknown operating system. • Specific user Execution of the tool will be whatever user is logged in.
To create a custom Central Management Server tool: 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 in length, and no more than 255 characters in length.
5. 6. 7. Specify the user account on the target system that will be used for the tool. Select one of the following options: • Logged-in user • Special user ("root" for UNIX and Linux systems, and "Administrator" for Windows systems) • Specific user Enter the Command with parameters field. (Optional) Enter the Environment variables for the tool. See “Environment variables for custom tools” for a list of variables available from HP Systems Insight Manager (HP SIM).
1. 2. 3. 4. 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 in length, and no more than 255 characters in length. The first character of the name must be alphabetic.
• Run as user • Automatic Event Handling The following options are available for managing custom tools: • “New” • “Edit” • “View tool definition” • “Run Now/Schedule” • “Delete” New This option enables you to create a new custom tool and opens the Select the tool to create page. Edit This option enables you to edit an existing custom tool. To edit a tool, select the tool, and then click Edit. The Edit Custom Tool Details section appears.
c. d. In the Help comments field, enter any comments for the application. In the Menu placement field, enter the full path (from the root of the HP SIM console) and the file name of the application. For example: c:\custom code\romflash.bat 4. 5. Specify the user account on the target system that will be used for the tool.
1. 2. 3. Select Tools→Custom Tools→Manage Custom Tools. The Manage Custom Tools page appears. Select the tool you want to edit, and then click Edit. 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 in length, and no more than 255 characters in length. The first character of the name must be alphabetic.
a. b. c. d. In the Name field, enter the command name. Custom tool names must be at least one character in length, and no more than 255 characters in length. The first character of the name must be alphabetic. Subsequent characters can be letters, digits, spaces, or any of the following: "-", ".", "(", ")" or "_". In the Description field, enter the necessary information for the application. In the Help comments field, enter any comments for the application.
Viewing tool definition files You can view the XML code, which are tool definition files, below the table of custom tools by clicking View Tool Definition from the Manage Custom Tools. To display the tool definition files: 1. 2. Select Tools→Custom Tools→Manage Custom Tools. The Manage Custom Tools page appears. Select a tool, and then click View Tool Definition The XML code appears.
NOTICESTATE. Internal value used by HP SIM, indicating whether the notice is cleared NOTICEPLAINTEXT. Plain text description of the notice that contains detailed information about the notice (In Progress, Cleared, or Not Cleared) NOTICERAWDATA. The raw data from the notice is passed as a string; this is a small pipe (|) delimited set of variables and might be useful for some simple parsing rules NOTICESEVERITYSTR.
RELATEDDEVICENAME%d. This environment variable returns the name of the associated system where %d is the iteration number, for example: IF, RELATEDDEVICECOUNT = 2 Then, RELATEDDEVICENAME0=DeviceName0 RELATEDDEVICENAME1=DeviceName1 RELATEDDEVICEIP%d. This environment variable returns the IPaddress of the associated system where %d is the iteration number, for example: IF, RELATEDDEVICECOUNT = 2 Then, RELATEDDEVICEIP0=111.111.111.111 RELATEDDEVICEIP1=222.222.222.222 RELATIONSHIP%d.
https://deploy.hp.com:280/deploy/deployimage.jsp? device1=nodea.hp.com&device2=nodeb.hp.com If we have only 1 selected target system in the above example, the expanded URL string would look like: https://deploy.hp.com:280/deploy/deployimage.jsp? device1=nodea.hp.com Because there is no current selection when we get to the repeat block, the entire repeat block is suppressed during the substitution process.
Parameter Description %u Name of the user running this tool %e Name of the user to execute this tool as %s Management server host name of the core CMS running the tool %# (where # is a positive integer) Substitute the value input by the user for the parameter referenced by the number (#) provided, as a list index position (one-based...
Tool filtering Tool filtering is a facility enabling the tool writer to control whether the tool should be executed on a selected system. Most tools are platform dependent in that their successful execution depends on commands that are provided on some platforms but not on others. For example, the bdf tool depends on the bdf command, which is provided on HP-UX platforms, but is not available under that name on Linux platforms.
A system filter expression is used as part of an include filter expression. There are three types of include filter expressions. Each type allows a different category of attribute names on which to be filtered. Category Filter type Attribute names allowed Operating System os OSName, OSVendor, OS Revision Hardware hardware DeviceType, DeviceSubType, Model Protocol Support protocol Any protocol name, except HTTP Other other Can be any predefined system attribute or any custom-system attribute.
operator="eq" value="HPVectra" /> If a tool contains more than one include filter of the same type, the conditions of the filters are logically OR'd together.
Web-launch aware tools must specify a main URL. When specifying file copy pairs, the destination file paths for each file copy pair within a single TDEF must be unique. Specifying the same destination file path for multiple source file paths results in a file parsing error. An error occurs when running a tool that copies a file if the file does not exist or is unreadable.
ssa-block, attribute* ) >
