Technical data

nn is the number in minutes before an idle event viewer session is deleted and cannot be accessed
again. This parameter has the same value options as the
EvtMgr_Session_Expiration_Time parameter. However, as noted above, it must be
set higher than the expiration parameter in order to have the ability to log on again to an
expired session before it is deleted permanently.
NOTE: In the absence of either of these parameters in an OSMCONF file for OSM version T0682
H02 ABP and later, the default value for that particular parameter (session expiration and/or
session deletion) will be in effect.
To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15).
Configuring OSM in a Network Address Translation (NAT) Environment
Network Address Translation (NAT) is a technology that allows small networks to contain
internal-only addresses that need only be unique inside of a sub-network, and translate them to
externalized addresses that are unique for a larger network, usually the public Internet. With T0682
H02 ABR and later, OSM can be configured to be compatible in an NAT environment.
While NAT automatically translates addresses back and forth in some situations, the nature of
OSM connectivity is such that it knows only the private (internal) network addresses and requires
that OSM be provided with the external addresses. This is done through the OSMCONF file, as
described in “Specifying Externalized OSM Addresses for NAT”.
Specifying Externalized OSM Addresses for NAT
To connect to a NonStop server in an NAT environment, the OSM Service Connection must be
provided with its external addresses. These external addresses must be specified in your OSMCONF
file as follows:
url = <protocol>://<first IP address or DNS name>:<port>
url = <protocol>://<second IP address or DNS name>:<port>
<etc.>
Rules:
• The URL must contain either a valid IP address or fully-qualified DNS name for the server.
• The only valid protocols are “http” and “https” and it must be in synch with the “UseSSL”
OSMCONF setting. If the UseSSL parameter is set to "On," then the protocol setting must be
“https.”
• A port number must be specified; the default port of 80 for "http" is almost certainly incorrect.
The ports are normally 5988 for http and 5989 for https, but may vary depending on your
NAT configuration.
• Each address must be confined within a 79 character limit.
To make changes to your OSMCONF file take effect, see “Creating and Using an OSMCONF
File” (page 15).
NOTE: The initial addresses are ordinarily provided by querying SCF for addresses corresponding
to the stacks specified either by the default setting ($ZTC0 and $ZTC1) or the stacks specified in
OSMCONF via the “stack” setting. For more information, see “Configuring Additional TCP/IP
Processes for OSM Connectivity”).
Known Issue: When using a NAT environment, there is an issue with external links provided within
the OSM Service Connection. The Tools menu option (on the OSM menu bar) to launch the OSM
Event Viewer will fail, as will OSM Service Connection actions to launch web-based management
applications such as iLOs, Onboard Administrators, and web interfaces for Maintenance Switch,
UPS, Alarm Panel, and Fibre Channel Router objects.
28 OSM Server-Based Components