Modify the Network Management Configuration File

	MPE documents
	Complete PDF
	Table of Contents
	Glossary
	Index
⇓ Page Bottom

⇑ Page Top

NOTE: Before modifying the NMCONFIG.PUB.SYS file, make a backup copy of it. If the modifications made to the configuration file are successful, purge the backup copy.

Step 1: Begin the Configuration Process

NOTE: You must be logged on to the SYS account to modify the configuration file.

Step 2: Open the Network Management Configuration File

1. NMCONFIG.PUB.SYS is the name required by the software. Verify that this name is displayed in the Configuration file name field.
2. Verify that the name of the correct backup configuration file is in the Configuration file name field. The default is NMCBACK.PUB.SYS.
3. Press the [Open Config] function key.
4. If the configuration file you are opening does not exist, the following message will appear on the message line at the top of the screen:

Fields

Configuration file name

The only valid configuration file name the system recognizes for use by the network subsystem is NMCONFIG.PUB.SYS.

You can create or modify a configuration file using a different name and save it as an offline configuration file. You can use offline configuration files as a means of creating and storing configurations that you want to use in the future. When you are ready to use an offline configuration file, rename it as NMCONFIG.PUB.SYS, validate within NMMGR (SYSGEN cross-validation is done automatically within NMMGR). Use DTCCNTRL to shutdown and restart DTS or reboot the system.

Backup configuration file name

A backup file name must be specified whenever a configuration file is opened or created. The default backup configuration file name is NMCBACK.PUB.SYS. The backup file will be automatically updated with the contents of the configuration file each time the configuration file is successfully validated.

Network directory file name

The Network directory file must be configured for each new X.25 node (unless you will only be accessing the node using direct level 3 access). This field is only used for X.25 network management. The network directory contains information that one X.25 node needs in order to communicate with other X.25 nodes. The only network directory file name supported by HP is NSDIR.NET.SYS.

Write access password

The password is an optional feature. If a password has been assigned, you must enter it in the password field to update the configuration file. It is possible to open the file without using an assigned password, but the file will be in read only mode and NMMGR will not accept any changes.

If a password has not been assigned, you should ignore the password field. If you want to assign a password for the system you are configuring, refer to Using the Node Management Services (NMS) Utilities manual.

Step 3: Configure the Local Node Name

1. Assign a node name to the HP 3000 host in the "Local HP 3000 node name" field. Use the format nodename.domain.organization.
   If your HP 3000 host is the only computer in your network, you may enter any node name. If you have several computers on your network, you must make sure the node names for each host are unique.
2. In the field after the question, "Are you using the OpenView DTC Manager?", enter an N.
   This means that you will not use the OpenView DTC Manager (that is, use a PC to manage your DTCs).
   Instead, you will use the HP 3000 host to manage your DTCs. If you specify "Y" for using OpenView DTC Manager refer to the Configuring Systems for Terminals, Printers, and Other Serial Devices manual.
3. In the field after the question, "Do you have X.25 system-to-system or PAD connections?", enter an Y for yes.
4. After you enter the information on the screen, press the [Save Data] function key to save your entries.
5. After the data is saved (the Data flag in the upper right-hand corner is Y), press the [DTS] function key.

Fields

Local HP 3000 node name

The local HP 3000 node name is the name by which the HP 3000 Series 900 computer is known in the network. The format of a node name is nodename.domain.organization where the total number of characters is 50 or fewer, and each field contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The first character of each field must be alphabetic.

The nodename portion of each node name must be unique within the node's network. The nodename.domain portion of each node name must be unique within the internetwork. HP recommends that all nodes on the network be assigned the same domain and organization.

Assign meaningful node names. For example, MKTG.ITG.HP and LAB.ITG.HP are meaningful names for two nodes on the same Local Area Network (LAN) within Hewlett Packard. One node (MKTG.ITG.HP) is used by the marketing department. The other node (LAB.ITG.HP) is used by the lab. The domain field is the same because the nodes belong to the same network. The organization field is the same because the nodes belong to the same internetwork.

Are you using OpenView DTC Manager?

If you answer yes (Y) to this question, NMMGR assumes you are using a PC to manage your system and takes you to the corresponding set of screens. If you answer no (N), NMMGR assumes you are using host-based network management and takes you to the set of screens required for host configuration. If you are using this manual, you should enter an N in response to this question. (If you are using a PC to manage your network, see Configuring Systems for Terminals, Printers, and Other Serial Devices for the correct configuration procedures.)

Do you have X.25 system-to-system or PAD connections?

If you answer yes (Y) to this question, NMMGR assumes you are configuring X.25 connections and takes you to the set of screens required to configure DTC X.25 Network Access Cards. If you answer no (N), NMMGR assumes you have no need to configure X.25 connections and takes you to a different set of screens. If you are using this manual, you should enter a Y in response to this question. (If you are not configuring X.25 connections, see Configuring Systems for Terminals, Printers, and Other Serial Devices manual for the correct configuration procedures.)

Step 4: Configure the Link

