Insight Integration for HP Network Node Manager Revision 3.4 User Guide
Table Of Contents
- Insight Integration for HP Network Node Manager Revision 3.4 User Guide
- Notice
- Contents
- Introduction
- Installation
- Installation overview
- Preinstallation considerations
- Upgrading from previous versions of the Insight Integration
- Installation procedures for HP-UX and Solaris platforms
- Installation procedures for Windows platforms
- Uninstalling the Insight Integration on HP-UX and Solaris platforms
- Uninstalling the Insight Integration on Windows platforms
- Configuration files
- Tool Definition configuration
- Additional configuration requirements
- Event-only integration
- Installing the Insight Integration on an NNM Remote Console
- Installing the Web Jetadmin integration
- Creating NNM events using HP SIM 5.0
- Creating NNM events using HP SIM 5.1
- Configuring SNMP on an HP ProLiant server running NNM
- Using the software
- Using the Insight Integration
- Discovering HP servers with the Insight Integration
- Insight Integration menus
- Insight Integration menu options
- Viewing HP systems information
- HP event management in HP Network Node Manager
- HP Insight Information menu options
- HP Insight Summary Launch for desktops
- HP Insight Information for servers
- Summary
- Integrated Management Log
- Software Version
- System—Processor
- System—Memory
- System—PCI slots
- Health—Fault-tolerant fans
- Health—Temperatures
- Health—Thresholds
- Drives—SCSI
- Drives—IDA
- Drives—Fibre
- Insight Lights-Out information
- Insight Lights-Out log
- HP Insight graphics
- HP Insight rack information
- Using HP Systems Insight Manager with HP Network Node Manager
- Configuring the HP Systems Insight Manager launch on Windows
- Configuring the Systems Insight Manager launch on UNIX
- Launching HP Systems Insight Manager
- Running an in-context launch to HP Systems Insight Manager
- Using the Insight Integration with the Dynamic Views interface
- Using the Insight Integration with the NNM web interface
- Using the Insight Integration with HP Web Jetadmin
- Viewing events in HP Systems Insight Manager
- Using the Insight Integration with the NNM Remote Console
- Troubleshooting
- Technical support
- Acronyms and abbreviations
- Index
Troubleshooting 94
Troubleshooting
Frequently asked questions
Why are there undefined alarms in the event log?
If alarms similar to the following continue to appear in the Alarm Browser, the trap definitions for the
integration module might not be installed correctly. Verify that the trap definition files are properly
installed.
Reload the trap definitions by executing xnmevents -load newtraps.cpq, and then stop and
restart the HP NNM services using the OVSTOP and OVSTART commands.
In the following messages, nnmsystem.mse.com is the name of the server running NNM.
- Normal Fri Sep 13 10:30:16 nnmsystem.mse.com Received event
.1.3.6.1.4.1.232.1.3.2.0.3001 (enterprise:.1.3.6.1.4.1.232.1.3.2
generic:6 specific:3001), no format in trapd.conf. 1 args: [1]
private.enterprises.compaq.cpqStdEquipment.3.2 (Integer): 7215
- Normal Fri Sep 13 10:30:16 nnmsystem.mse.com Received event
.1.3.6.1.4.1.232.1.3.11.0.3003 (enterprise:.1.3.6.1.4.1.232.1.3.11
generic:6 specific:3003), no format in trapd.conf. 1 args: [1]
private.enterprises.compaq.cpqStdEquipment.3.11 (Integer): 7215
- Normal Fri Sep 13 10:30:16 nnmsystem.mse.com Received event
.1.3.6.1.4.1.232.1.3.3.0.3002 (enterprise:.1.3.6.1.4.1.232.1.3.3
generic:6 specific:3002), no format in trapd.conf. 1 args: [1]
private.enterprises.compaq.cpqStdEquipment.3.3 (Integer): 7215
- Normal Fri Sep 13 10:30:17 nnmsystem.mse.com Received event
.1.3.6.1.4.1.232.1.3.2.0.3001 (enterprise:.1.3.6.1.4.1.232.1.3.2
generic:6 specific:3001), no format in trapd.conf. 1 args: [1]
private.enterprises.compaq.cpqStdEquipment.3.2 (Integer): 7217
Why are known HP nodes not classified as HP servers on the NNM map?
Complete the following steps to verify communication with the system:
1. Right-click the node, and then select Object Properties.
2. Open a command prompt and ping the selection name displayed in the Object Properties dialog
box.
3. If you cannot ping the selection name, add it to the hosts file on the system. The device should be
classified correctly.
4. If this action has no effect, verify that the console can communicate with the HP Insight Management
Agents.
5. Run cpqchksnmp in the %OV_MAIN_PATH%/install/tools/cpq directory to verify that a system is
running SNMP. For example:
cpqchksnmp 172.25.162.30 public
6. Run cpqchkagnt in the %OV_MAIN_PATH%/install/tools/cpq directory to verify that a system is
running the HP agents. For example:
cpqchkagnt -n 172.25.162.30