13.12.2012 Views

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setting the Time Zone Parameter<br />

Configuring OVO<br />

Configuring Flexible Management Templates<br />

You can force the OVO management server to use the message creation<br />

time on the local managed node, rather than the message arrival time on<br />

the management server.<br />

To specify the time zone parameter for service hours or scheduled<br />

outages, set one of the following strings using the ovconfchg<br />

command-line tool:<br />

❏ Service Hours<br />

OPC_SERVHRS_USE_AGENT_TZ TRUE<br />

❏ Scheduled Outages<br />

OPC_OUTAGE_USE_CREATE_TIME TRUE<br />

These strings force the OVO management server to apply the time frame<br />

for service hours and scheduled outages defined on the OVO<br />

management server (for example, 08:00 -- 16:00) as a sliding time frame<br />

for managed nodes in their respective local time zone.<br />

NOTE Make sure the local time is correctly set on the managed node.<br />

About the Command-line Interface<br />

The message manager does not automatically read the configuration<br />

template for outages and service hours each time the template file is<br />

modified (for example, by the system administrator or an external<br />

application).<br />

You can use the command-line tool opccfgout(1M) to start the<br />

reconfigure request:<br />

opccfgout -update<br />

Additional options allow you to set status variables for the conditions:<br />

opccfgout -set_cond [-true|-false|-default]<br />

To list the current status of the status variables, enter:<br />

opccfgout -list_cond |-all<br />

Chapter 2 145

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!