1. "Local HP 3000 node name" is a display-only field. Verify that it is correct.
2. The "Link name" field displays DTSLINK. This is used by the HP 3000 DTS subsystem. Use this default.
3. In the "Physical path of LANIC" field, type the slot number for the LANIC card in the host. See the default list for commonly used slot numbers.
4. Verify that the cursor is in the Number of non-nailed PAD terminals field. Type the number of non-nailed PAD terminals, as listed on the worksheets. This is the maximum number of PAD terminals, not configured as nailed PAD terminals, that can logon to the computer.
5. Verify that the cursor is in the Starting Ldev Number field. Type in the ldev number where the non-nailed pool should start. The non-nailed PAD devices will be configured with the starting ldev number and higher.
   For example, if the number of ldevs is 2 and the starting ldev number is 200, then the non-nailed ldevs would be 200 and 201. If 201 is already configured as a nailed device then the non-nailed devices would be 200 and 202.
6. Verify that the cursor is in the Non-nailed PAD terminal profile name field. Type the name of the terminal profile that the non-nailed PAD terminals will use, as listed on the worksheets.
7. Press the [Save Data] function key.
   Press the [Go to DTC] function key to proceed to Step 5: Select DTC Type.

NOTE: The [Go To UserPort] key is used to configure the user port (default ldev 21) on the NIO console. Pressing this key takes you to the HP Support Modem Port Screen for configuring the ldev, the line speed, modem type, and parity of the user port. The configuration of user port is only supported for the NIO LAN console card (for example, HP 3000 Series 9X7 and 9X7 LX). Refer to the Configuring Systems for Terminals, Printers, and Other Serial Devices manual for more information on the user port. The [Go To UPS Port] key takes you to the Uninterruptible Power Supply Port Screen. This screen is used to configure the ldev number, line speed, and parity on a port of the SCSI/Console LAN card (default ldev 22) to support an uninterruptible power supply (UPS) connection. This port is only available and supported on HP 3000 Series 9X8 systems. Refer to the Configuring Systems for Terminals, Printers, and Other Serial Devices and to Performing System Manager Tasks for more information on the UPS.

Fields

Local HP 3000 node name

For display only. The local node name is configured on the Main screen.

Link name

The link name that will be used when device connections, including PAD device connections, are established. It must start with a letter and can be up to eight alphanumeric characters. (Note that this link name is different from the X.25 link name that you will configure on the X.25 Configuration screen during NS configuration.) The default is DTSLINK

Physical path of LANIC

This is the location of the DTS LANIC in the system's backplane.

The default physical path (slot numbers) for HP 3000 computers are listed below. These defaults optimize performance and use of the computer's cabinet space. Before moving the LANIC into another slot, consult an HP representative.

HP 3000 Systems	Slot Number
920, 922, 935, 932, 935, or 949 with HPIB	4.3
920, 925, 935, or 949 with ALINK	4.2
9X7	56
9X8	56/56
930	8.4
950, 955, 960, 980	2/4.2
990/992, 991/995	0/40

Number of non-nailed PAD terminals

The number of non-nailed PAD terminals that will be allowed to establish connections with this system over an X.25 network.

Other than entering the non-nailed PAD terminal profile name, no additional configuration is needed for non-nailed connections.

Starting ldev number

The ldev number where the pool of non-nailed PAD ldevs will be configured.

Non-nailed PAD terminal profile name

The terminal profile that will be used for all non-nailed PAD connections accepted by the system. PAD terminals must use a profile that defines the terminal type as terminal type 24.

Step 5: Select DTC Type

1. Select the DTC type by pressing one of the function keys: [DTC16iX], [DTC16MX/RX], [DTC16], [DTC48], or [DTC72MX].
   NMMGR will take you to the configuration screen for the specified DTC type.

NOTE: You may use the [List DTCs] key on the DTC Configuration Selection screen to see a list of all DTC names configured on your system.

Step 6: Specify DTC Configuration

1. Enter the DTC's name in the "DTC name" field.
   The DTC name can be up to eight alphanumeric characters, beginning with a letter. The DTC name must be unique on the system. It is acceptable (and common) to use the nodename part of the "DTC node name" as the "DTC name".
2. Enter the DTC's LAN address in the "DTC LAN station address" field.
   The LAN address can be found on a label inside the front cover or on the back panel of the actual DTC box.
   For DTC 16RX access to an HP 3000 in an MPE/iX host-based management environment, you must use the value 00-00-00-00-00-00 as the DTC 16RX LAN address.
3. Type in the DTC's node name in the "DTC node name" field.
   Use the format nodename.domain.organization, where nodename identifies the DTC. If there is more than one DTC on the network, the nodename of each DTC must be unique. The following are examples of valid DTC node names on the same network:

   ALPHA.ACCTG.TEKLAB

   BETA.ACCTG.TEKLAB

   Note that "DTC name" and "DTC node name" are two different fields. However, it is acceptable (and common) to use the nodename part of the "DTC node name" as the "DTC name", such as:

   DTC name = ALPHA

   DTC node name = ALPHA.ACCTG.TEKLAB

4. (Optional) Enter an IP address for the DTC, if you want this DTC to be able to respond to PING/iX requests. Otherwise, leave the "DTC IP Address" field blank.
   For DTC 16RX access to an HP 3000 in an MPE/iX host-based management environment, the IP address of the DTC 16RX is configured using the DTC 16RX Manager on the HP 9000 host and not on the HP 3000. Any value entered for the DTC 16RX in this field will be ignored.
   Refer to Chapter 2, "Introductory Screens," for more information on IP addresses.
