OSM Migration Guide (G06.27+)

OSM Server-Based Components

OSM Migration Guide—527273-013

3-2

Optional OSM Configuration

It is not necessary to create a configuration file to use OSM with the default settings.

However, if you want to alter any default settings or take advantage of the following

OSM features, you must create and use an OSMCONF file:

•

Configuring Additional TCP/IP Processes for OSM Connectivity on page 3-2.

•

Adjusting the processor priority rating assigned to OSM processes relative to other

applications. For more information, see “OSM Performance Considerations”

Support Note (S03133A).

•

Disabling Creation of System Inventory Files on page 3-3.

•

Some optional parameters for Configuring Automatic Data Collection on page 3-4.

•

Enabling Secure Sockets Layer (SSL) on page 3-5

Creating and Using an OSMCONF File

To create an OSMCONF file from an OSMINI template file and to put your

configuration changes into effect:

1. Go to $SYSTEM.ZSERVICE and copy OSMINI to create a new file named

OSMCONF.

2. Edit the OSMCONF file to customize the default settings as desired. To avoid

possible problems, delete blank lines from the OSMCONF file.

3. When you start OSM server processes, configuration settings are read from the

OSMCONF file if one exists in that location. If not, OSM default settings are used.

To change your settings after OSM is running, select Reload Configuration

Settings from the OSM Service Connection Tools menu. To complete this

operation, you are instructed to restart the $ZOSM and $ZOEV processes.

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

Note. OSMINI is a template file delivered as part of T0682 so that you can create your own

customizable OSMCONF file. Because the OSMCONF file is user-created and not installed by

OSM, when you upgrade to a new T0682 SPR, your customized settings are not overwritten.