Technical data

NOTE: You can use the stack parameter with syntax <TCPIP process name>:<specific
IP address> to control the specific server IP addresses used by the OSM Service Connection,
HP SIM, or Insight Remote Support Advanced. The OSM server will not allow connections to other
IP addresses. For OSM Service Connection sessions, this parameter affects both the URLs allowed
for the initial connection to the OSM Server, and additional TCP/IP connections opened afterwards
for realtime updates and fault tolerance.
The feature of restricting the OSM stack to specific IP addresses is available only with T0682ACV
and later SPRs of T0682.
You can specify multiple specific IP addresses for a single TCP/IP process name by using more
than one stack entry, each with an additional IP address for a single TCPIP process name. A
single stack entry for a TCP/IP process name without any :<specific IP address> will
cause the OSM server to permit use of any of the NSK IP addresses associated with that TCP/IP
process name.
There could be many NSK Server IP addresses associated with a TCP/IP process name, especially
when using IPv6. You may use an SCF command such as SCF INFO SUBNET <TCPIP process
name>.* to see associated IP addresses.
For example, OSM Service Connection attempts to use all of the addressable IP addresses configured
in SCF for TCP/IP processes $ZTC0 and $ZTC1 after configuring the following entries in the
OSMCONF file:
stack = $ZTC0
stack = $ZTC1
In order to restrict OSM connections to two specific IP addresses for $ZTC0, while allowing OSM
to use all addressable IP addresses for $ZTC1, use the following entries:
stack = $ZTC0:<IP address A>
stack = $ZTC0:<IP address B>
stack = $ZTC1
The additional IP address may be written in IPv4 dotted octet form or in IPv6 form with sequences
of 4 hexadecimal digits separated by the : character. Do not specify IPv6 addresses unless the
additional TCPIP/IP process supports IPv6 and you have enabled OSM use of IPv6. See “Enabling
IPv6 Support” (page 32).
There is no point in specifying specific IP addresses in OSMCONF for the default IPv4 $ZTCP0
and $ZTCP1 TCP/IP processes, since only one address is available for each of these TCP/IP
processes.
Like any changes to OSM configuration defaults, these changes are most easily enabled if you
restart the affected OSM processes ($ZOSM and $ZCMOM, named $ZZKRN.#OSM-APPSRVR
and $ZZKRN.#OSM-CIMOM in SCF.)
In the OSMCONF file, the evtstack parameter applies to the OSM Event Viewer and its server
processes $ZOEV. The syntax for specifying only a specific IP address or addresses is the same
as for the stack flag:
evtstack = <TCPIP process name>:<IP address>
Restart $ZOEV ($ZZKRN.#OSM-OEV in SCF) for the evtstack change to take effect.
Configuring OSM to Monitor Devices Not on the Dedicated Service LAN
You can configure OSM to monitor a system device (storage router, UPS, maintenance switch,
Onboard Administrators, or CLIM) located outside of the dedicated service LAN ($ZTCP0/$ZTCP1)
by adding additional TCP/IP stacks to your OSMCONF file as follows:
MaintenanceStack = $ZTC00
MaintenanceStack = $ZTC01
To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15).
Optional OSM Configuration 19