| General |
| Q1. |
What is the Insight Integration for HP OpenView Network Node Manager? |
| A1. |
Additional data for individual and groups of HP servers is available through integrated links to the HP Systems Management Homepage, the Remote Insight Lights-Out Edition (RILOE) II and Integrated Lights-Out (iLO and iLO 2) solutions, HP Insight Manager 7 or HP Systems Insight Manager, and the HP Storage Management Appliance.
|
| |
| Q2. |
What is new in version 3.4b? |
| A2. |
The list of new features and enhancements in version 3.4b of the Insight Integration for HP OpenView NNM includes:
- Support for SNMP events defined by HP Insight Management Agents up to version 8.10
- Support for NNM 7.53
- Support for HP Integrity Agent release 6.0
- Support for c-Class blade systems
- Default support for HP Systems Insight Manager with NNM running on Windows, HP UX, and Solaris
|
| |
| Q3. |
What are the major benefits of using this solution? |
| A3. |
The benefits of implementing the Insight Integration for HP OpenView NNM can be summarized as follows:
- Maximizes investments in HP hardware and HP OpenView NNM
- Enables simplified systems hardware and network management from a single console
- Extends OpenView NNM with in-depth hardware and lifecycle management tools for HP platforms
- Streamlines IT administration and increases systems availability
|
| |
| Q4. |
What operating systems and NNM management console platforms are supported? |
| A4. |
The Insight Integration for HP OpenView NNM, rev 3.4b, provides updated NNM and operating system support as defined in the table below.
|
|
|
|
|
| 6.3x |
Yes |
Yes |
No |
| 6.4x |
Yes |
Yes |
No |
| 7.0x |
Yes |
Yes |
No |
| 7.5x |
Yes |
Yes |
Yes |
|
|
|
|
|
| 6.3.1 |
No |
Yes |
No |
| 6.4x |
Yes |
Yes |
No |
| 7.0x |
Yes |
Yes |
No |
| 7.5x |
Yes |
Yes |
Yes |
|
|
|
|
|
| 6.4x |
Yes |
Yes |
No |
| 7.0x |
Yes |
Yes |
No |
| 7.5x |
Yes |
Yes |
Yes |
|
| |
| Q5. |
What Insight Management Agent versions are required? |
| A5. |
To take full advantage of the benefits provided with this solution, Insight Management Agents for Servers 5.00 and Management Agents for Clients v4.60 are required as a minimum.
To obtain the very latest support for HP hardware and SNMP system events, the most current Insight Management Agents are recommended.
Revision 3.4b of the Insight Integration for OpenView NNM supports definitions provided with Insight Management Agents up to v 8.10.
|
| |
| Q6. |
Can I use any popular browser applications to access the web-enabled features of the HP Insight Management Agents? |
| A6. |
The following browser solutions are recommended:
- HP Insight Management Agents for Servers
- Microsoft Internet Explorer 6.0 or later
- Mozilla 1.5 or later
- HP Management Agents for Clients
- Internet Explorer 6.0 or later
|
| |
| Q7. |
What service and support options are available for this product? |
| A7. |
The Insight Integration for HP OpenView NNM is supported via e-mail through the normal HP Customer Support and Services channels. View the support page for HP Insight Integration solutions. HP Services can provide assistance in deploying this product, if desired.
|
| |
| Q8. |
How is this product made available? |
| A8. |
The Insight Integration for HP OpenView NNM can be downloaded from HP.com at no charge, following a simple registration. View further details and download the Insight integration.
|
| |
| Troubleshooting |
| Q1. |
What should I do before calling HP customer support? |
| A1. |
If you are having problems installing or configuring the Insight Integration, HP Customer Support can offer further assistance.
Before using the e-mail request form (View the support page for HP Insight Integration solutions), verify that you have completed the following steps:
- Review the installation steps listed in Chapter 2 of the Insight integration user guide
- Refer to the "Troubleshooting" items listed below and review the appendix section of the Insight integration users guide
- Provide copies of the following files:
- Installation log file CIMINSTALL.LOG
- Error log file TMP/CIMOVERR.LOG
- Screen output from any of the diagnostic tools mentioned in the "Validating the Configuration" section of the Insight integration user guide appendix
|
| |
| Q2. |
Why are there undefined alarms in the NNM event log? |
| A2. |
If alarms similar to those listed below continue to appear in the NNM Alarm Browser, the trap definitions for the Insight integration module might not be installed correctly. Verify that the trap definition files are properly installed.
Reload the trap definitions by executing the command xnmevents -load newtraps.cpq, then stop and restart the OpenView services (OVSTOP and OVSTART).
In the messages below, "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
|
| |
| Q3. |
Why are known HP nodes not classified as HP servers on the NNM map? |
| A3. |
There are several possible causes for this situation. Verify communication with the system using the following steps:
- Right-click the node, and select Object Properties.
- Open a command prompt, and ping the selection name displayed in the Object Properties dialog.
- If you cannot ping the selection name, add it to the hosts file on the system. The device should be classified correctly.
- If this action has no effect, verify the console can communicate with the HP Insight Management Agents.
- Run cpqchksnmp in the %OV_MAIN_PATH%/install/tools/cpq directory to verify a system is running SNMP. For example: cpqchksnmp 172.25.162.30 public
- Run cpqchkagnt in the %OV_MAIN_PATH%/install/tools/cpq directory to verify a system is running the HP agents. For example: cpqchkagnt -n 172.25.162.30
- Verify OpenView NNM can get the operating system information from the desired system:
- Run the OpenView MIB browser (%OV_BIN%/xnmbrowser).
- Enter the hostname or IP address of the system.
- Enter the community name to use for communication.
- Enter .1.3.6.1.4.1.232.11.2.2 for the MIB Object ID.
- Click Start Query.
The results should display the operating system name and version, similar to the following (depending on the operating system) in the MIB Values field:
- 0:Microsoft Windows NT Server
- 0:4.00
- 0:Service Pack 6 1381 Uniprocessor Free
- 0:3
- 0:3
If you cannot obtain any results, the system cannot communicate with the HP Insight Management Agents.
|
| |
| Q4. |
Why do the Insight Information options return errors when querying a node? |
| A4. |
SNMP must be installed and configured for the Insight Information menu items to work properly. In addition, the correct community string must be configured within NNM.
If you receive the error, "Could not perform SNMP get from HOSTNAME: No response arrived before timeout," verify that the correct SNMP community string is being used.
If you receive the message, "Note: requested information is not available from HOSTNAME," be aware that, in most cases, this message is not an error. The most likely cause of this message is requesting information that is not implemented on the target node. For example, selecting Insight Information, Drives, SCSI on a system that only has a drive array (no SCSI devices) results in this message.
|
| |
| Q5. |
Why are RILOE, RILOE II, iLO, or iLO 2 management processors not being discovered and associated with the server? |
| A5. |
The HP Insight Management Agents must be installed and configured on the target server, and the Remote Insight Agent must be running.
|
| |
| Q6. |
I have installed the Insight Integration for HP OpenView NNM, but my systems are not appearing on the NNM Segment Map as HP devices? |
| A6. |
First, verify that the HP Insight Management Agents are installed and active. If HP Insight Management Agents are not in use or not correctly enabled, your systems will not be discovered as HP systems.
HP Management Agents for Servers 5.0 or later and HP Management Agents for Clients 4.20 or later are recommended as a minimum.
Second, be sure that the CPQDIS background process is running by using the OVSTATUS command. Refer to the "Checking the Status of Background Processes" section in the appendix of the Insight integration user guide for more information.
If the problem persists, you might have a general configuration or communication problem. Refer to the "Validating the Configuration" section in the appendix of the Insight integration user guide to check the overall configuration.
|
| |
| Q7. |
Why does the Insight Agent icon within the NNM device window display WEB DISABLED and the HP Management Agent launch does not execute? |
| A7. |
This message indicates that the Web-enabled HP Insight Management Agents are not being used. Web enabled agents are required to activate the integrated browser launch and provide direct access to the data collected by the HP Management Agents.
Verify that HP Management Agents for Servers 5.0 or later and HP Management Agents for Clients 4.20 or later are installed and configured for all HP monitored systems.
|
| |
| Q8. |
Why are SNMP events not showing up within the NNM Event Browser? |
| A8. |
Several items can cause this. First, verify that the SNMP trap destination is correctly specified on all monitored nodes so that traps are sent to the NNM console.
Second, be sure that the CPQTRAPD background process is running by using the OVSTATUS command. Refer to the "Checking the Status of Background Processes" section in the appendix of the Insight integration user guide for more information.
Inspect the TRAPD.LOG file to determine if the raw trap is being received.
If the problem persists, you might have a general configuration or communication problem. Refer to the "Validating the Configuration" section in the appendix of the Insight integration user guide to check the overall configuration.
|
| |
| Q9. |
Why does the browser return an incomplete Web page when I press the WEB ENABLED icon to launch to the HP Management Agents? Why does the device home page appear, but there are no options to access the HP Management Agents? |
| A9. |
Be sure that your browser application has both the Java and JavaScript options selected and enabled. These options can usually be found under the Advanced component of the Preferences or Internet Options configuration windows.
|
| |
| Q10. |
Why, after the NNM device discovery, do the Insight Integration device icons on the IP Segment Map keep changing back to the default OpenView images? |
| A10. |
The following environment variable must be included to the $HOME/.dtprofile file for each user ID used to view the NNM maps. Verify that the following lines are included in each file:
IPMAP_NO_SYMBOL_CHANGES=TRUE
export IPMAP_NO_SYMBOL_CHANGES |
| |
| Q11. |
The status indications for nodes are only available on selected maps. Why can't I see system status reflected on all NNM maps? |
| A11. |
This symptom can occur if Map Persistence is not enabled. Enabling Map Persistence ensures that the HP status updates are populated on both the main map and submaps within the NNM console.
For details on configuring Map Persistence, refer to the "Additional Configuration Requirements" section in Chapter 2 of the Insight integration user guide.
|
| |
| Q12. |
Why can't I browse to the HP Systems Management Homepage and view Insight Management Agent data on the host NNM system? |
| A12. |
If you have HP Insight Management Agents installed on a ProLiant server that also acts as the NNM host, you must edit the SNMP EMANATE agent with the correct settings to enable correct operations. See the section "Configuring SNMP on a ProLiant System running NNM" in Chapter 2 of the Insight Integration user guide for full details.
|
| |
Printable version
