Filter
Top Products
288 Chapter 5
Configuring ITO
Flexible-management Configuration
RESPMGRCONFIGS
RESPMGRCONFIG
DESCRIPTION ”responsible managers M1 ”
SECONDARYMANAGERS
SECONDARYMANAGER
NODE IP 0.0.0.0 ”M1”
DESCRIPTION ”secondary manager M1”
SECONDARYMANAGER
NODE IP 0.0.0.0 ”M2”
DESCRIPTION ”secondary manager M2”
SECONDARYMANAGER
NODE IP 0.0.0.0 ”M3”
DESCRIPTION ”secondary manager M3”
ACTIONALLOWMANAGERS
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 ”M1”
DESCRIPTION ”action allowed manager M1”
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 ”M2”
DESCRIPTION ”action allowed manager M2”
ACTIONALLOWMANAGER
NODE IP 0.0.0.0 ”M3”
DESCRIPTION ”action allowed manager M3”
MSGTARGETRULES
MSGTARGETRULE
DESCRIPTION ”target rule description ”
MSGTARGETRULECONDS
# for all messages
MSGTARGETMANAGERS
MSGTARGETMANAGER
# target manager from 17:00 to 24:00
# and 00:00 to 6:00
# from Monday to Friday
TIMETEMPLATE ”shift1”
OPCMGR IP 0.0.0.0 ”M1”
# target manager from 6:00 to 17:00
# from Monday to Friday
MSGTARGETMANAGER
TIMETEMPLATE ”shift2”
OPCMGR IP 0.0.0.0 ”M2”
# target manager on the whole weekend
MSGTARGETMANAGER
TIMETEMPLATE ”shift3”
OPCMGR IP 0.0.0.0 ”M3”
Message Forwarding between Management Servers
If you install the following simple example of a message-forwarding
template on a server called Source, Source will:
• Forward messages with message group DATABASE to a database
expert center (dbexpert) and pass control of the message to this
center, inform a second server (dbnotify) and, finally, cause the
message to be acknowledged directly on the local ITO server