OMW to OMU Message forwarding

Problem -
I am having two management server architecture in my environment, wherein OMU acts as Manager of Managers and OMW monitors all the servers and applications.
I want to forward all the alerts from OMW to OMU.

Solution -
Whenver you add any node in OMW, add the same node simultaneously in OMU.
To add node in OMU, follow the below steps -
(1) Add node in OMU through Actions -> Node -> Add, specify the node name, Fully Qualified Node Name, server type etc.
Uncheck the Automatic Software De-installation, Check communication options that core id is 00000000000000000

(2) Once the node addition is successful, get the ovcoreid from the OMW server for the same node.

(3) execute following command in OMU -
/opt/OV/bin/OpC/utils/opcnode -chg_id
for example : /opt/OV/bin/OpC/utils/opcnode -chg_id abc.vtg BBC_SOL_SPARC solaris COMM_BBC NETWORK_IP unix 034fere34fd343fer

Once the command is executed successfully, move the node to appropriate node group

(4) Restart OMU services : /opt/OV/bin/opcsv -stop
/opt/OV/bin/opcsv -start

Switch management server from OMW to OMU in case OMW failure

Problem -
I am having two management server architecture and out of which Operation Manager for Unix acts as Manager of Managers which receives alerts from OMW, NNM, BAC etc. and other management server is OMW which monitors servers and applications.

I want to forward all alerts to OMU from OMW in case OMW services goes down or OMW server is not available.

Solution -
To achieve above target, perform following actions -

(1) Create a failover policy in OMW.
Failover policy would of type Flexible Management Policy with following content -

#
# Configuration file
# defines two action-allow managers
# messages are always send to the primary manager
#
TIMETEMPLATES
#none
RESPMGRCONFIGS
RESPMGRCONFIG
DESCRIPTION "responsible mgrs for Nodes in VAA"
#Secondary managers have to be specified,
#but this section is not used by OpenView Operations for Windows
SECONDARYMANAGERS
SECONDARYMANAGER
NODE IP 0.0.0.0 ""
DESCRIPTION "HP OpenView Operation for Unix Management Server"
SECONDARYMANAGER
NODE IP 0.0.0.0 """
DESCRIPTION "HP OpenView Opearion for Windows Management Server"
ACTIONALLOWMANAGERS
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 """
DESCRIPTION "HP OpenView Operation for Unix Management Server"
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 """
DESCRIPTION "HP OpenView Opearion for Windows Management Server"
# Recommended: include the primary manager into the list of action-allow managers
# even if all possible managers are already listed
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 "$OPC_PRIMARY_MGR"
DESCRIPTION "current primary manager"
MSGTARGETRULES
MSGTARGETRULE
DESCRIPTION "always send all messages to current primary manager"
MSGTARGETRULECONDS
MSGTARGETMANAGERS
MSGTARGETMANAGER
TIMETEMPLATE "$OPC_ALWAYS"
OPCMGR IP 0.0.0.0 "$OPC_PRIMARY_MGR"

(2) Deploy the policy on all of the managed nodes
(3) When you want to switch management server from OMW to OMU, run following command on OMU server :
opcragt -primmgr
Wait till the command execution completes and check whether command is executed succesfully. If it goes successful then management server switching is done.
(4) If you want to revert the management server back to OMW then issue the same command on OMW server :
opcragt -primmgr

Unable to get proper severity symbol against node icon

Problem -
Unable to get proper severity symbol against the icon of the nodes in OMW.
For example, if a server A has got an alert of severity critical then the corresponding node icon should represent red symbol.

Solution -
Restart OMW services using command vpstat -3 -r and once command is successful, verify that all the services running fine using following command :
vpstat -3

Unable to do service discovery of nodes in OMW

Problem -

I am unable to get service map of the nodes which are added in OMW, the agent services are running absolutely fine and discovery policies are also been deployed but still i am not able to get service map of the nodes.

Solution -

Please perform following options and check whether you are able to get service map of the nodes -

a. Remove all the policies from this Agent
b. Confirm you have no policies on the Agent with the
command ("ovpolicy –list")
c. Kill the Agent the Agent (“ovc –kill”)
d. Rename the file system.txt to system.txt.old
e. Delete all the file in the folder “C:\Documents and
Settings\All Users\Application Data\HP\HP BTO Software\tmp\agtrep”
f. Re-start the Agent
g. Re-deploy the service discovery policies

OvEpMsgActSrv Service in OMW is aborted

Problem -
In OMW 8.10 OvEpMsgActSrv Service is aborted abnormally and even restarting the servicesand rebooting the system it didn't started

Solution - Stopped OMW services using vpstat -3 -r stop and removed following folder

$OvShareDir\server\datafiles\bbc\snf\OvEpMessageActionServer

and then restarted services using vpstat -3 -r start

which finally resolvd the issue.