5. Enable the event logging classes that you want. It is recommended that you enable classes 2 and 3 and disable classes 4 through 6. See "DTC Event Logging" in Chapter 2, "Introductory Screens," for information on these event logging classes.
   Note that logging class 1 is not configurable and is always enabled.
   Event logging classes do not apply for access to an HP 3000 in an MPE/iX host-based management environment using a DTC 16RX; any values entered in these fields for the DTC 16RX will be ignored.
6. Verify that the cursor is in the "Type" field under "Enter card types as installed in the DTC." Enter the card type for each card in the DTC. The valid card types are listed on the screen.
   Note that DTC 16iX/16MX/16RX does not have cards since its port connectors are built directly onto the DTC backplane.
   Refer to Chapter 2, "Introductory Screens," for more information on card types for each DTC.
7. (Optional) Enter a password if you wish to require the users to provide a password when they attempt to establish a communication link to this DTC via a PAD device. The syntax that the user would use is described in PAD Profiles and Access Password in Chapter 4 "Terminal and Printer Profiles"
   Refer to Chapter 4 "Terminal and Printer Profiles" for the syntax that the user will enter at the PAD prompt to supply the password.
8. Press the [Save Data] function key.
9. To configure a card in the DTC, enter the number of the card you want to configure in the "To configure a card, enter a card number ..." field at the bottom of the screen.
   Press the [Config Card] function key. Proceed to Step 7: Configure DTC Cards.
   To configure the ports on a DTC 16iX/16MX/16RX, simply press the [Config Ports] function key. Proceed to Step 7: Configure DTC Cards.
10. Repeat steps 1 through 9 above for every newly-added DTC to be managed by the HP 3000 host. If you want to select a DTC that has already been configured, enter the DTC's name in the DTC name field and press the [Read DTC] function key.

Next Key Labels

DNS/IP Routing

This key goes to a screen used to configure the DTC to use Domain Name Services for IP address resolution and IP routing configuration. These services are configured when back-to-back connection through routers are used or connections are to be made from DTC ports to HP 9000s or third party ARPA nodes.

Tune DTC

This key goes to a screen to change the AFCP, TCP and management timers for the DTC, if needed.

DTC U I

This key goes to a screen that has information that defines how the DTC user interface behaves. The DTC user interface is used when a DTC port is configured as a switched port.

Config SNMP

You may use the [Config SNMP] key on the DTC Screen to configure the DTC to act as an SNMP agent. This key goes to a screen to configure the DTC to act as an SNMP agent. Refer to the DTC Technical Reference Guide for more information on SNMP.

Fields

DTC name

A name, up to eight alphanumeric characters, beginning with a letter, assigned to the DTC. For convenience, you may want to use the nodename portion of the DTC node name as the DTC name. Each DTC configured on the system must have its own unique DTC name.

You can call up (and modify) data for a previously configured DTC by entering an existing DTC name in the DTC name field and pressing the [Read DTC] key.

DTC LAN station address

The local station address of the DTC. This is a twelve character hexadecimal number. Each DTC's LAN station address is printed inside the DTC's front cover on a DTC48, or on the back panel of the DTC72MX or DTC16MX/iX/RX.

DTC node name

The fully qualified node name of the DTC, in the form nodename.domain.organization. Each part of the name can be up to 16 characters.

DTC IP Address (Optional)

The internet protocol (IP) address of the DTC being configured. An example of an address is: C 192.191.191 009. The IP address is optional for the DTC, but one must be configured if the DTC is to be able to respond to PING requests.

Enable logging class (Y/N)

These fields, labeled 1 through 6, enable the DTC to log various classes of events. Enter a Y to enable a class, N to disable. Only events falling into classes which you have explicitly enabled will be logged. Class 1 events are the most critical and will always be logged. Note that enabling class 5 will result in a substantial number of events being logged. HP suggests that you enable class 5 only when necessary and only for short periods of time. You should also avoid enabling logging class 5 simultaneously with an X.25 trace.

Type (of card)

The type of card installed in the DTC. Verify that the cursor is in the "Type" field under "Enter card types as installed in DTC." Enter the card type for each card in the DTC. The valid card types are listed on the screen.

PAD access password (optional)

A password, up to eight alphanumeric characters in length, that will be required when users connected to this DTC via a PAD device attempt to establish a communication link.

To configure a card, enter a card number then press Config Card

This parameter determines the next screen that will appear after you have saved the data configured on the screen. Enter the number of the card you want to configure and press the [Config Card] key.

Step 7: Configure DTC Cards

