Configuring and Managing Host-Based X.25 Links HP 3000 MPE/iX Computer Systems Edition 6 Manufacturing Part Number : 36939-90057 E0604 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 Host-Based Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nailed and Non-Nailed Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managed and Non-Managed DTCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 System-to-System Connections . . . . . . . . . . . . . . . . . . . . . .
Contents 3. Configuring DTCs Step-by-Step Network Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Copy the Sample File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Modify the Network Management Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Step 1: Begin the Configuration Process. .
Contents Modify the Network Management Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Begin the Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Open the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3: Select NS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 1-1. PAD Address Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Table 1-2. PAD Security Connection Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 4-1. Host-Based Terminal Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Table 4-2. Host-Based Printer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 8
Figures Figure 1-1. X.25 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Figure 1-2. Incoming PAD Security Flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 1-3. PAD Outgoing Security Flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 1-4. DTC PAD Switching examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 6-3. NS Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-4. Network Transport Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-5. X.25 Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6-6. X.25 Virtual Circuit Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 MP EXL 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 6, “Configuring X.25 Links Step-by-Step,” provides step-by-step instructions for configuring X.25 iX System Access for systems with host-based X.25 connections. • Chapter 7, “Managing Networks with DTCCNTRL,” describes how the DTCCNTRL command is used to start, stop, dynamically reconfigure, and obtain status about host-based X.25 system-to-system and PAD connections. Examples of command usage are included. • Chapter 8, “Formatting Host-Based X.
Related Publications Managing Host-Based X.
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: NOTE Chapter 1 • X.
Introduction Host-Based Network Connections Host-Based 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 four types of DTCs currently supported: DTC 72MX, DTC 16iX, DTC 16MX and the DTC 16RX. The DTC 72MX, is the only currently supported DTC can support the DTC/X.25 Network Access cards that make communications over X.25 networks possible.
Introduction Host-Based Network Connections 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. Any time a connection exists between a system and one of its nailed devices the same ldev number will belong to that device. This ldev number is reserved for the use of that connection and only that connection.
Introduction Host-Based Network Connections CAUTION The DTC MUST be defined as being managed by one and only one management platform. If a configuration for a DTC with the same LAN Station address is configured on more than one management platform, it is a race condition as to which platform will actually respond and download the DTC when the DTC is powered on. Usage of the management features such as reset on the other platform may have unpredictable affects on the DTC’s operations.
Introduction Host-Based X.25 and PAD Configuration Concepts Host-Based X.25 and PAD 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 and PAD Configuration Concepts (no) to the question “Are you using OpenView DTC Manager?” and “Y” (yes) to the question “Do you have X.25 system-to-system or PAD connections?”. Press the [Save Data] key, then press the [DTS] function key. Using the DTS configuration branch, you configure link information for the DTCs connected to the system.
Introduction Connections via PAD Support Connections via PAD Support Remote terminal users connecting via the DTCs PAD support use X.25 addresses to establish the connection to the DTC. When you configure PAD support on the DTC, you configure a PAD switching information table, which maps X.25 addresses to local systems. A remote terminal user who enters one of these X.25 addresses is automatically connected to the corresponding system.
Introduction Connections via PAD Support appear in the node names list can appear in an access list. The name can be an NS nodename or an IP address. You may have to enter more than one “version” of the same address, for example both the IP address and the Internet Services address of the same device, to allow users to enter either, and still gain access. When a remote PAD terminal calls into the DTC to connect to a local system, the DTC looks up the calling address in the PAD Incoming Security table.
Introduction Connections via PAD Support The following two flowcharts how incoming and outgoing calls are processed by the entries in the PAD tables. Figure 1-2 Incoming PAD Security Flowchart Incoming PAD call PAD Support Started? Yes No Clear Connection Does the PAD Switching table contain any entries? No Yes Is the called X.
Introduction Connections via PAD Support Figure 1-3 PAD Outgoing Security Flowchart FOPEN from host PAD support started? n y Device name and X.25 address listed in PAD Access table? n y Find if VC is available Clear Connection Connect host to device PAD Switching The DTC PAD switching allows remote users who enter a full address at the PAD prompt to be routed directly to the associated host system from the PAD prompt. Other calls are routed to the DTC user interface.
Introduction Connections via PAD Support • MPE_B has the X.25 subaddress 02, but has not been entered in the PAD switching table • System C has the IP address 128.12.100.1 and the X.25 subaddress of 03 The following table and diagram show what happens depending on the address entered by the user at the terminal connected to the remote PAD. Table 1-1 PAD Address Examples User at terminal types Chapter 1 ...
Introduction Connections via PAD Support Figure 1-4 DTC PAD Switching examples PAD Switching table: System X.25 addresss 12345601 12345603 System Node Name MPE_A.D.O 128.12.100.1 @12345601 @123456 MPE_A.D.O 01 Async DTC 2335A private PAD X.25 MPE_A.D.O 02 X.
Introduction Configuring PAD Support and PAD Security Configuring PAD Support and PAD Security This section contains the principles of configuring a DTC for PAD connections, and gives examples of how to configure certain connections. X.25 levels 1, 2, and 3 must be configured for PAD Support to function. DTC PAD support allows terminals connected to remote PADS to access LAN-based systems via the DTC, and LAN-based systems to access printers connected via DTC to remote PADs.
Introduction Configuring PAD Support and PAD Security • Figure 1-5 The address of the remote PAD Printer 1234502 is mapped to the PAD Device Name P1A2 in the PAD Access List DTC PAD Access Example Nailed PAD Access table for MPE A Profile Name TR24PAD PR26PAD LDEV 109 110 Device Name P1A1 P1A2 Remote Device X.25 address 1234501 1234502 CUG Number @1234502 MPE A 2335A private PAD X.25 X.25 DTC @1234501 LDEV Name 109 P1A1 110 P1A2 MPE B LDEV Name 109 P1A1 110 P1A2 Name X.
Introduction Configuring PAD Support and PAD Security Example of Incoming Security Figure 1-6 Setting Security Lists PAD Incoming Security Device X.25 Address 12345601 12345602 Access List Name LIST1 LIST2 The PAD Incoming Security tables maps calling X.25 addresses to access lists Each access list contains the names of the hosts which can be accessed by calling X.
Introduction Configuring PAD Support and PAD Security Table 1-2 PAD Security Connection Examples @ 98765404 connects directly to GG3.5.COM @ 987654 connects to the DTC suer interface DTC> connect NODE4.D.O this establishes the connection to GG3.5.COM @98765401 descret Connects directly to NODE1.D.O, giving the password for PAD access (assuming there is a password). If a password is required but is not present in the call user data received by the STC, the DTC will prompt the user for the password.
Introduction Configuring PAD Support and PAD Security • Figure 1-7 If XLA.D.O tries to call XLDD.D.O, the X.25 address 12345601 will be used as the calling address DTC System-to-System Switching Example System to System Switching table: System Node Name XLA.D.O System Link Name X25LINK Max SVC 64 System X.25 addresss 12345601 XLA.D.O 01 XLDD.D.O 03 X.25 DTC X.25 DTC X.25 XLB.D.O 02 @123456 X.
Introduction Configuring PAD Support and PAD Security • Figure 1-8 987654 and 987888 both have OUT permission only. DTC System Switching LUG Example System Switching LUG X.25 Address 987XXX 12345602 12345603 123456XX X.25 Security OU IN OU IO System A @987654 System B @987888 X.
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 3 Trace If you choose trace option 3, level 3 trace, you will be prompted for a VC type. Possible responses are PAd, to trace only PAD VCs, SYs, to trace system-to-system VCs, or All, to trace both PAD and system-to-system VCs that are active through the designated DTC and card. You will also need to specify the link name of the X.25 link. You will then be prompted for the filter (trace headers only or full packets) and given the option of specifying a file name.
Introduction Maintenance Hewlett-Packard recommends that you treat the files as read-only files. Once you have information that you want to format, copy the log file to another filename and format that file with the EVLOG formatter. NOTE 36 Switching to a different file only occurs when the current file runs out of space. If you are concerned about limiting the number of records written and formatted, a timestamp filtering capability is available in the formatter.
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 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 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. The following shows examples of three classes of IP addresses: Class A: nnn.xxx.xxx.xxx Class B: nnn.nnn.xxx.xxx Class C: nnn.nnn.nnn.xxx where nnn represents the network portion and xxx represents the node portion of the address.
Preparing to Configure DTCs Defining the DTC The valid card types for DTC 16 and DTC 48 are: D for direct connect cards (up to 8 ports per card), M for modem connect cards (up to 6 ports per card), X for DTC/X.25 Network Access cards (for connection) DTC Event Logging For each DTC, logging class 1 logs catastrophic events and will always be enabled. Class 2 logs critical events; class 3 logs non-critical events; classes 4 and 5 log informative events and clas s6 provides statistical information.
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 Terminal and Printer Profiles Each port needs to be assigned a profile. A profile defines a set of characteristics for a terminal, printer, or another serial device. A profile can be of five types: terminal profile, printer profile, PAD terminal profile, PAD printer profile, or Host port profile.
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 Configuring Worksheets Configuring 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. Chapter 3 “Configuring DTCs Step-by-Step” contains a description of all the fields referenced in these worksheets.
Preparing to Configure DTCs Configuring Worksheets PAD Access List Worksheet From the list of nodes in the Node Names list, enter those systems that will be allowed access for the PAD addresses configured with this list in the PAD Incoming Security worksheet. You can define up to 10 access lists, each with a maximum of 32 nodenames.
Preparing to Configure DTCs Configuring Worksheets DTC Configuration Worksheet Fill out a worksheet as shown in DTC Configuration Worksheet for each DTC you are configuring. Figure 2-3 DTC Configuration Worksheet DTC Configuration Worksheet DTC type (check one): DTC72MX: ____ DTC16iX: ____ DTC16MX/RX: ____ DTC48: ____ DTC 16: ____ DTC Name: DTC LAN Station Address: DTC Node Name: (Node.Domain.Organization) DTC IP Address: Card Types Installed in the DTC: Event Logging Classes: (Y/N) 3. 1. 2.
Preparing to Configure DTCs Configuring Worksheets DTC Card Configuration Worksheet Fill out worksheet as shown in DTC Card Configuration Worksheet for each direct connect card you are configuring.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration — Level 1 and Level 2 Worksheet Fill out worksheet as shown in DTC X.25 Level 1 and 2 Worksheet for each DTC X.25 Network Access card you are configuring. Figure 2-5 DTC X.25 Card Configuration -- Level 1 and 2 Worksheet DTC X.25 Card Configuration Level 1 and 2 Worksheet DTC Name: __________ Card Number: ____ Level 1 Line speed ________ Level 2 Packet Switched Network Name __________ CCITT X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration – Level 3 Worksheet Fill out worksheet as shown in DTC X.25 Card Level 3 Worksheet for each DTC X.25 Network Access card you are configuring.& Figure 2-6 DTC X.25 Card Configuration Level 3 Worksheet DTC X.25 Card Configuration Level 3 Worksheet DTC Name: _____________ Card Number: ____ X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration — System-to-System LUG Worksheet Fill out worksheet as shown in DTC X.25 Card Configuration System-to-System LUG Worksheet for each DTC X.25 Network Access card for which you are configuring system-to-system connections. Figure 2-7 DTC X.25 Card Configuration -- System-to-System LUG Worksheet DTC X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration -- System-to-System Switching Worksheet Fill out worksheet as shown in DTC X.25 Card Configuration System-to-System Switching Worksheet for each DTC X.25 Network Access card for which you are configuring system-to-system connections. Figure 2-8 DTC X.25 Card Configuration System-to-System Switching Worksheet DTC X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration – Nailed PAD Worksheet Fill out worksheet as shown in DTC X.25 Card Configuration Nailed PAD Worksheet for each DTC X.25 Network Access card for which you are configuring nailed PAD connections. Figure 2-9 DTC X.25 Card Configuration Nailed PAD Connections Worksheet DTC X.25 Card Configuration Nailed PAD Connections Worksheet DTC Name: _____________ Ldev Profile Card Number:____ Device Name Remote Device (PAD) X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration — PAD Switching Worksheet Fill out worksheet as shown in DTC X.25 Card Configuration PAD Security Worksheet for each DTC X.25 Network Access card for which you are configuring PAD switching connections. Figure 2-10 DTC X.25 Card Configuration PAD Switching Worksheet DTC X.25 Card Configuration PAD Switching Worksheet DTC Name: _____________ Card Number:____ Maximum number of PAD Connections: ______ System X.
Preparing to Configure DTCs Configuring Worksheets DTC X.25 Card Configuration — PAD Security Worksheet Fill out worksheet as shown in DTC X.25 Card Configuration PAD Security Worksheet for each DTC X.25 Network Access card for which you are configuring PAD security. Figure 2-11 DTC X.25 Card Configuration -- PAD Security Worksheet DTC X.25 Card Configuration PAD Security Worksheet DTC Name: _____________ Device X.25 Address Access List Name Card Number:____ Device 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-12 NMMGR DTS Screen Flow Open Config/ Directory File screen [Open Config] Main Screen [Go To DTS] [Go to NS] NS Configuation Host Configuration screen [Go To Access] [Go To 16iX] Level 1 &2 HP-IBM Configuration [Go To Profiles] DTC 16MX/ RX Config DTC 16 Config [Config Ports] [Card Config] Ports Configuation Async Card Configuation [Go To Lev 3] Level 3 Profile Selection [Go To DTC16] [Go To 16MX/RX] DTC 16iX Config [Add/M
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 Step 2: Open the Network Management Configuration File The Open Configuration/Directory File screen is displayed (Figure 3-1). This screen lets you specify the configuration and backup file names. 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.
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 Step 3: Configure the Local Node Name The Main screen is displayed after you press the [Open Config] key (Figure 3-2). This screen lets you specify the HP 3000 host's name. It also asks whether you are using the HP 3000 host or an OpenView Windows Workstation (PC) for DTC management, and if you are using X.25 or PAD. Figure 3-2 Main Screen 1. Assign a node name to the HP 3000 host in the “Local HP 3000 node name” field.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 HP3000 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 DTCs Step-by-Step Modify the Network Management Configuration File 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). This screen is used to configure the Datacommunications and Terminal Subsystem (DTS) on the HP 3000. DTS defines the interaction between the system and any asynchronous devices, such as terminals and printers. Figure 3-3 Host Configuration Screen (Host-Based) 1.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 6. 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 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 5: Configure PAD Node Name Lists The DTS Node List screen is displayed after you press the [Go to Access] key at the Host Configuration Screen. This is where you enter all the node names or IP address of all the systems that you will want to specify in the PAD Access Lists. PAD Node Names and Access Lists need to be configured only if you are going to configure PAD Incoming security.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 4. When you have entered all the desired node names, press the [Go to List] key to begin defining the PAD access lists. Proceed to step 6: Create PAD Access Lists. Fields Node Name The local NS node name that the system is known by on the network or the IP address that is configured for that node. The format of the NS node name is nodename.domain.organization. The format of IP is xxx.xxx.xxx.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 6: PAD Access List Selection The PAD Access List Selection screen lists the PAD Access lists available in your configuration file. To reach this screen, press the [Go to LIST] key at the DTS Node List screen. From this PAD Access List Selection screen, you may review, add, delete, or modify Access Lists. You can create up to 10 lists. Figure 3-5 PAD Access List Selection Screen 1.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File List name The name of the list to be reviewed, added, modified, deleted, or renamed. New name The new name for the list. Required only when renaming a list. List Names Display only. Lists the name of existing PAD Access Lists. Up to 10 lists. Step 7: Create and Modify the PAD Access Lists The PAD Access List screen is used to define Nodes from the Nodes Names list that are contained in a PAD Access List. Figure x.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 8: Select DTC Type The DTC Configuration Selection screen (Figure 3-7) is displayed when you press the [Go To DTC] key at the Host Configuration screen. Here you specify the type of DTC to configure. Figure 3-7 DTC Configuration Selection Screen 1. Select the DTC type by pressing one of the function keys: [DTC16iX], [DTC16MX/RX], [DTC16], [DTC48], or [DTC72MX].
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 9: Specify DTC Configuration The DTC Configuration screen is displayed after you select the DTC type at the DTC Configuration Selection screen. Figure 3-8 shows the DTC Configuration screen for a DTC 72MX. (DTC Configuration screens for DTC 16iX, DT C16MX/RX, DTC 16, and DTC 48 vary slightly). Figure 3-8 DTC Configuration Screen 1. Enter the DTC’s name in the “DTC name” field. 2.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Use the format nodename.domain.organization, where nodename identifies the DTC. The nodename of each node on the network in this domain and organization 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 10. 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. 11.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File DTC Async Card Configuration When you press the [Config Card] key at the DTC Configuration screen and the card is a direct or modem connect card, NMMGR will display the screen appropriate for the DTC. The screen for a DTC 72MX Asynchronous card is shown in Figure 3-9. Figure 3-9 DTC Async Card Configuration 1. Verify that the DTC name and card number displayed are correct. 2. (Optional) Enter the port group type.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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. If this is a managed DTC, you may assign an ldev of (-1) to a port with a TERMINAL or HOST profile type. A port with an ldev of (-1) and a TERMINAL profile is a non-nailed ldev.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File DTC/X.25 Card Configuration -- Nailed PAD Connections When a X.25 card is configured on a non-managed DTC, NMMGR will display the screen in Figure 3-10 to allow you to configure nailed PAD devices that will connect through a shared DTC. The corresponding ports must also be configured on the system where a DTC with the same DTC node name is configured as a managed DTC.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 11: Configure X.25 Connections NMMGR displays the DTC X.25 Card Configuration screen (Figure 3-11) if you press the [Config Card] key at the DTC Configuration screen (or at a different card configuration screen) with the card number of a DTC/X.25 Network Access card in the Config Card field. From this screen, you move to the screens that let you configure DTC values for X.25 system-to-system and PAD connections.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 12: Configure X.25 Level 1 and 2 NMMGR displays the DTC X.25 Card Configuration — Level 1 and 2 screen (Figure 3-12) if you press the [Go To Lvl 1&2] key at the DTC X.25 Card Configuration screen. On this screen, you enter level 1 and 2 values for the X.25 card being configured. You must configure these values for both system-to-system access and for PAD access.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 13: Configure X.25 Level 3 NMMGR displays the DTC X.25 Card Configuration — Level 3 screen (Figure 3-13) if you press the [Go To Level 3] key at the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration — Level 1 and 2 screen. On this screen, you configure level 3 values for this X.25 card including an X.25 card address.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 5. Use the [TAB] key to move to the Throughput class negotiation field. Enter Y to enable or N to disable according to your subscription. 6. 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. 7. Use the [TAB] key to move to the Extended packet sequence numberingfield. Enter Y to enable or N to disable according to your subscription. 8.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Throughput class Throughput class values for incoming and outgoing data. Values depend upon the speed of the link, as follows: Throughput Class 7 8 9 10 11 12 Line Speed 1200 2400 4800 9600 19200 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 14: Configure X.25 System-to-System LUG NMMGR displays the DTC X.25 Card Configuration — Sys-to-Sys LUGs screen (Figure 3-14) if you press the [Go To SysLUG] key at the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration — Level 3 & Miscellaneous screen. On this screen, you specify information for X.25 system-to-system Local User Groups.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 3. 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. 4. When you have entered all remote X.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File information for X.25 system-to-system switching table. The System-to-System Switching table maps the nodenames of LAN-based host system to X.25 addresses. Typically the X.25 address will be the X.25 address of the DTC followed by a unique subaddress. Figure 3-15 DTC X.25 Card Configuration — Sys-to-Sys Switching Screen 1. Verify that the cursor is in the System Node Names field.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Note that with certain networks (such as Transpac, in France) the called address is removed from incoming call packets and the calling address is added to outgoing call packets by the network. For these networks, enter only the subaddress in this field, not the full X.25 address. 5. Repeat Steps 1 to 4 for each local HP e3000 Series 900 system that will be allowed to establish a system-to-system connection with remote systems.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File • 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 16: Configure Nailed PAD Connections When you press the [Go to Pad] key from the DTC Card Configuration screen or the DTC X.25 Card Configuration --Sys-to-Sys Switching Table screen, NMMGR displays the DTC X.25 Card Configuration – Nailed PAD Connections screen (Figure 3-14). On this screen, logical device (ldev) numbers, profile names, device names, and remote X.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File Step 17: Configure PAD Switching When you press the [Go to PADswth] key at the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration -- Sys-to-Sys Switch Table screen, NMMGR displays the DTC X.25 Card Configuration -- PAD Switching Table screen (DTC X.25 Card Configuration PAD Table Screen). On this screen, you specify information for the PAD switching table.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 4. Repeat steps 1 to 2 for each local HP e3000 Series 900 system that will be allowed to establish a PAD connection with local systems. If you need to enter more than eight local system entries, press the [Save Data] key to save the data on this screen, then use the [Next Page] key to move to a new data entry screen to configure additional systems.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 (or NONE, for one system only) in this field, not the full X.25 address. System Nodename This is the NS node name as configured as NODENAME in NMCONFIG.PUB.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 1. Verify that the cursor is in the Device X.25 address field. Enter the X.25 address of the calling devices that will be associated with the following list name. You can use the letter X as a wildcard in place of any single digit. 2. Move the cursor to the Access List Name field. Enter the list name you want to associate with this address.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File file with the system I/O devices configured through the SYSGEN utility. This will take place only if the file opened at the start of the NMMGR session is NMCONFIG.PUB.SYS and validation is successful. Additionally, you must have System Manager (SM) capability or the cross-validation will not occur. The commands used for SYSGEN cross-validation are in the file NMGRXVAL.PUB.SYS.
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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 configura
Configuring DTCs Step-by-Step Modify the Network Management Configuration File 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.
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 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.25 connection. These devices can be terminals or PCs running terminal emulators. PAD Printer Profiles PAD printer profiles define the characteristics of ldevs that are used by printers that are connected to the HP 3000 through a PAD/X.25 connection.
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 Table 4-1 Host-Based Terminal Profile (Continued) Profile Name Characteristics Suggested Devices TR10U24 Terminal type 10 Record width of 80 bytes Parity: none Speed/Parity Sensing? N Reset HP Terminals? N Allow :HELLO logon? Y NLIO devices? N No device classes assigned Supported HP terminals Connected to modem port Set at 9600 bps TR24 Terminal type 24 Record width of 80 bytes Parity: none Speed/Parity Sensing? N Reset HP
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 4-2 Host-Based Printer Profiles Profile Name 110 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 9
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 4-2 Host-Based Printer Profiles (Continued) Profile Name Chapter 4 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 Table 4-3 PAD Profile Field (Continued) 7 6 5 4 3 2 1 0 Bit Position (128) (64) (32) (16) (8) (4) (2) (1) (Bit Value) 0 0 x x x x x x No forced data forwarding 0 1 x x x x x x Forced data forwarding 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.
Terminal and Printer Profiles DTC PAD Profile Field VPLUS mode; Telnet mode; 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 Terminal PAD Profiles Profile Definition 1 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 Table 4-4 Terminal PAD Profiles (Continued) 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.
Terminal and Printer Profiles DTC PAD Profiles Table 4-4 Terminal PAD Profiles (Continued) Profile 37 Definition No PAD test Init profile X.3 setting Data forward 3:127 Usage Used at connection initialization and during data transfer. The PAD must support the X.3 settings required by the applications and the 3:127 data forwarding. The PAD must support the X.3 setting needed by the applications. 39 No PAD test No init profile X.
Terminal and Printer Profiles DTC PAD Profiles Table 4-4 Terminal PAD Profiles (Continued) Profile Definition Usage 49 No PAD test Init profile No X.3 setting Data forward default Used at connection establishment and during data transfer. 51 No PAD test No init profile No X.3 setting Data forward default Used at connection establishment and during data transfer. The PAD must support the X.3 settings needed by the applications. 85 PAD test forwarding Init profile No X.
Terminal and Printer Profiles DTC PAD Profiles Table 4-4 Terminal PAD Profiles (Continued) Profile 121 123 125 Definition Usage No PAD test Init profile No X.3 setting Data forward 4:1 Forced data forwarding Used at connection establishment and during data transfer. No PAD test No init profile No X.3 setting Data forward 4:1 Forced data forwarding Used at connection establishment and during data transfer. No PAD test Init profile No X.
Terminal and Printer Profiles DTC PAD Profiles Table 4-5 Printer PAD Profiles (Continued) Profile Definition 32 No PAD test No init profile X.3 setting Data forward default Usage Used at a connection initialization. Recommended if you want to keep the profile set before connection establishment. To use this profile with iX, verify that the PAD supports the setting of the idle timer to 1/20 seconds, if you want to use terminal types such as TT22 or TT26. 34 No PAD test Init profile X.
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 Table 5-1 Configuration Values for X.25 Link (Continued) Parameter/Value Chapter 5 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.
Preparing to Configure X.25 iX System Access Plan the Network Configuration Table 5-1 124 Configuration Values for X.25 Link (Continued) Parameter/Value Screen Comment Reachable network IP network address Neighbor Gateway Reachable Networks The IP address of all remote nodes that can be reached through the gateway. Reachable network IP mask Neighbor Gateway Reachable Networks Optional subnet mask for the reachable network. Remote IP address X.
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 Figur e5-1 for the X.25 iX System Access links you are configuring. Figure 5-1 126 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 Figur e5-2 for each X.25 iX System Access link you are configuring. Figure 5-2 Chapter 5 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.25 iX System Access Identify Neighbor Gateways as a Configured Reachable Network reachable through gateway Node A and the IP address of Network 3 as a Configured Reachable Network reachable through gateway Node C.
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 Step 2: Open the Configuration File The first screen that NMMGR displays is the Open Configuration/Directory File screen (Figure 6-1). You should already have created the configuration file you are using when you configured DTS. (If you have not already configured DTS, stop here, and go to Chapter 3, “Configuring DTCs Step-by-Step,” for step-by-step instructions. Figure 6-1 Open Configuration/Directory File Screen 1.
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 Step 3: Select NS Configuration NMMGR displays the Main screen (Figure 6-2) after you create or open a 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File (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 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 1. Next to the words Enter a network interface:, enter a name for the network interface (for example, X25NI). 2. Next to the words Enter a network type:, enter a 3 to indicate that the NI is an X.25 NI. 3. Press the [Config Network] key. (There may be a short pause before the next screen appears.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Step 6: Configure X.25 Network NMMGR displays the X.25 Configuration screen (Figure 6-5) when you press the [Config Network] key at the Network Transport Configuration screen with an NI type of 3 (X.25). 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File 4. Enter the node name of the DTC that houses the DTC/X.25 Access card in the first DTC Node Name field the enter the slot number of the card in the Card Number field. Enter a link name, DTC node name, and card number for each link you are configuring. 5. When you are done adding links, press the [Save Data] key. 6.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File 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. IP subnet mask An IP subnet mask is specified in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space. An IP mask is used when configuring subnetworks.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Step 7: Configure X.25 Virtual Circuits NMMGR displays the X.25 Virtual Circuit Configuration screen (Figure 6-6) if you press the [Config Directry] key from the X.25 Configuration screen. This screen lets you configure the network directory. 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.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File press the [Go To] key. That brings you to the X.25 SVC Address Key Paths screen where you can then remove the default name POOL by typing over it with spaces and then saving the data. 4. If the address type is a switched virtual circuit, complete steps a through c, but if the address type is a permanent virtual circuit, skip to step 5. a. In the Remote X.25 address field, enter the X.25 address of the remote host for X.
Configuring X.25 Links Step-by-Step Modify the Network Management Configuration File Network interface (NI) name Display only. SVC or PVC Parameters The parameters for assigning either SVCs or PVCs are described in the following paragraphs. For SVCs Remote X.25 address The remote X.25 Address is the remote node’s X.25 address. This address is required for SVCs if you have specified an X.25 address key. This address must be 15 digits or less. Facility set The facility set name is a name for a set of X.
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 CARD=cardnum STOPBOTH Deactivates both X.25 and PAD support services on the specified card. STATUS Displays information about the DTC, including type (16, 48 or 72MX), X.25 cards, and whether X.25 or PAD support is active on the cards. Required if FUNC is one of STARTX25, STARTPADSUP, STARTBOTH, STOPX25, STOPPADSUP, or STOPBOTH. Specifies the X.25 card number on which the FUNC operation is to be performed. FORCED=foption Optional.
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. The FORCED=Y option for the DTS Shutdown function can not be selected from the menu.
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 Table 7-1 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: • System to System Local Users Group • System to System Switching • remote X.
Managing Networks with DTCCNTRL Dynamic Configuration Table 7-1 Dynamically Configurable Tasks (Continued) Task Host-based X.25 configuration changes: Action Required for Change to Become Active Use DTCCNTRL to: • change PAD access 1. Stop X.25/PADSUP • change level 1, 2, or 3 configuration 2. Start X.
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 If you type N, dynamic configuration changes will not take effect now. Your changes will take effect the next time dynamic configuration is invoked, a DTS shutdown/restart is performed, or the system is rebooted. Dynamic configuration changes can be implemented later by calling DTCCNTRL from the CI prompt any time thereafter. Or you can run NMMGR again and select validate DTS/Link.
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 DTCXXXX.domain.organization automatic configuration in progress..... (DTC download messages will appear here if you are at the system console.) DTCXXXX.domain.organization configured and downloaded successfully. All ports configured successfully. END OF PROGRAM : 7. If there are SNP cards installed in the DTC, run NMMGR and modify the configuration for Level 1 and 2 screen and Level 3 screen. 8. Modify any other X.
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 164 Chapter 7
Formatting Host-Based X.25 Log Files 8 Formatting Host-Based X.25 Log Files This chapter describes the event log formatter and provides instructions for its use. As described in Chapter 1, “Introduction,” you use a special formatting tool, EVLOG, to view and format host-based X.25 log files. EVLOG is capable of formatting and displaying the events as they are reported to DTS by the DTCs (dynamically).
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 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 To format a host-based X.25 log file using the default options, enter the following MPE command: :evlog logfilename where logfilename is the name of the file that you want to format.
Formatting Host-Based X.25 Log Files To Use EVLOG To Select Formatting Options To select the formatting option that you want to change when running EVLOG interactively, type the option number at the prompt. EVLOG will then prompt you to enter additional information. The information required depends on the option selected. Brackets displaying the current setting of the option are included in the prompt. Each of the options is described, each description includes an example of the option’s use.
Formatting Host-Based X.25 Log Files To Use EVLOG Options: 0 1 2 . . . — — — — — — Set all options back to their default values File (logfile1, 15 records) Records (2..5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Option 4: Subsystems Use this option to restrict the records displayed to those of a particular subsystem. In the following example, the user selects the NMP subsystem.
Formatting Host-Based X.25 Log Files To Use EVLOG MON X25 X25PAD SNMP (Monitor events) (L2 + L3 events) (X.25 + PAD events) = = = = 5120 3584 3584 8960 — — — — 5631 4607 5119 8971 Event code range: First event code [1]? Options: 0 1 2 3 4 5 . . . — — — — — — — — — Set all options back to their default values File (logfile1, 15 records) Records (2..5) Event types (3) Subsystems (4) Event codes (3584..4607) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Formatting Host-Based X.25 Log Files To Use EVLOG . — . — . . . . . . . . . . . . . . . . . . . . . . . . Option 8: Time/Offset Format There are four types of timestamps in event log records. They are: HOST time The time the event was logged on the host (HP 3000). Found in event type 3 (DTC). PC time The time the event was logged on the OV DTC MGR PC. (This type is not meaningful for log files created on systems using host-based network management.
Formatting Host-Based X.25 Log Files To Use EVLOG TO: hour min sec year month day hour min sec [0]? 11 [0}? [0]? [2020]? 1991 [1]? 10 [1]? 5 [0]? [0]? [0]? Options: 0 1 2 3 4 5 6 7 8 9 — — — — — — — — — — ? — Set all options back to their default values File (logfile1, 15 records) Records (2..5) Event types (3) Subsystems (4) Event codes (3584..4607) Logical Channel Identifier (LCI) (ALL) Virtual Port Number (VPN (ALL) Time/offset format (Host time) Time/offset 1970 — 2020)) (70-01-01-00-00-00...
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.
Formatting Host-Based X.
Migrating from Previous Releases A Migrating from Previous Releases This appendix describes the steps for migrating network configuration files to the current MPE/iX release from previous MPE/iX or MPE V releases or to migrate the network DTS configuration from PC-based DTC management to Host-based DTC management. A utility call NMMGRVER.PUB.
Migrating from Previous Releases Running NMMGRVER to Update Release Version Running NMMGRVER to Update Release Version To run NMMGRVER, logon as MANAGER.SYS in the PUB group and run the utility by entering NMMGRVER after the MPE/iX prompt. NMMGRVER will prompt you for the configuration file name. Enter NMCONFIG, and Y to the confirmation prompt. The steps to run NMMGRVER are shown here: : HELLO MANAGER.SYS,PUB : NMMGRVER NM Configuration File Conversion Utility 32098-20016 V.uu.ff © Hewlett-Packard Co.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management Migrating your Configuration to Host-Based Management This section describes the process that you can use to migrate the majority of the configuration of your DTCs from PC-Based Management to Host-based Management. This process is only performed on the HPe3000 system that you want to manage your DTCs. If you have other systems that share the DTCs you do not need to make any changes to the configuration on those systems.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management What the Migration Process Can/Cannot Do The Migration process will be able to migrate the following portions of the DTC’s configurations from the OpenView DTC Manager PC to DTCs configured on the HPe3000 host. • The following DTC types are migrated: DTC16, DTC48, DTC16iX, DTC16MX, DTC72MX. • All Global LAN configuration parameters will be migrated to the Host.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management 2. .On the HP e3000 host, remove any DTC configurations from the PC-Based configuration in the NMCONFIG file that aren’t in use or should not be included in the migration process. Change the configuration to Host-based Management and remove all DTCs that may still exist in the Host-Based configuration. 3. .
Migrating from Previous Releases Migrating your Configuration to Host-Based Management host HOSTAUTO PAD Terminal TR24AUTO PAD Printer PR26AUTO 6. The Host Migration tool will copy the profile name from the TIO ports and PAD devices in the PC-based DTC to the corresponding port in the Host-based DTC. The profile data itself WILL NOT be copied from the PC-based to the host-based configuration. 7.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management 4. If the card type configured in the Host-Based DTC does not match the card type in the PC-Based DTC then the card is not merged into the Host-based tree and the Host-based DTC will have the same configuration discrepancies as described in paragraph 1 and 2. 5.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management Your Host’s Configuration is Currently PC-Based The migration process was designed such that this is the most likely situation that will be migrated to Host-based DTC management. In this situation, there are the following four scenarios to consider. It is possible that your configuration will have one or more of these conditions.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management A DTC migrated from the PC is not configured in the PC-based tree This means that at the time the Host Migration tool is run, there is at least one DTC migrated from the PC where a DTC does not exist with a matching DTC Node Name in the PC-based tree of the NMCONFIG file.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management ACTION: DO NOT run the Host Migration tool. On the DTCs that are migrated from the PC, you must run NMMGR and assign valid ldev numbers to the nailed TIO Ports and PAD devices. You have a Non-managed DTC I In this case you can have two possibilities: The non-managed DTC is one of the DTC that you are migrating from the PC; the non-managed DTC is managed from another platform.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management 2. If you don't see a job logged on as: JINETD,MANAGER.SYS then check that FTP is properly configured on the host. Then check that the network services are running and start the ARPA process. :stream jinetd.net On the Open View DTC Manager PC NOTE 3. Install the OpenView DTC Manager patch with the migration tool on the Local PC. 4.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management 10. Save a backup copy of your NMCONFIG file. 11. Run NMMGRVER to update the NMCONFIG file to the version for these patches. 12. If your configuration is currently PC-Based, then complete the tasks in step 12a. If your configuration is Host-Based, complete the tasks in step 12b. a.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management :SAVE NMMGROUT :RESET NMMGRCMD Item already exists. (NMGRERR 21) The source path was not found. (NMGRERR 280) 16. .If your original configuration was Host-Based, then skip to step 19. If your original configuration was PC-Based and you have DTCs in the PC-Based tree that you want to merge into the Host-Based tree, then continue with the following step.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management Current operation NONE. Selected Modules X.25 [ ] PAD [ ] STARt #,# (X.25,PAD) STOp #,# (X.25,PAD) Dtc # List of DTCs (carriage return to exit) ? Running NMMGRVER from NMMGR The New Host-Based Management release provides two ways to launch NMMGRVER from within NMMGR. • When the New Host-Based Management is first installed and the NMCONFIG file needs to be updated.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management subsystem. Although the DTS subsystem is correctly configured, you will not be able to make changes to the DTS configuration until you update the NMCONFIG file to the latest release with NMMGRVER. Figure A-1 Convert DTS Screen If you press the [Do Convert] key, NMMGR will automatically run NMMGRVER to allow you to update the NMCONFIG file. Follow the instructions above “Running NMMGRVER to Update Release Version”.
Migrating from Previous Releases Migrating your Configuration to Host-Based Management Once you have completed the necessary steps prior to running the Host Migration tool, you can launch the Host Migration tool from within NMMGR. To launch the Host Migration tool, press the [Utility] key on the NMMGR Main screen. On the Utility screen, press the [Go To MIGRATE] key. You will see the following screen. Figure A-2 DTS Migration Launch the tool by pressing the [Launch Migrate] key.
Error Messages B 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: Verify the linkname on the Host Configuration screen. If the link data record does not exist, update the DTS Configuration screen. (DTSERR 9) Path: NMMGRpath — The non-nailed device profile is not defined. Cause: The profilename on the screen specified by the NMMGRpath is not defined; therefore, the profile data record does not exist.
Error Messages Validation Error Messages Action: Go back to the DTS Configuration screen and delete the link specified in the NMMGRpath. Delete all unused links so that eight or less links are being used. (DTSERR 19) Path: NMMGRpath — Too many paths are being used (max. number allowed =8). Cause: The link specified in the NMMGRpath cannot be processed. Too many physical paths are already defined. Action: Go back to the DTS Configuration screen and delete the link specified in the NMMGRpath.
Error Messages Validation Error Messages (DTSERR 30) Path: NMMGRpath — Modem type not supported. Cause: The modem type specified on the DTS Terminal Profile screen is not 0, 1, or 2. A problem occurred while adding the ldev to a device class. This could be caused because the class is used by a different type of device such as a HPIB printer. 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.
Error Messages Validation Error Messages Cause: A host node name is not specified on the screen specified in the path. Action: Enter a host node name on the screen specified in the path. (DTSERR 54) Path: NMMGRpath — The profile for LDEV #nnn, profilename, is not defined. Cause: An incorrect profile name was used for the logical device (ldev). Action: Verify the profile name for the logical device in the DTS Profile Selection screen.
Error Messages Validation Error Messages Cause: You have specified an invalid management timer selection. Action: Go to the Tune DTC — Timer Selection Screen and choose a value of 1 or 2 for a management timer selection. (DTSERR 76) Path: NMMGRpath — Baud rate 38400 for LDEV #nnn, defined in Profile profilename, is not supported on DTC16 and DTC48. Cause: You have used a profile that specified a baud rate of 38400 for a device that is connected to a DTC 16 or DTC 48.
Error Messages Validation Error Messages 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. (DTSERR 84) Path: NMMGRpath — Cardtype for card c does not match DTC card configuration. 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.
Error Messages Validation Error Messages Cause: Eight bit data length with odd/even parity (“8odd” or “8even”) feature is not supported on DTC 16 or DTC48. Action: Go to DTC specified in NMMGRpath and change the entry for the parity to the required value other than “8odd” or “8even”. (DTSERR 94) Path: NMMGRpath — Two stop bits for LDEV#nnn, defined in Profile , is not supported on DTC 16 or DTC 48. Cause: Modem Two stop bits feature is not supported on DTC16 or DTC 48.
Error Messages Validation Error Messages Cause: The X.25 table in the DTC specified in NMMGRpath cannot be processed. Too many PAD Switching entries are already configured. Action: Go to DTC configuration screen and delete the entries until only the specified number remain in NMMGRpath. (DTSERR 105) Path: NMMGRpath — Too many PAD Incoming Security table entries found. Maximum is 512. Cause: The X.25 table in the DTC specified in NMMGRpath cannot be processed.
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 Cause: A problem exists with the datacomm buffers. Action: Contact your Hewlett-Packard support representative. (DCCERR 8) DCC ERROR P-L, (External procedure not found, status SSSSSSSS). Cause: A problem exists with DCC execution. Action: Contact your Hewlett-Packard support representative. (DCCERR 9) DCC ERROR P-L, (Memory management error status SSSSSSSS). Cause: A problem with the system occurred; the DCC cannot obtain memory.
Error Messages DCC Error Messages Action: Contact your Hewlett-Packard support representative. (DCCERR 19) DCC ERROR P-L, Link error status SSSSSSSS. LLIO path: NMMGRpath. Cause: A problem occurred while configuring the link manager. Action: Contact your Hewlett-Packard support representative. (DCCERR 20) DCC ERROR P-L, Add LDEV to class failure (HLIO status SSSSSSSS, ldev LLL). Cause: A class contains more than 255 devices, or a conflict in class names exists, or NMCONFIG.PUB.
Error Messages DCC Error Messages (DCCERR 28) DCC ERROR P-L, Invalid DTC type specified, (DCC status SSSSSSSS. Cause: The NMCONFIG.PUB.SYS file may be corrupt. Action: Use a backup configuration file, verify and update your configuration, validate and cross-validate with SYSGEN, and restart DTS. Keep the corrupt configuration file and report this condition to your HP representative. (DCCERR 29) DCC ERROR P-L, DTC is not configured, NM path: NMMGRpath.
Error Messages DCC Error Messages Cause: An attempt was made to delete an ldev that is logged on or is SPOOLED. Action: Logoff the session using the device or stop the spooler on the device and retry the operation. (DCCERR 38) DCC ERROR P-L, Failed to delete ldev LLL. (HLIO status SSSSSSSS). Cause: An internal error occurred while deleting an ldev. The ldev is probably unusable. Action: Do a DTS shutdown and restart. If the problem persists, then reboot the system.
Error Messages DCC Error Messages Cause: While automatically adding a new DTC no boot request was received within the allowed time. The DTC is either powered off or the LAN address specified is not correct. Action: Make sure the DTC is powered on and the correct LAN address is specified. (DCCWARN 48) DCC WARNING P-L, (LLIO status SSSSSSSS) Cause: An internal problem has occurred with low-level I/O. Action: This is a warning. If it persists contact your Hewlett-Packard support representative.
Error Messages DCC Error Messages Action: Check that the file exists and that it is not locked. If the file exists and is not locked, check for file system or hardware problems. (DCCWARN 102) DCC WARNING P-L, (Startup) can not purge NMCONFIX, status SSSSSSSS. Cause: The NMCONFIX.PUB.SYS file cannot be purged. Action: Check that the file exists. If the file exists, check for file system or hardware problems. (DCCWARN 103) DCC WARNING P-L, (Startup) can not open NMCONFIX, status SSSSSSSS.
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 Cause: More parameters were entered than are defined by the DTCCNTRL command. For example, the command was entered as: DTCCNTRL DTC=DTC.ITG.HP;CARD=4;FUNC=RC;FORCED=Y;RECONF=ALL;A=4 Action: Reenter the command without the invalid parameter. For example: DTCCNTRL DTC=DTC.ITG.HP;CARD=4;FUNC=RC;FORCED=Y;RECONF=ALL CTLERR 01 Failed to open the catalog file DTCCAT.PUB.SYS. Cause: The catalog file does not exist or could not be opened at the time the command was executed.
Error Messages DTCCNTRL Error Messages Cause: The DTCCNTRL command was issued at a time when another user had exclusive access to the DTC (for example, TermDSM was running). Action: Either reissue the DTCCNTRL command using the FORCED option to force access to the DTC or wait until the DTC is no longer being exclusively accessed. CTLERR 08 Non-existing DTC. Cause: A DTCCNTRL command was issued for a DTC that is not configured for the host system.
Error Messages DTCCNTRL Error Messages Cause: An attempt was made to reconfigure global data values 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. Correct any problems then reenter the DTCCNTRL command with FUNC=RC to download the reconfigured global data values. CTLERR 15 Global physical security download failed.
Error Messages DTCCNTRL Error Messages Action: Reenter the command with a valid RECONF specification. Valid values are ALL, X25, CARD, PASS, and LOGCL. CTLERR 22 Invalid specification for FORCED parameter. Must be y or n. 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”. CTLERR 23 PAD download failed.
Error Messages DTCCNTRL Error Messages CTLERR 103 System error: bad status received from io_info_list, err_num = !, proc_num = !. Cause: Internal error. Action: Contact your Hewlett-Packard support representative. CTLERR 104 System error: bad NDM port number returned. Cause: Internal error. Action: Contact your Hewlett-Packard support representative. CTLERR 105 System error : bad Send_msg status received, info = !, subsys = !. Cause: Internal error.
Error Messages DTCCNTRL Error Messages Action: To cause reconfigured values to be downloaded, issue a DTCCNTRL command using the RC function. If no reconfigured values are to be downloaded, no action is required.
Error Messages Host Migration Tool Status Messages Host Migration Tool Status Messages The following message will be displayed if the migration was successful. If you see any other error messages the migration was not successful. Go to the manual Using the Node Management Services (NMS) Utilities for more detailed descriptions and actions to take to fix them. CONVERSION completed successfully.
Error Messages Host Migration Tool Status Messages MSG 152 Cannot copy DTC from PC-Based to Host based. Duplicate DTC name. Cause:The Host Migration tool found a DTC in the Host-Based tree that has the same DTC name as the DTC in the PC-Based tree, but with a different DTC Node Name. The DTC node name of the DTC in the PC-based configuration was not found in the Host-based configuration so the Host migration tool was attempting to create a non-managed DTC in the Host-based configuration.
Error Messages Host Migration Tool Status Messages MSG 159 No DTC was found in the PC-Based tree with the matching DTC node name . Cause: The Host Migration tool found a DTC with the displayed DTC Node Name in the Host-based configuration that does not exist in the PC-Based configuration. If the DTC in the Host-based configuration was migrated from the OVDTCMGR, then the TIO devices will be assigned ldev of (-1) and any PAD devices will be assigned ldev of (1).
Error Messages Host Migration Tool Status Messages 218 Appendix B
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 baud baud Measure of the speed at which information travels between devices, most commonly used in reference to terminal speed settings. Baud represents signal events per second. When one bit represents each signal change, baud is the same as “bits per second”. binary mode Data transfer scheme in which no special character processing is performed. All characters are considered to be data and are passed through with no control actions being taken. bit Binary digit.
Glossary destination node name Windows Workstation) depending on the type of network management you use. If any of the NS link products are installed on the system, network configuration is accomplished through use of NMMGR and, if PC-based X.25 connections are required, through the OpenView DTC Manager. configuration file he configuration file, which you create and update using the NMMGR utility, contains: 1) the information that the network needs in order to operate.
Glossary device class device class A collection of devices that have some user-defined relation. Device classes are assigned through use of the NMMGR configuration utility. device-dependent characteristic A file specification for which modifications are restricted because of the type of device on which the file is opened. For example, data directed to terminals must have a blocking factor of one. device driver Software module that controls a specific type of input/output device including NS 3000/iX links.
Glossary DTS shutdown DTC 16RX HP J2064A product. A routable communications server that enables up to 16 asynchronous connections for the HP 3000 environment and computer systems running ARPA, such as HP 9000s and third party systems. DTC switching A facility enabling terminal users to select any host system that they want to connect to. DTC switching is available only when the OpenView DTC Manager is used for network management.
Glossary duplex duplex Transmission method that allows two-way communication. If both ends of the transmission link can transmit simultaneously, it is called full duplex. If only one end can transmit at a time, it is half-duplex transmission. dynamic configuration The ability to make DTS configuration changes using NMMGR without rebooting the HP 3000 system.
Glossary IEEE 802.3 full gateway A full gateway is a node that belongs to more than one network and has one IP address for each network. It uses store and forward to transfer packets between each network that it belongs to. 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. gateway A node that connects two dissimilar network architectures.
Glossary IEEE 802.3 multicast address IEEE 802.3 multicast address A hexadecimal number that identifies a set of nodes. This address is used for multicast delivery. intranet routing Intranet routing involves all the processes required to route a packet from one node in a network to another node in the same network. IEEE 802.3 nodal address A unique hexadecimal number that identifies a node on an IE E E802.3 LAN.
Glossary M bit LCI Logical Channel Identifier. Local value on a network node which identifies the channel used to establish a virtual circuit (SVC or PVC) through an X.25 network. ldev See logical device number. leased line Data-grade telephone line leased directly to a subscriber and allocated specifically for the subscriber’s needs. through the NMMGR configuration have ldev numbers permanently assigned. The DTC devices can then be accessed programmatically through use of their ldev number.
Glossary medium attachment unit medium attachment unit A device attached to a ThickLAN coaxial cable that provides the physical and electrical connection from the AUI cable to the coaxial cable. MIB Management Information Base. A database of information about a network node used by SNMP. MIT Master Installation Tape. Magnetic tape containing the fundamental operating system for a HP 3000 Series 900 computer. modem Modulator/demodulator. A device that modulates and demodulates signals.
Glossary NS 3000/iX Link network subscribed facilities A set of parameters that the user chooses when he subscribes to the X.25 network; they include flow control negotiation, use of D-bit, throughput class negotiation and extended packet sequence numbering. network transport Software that corresponds to layers 4 and 3 of the OSI network architecture model.
Glossary NS 3000/iX Network Services the DTC/X.25 iX Network Link, the NS Point-to-Point 3000/iX Link, and the Token Ring 3000/iX Network Link. NS 3000/iX Network Services Software applications that can be used to access data, initiate processes, and exchange information among nodes in a network. The services are RPM, VT, RFA, RDBA, and NFT.
Glossary PXP path name When configuring with NMMGR, you can type a string in the COMMAND: field on display screens to branch to another screen. Each screen has a unique path name that corresponds to its location in the hierarchy of configuration screens presented by NMMGR. PDN Public Data Network. A data communication network whose services are available to any user willing to pay for them. Most PDNs use packet switching techniques.
Glossary Q bit Q bit Qualified bit. When set in DATA packets the Q bit signifies that the packet's user data is a control signal for the remote device, not a message for its user. QuickVal A software program that tests whether Network Services are operating correctly between nodes. RDBS Remote Data Base Access. A network service that allows users to access data bases on remote nodes. reachable network A network that can be accessed (with additional internet hops possibly required) by a particular gateway.
Glossary terminal profile SNMP Simple Network Management Protocol. An industry standard for managing networked computers in a multi-vendor environment. 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.
Glossary terminal type terminal type A collection of characteristics that cause a terminal connected to an MPE system to act and react in a specified manner. You may configure a terminal to use one of the system-supplied terminal types, or you may create custom terminal types using the workstation configurator. ThinLAN A LAN media that conforms to the IEEE 802.3 Type 10 BASE 2 standard LAN. ThinLAN 3000/iX Link Hardware and software necessary to create a broadcast network, which uses the IEEE 802.
Glossary X.Series (X.##) CCITT recommendations V.24 The CCITT recommendation that defines the function of the interchange circuits between a DTE and a DCE. validation The process of ascertaining whether the network transport configuration file has been correctly configured. In guided NMMGR, you do this by pressing the Validate Netxport key. VAN Value-Added Network. A data communication network that uses and pays for facilities belonging to another carrier. The value-added package is then sold to a user.
Glossary X.
Index A Address key, 143 address key, 142 allow access , 101 assigning node names, 66, 136 B backup configuration file, 64 backup configuration file name, 134 backup copies, 62 C Card Number, 86, 89 Card number, 92, 97 card number, 43, 141 card type, 76 CCITT X.25 protocol , 18 CCITT X.
Index default options , 168 formatter, 166 how to use, 167 limitations, 166 running interactively, 167 EVLOG option event codes, 169 logical channel identifier, 170 records, 168 subsystems, 169 time/offset format , 171 virtual port number, 170 Extended packet sequence numbering, 90 extended packet sequence numbering , 89 F facility set, 143, 144 facility sets defined, 144 Flow control negotiation, 90 flow control negotiation, 88 force DTCCNTRL operation, 163 format log files , 167 formatter EVLOG, 166 forma
Index configuration, example of , 128 defined, 145 Neighbor Gateways screen, 145 network directory file, 64, 132 network directory file name, 134 Network directory name, 143 network interface (NI) name, 144 network interface name, 138 guidelines for using , 138 network management configuration file NMCONFIG.PUB.SYS, 62 network name, 138 Network Transport configuration , 137 Network Transport Configuration screen, 137 network type, 138 NI name, 138 NI type, 138 nieghbor, 128 NMCBACK.PUB.SYS, 64 NMCONFIG.PUB.
Index X.25 Virtual Circuit Configuration, 142 screens Open Configuration/Directory File , 63 security X.
