| Q1. |
How do I get support for this product? |
| A1. |
If you can’t find the answer to your questions on this page, you can request support via e-mail. HP will usually respond to your request on the next business day. Request support. |
| Q2. |
When launching the Web browser to a device, why do I get a message stating that the page cannot be displayed or a connection cannot be established? |
| A2. |
Currently, the HP Management Agents menu option appears on all HP systems. In this case, the Web agents may not be running on the device that you are trying to browse.
|
| |
| Q3. |
When launching to Insight Manager 7, why does the browser display the message "The device at IPADDRESS was not found. The device was not found"? |
| A3. |
The device launched has not been discovered by the Insight Manager 7 server. Log into the Insight Manager 7 server and run discovery on the subnet containing the device, or add the device manually.
|
| |
| Q4. |
Why does the integration discovery program not execute? |
| A4. |
If hpqdscvr.exe exits unexpectedly when running discovery, verify that the discovery log file is not open.
|
| |
| Q5. |
Why are the Discovery Menu Items not Installed? |
| A5. |
The two Start Menu entries for the integration discovery programs are only included if the HP Class Extensions are installed on the selected system.
Both the discovery and un-classification programs can be run from the command line instead of the Start Menu.
|
| |
| Q6. |
Why are Remote Insight Inclusion Links not created for devices in the HP classes when using the R option? |
| A6. |
When the discovery program runs with the R option, it only checks the default Unicenter classes for Remote Insight Objects. Any objects in the HP classes will not be checked for Remote Insight Objects.
To check systems in the HP classes for Remote Insight objects, run hpqdscvr.exe with the S option.
|
| Q7. |
Why are Remote Insight inclusion links not created on my servers? |
| A7. |
These conditions must be met before the inclusion link for the Remote Insight/Integrated Lights-Out in a server will be created.
Both the server and the Remote Insight/Integrated Lights-Out must be discovered by Unicenter. The Remote Insight object will remain on the Unicenter segment map.
The Remote Insight/Integrated Lights-Out must be classified in the HP_RemoteInsight class.
|
| |
| Q8. |
Why are the new message records not used? |
| A8. |
The integration kit was installed, but the new message records are not being utilized (most of the trap messages still say Compaq).
The old message records are not removed by default when the new message records are installed on a system. Run the cpqem_remove script from the previous version of the integration in order to remove the old message records from the database.
Existing message records are not automatically removed in order to allow the user to preserve any customizations that may have been created.
If only the message records that new since the last version of the integration need to be installed, change to the cpqem\new3.1 directory and run the loadnew script.
|
| |
| Q9. |
Why does the In-context launch to HP Systems Insight Manager fail? |
| A9. |
When performing an in-context launch to Systems Insight Manager, a web page stating "An error occured when generating the page" is displayed.
Verify that you are using the correct launch program for Systems Insight Manager. The file hpsimlnh.exe should be used instead of hpim7.exe. If you are using Systems Insight Manager, you may delete hpim7.exe from the Unicenter\bin directory, rename hpsimlnh.exe to hpim7.exe, and copy the renamed file to the Unicenter\bin directory.
|
| |
| Q10. |
Why are the HP ProLiant MIBs missing in Unicenter? |
| A10. |
Sometimes not all of the HP MIBs are loaded into Unicenter. MIBs that are not loaded will not appear in the Unicenter MIB browser.
Make sure all the MIBs from the integration (\cpqwv\mibs) are copied to UnicenterDirectory\services\config\mibs directory and run CPQMIBS.BAT from the \cpqwv\mibs directory to reload the HP MIBs.
|
| |
| Q11. |
Why are the HP Management Agents are not discovered? |
| A11. |
The SNMP settings may need to be changed. Verify the correct SNMP community strings are configured for the InsightManager Agent Class in the DSM Wizard. Verify the correct SNMP community strings are configured for the InsightManager Agent Class in the Pollset Browser.
Note: Both of these settings default to "public".
|
| |
| Q12. |
Why are the HP Management Agents not discovered on HP_RemoteInsight devices? |
| A12. |
To avoid severity propagation errors like the following, HP_RemoteInsight devices are no longer monitored for the HP Management Agents. Only the host servers are monitored for the agents.
To achieve this, the hpqdscvr program deletes any InsightManager objects that have the state "ANY:ABSENT" when it is executed. Any devices that are reclassified as HP_RemoteInsight objects will have their InsightManager objects deleted during this step.
This can result in other InsightManager objects with the status of "ANY:ABSENT" being deleted. In this case, the agents will be rediscovered by the DSM when they return to the UP state.
Unicenter Severity Propagation Error:
"CA-Unicenter TND Severity Propagation_0_E: CA-Unicenter TND Severity Propagation Circular reference. Inclusion object ignored. Inclusion: ccd495bd-68f1-447b-aa75-e90266b8373f Parent: 8bd6702b-43c4-4e4d-9019-bcffee624362 Child: 15a57601-5a94-4719-acee-03cdd39eade7"
|
| |
| Q13. |
Devices appear on the map with the new HP icons, but no agents are discovered running on the HP devices. Why? |
| A13. |
Verify that the gwclass.dat file located in tng\services\config\aws_wvgate contains the entries "HP_Host|HP_Workstation|" at the end of the line. These entries tell the Distributed State Machine to monitor the new HP classes.
|
| |
| Q14. |
Why do the CA agents not appear under the HP classes in Unicenter NSM r11.0 and r11.1? |
| A14. |
Reclassification of systems running CA agents to the HP classes is not currently supported with the integration running on Unicenter NSM r11.0 and r11.1. Systems running CA agents should be returned to their default classes. |
Printable version
