Verifying Configuration

To verify that a configuration is correct, check the following:

1. Start all HP Operations services and processes
2. Use opcrpccp to verify that registration of the HP Operations RPC Servers on both the managed node and the management server is correct. Make sure the correct ports are used as configured. If there is no endpoint mapper running on the destination system, this command will fail entirely (which is correct).
3. Verify that all processes are running properly using vpstat and opcagt.
4. Test Server to Agent communication by starting a tool from the HPOM for Windows tools folder on the destination managed node.
5. Test Agent to Server communication by sending test messages using opcmsg or any other mechanism generating an HP Operations message to be sent to the management server. Optionally enable tracing (Area ALL, DEBUG and debug area COMM, CONF) and check the trace file.
6. Test configuration distribution (policies and instrumentation).
7. Wait for heartbeat-polling cycles to expire - no errors should be reported. If the HP Operations Agent is stopped, the associated heartbeat-polling errors should be displayed.
8. Everything should behave as usual. There should be no communication related error messages in the HPOM for Windows GUI originating from the managed node.
9. Check the opcerror log files on the managed nodes for applicable entries. The utility opcragt, which was introduced with patch OVOW_00095, can also be used in environments as described in this paper. Opcragt is an excellent tool for testing the server-to-agent communication.

   NOTE:
   The utility opcragt, which was introduced with patch OVOW_00095, can also be used in environments as described in this paper. Opcragt is an excellent tool for testing the server-to-agent communication.

   
   

   Related Topics:

   • Concepts of DCE RPC communication without endpoint mapper
   • Configuring the HP Operations management server system
   • Configuring HP Operations managed node systems
   • Server port specification File
   • Configuration examples
   • Troubleshooting
   • Variable reference
   • Internal process handling

    

   Internal Server Error

   The server encountered an internal error or misconfiguration and was unable to complete your request.

   Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

   More information about this error may be available in the server error log.

   Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.