Owner manual
Table Of Contents
- Systems Insight Manager 7.0 User Guide
- Table of Contents
- Part I Introduction
- Part II Setting up HP SIM
- 3 Setting up managed systems
- 4 Credentials
- 5 WMI Mapper Proxy
- 6 Discovery
- 7 Manage Communications
- 8 Automatic event handling
- 9 Users and Authorizations
- 10 Managed environment
- Part III HP SIM basic features
- 11 Basic and advanced searches
- 12 Monitoring systems
- 13 Event management
- 14 Reporting in HP SIM
- 15 HP SIM tools
- Part IV HP SIM advanced features
- 16 Collections in HP SIM
- 17 HP SIM custom tools
- 18 Federated Search
- 19 CMS reconfigure tools
- 20 Understanding HP SIM security
- 21 Privilege elevation
- 22 Contract and warranty
- 23 License Manager
- 24 Storage integration using SMI-S
- 25 Managing MSCS clusters
- 26 HP SIM Audit log
- 27 HP Version Control and HP SIM
- 28 Compiling and customizing MIBs
- A Important Notes
- System and object names must be unique
- Setting the Primary DNS Suffix for the CMS
- Distributed Systems Administration Utilities menu options not available
- Virtual machine guest memory reservation size
- Insight Remote Support Advanced compatibility
- Database firewall settings
- Annotating the portal UI
- Security bulletins
- Validating RPM signatures
- Central Management Server
- Complex systems displaying inconsistency with the number of nPars within the complex
- Configure or Repair Agents
- Data collection reports
- B Troubleshooting
- Authentication
- Browser
- Central Management Server
- Complex
- Configure or Repair Agents
- Container View
- Credentials
- Data Collection
- Database
- Discovery
- iLO
- Linux servers
- Event
- Host name
- HP Insight Control power management
- Insight Control virtual machine management
- HP Smart Update Manager
- Systems Insight Manager
- Identification
- Installation
- License Manager
- Locale
- Managed Environment
- HP MIBs
- Onboard Administrator
- OpenSSH
- Performance
- Ports used by HP SIM.
- Privilege elevation
- Property pages
- Reporting
- Security
- Sign-in
- SNMP settings
- SSH communication
- System Page
- System status
- Target selection wizard
- Tasks
- Tools
- Upgrade
- UUID
- Virtual identifiers
- Virtual machines
- VMware
- WBEM
- WBEM indications
- WMI Mapper
- C Protocols used by HP SIM
- D Data Collection
- E Default system tasks
- Biweekly Data Collection
- System Identification
- Old Noisy Events
- Events Older Than 90 Days
- Status Polling for Non Servers
- Status Polling for Servers
- Status Polling for Systems No Longer Disabled
- Hardware Status Polling for Superdome 2 Onboard Administrator
- Data Collection
- Hardware Status Polling
- Version Status Polling
- Version Status Polling for Systems no Longer Disabled
- Check Event Configuration
- Status polling
- F Host file extensions
- G System Type Manager rules
- H Custom tool definition files
- I Out-of-the-box MIB support in HP SIM
- J Support and other resources
- Glossary
- Index
If you delete a credential (system credential, global credential, or one configured with a discovery
task) while discovery or identification is running, and that credential is found to work with a system,
the attempt to write the working credential to the database fails because the original credential
has been removed. If you try to view System Credentials for such a system, the system will not be
listed in the Credentials that are in use table, or the table includes No data available.
Normally, a system is listed in this table; even one with no working credentials is listed with an
Access Type of None.
To resolve this issue, restart HP SIM to remove any extraneous database records, and re-run the
discovery or identification task.
Data Collection
Capacity information is not available from providers for passively managed storage arrays.
-------------------------------------------------------------
If you have more than 2000 objects in an array, you must increase the default data collection time
to 32400, by modifying the Storage_DC_Timeout field in the globalsettings.props file.
When the number of objects to be collected on any given storage array exceeds 1000, it is possible
that data collection will fail for the array with a default timeout value of 10800 seconds.
-------------------------------------------------------------
After a HP SIM upgrade, the Data Collection task might fail when executed.
Solution: Following upgrade procedures, you must run either the Identification Task or System
Discovery Task against the systems for them to be reconciled following the completed upgrade
procedure. The Daily Identification task is available by default and can be ran be any time by
selecting Run Now. In a future 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.
-------------------------------------------------------------
HP SIM might report duplicate entries for array controllers if the data is collected using both WBEM
and SNMP protocols on a HP Insight Management WBEM Providers for Windows Server
2003/2008 target.
Solution: To see the correct data in report, you can perform data collection by disabling one of
the protocols. You can also access HP SMH to see the correct number of array controllers.
-------------------------------------------------------------
You see a problem with more than two mxinventory processes starting on the CMS.
Solution: Complete the following:
Procedure B-7 Issue with two mxinventory processes starting
1. Verify that your HP-UX CMS has the latest HP-UX kernel patches required for Java 1.5 execution.
If the CMS is HP-UX 11.23 IA/PA, then verify that the PHKL_35029 Kernel patch (or its
superseding patch) is installed. See http://www.hp.com/go/java.
2. Verify that all your HP-UX managed systems have HP WBEM Services for HP-UX A.02.00.11
or newer and for managed systems running HP-UX 11.23 IA/PA, verify the PHSS_33349
Kernel path (or its superseding patch) is installed.
-------------------------------------------------------------
If you cancel a running task, by clicking Stop or Delete, and immediately try to start another task
of the same type, the second task does not run until the previously canceled task fully completes
the cancellation. Systems in the cancelled task that are currently being processed are allowed to
run to completion. For some long-running tasks like data collection or software deployment, it can
take some time to allow the systems in progress to reach completion and finally cancel the task.
Data Collection 181