Once you have opened the configuration file, you are placed at the NMMGR
"Main" screen.
Main Screen
From the "Main" screen shown in Figure 2-1
"Main Screen", you can select the category of network subsystems
you want to configure.
Figure 2-1 Main Screen
To access the NMMGR branch for configuring an SNA node and link, press
[f4] (IBM). This places you at
Figure 2-2 "HP-IBM Configuration Screen".
HP-IBM Configuration Screen
From Figure 2-2 "HP-IBM Configuration Screen"
you can select the item you want to configure.
Figure 2-2 HP-IBM Configuration Screen
To select SNA node and link configuration, press [f2] (Go To SNANODE).
SNA Node Configuration Screen
After you have selected SNA node and link configuration, NMMGR displays
the "SNA Node Configuration" screen, shown in
Figure 2-3 "SNA Node Configuration Screen".
(You can go directly to this screen from any screen by typing @SNANODE
in the command window and pressing [ENTER].) Here you specify
information about the new SNA node
you are configuring or the existing node you are modifying.
Figure 2-3 SNA Node Configuration Screen
Fields
Path
For display only. The NMMGR branch you are in.
SNA Node Name
The name of the new SNA node you are configuring or the existing node
whose configuration you are modifying. The name can be up to eight
alphanumeric characters long; the first character must be alphabetic.
SNA/X.25 (SVC): For troubleshooting purposes, we recommend that
the PUNAME operand of the PU macro in the VTAM
switched major node match this field, refer to
Table 2-3 "Host Macro Values for
X.25 Link SVC".
SNA/Token Ring: For troubleshooting purposes, we recommend that
the PUNAME operand of the PU macro in the VTAM
switched major node match this field, refer to
Table 2-7 "Host Macro Values for
Token Ring".
New Name
The new name of an existing SNA node. The name can be up to eight
alphanumeric characters long, the first character must be alphabetic.
SNA/X.25 (SVC): For troubleshooting purposes, we recommend that
the PUNAME operand of the PU macro in the VTAM
switched major node match this field, refer to
Table 2-3 "Host Macro Values for
X.25 Link SVC".
SNA/Token Ring: For troubleshooting purposes, we recommend that
the PUNAME operand of the PU macro in the VTAM
switched major node match this field, refer to
Table 2-7 "Host Macro Values for
Token Ring".
Once you have entered the new name, press [f4] (Rename),
the node is then renamed.
Configured SNA Nodes
For display only. The names of the SNA nodes that have been configured.
You can configure a maximum 36 nodes in a configuration file. Note that a
maximum eight nodes can be active at a time; however, to make this
possible, a multi-drop line must be used.
File
For display only. The name of the configuration file.
Once you have entered the name of the node, press [f5]
(Add) if this is a new node, or press [f6]
(Modify) if you are modifying an existing node. This places you
at Figure 2-3 "SNA Node Configuration
Screen"
PU Data Screen
After you have selected a node, NMMGR displays
Figure 2-4 "PU Data Screen" (You can go
directly to this screen from any screen by typing
@SNANODE.nodename in the command window and pressing
[ENTER].) Here you enter information that identifies the PU to
the host. If you are configuring a new node, you must enter all
of the information.
Figure 2-4 PU Data Screen
Fields
Path
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
Link Type
Required. The type of communications link the node is being
configured for.
Values: SDLC, X.25, TOKEN, or SDLCMUX.
Default: SDLC
Node Type
Required. The type of node being configured. If you are
configuring a T2.0 node, enter 2.0. If you are configuring a
T2.1 node, enter 2.1.
If you are configuring a node for SNA/X.25 Link, you must
enter 2.0 in this field.
If you are configuring a node for SNA/Token Ring Link, enter 2.1
in this field.
Values: 2.0 and 2.1
Default: 2.0
Host Configuration:
SNA/SDLCMUX: the PUTYPE operand of the PU
macro must be set to 2.1 and dependent LU should be
Y.
SNA/SDLC (dependent LU): The PUTYPE operand of the
PU macro must be set to 2, and the XID
operand of the same PU macro must be set to NO
or not specified at all.
SNA/SDLC (independent LU): The PUTYPE operand of the
PU macro must be set to 2, and the XID
operand of the same PU macro must be set to
YES.
SNA/Token Ring (dependent and independent LUs): The
PUTYPE operand of the PU macro must be set to
2, and the XID operand of the same PU
macro must be set to YES.
Node 2.1 Dependent LU Support
If you entered 2.0 in the Node Type field, this
field must be blank. If you entered 2.1 in the
Node Type field and one or more dependent LUs are configured,
enter Y. If you entered 2.1 in the Node Type
field and no dependent LUs are configured, enter N.
Default: Blank (the node is T2.0)
Physical Unit Data
Information about the Physical Unit (PU).
MAX DATA
Required. The maximum size, in bytes, of the transmission
buffers (frames) used to hold data for the SDLC connection, the X.25
QLLC connection, or token ring connection.
Range: 137-2057 (integer)
Default: 265
Host Configuration:
SNA/SDLCMUX: The MAXDATA operand of the PU
macro must match this field.
Required. Three hexadecimal digits which, together with
ID NUM (see below), form the exchange identifier used with
exchange identification (XID) requests. This composite identifier
must be unique within the SNA network.
NOTE: For communication with an IBM host, this parameter
(ID BLK) is ignored for nonswitched lines. For communication
with an IBM AS/400, this parameter is required for both switched
and nonswitched lines.
Range: 001-FFE (hexadecimal)
Default: 023 (ID BLK sent by the IBM 8100)
Host Configuration:
SNA/SDLCMUX: The IDBLK operand of the PU
macro must match this field.
Five hexadecimal digits that are appended to ID BLK
(see above) to form the exchange identifier used with exchange
identification (XID) requests. This composite identifier must be
unique within the SNA network.
NOTE: For communication with an IBM host, this parameter
(ID NUM) is ignored for nonswitched lines. For communication
with an IBM AS/400, this parameter is required for both switched
and nonswitched lines.
(Token Ring only) Required for APPC over Token Ring Link. The name
by which the HP e3000 node is known to the remote system.
Host Configuration: HP recommends that you use the PU name (the SNA
Node Name field in the SNA Node Configuration screen) in this field.
AS/400 Configuration: For APPN, the RMTCPNAME in the APPC
display controller description must match this field, refer to
Table 2-10 "AS/400 Parameter Values
for Token Ring Link". Otherwise, HP recommends that you use the
PU name (the SNA Node Name field in the SNA Node Configuration screen)
in this field.
File
For display only. The name of the configuration file.
Once you have entered all of the PU information, press [f6]
(Save Data).
After the information is saved, if you need to configure LU
information, press [f2] (Go To LUDATA); this places
you at Figure 2-5 "LU Data Screen"
If you do not need to configure LU information or link information,
press [f8] (Prior Screen) until you get to the screen
you need next.
LU Data Screen
Once you have specified the PU information, you are ready to specify LU
information. Refer to Figure 2-5 "LU Data
Screen" Select this screen by pressing [f2] (Go To LUDATA)
on Figure 2-4 "PU Data Screen" (You can go
directly to this screen from any screen by typing
@SNANODE.nodename.LUDATA in the command window and pressing
[ENTER].)
Figure 2-5 LU Data Screen
Fields
Path
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
Logical Unit Data
Information about the LUs to be configured for this node. You can
configure a maximum 256 LUs for each node.
LU Name
The remote system name (not the Network
Addressable Unit [NAU] number) of the LU. The name can be up to
eight alphanumeric characters long; the first character must be
alphabetic. Note that at least oneLU Name
must be specified.
SNA/X.25 (SVC): For troubleshooting purposes, we recommend
that the LUNAME operand of the LU
macro in the VTAM switched major node match this field, refer
to Table 2-3 "Host Macro
Values for X.25 Link SVC".
SNA/Token Ring: For troubleshooting purposes, we recommend
that the LUNAME operand of the LU
macro in the VTAM switched major node match this field, refer
to Table 2-7 "Host Macro
Values for Token Ring".
LU#
The LU (NAU) number. Note that for an independent LU this field
must be blank.
For display only. The name of the configuration file.
Note that you can enter LU information on up to eight pages of this
screen. Each page contains 32 LU Name and LU # fields
You do not have to fill all of the fields on a page before pressing
[f1] (Next Page), [f2] (Prev Page),
[f3] (First Page), or [f4] (Last Page) to
display another page of the screen for entering information. That is,
partially filled pages are allowed.
Once you have entered information for all of the LUs, do one of these two
things:
Press [f5] (Sort & Condense) to sort the
information from all pages of this screen by
LU Name. The sorted information is condensed into full
pages. Note that this takes approximately as much time as validation
of the configuration file. After the information is processed,
press [f6] (Save Data).
Press [f6] (Save Data). The information remains
in the order it was entered on the pages of the screen, and any
partially filled pages remain partially filled.
If you do not need to configure link information, press [f8]
(Prior Screen) until you get to the screen you need next.
SDLCMUX Link Data Screen
Once you have specified the PU and LU information, you are ready to configure
the communications link parameters for the SDLCMUX link. Select this screen by
pressing [f1] (Go To LINKDATA) as shown in
Figure 2-4 "PU Data Screen" You get the
screen shown in Figure 2-6 "SDLCMUX Link Data
Screen"Figure 2-6 SDLCMUX Link Data Screen
Fields
Path
Required. The Path field is the current physical path for the
adapter card as specified in the NMCONFIG configuration file.
Note: On PCI SDLCMUX links, the physical path generally has more
components and is a "longer" path (e.g., 0/6/0/1.2, which includes the
port number 2) along with the port number associated with that link. The
output for PCI links is different from HP-PB.
Modem type
Required. V.25bis is a ITU-T specification for a modem command
language and overall modem behavior. It includes both asynchronous and
synchronous command interfaces.
Hayes is the dialing standard for asynchronous modems. Hayes includes
V.25bis in its ULTRA modems to support synchronous out-dial facilities of
host computers and to support the evolution of synchronous communications
software on PCs.
Station ID
Required. This defines the HP e3000's link station identifier
to the remote system's communications controller.
Required. The Receive timeout field is the current value of the
T1 timer. The T1 timer waits the specified number of hundredths-of-seconds
for a particular frame to be acknowledged. A frame that is transmitted,
but not acknowledged, before the T1 timer expires, is
retransmitted.
Range: 1-63 seconds
Speed
Required. The Transmission Speed field displays the current
transfer rate, or clocking, configured for the node in the NMMGR Link
screen. If modems are used, the modems will control the clocking. The ACC
card transmits at the clocking setting of the modem and ignores the value
configured in this field.
Range: 1200-2048000 bps
Number of retries N2
Required. The N2 field is the maximum number of times a frame
is retransmitted after the SDLC Parm T1 expires. The frame is
retransmitted at the SDLC Parm T1 interval for the number of
times specified in this field. When this count is depleted, the frame is
retransmitted at T1 second intervals. If no response is received
after these transmissions, the link is brought down.
A node that is configured with the value specified in SDLC Configuration
Parameters output will attempt to retransmit an unacknowledged frame a
maximum of 15 times at T1 intervals.
Range: (1-15)
Physical interface
Required. The Physical Interface field displays the cable type
that is currently connected to the PSI card, This data is to be
configured through NMMGR. The possible values are:
0 = RS-232
1 = V.35
Transmit window size
Required. The Transmit Window size (K field) is the configured
number of unacknowledged frames that are allowed in the network at any
given time. For example, if this value is set to seven (7) for a node,
and that node transmits seven (7) packet frames onto the network, it
cannot transmit another frame until one or more of the transmitted frames
are acknowledged.
Range: 1-7
Connect timeout
Required. The Connect Timeout is the current logical link
level 2 connection timeout. The Connect Timeout parameter sets the amount
of time a node will wait for a logical connection to a remote node to be
established. If this timer expires, the node aborts the connection
attempt. The abort process can take several additional seconds.
Range: 5-900 seconds
Clock source
Required. The Clock source field defines the clocking mode. The
possible types of clocking source are:
0 = internal
1 = external)
Adapter timeout
Required. The Adapter Timeout is the value specified for the
Adapter timer. This timer, also called a heartbeat timer, is used to
monitor whether the system and/or
the ACC card are functioning. The ACC card, and the system, transmit
a signal, called a heartbeat signal, to each other on a specified
schedule. If for example, the heartbeat does not arrive at the ACC
card from the system (or vice-versa), the card or system waits the
number of seconds specified by this field. If no heartbeat arrives
before this timer expires, the link is dropped. You can determine
whether the ACC card or the system failed by checking to see which
device is still active. The default for this field is 60 seconds
and it is recommended that you do not change the value of this field.
Range: 5-900 seconds or 0
Auto hangup timer
Required. Intended primarily
for use with certain European public telephone systems. If set,
the driver will periodically attempt to hang up the local modem phone
line, then resume awaiting a connection. This recovers from situations
in which a human or incompatible modem accidentally dialed in during
the time period, but the local modem failed to hang up on its own
after failing to establish a connection. If a connection is successfully
established, the timer is cancelled. When zero, the feature is disabled.
Default: 0
Range: 5-900 seconds
Data encoding
Required. Enter 1 to enable the Non Return to Zero Inverted
(NRZI) feature; 0 to disable it.
Host Configuration: The NRZI operand of the LINE macro must
match this field.
Default: 0
Trace at startup
Yes or No
Trace file
If Y (yes) to Trace at startup, specify the trace file name.
Autodial
Yes or No
Phone number
The number you want the link to dial into.
SDLC Link Data Screen
Once you have specified the PU and LU information, you are
ready to configure the communications link parameters and the phone
data for the SDLC link. You do this on the screen shown in
Figure 2-7 "SDLC Link Data Screen" Select
this screen by pressing [f1] (Go To LINKDATA) on the screen
shown in Figure 2-4 "PU Data Screen" (You
can go directly to this screen from any screen by typing
@SNANODE.nodename.LINKDATA in the command window and pressing
[ENTER]).
Figure 2-7 SDLC Link Data Screen
Fields
Path
For display only. The NMMGR path to this screen.
It includes the name of the SNA node you are configuring.
Physical Path
Required. The address of
the PSI. At system start-up time, this address is assigned according
to the slot the PSI is in. The value you enter here is determined
by one of these formulas:
If only one card cage is present:
4 X SlotNumber
where (a) X is the multiplication sign (not
the character "X"), and (b) SlotNumber is the number
of the slot the PSI is in.
If the PSI is in slot 6, the Physical Path is 24
(4 multiplied by 6).
Example:
If two card cages are present:
PathNumber/(4 X SlotNumber)
where (a) PathNumber is a number corresponding to
the card cage the PSI is in:
Card cage 0: PathNumber = 2 Card cage 1:
PathNumber = 6
(b) / is the slash character (not the
division sign), (c) the parentheses are used to set off the
arithmetic formula (they are not entered as part of
the Physical Path value), (d) X is the
multiplication sign (not the character "X"), and (e)
SlotNumber is the number of the slot, within the
card cage, the PSI is in.
Examples:
If the PSI is in card cage 0, slot number 4, the
Physical Path is
2/16
(PathNumber, slash character, 4 multiplied by 4).
If the PSI is in card cage 1, slot number 3, the
Physical Path is
6/12
(PathNumber, slash character, 4 multiplied by 3).
Receive Timeout
Required. The number of seconds the SDLC link driver will wait
for the remote system poll before closing the line. If 0 is
specified, no timeout occurs.
Range: 0, 30-1800 (integer)
Recommended value: 180 (30 in Europe)
Default: 180
Local Timeout
Required. The number of seconds the SDLC link driver waits for
PSI card activity, before informing SNA Transport that the PSI is down
and the link driver is going down.
Note that the PSI card waits 20 seconds longer (than the value specified
here) for SDLC link driver activity before bringing down the link and
reporting a failure. This avoids unnecessary use of dial-up lines, which
avoids excessive phone charges. (Note that since no driver activity is
taking place, the driver probably will not receive the failure notice.)
If 0 is specified, no timeout occurs.
Range: 0, 30-900 (integer)
Recommended value: 30
Default: 30
Connect Timeout
Required. The number of seconds the SDLC link driver will wait
for a link Set Normal Response Mode (SNRM) command after telling the PSI
to enable the Data Terminal Ready (DTR) signal, before closing the line.
This includes time waiting for either the autodialer or the operator to
dial the remote phone number. If 0 is specified, no timeout
occurs.
If you are using a manual-dial modem, we recommend that you specify
either 0 (no timeout) or 900 (the maximum wait). You
can begin to dial after this logging message is displayed on the console
after issuing SNACONTROL START:
Node NodeName ready for activation by host
Note that if you are using a manual-dial modem, console logging must be
enabled for SNA Transport logging class CLAS0013, so that the
above message can be displayed (see Chapter 3
"Logging Configuration")
Range: 0, 30-900 (integer)
Default: 900
Number of Error Retries
Required. The maximum number of times the SDLC link manager
will retry after errors or timeouts before setting the line to idle.
Range: 1-999 (integer)
Default: 7
Transmission Speed
Required. The line transmission speed (bits per second). This
value is overridden by the modem, if one is used. For direct-connect, the
speed must be supported by the cable.
Required. Enter Y only if you are using an auto-dial
modem and you want the modem to dial at link startup time; N if
a leased line, a manual-dial modem, or no modem is used, or if you are
using an auto-dial modem but you want to defer dialing until the
SNACONTROL AUTODIAL command is issued (refer to
Chapter 6 "MPE Commands")
Default: N
Phone Number
The number you want the link to dial into. Note that you specify this
field only if you are using an auto-dial modem.
Allowable Characters:
Any of the 12 phone characters:
0 1 2 3 4 5 6 7 8 9 * #
- = A spacing character, used for readability
purposes.
D = Pause for three seconds.
E = The end of the phone number. This character might
be required by the modem; check your modem manual for details. Do
not use this unless you know the modem/auto-call unit (ACU)
requires it.
/ = Wait for a second dial tone. When the modem
encounters this character, it waits for another dial tone. This can
be used when an outside line must be accessed before the actual
phone number is dialed.
NOTE: Only 34 characters can be entered. So, if you have more than one
access number to dial, you might not be able to use the dash (-) spacing character.
Example:
Suppose this is typed in the Phone Number field:
9-DD-415-555-3216
9 is an access number to an outside line.
DD means to pause six seconds before dialing the next
set of numbers.
4155553216 is the number you want to dial, where
415 is the area code and 5553216 is the specific
number.
The dashes are used for readability.
File
For display only. The name of the configuration file.
Once you have entered the SDLC link information, press [f6]
(Save Data).
After the information is saved, press [f8] (Prior Screen)
until you get to the screen you need next.
X.25 Link Data Screen
Once you have specified the PU and LU information, you are ready to configure
the communications link parameters and virtual circuit data for the X.25 link.
You do this on the screen shown in Figure 2-8
"X.25 Link Data Screen" Select this screen by pressing [f1]
(Go To LINKDATA) on the screen shown in
Figure 2-4 "PU Data Screen" (You
can go directly to this screen from any screen by typing
@SNANODE.nodename.X25LINK in the command window and pressing
[ENTER].)
Figure 2-8 X.25 Link Data Screen
Fields
Path:
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
NS Network Interface Name
Required. The NS network
interface that the X.25 link will use. The name can be up to eight
alphanumeric characters long; the first character must be alphabetic. See
the appropriate NS documentation for more information.
X.25 System Access Configuration: An NI name in the Configured
Network Interfaces field of the "Network Interface Configuration"
screen must match this field.
Inactivity Timeout
Required. The number of minutes
that the QLLC module will wait between incoming packets. The timer is
reset each time a packet is received. If the specified number of
minutes elapses before the next packet arrives, the virtual circuit
is cleared and then released. For an incoming SVC, this results
in a recoverable link failure. If 0 is specified, the timer is
disabled. This can result
in an indefinite period of inactivity; however, note that it might
be desirable to disable the timer for permanent virtual circuits (PVCs).
Range: 0-32767 (integer)
Default: 0
Virtual Circuit Type
Required. The type of virtual
circuit to be used to connect to the host: permanent virtual circuit
(PVC) or switched virtual circuit (SVC). The X.25 network subscription
information and the host NPSI configuration should be used to determine
the type of virtual circuits that are available for this connection.
If you specify PVC, you must also specify the PVC Number
field (see below).
If you specify SVC, you must also specify the Remote's X.25
Network Address and Call Direction fields (both fields are
described later in this chapter).
Information about the permanent virtual circuit (PVC).
PVC Number
Conditionally required. The number identifying the permanent virtual
circuit that will connect the HP e3000 node to
the remote system. This is found in the X.25 network subscription
information, and is equivalent to the Logical Channel Number (LCN).
This field is required only if PVC is entered
for the Virtual Circuit Type field.
Range: 0-4095 (integer)
X.25 System Access Configuration: If you configured a specific address key
for the SNA/X.25 PVC (in the PVC Number field of the "X.25 PVC
Address Key Paths" screen), that address key must match the value
specified in this field, refer to
Figure 2-9 "PVC Configuration
Dependencies".
DTC Manager Configuration: The range specified for the LCI Range
field (for PVCs) of the "DTC Manager DTCX25 Board # Level 3" screen must
contain the value specified in this field.
DTS Configuration: The range specified for the LCI Range field
(for PVCs) of the "DTS X.25 Card Config — Level 3 &Miscellaneous"
screen must contain the value specified in this field.
SVC DATA
Information about the switched virtual circuit (SVC).
Remote's X.25 Network Address
Conditionally required. The X.25 network address of the remote system.
This is found in the X.25 network subscription information.
This field is required only if SVC is entered for
the Virtual Circuit Type field.
Host Configuration: If the host is configured to make outgoing calls, the
DIALNO operand value of the PATH macro that defines the
dial-out path to the HP e3000 node must contain the value specified in
this field, refer to Table 2-3 "Host
Macro Values for X.25 Link SVC". For security purposes, SNA/X.25 Link
compares the remote X.25 address contained in incoming calls with the
value specified in this field. See the HP SNA Products Remote
System Configuration Guide for more information about
host configuration. Also, the features and names of the facility
sets are found in the X.25 network subscription information.
Note that the facility set (the set of virtual circuit features
and security attributes associated with the SVC) configured on the
remote system must also be configured for the NS X.25 system link.
X.25 System Access Configuration: The facility set that the SNA/X.25 SVC
will use must be configured for the NS X.25 system link. If you followed
our recommendation and reserved the facility set for the SNA/X.25 SVC,
the X.25 Address you specified in the "X.25 SVC Address Key
Paths" screen must be the same as the address you specify in this field,
refer to Figure 2-10 "SVC Configuration
Dependencies".
Call Direction
Conditionally required. Enter IN if the HP e3000 will wait
for the remote system to request a connection (incoming direction);
OUT if the HP e3000 will initiate the connection (outgoing
direction).
If you specify OUT, you might need to specify the Maximum
Call Retries and Call Retry Delay fields. These fields are
described below.
This field is required only if SVC is entered
for the Virtual Circuit Type field.
NOTE: Only one incoming SVC is supported per system.
Values: IN and OUT
Recommended value: OUT
Default: OUT
Host Configuration:
If you are configuring an outgoing SVC, at least one
X25.LINE host macro must specify CALL=IN and you
must enter OUT in this field.
If you are configuring an incoming SVC, at least one
X25.LINE host macro must specify CALL=OUT and you
must enter IN in this field.
If CALL=INOUT is specified in at least one
X25.LINE host macro, eitherIN or
OUT can be specified in this field.
Maximum Call Retries
Conditionally required. The maximum number of times the QLLC module
will try to connect to the remote system without success. If 0
is specified, the QLLC module will not retry if the first attempt to
connect fails.
This field is required only if SVC is entered
for the Virtual Circuit Type field.
If you specify a value greater than 0, you must also specify the
Call Retry Delay field.
Note that this field is valid only when OUT is specified for the
Call Direction field.
Range: 0-999 (integer)
Default: 3
Call Retry Delay
Conditionally required. The number of seconds the QLLC module waits
between attempts to connect to the remote system.
This field is required only if a value greater than
0 is specified for the Maximum Call Retries field.
Note that this field is valid only when OUT is specified for the
Call Direction field (described earlier in this chapter).
Range: 60-999 (integer)
Default: 60
File:
For display only. The name of the configuration file.
Once you have entered the X.25 link information, press [f6]
(Save Data).
After the information is saved, press [f8] (Prior Screen)
until you get to the screen you need next.
Before Using the X.25 Link Data Screen
The PVC or SVC that SNA/X.25 Link is going to use must have
already been defined in the X.25 System Access configuration and
the DTC Manager configuration or the DTS configuration. Before configuring
the X.25 link parameters and virtual circuit data on the screen
shown in Figure 2-8 "X.25 Link Data Screen"
the following tasks must be performed.
For an SNA/X.25 PVC:
Configured a logical channel identifier (LCI) range in the DTC
Manager configuration or the DTS configuration. The
PVC Number you specify on the screen shown in
Figure 2-8 "X.25 Link Data Screen"
the screen must be within the LCI range you configured.
Configured a network interface (NI) for the SNA/X.25 PVC in the
X.25 System Access configuration. The value you specify for NS
Network Interface Name on the screen shown in
Figure 2-8 "X.25 Link Data Screen"
must match the NI name you configured.
Configured an address key for the SNA/X.25 PVC in the X.25 System
Access network interface configuration, if you want to reserve the
PVC for only SNA/X.25's use.
For an SNA/X.25 SVC:
Configured a network interface (NI) for the SNA/X.25 SVC in the
X.25 System Access configuration. The value you specify for NS
Network Interface Name on the screen shown in
Figure 2-8 "X.25 Link Data Screen"
matches the NI name you configured.
Configured a facility set in the network interface with the same
parameters as the facility set on the host. The HP e3000 facility set
can be configured for the SNA/X.25's SVC use only, or for use by any
SVC. We recommend that you configure the facility for only SNA/X.25's
use, because that ensures that SNA/X.25 receives only incoming calls
intended for it.
Data Required from the NS Configurations
Certain items from the X.25 System Access configuration and the DTC Manager
configuration or the DTS configuration must match or be compatible with items
in the SNA/X.25 configuration. Listed below are the X.25 System Access
configuration screens and DTC Manager configuration or DTS configuration
screens that contain those items.
For an SNA/X.25 PVC:
"DTC Manager DTCX25 Board # Level 3" screen or "DTS DTC X.25 Card
Config — Level 3 &Miscellaneous" screen: The PVC
LCI Range must include the PVC number specified for
PVC Number on the screen shown in
Figure 2-8 "X.25 Link Data
Screen"
"Network Interface Configuration" screen: The Configured
Network Interfaces list must include the NI name specified for
NS Network Interface Name on the screen shown in
Figure 2-8 "X.25 Link Data
Screen"
"X.25 PVC Address Key Paths" screen: If you want to reserve an
X.25 address key for the SNA/X.25 PVC's use only, the
PVC Number must match the PVC Number specified on
the screen shown in Figure 2-8
"X.25 Link Data Screen"
"Network Interface Configuration" screen: The Configured
Network Interfaces list must include the NI name specified for
NS Network Interface Name on the screen shown in
Figure 2-8 "X.25 Link Data
Screen".
"X.25 SVC Address Key Paths" screen: The name of the facility set
configured for the SVC must be found on this screen, even though it
is not actually used in the SNA/X.25 configuration.
If you reserve the facility set for the SNA/X.25 SVC's use
only, the X.25 Address you specify for the facility
set on this screen must match the address you specify for
Remote's X.25 Network Address on the screen shown in
Figure 2-8 "X.25 Link Data
Screen" Note that this address is the remote system's
address. Also, the security specification in the "X.25 SVC
Address Key Paths" screen must be compatible with the
Call Direction specified on the screen shown in
Figure 2-8 "X.25 Link Data
Screen"
If you do not reserve the facility set for SNA/X.25's use,
by associating it with the remote system's address, you must
configure it as the POOL facility set. You do this by specifying
the facility set as the default facility set for the POOL X.25
address key. Also, the security specification in the "X.25 SVC
Address Key Paths" screen must be compatible with the
Call Direction specified on the screen shown in
Figure 2-8 "X.25 Link Data
Screen"
Once you have specified the PU and LU information, you are ready to configure
the communications link parameters for the Token Ring Link. You do this on the
screen shown in Figure 2-11 "Token Ring Link
Data Screen" Select this screen by pressing [f1] (Go To
LINKDATA) on the screen shown in Figure 2-4
"PU Data Screen" (You can go directly to this screen from any screen by
typing @SNANODE.nodename.LINKDATA in the command window and
pressing [ENTER]).
CAUTION: If the Token Ring 3000/iX Network Link product is
already configured for the Network Services (NS) subsystem, the
values that initially appear in the Token Ring Link Data screen
fields reflect the NS configuration. If the same Token Ring Card
is being used for both NS and SNA communications, certain fields
in the Token Ring Link Data screen must match the values of the
NS Token Ring Link configuration. (See the following field descriptions.)
If the Link Name configured for an SNA Token Ring Link is the same
as the name of an NS Token Ring Link, make sure that the values
of these fields in the SNA Token Ring Link configuration match the
NS Token Ring Link configuration; otherwise, the SNA Token Ring
Link configuration will change the NS Token Ring Link configuration.
If more than one Token Ring Link is configured for NS, the values
of the first configured Token Ring Link appear.
Figure 2-11 Token Ring Link Data Screen
Fields
Path:
For display only. The NMMGR path to this screen. It includes the name
of the SNA node you are configuring.
Link Name
Required. The symbolic name of the Token Ring Card. The name
must start with an alphabetical character.
NOTE: If the same token ring card is being used for both NS and SNA
communications, you must use the same name in this field as is configured for
the NS link.
Physical Path of Device Adapter
Required. The address of the Token Ring Card. At system
start-up time, this address is assigned according to the slot in which
the Token Ring Card resides.
hr style="margin:0">
NOTE: If the same token ring card is being used for both NS
and SNA communications, you must use the same value for this field
as is configured for the NS link.
Remote DSAP
Required. The Service Access Point (SAP) for the remote system.
This is a two-digit hexadecimal number that is a multiple of 4.
Host Configuration: For a 3745 remote system, the IDNUM and
IDBLK values in the PU macro must also match the
ID NUM and ID BLK fields shown in
Figure 2-4 "PU Data Screen" on the
HP e3000. For a 3174 or 3745 remote system, HP recommends that the value
of this field be 04. While other values may work, a value of 04
has been verified to work.
Required. The SAP for the HP e3000 node. This is a two-digit
hexadecimal number that is a multiple of 4. Each active node on an
HP e3000 system must have a unique SAP.
NOTE: A Service Access Point (SAP) pair identifies a MAC type
2 connection. This pair consists of two SAPs: the destination SAP
(DSAP) and the local SAP (LSAP). DSAP is the SAP of the remote computer
and LSAP is the SAP of the local computer. The SAP pair, along with
the remote and local station address, uniquely identifies a logical
connection in the Token Ring network.
Unacknowledged Send Limit
Required. The maximum number of frames that a MAC type 2
connection expects to receive before sending an acknowledgment.
Range: 1-127 (integer)
Default: 2
Retry Limit
Required. The maximum number of times a MAC type 2 connection
retransmits a frame before dropping the connection.
Range: 1-254 (integer)
Default: 10
Acknowledgment Timer
Required. The maximum time, in tenths of a second, that the MAC
type 2 connection waits before determining that a frame has been dropped
and retransmitting.
Range: 1-254 (integer)
Default: 10 (1 second)
Error Timer
Required. The amount of time, in tenths of a second, that the
MAC type 2 connection waits before initiating a Poll/Find (P/F) cycle.
Enter Y to use the factory-configured local station address.
Enter N to use the address to be entered in the Local
Station Address field. In most IBM environments, the local station
address is assigned by the IBM system manager. This is necessary since
connection establishment requires knowledge of remote addresses.
NOTE: If the same Token Ring Card is being used for both NS
and SNA communications, you must specify the local station address
that is configured for the NS Token Ring Link.
Local Station Address
Required (if N is specified in the Use
Factory-Configured Local Station Address field.) For non-AS/400
communications, HP recommends that you use either the factory-configured
address (enter Y in the Use Factory-Configured Local Station
Address field) or use local station address for the NS Token Ring
Link, if it is configured.
NOTE: If the same Token Ring Card is being used for both NS
and SNA communications, you must use the local station address that
is configured for the NS Token Ring Link.
File:
For display only. The name of the configuration file.