Configuring and Managing Host-Based X.25 Links - Edition 6 (36939-90057)
Configuring DTCs Step-by-Step
Modify the Network Management Configuration File
Chapter 3
94
Note that with certain networks (such as Transpac, in France) the called address is
removed from incoming call packets and the calling address is added to outgoing call
packets by the network. For these networks, enter only the subaddress in this field,
not the full X.25 address.
5. Repeat Steps 1 to 4 for each local HP e3000 Series 900 system that will be allowed to
establish a system-to-system connection with remote systems. If you need to enter
more than eight local system entries, press the
[Save Data]
key to save the data on
this screen, then use the
[Next Page]
key to move to a new data entry screen to
configure additional systems.
Fields The following table provides additional information on the fields on this screen.
DTC name Display only.
Card Number Display only
System Node Names This is the NS node name as configured as NODENAME in
NMCONFIG.PUB.SYS on the system where you wish to allow connections.
The format of the nodename is nodename.domain.organization.
X.25 link name The name of the link that will be used by the system being configured
for X.25 system-to-system connections. Must be the same as the link
name entered during NS configuration of X.25 iX System Access using
the NS subbranch of NMMGR. The link name can be up to eight
alphanumeric characters, beginning with a letter.
Max SVC The number of switched virtual circuits (SVCs) that will be allowed
through this DTC/X.25 Network Access card.
DTC Type Max Conn Per
X.25 Board
DTC 16 32
DTC48 256
DTC 72MX 256.
The following factors must be considered in determining how many
SVCs to allow:
• The total number of SVCs which an X.25 board can establish
depends on the packet size configured in the X.25 level 3
configuration. Upper limits for each DTC48 and DTC72MX card
are:
— 256 for packet sizes of 512 or less.
— 150 for 1024 byte packets.
— 100 for 2048 byte packets.
— 54 for 4096 byte packets.
• Note that these limits are not affected by packet size negotiation.
That is, if you have configured a packet size of 4096, and a packet
size of 128 has been negotiated, you are still limited to the 54 SVCs
supported with 4096 byte packets.