HP Operations Manager

  • 發行項

適用於: Operations Manager 2007 R2

This section covers problems specific to the HP Operations Manager Connector.

Corrupt Data in Solaris SPARC

The profile sci_configuration file has two directives to support internationalization. Both Windows and UNIX platforms require the following directives.

  • OVO_NEW_EVENT_CODESET

  • OVO_MOD_EVENT_CODESET

Acceptable values are:

  • UTF8CODESET

  • LOCALCODESET

The default directives for Solaris SPARC are:

  • OVO_NEW_EVENT_CODESET=UTF8CODESET

  • OVO_MOD_EVENT_CODESET=LOCALCODESET

With older versions of the OVO Message Interceptor daemon (opcmgr) that require the LOCALCODESET directive for both OVO_NEW_EVENT_CODESET and OVO_MOD_EVENT_CODESET, data corruption is possible.

To avoid this possibility, restart the provider after you make a change to the profile_sci file.

On UNIX systems:

/opt/microsoft/scx/bin/tools/scxadmin -restart

On Windows systems:

Restart the OVO/W server.

Alerts Do Not Display

If alerts sent from Operations Manager 2007 R2 to HP Operations Manager do not display in the HP Operations Manager Event Browser, check the following:

  • Verify that HP Operation Manager recognizes the node, from which the alert was forwarded, and that the node is part of a Node Group within HP Operations Manager.

  • Verify that the user who is running the HP Operations Manager Event Browser has the necessary rights to view the events generated by Operations Manager 2007 R2. This includes the user’s Responsibilities for Node Groups and Message Groups.

  • Verify that there are no templates or policies preventing the events generated by the SCOM 2007 R2 Interop Connector from displaying in the HP Operations Manager Event Browser.

  • Verify that no HP Operations Manager agent is running on the Windows-based server that the Interop Connector service is running on.

  • Verify that you can receive events for the Operations Manager 2007 R2 agent in question. Send a test message from the HP Operations Manager server through the command line. The following code sample shows how to use the opcmsg command to simulate the Interop Connector.

    opcmsg a="System Center OpsMgr to HP OVO" msg_grp="SCInterop” o="PrincipalName=<node name of OpsMgr agent>" msg_text="Description=Some message description here" node=<node name of OpsMgr agent>

  • Verify that the HP Operations Manager agent running on the HP Operations Manager server is not buffering events.