OSM Migration and Configuration Guide (G06.30+)

OSM Migration and Configuration Guide—527273-021
6-1
6 TSM Coexistence and Fallback
You can have both OSM and TSM software installed and, in some cases, running on
your NonStop S-series servers and system consoles, provided the Coexistence Issues
are addressed. This section describes OSM and TSM coexistence issues and how to
fall back to using only TSM if necessary.
Coexistence Issues
Coexistence issues include some TSM functionality that is disabled by OSM, specific
situations in which OSM is required or strongly recommended, and other situations
where you can use OSM or TSM, but not both.
Starting OSM processes disables the following TSM functionality, once you restart
$ZTSM (as described in Starting OSM Persistent Processes on page 3-7):
•
Processor incident analysis and automatic power scrubbing
•
Automatic line-handler process used to communicate with other nodes
For information on how to reenable these TSM features, see Step 3 under Fallback to
TSM.
To avoid confusion and system problems, HP recommends these practices:
•
On your system console, check that only one Notification Director application is
configured for dial-out to avoid duplicate dial-outs for the same problem. You can
use either the OSM or TSM Notification Director. To learn about the advantages of
using OSM, see OSM Notification Director
on page 5-22.
•
Use the OSM Service Connection (instead of the TSM Service Application) for all
systems that are part of a ServerNet cluster. OSM suppresses generation of
alarms and dial-outs on all nodes in the cluster when service actions are performed
on a cluster from any node. This protection is not available if some nodes are
managed by TSM because TSM cannot communicate with OSM. Also, TSM does
not support the HP NonStop ServerNet Switch (model 6780) hardware used in
ServerNet clusters that are configured in a layered topology.
•
Do not perform simultaneous SP firmware updates with TSM and OSM.
•
If you have written tools to look for TSM events, change them to look for equivalent
OSM events.
Note. Running OSM and TSM software simultaneously is not recommended. The preferred
method is to stop TSM server processes before starting OSM. You can easily Fallback to TSM
if necessary. There is no need to remove TSM software, but instructions are provided should
you decide to do so (see Section E, Uninstalling TSM).