1. Verify that the DTC name and card number displayed are correct.
2. (Optional) Enter the port group type. The valid types are D for direct connect and M for modem connect. The default is D.
3. Press the [Tab] key to move the cursor to the first port on the card. Enter an ldev number for this port in the "Ldev" field.
   Ldev numbers used for each port on the DTC must be unique.
   For example, you can use ldev number 100 for port 0 of the first card, and increment the ldev number by 1 for each consecutive port.
   So a DTC 72MX with 3 asynchronous cards (a total of 72 ports) would be assigned ldev numbers 100 through 123 for the 24 ports on the first card, 124 through 147 for the ports on the second card and 148 through 171 for the ports on the third card.
   For the second DTC, you would start with an ldev number greater than 171.

   NOTE: Pressing the [Show Ldevs] key will display a list of all the ldev numbers configured in NMMGR in addition to the DTC name, card type, and profile name.

4. Enter the profile name for each port in the "Profile Name" field.
   A profile for the port defines the characteristics of the device to be connected to that port.
   For direct terminals ports, the suggested profile to use is TR10D96. For direct printer ports, the suggested profile to use is PR18D96 (or PR22D24 for HP printers with status checking). For a UPS connected to a DTC port, the suggested profile is UP10D12.
   See the Tables in Chapter 4 "Terminal and Printer Profiles" to list terminal, printer and UPS profiles supplied by the system. You may also create your own profiles. Refer to Chapter 4 "Terminal and Printer Profiles" for more information on profiles.
5. Repeat above two steps for every port in this card.

   NOTE: To reduce typing ldev numbers and profiles on the screen, you can use the [Fill Card] key to automatically assign ldev numbers and profile names. First, enter an ldev number (and profile name if you do not wish to use the default profile name) for port 0, then press [Fill Card]; the system will automatically assign incremental ldev numbers to each subsequent port on the screen and copy the specified profile for each port. The system will automatically save the data it has entered. The [Clear Display] key on your keyboard will clear the part of your screen that is below the cursor position. You may use this key and the [Fill Card] key to quickly modify a screen.

6. Press the [Save Data] function key to save the data on the screen.

   CAUTION: Before you exit this screen, make sure you press [Save Data] if you want to keep the data on the screen; otherwise your screen input will be lost. This occurs even if you temporarily exit the screen to read [Help] information.

7. To configure another card in the DTC, use the cursor keys to move to the field on the screen: "To configure a different card, enter its number,...". Enter the card number of the card you want to configure.
8. Press the [Config Card] function key. The corresponding screen for the card number entered in the last step will be displayed.
9. If all the cards have been configured, press the [Prior Screen] function key to return to the DTC Configuration Selection screen to select another DTC to configure. Otherwise, if every DTC has been configured, press the [Validate DTS/LINK] function key to validate the configuration file.

NOTE: NMMGR allows the configuration of up to 4649 terminal I/O devices. The largest valid ldev number allowed is 4679.

Fields

DTC name

Display only.

Card number

Display only.

Port Group Type (Optional)

The valid type are D for direct connect and M for modem connect. The default is D.

Ldev

The logical device (ldev) number to be associated with the port. Each ldev number must be unique; it may not be duplicated by any other device configured on the system.

Profile Name

The terminal or printer profile name to be associated with the port. The features defined by the profile must correspond to the actual operating features of the port and its attached device.

To configure a different card, enter its number; then press Config Card

The card that you want to configure next. Use this parameter in combination with the [Config Card] key to select and move to a different card in the same DTC. For example, after card 0 is configured, enter a 1 in this field and press the [Config Card] key to move to the configuration screen for card 1.

Step 8: Configure X.25 Connections

1. Choose the screen that you want to move to. To create a new card configuration, go to the screen that lets you configure level 1 and 2 parameters first. (If you are modifying an existing card configuration, you may choose to move to one of the other choices listed on the screen.)
2. Press the function key that corresponds to the screen that you want to move to.

   Fields

   This screen is used to select and move to the lower level DTC/X.25 Card Configuration screens. The function keys available for selection and the corresponding lower level screens are shown below:

   Go to Level 1&2

   Takes you& to the DTC X.25 Card Configuration — Level 1 and 2 screen. Use this screen to configure level 1 and 2 network parameters. Most of the information you enter on this screen will be on the subscription form for the packet switched network you are connecting to. You must enter level 1 and 2 parameters for all DTC/X.25 Network Access cards whether they support X.25 system-to-system connections, PAD connections, or both.

   Go to Level 3

   Takes you to the DTC X.25 Card Configuration — Level 3 & Miscellaneous screen. Use this screen to configure level 3 network values and to specify a maximum number of PAD connections (if the card is to support PAD connections). Most of the information you enter on this screen will be on the subscription form for the packet switched network you are connecting to. You must enter level 3 parameters for all DTC/ X.25 Network Access cards whether they support X.25 system-to-system connections, PAD connections, or both.

   Go to SysLUG

   Takes you to the DTC X.25 Card Configuration — Sys-to-Sys LUGs screen. Use this screen to configure the X.25 link name, the maximum number of switched virtual circuits, and local user group information the DTC will need in order to support X.25 iX System Access (NS system-to-system links). Information entered on this screen must not conflict with information entered during NS link configuration. (Configure information on this screen only if you are configuring X.25 system-to-system connections.)

   Go to PAD

   Takes you to the DTC X.25 Card Configuration — Nailed PAD Connections screen. Use this screen to configure information the DTC will need in order to support terminals and printers with permanently assigned ldev numbers (nailed devices) over PAD connections. (Configure information on this screen only if you are configuring nailed PAD connections.)

   Go to Security

   Takes you to the DTC X.25 Card Configuration — PAD Security screen. Use this screen to configure security if you want to allow or disallow PAD access from specific X.25 calling addresses. (Configure information on this screen only if you are configuring PAD and want to implement PAD security.)

