HP X.25/9000 User’s Guide HP-UX 11i v3 Edition 8 Manufacturing Part Number: J2793-90072 February 2007 © Copyright 2007 Hewlett-Packard Development Company, LP.
Legal Notices Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license required from HP for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents 1. About the X.25 Product Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application (L7), Presentation (L6), and Session (L5) Levels . . . . . . . . . . . . . . . . . . . . Transport Level (L4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet/network Level (L3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Add/Modify UUCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add/Modify X.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the High Availability Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 Cluster Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.
Contents Example 1: Running x25check Interactively (No Parameters) . . . . . . . . . . . . . . . . Example 2: Running x25check With an X.121 Address . . . . . . . . . . . . . . . . . . . . . . Example 3: Running x25check With a Data Packet . . . . . . . . . . . . . . . . . . . . . . . . . x25stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1: Displaying the Current Configuration. . . . . . . . . . . . . . . . . . . . . .
Contents pad_uucp Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring System and Device Files for UUCP . . . . . . . . . . . . . . . . . . . . . . . . . . . Local PAD Emulation (padem) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Transfer Mode . . . . . . . . . . . . . . . . . . .
Contents Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 8. Troubleshooting Troubleshooting Your X.25 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Flowcharts and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 2 – Procedures and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note 2-1 – x25stat . . . . . . .
Contents The x29hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 The Network Type File (x25_networks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 C. Diagnostic Messages Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Table 3-1. Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Table 3-2. Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Table 3-3. Configure Internet Address Field Descriptions . . . . . . . . . . . . . . . . . . . . .37 Table 3-4.
Tables Table 6-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Table 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Table 6-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Table 6-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table C-4. Timer Expired. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 Table C-5. Call Setup, Call Clearing, or Registration Problem . . . . . . . . . . . . . . . . .247 Table C-6. CATEGORY - Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Table C-7. International Problem and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . .251 Table C-8. DTE-Specific Signals . . . . . . . . . . . . . . . . . . . . .
Tables 12
Figures Figure 1-1. X.25 Link Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Figure 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Figure 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Figure 3-3. Configure Internet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 14
1 Chapter 1 About the X.
About the X.25 Product Introduction Introduction The Hewlett-Packard X.25 link for HP 9000 systems provides networking link hardware and software to allow HP computer systems to communicate with other HP and non-HP computers over X.25 packet switching networks. The X.25 link implements the CCITT X.25 Recommendations and contains the components necessary to connect an HP 9000 to a public or private packet switching network conforming to the CCITT X.
About the X.25 Product Introduction Figure 1-1 X.25 Link Architecture Internet Services OSI Services X.25 User User PAD Written Written Services L3 L4 Network Services NS OTS/9000 BSD IPC TCP/UDP X.25 Programmatic Access OTS-to-PLP Translator BSD-to-PLP Translator IP-to-PLP Interface X.25 Packet Level Protocol (PLP) X.25 Link Access Procedure-Balanced Protocol (LAP-B) X.
About the X.25 Product Application (L7), Presentation (L6), and Session (L5) Levels Application (L7), Presentation (L6), and Session (L5) Levels The X.25 link does not provide any components for the general support of the application and presentation levels (levels 7 and 6, respectively), although X.25/9000 PAD Services do provide some of the functionality of these levels.
About the X.25 Product Transport Level (L4) Transport Level (L4) At the transport level (level 4), the X.25 link provides TCP (based on the DARPA standard) and UDP. These Transport level protocols are used by Internet/Berkeley Services, by NS, and by user application programs that access the TCP/UDP and IP protocols. The TCP protocol is a connection-based protocol. TCP verifies that all data is delivered without duplication to its destination. The UDP protocol, unlike TCP, has no concept of a connection.
About the X.25 Product Packet/network Level (L3) Packet/network Level (L3) At the packet/network level (L3), X.25 link provides direct X.25 programmatic access via BSD IPC. For full details on X.25 programmatic access, refer to the X.25/9000 Programmer’s guide (part number: J2793-90065). The X.25 link also provides IP access to TCP or UDP Transport protocols for programs such as Internet/Berkeley Services and NS, allowing communication over X.25 in accordance with RFC 877.
About the X.25 Product Data link (L2) and Physical (L1) Levels Data link (L2) and Physical (L1) Levels At the data link level (level 2), the X.25 link provides the LAP-B (Link Access Procedure-Balanced) protocol. LAP-B is a data link protocol, specified by the 1980 CCITT X.25 recommendations, that determines frame exchange procedures. At the physical level (level 1), the X.25 link provides support for X.21, X.21bis, and V.35 interfaces (depending on your particular communications hardware).
About the X.
2 Chapter 2 Installation 23
Installation Before You Install the Software Before You Install the Software Before installing the X.25 link software, check the requirements below to make sure that all required software and hardware has been correctly installed and configured. NOTE This product is only supported on the system that is acting as a server. It is not supported on client systems. Hardware Requirements This section describes the hardware requirements of the J2793B X.25 software for HP 9000 server systems.
Installation Before You Install the Software OS Platform and Version Compatibility The version of the X.25 link software you’re installing must be compatible with the version of HP-UX you’re running (for example, HP-UX version 11i v3 for B.11.31.01) • Disk space required to install: 7 Mb • Software install with system up or down? Up • Single-user state required or recommended? No • Reboot? Yes Memory Your X.25 link supports a high number of virtual circuits operating at high baud rates.
Installation Before You Install the Software Shortcut Method Assuming B = P for all VCs, TM can be rounded to: • If B < 512, TM = approx. (1,536 + (2 x W + 2) x B) x No. of VCs • If B > or = 512, TM = approx. (2 x W + 5) x B x No. of VCs The following table (in bytes/VC) provides a quick guide: Table 2-1 Buffer Size (B) = Packet Size (P) in bytes Window (W) size Example 2-1 128 256 512 1024 2048 4096 1 2K 2.5 K 3.5 K 7K 14 K 28 K 2 2.3 K 3K 4.5 K 9K 18 K 36 K 3 2.5 K 3.5 K 5.
Installation Before You Install the Software TM = (4096 x 3) + (2 x 3 x 1024)) x 200 + ((4096 x 3) + (2 x 5 x 128)) x 400 + (2 x 5120) TM = 9,123,840 (8.7 Mb) Software Requirements Before installing the X.25 link product, make sure that the software listed below has been correctly installed on your system. Refer to the related publication if you need more information about any of these products. If you cannot find the software or information you need, contact your HP representative.
Installation Installing the X.25 Link Software Installing the X.25 Link Software Follow the steps below to install the X.25 link software: Step 1. Insert the software media (tape or disk) in the appropriate drive. Step 2. Type: swinstall. (See the man page on swinstall for more information on this command). Step 3. Click on OK on the “Specify Source” window. Step 4.
3 Chapter 3 Configuration 29
Configuration Configuring the X.25 Link Configuring the X.25 Link This section describes how to configure your X.25 link using HP System Management Homepage(SMH). HP SMH provides Graphical User Interface (GUI), Terminal User Interface (TUI) and Command Line Interface (CLI) for managing HP-UX. You can access these interfaces using the smh command (/usr/sbin/smh). If the DISPLAY environment variable is set, HP SMH opens in the default web browser.
Configuration Configuring the X.25 Link (To run SMH in the background, type: smh &). Step 2. At the SMH main window, select “Tools” menu. SMH displays numerous object lists. Step 3. Double-click on the Network Services Configuration menu. SMH displays an object list that shows all network interfaces (devices) installed in your system. SMH displays each port (for multi-port cards) as a unique interface with its hardware path and name. Interfaces are listed in order of their slot number. Step 4.
Configuration Configuring the X.25 Link Configuring an X.25 Address Follow the steps below to configure an X.25 address: Step 1. From the “Configure X.25 Software” window, select Configure X.25 Address. The following dialog appears: Figure 3-1 NOTE The SMH windows and dialogs shown on these pages are intended only as examples. The information that appears in your SMH dialogs, such as the Card Name and Programmatic Access Name, depends on your particular communications hardware. Step 2.
Configuration Configuring the X.25 Link Table 3-1 Field Descriptions Configuration File name Name of the file that will contain the parameters for configuring the interface (a physical port). If you are configuring more than one interface, specify a unique configuration file for each interface.
Configuration Configuring the X.25 Link DCE_80 DTE_84 DATAPAC DDN LUXPAC TYMNET DCE_84 DTE_88 DATEXP_AUSTRIA DDXP PSS IBERPAC DCE_88 AUSPAC DATEXP_DEUTSCHE HPPPN TELENET TELEPAC DTE_80 DATANET1 DCS ITAPAC TRANSPAC DATAPAK Step 3. Click on OK to return to the “Configure X.25 Card” window when you have finished configuring the X.25 Address. Configuring X.25 Virtual Circuits (VCs) Follow the steps below to configure X.25 virtual circuits: Step 1. From the “Configure X.
Configuration Configuring the X.25 Link Table 3-2 Field Descriptions Permanent Quantity Number of Permanent VCs. Use the value given on your subscription form. Switched (inbound) Quantity Number of Switched (inbound) VCs. Use the value given on your subscription form. Switched (two-way) Quantity Number of Switched (two-way) VCs. Use the value given on your subscription form. Switched (outbound) Quantity Number of Switched (outbound) VCs. Use the value given on your subscription form. Step 3.
Configuration Configuring the X.25 Link Figure 3-3 Configure Internet Address The “Configure Internet Address” dialog gives you a yes or no option to configure an IP address for this port. Step 2. Choose Yes or No to configure an IP address. If you select No, you indicate that no IP address is associated with this X.25 port. When you select No, all other fields in this dialog disappears. If you select Yes, you must fill in the other required fields in this dialog.
Configuration Configuring the X.25 Link Step 3. Enter or modify field values as required (refer to the following field descriptions). Table 3-3 Configure Internet Address Field Descriptions Internet Address The identifier by which this interface (port) is known on the network. It consists of four sets of integer values (0 to 255) separated by periods (for example, 192.2.3.6). The IP address must be unique for each X.25 interface. It must also specify a different subnet from the IP address of any other X.
Configuration Configuring the X.25 Link Table 3-4 IP Address and Default Subnet Masks (Continued) IP Address Class Default Subnet Mask A.B.*.* (A between 128 and 191) (B between 0 and 254) B 255.255.0.0 A.B.C.* (A between 192 and 239) (B,C between 0 and 254) C 255.255.255.0 A.B.C.* (A between 240 and 254) (B,C between 0 and 254) D Not Allowed The Internet address is composed of two addresses: the network address and the subaddress. Zero (0) and -1 are not allowed in the subaddress. Step 4.
Configuration Configuring the X.25 Link Enter or modify field values as required (refer to the field descriptions below). Table 3-5 Modify IP over X.25 Defaults Field Descriptions Idle Timer Sets the number of seconds a circuit stands idle before it is cleared by IP. The range is 0 to 32767. The default is 600. Hold Timer Sets the number of seconds a circuit may be inactive before it is designated as inactive.
Configuration Configuring the X.25 Link Figure 3-5 Verify Level 3 Values Step 2. Enter or modify field values as required (refer to the field descriptions below). Table 3-6 40 Verify Level 3 Values Field Descriptions Fast Select Accepted If fast select is enabled (Yes), up to 128 octets of information can be transferred in call request and clear packets. The default is No (disabled). See your subscription form. Flow Control Negotiation The default is No (disabled).
Configuration Configuring the X.25 Link Step 3. Click on Modify Flow Control Settings to modify Switched and Permanent VC flow control settings. The following dialog appears: Figure 3-6 Step 4. Select either Modulo-8 or Modulo-128 to set level 3 Modulo parameters. The default is Modulo-8. The valid window-size values for Modulo-8 range from 1 to 7. For Modulo-128, the valid window-size values range from 1 to 127.
Configuration Configuring the X.25 Link Enter or modify field values as required (refer to the field descriptions below). Table 3-7 Table 3-8 42 Switched VC Flow Control Field Descriptions Default Packet Size: Inbound & Outbound Maximum packet size to be used over an SVC. The range is 16 through 4096 octets. The default is 128 for inbound and outbound packets. Use the value given on your subscription form.
Configuration Configuring the X.25 Link Step 5. Click on Modify Throughput Class Settings to modify Switched and Permanent VC throughput class settings. The following dialog appears: Figure 3-7 Step 6. Enter or modify field values as required (refer to the field descriptions below). Table 3-9 Modify Throughput Class Settings Field Descriptions Switched VC Default: Inbound and Outbound Chapter 3 CCITT class number.
Configuration Configuring the X.25 Link Table 3-9 Modify Throughput Class Settings Field Descriptions Switched VC Negotiated: Inbound and Outbound Table 3-10 CCITT class number. If Throughput Class negotiation is enabled, this value is used as the opening bid for outbound calls and as a counter offer when the inbound opening bid is higher. The range is 3 through 13, and the default is 11. See the table below for CCITT class numbers and corresponding line speed Baud rate.
Configuration Configuring the X.25 Link If you subscribe to a public network, the network provider will provide the appropriate settings for all level 2 parameters. These settings will differ depending on the network provider and the type of service to which you subscribe. Refer to your Network Subscription Form for the correct settings for your configuration. NOTE Step 1. At the “Configure X.25 Card” window, select Verify Level 2 Values.
Configuration Configuring the X.25 Link Step 2. Enter or modify field values as required (refer to the field descriptions below). Use the Help button to display information and instructions for each field. Table 3-11 NOTE Verify Level 2 Values Field Descriptions k - Level 2 Window Size Maximum number of frames that can be transmitted without an acknowledgment. The range is 1 through 7 for Modulo-8 and 1 through 127 for Modulo-128. The default is 7. Use the value given on your subscription form.
Configuration Configuring the X.25 Link Step 4. Click on OK to complete X.25 software configuration and save your changes. Your X.25 interface (port) should appear in the object list with status Enabled (no problem found and link connected correctly). If not, carefully repeat the steps in this chapter until the configuration is enabled. If your port is not connected to a running network, it will display as configured. You have completed the interface configuration. Step 5.
Configuration Configuring Remote System Access Configuring Remote System Access Follow the steps below to configure access to other hosts and systems that use TCP/IP protocol. (The procedures in this section are optional. Your X.25 link software does not require that you configure access to other systems). NOTE System Administration Manager (SAM) is deprecated in the 11iv3 release of HP-UX. HP System Management Homepage (HP SMH), an enhanced version of SAM, is introduced for managing HP-UX. Step 1.
Configuration Configuring Remote System Access Figure 3-9 Add Internet Connectivity Dialog Step 5. Enter or modify field values as required (refer to the field descriptions below). Use the Help button for information and instructions for each field. A Provide X.25 Information button may appear on this dialog depending on the Internet address you configure. If it does, follow the instructions in Step 6.
Configuration Configuring Remote System Access Table 3-12 Add Internet Connectivity Field Descriptions Internet Address Identifier by which the remote system is known on the network. It is composed of four integers (0 to 255) separated by periods (for example, 192.2.3.6). Use the Add Aliases button to assign one or more aliases (in alphanumeric format) to the IP Address for easier referencing.
Configuration Configuring Remote System Access Figure 3-10 Step 7. Enter or modify field values as required (refer to the field descriptions below).
Configuration Configuring Remote System Access Table 3-13 52 Provide X.25 Information Field Descriptions X25 Address X.25 address (sometimes referred to as the X.121 address) of the remote system. The X.25 address assigned by the network provider uniquely identifies the node in an X.25 network. The address consists of a maximum of 15 digits. You must complete this field. Switched VC Enable this field if a switched virtual circuit (SVC) will be used for this connection.
Configuration Configuring Remote System Access Step 8. Click on Apply or OK. The Apply button leaves you in the current dialog so you can configure other remote systems; the OK button returns you to the Internet Addresses (& Routes) object list. SMH updates the object list to include the remote system you configured regardless of which button you used.
Configuration Configuring X.25 over LLC2 Configuring X.25 over LLC2 This section describes how to configure X.25 over LLC2. Configuring X.25 over LLC2 allows X.25 layer 3 to connect to DLPI instead of LAP-B and provides the X.25 functionality on top of LAN cards such as Ethernet, FDDI, and TokenRing. NOTE In this document, an XOL interface on the peer or local system is referred to as “box”.
Configuration Configuring X.25 over LLC2 Table 3-14 lists the XOL specific parameters that must be defined while configuring an XOL interface. Table 3-14 Additional XOL specific configuration parameters Field Format device Device name string. Name of the LAN card where the XOL interface is configured. XOL_logical_port_id Integer 0-n The XOL logical port identifier for the XOL interface on the given LAN card. One hexadecimal value. This value must be prefixed with 0x.
Configuration Configuring X.25 over LLC2 Table 3-14 Additional XOL specific configuration parameters (Continued) Field Format Value standby_device** Device name string Name of the standby LAN device used for local failover. For more details about this parameter, see “Configuring the High Availability Feature for X.25 over LLC2” on page 81. Required only for local failover support.
Configuration Configuring X.25 over LLC2 Example 3-1 Sample File with the Old Parameters in the Old Format device lan00x7c lan_box_id 1 lan_box_addr 0x080009c4728a 0x7e Example 3-2 device Sample File with the New Parameters in the New Format lan0 XOL_logical_port_id 1 XOL_destination_macaddr 0x080009c4728a XOL_DSAP 0x72 XOL_SSAP 0x7C standby_device lan1 XOL_floating_macaddr 0x0060B0A4EBE5 A sample generic configuration file is available for reference.
Configuration Configuring X.25 over LLC2 X.121_packet '' “ (TransPacaddressing) name interface0 # use a null (i.e.
Configuration Configuring X.
Configuration Configuring X.25 over LLC2 • To enable the cmns, complete the following steps: Step 1. Run the following command at the CISCO console: Configure Terminal Step 2. Run the following command at the CISCO console: Interface fastethernet 1/0 Step 3. Run the following command at the CISCO console: cmns enable Step 4. Run the following command at the CISCO console: • To add routing entries to X.25 routing table, complete the following steps: Step 1.
Configuration Configuring X.25 over LLC2 config_file is the generic X.25 product configuration file and llc2_config_file is the LLC2 specific configuration file. A sample invocation is as shown below: x25init -c x25init_def -L llc2_conf_def This command is executed once per box. It can be executed with different file but with the same file. Stopping To stop the communication with one box, the x25stop command is executed with the -L option.
Configuration Configuring X.25 over LLC2 One Lan and Two Boxes configuration A graphical representation of the above configuration with some arbitrary values for the MAC addresses and lan-ids is shown below: Figure 3-11 One LAN, Two Boxes Configuration To connect HOST to BOX 0 To implement the above configuration, the following configuration files need to be created on the HOST system. • Generic X.
Configuration Configuring X.25 over LLC2 The file x25_host_box_0 should contain all the mandatory level 2 and level 3 parameters.
Configuration Configuring X.25 over LLC2 To implement the above configuration, the following configuration files need to be created on the BOX 0. • Generic X.25 configuration file, x25_box_0_host • LLC2 configuration file, llc2_lan_1 The generic X25 configuration file has to be created in the /etc/x25 directory using the example configuration file, /etc/x25/x25init_llc2_smpl.
Configuration Configuring X.
Configuration Configuring X.25 over LLC2 Figure 3-12 Two Lans, One Box per Lan configuration To Configure Host to LAN0 to Box0 To configure the Host to LAN 0, BOX 0 communication the following configuration files need to be created. • Generic X.25 configuration file, x25_lan_0_box_0 • LLC2 configuration file, llc2_lan_0_lan_1 The x25_lan-0_box_0 file will contain all the level 3 and level2 parameters.
Configuration Configuring X.25 over LLC2 The LLC2 configuration file, llc2_lan_0_lan_1 will have the following entires: lan0 lan1 1 1 To configure Host to LAN 1 to BOX 1 To configure the Host to LAN 1 to BOX 1communication, the following configuration file need to be created. • X.25 generic configuration file, x25_lan_1_box_1 • LLC2 configuration file, llc2_2_lan_0_lan_1 The x25_lan_1_box_1 file is created in the /etc/x25 directory. It will contain all the level 2 and level 3 parameters.
Configuration Configuring X.25 over LLC2 To implement the above configuration, the following configuration files need to be created on the BOX 0. • Generic X.25 configuration file, x25_box_0_host. • LLC2 configuration file, llc2_lan_2 The generic X25 configuration file has to be created in the /etc/x25 directory using the example configuration file, /etc/x25/x25init_llc2_smpl. The file x25_box_0_host must contain all the mandatory level 2 and level 3 parameters.
Configuration Configuring X.25 over LLC2 The generic X25 configuration file has to be created in the /etc/x25 directory using the example configuration file, /etc/x25/x25init_llc2_smpl. The file x25_box_0_host should contain all the mandatory level 2 and level 3 parameters.
Configuration Configuring X.25 over LLC2 70 • Check the remote node’s hardware address using lanscan. Use the same hardware address in the generic X.25 configuration file. If you modify the hardware address to correct the error then, re-initialize the card using x25init. • If the nodes are connected back to back, check if the SAP’s are identical for both the nodes in the generic X.25 configuration file.
Configuration Configuring PAD Services Configuring PAD Services This section contains step-by-step instructions for configuring PAD services. Skip this section if you don’t need to configure PAD services. The procedures in this section are optional. Your X.25 link software does not require you to configure PAD services. You can use SMH to add or modify the following: • PAD terminal emulation (local to remote) • PAD support server (remote to local) • PAD printer server • PAD UUCP server • X.
Configuration Configuring PAD Services SMH displays an object list that shows all remote systems currently configured for PAD terminal emulation. Step 4. Select Add from the Actions menu to configure PAD terminal emulation for an unlisted remote system, or highlight a remote system from the list and select Modify. Step 5. Enter or modify field values as required. Step 6. Click on Apply to apply the new settings and to add additional system connections. Click on OK to save changes and exit this dialog.
Configuration Configuring PAD Services Step 5. Enter or modify field values as required. Step 6. Click on Apply to apply the new settings and to add additional PAD support servers. Click on OK to save changes and exit this dialog. Step 7. Select Exit from the List menu to return to the “X.25 PAD Services” dialog. Step 8. Select the next PAD service you need to configure from the list on the “X.25 PAD Services” dialog.
Configuration Configuring PAD Services Step 1. At the SMH main window, highlight “Networking and Communications” and select Open Item from the Actions menu. Step 2. At the “Networking and Communications” window, highlight X.25 PAD Services and select Open Item from the Actions menu. Step 3. Highlight UUCP Server and select Open Item from the Actions menu. SMH lists all remote systems currently configured for X.25 PAD UUCP connectivity. Step 4.
Configuration Configuring PAD Services NOTE The X.3 values that you configure here are initially downloaded to the PAD. As the terminal characteristics of your session change, the X.25 software automatically downloads new values for certain parameters. Do not be alarmed if the values of some parameters are different from the values you initially specified. Step 1. At the SMH main window, highlight “Networking and Communications” and select Open Item from the Actions menu. Step 2.
Configuration Configuring the High Availability Feature Configuring the High Availability Feature The X.25 link software provides integration of the X.25/Streams solution to the High Availability HP MC/ServiceGuard feature on HP 9000 Series 800 Systems, allowing local and remote failure recovery. This feature requires that the HP MC/ServiceGuard product (B3936AA) has been installed and that the X.25 software uses switches that support Hunt Group Facility allowing multiple DTEs to share a common X.
Configuration Configuring the High Availability Feature X.25 Cluster Definition To configure a High Availability cluster, use SMH to define all cluster systems by giving their: NODE_NAME NETWORK_INTERFACE HEARTBEAT_IP X.25 Commands to be Configured in High Availability Packages Start X.25 link x25init -c x25config -a ipmap -d x25dev (see x25init (1m)) Stop X.25 link x25stop -d x25dev (see x25stop (1m)) Monitor X.25 link x25ifstate -d x25dev -H (see x25ifstate (1m)) X.25 Package Definition An X.
Configuration Configuring the High Availability Feature to monitor the X.25 link status. It could be either a script based on x25ifstate or the x25ifstate command directly, depending on your configuration. Package Control Script Location: location of the script to start/stop the X.25 link and execute the service(s). X.25 High Availability Configuration General Solution for Local and Remote Failover PKG A Client Package A Hunt Group Connections X.
Configuration Configuring the High Availability Feature # e.g.# SERVICE_NAME [1] = # SERVICE_CMD [1] = # START OF CUSTOMER DEFINED FUNCTIONS function customer_defined_run_cmds { #ADD customer defined run commands : # do nothing instruction, because a function must contain at least one command.
Configuration Configuring the High Availability Feature $ x25check 250207 -s 32 -n 1 X25CHECK (c) COPYRIGHT Hewlett-Packard Company 1988. Test Starts on .. Wed Dec 8 09:15:47 1993 Initialization of the test... CALL packet sent ... DATA packet sent ... DATA packet received The following figures have been measured on the network: Set up time : 286 ms Transit time : 245 ms Remote Connection Succeeded If your system has multiple X.
Configuration Configuring the High Availability Feature for X.25 over LLC2 Configuring the High Availability Feature for X.25 over LLC2 This section describes how to configure the local and remote failover features for X.25 over LLC2 (XOL) interface. It also describes the local, remote, and a combination of local and remote failover. WARNING The failover is not transparent and results in loss of data and existing connections. After a failover, the XOL connections must be re-established.
Configuration Configuring the High Availability Feature for X.25 over LLC2 NOTE The routing table of the router connected to the host system must be updated with the unique MAC address identified by the user. If the XOL router supports the Hunt Group facility for XOL HA, the unique MAC address may not be required to achieve the HA functionality for XOL interface. For more information on Hunt Group facility, see “Configuring the High Availability Feature for X.25 over LLC2” on page 81.
Configuration Configuring the High Availability Feature for X.25 over LLC2 Configuring XOL HA for Local Failover Without ServiceGuard In Figure 3-13, system A has two LAN cards, namely, lan0 (the primary LAN card) and lan1 (the standby LAN card). The standby LAN card provides local failover for the XOL interface with X.121 address 1111. The user supplied, unique MAC address that is specified in the XOL configuration file as a value for the field XOL_floating_macaddr, for that LAN segment is uMAC.
Configuration Configuring the High Availability Feature for X.25 over LLC2 X.25 connection must be re-established on the XOL interface. When the card lan0 comes up later, it is configured with the factory default MAC address. Figure 3-14 After the Failover To configure XOL local failover, complete the following steps: NOTE 84 The XOL HA feature is enabled by default in HP-UX 11i v3. Therefore, the -enableXOLHA option is no longer required.
Configuration Configuring the High Availability Feature for X.25 over LLC2 Step 1. To configure the standby device and the unique MAC address in the configuration file of the XOL primary interface, modify the following syntax: Standby_device # used for local failover XOL_floating_macaddr NOTE Local failover is automatically enabled by defining a standby_device in the configuration file.
Configuration Configuring the High Availability Feature for X.25 over LLC2 x25init -c -L Remote Failover NOTE Remote failover, with or without local failover, requires the installation of the ServiceGuard product on the system. For more information on HP MC/ServiceGuard product, see Managing MC/ServiceGuard document. In the ServiceGuard cluster, the remote failover works between LAN cards on different nodes.
Configuration Configuring the High Availability Feature for X.25 over LLC2 Figure 3-15 Before the Failover If the SG package for XOL detects an error in the XOL interface, the package is stopped on the primary system and the equivalent package starts on the standby system. When the SG package is stopped on system A, the XOL interfaces (and optionally applications) on the failed LAN card are stopped. An attempt is made to configure LAN card on system A with the factory default MAC address.
Configuration Configuring the High Availability Feature for X.25 over LLC2 Figure 3-16 After the Failover XOL Cluster Definition You must define the cluster by providing the system names that are part of SG cluster. X.
Configuration Configuring the High Availability Feature for X.25 over LLC2 x25stop -d /dev/x25_0l1 XOL Package Definition An XOL SG package is required to configure a highly available XOL interface on all nodes in the SG cluster. This package allows HP MC/Service Guard to automatically: • Assign a unique MAC address (using the lanadmin command) to the LAN card in use. • Start the X.25 link (x25init command) when the X.25 package starts.
Configuration Configuring the High Availability Feature for X.25 over LLC2 NOTE When the XOL interface goes down, the service command (x25ifstate) exits. The SG performs a package failover to the standby node configured in the SG cluster. The SG package file that contains the X.25 commands is /etc./cmcluster/pkg*/control.sh file (one per XOL package). Following is a sample SG package file: Example 3-6 XOL SG package for remote failover # SERVICE NAMES AND COMMANDS SERVICE_NAME [0] =pkg1.
Configuration Configuring the High Availability Feature for X.25 over LLC2 } function customer_defined_halt_cmds { # START of customer defined halt commands. /usr/sbin/x25stop -d /dev/x25_0l1 Sleep 2 test_return 52 # END of customer defined halt commands } Remote Failover with Local Failover Support Using Service Guard This is a combination of local failover and remote failover.
Configuration Configuring the High Availability Feature for X.25 over LLC2 NOTE Enabling or disabling of HA feature for XOL interface is system wide. Before enabling or disabling the HA feature on a system, all existing XOL interfaces must be stopped. The XOL HA feature is enabled by default on 11i v3. Step 1.
Configuration Configuring the High Availability Feature for X.25 over LLC2 In the event of a failover, the XOL_floating_macaddr is moved from the Primary LAN card to the standby LAN card. HP recommends that you use the primary and standby LAN cards only for the XOL links configured with HA feature. NOTE Step 2. Configure the SG package. For information on achieving remote failover functionality, see “XOL Package Definition” on page 89.
Configuration Configuring the High Availability Feature for X.25 over LLC2 # SERVICE NAMES AND COMMANDS SERVICE_NAME [0] =pkg1.Service_Name_01 (same SERVICE_NAME as in pkg conf) SERVICE_CMD [0] ="/usr/sbin/x25HAmonitor -c x25config_llc2 -L llc2_conf_def -m " SERVICE_RESTART [0] = " " # Unique MAC address in the subnet (LAN segment) which is not in use. This will be the Active MAC address on the active node in the cluster.
Configuration Configuring the High Availability Feature for X.25 over LLC2 function customer_defined_halt_cmds { # START of customer defined halt commands.
Configuration Verifying the X.25 Link Verifying the X.25 Link After completing the installation and configuration instructions, follow these steps to verify your link: Step 1. If you are using IP over X.25, use the ping command to check that the IP connection is operating properly. Refer to your man pages for details on the ping command. Examples are given below. To check the connection to and from the network to the IP address (for example, 193.6.3.2), type: ping 193.6.3.
4 Chapter 4 OLA/R Overview and Concepts 97
OLA/R Overview and Concepts Introduction Introduction The letters O, L, A and R stand for On Line Addition [and] Replacement. This, of course, refers to the ability of a PCI I/O card to be replaced/added to an HP-UX computer system designed to support this feature without the need for completely shutting down, then re-booting the system or affecting other system components. The system hardware uses the per-slot power control combined with operating system support to enable this feature.
OLA/R Overview and Concepts Important Terms and Concepts Important Terms and Concepts Table 4-1 Terms used in this section Term IMPORTANT Meaning OLA/R All aspects of the OLA/R feature including On-line Addition (OLA) and On-line Replacement (OLR). Power Domain A grouping of 1 or more interface card slots that are powered on or off as a unit. target card / target card slot The interface card which will be added or replaced using OLA/R, and the card slot it resides in.
OLA/R Overview and Concepts Planning and Preparation Planning and Preparation For the most part SMH prevents you from performing OLA/R procedures that would adversly affect other areas of the server. This section provides you with important information that can help minimize errors or problems when performing OLA/R procedures. Card Compatibility On-Line Addition When on-line adding an interface card, the first issue that must be resolved is whether the new card is compatible with the system.
OLA/R Overview and Concepts Planning and Preparation question about the driver’s presence, or if you are not certain that the replacement card is identical to the existing card, you can use ioscan together with rad to investigate. • During the replacement process, the original driver instance runs in a suspended state. I/O to the card is either queued or failed while the card is suspended. When the replacement card is brought on-line, the driver instance resumes normal operation.
OLA/R Overview and Concepts Planning and Preparation could replace the card when the server is off-line, or if you must take action immediately, you can use rad to attempt an on-line addition of a backup card and deletion of the target card. Failover Actions / Single Points of Failure In most cases, the system will automatically fail over to the alternate resource when a card is suspended. However, some subsystems might require manual intervention.
OLA/R Overview and Concepts How to On-line Replace (OLR) a J3525A PCI Card using SMH How to On-line Replace (OLR) a J3525A PCI Card using SMH WARNING When performing online replacemant, the stack for all the ports of the interface card under consideration will be stopped before repalcement. They will be restarted after the repalcement. Thus any user application which has open connections will receive DISCONNECT messages.
OLA/R Overview and Concepts How to On-line Replace (OLR) a J3525A PCI Card using SMH Output messages from the CRA process are presented in the Analyze Critical Resources screen which will be shown before you can proceed. The messages displayed on this screen and the availability to continue on from it (“OK” button activated) depend on the results of the analysis. Table 4-2 104 Three Possible Critical Resource Analysis (CRA) Outcomes Outcome Notes No critical resources identified.
OLA/R Overview and Concepts How to On-line Replace (OLR) a J3525A PCI Card using SMH NOTE The cables must be removed from the PCI I/O card before proceeding with the OLR operation. Step 8. Once you click the “OK” button on the Analyze Critical Resources screen, SMH begins to take the selected card out of service. SMH requests a suspend operation for the driver of the selected card. Step 9. Once the drivers are suspended, SMH turns off the power to the slot in which the card is located. Step 10.
OLA/R Overview and Concepts How to On-line Replace (OLR) a J3525A PCI Card using SMH Step 15. SMH completes the operation by reversing the sequence of actions. That is, SMH will: a. return power to the card slot, and enables power to the Green LED b. identify the new card c. resume driver operations to the card Step 16. Connect the cables to the card.
OLA/R Overview and Concepts How to On-line Add (OLA) a J3525A PCI Card using SMH How to On-line Add (OLA) a J3525A PCI Card using SMH NOTE On-line addition will recognize and claim the interface card only if the X.25/9000 software is already loaded on the system. Also check if the appropriate J3525A drivers are loaded in the kernel. Step 1. Read the information (below) in this step. An understanding of this section is important in order for you to make the correct decision later in the procedure. 1.
OLA/R Overview and Concepts How to On-line Add (OLA) a J3525A PCI Card using SMH Output messages from the CRA process are presented in the Analyze Critical Resources screen which will be shown before you can proceed. The messages displayed on this screen and the availability to continue on from it (“OK” button activated) depend on the results of the analysis. Table 4-3 Three Possible Critical Resource Analysis (CRA) Outcomes Outcome Notes No critical resources identified.
OLA/R Overview and Concepts How to On-line Add (OLA) a J3525A PCI Card using SMH NOTE Do not connect the cables to the card at this point Step 10. Once you have inserted the new card, return to the console and click “OK” on the dialog, assuming there is one. At this point, SMH will: a. return power to the card slot and enable power to the Green LED b. attach drivers by running ioscan on the new hardware c.
OLA/R Overview and Concepts How to On-line Add (OLA) a J3525A PCI Card using SMH 110 Chapter 4
5 Chapter 5 Diagnostic Utilities 111
Diagnostic Utilities Using Diagnostic Utilities Using Diagnostic Utilities This chapter describes how to use the X.25 diagnostic utilities. The diagnostic utilities provided with your X.25 link are described briefly in the following table. Refer to Chapter 8, Troubleshooting, if you need help deciding which utility to use. Table 5-1 Available Diagnostic Utilities Utility Description Refer to: x25check x25server Tests connectivity up to X.25 level 3 between the local and remote nodes.
Diagnostic Utilities Using Diagnostic Utilities Figure 5-1 Scope of X.25 Diagnostic Utilities x25stat options UserWritten Programs netstat options OSI Services x25check/x25server PSIDAD Berkeley IPC Programmatic Access OTS to PLP Translator OTS/9000 X.25 Packet Level -m -v -t -x -c -z -g LAP-B -f X.21bis or V.
Diagnostic Utilities Before Using the Diagnostic Utilities Before Using the Diagnostic Utilities Some of the diagnostic utilities request or display information about the X.25 interface card using one or more of the naming conventions described below. Keep these conventions in mind when using the diagnostic utilities: • the name of the device file, uses the format x25_npx, where n represents the card instance number (0 to 15).
Diagnostic Utilities x25check and x25server x25check and x25server These commands are used together to test the connection between a source node and a destination node, up to and including X.25 programmatic access level. x25check is a major tool for debugging the X.25 subsystem and for checking the configuration for that subsystem. x25server is a background process that waits for call requests from x25check. The x25server must be running before you execute x25check.
Diagnostic Utilities x25check and x25server Initialization of the test... Do you want to send only a CALL packet (no DATA)? (y/n) > y Enter the X.121 Address of the remote node ( ) > 2502057 Enter the programmatic access name through which you want to check ( ) > interface2 Use reverse charging? (y/n) > y Closed user group identification number (Blank or xx or xxxx) > CALL packet sent ...
Diagnostic Utilities x25check and x25server VC_CLEAR Packet was received with CAUSE 0 : DTE Originated DIAG 245 : Cannot Interpret Diagnostic Code Example 2: Running x25check With an X.121 Address In the example below, the destination X.121 address of the destination node is specified as a parameter to x25check. This example shows a successful test and assumes the closed_user_group to be 51. $ x25check 250207 -i interface0 -g 51 X25CHECK (c) COPYRIGHT Hewlett-Packard Company 1988. Test Starts on ..
Diagnostic Utilities x25stat x25stat This command displays the status, configuration, and VC statistics of an X.25 interface. See the man pages on x25stat for syntax and parameter information. Example 1: Displaying the Current Configuration x25stat -c -d x25_0 -------- X.25 CONFIG ----------General Parameters: X.121 Address: 110 X.
Diagnostic Utilities x25stat Example 2: Displaying Global Statistics See the tables provided after this example under the headings “SUBNETWORK STATISTICS FOR X25” and “STATISTICS FOR LAPB” for help in interpreting the displayed “State” of the X.25 link.
Diagnostic Utilities x25stat Other: Bad length 0 Unknown 0 Erroneous 0 Discarded 0 Ignored 0 0 Retransmitted 0 ----------------------------------------------------------Timers: T1 0 T4 0 T4 (N2 times) 0 STATISTICS FOR WAN -----------------Subnetwork Link State : HDLC_ESTB WAN: 83 good frames transmitted 87 good frames received 0 transmit underruns 0 receive overruns 0 CRC/frame errors received 0 received frames with no buffer 0 received frames with no flow control 0 receive buffer overflows The level 3 “S
Diagnostic Utilities x25stat Table 5-2 Level 3 State (Continued) Waiting link disc reply Level 2 going down Buffer to enter WtgRES Restart sent after retry Buffer to enter L3restarting Waiting for restart reply during “link going down” phase Buffer to enter L_disconnect Waiting for buffer to clear VCs during “link going down” phase Unknown Unable to define error/problem a. DXE is DCE or DTE b.
Diagnostic Utilities x25stat The level 1 “Link state” under the “STASTISTICS FOR WAN” heading can be: Table 5-4 Level 1 Link State Output on Screen Description/Meaning HDLC_ESTB WAN connection established HDLC_IDLE No WAN connection established HDLC_DISABLED WAN connection disabled The output under the heading “STATISTICS FOR WAN” is explained in the table below: Table 5-5 Statistics for WAN Output Output on Screen 122 Description/Meaning transmit underruns Shows the number of times a transmis
Diagnostic Utilities x25stat Example 3: Displaying Virtual Circuit Data Packet Counters The following example shows the output when there is one virtual circuit connected. Note that the virtual circuit specified in the command line is 64, in decimal. The LCN shown in the example output is displayed as 40, the hexadecimal equivalent of 64.
Diagnostic Utilities x25stat Table 5-6 VC State (Continued) 4 - P3 INCOMING CALL received, but not yet replied 6 - Datatransfer Connection established 7 - DXEa busy RNR sent 8 - D2 RESET REQUEST sent, but not yet replied 19 - DXE resetting RESET INDICATION received, but not yet replied 20 - P6 CLEAR REQUEST sent, but not yet replied a. DXE is DCE or DTE. Example 4: Displaying Global X.
Diagnostic Utilities x25stat Subnetwork : 0 Link mode : LC_LAPBDTE Link state : NORMAL ---------------------------------------------------------FRAMES TX_CMD TX_RSP RX_CMD RX_RSP ---------------------------------------------------------Supervisory: RR 45 1045 0 46 RNR 0 0 0 0 REJ 0 0 0 0 Unumbered: SABM 0 1 DISC 0 0 DM 0 0 UA 1 0 FRMR 0 0 Information: I 1280 2551 ----------------------------------------------------------TX RX ----------------------------------------------------------Other: Bad length 0 Unk
Diagnostic Utilities x25stat 0 0 NOTE receive buffer overflows receive aborts T4 under “STASTISTICS FOR LAPB” in the example above is only an internal parameter; it is not configurable.
Diagnostic Utilities x25stat LCI --040 Type VC State Subnetwork Local address Remote Address -------------------- ------------- -------------SVC-2way Datatransfer 0 110 202 Note that the LCI number given in this example output is displayed in hexadecimal, not decimal. Example 7: Displaying Current IP to X.25 Address Mapping x25stat -a IP Address PktszWindow VCs 192.25.0.12 1 1 192.25.0.22 1 1 192.25.0.32 1 1 CUG GOO11 - SUB-REV y y y BAR-REV n n n X25 Address 0.250107.. 0.250112.. 0.250208..
Diagnostic Utilities x25mibstat x25mibstat This is a programmatic application that can be used to display statistics for X.25 sub-systems. Refer to the x25mibstat(1) man pages for instructions on using this utility. Some examples of x25mibstat statistics are provided in the following table.
6 Chapter 6 PAD Services 129
PAD Services Introduction Introduction This section describes X.25/9000 PAD (Packet Assembler/Disassembler) Services which enable HP 9000 computers to connect and communicate with remote systems over a Packet Switching Network (PSN). NOTE Refer to “Configuring PAD Services” in Chapter 3 for information on configuring PAD Services with SMH.
PAD Services Introduction Recommendation X.29 is the protocol for the exchange of messages between the host and PADs. Recommendation X.3 defines a set of parameters that control PAD operation. The following illustration shows the relationship between each of these recommendations. Figure 6-1 PAD Support Protocols Packet Switching Network HOST X.25 PAD X.25 T X.28 X.3 X.29 PAD services and the HP 9000 host All of the PAD services can be seen as a pipe through which data is passed from X.
PAD Services Remote PAD Support (x29server) Figure 6-2 PAD Services as a Pipe PSN X.25 HP 9000 host X.25 Level 3 PAD Services PTY User Applications (uucp, lp, login, etc.) Remote PAD Support (x29server) Overview The x29server user-level process provides support for communications with terminals attached to a remote PAD. This process accesses X.25 level 3 through Berkeley Sockets (programmatic interface) and has an interface to PTYs (see illustration below).
PAD Services Remote PAD Support (x29server) Figure 6-3 Remote PAD Support HP 9000 host User Level T UNIX Applications x29server T PAD BSD T Sockets X.25 Level III Kernel Pseudoterminal drivers (PTYs) Packet-Switching Network The x29server remote PAD support provides capabilities for: • Managing call acceptance. • Launching applications automatically. • Ensuring system security. • Monitoring access and data transfers.
PAD Services Remote PAD Support (x29server) The x29server process employs Berkeley Sockets (at X.25 level 3) to set up dedicated listening sockets that only handle calls arriving at a particular subsystem. Addressing information contained in incoming call request packets enables the listening process to determine if the call should be accepted.
PAD Services Remote PAD Support (x29server) NOTE See the man pages for x29server for its syntax and parameters. Supported Remote PAD Terminals • 700/41, 700/92, 700/94, 700/22 • 2392A • 2393A • Vectra with AdvanceLink Terminal Emulation Configuring Remote PAD Support You can configure remote PAD support with SMH or by editing configurable parameters in the /etc/x25/x29hosts and /etc/x25/x3config files.
PAD Services Remote PAD Support (x29server) pad_spt Parameters This section describes the remote PAD support parameters shown in the above example: interface_name Optional. This is a character string (maximum 12 characters) with no wildcards allowed. If this field is not present, x29server will listen on all X.25 interfaces. remote_x121 Mandatory (no default value). This is the calling address (the address of the remote system).
PAD Services Remote PAD Support (x29server) The name of the corresponding master PTY driver must also exist in a file beginning with “ptym” (format: ptym [filename]) located in the /dev/ptym/ directory: Wildcards are not allowed in these file and path names. If the pty_slave_fname field contains an entry, x29server considers any communication initiated by this entry to be restricted to exclusive use by the TTY/ PTY (master/slave) pair.
PAD Services Remote PAD Support (x29server) problems. Note that size and parity processing will only be performed on input from the PAD to the system. x3 Optional. This is the X.3 configuration set name for this x29server session. If this entry is included in the /etc/x25/x29hosts file, the configuration name and its set of X.3 parameters must also be specified in the /etc/x25/x3config file. If more than one X.3 configuration set with the same name exists in x3config, the first one is used. X.
PAD Services Remote PAD Printer Support (x29printd) CAUTION Use extreme caution when specifying applications other than the default (login) application. Since the x29server process is started with superuser privileges, it gives root privileges to applications triggered by incoming calls. You can automatically launch a user application by: • configuring the application field with the relevant application name as its value without specifying the cud field.
PAD Services Remote PAD Printer Support (x29printd) Figure 6-5 Remote Printer Support HP 9000 User Level LP Spooler or other Spooler x29printd PAD Printer BSD Sockets X.25 Level III Kernel Pseudoterminal drivers (PTYs) Packet-Switching Network When x29printd begins execution, it examines the /etc/x25/x29hosts file for all PAD devices configured with a PAD type printer. For each of these configured devices, x29printd monitors all print requests sent to the spooling system (see Appendix B, X.
PAD Services Remote PAD Printer Support (x29printd) The following kernel parameters should not be modified and should retain the values indicated below: • NFILE =(16 x (NPROC + 16 + MAXUSERS)/(10 + 32+(2 x NPTY)) • NINODE = ((NPROC + 16 + MAXUSERS) + 32 + (2 x NPTY) + (SERVER_NODE x 18 x NUM_CODES)) For more information on dependencies, refer to your System Administration Tasks manual. NOTE See the man pages for x29printd for its syntax and parameters.
PAD Services Remote PAD Printer Support (x29printd) name Mandatory. This is the name of the programmatic interface that will be used for call setup. There is no default for this entry. This name must match the programmatic access name (also called name) specified in the x25init X.25 configuration file. remote_x121 Mandatory (no default). This is the X.121 address of the PAD device plus the subaddress of the printer. This address is required for calls to be initiated. Only digits 0 through 9 are legal.
PAD Services Remote PAD Printer Support (x29printd) x3 Optional. This is the X.3 configuration set name for this x29server login session. If used, the configuration set name (and X.3 parameter set) must also exist in /etc/x25/x3config. If more than one X.3 configuration set with the same name exists, the first one found in the file is used. If there is no configuration set name in /etc/x25/x29hosts or no matching X.3 configuration set name in /etc/x25/x3config, default values are used.
PAD Services Remote PAD Printer Support (x29printd) Examples x29printd and lpsched Operation For this example, a printer (a RuggedWriter) is connected on port 5 (or B1 on HP 2335a PADs) to a PAD whose address is 4085551203. The address of the printer in this case would be 408555120305.
PAD Services Remote PAD Printer Support (x29printd) Step 3. Configure the printer in the spooler system with the following commands: lpshut lpadmin -v/dev/x29/x29printer1 -pfoo -mruggedwriter lpsched accept foo enable foo lpshut(1M) is necessary since lpadmin will not execute when lpsched is running. You must restart LP scheduler after lpadmin. lpsched(1M) schedules requests taken by lp(1) for line printing. After a printer is configured in the spooler, you must enable it to accept printing requests.
PAD Services UUCP Support (x29uucpd) UUCP Support (x29uucpd) Overview x29uucpd provides UUCP connectivity on X.25 networks using CCITT Recommendations X.3 and X.29. With x29uucpd, users on HP 9000 host systems with X.25 access and UUCP can execute UUCP subsystem commands to other systems running X.25, PAD support, and UUCP. x29uucpd interfaces with the X.25 subsystem through BSD Sockets to initiate call request packets to remote systems on X.25.
PAD Services UUCP Support (x29uucpd) Figure 6-6 Remote Printer Support Receiving HP 9000 Sending HP 9000 User Level UUCP Pseudoterminal drivers (PTYs) User Level x29uucpd Kernel uucico Slave x29server X.25 X.25 Level III Level III Kernel Pseudoterminal drivers (PTYs) Packet-Switching Network When x29uucpd is executed, it examines the /etc/x25/x29hosts file for all PAD devices that are configured for UUCP.
PAD Services UUCP Support (x29uucpd) NOTE See the man pages for x29uucpd for full details on syntax and parameters. Table 6-1 File Contents /etc/x25/x29hosts pad_uucp parameters for each remote host /etc/passwd uucp entry /etc/x25/x3config optional X.
PAD Services UUCP Support (x29uucpd) name Mandatory. This is the name of the programmatic interface that will be used for call setup. There is no default for this entry. If this entry does not exist, the call setup will not be completed and file transfer will not take place. This name must match with the programmatic access name (also called name) specified in x25init. remote_x121 Mandatory. This is the X.121 address of the X.
PAD Services UUCP Support (x29uucpd) x3 Optional. This is the X.3 configuration set name for UUCP file transfers. If this entry is used in /etc/x25/x29hosts, the configuration set name with its set of X.3 parameters must be specified in /etc/x25/x3config. All legal X.3 parameters contained in the x3config file are downloaded at connection time. If there is more than one X.3 configuration set with the same set name in /etc/x25/x3config, the first one is used.
PAD Services UUCP Support (x29uucpd) Any – indicates that bill can be called at any time. 5 – is the retry duration (dave will try again to connect to bill in 5 minutes). dev_bill – is the name of the remote system declared in dave’s Devices file. f – is the file transfer protocol. HP recommends using f rather than g for better performance. 19200 – is the transfer rate (it must be set at the same speed as that specified in the dave’s Devices file).
PAD Services UUCP Support (x29uucpd) pad_uucp { device name remote_x121 logging x3 } bill interface0 [bill’s X.121_address] 3 default_x3 Refer to “Configuring the x29hosts file” earlier in this section for the definitions of these parameters. Step 6. Launch /usr/sbin/x29uucpd at the HP-UX command prompt. At the “bill” system: Step 7. Make the following modifications to the pad_spt section of /etc/x25/x29hosts file: pad_spt { remote_x121 logging x3 [dave’s X.
PAD Services UUCP Support (x29uucpd) READ=/ \ WRITE=/ \COMMANDS=ALL where the LOGNAME parameter creates a link with dave’s Systems file. Step 11. Test the X.25 connection using: bill# x25server dave# x25check [bill’s X.121 address] If successful, you will receive the message “Remote connection succeeded.” Step 12. Test the files: x29hosts, x3config (at bill) using: dave# padem [bill’s X.121 address] If successful, you will receive the “login” message and you will be able to enter your details. Step 13.
PAD Services UUCP Support (x29uucpd) bill --- --- --- [error message] Refer to the UUCP section in Chapter 9 of the Remote Access: User’s Guide (part number B2355-90037) for more information on UUCP error messages. Step 14. Test the file permissions of both bill and dave using: dave# /usr/lib/uucp/uucico -r1 -x9 -sbill where -r1 indicates that dave is the “master” (for UUCP purposes) and -x9 is the highest debugging level.
PAD Services UUCP Support (x29uucpd) imsg >ˆPROKˆ@msg-ROK Rmtname bill, Role MASTER, Ifn - 6, Loginuser - root rmesg - ‘P’ imsg >ˆPPgfdxˆ@got Pgfdx wmesg ‘U’f Proto started f /*the f protocol for UUCP is selected*/ *** TOP *** - role=1, setline - X gtwvec: dir /var/spool/uucp/bill wmesg ‘H’ got HY- ‘H’ enter frdmsg:HY PROCESS: msg - HY HUP: wmesg ‘H’Y cntrl - 0 send OO 0,imsg >HYˆMˆPOOOOOOˆ@exit code 0 Conversation Complete: Status SUCCEEDED If you receive an error such as “RETRY TIME NOT REACHED,” you ca
PAD Services Local PAD Emulation (padem) Local PAD Emulation (padem) The padem program provides local PAD emulation to enable a local terminal (real or emulated) to connect to a remote system over an X.25 PSN. x29server handles the connection on the remote host side. The remote system can be specified upon execution or with subsequent padem commands issued during operation (see illustration below). Figure 6-7 HP 9000 User Level Packet-Switching Network padem X.
PAD Services Local PAD Emulation (padem) Data Transfer Mode If the X.121 address or the symbolic address of the remote host is specified, padem begins execution in data transfer mode. In data transfer mode, typed text is sent to the remote host and text received from the remote host is displayed at the local terminal. You can re-enter command mode to issue a padem command by pressing Ctrl P. If the VC is cleared at any time (by the remote host or by the X.
PAD Services Local PAD Emulation (padem) name Optional. This is the name of the programmatic interface used for call setup. If this entry does not exist, the default name associated with /dev/x25_0 is used. This name must match the programmatic access name (also called name) in the X.25 configuration file. logging Optional. Specifies the logging level that applies to all calls made during this session. The log file is $HOME/plog.aXXXXX, where the last five characters are from the process ID of padem.
PAD Services Local PAD Emulation (padem) Command line options are given priority over those in the x29hosts file. If options are not specified at the command line or in the x29hosts file, the programmatic access name associated with /dev/x25_0 is used for call setup, the logging level is set to 1, the reverse charge option is disabled, and the default X.3 profile values are used.
PAD Services PAD Commands PAD Commands PAD command signals are grouped into the X.28 PAD command set (defined by CCITT X.28 recommendations) and include an extended command set providing additional functionality. X.28 PAD Command Set clr Clears a virtual circuit (VC), disconnecting the VC from the remote host. int Transmits an interrupt to the remote host. par? Displays all of the X.3 parameters and their current values. The format for the display is: X.
PAD Services PAD Commands Sets the X.3 parameter n to value v and displays the current setting of all parameters. This command is a combination of the set and par? commands. stat Displays status information of a VC. padem responds with “FREE” if no VC is established or with “ENGAGED” if there is a VC established. [r,g[n[n]]-] x121_address [subaddress] [P/Dd..d Performs a virtual call to the remote host defined by its X.121 address.
PAD Services PAD Commands verbose NOTE 162 Puts padem in verbose display mode. When padem operates in verbose display mode, it displays CAUSE, EFFECT, and ACTION messages in addition to the standard diagnostic message. Certain parameters may be changed automatically during the session as a result of PTY reconfigurations by the application at the other side of the connection. These changes will temporarily alter the original defaults set by the PAD Services.
PAD Services Configuring X.3 Profile Parameters Configuring X.3 Profile Parameters X.3 PAD parameters are used to specify how certain I/O operations are performed between Data Terminal Equipment (DTE) and the remote host PAD. These parameters are used to ensure that the local DTE and the remote PAD use the same communications profile. Each of the 22 parameters has an identifier known as the parameter reference. This identifier is an integer value from 1 to 22.
PAD Services Configuring X.3 Profile Parameters Parameter Values config_name Mandatory. Specifies the configuration set name, a character string that identifies the X.3 parameter set. Each config_name must be unique. This is a required parameter for all PAD services if user-defined X.3 parameters are to be used. This name must match the x3 value given in the x29hosts file for pad_spt, printer, or pad_uucp entries.
PAD Services X.3 Parameter Descriptions the current X.3 setting is overwritten on the server. A set command is sent to reset the parameter in the remote PAD. If x29server cannot map the terminal I/O parameter to X.3, the request is processed as a normal terminal I/O ioctl(). When x29printd and x29server transform terminal I/O parameters into X.3 parameters, they intercept the ioctl (tcseta) call and send an X.29 set command with new X.3 parameter values if necessary. The related X.
PAD Services X.3 Parameter Descriptions NOTE Parameters 1 to 18 are available for networks using either the 1980 or 1984 standard. Parameters 19 through 22 only apply to the 1984 standard. Table 6-2 X.3 Parameter Descriptions X.3 Parameter Description 1 - ESC/Data Transfer Specifies whether or not the terminal user will be allowed to escape from data transfer mode in order to send PAD command signals.
PAD Services X.3 Parameter Descriptions Table 6-3 NOTE (Continued) 16 ETX and EOT only. 32 HT, LT, VT, FF only. 64 NUL, SOH, STX, BS, LF, CR, SO, SI, DLE, DC1, DC3, DC4, NAK, SYN, ETB, EM, SUB, FS, GS, RS, and US (all other characters in the first two columns of the International Alphabet #5). 126 All characters, except alphanumerics. 127 All characters are data forwarding. The values listed for parameter 3 may be combined by specifying the sum of the values.
PAD Services X.3 Parameter Descriptions Table 6-4 (Continued) 6 - Service Signals Specifies that the terminal is to receive the PAD service signals that are received by the PAD. PAD service signals are described in X.25: The PSN Connection. 0 indicates that no PAD service signals are received by the terminal, and 1 indicates that the terminal will receive PAD service signals. 7 - On Break Specifies the action to be taken by the PAD when it receives a break signal from the terminal.
PAD Services X.3 Parameter Descriptions Table 6-6 (Continued) 8 - Discard Output This parameter restores data delivery to the terminal after the reception of the break character and value 16 has been specified for X.3 Parameter 7. This value may be modified by the reception of the break character. 0 indicates normal data delivery, and 1 indicates that data is discarded. 9 - Number of CR Padding Chars Specifies the number of buffer characters to be added following a carriage return.
PAD Services X.3 Parameter Descriptions Table 6-7 (Continued) 6 150 7 1800 8 200 9 100 10 50 11 75 from terminal, 1200 to terminal 12 2400 13 4800 14 9600 15 19200 16 48000 17 56000 18 64000 Table 6-8 X.3 Parameter Description 12 - Flow Control Specifies whether the terminal can control the flow of data from the PAD to the terminal. 0 indicates no flow control by the terminal, and 1 indicates that flow control by the terminal may be used.
PAD Services X.3 Parameter Descriptions Table 6-9 NOTE (Continued) 1 Line feed inserted after carriage return in data stream to the terminal. 2 Line feed inserted after carriage return in data stream from the terminal. 4 Line feed inserted after carriage return when echoed to the terminal. The values listed for parameter 13 may be combined by specifying the sum of the values. For example, specifying 3 is the same as specifying 1 and 2. Table 6-10 X.
PAD Services X.3 Parameter Descriptions Table 6-10 (Continued) 18 - Line Display Specifies which character to use for the line display character (when editing is allowed). The range is 0 through 127. 19 - Edit Service Signals Specifies whether and how PAD service signals can be edited. This parameter is valid when the setting of X.3 Parameter 6 is not 0. The possible values are shown below. Table 6-11 Value NOTE Meaning 0 No editing permitted. 1 Editing permitted for printing terminals.
PAD Services X.3 Parameter Descriptions Table 6-13 NOTE (Continued) 1 Do not echo carriage return. 2 Do not echo line feed. 4 Do not echo VT, HT, and FF. 8 Do not echo BEL and BS 16 Do not echo ESC and ENQ. 32 Do not echo ACK, NAK, STX, SOH, EOT, ETB, and ETX. 64 Do not echo characters specified in X.3 Parameters 16, 17, and 18. 128 Do not echo NUL, SO, SI, DLE, DC1, DC4, SYN, CAN, EM, SUB, FS, GS, RS, US, and DEL. The values above may be combined by specifying the sum of the values.
PAD Services X.3 Parameter Descriptions Table 6-15 (Continued) 3 NOTE Parity checking or generation. This parameter is available only for networks using the 1984 or 1988 standards. Table 6-16 X.3 Parameter 22 - Number of Chars Before Page Wait 174 Description Indicates whether an end of page wait should occur and, if so, the number of lines per page. The range is 0 through 255. This parameter is available only for networks using the 1984 standard.
7 Chapter 7 Tracing and Logging Utilities 175
Tracing and Logging Utilities Introduction Introduction This chapter describes the use of the X.25 tracing and logging utilities provided with your X.25 link. These utilities are briefly described in the following table. Refer to Chapter 8, Troubleshooting, if you need help deciding which utility to use. Table 7-1 Available Tracing and Logging Utilities Utility Description Refer to: nettl Creates a user-defined log file containing frame and packet trace information from X.25 packet and LAP-B levels.
Tracing and Logging Utilities Introduction Figure 7-1 The Scope of X.25 Tracing and Logging Utilities OSI Services X.25 User User PAD Written Written Services L3 L4 OTS/9000 Internet Services Network Services (NS) BSD Sockets NetIPC Sockets BSD IPC TCP/UDP X.25 OTS-to-PLP Programmatic Access Translator BSD-to-PLP translator IP-to-PLP Interface strace X.25 Packet Level Protocol (PLP) nettl X.25 Link Access Procedure-Balanced Protocol (LAP-B) X.
Tracing and Logging Utilities nettl nettl Use this command to create an X.25 trace file. The description below is limited to the context of X.25 and assumes that nettl is already operating on your system. For more information and examples for this command, refer to your man pages. NOTE Before you can use the nettl command, your X.25 connection must be operating (launched with the x25init command). Syntax nettl [-traceon kind [kind...]][-entity subsystem [subsystem...
Tracing and Logging Utilities nettl Table 7-2 Tracing Masks keyword a mask hdrin 0x80000000 hdrout 0x40000000 pduin 0x20000000 pduout 0x10000000 a. Use hdrin or hdrout when you only want packet header information displayed. Use pduin or pduout when you want both the packet header AND the data displayed. You can specify masks separately or combine them into a single number.
Tracing and Logging Utilities nettl The device file must be called x25_npx, where n represents the mandatory card instance number (range 0 to 255). The card instance number is the number reported by the ioscan -f command output (in the “I” column). The (lower case) p is a place holder and x represents the port number (1 or 2). p and x are required only for systems with dual-port cards. NOTE -traceoff (-tf) This option turns tracing, specified with the -entity option, off.
Tracing and Logging Utilities netfmt netfmt Use this command to format the trace file that was created with nettl. Refer to the man pages for x25trace for more information and examples on this command Syntax netfmt [-c filter file [-p]] [-F] [-t records] [-N] [-v] [-l] [-1[LT]] [[-f] file_name] Parameters -c filter file Specifies the name of the file containing the filter configuration commands. You create this file with your text editor.
Tracing and Logging Utilities netfmt Use this option to specify the binary file containing the log or trace data. This is the name of the .TRC0 file that was specified when nettl was run the first time with the -traceon and -file options. By default, data is read from standard input. -v Enables “verbose” mode, but also gives the full data output for each packet header (see Examples section below). -N Enables “Nice” formatting of output.
Tracing and Logging Utilities netfmt 0: 00 00 00 01 61 61 61 61 61 61 61 61 61 61 61 61 ...aaaaaaaaaaaa 16: 61 61 61 61 -- -- -- -- -- -- -- -- -- -- -- -- aaaa.......... To format the file /tmp/tracex25.TRC0 in “Nice” mode (output is mainly packet headers) with no filtering: /etc/netfmt -N -f /tmp/tracex25.TRC0 | more The output will be: Tx board: 0 at Wed Sep 28 1994 10:16:19.
Tracing and Logging Utilities netfmt or SX25L3 [type][!] [value][value]... The value field specifies the value for the given type. By default, this value is on (applies as a filter), but can be set to off with the “!” (not) prefix. The value used with SX25L3 can be a list of consecutive values, or a range of values. The permitted values for the types are given in the table below. See the man pages for netfmt for examples.
Tracing and Logging Utilities netfmt The following table lists the packet types displayed for each value combined with family.
Tracing and Logging Utilities netfmt Filter File Examples The following examples illustrate the use of filter configuration commands within the filter file.
Tracing and Logging Utilities strace strace The strace command collects logging event messages from X.25 level 3 and X.25 level 2 STREAMS modules and writes them to standard output. strace runs until terminated by the user. See the man pages for strace(1) for a more detailed description. Running strace with several sets of arguments can impair STREAMS performance. Also, some messages may be lost if too many are logged at one time.
Tracing and Logging Utilities strace x25_1, the sub would be 49 (48 + 1 = 49). See the table below for more examples of the codes to be used for specific interfaces.
Tracing and Logging Utilities strace A simple way to think of dual-port sub codes is as the decimal equivalent of 7030 + n (expressed in hexadecimal), where n is the card instance number. For example, for the device file x25_1p2, the sub in hexadecimal would be 7030 + 1 = 7031 which, when converted to decimal gives you 28721. Some sample calculations of the sub code for dual-port cards are provided in the table below.
Tracing and Logging Utilities strace The value all can be used for any argument in the command line to indicate that there are no restrictions for that argument. Table 7-7 Output Format X.25 level 3 (mod=200) X.25 level 2 (mod=201) IP over X.
Tracing and Logging Utilities strace The following table describes the parameters displayed for the various packet types at level 3.
Tracing and Logging Utilities strace Table 7-9 Table 7-10 (Continued) FRMR Out “Rsn 1” means the control field received was not defined or not implemented. “Rsn 3” means the control field received was invalid. “Rsn 4” means the information field received was too long. “Rsn 8” means the control field received contained an invalid variable. REJ In/Out (level 2) “N(XX)” is an internal variable of no importance or meaning. LINK Bsy (level 2) “Local” means that the RNR has been sent.
Tracing and Logging Utilities strace Examples of strace Output The command: strace 200 48 all gives the following output: 324112 14:59:16 33683766 1 ... 200 48 CALL Out:‘30’ lci 400 gfi 1 324115 14:59:16 33683776 1 ... 200 48 CAA In:‘30’ lci 400 gfi 1 324116 14:59:16 33683776 6 ... 200 48 DATA Out:‘30’ lci 400 ns/nr 0000 324119 14:59:16 33683778 6 ... 200 48 DATA In:‘30’ lci 400 ns/nr 0001 324124 14:59:16 33683781 2 ... 200 48 CLR Out:‘30’ lci 400 C/D 00f2 324127 14:59:16 33683782 2 ...
Tracing and Logging Utilities strace 324203 14:59:59 33688091 2 ... 200 49 CLR In: ‘31’ lci 400 C/D 00f2 324204 14:59:59 33688091 2 ... 200 49 CLC Out: ‘31’ lci 400 The command: strace 201 48 all gives the following output: 324790 15:06:17 33725841 1 ... 201 48 LINK Up : ‘30’ The command: strace 201 49 all gives the following output: 324893 15:07:18 33731984 1 ... 201 49 LINK Dwn: ‘31’ [Remote] NOTE 194 The last example indicates a remote disconnection.
Tracing and Logging Utilities strerr strerr Receives error messages from the STREAMS log driver. The strerr daemon receives error messages from the STREAMS log driver (see the man pages for strlog(7)). By default, additions to the STREAMS error log files (error.dd-mm) are in the STREAMS error log directory (/usr/adm/streams). When first called, strerr creates the log file error.mm-dd. This is a daily log file where mm indicates the month and dd indicates the day of the logged messages.
Tracing and Logging Utilities strerr 196 Chapter 7
8 Chapter 8 Troubleshooting 197
Troubleshooting Troubleshooting Your X.25 Link Troubleshooting Your X.25 Link This section describes troubleshooting procedures for checking your X.25 link up to X.25 level 3. It also provides information on troubleshooting IP over X.25, as well as procedures for diagnosing switching problems. To use these procedures you should be familiar with the following commands: Table 8-1 Troubleshooting Commands Command 198 Purpose Refer to... x25init Initializes X.25 interface and software. Superuser only.
Troubleshooting Troubleshooting Your X.25 Link Table 8-1 Troubleshooting Commands (Continued) strace Logs X.25 event messages. man pages and Chapter 7, Tracing and Logging Utilities, strerr Receives error messages from the Streams log driver.
Troubleshooting Troubleshooting Your X.25 Link Figure 8-1 Flowchart 1 Start Run x25stat X.25 not initialized Level 2 down Statistics dispayed Go to Flowchart 2 Go to Flowchart 3 Go to Flowchart 4 Flowchart 2 – Procedures and Notes Use these procedures to verify that your X.25 link is correctly initialized. Read the following notes before carrying out the initialization check procedures in Flowchart 2.
Troubleshooting Troubleshooting Your X.25 Link If this problem occurs, you can work around it by running the eisa_config utility in interactive mode as shown below. Step 1. At the EISA prompt, type: add !HWP19A0.CGF where is the number of the EISA slot in which the interface card is installed. Step 2. Then type: save quit Step 3. Reboot your system.
Troubleshooting Troubleshooting Your X.25 Link Figure 8-2 Flowchart 2 – Initialization Check Use SMH to configure and enable X.
Troubleshooting Troubleshooting Your X.25 Link Flowchart 3 – Procedures and Notes Use these procedures to verify that your hardware is properly connected and operating correctly. Read the following notes before running the hardware check procedures in Flowchart 3.
Troubleshooting Troubleshooting Your X.25 Link Flowchart 4 – Procedures and Notes This flowchart describes how to run a loopback test using x25check on the local node. This checks that your X.25 link to the network or X.25 switch is working correctly. Note 4-1 – x25check You do a loopback test using the x25server and x25check commands. The x25server process is only used to accept and echo back an X.25 packet coming from an x25check process.
Troubleshooting Troubleshooting Your X.25 Link Figure 8-4 Flowchart 4 – X.25 Configuration Check Start x25server Run x25check to perform loopback test (See Note 4-1) x25check successful? No Check your configuration parameters using information contained in error messages Yes Local configuration OK? Your local X.
Troubleshooting Troubleshooting Your X.25 Link Note 5-1 – ping Use ping on your own IP over X.25 address, for example: ping 195.25.0.13 Do not use aliases (for example, as defined in/etc/hosts), since this may introduce other errors. Use the Break key or Ctrl-C to terminate ping if you have not set the number of packets with the -n option. Note 5-2 – Checking your IP over X.
Troubleshooting Troubleshooting Your X.25 Link • has X.25 initialized, • is compatible with IP and ICMP protocols, • and has an entry for your node in its map table (can map your IP address to your X.121 address). If you still experience problems, ask the remote host System Administrator to check the IP over X.25 configuration on the remote side of the connection. Figure 8-5 Flowchart 5 – IP Over X.25 Check Start Use ping (See Note 5-1) 0% packet loss No Check your IP over X.
Troubleshooting Recovering From a Power Failure Recovering From a Power Failure For Systems With a Backup Power Supply If your site is equipped with a backup power supply, system memory will be preserved in the event of power failure. However, because your X.25 hardware does not have backup capability, any on-board RAM-based memory is lost. Recovery from a power failure is automatic when the /etc/powerfail script is invoked by /etc/inittab.
Troubleshooting Reporting Problems Reporting Problems If you have a service contract with HP, ask your service representative to document the problem as a Service Request (SR). Include the following information where applicable: NOTE Chapter 8 • A detailed description of the problem. Describe the events leading up to the problem and the symptoms of the problem. Include information on HP-UX commands, communication subsystem commands, job streams, result codes, and error messages (the exact wording).
Troubleshooting Reporting Problems • For PAD Problems: — Copies of the x29hosts and x3config files. — A copy of the output from the ls -l /dev/x29 command if you are running x29printd or x29uucpd. — Identify which PAD utility is encountering the error (PAD services, PAD emulation, Remote PAD printer, or UUCP). Include all files relative to that service (for example, .login, profile ID, /usr/spool/lp/*, or /usr/lib/uucp/*). — Include log files for the PAD services.
Troubleshooting Back-to-back Configuration on the Same Host Back-to-back Configuration on the Same Host Systems with multiple X.25 interfaces can use back-to-back configurations to perform diagnostics. If you suspect that a switch might be the source of your connection problem, you can set up a back-to-back configuration to test the circuit without the PAD switch.
Troubleshooting Configuration and Troubleshooting Commands Configuration and Troubleshooting Commands This section provides a brief summary of X.25 commands and indicates where further information can be found. Examples of x25init and the syntax for IP over X.25 mapping are provided at the end of the section. Command Summary NOTE You can use the x25message utility to get an explanation of an error message.
Troubleshooting Configuration and Troubleshooting Commands Utility with programmatic interface that allows users to get additional X.25 statistics. x25ping Checks if a remote host can be reached via the X.25 interface. See your man pages. ping Tests connectivity to a remote host up to the Internet Protocol (IP) level (level 3). See your man pages. route Used to add a host or network to the network routing table. See your man pages.
Troubleshooting Configuration and Troubleshooting Commands strace Collects and writes X.25 logging event message. See your man pages and the examples in Chapter 7, “Tracing and Logging Utilities.” strerr Receives error messages from the STREAMS log driver. See your man pages and the examples in Chapter 7, “Tracing and Logging Utilities.” ifconfig Configures network interface parameters. See your man pages.
Troubleshooting Configuration and Troubleshooting Commands reach a host with a particular IP address. Reverse mapping reverses the order of translation. The default file name and directory for the mapping table is /etc/x25/ip_to_x121_map. When the packet is outbound, the IP address is mapped to the X.121 address that is associated with it in the IP map file. When the packet is inbound, the X.121 address is mapped to the IP address of the same destination host. This is called “reverse mapping.
Troubleshooting Configuration and Troubleshooting Commands NOTE If you do not include the packet_size and window_size values, and the x25_card_device is the last field, the default values will be applied to the packet_size and window_size fields. Example 15.128.174.04 12345 -URC -ARC 30.0.0.2 34567 -URC -ARC device=x25_0,256,7 In this example, a card has been configured with a device equal to x25_0, a packet size of 256, and a window size of 7.
Troubleshooting Configuration and Troubleshooting Commands Because pvc describes a permanent circuit for a particular interface, that interface must have been initialized prior to the initialization of the address map table. If the interface or the specified PVC does not exist, an error is reported. prog_access _name Specifies the card's programmatic access name. For Series 712 workstations this is always name=interface0.
Troubleshooting Configuration and Troubleshooting Commands NOTE 218 For non-DDN configured interfaces, all remote hosts must have entries in the IP-to-X.121 address map table. Remote hosts not on your X.25 network (that is, on the other side of gateways) do not need to have map table entries. For more information, refer to the routing description in this section.
A Appendix A Using Non-English Subscription Forms 219
Using Non-English Subscription Forms Subscription Form Translations Subscription Form Translations This appendix lists the English (SMH dialog field) equivalents for terms that appear on your French, Italian, German or Spanish subscription form. Use this information to locate the English SMH dialog field equivalents of these terms. Terms are listed in order of appearance. Online help (using the Help button) is available for each field.
Using Non-English Subscription Forms Subscription Form Translations Table A-1 Table A-2 French TRANSPAC Subscription Form (Continued) k - Level 2 Window Size (frames) Fenêtre T1 - Retransmission Timer (ms) Temporisateur Using Your ITAPAC (Italian) Subscription Form English on SMH dialogs Appendix A Italian on subscription form X.25 Address Indirizzo X.
Using Non-English Subscription Forms Subscription Form Translations Table A-2 Table A-3 Using Your ITAPAC (Italian) Subscription Form (Continued) Switched VC Default - Inbound & Outbound (Modify Throughput Class Setting) Classe di throughput di default in entrata & in uscita Switched VC Negotiated (Modify Throughput Class Setting) Classe di throughput negocia k - Level 2 Window Size (frames) k - Dimensione di finestra a livello 2 T1 - Retransmission Timer (ms) T1 - Timer di ritramissione (ms).
Using Non-English Subscription Forms Subscription Form Translations Table A-4 Appendix A Using your IBERPAC (Spanish) Subscription Form (Continued) Permanent - Quantity Canales Lógicos Permanentes cantidad Switched (inbound) - Quantity Canales Lógicos Unidireccionales Entrante - cantidads Switched (two-way) - Quantity Canales Lógicos Bidireccionales cantidad Switched (outbound) - Quantity Canales Lógicos Unidireccionales Salientes - cantidad Fast Accept Selected Selección Rápida Flow Control Neg
Using Non-English Subscription Forms Subscription Form Translations 224 Appendix A
B Appendix B X.
X.25 Configuration Files and Examples X.25 Configuration Files X.25 Configuration Files This section lists X.25 configuration and addressing files. Table B-1 Table B-2 226 /etc/x25 directory x25config_0 ASCII file containing X.25 parameters. This file can be used by the x25init command when initializing the card. It is created automatically if you configure X.25 using SMH. To configure X.25 manually, copy and edit either x25init_def or x25init_smpl. x25init_def Contains default X.
X.25 Configuration Files and Examples X.25 Configuration Files Table B-2 /etc directory (Continued) networks Table B-3 /var/x25/log/x25server directory x25server.log Table B-4 Appendix B Log file of output from x25server process. /var/x25/log directory x25init.log Table B-5 Contains information regarding known networks. Log file of output from x25init command. Home directory .rhosts (optional) Security file which authorizes remote hosts and users on local host. See the man page for hosts.equiv.
X.25 Configuration Files and Examples Example Files Example Files This section provides example file listings for of the x25init_def, x_25init_smpl, x3config, x29hosts, and x25_networks files. The x25init_def File Table B-6 # # Likely runstring: x25init -c x25init_def # This sample X.25 configuration contains default values # Mandatory parameter - X.121 address # X.121 4085551202 # Typically the address on the packet is identical to X.
X.25 Configuration Files and Examples Example Files Table B-6 (Continued) # Level 3 Parameters # # # # Mandatory Parameters - virtual circuit parameters logical channel id, start num [1-4095], type, how many At least one lci type (PVC, incoming, two-way or outgoing SVC) needs to be configured.
X.25 Configuration Files and Examples Example Files Table B-6 (Continued) # neg_inthruputclass 19200 # neg_outthruputclass 19200 pvc_inpacketsize 128 pvc_outpacketsize 128 pvc_inwindow 2 pvc_outwindow 2 # # # # offered thruput class if using thruput class negotiation offered thruput class if using thruput class negotiation # # # # packetsize for PVCs packetsize for PVCs window size for PVCs window size for PVCs # These set of parameters are specified only if you wish to run IP over X.25.
X.25 Configuration Files and Examples Example Files The x25init_smpl File Table B-7 # # Likely runstring: x25init -c x25init_smpl X.121 4085551202 X.121_packet ’’ name interface0 device x25_0p1 # # # # # X.121 address use a null (i.e.
X.
X.
X.
X.
X.
X.25 Configuration Files and Examples Example Files Table B-8 (Continued) } # for x29server pad_spt { remote_x121 x3 logging reverse_charge 408555120801 hp_padsrvr 1 disable } The Network Type File (x25_networks) The network type file describes standard network types. If the network to which you are subscribing does not meet any of the network descriptions specified in this file, use one of the generic entries (DTE_80, DTE_84 or DTE_88). The network type file is read-only.
X.25 Configuration Files and Examples Example Files The delivered X.
C Appendix C Diagnostic Messages 239
Diagnostic Messages Introduction Introduction This appendix describes the diagnostic codes and messages which are a subset of the list defined by the International Standards Organization (ISO) in IS-8202:1987(E). Only those diagnostics supported on X.25 for HP 9000 systems are listed. Each message is listed in numerical order by its diagnostic code and includes an ISO description and explanation. Refer to Appendix D of the X.
Diagnostic Messages Diagnostic Message Example Diagnostic Message Example An example diagnostic message generated by the network from a CLEAR REQUEST packet is shown below: Clear request LCGN: 0 LCN : 32 Clearing Cause [0] : DTE originated. Diagnostic [241] : In the example above, LCGN is the Logical Channel Group Number and LCN is the Logical Channel Number (the number denoting the logical association between a DTE and DTE connected by a VC).
Diagnostic Messages Cause Code Settings Cause Code Settings X.25 automatically resets (silently forces) the network-generated cause code of CLEAR or RESET REQUEST packets to comply with the applicable CCITT X.25 Recommendation. • 1980 – The cause is silently forced to zero. • 1984 – The cause is left at zero or OR'ed with 128 if it is not zero. • 1988 – The cause is left at zero or OR'ed with 128 if it is not zero. X.
Diagnostic Messages Packet Codes Packet Codes RESTART Packet Codes When the system receives a RESTART INDICATION packet, the received CLEAR INDICATION or RESET INDICATION packet contains a cause code of 0 and the diagnostic code used in the RESTART. RESET/CLEAR Packet Codes The system may generate a RESET/CLEAR because of an error, lack of memory, or other condition. When this occurs, a RESET/CLEAR INDICATION is delivered to the application and a RESET/CLEAR REQUEST packet is sent to the network.
Diagnostic Messages X.25 Diagnostic Messages X.25 Diagnostic Messages Table C-1 No Additional Information ISO Description Diagnostic Explanation 1 (RESET) Invalid P(S). DATA packet received from network with P(S) invalid or outside of allowable window. 2 (RESET) Invalid P(R). DATA packet received from network with P(R) invalid. Table C-2 Packet Type Invalid Diagnostic 17 (RESTART, CLEAR, RESET) ISO Description Explanation Packet type invalid for state R1.
Diagnostic Messages X.25 Diagnostic Messages Table C-2 Packet Type Invalid (Continued) 25 (CLEAR) Packet type invalid for state P6. Invalid packet received on VC in state P6 (DTE Clear Request). 27 (RESET) Packet type invalid for state D1. Invalid packet received on VC in state D1 (Flow Control Ready). 29 (RESET) Packet type invalid for state D3 Invalid packet received on VC in state D3 (DCE Reset Indication).
Diagnostic Messages X.25 Diagnostic Messages Table C-3 Packet Not Allowed (Continued) 39 (RESTART, CLEAR, RESET) Packet too long. Received packet exceeds maximum length. The packet may be larger than allowed by the configuration and negotiations (i.e., fast select), or contain a field (i.e., call/clear user data) that is larger than the allowed size. 41 (RESTART, CLEAR, RESET) RESTART or REGISTRATION packet with non-zero LCI.
Diagnostic Messages X.25 Diagnostic Messages Table C-4 Timer Expired (Continued) 50 (CLEAR) Timer expired for CLEAR INDICATION (or DTE timer expired or retransmission count surpassed for CLEAR REQUEST). CLEAR CONFIRM not received within T23 time limit (set at approximately 180 seconds) after transmission of CLEAR REQUEST. After a certain number of CLEAR retries, system places logical channel in state P1 (Ready).
Diagnostic Messages X.25 Diagnostic Messages Table C-5 65 (CLEAR) Call Setup, Call Clearing, or Registration Problem (Continued) Facility/ registration code not allowed. Packet size negotiation, Window Size Negotiation or Throughput Class Negotiation facility codes found in the facility field of the call setup packet when corresponding negotiation had not been configured. In CALL REQUEST, condition results in error returned to user instead of generation of CLEAR.
Diagnostic Messages X.25 Diagnostic Messages Table C-5 66 (CLEAR) Call Setup, Call Clearing, or Registration Problem (Continued) Facility parameter not allowed. Parameter field of a packet size negotiation, window size negotiation or throughput class negotiation facility in a call setup packet has been found to be invalid because it contains values not allowed by the configured level (1980 or 1984).
Diagnostic Messages X.25 Diagnostic Messages Table C-5 69 (CLEAR) Call Setup, Call Clearing, or Registration Problem (Continued) Invalid facility/ registration length. Length of the facility field is greater than the maximum allowed by the configured revision level of CCITT X.25 Recommendation (63 for 1980, 109 for 1984). The condition will result in an error returned to the user instead of generation of CLEAR if it is detected in CALL REQUEST.
Diagnostic Messages X.25 Diagnostic Messages Table C-5 Call Setup, Call Clearing, or Registration Problem (Continued) 73 (CLEAR) Duplicate facility requested. Same facility code appeared twice in the facility field. Error is returned to caller if condition was detected in CALL REQUEST. CLEAR was not generated. 76 (CLEAR) Facility not provided when expected. When system was configured to handle IP over X.
Diagnostic Messages X.25 Diagnostic Messages Table C-8 160 (CLEAR, RESET) DTE-Specific Signals (Continued) DTE-specific signal (generic). CALL INDICATION with reverse charge requested has been received, and reverse charge is configured to be rejected by system. CALL INDICATION with reverse charge requested has been received by IP and reverse charge is configured to be rejected for that IP/X.121 address pair. Check is done via IP to X.121 address map table.
Diagnostic Messages X.25 Diagnostic Messages Table C-8 DTE-Specific Signals (Continued) 164 (CLEAR) Fast select not subscribed. CALL INDICATION requiring fast select facility has been received and fast select is not configured. Results in error when detected on CALL REQUEST. 225 (CLEAR) Disconnection (transient condition). X.25 subsystem is down when X.25/9000 to IP subsystem is servicing CALL CONFIRMATION or incoming DATA.
Diagnostic Messages X.25 Diagnostic Messages Table C-9 231 (CLEAR) Connection rejection. NSAP unreachable (transient condition). No listen socket capable of servicing CALL INDICATION. X.25 subsystem is down when X.25-to-IP subsystem is servicing CALL INDICATION. 232 (CLEAR) Connection rejection. NSAP unreachable (permanent condition). CALL INDICATION with first byte of call user data other than CC (hex) received on system which does not have X.25/9000 programmatic access configured in kernel.
Diagnostic Messages X.25 Diagnostic Messages Table C-10 Higher Level Initiated (Continued) 241 (CLEAR) Disconnection normal. Application closed or shut down socket and did not specify cause/diagnostic combination to be used on socket. This is the default. If available, application-specified cause/diagnostic combination is used. This is not an error condition. 242 (CLEAR) Disconnection abnormal. Application using a socket supporting virtual connection crashed.
Diagnostic Messages X.25 Diagnostic Messages Table C-10 250 (RESET) 256 Higher Level Initiated (Continued) Reset. User resynchronizatio n. PVC is claimed by programmatic access socket. RESET is sent as part of socket initialization procedure. Code is used if the application did not specify which cause/diagnostic combination to use. Application requires RESET to be sent. No cause/diagnostic combination is specified on socket.
Index Symbols .netrc file, 227 .rhosts file, 227 A accept reverse charge IP to X.121 mapping file, 217 add PAD-UUCP services, 74 add remote PAD support, 72 addresses IP to X.121 mapping, 214 summary of files, 225 B battery backup, 208 Break key, 114 C cause code, 242 CCITT X.25 Recommendations, 237 closed user group IP to X.
Index x25_networks, 226, 237 x25init.log, 227 x25init_def, 226, 228 x25init_smpl, 226, 231 x25server.log, 227 Filter file, 183 G gateway, 215 H hardware requirements, 24 High Availability feature, 24 hosts file, 226 hosts.equiv file, 226 I ifconfig see man pages installing multiple X.25 cards, 24 interface card displaying configuration, 118 displaying statistics, 118 displaying status, 118 initialization, 208 name, 114 troubleshooting, 199 interrupt signal, 114 IP, 18 IP address mapped to X.
Index netstat see man pages netstat command, 213 nettl see man pages nettl command, 178 network carrier type, 33 network type, 237 network type file, 237 networks types of, 237 networks file, 227 O online help (SAM) , 31 P packet codes RESET/CLEAR, 243 RESTART, 243 PAD, 157 call acceptance, 133 CCITT, 130 command sets, 160 configuring remote printers, 141 configuring remote support, 135 configuring uucp support, 148 extended command set, 161 launching applications automatically, 138 padem, 156 remote PAD su
Index statistics VCs, 118 status of interface card, 118 strace see man pages strace command, 187 examples, 192 options, 187 output format, 190 syntax, 187 strerr see man pages strerr command, 195 description, 195 options, 195 syntax, 195 subnet masks defaults, 38 support See service representative Switched VC Flow Control field descriptions, 42 T TCP/UDP, 18 throughput classes and line speeds, 44 tracing utilities, 175 troubleshooting, 198 hardware check, 203 ping command, 206 X.
Index x25init_def file, 226, 228 x25init_smpl file, 226, 231 x25mibstat, 128 see man pages x25ping see man pages x25printd, 139 x25server, 132 see man pages x25server command, 115 description, 115 troubleshooting, 204 x25server.
