Configuring and Managing Host-Based X.25 Links HP 3000 MPE/iX Computer Systems Edition 5 36939-90054 E1098 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction X.25 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 System-to-System Connections . . . . . . . . . . . . . . . . . . . . . . . . . Device Connections Via PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host-Based X.25 Configuration Concepts. . . . . . . . . . . . . . . . . . . . . . . DTS Configuration Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NS Configuration Branch. . . . . . . . . . . .
Contents 4 Step 5: Select DTC Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6: Specify DTC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . Next Key Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7: Configure DTC Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 8: Configure X.25 Connections . . . . . . . . . . . . . . . . . . . . . . . . . Step 9: Configure X.25 Level 1 and 2 . . . . . . . .
Contents 7. Managing Networks with DTCCNTRL DTCCNTRL Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTCCNTRL Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMCONFIG and NMCONFIX Files. . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Configuration of DTCs. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6
Figures Figure 1-1 . X.25 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Figure 2-1 . Incoming PAD Security Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Figure 2-2 . DTC Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Figure 2-3 . DTC Card Configuration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 8
Tables Table 4-1. Host-Based Terminal Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Table 4-2. Host-Based Printer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Table 4-3. PAD Profile Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Table 4-4. Terminal PAD Profiles . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This manual describes the configuration, operation, and management of X.25 network connections for users of HP 3000 Series 900 systems with host-based network management. Host-based X.25 connections are available on systems running MPE XL release 3.1 or later MPE/iX release. You should use this manual only if the connections you are configuring are host-based X.25 connections. To configure X.
• Chapter 2, “Preparing to Configure DTCs,” details the information you will need before you can begin to configure DTS for systems with host-based X.25 connections. It also describes worksheets you can use to plan and record your DTS configuration. • Chapter 3, “Configuring DTCs Step-by-Step,” provides step-by-step instructions for configuring DTCs for systems with host-based X.25 connections.
NS Cross-System Network Manager’s Reference Manual Using NS 3000/iX Network Services NS Cross-System NFT Reference Manual Configuring Systems for Terminals, Printers, and Other Serial Devices Troubleshooting Terminal, Printer, and Serial Device Connections Using OpenView DTC Manager Berkeley Sockets/iX Reference Manual Customizing Terminal and Printer Type Files with Workstation Configurator Asynchronous Serial Communications Programmer’s Reference Manual System Startup, Configuration, and Shutdown Referenc
Introduction 1 Introduction This manual provides a complete reference for the configuration, operation, and management of X.25 network connections for users of HP 3000 Series 900 systems with host-based network management. Host-based X.25 support is provided for both system-to-system and PAD communications. This chapter describes the host-based X.25 capabilities. It includes the following: • X.
Introduction X.25 Network Connections X.25 Network Connections Many of the communications services available for HP 3000 Series 900 systems are provided through the Datacommunications and Terminal Controller (DTC). There are six types of DTCs currently supported: DTC 72MX, DTC 48, DTC 16, DTC 16iX, DTC 16MX and the DTC 16RX. The DTC 72MX, DTC 48 and the DTC 16 can support the DTC/X.25 Network Access cards that make communications over X.25 networks possible.
Introduction X.25 Network Connections The PAD support provided on MPE/iX systems conforms to the 1984 version of CCITT recommendations X.3 and X.29. Support is also provided for the 1980 recommendation. Packet sizes of 128, 256, and 512 bytes are supported. Access is provided for users of asynchronous serial devices connected to both public and private PADs. A public PAD is a service provided by a Public Data Network (PDN), such as TELENET or TRANSPAC.
Introduction Host-Based X.25 Configuration Concepts Host-Based X.25 Configuration Concepts Host-based X.25 connections are configured using the Node Management Configuration Manager (NMMGR). NMMGR allows you to completely configure both PAD support and system-to-system X.25 connections. For more information on NMMGR and its operation, see Using the Node Management Services (NMS) Utilities manual.
Introduction Host-Based X.25 Configuration Concepts NOTE The X.25 iX System Access procedure described in this manual assumes the use of guided configuration. While it is possible to configure this link using non-guided configuration, Hewlett-Packard strongly recommends the use of the guided configuration process. Nailed and Non-Nailed Connections A nailed device is one that is permanently associated with an ldev number through the NMMGR configuration of an MPE/iX system.
Introduction Host-Based X.25 Configuration Concepts When the user connects to the system through a public PAD, the connection will use a non-nailed device on the host.
Introduction Operation Operation When the HP 3000 is configured to use host-based X.25 networking configurations, the command DTCCNTRL is provided to allow operators to start and stop X.25 system-to-system or PAD connection support, obtain status about whether X.25 and PAD support are up, and to dynamically change many configuration parameters entered for the DTS subsystem without rebooting the system. System Operator (OP) capability is required to obtain status and start and stop X.25 and PAD support.
Introduction Maintenance Maintenance To support the maintenance of host-based X.25 connections, the Terminal Diagnostic Support Monitor (TermDSM) utility supports additional command functions. These functions are part of the DIag, DUmp, Reset, and Status commands (capital letters indicate command abbreviations). Additionally, the TermDSM Trace command allows tracing of X.25 level 2 or level 3, or of a virtual circuit (VC). Several of the TermDSM command functions now provide data about DTC/X.
Introduction Maintenance Level 2 Trace If you choose trace option 2, level 2 trace, you will be prompted for the filter (trace headers only or full packets) and given the option of specifying a file name. No other information is required. Level 3 Trace If you choose trace option 3, level 3 trace, you will be prompted for a VC type.
Introduction Maintenance HnnnnnnB.PUB.SYS (second log file) All the host-based X.25 log files begin with the letter H. The second through the seventh digits correspond to the last six digits of the DTC address (remember, each DTC has its own set of two log files). The A or B at the end of the file name indicates whether it is the first or the second file. Each file stores up to 500 records, with each record or packet being 132 bytes. Hewlett-Packard recommends that you treat the files as read-only files.
Preparing to Configure DTCs 2 Preparing to Configure DTCs This chapter details the information you will need before you can configure the datacommunications and terminal subsystem (DTS) for host-based systems that include X.25 networking. DTS defines the physical connections and configuration parameters for the computer, its DTCs, and all DTC-connected devices. Sample worksheets are included to facilitate configuration.
Preparing to Configure DTCs Plan the Network Configuration Plan the Network Configuration Before you use NMMGR to configure DTS (the DTCs and DTC connections for your system), you must define the physical layout and configuration parameters for the computer, its DTCs, and all DTC-connected devices. Configuration values that you must determine include a name for the computer and a link name and physical path for the link between the computer and its DTCs.
Preparing to Configure DTCs Plan the Network Configuration Figure 2-1 Incoming PAD Security Flowchart Chapter 2 27
Preparing to Configure DTCs Defining the HP 3000 System Defining the HP 3000 System The following configuration parameters are required to define the HP 3000 host for asynchronous device connections. Local HP 3000 Node Name The name by which the HP 3000 Series 900 computer is known in your network. The format of a node name is nodename.domain.organization, where each field can contain 16 or fewer characters (alphanumeric, underscores, or hyphens). The first character of each field must be alphabetic.
Preparing to Configure DTCs Defining the DTC Defining the DTC The following parameters are required to define each DTC used for connection between the HP 3000 and its asynchronous devices (terminals and printers). You can use the DTC Configuration worksheets as shown later in this chapter to record the values selected for each DTC. DTC Name A name for the DTC, up to eight alphanumeric characters, beginning with a letter. Each DTC configured on the system must have a unique name.
Preparing to Configure DTCs Defining the DTC DTC IP Address (optional) The internet protocol (IP) address of the DTC. The IP address is optional. It is used if your HP 3000 is configured as part of a network and you want the DTC to be able to respond to PING/iX requests. An IP address is made up of a network portion and a node portion. The address is formed as four fields of decimal numbers where each number is a value ranging from 000 to 255.
Preparing to Configure DTCs Defining the DTC DTC Cards (or DTC Boards) The number and types of connector cards in the DTC. (The cards are also referred to as boards.) DTC 16 can have up to 2 asynchronous cards and 1 DTC/X.25 Network Access card, DTC 48 up to 6 cards, and DTC 72MX up to 4 cards. DTC 16iX/16MX/16RX has its two port connectors built directly onto its backplane for support of up to 16 asynchronous devices.
Preparing to Configure DTCs Defining the DTC Connector Cards Defining the DTC Connector Cards Connector cards (also called boards) in the DTC allow terminals, printers, and other serial devices to be connected to the DTC for communication with an HP 3000 Series 900. You can use the DTC Card Configuration worksheet as shown later in this Chapter, to record the values selected for each DTC card.
Preparing to Configure DTCs Defining the DTC Connector Cards called nailed devices. Printers and UPSs, as well as devices that will be programmatically accessed, must be nailed devices. Each nailed ldev number assigned in NMMGR must be unique. For host-based DTC management, you may have PAD ports without ldev numbers assigned to them; hence they are non-nailed devices.
Preparing to Configure DTCs Determine X.25 Connection Characteristics Determine X.25 Connection Characteristics You must define characteristics for the X.25 PAD or system-to-system connections you are configuring. Values need to be configured for each DTC/X.25 Network Access card mounted in the DTCs for the system you are configuring. Whether you are configuring system-to-system, PAD connections, or both, you will need to define values for levels 1, 2, and 3 of the X.25 network.
Preparing to Configure DTCs Configuration Worksheets Configuration Worksheets Before you start NMMGR, use the worksheets provided here to gather the necessary configuration information. Make copies of these worksheets and fill in the parameter information, then use the worksheets to guide you through configuration in NMMGR.
Preparing to Configure DTCs Configuration Worksheets DTC Configuration Worksheet Fill out worksheet as shown in Figure 2-2 for each DTC you are configuring.
Preparing to Configure DTCs Configuration Worksheets DTC Card Configuration Worksheet Fill out worksheet as shown in Figure 2-3 for each direct connect card you are configuring.
Preparing to Configure DTCs Configuration Worksheets DTC X.25 Card Configuration — Level 1 and Level 2 Worksheet Fill out worksheet as shown in Figure 2-4 for each DTC X.25 Network Access card you are configuring. Figure 2-4 DTC X.
Preparing to Configure DTCs Configuration Worksheets DTC X.25 Card Configuration – Level 3 & Miscellaneous Worksheet Fill out worksheet as shown in Figure 2-5 for each DTC X.25 Network Access card you are configuring.& Figure 2-5 DTC X.
Preparing to Configure DTCs Configuration Worksheets DTC X.25 Card Configuration — System-to-System Worksheet Fill out worksheet as shown in Figure 2-6 for each DTC X.25 Network Access card for which you are configuring system-to-system connections. Figure 2-6 DTC X.
Preparing to Configure DTCs Configuration Worksheets DTC X.25 Card Configuration – Nailed PAD Worksheet Fill out worksheet as shown in Figure 2-7 for each DTC X.25 Network Access card for which you are configuring nailed PAD connections. Figure 2-7 DTC X.
Preparing to Configure DTCs Configuration Worksheets DTC X.25 Card Configuration — PAD Security Worksheet Fill out worksheet as shown in Figure 2-8 for each DTC X.25 Network Access card for which you are configuring PAD security. Figure 2-8 DTC X.
Preparing to Configure DTCs Configuring With NMMGR Configuring With NMMGR NMMGR, the Node Management Configuration Manager, is the utility used by HP 3000 Series 900 to configure asynchronous device connections. The parameters described previously in this chapter are entered in NMMGR through a screen-by-screen user interface. These parameters are then stored by NMMGR into the HP 3000 network configuration file NMCONFIG.PUB.SYS.
Preparing to Configure DTCs Configuring With NMMGR Figure 2-9 NMMGR DTS/DTC Screen Flow 44 Chapter 2
Configuring DTCs Step-by-Step 3 Configuring DTCs Step-by-Step This chapter provides step-by-step instructions for configuring Datacommunications and Terminal Controllers (DTCs) for systems using host-based network management. If you are using this manual to configure DTCs, it is assumed that X.25 network connections will be part of the host-based configuration. Before using NMMGR to configure DTCs, you should complete the worksheets provided.
Configuring DTCs Step-by-Step Network Configuration Overview Network Configuration Overview Information required for network configuration on the host is contained in one file. The name of this configuration file is NMCONFIG.PUB.SYS. When building a new configuration file, it is not necessary to define every field. This is because a sample configuration file is supplied with the MPE/iX operating system. The sample configuration file is called NMSAMP1.PUB.SYS.
Configuring DTCs Step-by-Step Copy the Sample File Copy the Sample File Use NMSAMP1.PUB.SYS as a template for first time configuration. This file is supplied with the MPE/iX operating system. Do not modify NMSAMP1.PUB.SYS. Instead, copy the sample configuration file into NMCONFIG.PUB.SYS and then modify the file as necessary. To copy NMSAMP1.PUB.SYS into NMCONFIG.PUB.SYS, enter these commands at the MPE/iX prompt (:): HELLO MANAGER.SYS,PUB FILE CONFIG=NMCONFIG.PUB.SYS;DEV=1 FCOPY FROM=NMSAMP1.PUB.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Modify the Network Management Configuration File The network management configuration file (NMCONFIG.PUB.SYS) contains information that is referenced during system boot-up. A step-by-step procedure for creating or updating the host’s network management configuration file follows. NOTE Before modifying the NMCONFIG.PUB.SYS file, make a backup copy of it.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-1 Open Configuration/Directory File Screen Follow the steps listed here to enter data for this screen. Refer to “Fields” subsection on the next page for detailed information about each field on the screen. 1. NMCONFIG.PUB.SYS is the name required by the software. Verify that this name is displayed in the Configuration file name field. 2.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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).
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-2 Main Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 The Host Configuration screen is displayed when you press the [DTS] function key at the Main screen (Figure 3-3).
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 The DTC Configuration Selection screen (Figure 3-4) is displayed when you press the [Go To DTC] key at the Host Configuration screen. Here you specify the type of DTC to configure.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 6: Specify DTC Configuration The DTC Configuration screen is displayed after you select the DTC type at the DTC Configuration Selection screen. Figure 3-5 shows the DTC Configuration screen for a DTC 72MX. (DTC Configuration screens for DTC 16iX, DTC 16MX/RX, DTC 16, and DTC 48 vary slightly). Figure 3-5 DTC Configuration Screen 1. Enter the DTC’s name in the “DTC name” field.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-6 DTC Card Configuration Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Card number Display only. Port Group Type (Optional) Ldev The valid type are D for direct connect and M for modem connect. The default is D. 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-7 DTC X.25 Card Configuration Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File values for both system-to-system access and for PAD access. You can also reach this screen by typing the following path at the Command line and pressing the [ENTER] key: @DTS.DTC.SELECT.dtcname.X25CARDn.LEVEL12 Figure 3-8 DTC X.25 Card Configuration — Level 1 and 2 Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File CCITT X.25 Standard Frame size (N1) Version of the CCITT X.25 standard you are using, either 1980 or 1984. 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File address and the maximum number of PAD connections that will be allowed if PAD is supported. You must configure the level 3 values for both system-to-system access and for PAD access. You can also reach this screen by typing the following path at the Command line and pressing the [ENTER] key: @DTS.DTC.SELECT.dtcname.X25CARDn.LEVEL3 Figure 3-9 DTC X.25 Card Configuration — Level 3 & Miscellaneous Screen 1.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-10 DTC X.25 Card Configuration — Sys-to-Sys LUGs Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 NMMGR displays the DTC X.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Figure 3-12 DTC X.25 Card Configuration — PAD Security Screen 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 14: Validate/Cross-Validate the Configuration File Validation ensures that no conflicts exist in the network configuration file (NMCONFIG.PUB.SYS) between the DTCs and other configuration parameters. After NMMGR validates the network configuration file, it will automatically cross-validate the file with the system I/O devices configured through the SYSGEN utility.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 3. After successful validation and cross-validation, and if the file in use is NMCONFIG.PUB.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File NOTE 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 First, logoff any sessions. To reset the DTC, turn off the power and then turn on the power again for the DTC. You may also use TermDSM, an online diagnostic program for host-managed DTCs, to reset the DTC.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 86 Chapter 3
Terminal and Printer Profiles 4 Terminal and Printer Profiles This chapter provides an overview of the purpose and usage of terminal and printer profiles. Additional detailed information is provided that is specific for PAD devices. This information describes the PAD profile byte, using the PAD password, and forced data forwarding. This chapter also contains a list of features controlled by the PAD profile byte.
Terminal and Printer Profiles What is a Profile What is a Profile A profile is a group of device connection specifications and characteristics that can be associated with devices. Profiles can be associated with terminals, printers, PAD terminals and printers, and UPSs. The word profile is used in two different contexts in this chapter. When a ldev is configured on the MPE/iX system, a profile name is associated with each ldev. This association is configured on the DTC Card Configuration screens.
Terminal and Printer Profiles What is a Profile Printer Profiles Printer profiles define the characteristics of ldevs that are connected to printers, or other devices that are intended to only receive data from the DTCs. Devices that use these profiles are usually connected directly to the DTC ports or are connected through a modem over a phone line. PAD Terminal Profiles PAD terminal profiles define the characteristics of ldevs that are used by devices that are connected to the HP 3000 through a PAD/X.
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles System Supplied Terminal and Printer Profiles The Host-Based Terminal Profiles as shown in Table 4-1 lists the terminal and printer profiles supplied by the MPE/iX system for host-based and PC-based management. You may choose these profiles for your terminal and printer configuration. You may also create your own profiles.
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Profile Name Characteristics Suggested Devices TR10U12 Terminal type 10 Record width of 80 bytes Modem type 1 (US modem) Parity: none Speed/Parity Sensing? N Reset HP Terminals? N Allow :HELLO logon? Y NLIO devices? N No device classes assigned Supported HP terminals US modem connection Set at 1200 bps TR10U24 Terminal type 10 Record width of 80 bytes Parity: none Speed/Parity Sensing? N Reset HP Terminals? N Allow :HELLO lo
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 4-2 Host-Based Printer Profiles Profile Name Characteristics Suggested Devices PR18D24 Printer type 18 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: LP Printers with no status checking Connected directly Set at 2400 bps PR18D96 Printer type 18 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: LP Printers with no status checking Connected directly Set at 9600 bp
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Profile Name Characteristics Suggested Devices PR26D96 Printer type 26 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: LP Supported HP printers Connected directly Set at 9600 bps PR26PAD Printer type 26 Record width of 132 bytes Spooled No NLIO devices PAD test requested? Y Send initial profile? Y X.
Terminal and Printer Profiles DTC PAD Profile Field DTC PAD Profile Field The profile number used by the PAD is the decimal value of the binary number calculated from Table 4-3 as done by the [Compute Byte] function key. An “x” in a box means that the value doesn’t matter: that is, the values of the bits are not dependent on each other. Bit 7 is reserved for future use, and is set to 0. Note that you can only use certain combinations: meaningless or dangerous combinations are blocked and cannot be entered.
Terminal and Printer Profiles DTC PAD Profile Field PAD Profiles and Access Password When users attempt to establish a connection from a PAD, the PAD selection command may specify a password and/or a profile number. The password will be needed if a password has been configured for the DTC that contains the X.25 card being called. The profile number may be specified to override the PAD profile field configured for the PAD port.
Terminal and Printer Profiles DTC PAD Profile Field character mode when EOR and AEOR are not carriage return. The value in the field is not used during a connection when in character mode and EOR or AEOR is carriage return. In this case the default values will be used: parm #3 is 2 and parm #4 is 0. When the “Forced data forwarding” bit is 1, the data forwarding parms #3 and #4, that are set at connection time in the PAD, are ALWAYS used.
Terminal and Printer Profiles DTC PAD Profiles DTC PAD Profiles Table 4-4 shows the usable DTC PAD profiles and their recommended usage. You must not use profiles 18, 45 and 50, even though they are available. All other numbers are blocked, and cannot be entered. Table 4-4 Profile 1 Terminal PAD Profiles Definition PAD Test Init profile X.3 setting Data Forward default Usage Default terminal profile. Does not need to be entered in the CALL User Data.
Terminal and Printer Profiles DTC PAD Profiles Profile 13 Definition PAD Test Init profile X.3 setting Data forward 4:2 Usage Used in data transfer. Recommended for more performance in iX for VPLUS mode (NS/PAD compatibility) or for character mode applications which need to send few characters to the host. The profile loads the X.25 line with many, small packets each time the application requires a termination character other than CR. The PAD must support 4:2. 17 PAD Test Init profile No X.
Terminal and Printer Profiles DTC PAD Profiles Profile 39 Definition No PAD test No init profile X.3 setting Data forward 3:127 Usage Used at connection establishment and during data transfer. Recommended if you want to combine profiles 35 and 5. The PAD must support the X.3 settings needed by the applications and the 3:127 data forwarding. 41 No PAD test No init profile X.3 setting Data forward 4:1 Used at connection establishment and during data transfer.
Terminal and Printer Profiles DTC PAD Profiles Profile 93 Definition Usage PAD test Init profile No X.3 setting Data forward 4:2 Forced data forwarding Used at connection establishment and during data transfer. This profile is advised when you want to force the data forwarding value selected. The PAD must support the 4:2 data forwarding. 117 No PAD test Init profile No X.3 setting Data forward 3:127 Forced data forwarding Used at connection establishment and during data transfer.
Terminal and Printer Profiles DTC PAD Profiles Table 4-5 Printer PAD Profiles Profile Definition 2 PAD test Init profile X.3 setting Data forward default Usage Default printer profile. Direct replacement for the “Printer” device type of releases prior to 12.0. Ensures DTC 2.0 to 10.5 backward compatibility. 18 PAD test Init profile No X.3 setting Data forward default Used in data transfer. 32 No PAD test No init profile X.3 setting Data forward default Used at a connection initialization.
Terminal and Printer Profiles DTC PAD Profiles 102 Chapter 4
Preparing to Configure X.25 iX System Access 5 Preparing to Configure X.25 iX System Access This chapter details the information you will need before you can begin to configure X.25 iX System Access for host-based systems that will include an X.25 system-to-system link. Sample worksheets are included to ease configuration. Hewlett-Packard recommends that you configure the datacommunications and terminal subsystem (DTS) before configuring the NS X.25 link.
Preparing to Configure X.25 iX System Access Plan the Network Configuration Plan the Network Configuration Before you begin the process of configuring the X.25 iX System Access link, you must define the physical layout and configuration parameters for the system-to- system network connections that will be required for the system you are configuring. Once you have determined what the configuration should be, you can begin the process of entering the configuration values into NMMGR.
Preparing to Configure X.25 iX System Access Plan the Network Configuration Parameter/Value Screen Comment Hops Neighbor Gateway Reachable Networks Number of hops (full gateways) needed to get from the system being configured to the reachable network. IP address X.25 Configuration The internet protocol (IP) address of the system (node) being configured. IP subnet mask X.25 Configuration Optional. Identifies which bits of the IP address will be used to define a subnetwork. Link name X.
Preparing to Configure X.25 iX System Access Plan the Network Configuration Parameter/Value Screen Comment Remote node name X.25 Virtual Circuit Configuration In the network directory, name of each remote X.25 node on the network. Remote X.25 address X.25 Virtual Circuit Configuration For SVCs only. In the network directory, the X.25 address of the remote host for X.25 public data networks or private networks. Security class X.25 Virtual Circuit Configuration For SVCs only.
Preparing to Configure X.25 iX System Access Determine X.25 iX System Access Network Characteristics Determine X.25 iX System Access Network Characteristics You must define the characteristics of the X.25 iX System Access link or links that you will be configuring. You must specify a link name and configuration for each DTC/X.25 Network Access card that will be used for X.25 system-to-system connections. Several of the parameters that you will configure for X.
Preparing to Configure X.25 iX System Access Determine X.25 iX System Access Network Characteristics X.25 Configuration Worksheet Fill out worksheet as shown in Figure 5-1 for the X.25 iX System Access links you are configuring. Figure 5-1 X.
Preparing to Configure X.25 iX System Access Determine X.25 iX System Access Network Characteristics X.25 Virtual Circuit Configuration Worksheet Fill out worksheet as shown in Figure 5-2 for each X.25 iX System Access link you are configuring. Figure 5-2 X.
Preparing to Configure X.25 iX System Access Identify Neighbor Gateways Identify Neighbor Gateways This section only applies if one of the nodes on your network is a gateway. A neighbor gateway is a gateway that is on the same network as a given node. A non-gateway node on a network may need to go through a neighbor gateway in order to send messages to an entirely different network. Two nodes are on the same network if the network portion of their IP addresses are the same. All X.
Preparing to Configure X.
Preparing to Configure X.
Configuring X.25 Links Step-by-Step 6 Configuring X.25 Links Step-by-Step This chapter provides step-by-step instructions for configuring X.25 iX System Access for systems using host-based network management. This manual assumes that you are using the guided configuration capabilities of NMMGR. Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 5, “Preparing to Configure X.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Modify the Network Management Configuration File The procedures that follow describe how to modify the NMMGR configuration file and network directory file for X.25 iX System Access configuration. These procedures assume that you have already configured the datacommunications and terminal subsystem (DTS) for this system. See Chapter 3, “Configuring DTCs Step-by-Step,” for information on DTS configuration.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Figure 6-1 Open Configuration/Directory File Screen 1. Verify that the correct configuration file name, backup configuration file name, and network directory file name are in the appropriate fields 2. If you have assigned a write access password, enter it in this field. If you are not using the password feature, leave this field blank. 3. Press the [Open Config] key.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Figure 6-2 Main Screen 1. You should already have configured a local node name and entered the other information required for this screen. Verify that the information is correct 2. Press the [NS] key to select the NS configuration branch. 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Figure 6-3 NS Configuration Screen 1. If you are using domain names for network access, replace the node name in the field at the bottom of the screen with this system’s domain name and press the [Save Data] key. If not using domain names, leave the local HP 3000 node name in this field. 2. Press the [Guided Config] key to proceed with guided configuration of X.25 iX System Access.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Step 5: Perform Guided Network Transport Configuration NMMGR displays the Network Transport Configuration screen (Figure 6-4) if you press the [Guided Config] key at the NS Configuration screen. Figure 6-4 Network Transport configuration Screen 1. Next to the words Enter a network interface:, enter a name for the network interface (for example, X25NI). 2.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File name, it will be easier to remember if you make the NI name the same for all nodes on the same network (for instance, X25net1). You will use the NI name with the NETCONTROL command to start the transport and network link. NOTE You can have more than one X.25 NIs configured for the same X.25 card on one MPE/iX system, but only one can be running at any one time.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Figure 6-5 X.25 Configuration Screen 1. In the IP address field, enter the internet protocol (IP) address for the node being configured. An example of an address is: C 192.191.191 009 2. The IP subnet mask is optional. If entering one, tab to the IP subnet mask field and enter the number in the same format as an IP address.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File 6. If the network that this node is on contains ANY internetwork gateway (either full or half) press the [Neighbor Gateways] key and proceed to the section in this chapter called “Configure Neighbor Gateways.” 7.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File such items as the node name and IP address of each node. If there is no record, and if you want to find out each node’s IP address, you will have to issue the following command (NM capability required) on each of the nodes: NETCONTROL NET=NIname;STATUS The last line of output from this command tells you what the complete IP address is for that node; the last three digits are the unique node portion of the address.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Figure 6-6 X.25 Virtual Circuit Configuration Screen 1. In the Remote node name field, enter, in turn, the nodename of each remote X.25 node on your network in the format nodename.domain.organization. Also, if you need to be able to perform a loopback DSLINE command to the local node, then enter the local HP 3000 node's name here as well. 2.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File a. In the Remote X.25 address field, enter the X.25 address of the remote host for X.25 public data networks or private networks. b. Make sure the name of the facility set you are using is in the Facility set field. You may either choose the default facility set (STDSFSET) or enter an alternative. If you are configuring a new facility set, enter a new name.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File its full name is node.domain.organization). You must configure an X.25 address key for each remote node with which your node will be communicating. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. The X.25 address key name must be eight characters or less and the first character must be alphabetic.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Security Class The security class is the level of logical security you want to have when a connection is made to or from the specified remote node. A Security level is required for SVCs if you have specified an X.25 Address Key. The possible values are as follows: • IO—Both incoming and outgoing calls are accepted. This is the default value. • IN—Only incoming calls are accepted from this particular remote address.
Configuring X.25 Links Step-by-Step Configure Neighbor Gateways Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. (Go back one level by pressing the [Prior Screen] key, then select [Neighbor Gateways] key).
Configuring X.25 Links Step-by-Step Configure Neighbor Gateways 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring. 2. If you are adding the identified gateway for the first time, press the [Add] key. If you are modifying the configuration of this node, press the [Modify] key. The Neighbor Gateway Reachable Networks screen will be displayed. Proceed to “Identify Neighbor Gateway Reachable Networks.” 3.
Configuring X.25 Links Step-by-Step Configure Neighbor Gateways 2. In the IP Network Address fields under the title Configured Reachable Networks, enter the IP addresses of all the remote networks that can be reached through the gateway whose IP address is configured in the previous field. 3. The IP subnet mask is optional. If entering one, tab to the next field. In the IP subnet mask field, enter the number in the same format as an IP address.
Configuring X.
Managing Networks with DTCCNTRL 7 Managing Networks with DTCCNTRL This chapter describes the syntax of the DTCCNTRL command and how it is used. DTCCNTRL is a command file that is used to start, stop, and obtain status about host-based X.25 system-to-system and PAD connections; dynamically implement changes that were made to the DTS subsystem in NMMGR; shutdown and restart the DTS subsystem; automatically add a new DTC.
Managing Networks with DTCCNTRL DTCCNTRL Parameters DTCCNTRL Parameters Dynamically implements DTS changes made in NMMGR. Initiates automatic configuration of DTCs. Shuts down and restarts the DTS subsystem. Starts, stops, and controls the operation of host-based X.25 connections. See the following sections for further information on each of the following functions.
Managing Networks with DTCCNTRL DTCCNTRL Parameters STARTPADSUP Activates PAD support services on the specified card. X.25 services must already be active. STARTBOTH Activates both X.25 and PAD support services on the specified card. STOPX25 Deactivates X.25 services on the specified card. If PAD support services are active, they must be deactivated prior to entering this command. STOPPADSUP Deactivates PAD support services on the specified card. X.25 services remain active.
Managing Networks with DTCCNTRL DTCCNTRL Menu DTCCNTRL Menu If DTCCNTRL is invoked without the FUNC=function parameter, the following menu will be displayed. Enter the number for the desired function at the prompt. DTCCNTRL will prompt for additional information if needed. If the DTS Shutdown function is selected the FORCED=Y option can not be selected.
Managing Networks with DTCCNTRL Dynamic Configuration Dynamic Configuration Dynamic Configuration enables you to change the configuration of the DTS subsystem by applying the configuration changes made in NMMGR without rebooting the system. Such configuration changes include adding or deleting ldevs, adding or deleting DTCs, modifying most parameters of profiles, or DTCs, changing the number of non-nailed ldevs. See for a complete list of changes that can be made dynamically.
Managing Networks with DTCCNTRL Dynamic Configuration Table 7-1 Dynamically Configurable Tasks Task Add/configure new terminal/printer Add/delete class name Change DTC event logging class Host-based X.25 configuration changes: Action Required for Change to Become Active No action; changes take effect dynamically • maximum number of PAD connections • X.25 link name • remote X.25 addresses and security • X.25 allow access • remote X.
Managing Networks with DTCCNTRL Dynamic Configuration Task Action Required for Change to Become Active Host-based X.25 configuration changes: Use DTCCNTRL to: • change PAD access 1. Stop X.25/PADSUP • change level 1, 2, or 3 configuration 2. Start X.25/PADSUP (see Configuring Systems for Terminals, Printers, and Other Serial Devices for more information) Add/configure new DTC Reboot or reset DTC or Perform automatic configuration Add/configure a TIO carD 1.
Managing Networks with DTCCNTRL NMCONFIG and NMCONFIX Files NMCONFIG and NMCONFIX Files Dynamic Configuration uses both files NMCONFIG.PUB.SYS and NMCONFIX.PUB.SYS to manage the devices created by the DTS subsystem. When users wish to make any dynamic change, NMMGR will be used to modify the configuration in NMCONFIG.PUB.SYS. When DTCCNTRL is invoked, either within or from outside of NMMGR, NMCONFIG will be compared to NMCONFIX and the desired changes will be made to the system configuration.
Managing Networks with DTCCNTRL NMCONFIG and NMCONFIX Files 2. After successful validation and cross-validation, NMMGR will prompt you as to whether you want DTS changes to take effect now. The following prompt will appear: Do you want DTS changes to be become active now (Y/N)? Y = all changes made take effect now N = all changes made will take effect upon next dynamic configuration or system boot H = help > If you type Y, dynamic configuration changes will take effect now.
Managing Networks with DTCCNTRL Automatic Configuration of DTCs Automatic Configuration of DTCs Automatic configuration provides the capability to add, and configure a new host-based managed DTC to the HP 3000 system without the need to specify most of the detailed configuration information. You can initiate automatic configuration using the DTCCNTRL command at the CI prompt, or from within NMMGR. This section describes how to start automatic configuration at the CI prompt.
Managing Networks with DTCCNTRL Automatic Configuration of DTCs At the prompt “The default DTC node name is DTCXXXX.domain.organization. Press RETURN to continue or enter the DTC node name to overwrite default:” press the [Return] key to continue or enter a different DTC node name to overwrite the default. 5. At the prompt “Enter optional DTC IP address in the format of n.n.n.n or press RETURN to continue:” enter the optional DTC IP address or press the [Return] key to continue.
Managing Networks with DTCCNTRL Obtaining Status Using DTCCNTRL Obtaining Status Using DTCCNTRL The DTCCNTRL STATUS function displays the current status of each DTC/X.25 Network Access card installed in a specified DTC. The command displays the DTC type (16, 48 or 72MX) and the software module that is currently active on any DTC/X.25 Network Access cards that are installed. (Asynchronous cards installed in the DTC are not displayed.
Managing Networks with DTCCNTRL DTS Shutdown and Restart DTS Shutdown and Restart The DTS shutdown capability is provided by the DTCCNTRL command. It allows you to bring down the entire DTS subsystem and includes the release of all TIO-related system resources. DTCCNTRL requires that you have a minimum of System Manager (SM) capability, this operation can only be done from the system console.
Managing Networks with DTCCNTRL X.25 and PAD Services Control X.25 and PAD Services Control X.25 and PAD support services may both be started individually, through the STARTX25 and STARTPADSUP functions respectively, or they may be started at the same time, through the STARTBOTH command. When they are started through individual commands, the STARTX25 command must be entered before the STARTPADSUP command. Conversely, X.
Managing Networks with DTCCNTRL DTCCNTRL Examples DTCCNTRL Examples Following are examples of using the DTCCNTRL command to control the operations of a DTC/X.25 Network Access card. In these examples, the card is mounted in slot 3 of a DTC with the node named DTC1.NET.IND. Start X.25 support services: :DTCCNTRL DTC=DTC1.NET.IND;CARD=3;FUNC=STARTX25 Start PAD support services (X.25 must already be started): :DTCCNTRL DTC=DTC1.NET.IND;CARD=3;FUNC=STARTPADSUP Start both X.
Managing Networks with DTCCNTRL DTCCNTRL Examples 148 Chapter 7
Formatting Host-Based X.25 Log Files 8 Formatting Host-Based X.25 Log Files As described in Chapter 1, “Introduction,” you use a special formatting tool, EVLOG, to format host-based X.25 log files. You cannot use the NMDUMP formatter for these files. This chapter describes the event log formatter and provides instructions for its use. Included in this chapter you will find information on the following: • A description of the EVLOG formatter, including limitations. • Instructions for running EVLOG.
Formatting Host-Based X.25 Log Files The EVLOG Formatter The EVLOG Formatter The EVLOG formatter provides a user interface that is similar to the NMDUMP interface with options set in the same manner as for NMDUMP. EVLOG also provides some filtering capability, including filtering on host-based time. See the descriptions of formatting options later in this chapter. NOTE This formatter is only intended to be used on log files with X.25 and PAD events.
Formatting Host-Based X.25 Log Files To Use EVLOG To Use EVLOG You can run EVLOG using default options or you can run EVLOG interactively to select and modify specific options. Instructions for each run mode follow. The options are described in the remainder of this chapter. To Run EVLOG Using Default Options Follow these steps to format a host-based X.25 log file using the default options. 1. Copy the file that you want to format to a different file name.
Formatting Host-Based X.25 Log Files To Use EVLOG The following display will appear: EVLOG C.00.00 001 File type = 7 (Version = A1200D00) Options: 0 1 2 3 4 5 6 7 8 9 — — — — — — — — — — ? — Set all options back to their default values File Records Event types Subsystems Event Codes Logical Channel Identifier (LCI) Virtual Port Number (VPN) Time/offset format Time/offset (1970–2020) (MYFILE, 0 records) (1..0) (ALL) (ALL) (1..2147483647) (ALL) (ALL) (HOST time) (70-01-01-00-00-00...
Formatting Host-Based X.25 Log Files To Use EVLOG Enter number of option or to select current options: 2 First record [1]? 2 Last record [15]? 5 Options: 0 1 2 . . . — — — — — — Set all options back to their File Records . . . . . . . . . . . . . . . default values . . . . . . . . . (logfile1, 15 records) (2..5) . . . . . . . . . . . . Option 3: Event Tapes. Use this option to restrict the records displayed to those of a specific event type.
Formatting Host-Based X.25 Log Files To Use EVLOG Options: 0 1 2 3 4 . . . — — — — — — — — Set all options back to their File Records Event types Subsystems . . . . . . . . . . . . . . . default values . . . . . . . . . (logfile1, 15 records) (1..0) (3) (4) . . . . . . . . . . . . Option 5: Event Codes. Use this option to specify a range of event codes to be displayed. To specify the codes, you may enter either the event code numbers or the mnemonics listed in the prompt display.
Formatting Host-Based X.25 Log Files To Use EVLOG Options: 0 1 2 3 4 5 6 . . . — — — — — — — — — — Set all options back to their default values File Records Event types Subsystems Event codes Logical Channel Identifier (LCI) . . . . . . . . . . . . . . . . . . . . . . . . (logfile1, 15 (2..5) (3) (4) (3584..4607) (ALL) . . . . . . records) . . . . . . Option 7: Virtual Port Number (VPN). Use this option to restrict the records displayed to those for a particular virtual port number (VPN).
Formatting Host-Based X.25 Log Files To Use EVLOG Enter number of option or to select current options: 8 Time formats: 1 2 3 4 5 — — — — — HOST PC DTC CPU DTC SNP Record offset Time format [1]? 1 Options: 0 1 2 3 4 5 6 7 8 . . — — — — — — — — — — — Set all options back to their default values File Records Event types Subsystems Event codes Logical Channel Identifier (LCI) Virtual Port Number (VPN) Time/offset format . . . . . . . . . . . . . . . . (logfile1, 15 records) (2..5) (3) (4) (3584..
Formatting Host-Based X.25 Log Files Displaying the Data Displaying the Data After you have set the display options, press [RETURN] to display the formatted logging information. Your display will look similar to the following: Enter number of option or to select current options: T Y Evnt P # YYMMDDHHMMSS E — – 2 911004145508 3 Try Again? (NO) Time/Offset S U B S Y S – 4 > Evnt Code Description DTC Name C A R D 3604 Host Conn.
Formatting Host-Based X.
Error Messages A Error Messages This Appendix contains validation, datacommunication configurator (DCC), and DTCCNTRL error messages. Validation errors indicate problems with the network management configuration file. They are detected during NMMGR configuration when you attempt to validate the network management configuration file. DCC errors indicate problems with the link or the DTS manager. They are detected when the system is rebooted.
Error Messages Validation Error Messages Validation Error Messages The network management configuration file must be validated before automatic cross-validation with SYSGEN takes place. The DTS validation procedure starts by displaying the following: -> Validation of DTS/LINK started. Validation of DTS/LINK finished.
Error Messages Validation Error Messages Action: Go back to the screen specified by the NMMGRpath or go to the link screen specified by the linkname and modify the physical path. Path: NMMGRpath — The same station address is being used at LINK.linkname. (DTSERR=7) (DTSERR 7) Cause: The IEEE 802.3 station address is already used. Each station address must be unique. Action: Go back to the screen specified by the NMMGRpath or go to the screen specified by the linkname and correct the station address.
Error Messages Validation Error Messages Action: Go to one of the two screens and change the ldev number. The ldev number must be unique for each port. Path: NMMGRpath — LDEV #nnn is too big (must be <=4679). (DTSERR=14) (DTSERR 14) Cause: The logical device (ldev) number is bigger than the allowed maximum ldev number. Action: Go to the screen specified by the NMMGRpath and modify the ldev number. Path: NMMGRpath — Too many LDEVs are being used (must be <=4649).
Error Messages Validation Error Messages Path: NMMGRpath — Too many nodes are being used (max. number allowed = 129). (DTSERR=21) (DTSERR 21) Cause: The DTC specified in the NMMGRpath cannot be processed. Too many nodes are being used. Action: Go back to the DTC Configuration screen and delete the DTC specified in the NMMGRpath. Path: NMMGRpath — Too many classes are being used (max. number allowed = 1000). (DTSERR=22) (DTSERR 22) Cause: The total number of classes exceeds the maximum allowed number.
Error Messages Validation Error Messages Action: Remove the class name from the profile for the ldev and delete and re- add the ldev. Cross-validate the NMCONFIG.PUB.SYS file with SYSGEN. Correct any problems found then restart DTS. Path: NMMGRpath — Must supply a Physical Path. (DTSERR=32) (DTSERR 32) Cause: A physical path was not specified in the Physical Path of LANIC field. Action: Go to the DTS Configuration screen and enter the appropriate physical path.
Error Messages Validation Error Messages Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD012.PAD2. (DTSERR=40) (DTSERR 40) Cause: A PAD name is used more than once. Action: Remove all of the duplicate references to the PAD name. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD3. (DTSERR=41) (DTSERR 41) Cause: A PAD name is used more than once. Action: Remove all of the duplicate references to the PAD name.
Error Messages Validation Error Messages Action: Remove the duplicate ldev number. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD5. (DTSERR=49) (DTSERR 49) Cause: The same logical device (ldev) number is used more than once. Action: Remove the duplicate ldev number. Path: NMMGRpath — The same LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD012.
Error Messages Validation Error Messages Action: Change the PAD terminal or PAD printer profile to be a terminal or printer profile. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=59) (DTSERR 59) Cause: The same PAD device name is used more than once in the configuration. Action: Remove any duplicate references to the PAD device name. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD012.PAD1.
Error Messages Validation Error Messages Path: NMMGRpath — The same LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD012.PAD1. (DTSERR=66) (DTSERR 66) Cause: The logical device (ldev) number is used more than once in the configuration. Action: Remove any duplicate references to the ldev number. Path: NMMGRpath — The same LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD012.PAD2. (DTSERR=67) (DTSERR 67) Cause: The logical device (ldev) number is used more than once in the configuration.
Error Messages Validation Error Messages (DTSERR 72) Cause: Hardware handshaking is not supported for devices on a DTC 16 or DTC 48. Hardware handshaking is being specified for LDEV #nnn, which is on a DTC 16 or DTC 48. Action: Make sure you have specified the right DTC type (not a DTC 16 or DTC 48), or if you are configuring ports on a DTC 16 or DTC 48, do not use a profile that specifies hardware handshaking. Path: NMMGRpath — Modem behavior is not supported.
Error Messages Validation Error Messages Action: Ports using HOST profiles are for back-to-back and must have an ldev of -l. Go to the screen specified in NMMGRpath and change the ldev to -l or use a different profile that is not of type HOST. Path: NMMGRpath — X.25 card is not allowed in slot s. (DTSERR=79) (DTSERR 79) Cause: An X.25 card has been configured in a slot that is not allowed for the DTC type. Action: Go to the DTC specified in the NMMGRpath and delete the X.25 card from the slot number s.
Error Messages Validation Error Messages Path: NMMGRpath — Cardtype configured on card c not allowed on dtctype. (DTSERR=85) (DTSERR 85) Cause: The configuration for the DTC specified in NMMGRpath has been corrupted. Action: Delete the DTC specified in NMMGRpath and re-enter the data for this DTC. Path: NMMGRpath — Ldev #nnn> is not valid (must be >= -l and <=4679). (DTSERR=86) (DTSERR 86) Cause: The logical device (ldev) number is outside the allowed range.
Error Messages DCC Error Messages DCC Error Messages As system start-up nears completion, the Datacomm Configurator (DCC) creates the LINK and DTS managers. If the procedure is successful, the following message will be displayed on the console: DCC STARTUP OK! If the procedure is not successful, the message above is replaced by one or more error messages.
Error Messages DCC Error Messages Action: Validate the NMCONFIG.PUB.SYS file and restart DTS. If the error persists, replace the file, validate it, and restart DTS. DCC ERROR P-L, configuration record data was invalid. NM Path: NMMGRpath (DCCERR=5) (DCCERR 5) Cause: Data in the NMCONFIG.PUB.SYS file was not validated or the data is corrupt. Action: Validate the NMCONFIG.PUB.SYS file and restart DTS. DCC ERROR P-L, (HLIO status SSSSSSSS, ldev LLL).
Error Messages DCC Error Messages DCC ERROR P-L, link name specified for the DTS does not exist. (DCCERR=13) (DCCERR 13) Cause: The link name configured in NMMGR on the DTS Configuration screen does not exist. Action: Go to the DTS Configuration screen and enter the link name, then restart DTS. DCC ERROR P-L, link name specified for the DTS is not available (link status SSSSSSSS).
Error Messages DCC Error Messages DCC WARNING P-L, Configuration file close error SSSSSSSS. (DCCWARN=21) (DCCERR 21) Cause: A problem occurred while closing the NMCONFIG.PUB.SYS file or the NMCONFIX.PUB.SYS file. Action: Check that the files exist, and that adequate disk space is available for them. If the files exist and the disk space is large enough, check for file system or hardware problems. NLIO status SSSSSSSS, ldev LLL) (DCCERR=22) (DCCERR 22) Cause: A problem exists in the NLIO services.
Error Messages DCC Error Messages Action: For DTC 72MX, the valid range for card number is 0 to 3. For DTC 48, the valid range for card number is 0 to 5. For DTC 16, you may use card 0 and 1 for connector cards and card 2 for X.25 card. DCC ERROR P-L, Invalid DTC type specified, (DCC status SSSSSSSS. (DCCERR=28) (DCCERR 28) Cause: The NMCONFIG.PUB.SYS file may be corrupt.
Error Messages DCC Error Messages (DCCWARN 33) Cause: A class contains more than 255 devices, a conflict in class names exists, or NMCONFIG.PUB.SYS was not cross-validated with files created with SYSGEN. Action: The ldev is still usable but will not be in the class. Validate the NMCONFIG.PUB.SYS file and run SYSGEN to verify conflict. DCC ERROR P-L, Delete Ldev from class failure. (HLIO status SSSSSSSS, ldev LLL).
Error Messages DCC Error Messages Action: Logoff or stop the spooler on the devices that are still in use. Retry the DTS shutdown. DCC ERROR P-L, LLIO error (Status: SSSSSSSS, path: NMMGRpath) (DCCERR=41) (DCCERR 41) Cause: A problem exists with the low-level I/O services. Action: Contact your Hewlett-Packard support representative. DCC ERROR P-L, Too few non-nailed ldevs found.
Error Messages DCC Error Messages Action: This is a warning. If it persists contact your Hewlett-Packard support representative. DCC WARNING P-L, Ldev LLL is unusable until next DTS restart. (DCCWARN=49) (DCCWARN 49) Cause: The ldev was being accessed programmatically when a DTS Shutdown was performed and the forced=y option was specified. Action: Logoff the session or job that was accessing the device and restart DTS. Perform another DTS shutdown and restart.
Error Messages DCC Error Messages Action: Check that the file is not locked. If the file is not locked, check for file system or hardware problems. DCC WARNING P-L, (Startup) can not create NMCONFIX, status SSSSSSSS. (DCCWARN=104) (DCCWARN 104) Cause: A disk space problem, a file system problem, or a hardware problem exists. Action: Verify that enough disk space is available. If enough disk space is available, verify that no file system problems exist. Then, verify that no hardware problems exist.
Error Messages DTCCNTRL Error Messages DTCCNTRL Error Messages Two types of error messages can occur when a DTCCNTRL command is issued. The first type of error message is generated by the command interpreter (CI) process when a DTCCNTRL command is issued incorrectly. CI errors are listed first below. The second type of DTCCNTRL error message is generated when a DTCCNTRL operation fails (CTLERR messages) or when a warning is generated (CTLWARN messages).
Error Messages DTCCNTRL Error Messages Action: Reenter the command specifying a valid function in the FUNC parameter. For example: DTCCNTRL DTC=DTC.ITG.HP;CARD=4;FUNC=STARTX25 Valid functions are STARTX25, STARTPADSUP, STARTBOTH, RC, STOPX25, STOPPADSUP, STOPBOTH, and STATUS. ENCOUNTERED AN UNEXPECTED END-OF-LINE. (CIERR 10051) PARAMETERS DO NOT MATCH USER COMMAND DEFINITION. (CIERR 2039) CIERR 10051 Cause: More parameters were entered than are defined by the DTCCNTRL command.
Error Messages DTCCNTRL Error Messages Action: None. If attempting to control X.25 operation on a PC-based system, refer to the documentation for PC-based networks. Missing parameter: CARD not specified. (CTLERR 05) CTLERR 05 Cause: The DTCCNTRL command was issued with a FUNC parameter that requires a card number, but no CARD parameter was specified. The STARTX25, STARTPADSUP, STARTBOTH, RC, STOPX25, STOPPADSUP, and STOPBOTH functions all require the CARD parameter.
Error Messages DTCCNTRL Error Messages Or Issue a DTCCNTRL command with a function of STOPPADSUP, followed by a second DTCCNTRL command with a function of STOPX25. PAD switching list download failed. (CTLERR 11) CTLERR 11 Cause: An attempt was made to reconfigure PAD switching list values using the RC function of DTCCNTRL. A problem occurred with the DTC while the PAD support values were being downloaded. Action: Check the DTC.
Error Messages DTCCNTRL Error Messages SYS-TO-SYS switching download failed. (CTLERR 16) CTLERR 16 Cause: An attempt was made to reconfigure the system-to-system switching information (X.25 link name or number of switched virtual circuits) for the DTC using the RC function of DTCCNTRL. A problem occurred with the DTC while the new configuration values were being downloaded. Action: Check the DTC.
Error Messages DTCCNTRL Error Messages Action: Reenter the command with a valid RECONF specification. Valid values are ALL, X25, CARD, PASS, and LOGCL. Invalid specification for FORCED parameter. Must be y or n. (CTLERR 22) CTLERR 22 Cause: A DTCCNTRL command was entered using the FORCED option but an invalid value was specified in the FORCED parameter. Action: Reenter the command with a valid FORCED specification. Valid values are Y for “yes” and N for “no”. PAD download failed.
Error Messages DTCCNTRL Error Messages System error : NDM nm_find_port error, err_num = !, proc_num = !. (CTLERR 101) CTLERR 101 Cause: Internal error. Action: Contact your Hewlett-Packard support representative. System error : NDM get_sysbase error, err_num = !, proc_num = !. (CTLERR 102) CTLERR 102 Cause: Internal error. Action: Contact your Hewlett-Packard support representative. System error : bad status received from io_info_list, err_num = !, proc_num = !.
Error Messages DTCCNTRL Error Messages PAD already started. (CTLWARN 02) CTLWARN 02 Cause: A DTCCNTRL command was entered to stop PAD support but PAD support was already active. Action: No action required. This message is for information only. X25 already started. (CTLWARN 03) CTLWARN 03 Cause: A DTCCNTRL command was entered to start X.25 support but X.25 support was already active. Action: No action required. This message is for information only. X25 already stopped.
Glossary Glossary access port A special interface card in the system cabinet through which the system console is connected. address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key. address resolution In NS networks, the mapping of node names to IP addresses and the mapping of IP addresses to subnet addresses. address resolution protocol ARP.
Glossary directly accessible by people (for example, terminal keyboards) operate in this manner. asynchronous processor board The new 24-port mux board for the DTC 72MX. Allows up to 24 direct and modem connections per board. A DTC 72MX can have up to 3 asynchronous processor boards (for a total of 72 connections). attachment unit interface The cable that runs between each node (host, DTC, or other device) and the Medium Attachment Unit (MAU) that connects it to the LAN in a ThickLAN configuration.
Glossary block mode Terminal processing mode in which groups, or “blocks,” of data are transmitted all at once. BNC T-Connector Connector used to connect a computer or a component such as a DTC to the LAN in a ThinLAN configuration. boundary See network boundary. bps Bits per second. The number of bits passing a point per second. broadcast Communication method of sending a message to all devices on a link simultaneously. byte A sequence of eight consecutive bits operated on as a unit. call In X.
Glossary compatibility mode Processing mode on HP 3000 Series 900 computers that allows applications written for MPE V/E-based systems to be ported and run without changes or recompilation. computer network A group of computer systems connected in such a way that they can exchange information and share resources. configuration 1) The way in which computer equipment is physically interconnected and set up to operate as a system.
Glossary that it be consistent. For example, an automatic cross-validation occurs when you enter SYSGEN to assure that information contained in NMCONFIG.PUB.SYS agrees with system configuration data. CSMA/CD Carrier Sense Multiple Access with Collision Detect, transmission access method used by the IEEE 802.3 LAN standard. CSN See circuit-switching network. CTB The cache transfer bus in the backplane of an HP 3000. CUG See closed user group.
Glossary destination node name In DTS configuration, it is either 1) the name of a host that a user can be connected to by default (if switching is not enabled for that user, or if automatic modem connection is enabled), or 2) the name of the only host that can access a dedicated printer. device class A collection of devices that have some user-defined relation. Device classes are assigned through use of the NMMGR configuration utility.
Glossary host-based network management, and by the PC for DTCs managed by the OpenView DTC Manager. link supporting up to 32 virtual circuits at speeds of up to 19.2 Kbps. driver See device driver. DTC 16iX HP J2062A product. A DTC terminal server for HP 3000 systems. It allows up to 16 asynchronous (direct and modem) LAN connections to HP 3000 systems. DTC Datacommunications and Terminal Controller.
Glossary DTC 16TN HP J2060A product. A DTC terminal server for Telnet systems. It allows up to 16 asynchronous connections to computer systems running ARPA, such as HP 9000s and third party systems. DTC 48 HP 2345B product. A DTC that provides 6 slots for asynchronous connections, X.25 links, or Telnet Access. Each slot allows up to 8 direct connections or 6 modem connections. A DTC 48 may have up to 3 slots used for X.
Glossary DTC/X.25 Network Access card This is the hardware card and channel adapter that provides X.25 Network Access. It resides in the Datacommunications and Terminal Controller (DTC). DTC/X.25 iX Network Link Software and hardware that provides access to private and public X.25 networks. The X.25 iX System Access software resides on an HP 3000 host and is configured through use of NMMGR. DTE Data Terminal Equipment.
Glossary one or more other characters, used to convey control directives to printers, plotters, or terminals. transmitted as part of the control packets that establish and clear a virtual connection. Ethernet A Local Area Network system that uses baseband transmission at 10 Mbps over coaxial cable. Ethernet is a trademark of Xerox Corporation. FCS Frame Check Sequence. A sequence of bits generated by X.25 at level 2 that forms part of the frame and guarantees the integrity of its frame’s content.
Glossary flow control negotiation One of the network subscribed facilities, selected at subscription time. This facility allows the flow control parameter to be negotiated at call set-up time, as opposed to having a predefined value. formal file designator Name that can be used programmatically or in a file equation to refer to a file. FOS Fundamental Operating System. The programs, utilities, and subsystems supplied on the master installation tape that form the basic core of the operating system.
Glossary host-based network management Method of managing asynchronous communications for HP 3000 Series 900 computers. All of the control software is configured on a single host and is downloaded to the DTCs that are managed by that host. With host-based management, there is a permanent relationship between each DTC and the host, and terminal users can access only the single system that owns the DTC their terminal is connected to. host-based X.25 The management of X.
Glossary IEEE 802.3 multicast address A hexadecimal number that identifies a set of nodes. This address is used for multicast delivery. IEEE 802.3 nodal address A unique hexadecimal number that identifies a node on an IEEE 802.3 LAN. IEEE 802.5 A standard for a token ring network published by the Institute for Electrical and Electronics Engineers (IEEE). This standard is used for the Token Ring 3000/iX Network Link.
Glossary IP See Internet Protocol. IP address Internet Protocol address. An address used by the Internet Protocol to perform internet routing. A complete IP address comprises a network portion and a node portion. The network portion of the IP address identifies a network, and the node portion identifies a node within the network. IP subnet mask See subnet mask. ISO International Standards Organization.
Glossary characters except the first can be alphanumeric; the first character must be alphabetic. Local Area Network Interface Controller (LANIC) A hardware card that fits into the backplane of the HP 3000 Series 900 computer and provides a physical layer interface for local area networks. local connection See direct connection. local node The computer that you are configuring or that you are logged on to.
Glossary map, network A drawing that shows the topology of the network. For networks managed by the OpenView DTC Manager, a network map must be created through use of the OVDraw capability provided with the management software. A network map is also a hardcopy drawing used when planning a network. It shows network topology, node and network names, addresses, network boundaries (for an internetwork map), and link types.
Glossary nailed device A device with a permanently associated ldev that was assigned through the NMMGR configuration of the host system on which the association is established. Nailed devices can be accessed programmatically through their ldev number. In contrast, non-nailed devices have ldev numbers that are assigned from a pool of available ldev numbers for the life of their connection to a system. native mode The run-time environment of MPE/iX.
Glossary network boundaries (for an internetwork map), and link types. backup file is updated each time the configuration file is successfully validated. Network Services NS. Software application products that can be used to access data, initiate processes, and exchange information among nodes in the network. The NS 3000/iX Network Services include RPM, VT, RFA, RDBA, and NFT. NMCONFIG.PUB.
Glossary NMSAMP1.PUB.SYS Sample configuration file supplied with FOS that can be used as a template for DTS configuration. node A computer that is part of a network. The DTC is also considered to be a node and has its own address. node address The node portion of an IP address, which consists of a node portion and a network portion. Node Management Services Configuration Manager See NMMGR. node name A character string that uniquely identifies each system in a network or internetwork.
Glossary node to node over a defined route until it reaches its destination. This technique is referred to as store and forward. Systems in a point-to-point network are connected by means of leased or dial-up telephone lines. HP 3000 systems attach to the point-to-point network via HP 3000 Programmable Serial Interface (PSI) cards that fit into the back of each system’s SPU. by the DTC Manager, including monitoring and diagnostic functions. NSDIR.NET.SYS Name of the active network directory file.
Glossary Packet Exchange Protocol PXP. A transport layer protocol used in NS 3000/iX links to initially establish communication between nodes when NetIPC socket registry is used. packet-switched network name The name of a data communication network adhering to the CCITT X.25 recommendation. This can be a PDN or a private network, such as the HP PPN.
Glossary (for networks using OpenView Network Management) to define a printer by name. Can be shared by several printers (port pool). printer profile A set of configuration characteristics that can be associated with one or more printers through the NMMGR configuration. Printer profile specifications include the printer type, line speed, device class assignment, and other values relevant to printers connected through a DTC.
Glossary PSN Packet-Switching Network. Any data communication network using packet- switching techniques wherein data is disassembled into packets at a source interface and reassembled into a data stream at a destination interface. A public PSN offers the service to any paying customer. PSS Packet-Switching System. The national public PSN of the United Kingdom. PVC Permanent Virtual Circuit.
Glossary terminate other processes throughout a network from any node on the network. RS-232-C Electronic Industries Association (EIA) level 1 protocol specification that defines electrical circuit functions for 25 connector pins. HP provides two implementations of this standard: a 3-pin version for direct connections up to a distance of 15 meters (50 feet), and a version which makes use of additional circuits and can be used for either modem or direct connections.
Glossary SNMP agent A network node, such as a DTC, that is able to respond to SNMP requests. SNP Synchronous Network Processor card; an alternative name for an X.25 board. spooled device A printer that is accessed through the spooling facility. The spooling facility allows a nonsharable device to be shared among several users by temporarily storing output data on disk and managing the selection of output spool files destined for the spooled device.
Glossary system configuration The way you tell the operating system what peripheral I/O devices are attached and what parameters are required for system operation. TCP See Transmission Control Protocol. telenet A proprietary public data network in the USA. Telnet Access Card (TAC) A card that resides in the DTC 48 and provides protocol conversion between Telnet and AFCP. Telnet Express See HP ARPA Telnet Express. class assignment, and other values relevant to terminals connected through a DTC.
Glossary throughput class negotiation One of the network subscribed facilities defined at subscription time. This allows the user to negotiate the throughput class at call set-up time. timer (T3) Length of time that a link can remain in an idle state. After the expiration of the timer, the link is considered to be in a non-active, non-operational state and is automatically reset. The value should be chosen carefully.
Glossary typeahead A facility that allows terminal users to enter data before a read is actually posted to the terminal. UPS See uninterruptible power supply. unacknowledged frame number (K) The number of frames that can be transmitted without receiving an acknowledgment from the destination address. When this number (K) frame is reached, the same K frames are retransmitted. unedited mode See transparent mode.
Glossary X.25 Defines the interface between a DTE and a DCE for packet mode operation on a public data network (PDN). X.25 address The X.25 address provided by the network administration if you are connected to a public data network (PDN). X.25 address key An X.25 address key is a label that maps a node's IP address to its X.25 address and its associated X.25 parameters. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. X.25 LUG address X.
Glossary 218 Glossary
Index A accept PAD calls, 81 Address key, 127 address key, 125 Allow access, 81 allow access, 80 assigning node names, 52, 118 B backup configuration file, 50 backup configuration file name, 116 backup copies, 48 C Card Number, 68, 71 Card number, 75, 78 card number, 32, 124 card type, 58 CCITT X.25 protocol, 16 CCITT X.
Index subsystems, 153 time/offset format, 155 virtual port number, 155 EVLOG opton event types, 153 Extended packet sequence numbering, 73 extended packet sequence numbering, 71 F facility set, 126, 127 facility sets defined, 127 Flow control negotiation, 73 flow control negotiation, 71 force DTCCNTRL operation, 147 format log files, 151 formatter EVLOG, 150 formatting host-based X.
Index non-nailed device, 19 NS configuration, 117 NS configuration branch, 18 NS Configuration screen, 118 NSDIR.NET.
Index system X.