Step 9: Configure X.25 Level 1 and 2

1. Verify that the cursor is in the Line speed field. Enter the line speed for the DTC/X.25 Network Access card as specified by your network subscription.
2. Verify that the cursor is in the Packet Switched Network Name field. Enter the name of the network you subscribe to.
3. Verify that the cursor is in the CCITT X.25 Standard field. Enter the X.25 standard you are using.
4. Verify that the cursor is in the Frame size (N1) field. Enter the frame size as specified by your network subscription.
5. Verify that the cursor is in the Retransmission timer (T1) field. Enter the value for the retransmission timer as specified by your network subscription.
6. If you are using the 1984 standard, verify that the cursor is in the Timer T3 field. Enter the value for this timer as specified by your network subscription. If you are using the 1980 standard, skip this field (press [TAB] to move to the next field).
7. Verify that the cursor is in the Retransmission count (N2) field. Enter the value for the retransmission count as specified by your network subscription.
8. Verify that the cursor is in the Unacknowledged frame number (K) field. Enter the value for the number of frames that can be transferred without acknowledgment as specified by your network subscription.
9. Verify that the cursor is in the Modulo field. Enter the modulo value as specified by your network subscription.
10. When you have entered all level 1 and 2 values as specified by your subscription, press the [Save Data] key to save the configuration.
11. Press the [Go To Level 3] key to move to the DTC X.25 Card Configuration — Level 3 & Miscellaneous screen.

    Fields

    You use this screen to configure X.25 level 1 and 2 parameters for the DTC/X.25 Network Access card being configured. You must define these parameters for both X.25 system-to-system and PAD connections. Ranges for configurable values are listed on the screen.

    DTC Name

    Display only.

    Card Number

    Display only.

    Line speed

    The line speed for the connection. Supported speeds for a card installed in a DTC16 are 1200, 2400, 4800, 9600, or 19200 bps. Supported speeds for a card installed in a DTC48 or DTC72 are 1200, 2400, 4800, 9600, 19200, 48000, 56000, or 64000 bps.

    Packet Switched Network Name

    The name of the network you subscribe to. Possible network names include: DATAPAC, PSS, DATEX-P, TRANSPAC, TYMNET, TELENET, DDN, HP PPN, ITAPAC, LUXPAC, DATANET1, DCS, DCE, X25PDN. (The name must be entered exactly as shown here.)

    If two X.25 systems are directly connected (for example, if you have a cable connecting one DTC X.25 card directly to another DTC X.25 card) one of the two systems must be configured as DCE and the other as DTE. To configure a card as DCE, enter DCE in the Packet Switched Network Name field. To configure a card as DTE, enter X25PDN in the Packet Switched Network Name field. (Entering DCE configures the X.25 card as a DCE at levels 2 and 3 of X.25. At level 1 it remains DTE.)

    CCITT X.25 Standard

    Version of the CCITT X.25 standard you are using, either 1980 or 1984.

    Frame size (N1)

    The frame size, in bytes, as listed on your subscription. Note that many network subscription forms give this value in bits, not bytes. In such cases, divide the number of bits by 8 to obtain the correct number of bytes to enter in this field.

    Range: 23 to 4103 bytes.

    Retransmission timer (T1)

    Time, in milliseconds, the transmitting node waits before retransmitting an unacknowledged frame. The default of 3000 milliseconds is adequate for most installations.

    Range: 1000 to 12000 milliseconds.

    Timer (T3)

    This value is required only if you are using the 1984 CCITT standard. Specifies the time a link will remain idle before it is automatically reset. The value of T3 must be greater than T1. The default is 20 seconds.

    Range: 0 to 1000 seconds.

    Retransmission count (N2)

    The number of times a frame is retransmitted before an error is indicated. The default is 20 times.

    Range: 0 to 255.

    Unacknowledged frame number (K)

    The maximum number of frames which can be transmitted without acknowledgment from the network.

    Range: 1 to 7.

    Modulo

    The counting cycle for the send frame sequence number.

    Range: 8 or 128.

Step 10: Configure X.25 Level 3 and Miscellaneous

1. Verify that the cursor is in the X.25 card address field. Enter the address that will be appended to outgoing PAD calls. If no address should be sent in call request packets, leave this field blank.
2. Verify that the cursor is in the Maximum number of PAD connections field. Enter the maximum number of PAD connections that will be allowed through this card. Remember that this number must include both nailed and non-nailed PAD connections. If PAD will not be configured, leave this field blank.
3. Use the [TAB] key to move to the Logical Channel Identifier (LCI) Range fields. Enter high and low values for the permanent virtual circuits (PVCs) or switched virtual circuits (SVCs) you are configuring per your network subscription. At lease one pair must be configured. Leave the fields blank for any PVC or SVC types that are not configured.
4. Use the [TAB] key to move to the Default Flow Control fields. Enter In and Out values according to your network subscription.
5. Use the [TAB] key to move to the Flow control negotiation field. Enter Y to enable or N to disable according to your subscription.
6. Use the [TAB] key to move to the Throughput class negotiation field. Enter Y to enable or N to disable according to your subscription.
7. Use the [TAB] key to move to the Use of D-bit field. Enter Y to enable or N to disable according to your subscription.
8. Use the [TAB] key to move to the Extended packet sequence numbering field. Enter Y to enable or N to disable according to your subscription.
9. When you have entered all level 3 values as required by your subscription, press the [Save Data] key.
10. Press the [Go To SysLUG] key to move to the DTC X.25 Card Configuration — Sys-to-Sys LUGs screen.

