Absent Member.. GTrejos7 Absent Member..
Absent Member..

[ST OMU] How to modify an Internal policy in OMU


How to modify an internal policy an internal policy in Operations Manager for Unix (OMU), so that one can create for example an incident ticket.
i.e: The policy that generates the message:
"node abc.net is probably down. Contacting it with ping packages failed. (OpC40-436)"

Trying to modify this policy is not allowed since the source say that is "Internal".


Internal messages can be passed to local Operations Manager for Unix (OMU) agent (agent installed on the Management Server)
which can then be filtered through message interceptor policies (msgi).


To Pass the internal messages to the agent you have to set either of the following variables:

Description : If TRUE, OVO-internal messages (message-group OpC or OpenView; mainly OVO-internal status- and error-messages) are passed to the OVO agent and can be filtered through message interceptor templates.
Note: This is also possible on the OVO management server. However, the local OVO management server's agent must run and it must use the same character set as the server.

Type/Unit : bool

Default : FALSE

Documented : Y

namespace: eaagt, opc (>=OVO8)

Description : With this variable set to TRUE, OVO internal messages are always filtered by the Message Interceptor, even if the process itself is not running. In this case, internal messages arrive at the next startup of the Message Interceptor. Setting this variable to TRUE, no internal messages are sent unfiltered to the Management Server.
Be careful when using this setting, as OVO internal messages sent to the management server may arrive delayed. Important Note: OPC_INT_MSG_FLT must be set to TRUE in order to use OPC_INT_MSG_FLT_AWS!

Type/Unit : bool

Default : FALSE

Documented : Y

namespace: eaagt, opc (>=OVO8)

First you need to set variable OPC_INT_MSG_FLT VARIABLE to true in your management server:

#ovconfchg -ovrg server -ns eaagt -set OPC_INT_MSG_FLT TRUE

and then create the policy using Message Groups Openview or OPC.

Please be aware of after setting the OPC_INT_MSG_FLT variable to TRUE, you must restart manually the agent in order to
enable the usage of this variable. Therefore please run:

#ovc -restart

Additionally, you need to se the variable OPC_INT_MSG_FLT_AWS to TRUE:

#ovconfchg -ovrg server -ns eaagt -set OPC_INT_MSG_FLT_AWS TRUE

Then you will observe the incoming messages and you can start building the rules to match those you want.

Most of the internal messages have the following values for "Application":

• OpC
• HP OpenView Operations
• OpenView
• ...

and the "Object" field can contain:

• Heartbeat Polling
• ovlogmsg
• ovoadif
• opcmsga
• ovcd
• opcmona
• ovconfd
• ...

and the "Message Group" field can contain:

• OpenView
• OpC
• ...

This is documented in the following KCS article:


HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you liked it I would appreciate KUDOs.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.