HP OpenView Operations Administrator's Reference - filibeto.org

Configuring OVO
Configuring Flexible Management Templates
144
About the Time Zone String
The creation time of an OVO message is always defined in UTC,
regardless of where in the world the managed node is located. As a
result, OVO messages contain an indication of the difference between
UTC and the local time on the managed node. By tracking time in this
way, the OVO management server is able to calculate the local time of
the managed node that sent the message. The management server can
then decide whether or not it is appropriate to act.
Service hours are usually defined in terms of the local time on the
managed node. For example, a service provider uses the service hours
template to tell the OVO management server that managed nodes in
various time zones must be supported between 08:00 and 16:00 local
time. Templates for scheduled outages define time in terms of the local
time on the server that provides the service that is scheduled to be
unavailable. For example, the administrator of an OVO management
server in the United Kingdom (UK) knows that a SAP server situated in
eastern United States (U.S.) will be unavailable for maintenance reasons
between 22:00 and 02:00 U.S. Easter Standard Time (EST).
The templates for scheduled outages and service hours on the OVO
management server can contain a string that defines a fixed local time
zone (for example, EST). The OVO management server uses the value of
the time zone string and the time (in UTC) to calculate the fixed local
time on the given management server for which an outage has been
scheduled.
Syntax for the Time Zone String
The following example illustrates the syntax for the time zone string:
TIMEZONETYPE Fix TIMEZONEVALUE "EST"
By default, OVO evaluates time conditions for both service hours and
scheduled outages by comparing the time frame defined for each
condition to the time the message is received on the OVO management
server.
Chapter 2