Fields

DTC Name

Display only.

Card Number

Display only.

X.25 card address

A calling address appended to outgoing calls. Used for programmatic access to PAD devices. Also used for network loopback test. For most network applications, this is the same as the address used for X.25 system-to-system communications.

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.

Maximum number of PAD connections

Number of PAD connections that you will allow at any given time through the card being configured. The maximum number of connections that can be allowed are: For DTC16 the maximum is 32, for DTC48 the maximum is 256 and for DTC72MX the maximum is 156. Note that this number specifies the limit for all PAD calls through this card, including both nailed and non-nailed connections.

In determining how many PAD connections to allow, keep in mind that PAD connections use SVCs, out of the pool of available SVCs. The same pool of SVCs is used for system-to-system connections if system-to-system connections are also configured for this card. You will need to balance your PAD support requirements with you system-to-system requirements to find the optimum configuration for your network.

PVCs

Low and high values for permanent virtual circuits as listed on your X.25 subscription.

One-way incoming SVCs

Low and high values for one-way incoming switched virtual circuits as listed on your X.25 subscription.

Two-way SVCs

Low and high values for two-way (incoming and outgoing) switched virtual circuits as listed on your X.25 subscription.

One-way outgoing SVCs

Low and high values for one-way outgoing switched virtual circuits as listed on your X.25 subscription.

Packet size

Size of packet, in bytes, for incoming and outgoing data as listed on your X.25 subscription. Note that for X.25 cards on which you intend to configure PAD support, the subscribed and configured packet size must be 128, 256, or 512 bytes.

Window size

Window size for incoming and outgoing data as listed on your X.25 subscription.

Throughput class

Throughput class values for incoming and outgoing data. Values depend upon the speed of the link, as follows:

Throughput class	Line Speed
7	1200
8	2400
9	4800
10	9600
11	19200
12	48000

Flow control negotiation

Specifies whether or not flow control negotiation is enabled. When flow control negotiation is enabled, both packet size and window size are negotiable. Enter Y if your subscription allows flow control negotiation and you wish to enable it. Otherwise enter N.

Use of D-bit

Specifies whether or not delivery confirmation is enabled. Enter Y if your subscription allows delivery confirmation and you wish to enable it. Otherwise enter N.

Throughput class negotiation

Specifies whether or not throughput class negotiation is enabled. Enter Y if your subscription allows throughput class negotiation and you wish to enable it. Otherwise enter N.

Extended packet sequence numbering

Specifies whether or not extended packet sequence numbering is enabled. Enter Y if your subscription allows extended packet sequence numbering and you wish to enable it. Otherwise enter N.

Step 11: Configure X.25 System-to-System Information

1. Verify that the cursor is in the X.25 link name field. Enter the link name that will be used for X.25 iX System Access (X.25 system-to-system connections) for this DTC/X.25 Network Access card. This link name must be the same as the link name configured on the X.25 Configuration screen during NS configuration (see Chapter 6 "Configuring X.25 Links Step-by-Step")
2. Move the cursor to the Maximum number of Switched Virtual Circuit field. Enter the maximum number of SVC connections that will be supported for this card.
3. Move the cursor to the System X.25 address field. Enter the same X.25 address as entered in the X.25 card address field on the Level 3 and Miscellaneous screen unless your network application requires the address used for X.25 system-to-system communications to be different from that used for PAD communications. If the addresses must be different, enter the X.25 address that the local system will use for system-to-system connections in this field.
   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.
