This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
MoM•A Large service configuration can be distributed over a number of servers
•Breakdown service conf. over a number of ‘Mid-Level-Manager’ servers aggregated by Manager-of Managers
•Create ‘connection services’ on higher level to reflect top – level service on lower level
top-level services
connection services
•Forward status changes
Distribute a service configuration
August 28, 2015 16
Forward
MLM Server
Status Listenerscript
•Service Listener script listens for status changes of top level services
•New message impacts the top level service E-mail
message
MoM server
•Service Listener generates a message with service name and new severity
•Message is forwarded to the MoM server
Forward template
Forwarding service status
August 28, 2015 17
MoM Server
•On MoM server we observe the aggregated top-level services from MLM servers
•Forwarded message from MLM server impacts connection service
messageMLM server
•Use actions on impacted service to drill-down distributed service hierarchy
Monitor status on MLM server
August 28, 2015 18
• Service graph
MoM Server
• Root Cause Graph
• Message Browser
Actions open Java UI connected to MLM server
MLM server
Drill down service hierarchy
August 28, 2015 19
Forward
MLM Server
Status Listenerscript
• After the problem is resolved, message can be acknowledged
• Impacted service returns to Normal severity
message
MoM server
• Service Listener generates the message with new severity (Normal)
• Message is forwarded to the MoM server
Forward template
Synchronize states
August 28, 2015 20
Two implementations• Local listening of service status changes−Status Listener scripts are running on MLM server(s).−Messages generated are forwarded via message
forwarding template to MoM server.
• Remote listening of service status changes−Status Listener scripts are running on MoM server. −Service status changes are monitored remote via TCP
socket connection to MLM server. − There is no message forwarding needed (messages are
generated on MoM server).
August 28, 2015 21
Architecture 1: listen locally
• Objectives• Problem description• Use Cases• Architecture• Implementation
MoM Server MLM Server 2MLM Server 1
opcsvcm
Flex. Mgmt. Template on local agent: Send message to
MoM server
opcuiwww
opcsvcm
XML
Attach and monitor status changes of top level services via XML
or C++ interface
Drill down / open Java UI on MLM server to
inspect details via actions defined
on services, using JGUI APIs
generate message using opcm sg
Status Listenerscript
Configurationscript
opcuiwww
message receiver /manager
August 28, 2015 22
MoM Server
MLM Server 2MLM Server 1
opcuiwww
opcsvcm
opcsvcm
XML
Attach and monitor status changes of top level services via XML
or C++ interface
Drill down
configure top level services to be
monitored
Discover top level serviceson MLM severs
inetd TCP socket
opcuiwww
generate message using opcmsg
Status Listenerscript
Status Listenerscript
Configurationscript
Architecture 2: listen remotely
agent
message receiver
August 28, 2015 23
How to install and configure? (1)• Local listening of service status changes −Copy the example files− Enable Java UI API functionality −Modify the example MoM service hierarchy xml file−Add and assign service hierarchy on MoM server−Configure MoM environment and upload prepared
templates on MLM servers−Configure the status listener processes−Start the status listener processes
August 28, 2015 24
How to install and configure? (2)• Remote listening of service status changes −Copy the example files− Enable opcsvcterm port on all MLM servers− Enable Java UI API functionality−Modify the example MoM service hierarchy xml file−Add and assign service hierarchy on MoM server−Upload message template for acknowledging−Configure the status listener processes−Start the status listener processes
August 28, 2015 25
Federated Manager of Manger with cascading Service Navigators:
How to use SNVP in this scenario?
August 28, 2015 26
How to use SNVP in this scenario?
• SNVP works Service Hierarchy oriented− Hierarchies contain a specific view.− Only Hierarchies can be deployed to OVO
management servers− Objects can be copied between hierarchies.
• Can I maintain one large Service Hierarchy and deploy only parts?− No. For this use case you have to maintain
separate Service Hierarchies
• How to maintain “connection services”?− Select the same Object from the CMDB, or− copy objects between hierarchies, or− upload services from MLM.
MLM1 Hierarchy
MoM Hierarchy
August 28, 2015 27
Operational Service Views
August 28, 2015 28
Why an additional state?• Today:−Service Navigator can display only one state per service−All messages in active browser are used to calculate
service states.
• Drawback−Some operators are not interested in problems already
owned by other operators.−Other users want to see all open problems
August 28, 2015 29
Solution• User can choose, if …−Service views shall consider all active messages, or−only not already “owned” messages.
• Two states−Overall:
All message drive the status of service objects−Operational:
Only new message are used for status calculation
• User can switch between the views
Available with OVO/UNIX 8.1x 1HCY05
August 28, 2015 30
•Service hierarchy My Internet without any OVO events
Major message
•Event with severity major hits SystemA service
Critical message
Critical message
•SystemA is hit by another message. This time the problem is critical.
•Also SystemB is critical, due to an critical event
Current - Overall calculation
August 28, 2015 31
Owning critical
Select “Operational”
Severity has changed to MAJOR
Owning critical
Severity has changed to NORMAL
Select “Overall”
Severity has changed to CRITICAL
•Operator owns the critical message from SystemA
•Operator selects “Operational” view from drop down list
•SystemA turns from critical to major. Multi state indicator is in lower right corner
•Owning the last critical event, changes “My Internet” to major, since all critical events are owned
•Operator switches back to Overall calculation view. Owning did not have any impact on the original CRITICAL service status
New Operational view
August 28, 2015 32
Overall and operational views
Overall:all message are
calculated
Operational:Only not owned
message are calculated
August 28, 2015 33
Enable Operational Views
• Service engine:# /opt/OV/bin/ovconfchg -ovrg server \
-ns opc -set OPC_SVC_CALC1 TRUE
• Enabel Java GUI# /opt/OV/bin/ovconfchg -ovrg server -ns opc \