Technical data

Workaround: Launched independently of the OSM Service Connection, the OSM Event Viewer is
already compatible with NAT and no additional configuration is necessary. The workaround for
accessing the web-based management applications is also to launch them directly from an Internet
browser and not through the OSM Service Connection.
Configuring Insight Remote Support Advanced
“HP Insight Remote Support Advanced” (page 39) replaces the OSM Notification Director in both
modem-based and HP ISEE remote support solutions. For information on migrating to Insight Remote
Support Advanced, refer to the instructions in Insight Remote Support Advanced for NonStop,
located in the Support and Services collection of NTL
As part of the migration process described in that document (after disabling the OSM ND), you
will be directed to add the following parameter to your OSMCONF file (for each NonStop system
to be monitored by Insight Remote Support Advanced) to enable remote notification (dial-out) to
Insight Remote Support Advanced/WEBES:
IR_Alert = YES
Additionally, the following parameter must be added to each NonStop system to be monitored by
Insight Remote Support Advanced (not necessary needed for NonStop BladeSystems, as SSL is
enabled by default):
UseSSL = ON
NOTE:
With OSM version T0682 H02 ADD (or later), you do not need to add the UseSSL parameter.
NOTE: This assumes you are using OSM version T0682 H02 ACC or later, which eliminates the
need for additional OSMCONF parameters required in earlier versions and also supports fault
tolerant console configurations for NonStop NS-series and NonStop BladeSystems, allowing Insight
Remote Support Advanced to monitor a system from more than one console without getting duplicate
remote notifications (dial-outs).
After editing your OSMCONF file, you must restart the following OSM server processes (if running
on the NonStop system) for the changes to take effect:
• $ZCMOM ($ZZKRN.#OSM-CIMOM)
• $ZOSM ($ZZKRN.#OSM-APPSRVR)
• $ZOEV ($ZZKRN.#OSM-OEV)
Configuring OSM Power Fail Support
With T0682 H02 ACC (and later), OSM enhances power fail support by providing two new
OSMCONF settings to allow for execution of an automated system application shutdown script.
The SHUTDOWN_SCRIPT_NAME and SHUTDOWN_SCRIPT_TIME parameters specify the name
and location of the script to be run and when it will be executed during the power fail detection
and monitoring sequence. For information on how to configure your NonStop system to take
advantage of OSM power fail support, see the planning guide for that type of NonStop NS-series
or NonStop BladeSystem.
When power fail support is properly configured and OSM detects an AC power failure, it triggers
and counts down a ride-through period after which – if the power has not yet been restored –
OSM initiates a controlled shutdown of I/O operations and processors. If the script name and time
parameters have been added to your OSMCONF, the specified script is triggered by the
SHUTDOWN_SCRIPT_TIME, which provides time for the script to run before the end of the
configured ride-through time (as described below).
SHUTDOWN_SCRIPT_NAME = name
name is a fully qualified location/name of the application shutdown script to be executed. The
file type should be file code 101 (an editable text file). The location/name must be fully
Optional OSM Configuration 29