4. Move the cursor to the first Address field under Enter remote X.25 addresses and security. Enter the X.25 address of a system that will be able to establish a system-to-system connection with the HP 3000 Series 900 you are configuring.
5. Move the cursor to the Sec. field next to the address you just entered. Enter the security level for connections between the remote X.25 address and the system you are configuring. Possible values are IN (accept calls from the address), OU (send calls to the address), and IO (accept calls from and send calls to the address).
6. Repeat steps 4 and 5 for each remote system that will be able to establish a system-to-system connection with the HP 3000 Series 900 you are configuring. If you need to enter more than eight remote system addresses, 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 addresses.
7. When you have entered all remote X.25 addresses and associated security, press the [Save Data] key to save the configuration.
8. Press the [Go To PAD] key to move to the DTC X.25 Card Configuration — Nailed PAD Connections screen.

   Fields

   This screen lets you configure X.25 system-to-system local user group (LUG) information for the DTC/X.25 Network Access card being configured.

   DTC name

   Display only.

   Card number

   Display only.

   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.

   Maximum number of Switched Virtual Circuits

   The number of switched virtual circuits (SVCs) that will be allowed through this DTC/X.25 Network Access card. Up to 32 SVCs are allowed for cards mounted in a DTC 16, up to 256 SVCs are allowed for cards mounted in a DTC 48 and up to 156 SVCs are allowed for cards mounted in DTC 72MX.

   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.
   • If you are also configuring PAD connections on this card, remember that PAD connections use SVCs out of the pool of available SVCs. You will need to balance your PAD support requirements with your system-to-system requirements to find the optimum configuration for your network.
   • The total number of SVCs available may also be limited by your PSN subscription.

   System X.25 address

   This is the X.25 address of the X.25 card, to be used for system-to-system connections. In most cases, this will be the same as the address entered on the Level 3 & Miscellaneous screen. If, however, your network application requires the address used for X.25 system-to-system communications to be different from the address used for PAD connections, enter a different address here. For most connections to public data networks, this will be the DTC/X.25 Network Access card address plus a unique subaddress for the host system.

   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.

   Address

   The X.25 addresses of the remote systems in your X.25 network

   Sec.

   The security level associated with each remote X.25 address. To accept only incoming calls for call setup, enter IN in the security field beside the address. To allow only outgoing calls for call setup, enter OU. To allow both incoming and outgoing calls for call setup, enter IO.

Step 12: Configure Nailed PAD Connections

@DTS.DTC.SELECT.dtcname.CARD012.PADn

or

@DTS.DTC.SELECT.dtcname.CARD345.PADn

1. Verify that the cursor is in the first field under Ldev. Type the ldev number that the nailed connection will use in the Ldev field.
2. Move the cursor to the Profile field and enter the profile name the connection will use.

   NOTE: To see a list of existing profiles, press the [Go To Profiles] key. If you need to create a new profile, see Chapter 4 "Terminal and Printer Profiles"

3. Move the cursor to the Device Name field and enter the unique name assigned to the remote device that will be using this nailed connection.
4. Move the cursor to the Remote Device (PAD) X.25 Address field and enter the X.25 address of the remote PAD that will be using this nailed connection.
5. If you want to associate a closed user group number with this nailed connection, move the cursor to the CUG No. field and enter the CUG number.
6. Repeat the above steps for every device attached to this card. (You can use the [Fill Cards] key to fill in ldev and profile information.) If you need to configure more than eight nailed PAD connections for this card, 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 nailed connections. You can configure up to 256 nailed PAD connections for each card.
7. When all nailed connections have been configured, press the [Save Data] key.
8. Press the [Go To Security] key to move to the DTC X.25 Card Configuration — PAD Security screen.

Fields

DTC name

Display only.

Card number

Display only.

Ldev

The logical device (ldev) number to be associated with the connection. Each ldev number must be unique; it may not be duplicated by any other device configured on the system.

Profile

The PAD terminal or PAD printer profile name to be associated with the connection. The features defined by the profile must correspond to the actual operating features of the connection and the device.

Device Name

The name associated with the PAD-connected terminal or printer. The device name can be up to eight (8) characters and must be unique for each PAD connection.

Remote Device (PAD) X.25 Address

The X.25 address of the remote PAD device. Where devices are connected to a multiport PAD, include port subaddresses in this field.

CUG No. (Optional)

The closed user group number (0 to 99), if specified for your network subscription. Leave blank if your subscription does not specify a CUG number.

Step 13: Configure PAD Security

