Group 1
======
Agent directly forwarding alerts to the management Server (MOM-SAS).
Group 2
======
Agent forwarding alerts to the internal management Server (I-MOM) & this inturn forwards alert to MOM-SAS.
Question
=======
We will be setting up 2 OMW 9.x servers (Primary-OMW & Secondary-OMW) & within 2 - 3 months MOM-SAS will be removed but till then all the alerts from Group 1 & Group 2 should be visible on on of the new OMW server & MOM-SAS.
Can this be achived?
I have refered HPOpenViewOperationsManagerAdministratorReference.pdf, page 115.. Has anyone tried this.
Also Page 281, on
http://update.external.hp.com/HPSoftware...e_Help.pdf
Forwarding messages to Server Pool. Will this solve my problem.
Yes, this should work.According to the documentations,
OVO gives such enterprises the ability to send
messages from one managed node to multiple OVO Management Servers, and to exchange
and forward messages among management servers as well. This concept is referred to as
"Flexible Management."
Note that Flexible Management does not imply sending the same message to multiple
managers; this would require huge synchronization efforts, and it is very difficult to handle
sending the same message to multiple instances. Each message created is sent to one
management server only. However, the managed nodes are able to send different types of
messages to different management servers.
For example, all database-related messages can
be sent to one manager and all OpenView trap-related messages to another management
server. Using a "time template" it is possible to implement "Manager-of-Manager" functionality
and "Follow-the-Sun" models. Additionally, operators can escalate messages to other OVO
Management Servers if predefined by the administrator, and the administrator can configure
automatic message forwarding to other OVO Management Servers
So Group1 of servers will send the messages to MOM-SAS
and Group1 of servers will send the messages to I-MOM.
and MOM-SAS receives the event from I-MOM after ur configuration. This is possible.
Check this link, The author of the post was able to send messages to 2 managers.
http://h30499.www3.hp.com/t5/ITRC-OV-Ope...ue#M156660
Also I referred "MoM Cookbook" & send messages to 2 Managers should be possible by "Server Pooling".. Has anyone tried this.
(10-28-2011 07:44 PM)fire Wrote: [ -> ]Yes, this should work.According to the documentations,
OVO gives such enterprises the ability to send
messages from one managed node to multiple OVO Management Servers, and to exchange and forward messages among management servers as well. This concept is referred to as "Flexible Management."
Note that Flexible Management does not imply sending the same message to multiple managers; this would require huge synchronization efforts, and it is very difficult to handle sending the same message to multiple instances. Each message created is sent to one management server only. However, the managed nodes are able to send different types of messages to different management servers.
For example, all database-related messages can be sent to one manager and all OpenView trap-related messages to another management
server. Using a "time template" it is possible to implement "Manager-of Manager" functionality
and "Follow-the-Sun" models. Additionally, operators can escalate messages to other OVO
Management Servers if predefined by the administrator, and the administrator can configure
automatic message forwarding to other OVO Management Servers
So Group1 of servers will send the messages to MOM-SAS
and Group1 of servers will send the messages to I-MOM.
and MOM-SAS receives the event from I-MOM after ur configuration. This is possible.
We have recently implemented OMW 9 and we have implemented in a Server Pooling configuration.
Flexible Management is a concept where a Managed Node can be managed by any one of the OM in the group.
Let me know what specifically you are looking for and I can provide you the information. Most of the information is available in OMW installation guide and it is explained clearly.
What we have noticed is that the messages from the managed node is sent to a virtual IP (which is configured to point to the primary OM server); and OM uses WMI to automatically sync messages from the primary server to the secondary.
Once the message is acknowledged - the secondary server is automatically updated.
The real challenge we are currently facing is the "TWO WAY SYNC" for all policies/nodes and Instrumentations---- currently we are managing this manually - but when time permits we are planning to automate this process... the beauty of HP OpenView is it allows you to do anything through scripts - as long as you are a "Scripting Guru".....
@nokia9300
Thanks for responding to my query.
We already have agents forwarding messages to OMU-1. OMU-1 is set to forward all the alerts to OMU-2.
OMU-2 will be decommissioned within 2 - 3 months & now a new OMW (Primary & Secondary) will be setup.
Requirement.
I want OMU-1 to continue forwarding messages to OMU-2 & also to OMW. In short the messages should be visible simultaneously on OMU-2 & OMW (Not worried about sync at the movement)