OSM Migration Guide (G06.28+)
Table Of Contents
- What’s New in This Manual
- About This Guide
- 1 Introduction to OSM
- 2 Preparing for OSM
- 3 OSM Server-Based Components
- 4 OSM Client-Based Components
- 5 Getting Started With OSM Applications
- 6 TSM Coexistence and Fallback
- A Migrating Your Registry Settings
- B Memory Guidelines for OSM
- C Configuring Remote Services
- Configure Modem for Dial-In and Dial-Out
- Create Windows User Name
- Configure Carbon Copy 5.7 or Microsoft NetMeeting for Dial-In
- Configure OSM Notification Director (ND) for Each Host Server
- Configure OSM Notification Director (ND) for Dial-In and Dial-Out
- Configure Incoming Connections
- Reconfigure System Standby and Hibernate Mode
- D Troubleshooting
- E Uninstalling TSM
- Index
OSM Server-Based Components
OSM Migration Guide—527273-015
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>
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
.
Creation of System Inventory Files
For T0682G06 AAC and later, OSM has automatic system inventory file creation
enabled by default (you no longer need to perform the Reload Configuration Settings
action every time you want to create a system inventory file). These system inventory
files are created along with Periodic Incident Reports (IRs), and are attached to the IRs
if the “Suppress Attachment files on Periodic IRs” option is deselected in the OSM
Notification Director Preferences dialog box.
Note. A system inventory file will not be created if a Periodic IR is generated before OSM
completes system discovery.