1. Verify that the cursor is in the Allow access field. If you want to accept calls only from the calling addresses listed below (and reject all other calls), enter a Y. If you want to reject calls only from the calling addresses listed below (and accept all other calls), enter an N.
2. In the fields under Enter remote X.25 calling address below:, enter the X.25 addresses of all remote PAD devices that will be accepted for connection, if Allow access is Y, or enter the addresses of all remote PAD devices that will be rejected for connection, if Allow access is N. If you need to configure more addresses than there is room for on this screen, press the [Save Data] key, then press the [Next Page] key to enter more device addresses. Up to 512 remote X.25 calling addresses can be configured.
3. If you have finished configuring PAD security for this card but still need to configure additional cards or DTCs, press the [Prior Screen] key until you return to the DTC Configuration screen so that you can select a different card or DTC to configure.
4. If all DTCs and all cards have been configured, press the [Validate DTS/LINK] key to validate the DTC configuration for the system. (See appendix A for validation error messages.)

   Fields

   DTC name

   Display only.

   Card number

   Display only.

   Allow access

   Specifies whether connection requests from devices whose addresses are listed will be accepted (Y) or rejected (N).

   If you enter Y, calls will only be accepted from devices whose addresses you list on this screen. If you enter Y and do not list any addresses, all calls will be rejected.

   If you enter N, calls will only be rejected from devices whose addresses you list on this screen. If you enter N and do not list any addresses, all calls will be accepted.

   If you do not update this screen (data flag is N, a default PAD security will be downloaded that allows all calls to be accepted.

   Enter remote X.25 calling address below

   Lists the X.25 addresses of all PAD devices that will be accepted for connection if Allow access is Y or rejected for connection if Allow access is N. Enter up to 32 remote addresses per screen and up to 512 per DTC/X.25 Network Access card.

   You can use the letter X as a wildcard character in place of any single digit. All systems with corresponding addresses will have the same access rights. The address check is sensitive to the length of the address. To manage addresses, you may enter pyramids of Xs where the base is the longest expected address and the peak is the shortest expected address.

   For example to control access to all PAD addresses of six, seven or eight digits starting with 1234:

   1234XX

   1234XXX

   1234XXXX

   To control access to PADs with addresses of seven digits starting with 6789:

   6789XXX

Step 14: Validate/Cross-Validate the Configuration File

1. To validate the DTS configuration in the configuration file, press the [Validate DTS/LINK] key at the Card Configuration screen. You can also reach the Validate Configuration File screen by typing validate at the command line on top of any NMMGR screen and pressing [Enter]. (Note that the [Enter] key is not the carriage return key.) While at the Validate screen press the [Validate DTS/LINK] key to validate the DTS configuration.
   The DTS validation procedure starts by displaying the following on the terminal:

   -> Validation of DTS/LINK started. <-

   -> Validation of DTS/LINK finished. <-

   If errors were encountered in the configuration file, the validation procedure will print out the total number of errors found. Error messages will also be displayed explaining the problems found. Refer to Appendix A "Error Messages" for more information about these error messages.
2. After validation of the network configuration file is complete, the following will appear on the screen as the file is cross-validated with the files created with SYSGEN (warning messages may vary):

   
    NMMGR will now cross-validate the NMCONFIG file with SYSGEN.
    
    SYSGEN version E.00.00 : catalog version E.00.00 FRI, FEB 4, 1994, 3:32 PM
    Copyright 1987 Hewlett-Packard Co. All Rights Reserved.
            **warning** No NMCONFIG file in the configuration
            **warning** NMCONFIG.PUB.SYS is now the NMCONFIG file
   
            ** First level command **
            io                log (lo)       misc (mi)        spu (sp)
            sysfile (sy)
   
            basegroup (ba)    keep(ke)       permyes (pe)     show (sh)
            tape (ta)
   
            clear (cl)(c)     exit (ex)(e)   help (he)(h)     oclose (oc)
            redo
   
    sysgen> PERMYES ON {Automatically reply YES}
    sysgen> SY {Go to the SYSFILE subsystem}
            ** SYSFILE configurator commands **
   
            aauto (aa)      aboot (ab)     acmsl (ac)        asprog (as)
            cmsl (cm)       dauto (da)     dboot (db)        dcmsl (dc)
            dsprog (ds)     lcmsl (lc)     rauto (ra)        rboot (rb)
            rcat (rc)       rcmsl (rcm)    rdcc (rd)         ripl (ri)
            rnmlib (rn)     rsprog (rs)    show (sh)
   
            clear (cl)(c)   exit (ex)(e)   help (he)(h)      hold (ho)
    sysfile> RDCC {Set configuration file to NMCONFIG.PUB.SYS}
    sysfile> {HO} {Remove braces to HOLD RDCC command}
    sysfile> EX {EXit the SYSFILE subsystem
             configuration changes are not kept yet!
             still want to exit (yes/no)? Automatic yes
   
    sysgen> BA CONFIG {Set BAse group to CONFIG}
    sysgen> KE (KEep the changed configuration data)
               keeping to group CONFIG.SYS
               Purge old configuration (yes/no)? Automatic yes
               ** configuration files successfully saved **
    sysgen> EX {EXit SYSGEN}
   
           Cross-validation with SYSGEN was successful.
           Copying validated configuration file to backup file, please wait ***
           (Press RETURN when done viewing screen contents)
           

3. After successful validation and cross-validation, and if the file in use is NMCONFIG.PUB.SYS, the following prompt will appear:

   
    Do you want DTS changes to become active now (Y/N)?
   
    Y =   all changes made take effect now
   
    N =   all changes made will take effect up next dynamic
          configuration or system reboot
   
    H =   help
   
    >
           

   Answer Y if you want to invoke DTCCNTRL and make DTS changes take effect now, or answer N if you don't want DTS changes to take effect now. Note any messages that describe additional actions needed for changes to become active. After you exit NMMGR you can review any actions needed by viewing the logs at the end of the file LOGDCC.PUB.SYS.
   If you answer N, the DTS changes will take effect the next time DTCCNTRL is invoked, a DTS shutdown/restart is done, or the system is rebooted.
   Type H if you need more help to answer the question.
4. After viewing the messages describing what actions are required, if any, enter [RETURN] when you see the prompt:
   (Press RETURN when finished view screen contents.)
   You will return to the Validation screen. You may make additional configuration changes or exit NMMGR.

Step 15: Ensure DTS Changes Become Active

NOTE: If you answered N to the question in Step 14, thus choosing not to call DTCCNTRL after NMMGR exit, refer to Chapter 7 "Managing Networks with DTCCNTRL" for the syntax on how to invoke DTCCNTRL outside NMMGR.For host-based X.25 configuration tasks and associated actions for changes to take effect, refer to Configuring and Managing Host-Based X.25 Links for more information.

Performing a DTC Reset

Performing a DTS Shutdown/Restart