OSM Migration Guide (G06.29+)

OSM Server-Based Components

OSM Migration Guide—527273-018

3-3

Configuring Additional TCP/IP Processes for OSM

Connectivity

Configuring Additional TCP/IP Processes for OSM Connectivity

OSM has two default TCP/IP processes, $ZTCP0 and $ZTCP1, which are used for

OSM Service Connection and OSM Event Viewer connectivity. The physical

connections (two for fault tolerance) are made through Ethernet ports located in PMF

CRUs in your NonStop S-series server (as described in the NonStop S-Series

Hardware Installation and FastPath Guide). This allows the OSM Service Connection

to communicate with the OSM CIMOM (server) process through the service processors

(SPs), using those default $ZTCP0 and $ZTCP1 TCP/IP processes.

For when faster response between OSM Service Connection and the server is desired,

you can configure and use additional TCP/IP processes in your OSMCONF file. These

physical connections are made through dedicated ports on either an E4SA, FESA, or

GESA, or through a Gigabit 4-port ServerNet adapter (G4SA) in an IOAM enclosure.

To configure these optional TCP/IP processes for OSM connectivity, edit the

OSMCONF file to specify TCP/IP processes in addition to the default SP stacks

($ZTCP0 and $ZTCP1):

stack = <TCPIP process name>

For example:

stack = $ZTC00

stack = $ZTC01

If you choose this alternative connection option, use the IP address or host name

corresponding to one of the stacks specified when Establishing an OSM Service

Connection Session or OSM Event Viewer session.

Like any changes to OSM configuration defaults, these changes are easiest to make

before you start OSM processes ($ZOSM and $ZOEV in this case). However, you can

also make the changes to your OSMCONF file take effect after OSM processes have

already been started, as described in Creating and Using an OSMCONF File.

Enable Enhanced Redundant Power Scrub

For T0682G06 AAR and later, an enhanced version of the Redundant Power Scrub

test is available. It provides independent battery testing and an extended load test for

the bulk power supplies.

This enhanced version of the Redundant Power Scrub must be enabled in your

OSMCONF file, but not until these prerequisites are met:

•

All enclosures must be updated with a new PIB-to-PIB crossover cable (see FCO

44440 for details).

•

OSM T0682G06 AAR or later is installed.

Note. With this new version of Redundant Power Scrub, the action can take up to 25 minutes

to complete. The new battery scrub is significantly enhanced in its ability to detect weak or

failed batteries. For systems with many old batteries (over 5 years old), the battery scrub might

call out multiple batteries for replacement