HP Systems Insight Manager 6.
© Copyright 2010 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents I Introduction...............................................................................................11 1 About this document.............................................................................12 User Guide.....................................................................................................................................12 Systems Insight Manager User Guide layout........................................................................................
7 Manage Communications......................................................................34 Configuring the managed system software using the Configure or Repair Agents feature from the CMS.......34 Sending test traps and indications......................................................................................................34 8 Automatic event handling......................................................................36 Example automatic event handling tasks................................
Scheduling tools..............................................................................................................................58 Managing with tasks........................................................................................................................58 Viewing results................................................................................................................................59 Example - Device ping..........................................................
HP-UX and Linux.........................................................................................................................83 Systems Insight Manager database....................................................................................................83 SQL Server and MSDE................................................................................................................83 Remote SQL Server.......................................................................................
Configuring the SNMP trap destination on Windows 2000.......................................................104 Configuring the SNMP trap destination on HP-UX....................................................................104 Loading the HSV MIB on the CMS for EVA..............................................................................104 Discovery......................................................................................................................................
Data Collection...................................................................................................................................127 Database...........................................................................................................................................129 Discovery...........................................................................................................................................129 Event......................................................
mxtool command parameters................................................................................................................148 Parameterized strings...........................................................................................................................149 Common tool attributes........................................................................................................................150 Tool Filtering attributes....................................................
List of Tables 2-1 12-1 12-2 12-3 14-1 14-2 17-1 20-1 21-1 21-2 21-3 23-1 23-2 23-3 23-4 26-1 E-1 E-2 E-3 E-4 G-1 G-2 G-3 G-4 G-5 G-6 G-7 G-8 G-9 G-10 G-11 G-12 G-13 G-14 H-1 Status types....................................................................................................................................14 Health status types........................................................................................................................43 Software status types..........................
Part I Introduction 11
1 About this document User Guide HP Systems Insight Manager provides this user guide to help you understand management features. Systems Insight Manager User Guide layout • Introduction Describes the features, basic concepts, and using the graphical user interface (GUI) in Systems Insight Manager.
2 Product overview What's new in Systems Insight Manager 6.0 • Scalability HP Systems Insight Manager can mange up to 10,000 systems (up to 5,000 servers, with additional 5,000 management processors, VMS, and so on) when using Windows 64-bit. • Reporting Systems Insight Manager 6.0 introduces enhanced reporting including tables and graphs for easier access to Systems Insight Manager data. • Migration New migration tool to transfer settings from a Systems Insight Manager 5.3.
Basic concepts Discovery and identification Systems Insight Manager can automatically discover and identify systems attached to the network using information from management protocols such as Simple Network Management Protocol (SNMP), Windows Management Instrumentation (WMI), WBEM, Secure Shell (SSH), and Secure Sockets Layer (SSL). Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs.
Tools and tasks Tools are actions you perform on the managed systems from within Systems Insight Manager's GUI or CLI. Many tools ship with Systems Insight Manager, but you can also add your own custom tools. Tasks are instances of running tools. To create a task, select target systems (systems or events that the task will work on) and then select the tool from the Systems Insight Manager menu. Tasks can be run immediately or scheduled, and you can view task results by selecting Tools→View Task Results.
Each time you receive an Untrusted Connection warning in Firefox, you must add a permanent security exception to avoid seeing the warning again for that host. Note that if you browse to a single system using its short host name, fully qualified Domain Name Service (FQDN), and IP address (for example, three different ways), you must add three security exceptions.
• 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. Procedure 2-1 Configuring the browser in Internet Explorer 1. 2. 3. 4. In Internet Explorer, enable Integrated Windows Authentication under Tools→Internet Options→Advanced tab. The CMS must be in the Local Intranet or Trusted Sites zone, which can be configured under the Tools→Internet Options→Security tab.
Guided tour of the Systems Insight Manager user interface The GUI includes the following six regions: 1. Banner area The banner provides a link to the Home page, a link to Sign Out of Systems Insight Manager, and displays the user that is currently signed in. Click the minimize icon in the top right corner to minimize the banner. To maximize the banner, click the maximize icon. 18 2.
NOTE: To maximize the workspace, click the Maximize link next to the Help icon ( the workspace to its original size, click Restore Size. ). To restore Customizing views A Customize link is available in the upper right of many pages in Systems Insight Manager. Use this link to customize the way the page is presented.
Part II Setting up Systems Insight Manager 20
3 Setting up managed systems Setting up managed systems involves installing the required Management Agents software and configuring the supported protocols to communicate with the Systems Insight Manager software. Setting up Windows servers to be managed by Systems Insight Manager To be fully managed by Systems Insight Manager, HP ProLiant servers running Windows should have the Insight Management Agents installed. These agents are part of the ProLiant Support Pack.
a. b. c. d. In the User name field, enter the Windows administrator user name for the target system. In the Password field, enter the administrator password. In the Password (Verify) field, re-enter the Windows administrator password. In the Domain field, enter the Windows domain. This field can be left blank if the system is not part of a domain. NOTE: If ProLiant Support Pack has not been previously installed on the system, you must enter the credentials here and do not select Use sign-in credentials.
NOTE: To expand the System Software Baseline to display all contents, click the in the upper-left corner of the Select a Support Pack to Install section. Click the the listings. icon located icon to collapse (Optional) To install and configure OpenSSH on the target systems, select Install and initialize SSH (Secure Shell). This option is disabled by default. 9.
If iCap information is desired, also install: ▲ 2. B9073BA version 08.01.01 iCAP for HP-UX Ensure the managed system software is installed. To verify that the minimum required software is installed, log in to the remote system, and run the following command: $ swlist –l bundle T1471AA B8465BA OpenSSL To verify that the optional providers and HP System Management Homepage are installed, run commands such as: $ swlist –l bundle LVMProvider WBEMP-LAN-00 SysMgmtWeb SysFaultMgmt OnlineDiag 3.
Configuring SSH access On the CMS, copy the SSH-generated public key from the CMS to the managed system using the mxagentconfig: Use one of the following commands: • mxagentconfig -a -n -u root -f • mxagentconfig -a -n -u root -p NOTE: Using the -p option exposes the password through ps output, so using the -f option (with a file only readable by root, and containing only the managed system root password) is highly recommended when using mxa
Setting up Linux servers to be managed by Systems Insight Manager To be fully managed by Systems Insight Manager, HP ProLiant servers running Linux should have the Insight Management Agents installed. These agents are part of the ProLiant Support Pack. You can install the PSP manually, or configure it to be installed as part of your normal operating system deployment procedures.
4. Edit the snmpd.conf file. For Red Hat Linux, open the following file in the vi editor: vi /etc/snmp/snmpd.conf For SuSE SLES 8, open the following file in the vi editor: vi /usr/share/snmp/snmpd.conf a. Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS: trapsink IPaddress where IPaddress is the IP address of the CMS. b.
4 Credentials In Systems Insight Manager, credentials are used to enable the CMS to communicate with managed systems, through WBEM, WS-MAN, SSH, and SNMP. However, the Sign-in credential is used unless you configure the other protocols. The Sign-in credential is protocol independent and can be tied to systems through the discovery credential. In Systems Insight Manager, there are three different types of credentials: • System credentials Credentials used by identification to access managed systems.
password="pswd" /> username="root" username="root" username="root" username="euploid\administrator" You can include the IP addresses of the systems to be discovered in an XML comm
5 WMI Mapper Proxy Windows systems use a variation on the WBEM management protocol called WMI. For Systems Insight Manager to communicate with Windows systems, the WBEM protocol it uses must be converted to the WMI protocol and vice versa. This is the function of the WMI Mapper Proxy. This proxy is typically installed on the same system as Systems Insight Manager when Systems Insight Manager is installed on a Windows system.
6 Discovery Discovery is the process of finding systems in the management domain so that they can be managed from the CMS by Systems Insight Manager;. Systems Insight Manager can automatically discover and identify systems attached to the network using information from management protocols such as SNMP, WMI, WBEM, SSH, and SSL. Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs.
NOTE: Citrix Xen VMs discovered in category 5 will always return a discovery error unless the Citrix Xen Host has been registered through Configure→Virtual Machine→Register Virtual Machine Host. If you have a small network, an alternate way of setting up your discovery tasks is to create a single task with one IP address range and all of the required credentials for the systems in that range.
Discovery filters Discovery filters prevent or enable certain system types from being added to the database through automatic discovery. When you want to discover systems of a certain type, using filters is much easier than specifying the IP addresses of each individual system. Discovery filters do not apply to individually added systems. You can access discovery filters from the Discovery page by selecting Enable discovery filters in the Configure general settings, section.
7 Manage Communications Use the Manage Communications feature to troubleshoot communication problems between the CMS and targeted systems. For each failed communication function, troubleshooting information is available. You can reconfigure communication settings, launch agents, and push certificates to target systems.
Procedure 7-1 Sending test traps on a Windows or HP-UX system 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. • dm_memory • lpmc_em • disk_em • dm_chassis • dm_core_hw • ia64_corehw • fpl_em Confirm that the test indication is shown in the Systems Insight Manager event table view after you trigger it.
8 Automatic event handling Automatic event handling enables you to define an action that Systems Insight Manager performs when an event is received. Users who want to access this feature must have administrative rights. • Managing Tasks Enables you to view definitions, copy tasks, edit tasks, view task results, disable or enable tasks, or delete existing Automatic Event Handling tasks. • Creating a New Task Enables you to create a new Automatic Event Handling task.
9 Users and Authorizations Systems Insight Manager enables you to configure authorizations for specific users or user groups. Authorizations give the user access to view and manage systems. Each authorization specifies a user or user group, a toolbox, and a system or system group. The specific set of tools that can be run on a system is specified in the assigned toolbox. You must plan which systems each user will manage and which specific set of tools each user is authorized to execute on managed systems.
10 Managed environment The Managed Environment feature enables you to select the operating systems that you will manage. There are four options: Windows, Linux, HP-UX, and Other. The selections made here configure Systems Insight Manager to hide collections, tools, and reports for operating systems you do not manage. NOTE: These settings can be changed at any time, and the hidden collections, tools, and reports can be made visible again.
Part III Systems Insight Manager basic features 39
11 Basic and advanced searches Basic search The Search feature enables you to quickly retrieve details about a system using its name or common system attributes. For example, you could search for a system name, IP address, or a word such as server, HP-UX, or storage. The search field only allows the following characters: letters, numbers, tilde (~), dash (-), period (.), underscore (_), apostrophe ('), and space.
Searching for tools The Tool Search feature provides a quick way to search and filter textually, based on tool names, tool locations in the Systems Insight Manager cascading menu structure, and tool descriptions. For additional information, see the Systems Insight Manager online help.
12 Monitoring systems Viewing system collections In Systems Insight Manager monitoring systems involves Systems Insight Manager polling HP Insight Management Agents or firmware on the managed systems to retrieve status information, and then displays this information as status icons. There are several types of status that can be displayed, such as Health Status (HW), Software Versioning Status (SW), or Management Processor status (MP). Other status icons might be added by plug-ins to Systems Insight Manager.
status is determined by information collected live through the WBEM protocol and the information provided by the WMI provider. You can access Property pages in the following ways: • • From the System Page on the System tab, click Properties. The Property pages appear for the target system. • Select Tools→System Information→Properties, select the target system, and click Run now. The Property pages display for the target system.
Status icon Status type Description Unknown Systems Insight Manager cannot obtain management information about the system using SNMP>. Although no management instrumentation information is available, the system can be pinged. It might have an invalid community string or security setting, or it might be an IP address that is no longer associated with a system. Informational The system might be in a transitional state or a nonerror state.
Status icon Status type Description Predictive Failure, Error, Aborted, Supporting Entity in Error A major problem exists with this system and must be addressed immediately. Degraded, Stressed • Predictive Failure indicates that the element is functioning nominally, but a failure is likely to occur in the near future. • Error indicates that the element is in an error state. • Aborted indicates that the element's functionality has stopped abruptly.
The Suspend or Resume Monitoring tool enables you to suspend monitoring of a single system or multiple systems, which enables systems to be excluded from status polling, identification, data collection, and the automatic event handling features of Systems Insight Manager. The available suspend lengths include the predetermined increments of 5 minutes, 15 minutes, 1 hour, 2 hours, 8 hours, 1 day, 2 days, 3 days, 4 days, 5 days, 6 days, and 7 days. You can turn on the suspend tool indefinitely.
NOTE: This tool can be used for a single system. However, some of the properties that are available from the System Page are not available when selecting this option. For example, the serial number is not available here, whereas it is available from the System Page. NOTE: To complete this procedure, you must be authorized to use the EDIT_SYSTEM_PROPERTIES tool on the systems you want to update. See the Systems Insight Manager online help for information on editing system properties.
13 Event management Events are typically sent to the CMS from agents running on the managed systems. However, some events are generated directly from the CMS itself. Managed systems must be configured to send events to the CMS. After the CMS receives the event, if it passes the filters, any actions configured to happen upon its receipt are run, and the event is stored in the Systems Insight Manager database for later viewing.
IMPORTANT: When using time filters, you can use on-call style e-mails or pages. If you want one person to be notified during business hours and another at night, create two different tasks and set the time filter appropriately. NOTE: This same type of task configuration can be applied to a Paging Task to use a modem in the Systems Insight Manager server to page through a cell phone or alphanumeric pager. NOTE: Paging is only supported on a CMS running Windows.
NOTE: The URL specified in an e-mail message appears only if the format is set to standard. You can send the following e-mail pages from Systems Insight Manager: • Standard • Pager/SMS • HTML Example of a standard e-mail page From: Doe, John Sent: Wednesday, April 28, 2004 5:04 PM To: Doe, Jane Cc: Smith, Jim; Jones, Beth Subject: System A: Storage System side panel is removed (Ver. 3): Standard E-mail format Event Name: Storage System side panel is removed (Ver.
Example of an HTML page From: Doe, John Sent: Wednesday, April 28, 2004 5:04 PM To: Doe, Jane Cc: Smith, Jim; Jones, Beth Subject: qaunit1: Storage System side panel is removed (Ver. 3): HTML Format E-mail testing Where quanit1 is the system name. Example - Creating a task to send an e-mail when a system reaches a critical state The following instructions set up an automatic event handling task to be run when a discovered system goes to a Critical status.
13. Specify the e-mail address that the management server uses when sending e-mail notifications in the Sender's Email Address box. 14. To authenticate your SMTP server, select the Server Requires Authentication checkbox. 15. Specify the account name in Account name box. 16. Specify the password in the Password box. 17. Click OK to save changes. 18. To configure status change events, select Options→Events→Status Change Event Settings. The Status Change Event Settings page appears. 19.
Example - Creating a task to delete all cleared events The following example describes how to create a task to delete all cleared server events from the Systems Insight Manager database. This task is useful to include in your management portfolio because deleting cleared events on a regular basis empties the database of unnecessary entries and improves system performance.
14 Reporting in Systems Insight Manager Standard reports Standard reports are shipped with Systems Insight Manager. The reports are based on common user scenarios and do not need any additional configuration or enablement. These reports are installed, configured, and available for use as soon as Systems Insight Manager is installed and configured. Standard reports are tied to existing systems collections in Systems Insight Manager, for instance, All Systems or All Servers.
• Edit Systems Insight Manager enables you to edit existing report configurations. You can save these updated report configurations over the existing report configuration, or you can save it as a new report configuration. NOTE: You must have administrative rights or operator rights to create, save, edit, copy, or delete report configurations. Users with user rights cannot edit the report configurations. • Delete • Showing SQL Queries.
Select Reports→Enhanced Reports. The Enhanced Reports, Reports by Product page appears. Run Enhanced reports Running reports executes an available report in the reporting engine. The generated report is displayed in a new page when Run Report is clicked. A generated report provides you with the report name, associated system collection, and report run date and time in the following formats. You select the format before you run the report.
Deleting reports User-created reports located in the Reports by Product section can be deleted. Before the report is deleted, a popup message displays asking if you are sure you want to delete the selected report. If you click OK, the report is deleted and the product and report page is refreshed to show the correct status of the reports.
15 Systems Insight Manager tools Target selection Targets are systems that a tool acts upon. Targets can be single systems, collections, or groups of systems that are chosen just for the task at hand. You can select the targets either before or after selecting the tool. You can verify and modify the selection using the task wizard. After the targets are verified, they appear in the title area of the tool. NOTE: Some tools cannot work on multiple systems.
Systems Insight Manager provides system-delivered (default) tasks. These tasks can be disabled or have their schedules modified but they cannot be removed or reassigned to another user. Systems Insight Manager requires these tasks (for example, Data Collection) to provide a complete picture of the systems being monitored. Viewing results After a task runs, you can view the task results by selecting Tasks & Logs→View Task Results.
Part IV Systems Insight Manager advanced features 60
16 Collections in Systems Insight Manager 6.0 Collections in Systems Insight Manager Systems and events are grouped into collections based on information from the Systems Insight Manager database. After a collection is defined, you can display the results or associate the collection with a task. You can also save an edited or unedited collection as a collection with another name. You can use collections to organize large numbers of systems into smaller, more meaningful groupings.
• Run a system search and save the search criteria as the attributes defining a collection. Saving a collection from the Advanced Search page For more information on saving collections, see the HP Systems Insight Manager online help. Types of collections • By member When you create a collection, you can select exactly which specific systems or collections you want to include. From the, Customize Collections page, click New. The New Collection section appears. Select Choose members individually.
Because collections by attribute use a database query, collections that are complex take more system resources every time they are accessed. Keeping collections simple minimizes performance impact. • Combination collections Combination collections are new in Systems Insight Manager 6.0. This new form of collections enables you to bind together a system collection and an event collection. Combination collections enable you to reuse and recombine system and event collections that you have created.
members of these collections. Setting properties on systems that might not be part of the collection in the future would be of very limited value. • Edit Any collection can be edited. However, collections cannot change type. For example, you can change the criteria for a collection that is defined by attribute, but you cannot change the collection type so the collection is a collection by member or a combination collection.
There are two instances of SystemC in the view of the hierarchy because CollectionC is the same throughout the application. Any place that CollectionC is referenced, it will always contain the same systems. However, SystemD appears only under CollectionB. CollectionB and Copy of CollectionB are distinct and independent collections. • Move Move enables you to easily move a collection exactly where you want it in the hierarchy.
that collection is made not visible, then the task will not run on that collection. You can change the visibility setting at any time. • Status Displayed property You can set the Status Displayed property to enable you to easily view the aggregate status of a particular collection in the System and Event Collections panel. You can set this property only on individual systems or on collections by attribute, for example, the lowest System and Event Collections panel displaying collection aggregate status.
be displayed as icons or a tree. Collections by members default to a tree view, but they can also be displayed as icons or a table. Special types of system collections default to picture views or special consoles. You can change the default view using this property.
17 Systems Insight Manager custom tools General concepts Custom tools are tools that can be created by the user to run on the CMS or on target systems. For example: • Remote tool A tool that runs on selected target systems. It might copy files to the target systems or run specific X-Window applications on the target systems. You can schedule this tool. • CMS tool A tool that runs on the CMS. It is usually a script or batch file and can pass in environment variables.
Name Description by a universal resource locator (URL). Web-launch applications that do not share Systems Insight Manager certificates should be executed in a separate frame. Application launch tool OR CMS Tool in the GUI An application launch tool is a batch file, script, or executable that runs on the CMS and can reference environment variables specified by the tool to access device or event information.
Then, DEVICEIPADDRESS0 = 111.111.111.111 DEVICEIPADDRESS1 = 222.222.222.222 DEVICEMACADDRESSCOUNT. The number of MAC addresses collected for the system. Before this information is available, you must run a Data Collection task. DEVICEMACADDRESS%d. Based on the MAC address count, %d is an integer that references the actual MAC address environment variable. For example: IF, DEVICEMACADDRESSCOUNT = 2 Then, DEVICEMACADDRESS0=00:80:5F:7F:B0:81 DEVICEMACADDRESS1=00:80:C7:29:EF:B6 GENERICTRAPID.
Menu level Example top-level-menu Tools top-level-menu|first-level-cascade Tools|Custom Tools top-level-menu|first-level-cascade|second-level-cascade Tools|Custom Tools|My Tools For example, place a tool under Tools→Custom Tools, place an entry in the Menu placement field such as Tools|CustomTools. By default, if the Menu placement field is left blank, the tools are placed in Tools→Custom Tools.
• Command • 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 Use to create a custom tool and open the Select the tool to create page. Edit Use to edit an existing custom tool. Select the tool, and then click Edit. The Edit Custom Tool Details section appears. You can edit all fields and add or delete environment variables.
For this example, it is assumed that the administrator will want to execute this procedure again and be able to quickly locate it in the Systems Insight Manager menus, so an entry in the Deploy menu is made and called Software Distributor, which when invoked allows the administrator to execute this custom tool. Procedure 17-1 Creating the Software Distributor tool 1. Log into the CMS using a valid user name and password. Systems Insight Manager grants authorization based on the operating system login.
NOTE: The must be a directory that exists on the Managed Node. The default file permission value used by DTF for a file copy operation is 755. If another permission is to be used, an explicit file permission command such as chmod should be included in the copy block element for security reasons. 8. Type the following attribute element code, which states where the tool will be located in the Systems Insight Manager menu. 9. To finish the TDEF, enter the final tool list tag as shown below.
Note that file names on Linux and HP-UX operating systems are case-sensitive. The directory used by Systems Insight Manager to store tools is as follows: • for HP-UX and Linux systems: /var/opt/mx/tools • for Windows systems: C:\Program Files\HP\Systems Insight Manager\tools 11. To add the new tool to Systems Insight Manager, perform the procedure described in the section “Adding a TDEF to Systems Insight Manager”. For more information about specific SSA tool attributes, see SSA-specific attributes.
NOTE: When the XWindows tool is launched, the system running the browser must be running an XWindows server for the tool's GUI to be visible. For more information about specific MSA tool requirements and attributes, see MSA-specific attributes. Example Enabling Remote Desktop tool Remote Desktop is a Microsoft feature that enables you to remotely access any Windows 2003 server.
Adding a TDEF to Systems Insight Manager After you create a custom TDEF, to function, you must add it into Systems Insight Manager. Add a TDef to Systems Insight Manager using the mxtool -a command, as described in the following procedures: Procedure 17-2 Adding a TDEF to Systems Insight Manager 1. At a terminal or command line prompt, type mxtool -a -f . NOTE: 2. For more information about mxtool command parameters, see mxtool command parameters.
NOTE: If a task or task results are tied to a tool, by default the tool cannot be removed. The -x force option is used in this case. Modifying a TDEF Modifying a TDEF allows users to customize the XML to align with their business. Each TDEF included can be modified to fit with each customers business needs. To modify a TDEF to execute as a different user, perform the following steps: Procedure 17-4 Modifying a TDEF 1.
18 Understanding Systems Insight Manager security This chapter provides an overview of the security features available in the Systems Insight Manager framework. Systems Insight Manager runs on a CMS and communicates with managed systems using various protocols. You can browse to the CMS or directly to the managed system. Securing communication Secure Sockets Layer (SSL) SSL is an industry-standard protocol for securing communications across the Internet.
WBEM All WBEM access is over HTTPS for security. Systems Insight Manager is configured with a user name and password for WBEM agent access. Using SSL, Systems Insight Manager can optionally authenticate the managed system using its SSL certificate. For HP-UX, certificates can be used instead of username and password for WBEM authentication. You can configure WBEM authentication from the System Credentials→WBEM tab by selecting Options→Security→Credentials→System Credentials.
the CLI command mxnodesecurity. A few passwords might be stored in a file on the CMS that are also encrypted using the same 128-bit Blowfish key. These passwords can be managed using the mxpassword command. The password file and the Blowfish key file are restricted with operating system file permissions to administrators or root. Prior to Systems Insight Manager 5.
the managed systems without any user interaction. The session times-out after 20 minutes if the browser is closed or navigates to another site. An active mode is also supported where the session times out after 20 minutes if the user does not interact with Systems Insight Manager, by clicking a menu item, link or button. You can enable active mode by editing the globalsettings.props file and change the EnableSessionKeepAlive setting to false.
such as private keys and passwords, which are stored in a recoverable format on the file system. Systems Insight Manager does not store user account passwords for users signing into Systems Insight Manager. IMPORTANT: Systems Insight Manager sets appropriate restrictions on the application files. These restrictions should not be changed because this could affect the operation of Systems Insight Manager or allow unintended access to the files.
Command-line interface Much of Systems Insight Manager’s functionality can be accessed through the command line. To access the command-line interface, you must be logged on to the CMS using an operating system account that is a valid Systems Insight Manager user account. That account’s authorizations and privileges within Systems Insight Manager apply to the command line interface as well.
4. 5. Add a user to access WMI data along with their access rights. The enable account and remote enable permissions options must be enabled for correct operation of Systems Insight Manager. The user name and password specified here must be configured in the CMS. • Set up user accounts for Insight Web Agents • Add the CMS SSH public key to the system’s trusted key store by running mxagentconfig on the CMS.
Procedure 18-1 Setting security to strong 1. Generate certificates from your certificate server for each managed system and the Systems Insight Manager system. To do this, first generate a certificate signing request (CSR) from the various systems. This generates a PKCS#7 file. This file should then be taken to the certificate server and signed, and then the resulting file (generally a PKCS#10 response) should be imported into the each managed system and the Systems Insight Manager system.
19 Privilege elevation Privilege elevation enables users without root privileges to run tools requiring root privileges on HP-UX, Linux, and VMware ESX managed systems. To use this feature with Systems Insight Manager, a privilege elevation utility such as su, sudo, or Powerbroker must be installed on the managed system.
20 Contract and warranty The Contract and Warranty Status is available when you have a Windows CMS, and the HP Insight Remote Support Pack is installed. You can view Contract and Warranty status updates for HP systems that have contract and warranty data collection enabled. Click the Contract and Warranty Status icon to view the Contract and Warranty Details page for the system.
collected by Systems Insight Manager during identification, contract and warranty data will not be collected. • Monthly contract and warranty collection This task collects contract and warranty data every month. If the required system properties are not entered for a system or automatically collected by Systems Insight Manager during identification, contract and warranty data will not be collected.
• • B: Delivery blocked • C: Cancelled. Active Obligation. This value is true if there is an active support contract for a system. The contract start and end date is listed for each contract item along with the following information: • Status The possible values are: • A: Active. • F: The start date is in the future. • X: Expired. • E: There is no end date. • I: The agreement is informal. This status might mean that the agreement is not finalized. • B: Delivery blocked • C: Cancelled.
Status Icon Icon Meaning Description Minor • Contract information is temporarily unavailable. • The contract expires in 30 days. Warning The contract expires in 90 days. Normal The system has a valid contract or warranty. Unknown No contract information was found. The system might not have a serial number or product ID. Disabled The Do not collect contract and warranty data for this system option is set for the system.
21 License Manager License Manager enables you to view and manage product licenses within the Systems Insight Manager user interface. To access additional information about Updates, Upgrades, and Technical support, contact your HP services or HP partner representative or access the IT Resource Center (ETC) at www.itrc.hp.com.
For some products, the license is stored in a licensing structure in the Windows registry on the licensed system. License Manager employs Microsoft's remote registry API over the COM protocol to assign licenses to and collect license information from those remote systems. License information is duplicated in the Systems Insight Manager database, but licenses are managed remotely and must be periodically collected to keep this information current.
License Type Description Duration Offers time limited, full functionality license. A Duration license (DLL) can be assigned to a system multiple times. When the licensed product consumes a license and that license subsequently expires, a new license will be consumed and removed from the stack of assigned licenses (if there are any and using the same license key).
you which license keys are "support and update enabled" and which license keys require the purchase of future updates and upgrades. Collect Remote License Info (for servers) collects license details from selected targets. If licenses are stored on the selected system (for details, see the specific product information), the selected machine must be running a variant of Microsoft Windows.
I. J. Target system is not running Microsoft Windows as required. Keys cannot be collected from a system of this type. NOTE: This displays if the system is of a different type such as; a switch, a printer, a cluster, a complex, or a system not running a Windows OS. K. Cannot collect keys stored on this node. Systems Insight Manager host and specified system must be running Microsoft Windows. NOTE: This happens when, for example CMS or a remote system is not running a Windows variant operating system. L.
replace a demo key with a permanent license. If a permanent key is already present, Integrity MP displays a message such as License already Installed. • An assigned license cannot be unassigned from one management processor and assigned to another management processor. Licenses delivered directly to the actual target system cannot be unassigned because the behavior of the product operating with that license is outside the scope of License Manager.
Assigning or Applying Licenses page 1 2 3 4 5 6 7 8 9 98 System Name The name of the system where the task was executed. Serial Number A number the licensing product chooses to identify remote systems. (Check product information for specific details). Unique Identifier A unique string that further identifies a system. Systems can be licensed by any combination of system name, serial number, or unique identifier. Status The status of the use of the license on the named system.
License unlicensed systems (optional) page 1 2 3 4 5 System license status Displays the status of system licenses, such as Not licensed, or assigned duration license. System selected to be licensed System Name 15.146.233.1 is selected to have a license assigned to it. Licenses currently available Displays all of the currently available licenses to be assigned. License selected A license is selected to be assigned to system 15.148.233.1. Apply license Applies the selected license to the selected system.
22 Storage integration using SMI-S About storage systems Storage systems are SAN-attached Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters). Systems Insight Manager uses WBEM SMI-S providers to discover and collect data from storage systems. To view the latest information about Systems Insight Manager device support and for information about obtaining and installing SMI-S providers, see http://www.hp.com/go/hpsim/ providers .
to the Command View server that generated the event. Systems Insight Manager associates a disk or RAID subsystem with the controller managing these drives for internal storage.
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.
The following components can be provided in several different ways: • Embedded agent The hardware device has an embedded SMI-S agent. No other installation of software is required to manage the device. • SMI solution The hardware or software ships with an agent installed on a host. The agent must connect to the device and obtain unique identifying information. This is the method used by all HP storage devices and most SAN devices.
For Command View SDM Procedure 22-1 Configuring SNMP trap destination on Windows NT 4.0 on the Command View server 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. 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.
Discovery The Systems Insight Manager discovery process for systems running Command View includes the following: • CV XP on port 80 (http) • CV VA/SDM on port 4096 (http) • CV TL on port 4095 (http) • Discovery of Command View EVA is encapsulated within the discovery of the HP StorageWorks Storage Management Appliance on ports 2301 or 2381 Systems Insight Manager must be permitted to access the web server. NOTE: To configure Command View and SDM: Procedure 22-5 Configuring Command VIEW and SDM 1.
Viewing individual storage systems Procedure 22-7 Viewing individual storage systems 1. 2. 3. In the System and Event Collections panel, expand Systems, Shared, Systems by Type, and Storage Systems. Expand the storage system collection that contains the system you want to view. Click the name of the storage system you want to view. The System Page for that system appears. Viewing storage system reports Systems Insight Manager provides predefined and customized storage system reports.
Viewing storage capacity for a single array Procedure 22-8 Viewing storage capacity for a single array 1. 2. In the System and Event Collections panel, expand Systems, Shared, Systems by Type, Storage Systems, and All Storage Arrays. Select a storage array. 3. Click the icon next to Capacity Information.
23 Managing MSCS clusters Cluster Monitor is a core component of Systems Insight Manager, and adds the ability to monitor and manage multi-node clusters. Cluster Monitor also manages multiple cluster platforms in a heterogeneous environment. Procedure 23-1 Managing clusters 1. Access the Cluster Monitor page by using one of the following methods: • Method 1: 1. Select Tools→System Information→Cluster Monitor. Note: If no MSCS clusters are discovered, Cluster Monitor is not listed in the menu. 2.
Name Description Quorum Resource that maintains essential cluster data and guarantees that all nodes have access to the most recent database changes Node fields Table 23-2 Node fields Name Description Name Name or alias for the node Condition Condition of the node: Normal (the node status is an active cluster member), Degraded (the node status is down, trying to form or rejoin a cluster, is operating as an active member of a cluster but cannot host any resources or resource groups, or is up but clu
NOTE: A group must have a network name and an IP address associated with it for you to access group resources. A group can be owned by any node in the cluster and can be moved by users with administrative rights for load balancing and other administrative purposes. When a failure takes place, the entire group fails over, which prompts the cluster software to transfer all group resources and data to a different node in the cluster.
List Normal Degraded Failed Other resource groups, or is up but cluster activity is paused. Network The network state is Online or Available. Resources The resource state is Online. The resource state is The resource state is Failed. The resource state is Unavailable, Offline, Online Unknown. Pending, or Offline Pending. NOTE: The network state is Partitioned. The network state is Offline.
24 Systems Insight Manager Audit log Systems Insight Manager logs all tasks performed by all Systems Insight Manager users on all systems. The information is stored in the Audit Log file on the CMS. Several features of the Systems Insight Manager Audit Log are configurable. For example, you can specify which tools log data and the maximum Audit Log file size. The Systems Insight Manager Audit Log is configured through the log.
Running Tool:ls Expanded Command Line:ls Targets: cup11.hp.com 104612: 2008-04-24 11:17:45 PDT,JOB,PROGRESS,START,JOB,44641_cup12.hp.com:cup11.hp.com, DETAIL,partner,,, Running Tool:ls 104613: 2008-04-24 11:17:45 PDT,JOB,SUCCESS,DONE,JOB,44641_cup12.hp.com:cup11.hp.com, DETAIL,partner,,, Running Tool:ls Exit Code:0 Log content The Systems Insight Manager Audit Log contains the following information in the order listed, and the log entry key @!@ precedes all other fields in an audit log entry.
25 HP Version Control and Systems Insight Manager About the Version Control Agent The VCA is an Insight Management Agent installed on a system that enables you to view HP software and firmware installed on the system. You can configure: VCA to point to a repository managed by VCRM, enabling easy version comparison and software updates from the repository to the system where VCA is installed. VCA provides version control and system update capabilities for a single HP system.
Alone, VCRM can catalog and manage a repository of ProLiant and Integrity Support Packss and software and firmware for HP ProLiant and Integrity systems. NOTE: Although you can install ProLiant and Integrity Support Packs or component to the local machine using VCRM, you cannot install the software on remote servers unless VCA is installed on the remote server and using VCA.
is by using the Automatic Update feature of VCRM. This feature enables you to schedule an automatic population of the repository. However, the repository can be updated in one or more of the following ways: • By using the Automatic Update feature of VCRM • By using the Upload ProLiant Support Pack feature of VCRM, which enables users to easily copy ProLiant Support Packs from a SmartStart CD or other accessible media • By manually downloading the software into the repository from http://www.hp.
26 Compiling and customizing MIBs Systems Insight Manager; provides the capability of managing systems through SNMP and by receiving incoming SNMP trap events. Systems Insight Manager ships with many MIBs pre-configured. For a complete list, see Out-of-the-box MIB support in Systems Insight Manager.You can use tools provided by Systems Insight Manager to integrate third-party (non-HP) SNMP v1/v2 MIBs into Systems Insight Manager and to provide support for processing and displaying traps from other systems.
Use of the -d switch is not necessary when you have copied all MIBs, including dependency MIBs, to the \mibs directory and execute mcompile from the \mibs directory. The -d switch specifies which directory contains the MIB files to be compiled into Systems Insight Manager. The directory path must be specified as relative to the full path or relative to the directory. As output, mcompile produces a CFG file and save it to the \mibs directory.
resolved from BLADETYPE2-SWITCH.MIB and ipCurCfgGwIndex is resolved from BLADETYPE2-NETWORK.MIB. To illustrate further how imports are resolved—the following procedure is how mcompile would attempt to resolve the import for hpSwitchBladeType2-Mgmt: Procedure 26-1 How MIB imports are resolved 1. 2. 3. 4. 5. Search for a file named HP-SWITCH-PL-MIB.mib (module name, uppercase). Search for a file named HP-SWITCH-PL.mib (module name without -MIB, uppercase). Search for hp-switch-pl.
Systems Insight Manager might not properly resolve varbind data for incoming traps from MIB X when a varbind has been imported from MIB Y that was not registered prior to registering MIB X. MIB dependencies are typically identified at the top of MIB files in the IMPORTS section ad are discussed in the mcompile section. Note that failing to compile imported MIBs properly does not block reception of traps; it only limits the data captured for some traps.
• General Backup • Giga Switch Events • HP Open View Internet Services Events • HP OVSAM Events • HP Service Events • HP StorageWorks HSV Controller Events • HP StorageWorks SAN Switch Events • HP-UX EMS Events • Integrity Server Events • IO Drive Events • NetServer Events • PATROL Events • PowerDevice • ProLiant Application Events • ProLiant BL p-Class GbE Interconnect Switch Events • ProLiant BL p-Class GbE2 Interconnect Switch Events • ProLiant Cluster Events • ProLiant
This keyword has a number of Systems Insight Manager specific commands. These commands are parsed and executed when a paging or e-mail Automatic Action on Event rule is created and exercised within Systems Insight Manager. You might view these commands as a paging or e-mail command language. The general layout of each command contains an operand and descriptive text associated with the operand. The descriptive text must be delimited by a # pair.
the status of an HP Drive Array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If the physical drive status is failed(3) or predictiveFailure(4), replace the drive.
• The Category field is used to logically group similar events for display purposes in Systems Insight Manager. These groups are shown when you create event lists and when configuring Automatic Event Handling. This is extremely helpful when wanting to group specific networking, storage, and other traps to be easily found in the user interface. This field corresponds to the #CATEGORY keyword in the CFG files. • The Enable/Disable field can be toggled to support or suppress events on a per-trap basis.
A Troubleshooting Authentication On a Linux or ESX system, you might receive the following error when running the mxagentconfig command or through Configure or Repair Agents: Configuration failed to complete due to the following exception: Could not access the file or directory sshd_config.orig on the target system esxhost1. Remote system reported following error message: Permission denied. Check whether the directory or file exists or whether the user has the operating system permission to access it.
Solution: Note the name being used in the browser window, verify that the name resolves on the network, and that it is not being affected by any proxy settings in the browser. ------------------------------------------------------------When you try to browse to the SMH on the same Linux system that Systems Insight Manager is installed, you might receive multiple browser warning messages. Solution: Complete the following: 1. Open a terminal window. 2.
Solution: HP recommends turning off the Windows Vista User Account Control. How do I push an SSH key through Configure or Repair Agents on Windows 2008? Solution: HP recommends disabling User Account Control on Windows 2008 systems. NOTE: Configure or Repair Agents is not supported on Windows Vista. ------------------------------------------------------------I received a connection failed error in Configure or Repair Agents on Windows XP. Solution: You might have Windows XP SP2 or later installed.
release, the upgrade process will incorporate the automatic launching of the Identification task against discovered systems. ------------------------------------------------------------The Data Collection task for an Onboard Administrator times out on non-Windows CMS. Solution: This affects the individual task only and does not affect other tasks in the batch.
On Windows: C:\program files\hp\systems insight manager\config\identification The folders listed above are the default folders and should be used unless you have changed the installation folder location. • You might have failed to set up and specify appropriate WMI Mapper proxy servers. • You might have failed to specify appropriate WBEM credentials.
Solution: This is due to a default timeout value of three hours for this operation. There are two ways to resolve the issue: • Configure the array to have a maximum of 2500 collectible objects (volumes, disks, ports, and so on). • Increase the timeout value, depending on the configuration, to an optimal value by modifying the configurable parameter Storage_DC_Timeout which is set to a default value of 10800 (equals 3 hours), with the mxglobalsettings command.
HP Insight Control power management After discovering new servers and their iLO 2 management processors using Reports→Insight Power Manager, the task wizard indicates the server is not compatible with Insight Power Manager. Solution: Insight Power Manager requires an association to exist between the iLO management processor and the server before compatibility can be determined. If you attempt to use the Insight Power Manager tool before this has been determined, you encounter this issue.
Solution: Uncheck Simple File Sharing by navigating to Tools→Folder Options→View or set the security policy Network access: Sharing and security model for local accounts to Classic: Local users authenticate as themselves. Installation The Systems Insight Manager installation might hang at the database initialization step for a long period of time on Windows Server 2008. Solution: The installation might have been completed in the background. Verify by browsing to the Systems Insight Manager UI.
Solution: To bypass this problem, modify the Ignite tools from the CLI using the tools' original tdefs, as follows: Procedure A-9 Issue with changing and saving the address of an Ignite server 1. 2. From the CLI, go to the Tools directory under the Systems Insight Manager install directory on Windows and under /var/opt/mx/tools on Linux and HP-UX. Run mxtool -mf -x force' where for each TDef is as follows: iux_tools.xml swm-msa-tools.xml swm-ssa-tools-up.xml swm-ssa-tools.
Tasks The Initial ProLiant Support Pack Install task does not work on Windows 2000 target systems. Likewise, the install portion of the Configure or Repair Agents tool does not work on Windows 2000 systems. Solution: If the HP Version Control Agent is present on these target systems, then the Install Software and Firmware tool can be used to distribute agents, Support Packs and other components to Windows 2000 systems. Tools The message /tmp/Acmd42947.
B Protocols used by Systems Insight Manager Systems Insight Manager uses many different management protocol standards. This capability enables Systems Insight Manager to provide management support for a wide array of manageable systems. SNMP The Internet Engineering Task Force (IETF), the standards-rating body for the worldwide Internet, has defined a management protocol, SNMP, which has accumulated a major share of the market and has the support of over 20,000 different products.
IP address filtering. Be sure the Systems Insight Manager IP address is in the allow list for any given SNMP agents. The operating system of the managed system can provide additional security capabilities for SNMP such as IP address restrictions for valid requests. HTTP Systems Insight Manager also takes advantage of the industry standard HTTP protocol (used to transfer information over the World Wide Web) for transportation of management information.
Simple Object Access Protocol (SOAP) SOAP is used by partner applications to communicate with Systems Insight Manager. It is primarily XML over HTTPS. Protocol functionality The following table displays descriptions of management protocols displayed under Management Protocols on the System Page which displays protocols that have responded when attempting to identify the system. NOTE: The CMS initiates the requests for all protocols except events.
Management standard Description Functionality when enabled CIM, CIM-XML, and WS-Management. The CIM-XML protocol is most widely used with WBEM today, and the term WBEM is often used to mean this protocol. Note: Configure firewalls to allow the CMS to communicate with managed systems through default port 5989. If you have modified the default port setting for your WBEM provider, you must configure your firewall for the port number your WBEM provider on which it is actually configured.
C Data Collection After Systems Insight Manager collects data initially during the identification process, you can schedule a Data Collection task to specify systems and run the task with different schedules. In addition to the default Initial and Bi-Weekly Data Collection tasks built in to Systems Insight Manager, you can set new data collection tasks targeting specific managed systems. To create a Data Collection task from the toolbar, select Options→Data Collection.
D Default system tasks Polling tasks track the health status of systems in associated collections. Hardware status polling must occur periodically to determine when systems go offline or when hardware degrades. You can customize polling tasks for specific systems to run at scheduled times. You can also create polling tasks with different collections to meet your needs. You can configure polling tasks to take place based on the receipt of an event. Event polling tasks are associated with event collections.
Delete Old Noisy Events Includes events that are transient and happen frequently, but do not generally indicate hardware failures. For example, link up, link down, and authentication events. These events fill the event database tables, but do not add value to the hardware event history. Delete Events Older Than 90 Days This task deletes events older than 90 days and can help maintain Systems Insight Manager by limiting the total number of events. By default, this task is disabled.
Status polling Polling tasks track system health status for systems in the system list. They provide a simple means of assessing system health in the event that an SNMP trap or other event was not properly delivered to the management console. Hardware status polling must occur continuously to determine when systems go offline or performance degrades. You can customize polling tasks for specific systems to run at scheduled times.
E Host file extensions Hosts files are used during discovery to manually add multiple systems to the Systems Insight Manager database. Hosts files typically contain IP addresses, system names, system name aliases, and user comments. The hosts file that you create can contain additional information about systems. The information appears as one or more comments that precede the hosts file entry for the system. Unless other values are specified, the default values are used.
16.26.176.92 EngProliant.compaq.com EngProliant #user comments The system testServer in the following example defaults for TYPE. The defaults for SNMP Timeouts and Retries were restored for this system but only apply to testServer. The SNMP write community string default was changed and only applies to testServer. #$IMXE: TYPE=Server #$IMXE: SNMP_TIM=0 SNMP_RET=0 SNMP_MON=public SNMP_CON=private 16.26.160.20 testServer.compaq.
Table E-4 Hosts file default parameters Keyword Value Description TYPE • Application Unknown (Default) • Cluster • Complex • Desktop • Enclosure • Environmental Monitor • Handheld • Hub • KVM Switch • Management Processor • Notebook • Partition • Power Distribution Unit • Power Supply • Printer • Rack • Resource Partition • Remote Access Device • Router • Server • Shared Resource Domain • Storage Device • Switch • Tape Library • Thin Client • UPS • U
F System Type Manager rules System Type Manager enables you to extend Systems Insight Manager's SNMP-based discovery so that it is able to identify new types of systems. You do this by creating a System Type Manager rule that maps a System Object ID (OID), and optionally an additional MIB variable, to the desired type. Manufacturers assign unique System OIDs to their SNMP-instrumented products. Systems supply information about themselves using variables described in files called MIBs.
G Custom tool definition files Custom tool definition files are XML files that describe how Systems Insight Manager should run tasks based on a program, script, or UTL added by the user. This appendix describes the wuyntax of these tool definition files (tdef). For more information, see "???". Tool type-specific requirements SSA-specific attributes An SSA tool executes on a selected target and is only aware of the target system environment.
WLA-specific attributes A WLA tool typically launches in a separate browser (by default) or in the same frame as Systems Insight Manager and is specified by a universal resource locator (URL). Web-launch applications that do not share Systems Insight Manager certificates should be executed in a separate frame. Web-launch aware tools must specify a main URL.
Parameter Function -r Specify a file/tool to be removed -t Specify a tool name -x force Force a tool to be removed or modified even if the version is the same or tasks are tied to the tool NOTE: For more information about mxtool parameters, refer to the mxtool man page in the Systems Insight Manager information library at the following URL: http://h18013.www1.hp.com/products/servers/ management/hpsim/info-library5/mxtool.1m.html or in the HP SIM 6.
Parameter Description the contact use %r%{MgmtProcToServer.Contact%}. If the related systems attribute is omitted, then for each system, the network name and IP address are returned in the form "network name|ip address." If more than one system is returned, then they are comma-delimited. Note that the relationship type "MgmtProcToServer" can be used to return related system information for all management processor relationship types. %{attribute]%} The value of the named attribute of the target system.
Names values Description Values: true | false (default: false) Table G-9 Defined name values Names values Description product-name 32 character string Product-version 24 character number Insert-separator Insert a separator line in the menu structure before (“true”) or after (“after”) this tool. Values: true | after | false (default: false) I18n-attrs String. Name of a resource bundle for storing localized tool parameters. See the section on tool internationalization. Tool-id String.
Table G-12 Tool filtering attributes Filter name OSName Description Acceptable values include: HPUX (no space or hyphen in the value) Linux WINNT (all windows flavors) OSVendor Acceptable values include: Microsoft SuSE RedHat HP OSRevision Acceptable values are as follows (see text below for version number details) (for Windows) 4.0, 4.1, 5.0, 5.1 (for Linux) 7.3, 8.0, 2.1 (for HP-UX) 11.11, 11.23 DeviceType Long list: Bring up the Options menu, then select Discovery and then Identification.
Names values Description NoticeRawData The raw data of the event that was sent and in a string format. It is in a pipe (|) delimited format that can be used for simple parsing NoticeSeverityStr Can be Critical, Major, Minor, Unknown, Normal, Warning, or Informational NoticeSeverity An integer format of the severity 1 – Normal 2 – Warning 3 – Minor 4 – Major 5 – Critical 100 - Informational NoticeQueryName Displays the event list that generated the event.
Parameter field Data entry required? Parameter string assignment Entry guidelines Tool command Yes %2 This is the new command used to call the tool, and it may include parameters. Prompt No %3 If the Tool command includes the %1 parameter, then this field entry is required to specify the destination prompt. Tool menu category No %4 Use this entry to specify the location of the tool in the menu. If left blank, the new tool will be added to the Tools→Command Line Tools menu.
H Out-of-the-box MIB support in Systems Insight Manager The following table represents the key MIBs that ship with Systems Insight Manager. Those MIBs that are marked as preloaded are registered as part of every Systems Insight Manager installation. The remaining MIBs are in the MIB directory for you to compile, if necessary, for managing those types of systems in your environment. Table H-1 MIBs supported in Systems Insight Manager MIB name Supports Pre-loaded asmib.mib ARC Serve X atmf.
MIB name Supports Pre-loaded cisco-rttmon.mib cisco products X cisco-stack-mib.mib cisco products X cisco-stackmaker.mib cisco products X cisco-stp-extensions.mib cisco products X cisco-syslog.mib cisco products X cisco-tc.mib cisco products X cisco-tcp.mib cisco products X cisco-udldp.mib cisco products X cisco-vlan-iftable-relationship.mib cisco products X cisco-vlan-membership.mib cisco products X cisco-vtp.mib cisco products X compaq-agent.
MIB name Supports Pre-loaded cpqstdeq.mib HP Proliant System and Environmental X cpqstsys.mib HP Proliant Storage X cpqswcc.mib HP StorageWorks Command Console X cpqthrsh.mib HP Proliant threshold X cpqups.mib HP Proliant UPS X cpqwcrm.mib System and Environmental X cpqwinos.mib HP Proliant Operating System X dataprotector.mib Data protector X dlghwinf.mib Dialogic Hardware X ems.mib HP-UX EMS X emsmibax.mib Tandem EMS X fa-mib40.
MIB name Supports Pre-loaded nsavolcp.mib HP Netserver X old-cisco-chassis.mib cisco products X old-cisco-flash.mib cisco products X old-cisco-interfaces.mib cisco products X old-cisco-ip.mib cisco products X old-cisco-sys.mib cisco products X old-cisco-tcp.mib cisco products X old-cisco-ts.mib cisco products X ovis-v2.mib HP Open View Internet Services X pcisnet.mib ServerNet X pfc.mib PATROL X rfc1213.mib RFC MIB X rfc1215.mib RFC MIB X rfc1514.
I Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact HP U
Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.com Include the document title and manufacturing part number in your message. All submissions become the property of HP.
CAUTION IMPORTANT NOTE TIP An alert that calls attention to important information that, if not understood or followed, results in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that contains additional or supplementary information. An alert that provides helpful information.
Glossary A administrative rights user A user who is authorized for the All Tools toolbox on all systems, including the CMS. This type of user has been given special privileges to administer the Systems Insight Manager software. administrator A user who manages users, resource pools, and self-service requests through HP Insight Orchestration console. agent A program that regularly gathers information or performs some other service without the user's immediate presence.
cluster A parallel or distributed computing system made up of many discrete systems that form a single, unified computing resource. Clusters vary in their features, complexity, and the purposes for which they are best suited. cluster monitor resource A program that provides a monitoring or management function for clustered nodes in a cluster. CMS (CMS) A system in the management domain that executes the Systems Insight Manager software.
E enclosure A physical container for a set of server blades. It consists of a backplane that routes power and communication signals and additional hardware for cabling and thermal issues. It also hosts the CPU or server power supplies. event Information sent to certain users that something in the managed environment has changed. Events are generated from SNMP traps. Systems Insight Manager receives a trap when an important event occurs. Events are defined as: • Warning. • Informational. information.
HP Systems Insight Manager database (database) The database that stores vital information about Systems Insight Manager, including users, systems, and toolboxes. HP Version Control Agent (VCA) An agent that is installed on a server to enable you to see the HP software installed on that server. The VCA can be configured to point to HP Version Control Repository Manager, enabling easy version comparison and software update from the repository.
Management Information Base (MIB) The data specification for passing information using the SNMP protocol. An MIB is also a database of managed objects accessed by network management protocols. management instrumentation Agents running on systems that provide management information for HTTP, or SNMP protocols. management protocol A set of protocols, such as WBEM, HTTP, or SNMP, used to establish communication with discovered systems.
public key the public half of a public and private key pair. The public key can be freely distributed without fear that it can be used to impersonate the user. It can only be used for authentication in conjunction with a private key. R HP Insight Control server deployment The HP Insight Control server deployment is a multiserver deployment tool that enables IT administrators to easily deploy large numbers of servers in an unattended, automated fashion.
Secure Sockets Layer (SSL) A standard protocol layer that lies between HTTP and TCP and provides privacy and message integrity between a client and server. A common usage of SSL is to provide authentication of the server, so clients can be assured they are communicating with the server it claims to be. It is application protocol independent. Secure Task Execution (STE) A feature of Systems Insight Manager that securely executes a task from a managed system.
software update A task to remotely update software and firmware. spoofing The act of a website posing as another site to gather confidential or sensitive information, alter data transactions, or present false or misleading data. SSH client Connects to SSH servers to perform remote task execution and file copy. SSH server Listens for and services requests coming in on the proper TCP/IP port, usually port 22.
system search Logical grouping of systems into a collection based on information in the Systems Insight Manager database. After a search is defined, you can display the results from the system view page or associate it with a management task. system status panel The section of the GUI on the left of the screen that displays status information and system or event alarms. system type One of 12 supplied types. You can add your own based on one of these types.
user accounts Accounts used to sign-in to Systems Insight Manager. These accounts associate a local Windows user account or a domain account with privilege levels and paging attributes inside Systems Insight Manager. user group A group of users defined on the CMS operating system that has been added to Systems Insight Manager. Members of the user group in the operating system can sign-in to Systems Insight Manager. user rights user A user who cannot configure the CMS.
Index A about, 114, 115 default polling tasks, 140 searches, 40 storage solutions (SNMP), 100, 103 version control agent, 114 accessing automatic event handling, 48 discovery filters, 33 accessing the GUI, 15 adding SNMP rules, 146 agents, 21 All c-Class Racks collection discontinued, 131 All p-Class Racks collection discontinued, 131 all scheduled tasks task results list, 58 applying time filters, 48, 51 array controllers duplicate entries, 127 attributes cluster monitor, 110 audit log, 112 authentication
communication errors>, 125 community strings, 43 complex deleting, 126 discovering, 126 System Page, 126 Configure or Repair Agents, 14 Windows Vista, 126 Configure or Repair Agents task, 126 configuring, 126 fails, 126 configuring audit log, 112 Configure or Repair Agents task, 126 storage system discovery, 105 tool definition files, 112 contract and warranty default tasks, 140 status, 88, 89 system properties, 46 CPU resource, 110 CPU utilization, 110 creating automatic event handling tasks, 48, 51 custom
enabling, 31 general settings, 31 running, 31 stopping, 31 disk capacity, 110 disk resource, 110 DL100 series systems identifying, 131 DL160 G5, 131 DL180 G5, 131 DMI , 135 DTMF , 135 E e-mail paging examples, 49 e-mail settings, 48 editing custom tools, 68 discovery filters, 33 discovery task, 31 tasks, 58 Emulex 1050C HBA card identified as two single port HBAs, 131 Emulex Host Bus Adapter identifying, 131 enabling discovery task, 31 enclosure missing servers, 127 enclosure view, 126 environment variable
HP ProLiant WBEM Providers, 133 HP Serviceguard package, 129 HP Storage Essentials affect on reports, 106 discovery, 31 system properties, 46 HP Systems Insight Manager collections, 61 HP Version Control, 114, 115, 116 HP-UX, 139 empty, 127 managed systems, 21 HTTP , 135 I identification, 131 cluster, 142 management processor, 142 SNMP, 146 storage solutions (SNMP), 103 identifying BC1000 blades, 131 complex, 131 DL100 series systems, 131 Emulex 1050C HBA card, 131 Emulex Host Bus Adapter, 131 management p
MSCS clusters, 108 MSCS cluster services discovery, 129 MSCS resource, 110 MSDE installing, 132 multiple-system-aware custom tools, 147 mxagentconfig, 125, 126, 134 mxauthenticationexception, 134 mxinventory processes, 127 mxnodesecurity, 28, 134 mxstm, 146 N name mismatches, 129 naming restrictions, 129 National Language Support, 132 navigating Home page, 18 nPars, 126 O Onboard Administrator, 129 data collection, 127 OpenSSH, 21, 133 typical install, 132 operating system inconsistent version, 131 Oracle
security alerts, 15 server protocols, 137 server connections increase size, 125 setting up managed systems, 21 managed systems - HP-UX, 21 managed systems - Linux, 21 managed systems - Windows, 21 settings browser, 15 signing in GUI, 15 Simple File Sharing, 131, 132 Single Sign-On, 129 single system protocol settings, 135 setting, 139 single-system-aware custom tools, 147 SMH, 127 SMI-S, 129 SMI-S providers storage systems, 105 SNMP, 21, 135, 139, 142 adding rules, 146 port 162, 135 SnmpTrapPortAddress, 135
invalid characters, 134 paging, 48 polling, 140 scheduling, 58 stopping, 58 track status, 58 user privileges, 58 TDEF (see tool definition files) custom tools, 147 thresholds cluster monitor, 110 time filters applying, 48, 51 tool definition files, 112 tools, 14, 134 authorization, 134 customized, 13 Kernal Configuration (kcweb), 134 launching, 134 Peripheral Device (pdweb), 134 ping, 59 trust relationships, 134 U unsupported characters database user names and passwords, 132 operating system, 132 upgrading
