HP 3000 Manuals HP 3000 Manuals
NMMGR Configuration Overview
The SNA node and link configuration is done by using NMMGR to create or
modify a configuration file. The file contains this information:
* SNA node information: used by SNA Transport to manage sessions
with the host.
* Link information: used for SDLC data link control and phone data
(for switched lines), X.25 link information, and token ring link
information.
The basic operation of NMMGR is described in Using the Node Management
Services Utilities (32022-61005); if you are not familiar with NMMGR, you
should read that manual before continuing. Note that you must have node
manager (NM) or network administrator (NA) capabilities to use NMMGR.
NOTE When configuring an SNA node and link, the configuration file can
be named anything you prefer. However, when you start the node and
link, it looks for a configuration file named NMCONFIG.PUB.SYS. For
example, you could have these configuration files:
XYZ.CONFIG.SYS
CONFIG1.FILES.SYS
FILE3.CONFIG.SYS
If you wanted to use FILE3.CONFIG.SYS when you started the SNA node
and link, you would have to rename or copy the file to
NMCONFIG.PUB.SYS before you started the node and link.
SNA Node Information
SNA node information is used by SNA Transport, which manages data
transmission for the SNA services by providing an interface to establish
LU-LU sessions with the host.
Before SNA Transport can allow the SNA services to establish sessions
between dependent LUs, SNA Transport must establish communication with
the host's System Services Control Point (SSCP). The SSCP manages the SNA
network functions on the host. It also manages SNA network functions on
the HP 3000, via the PU-SSCP session. For dependent LU sessions, the HP
3000 must establish a PU-SSCP session and LU-SSCP sessions. You do not
have to configure any information for the PU-SSCP or LU-SSCP sessions
because it is already set in the SNA Transport software.
For a session between independent LUs, an associated LU-SSCP session is
not required. This is the major difference between dependent LUs and
independent LUs.
For dependent LUs and independent LUs, you must provide information for
the LU-LU sessions. For each LU defined in SNA Transport, an LU must be
defined in the host's NCP/VTAM configuration. You must configure each LU
and establish a correspondence with an LU in the NCP/VTAM configuration.
You configure these items for an SNA node:
* Node identification. This information identifies the node to the
host and specifies the type of node (T2.0 or T2.1) being used.
* Link type. This information specifies whether you are configuring
an SDLC link, an X.25 link, or a token ring link.
* PU data. This information identifies the PU to the host.
* LUs. A list of up to 256 LUs can be configured for an SNA node.
Link Information
After you specify configuration information for the SNA node, you specify
information for the link.
For an SNA/SDLC link, you provide this information:
* Link data. This information includes the PSI physical path,
timeout values, transmission speed, and link station ID.
* Phone data. This information includes the phone number and
associated data for switched lines.
For an SNA/X.25 link, you provide this information:
* Link data. This information is about the Network Services (NS)
network interface and the type of virtual circuit to be used.
* Virtual circuit data. This information is specifically about the
permanent virtual circuit (PVC) or switched virtual circuit (SVC)
to be used.
For an SNA/Token Ring link, you provide this information:
* Link data. This information is about the name and location of the
token ring card, the MAC address of the remote system, the local
and remote service access points (SAPs), and MAC layer timeout and
retry values.
NOTE If you change the configuration for an SNA node or link while it is
running, the changes will not take effect until the node or link is
restarted.
Configuration File Validation
Validating the configuration file ensures that the configuration data is
logically and syntactically correct. Each SNA service's data is also
checked against the SNA node configuration data for correctness (for
example, correct LU names). See each service's Node Manager's Guide for
that service's validation error messages.
You should validate the configuration file after completing any of these
tasks:
* An initial configuration of one or more SNA nodes
* An initial configuration of one or more SNA services
* A modification of an existing configuration
The configuration file is validated through NMMGR; see Using the Node
Management Services Utilities (32022-61005).
Configuration File Critical Summary
The critical summary is a printout of the data in the configuration file.
It can be used to check current contents of the configuration
file--without opening the file--to determine whether the configuration is
correct. The critical summary is generated through NMMGR; see Using the
Node Management Services Utilities (32022-61005).
SNA/SDLC Data.
An example of a critical summary of SNA/SDLC node and link configuration
data is shown below.
CRITICAL SUMMARY - SNANODE CONFIGURATION
TUE, APR 20, 1993, 2:49 PM
CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS
Validated subsystem.
SNANODE NAME: IBMNODE
ID Blk: 023 ID Num: 12345 Max Data: 2057 Type: SDLC
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LUNAME01 1 LUNAME02 2 LUNAME03 3 LUNAME04
LUNAME05 LUNAME06 LUNAME07 7 LUNAME08
LUNAME09 9 LUNAME10 10 LUNAME11 LUNAME12
LUNAME13 LUNAME14 14 LUNAME15 15 LUNAME16 16
LINKDATA
Physical Path: 24
Phone Number: 9-DD-415-555-3216
Station ID: FE Receive Timeout: 180 Local Timeout: 30
Connect Timeout: 900 Error Retries: 7 Transmission Speed: 9600
NRZI: N Auto Dial: Y
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: IBMNODE2
ID Blk: 023 ID Num: 00001 Max Data: 265 Type: SDLC
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LUNAME01 1 LUNAME02 2 LUNAME03 3 LUNAME04 4
LINKDATA
Physical Path: 2/16
Phone Number:
Station ID: 01 Receive Timeout: 0 Local Timeout: 0
Connect Timeout: 0 Error Retries: 1 Transmission Speed: 1200
NRZI: N Auto Dial: N
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: IBMNODE5
ID Blk: *** ID Num: ***** Max Data: *** Type: ****
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
(No data configured for this node)
LINKDATA
Physical Path:
Phone Number:
Station ID: 01 Receive Timeout: 180 Local Timeout: 30
Connect Timeout: 900 Error Retries: 7 Transmission Speed: 9600
NRZI: N Auto Dial: N
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Some fields could not be found or printed.
SNA/X.25 Data.
An example of a critical summary of SNA/X.25 node and link configuration
data is shown below.
CRITICAL SUMMARY - SNANODE CONFIGURATION
TUE, APR 20, 1993, 4:04 PM
CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS
Validated subsystem.
SNANODE NAME: XSIMPVC
ID Blk: 023 ID Num: FFFF0 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU1 1
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 5
VC Type: PVC Call Direction: OUT
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: 10 Remote Address:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: XSIMOUT
ID Blk: 023 ID Num: FFFF1 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU1 1
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 5
VC Type: SVC Call Direction: OUT
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: Remote Address: 012345678901234
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: XSIMIN
ID Blk: 023 ID Num: FFFF2 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU1 1
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 5
VC Type: SVC Call Direction: IN
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: Remote Address: 012345678901234
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: PVC1
ID Blk: 023 ID Num: FFFF3 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU01 1 LU02 2 LU03 3 LU04 4
LU05 5 LU06 6 LU07 7 LU08 8
LU09 9 LU10 10 LU11 11 LU12 12
LU13 13 LU14 14 LU15 15 LU16 16
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 0
VC Type: PVC Call Direction: OUT
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: 1 Remote Address:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: SVCIN16
ID Blk: 023 ID Num: FFFF4 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU01 1 LU02 2 LU03 3 LU04 4
LU05 5 LU06 6 LU07 7 LU08 8
LU09 9 LU10 10 LU11 11 LU12 12
LU13 13 LU14 14 LU15 15 LU16 16
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 0
VC Type: SVC Call Direction: IN
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: Remote Address: 01
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: SVCOUT
ID Blk: 023 ID Num: FFFF5 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU01 1 LU02 2 LU03 3 LU04 4
LU05 5 LU06 6 LU07 7 LU08 8
LU09 9 LU10 10 LU11 11 LU12 12
LU13 13 LU14 14 LU15 15 LU16 16
X25LINK:
NS NI Name: X25NI Inactivity Timeout: 0
VC Type: SVC Call Direction: OUT
Max Call Retries: 3 Call Retry Delay: 600
PVC Number: Remote Address: 01
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SNANODE NAME: TEMP
ID Blk: 023 ID Num: FFFF6 Max Data: 265 Type: X.25
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
- - - - - - - - - - - - - - - - - - - - - - - -
LU01 1
X25LINK:
NS NI Name: ******** Inactivity Timeout: *****
VC Type: *** Call Direction: ***
Max Call Retries: *** Call Retry Delay: ***
PVC Number: **** Remote Address: ***************
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Some fields could not be found or printed.
SNA/Token Ring Data.
An example of a critical summary of SNA/Token Ring node and link
configuration is shown below.
CRITICAL SUMMARY - SNANODE CONFIGURATION
TUE, APR 20, 1993, 4:34 PM
CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS
Validated subsystem.
SNANODE NAME: TRN3745
ID Blk: 2 ID Num: DCA12 Max Data: 017 Type: TOKEN
Node Type: 2.1 Node 2.1 Dependent LU Support: Y
LU Name LU# LU Name LU# LU Name LU# LU Name LU#
-------- --- -------- --- -------- --- -------- ---
LU02 2 LU03 3
TOKEN Link:
Remote DSAP: 04 Retry Limit: 10
Local SSAP: 04 Acknowledgment Timer: 10
Unacknowledged Send Limit: 2 Error Timer: 100
Remote Station Address: 40-00-13-74-51-01
LINK NAME: TOKENLNK TYPE: TOKEN
Physical Path: 44
Buffer Size: 4096
Factory Configured address: Y
Local station address: FF-FF-FF-FF-FF-FF
-------------------------------------------------------------------------------
Some optional or required fields are not configured.