Troubleshooting Terminal, Printer, and Serial Device Connections HP 3000 MPE/iX Computer Systems Edition 5 Manufacturing Part Number : 32022-90058 E0604 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. General Information Datacommunications and Terminal Subsystem (DTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datacommunications and Terminal Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Powerfail Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DU[MP] DT[C] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DU[MP] LD[EV] . . . . . . . . . . . . . . .
Contents T[RACE] TI[O] TRACES[HOW] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T[RACE] X2[5] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T[RACE] X2[5] TRACEON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T[RACE] X2[5] TRACEOF[F] . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6
Tables Table 3-1. Security Levels for TermDSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 8
Figures Figure 1-1. Datacommunications and Terminal Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-2. ThinLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-3. 10/100 Base-T Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 10
Preface This manual documents functionality for the MPE/iX release for HP 3000 Series 900. This manual is designed to aid the troubleshooting of device connections. Information and strategies for troubleshooting networking environments is provided. TermDSM is a utility program used to troubleshoot: • Terminal connections. • Printer connections. • Other serial device connections. This manual only covers troubleshooting connections for host-based management (i.e.
Skills Troubleshooting Terminal, Printer, and Serial Device Connections will be of greatest value to the person responsible for the overall operation and reliability of an MPE/iX computer. This person is usually called the system administrator or system manager, and needs to be able to prepare devices for operation and to configure the computer to recognize asynchronous devices.
Guide To This Manual Troubleshooting Terminal, Printer, and Serial Device Connections is divided into the following chapters and appendixes: • Chapter 1, “General Information,” presents an overview of the troubleshooting environment. • Chapter 2, “Troubleshooting Procedures,” gives information and suggests troubleshooting strategies. • Chapter 3, “Introduction to TermDSM,” introduces the TermDSM utility program and lists the steps to start it.
Helpful Manuals The following manuals should be available for reference when using this manual: 14 • Configuring Systems for Terminals, Printers, and Other Serial Devices (32022-61000) • Asynchronous Serial Communications Programmer’s Reference Manual (32022-61001) • DTC Planning Guide (D2355-95017) • DTC Technical Reference (5961-9820)
1 General Information This manual addresses troubleshooting from a host (and host-based management) perspective. For troubleshooting information related to PC-based management, see the Using HP OpenView DTC Manager manual as well as other manuals referenced earlier in this book. This chapter provides a description of the hardware and software components of the Datacommunications and Terminal Subsystem (DTS).
General Information Datacommunications and Terminal Subsystem (DTS) Datacommunications and Terminal Subsystem (DTS) With the exception of the system console which has its own access port, all asynchronous serial devices can be connected to HP 3000 Series 900 computers through the Datacommunications and Terminal Subsystem (DTS).
General Information Datacommunications and Terminal Subsystem (DTS) access to X.25 networks, and can be used to connect asynchronous devices through PAD connections. Alternatively, a single Telnet Access Card per DTC can be used to access MPE/iX systems from ARPA systems. Each DTC 48 provides six slots, each of which can contain one of the following connector cards: • Eight 3-pin RS-232-C local connections. • Eight 5-pin RS-422 local connections. • Six 25-pin RS-232-C modem connections. • DTC/X.
General Information Datacommunications and Terminal Subsystem (DTS) LAN Interface Card (LANIC) Every computer in the HP 3000 Series 900 family has a LAN Interface Card (LANIC) as part of its hardware. This card is located in the System Processing Unit (SPU) and enables the system to communicate with asynchronous devices via the LAN by providing the basic connection between the computer and the LAN.
General Information Datacommunications and Terminal Subsystem (DTS) ThinLAN Connection LAN cable is available in two versions. The first, ThinLAN (Type 10 BASE 2), is available in connection lengths of up to 185 meters (555 feet), and provides an economical solution where DTCs are located in close proximity to their computer system. ThinLAN is a flexible cable which is easy to install, and can be bent around objects to accommodate its use in confined areas.
General Information Datacommunications and Terminal Subsystem (DTS) 10Base-T and 100 Base-T Figure 1-3 shows the star topology of the 10/100 Base-T network and offers another way to lay out your Ethernet network. 10/100 Base-T offers maximum connection lengths of up to 200 meters of unshielded twisted pair per segment and supports up to 12 workstations per HUB. You can connect multiple HUBs to the LAN with an Ethernet performance of 10 Mbps. The DTCs only support a connection at the 10 Base-T speed.
General Information Powerfail Recovery Powerfail Recovery DTC powerfail recovery works for direct-connect nailed sessions using character mode. The system also attempts to recover direct-connect sessions using block mode; however, this might not be successful if the powerfail has affected terminal configuration. This is especially true for VPLUS applications. In the event of a DTC powerfail, some data loss might occur. Data buffered in the DTC at the time of the powerfail is not recoverable.
General Information Troubleshooting Responsibilities Troubleshooting Responsibilities Many problems encountered with terminals and serial printers can be solved by the end user. Even more can be solved by a system manager. If the system manager cannot solve a problem, they should contact an HP support representative. Each of the above groups has a specific role to play in the troubleshooting process. Each person needs to fulfill this role for troubleshooting to be completed quickly.
General Information Troubleshooting Responsibilities Not all of the above steps are necessary each time. For instance, if many devices go down at once, it is likely that the problem lies in the DTC or the LAN, instead of each individual device. It is important to note that intermittent problems can become more frequent. This is especially true if a piece of hardware is beginning to fail.
General Information Troubleshooting Responsibilities 24 Chapter 1
2 Troubleshooting Procedures Recall that, in this manual, “serial device” refers to any of the following DTC connected devices: • Terminals. • Serial printers. • PCs (in terminal emulation mode). • Plotters. Serial device problems can be caused by the system, by application software, by faults within the device or DTC connections, or by the LAN hardware. Procedures for troubleshooting all possible faults are beyond the scope of this manual.
Troubleshooting Procedures Troubleshooting Pathway Troubleshooting Pathway A practiced method for problem resolution is to first identify the problem and then identify alternative causes of that problem. Break the big problem into smaller, more manageable components. By breaking the problem into manageable and testable components, the cause can be easily isolated. A recommended troubleshooting pathway is shown in Figur e2-1.
Troubleshooting Procedures Troubleshooting Pathway 2. Testing DTC-Device Connections. If necessary, use TermDSM for more detailed diagnostics. This must be done at another device or the console. Test DTC-device connections first. This can detect faults within the device, the device cable, and parts of the DTC circuitry. If DTC-device connections are not causing the problem, further DTC diagnostics are suggested. 3. Testing the DTC. Using TermDSM, perform a DTC selftest.
Troubleshooting Procedures Troubleshooting the Device Troubleshooting the Device Most problems can be diagnosed and/or resolved quickly at the device (terminal or serial printer). It’s best to do simple verifications before using TermDSM for more involved diagnostics. First, note the following: • How many devices are affected? • Which devices are affected? The number and proximity of devices affected provides a clue to the cause. If all devices are affected, the fault is likely to be with the system.
Troubleshooting Procedures Testing DTC Device Connections Testing DTC Device Connections This section applies if only one device is affected and simple causes have been ruled out. In this case, it is appropriate to use TermDSM for more detailed diagnostics. This must be done from another terminal or the console. TermDSM is part of the Online Diagnostic Subsystem. The diagnostics in this section require security level 2 (SM, DI, or OP capability).
Troubleshooting Procedures Testing DTC Device Connections • If the test fails, the fault is in the DTC (refer to “Testing the DTC” later in this chapter). • If the test passes, do the Terminal Write/Read Test. 2. Terminal Write/Read Test. • If the test fails, and a loopback connector is available, do the External Port Loopback Test. • If the test fails, but no loopback connector is available, alternate testing is required (fault might be in the DTC, the device, or the device cable).
Troubleshooting Procedures Testing the DTC Testing the DTC If the DTC is suspected as the cause, TermDSM can be used to determine the hardware or software component involved. It also provides DTC dump and reset functions. CAUTION TermDSM functions described in this section cause all sessions on the DTC to abort. Data for each session can be lost. Verify that users are logged off before attempting these tests. Security level 1 (SM or DI capability) is required for the following functions.
Troubleshooting Procedures Testing the LAN Testing the LAN If system, device, and DTC faults are ruled out as the cause of the problem, LAN hardware is suspect. LAN hardware troubleshooting is beyond the scope of this manual. Contact your HP support representative.
3 Introduction to TermDSM TermDSM (Terminal Online Diagnostic/Support Monitor) is a utility program for host-based management that provides various diagnostic services for terminal and serial printer connections on systems of the HP 3000 Series 900 computer family. It is patterned after the MPE V utility of the same name. Typically, TermDSM is used when a problem is suspected with one or more terminals, printers, or other serial devices; the problem can be related to hardware or software.
Introduction to TermDSM TermDSM Requirements TermDSM Requirements The following hardware is required when using TermDSM: • The minimal mainframe configuration of a HP 3000 Series 900 computer. • The system and each DTC connected and configured as nodes on the LAN. • At least one pair of serial interface/connector cards installed in each DTC, with at least one port of each connector card connected to an asynchronous device.
Introduction to TermDSM TermDSM Requirements If more than one user is running TermDSM, it is not advisable for one user of TermDSM to reset another user of TermDSM. (The user’s port, ldev, SIC, or DTC should not be reset.
Introduction to TermDSM TermDSM Functionality TermDSM Functionality TermDSM is a command-based utility program which allows you to monitor and troubleshoot the DTS. It is set up so that you can monitor the condition of a single device or an entire DTC. TermDSM provides several specific functions. Some commands provide only information, such as a listing of all the DTCs associated with the system or the internal configuration information of any DTC.
Introduction to TermDSM TermDSM Command Summary TermDSM Command Summary This section lists the first level commands and basic functionality of all the available TermDSM operations. These commands are used to view, control and diagnose various operations of the DTS Subsystem. Chapter 3 • C[onnect] Access the Show Connections function to display all the TIO and PAD connections established through selected cards in the DTCs. The security level of this command is 2..
Introduction to TermDSM TermDSM Command Summary Further explanation for each command is contained in Chapter 4, “TermDSM Commands.
Introduction to TermDSM Starting TermDSM Starting TermDSM To use TermDSM, enter the SYSDIAG command at the MPE/iX prompt (:). The Diagnostic User Interface prompt appears: DUI> From this prompt, many diagnostics can be run. Type HELP to see a list.
Introduction to TermDSM Stopping TermDSM Stopping TermDSM To stop using TermDSM, enter the EXIT command at the TermDSM main prompt. The DUI prompt is displayed. Enter EXIT again to return to the MPE/iX prompt.
4 TermDSM Commands This chapter provides complete descriptions of the TermDSM commands. Commands are listed in alphabetical order for your convenience. Each command description uses the same format: 1. Command Name. 2. Purpose of Command. 3. Security Level. 4. Syntax of the command’s functions. 5. Parameter descriptions (if the command has parameters). 6. Description. This provides an explanation of the command's functions and details not listed in the individual parameter descriptions. 7.
TermDSM Commands CONNECTION CONNECTION This command accesses the subsection that displays information about the connections currently active on a specified DTC board. Security level: 2. Syntax C[onnection] Description After the Connect command is entered, the following prompt is displayed on the terminal: (show connection) SHow #,# (carriage return to exit) ? If you press [Return] instead of the subcommand, you will be returned to the major prompt and can then enter another TermDSM command.
TermDSM Commands CONNECTION • Information on the connection. For example, the virtual circuit number or the AFCP connection number. After the header in addition to the card and port number of the source DTC, the command displays the following information for the three type of connections possible through the Asynchronous Serial Card .
TermDSM Commands CONNECTION --------------------------------------------------------------------------- This is an example of the information displayed for connections from a DTC port to another DTC Host port. 1 Board# 4 WAR3.ITG.HP 1, Port# 16, TCP CNX#12567, Port Name HOSTPORT --------------------------------------------------------------------------1 Board# 5 WAR3.ITG.
TermDSM Commands DI[AG] DI[AG] Determines if the DTC hardware or the connections from a DTC to its devices are functioning properly. Security level: 1 for DTC selftest; 2 for remaining diagnostic functions.
TermDSM Commands DI[AG] Parameters dtcnum The number TermDSM associates with a particular DTC. The DTC command lists each DTC with its assigned number. This list is also printed when you make a mistake while typing in a DTC number. cardnum Number of the interface card within the DTC to which the device is connected. The cards are numbered from zero beginning at the bottom of the DTC. portnum Number of the port on the interface card.
TermDSM Commands DI[AG] Parameters dtcnum The number TermDSM associates with a particular DTC. The DTC command lists each DTC with its assigned number. This list is also printed when you make a mistake while typing in a DTC number. cardnum Number of the interface card within the DTC to which the device is connected. The cards are numbered from zero beginning at the bottom of the DTC. portnum Number of the port on the interface card.
TermDSM Commands DI[AG] Parameters CAUTION dtcnum The number TermDSM associates with a particular DTC. The DTC command lists each DTC with its assigned number. This list is also printed when you make a mistake while typing in a DTC number. cardnum Number of the interface card within the DTC to which the device is connected. The cards are numbered from zero beginning at the bottom of the DTC. portnum Number of the port on the interface card.
TermDSM Commands DI[AG] DI[AG] SE[LFTEST] Determines if the hardware of a particular DTC is functioning properly. Security level: 1. Syntax SE[LFTEST] dtcnum Parameter dtcnum CAUTION The number TermDSM associates with a particular DTC. The DTC command lists each DTC with its assigned number. This list is also printed when you make a mistake while typing in a DTC number. This subcommand aborts all sessions on the DTC under test. Data for those sessions may be lost.
TermDSM Commands DI[AG] As each selftest completes, the results of each SIC selftest will be printed on the terminal. Below is a selftest print out for a DTC 48: Card SIC/SNP type Card test status Ports (G:good or x:bad) 5 (not installed) 4 (not installed) 3 X25 RS-232 Direct OK GG 2 TIO RS-232 Direct OK GGGG GGGG 1 TIO RS-232 Direct OK GGGG GGGG 0 TIO RS-232 Modem OK GGGG GG The test passed 1 times and failed 0 times.
TermDSM Commands DI[AG] seven write/read operations will not be run. If you answered no, all 10 write/read operations will be executed regardless of the results of each test. The following is then printed on the terminal: Please connect and make ready (power on, remote mode, etc.) a supported terminal, before answering the “How many times?” question.
TermDSM Commands DI[AG] cardnum Number of the interface card within the DTC to which the device is connected. The cards are numbered from zero beginning at the bottom of the DTC. (Note that SNP cards may not be mounted in slot 0 or 1 for DTC 16, and slot 0 for DTC 48.) Description Determines if the SNP hardware is functioning properly. This internal loopback test is executed only if X.25 is not started on this SNP (X25 Level 1, 2, and 3). No external connections are required.
TermDSM Commands DI[AG] Description Determines if the SNP hardware is functioning properly. This internal loopback test is executed only if the SNP is not started (X25 Level 1, 2, and 3). External connections are required only for the V.35, the V.36, and the RS-422 interface. All loopback tests are disruptive in the sense they will abort any existing VC connections on that SNP. Other SNPs in the DTC will not be effected.
TermDSM Commands DI[AG] Description Determines if the network is functioning properly by testing the connection between an SNP and the network. The test tries to send and receive data from the network. To do this, a VC is opened with a destination address on the local side. The correct X.25 address must be configured in the Level 3 Configuration screen in NMMGR. Additionally, this address must be entered as the last parameter of the SNP network loopback command. This test is executed only if X.
TermDSM Commands DT[C] DT[C] Lists each DTC assigned to the system and displays the number that TermDSM has assigned to each DTC. Security level: 2.
TermDSM Commands DU[MP] DU[MP] Captures data pertaining to a particular port, asynchronous processor board (mux card of a DTC 72MX), DTC, or logical device number and writes it to a disk file. Security level: 1 for DTC dump; 2 for remaining dump functions.
TermDSM Commands DU[MP] The file will also contain: • The day and time of the dump. • The type of dump (logical device number or port). • Headings before each of the major areas of dump information. If a dump file for an ldev number or port is to be printed, a printer file equation with the CCTL option should be used. In the following example, TRM123AB is the name of the dump file: :FILE LIST;DEV=LP;CCTL :PRINT TRM123AB.PUB.
TermDSM Commands DU[MP] Shhhhhhc.PUB.SYS TRMdddll.PUB.SYS where hhhhhh is the last six hexadecimal digits of the DTC’s LAN address and c is a character in the range from A to Z. The ddd is the Julian day of the year and ll is a two-character string in the range: AA, AB, AC, ..., BA, BB, BC, ..., ZZ This numbering system allows you to create many dump files in one day and to later know on what day each dump was created by simply looking at the file name.
TermDSM Commands DU[MP] DU[MP] M[UX] Captures data pertaining to a particular asynchronous processor board (mux card) of a DTC 72MX to a disk file. This command is supported for DTC 72MX only. Security level: 2. Syntax M[UX] dtcnum, boardnum Parameters dtcnum Number of the DTC to which the board is installed. This is the number TermDSM associates with this DTC. boardnum Number of the asynchronous processor board (mux card) within the DTC 72MX.
TermDSM Commands DU[MP] portnum Number of the port on the interface card. As you face the back of the DTC, the ports are numbered from zero beginning at the left of the board. Description Information associated with the port is dumped to a disk file. If the port is also associated with an ldev number, information pertaining to the ldev number is dumped.
TermDSM Commands DU[MP] Please deliver the following SNP dump to your HP representative. Cbxxxxxa.PUB.SYS where b is the board number in that DTC, xxxxx is the last 5 characters of the IEEE 802.3 address of that DTC and a is a character in the sequence a, b, ...,z to allow multiple dumps. DU[MP] V[C] Captures data pertaining to a particular VC on an X.25 card and writes it to a disk file. (If the VC you are attempting to dump is a PAD VC, you must use the Ldev option instead.) Security level: 2.
TermDSM Commands EE[PROM] DT[C] EE[PROM] DT[C] Downloads the new ROM code on the DTC 72MX and DTC 16iX/16MX. This feature is not supported on the DTC 48 and the DTC 16. Security level: 1. Syntax DT[C] dtcnum Parameter dtcnum The number TermDSM associated with a particular DTC. The DTC command lists each DTC with its assigned number. This list is also printed when you make a mistake while typing in a DTC number. CAUTION This subcommand aborts all sessions on the DTC under test.
TermDSM Commands EX[IT] EX[IT] Exits the TermDSM program and returns you to the DUI prompt.Security level: 2.
TermDSM Commands H[ELP] H[ELP] Lists information regarding TermDSM and its commands. Security level: 2.
TermDSM Commands MULTI MULTI This command accesses the subcommands that allow you to start or stop the X.25 or PAD protocols on multiple DTCs and multiple X.25 cards. Security level: 1. Syntax M[ulti] Description After the MULTI command is entered, the following prompt is printed on the terminal: (multiple operations) Current operation STARt #,# STOp #,# Dtc # NONE. Selected Modules X.25 [ ] PAD [ ] (X.25,PAD) (X.
TermDSM Commands MULTI Current operation STARt #,# STOp #,# Dtc # START. Selected Modules X.25 [X] PAD [X] (X.25,PAD) (X.25,PAD) List of DTCs (carriage return to exit) ?dt 1,2 DTC After the operation and protocols are selected this command is used to initiate the operation on a set of selected DTCs. Syntax D[tc] dtcnums Parameters The DTC number TermDSM associates with a particular DTC. The DTC command lists each DTC with its assigned DTC number.
TermDSM Commands R[ESET] R[ESET] To clear hardware and software associated with a logical device number, physical port, serial interface card, or DTC so that a new session or job can be started on each port. Security level: 1 for DTC; 2 for remaining functions. Syntax R[ESET] Description After the RESET command is entered, the following prompt is printed on the terminal: (reset) Ldev # POrt #,#,# SNp # ,#(X.
TermDSM Commands R[ESET] You may also reset multiple DTCs with one RESET DTC command. The first command below resets DTC 3, 5, and 9. The second command resets DTCs 4 through 15, inclusive. These two commands are typed at the RESET subcommand prompt. DTC 3, 5, 9 DTC 4/15 Description After entering the DTC subcommand, the following is printed on the terminal: Warning: This will reset all users on that DTC.
TermDSM Commands R[ESET] Description This subcommand also resets the port associated with this ldev number. Also, any session or job running on the device is aborted. When it is complete, the reset prompt will be displayed and you can then enter another RESET subcommand. R[ESET] PO[RT] Clears the software associated with a particular port so that the associated device can be used again.Security level: 2.
TermDSM Commands R[ESET] Description When the subcommand is entered, all ports of the card are reset. When the reset completes, the status of each port of the card will be displayed. The reset prompt will then be displayed and you can enter another RESET subcommand. This subcommand should also be used when resets of a particular port on an SIC have been unsuccessful. If the reset of the card is also unsuccessful, consider using the DTC subcommand to reset the entire DTC.
TermDSM Commands R[ESET] cardnum Number of the X.25 card within the DTC. The cards are numbered from zero beginning at the bottom of the DTC. (Note that SNP cards may not be mounted in slot 0 or 1 for DTC 16, and slot 0 for DTC 48.) vcnum Number of the VC on the X.25 card within the DTC. On a DTC 48 or DTC 72MX, up the 256 VCs are supported. On a DTC 16, up to 32 VCs are supported. (PAD VCs must be reset using the Ldev option.) Description When the subcommand is entered, the specified VC on an X.
TermDSM Commands S[TATUS] S[TATUS] Obtains information about DTC or port configuration and the state of the DTC or port. Security level: 2. Syntax S[TATUS] Description After the STATUS command is entered, the following prompt is printed on the terminal: (status) DTc # POrt #,#,# SNp #,# ,#X.25 options - 1:Global, 2:level2, 3:level3, 4:PAD) Vc #,#,# (carriage return to exit) ? These subcommands will display the status for the selected component or connection.
TermDSM Commands S[TATUS] The following is a brief explanation of key fields printed on the terminal: • Machine Type. The HP product number of the DTC. • DTC Node Name. The user-assigned node name of the DTC. • NOVRAM Value. A code that indicates location of Nodal address and Boot Multicast address within DTC RAM. • Nodal address. 802.3 station address of the DTC. • Boot Multicast address. 802.3 multicast address which DTC uses when requesting its code file. • Host Node Address. 802.
TermDSM Commands S[TATUS] The following is a brief explanation of key fields displayed on the terminal: • Revision Number. Provides version number of SIC hardware and software. • Current Host Name. If a connection is active, and it was initiated by the terminal, then this is the name of the host to which the port is connected. Otherwise, this field is blank. • Port Type. The type of DTC connector card attached to the port. • Connection State.
TermDSM Commands S[TATUS] Description When this subcommand is entered, a large amount of information related to the X.25 card is printed on the terminal.
TermDSM Commands VC VC Obtains status information about a particular VC on an X.25 card. Security level: 2. Syntax V[C] dtcnum,cardnum,vcnum Parameters dtcnum Number of the DTC that contains the X.25 (SNP) card. This is the number TermDSM associates with this DTC. cardnum Number of the X.25 card within the DTC. The cards are numbered from zero beginning at the bottom of the DTC. (Note that SNP cards may not be mounted in slot 0 or 1 for DTC 16, and slot 0 for DTC 48.) vcnum Number of the VC.
TermDSM Commands T[RACE] T[RACE] Turns on a trace for a specific port on an asynchronous processor board of a DTC 72MX or a specific VC, level 2, or level 3 on an X.25 card (for a DTC 16, DTC 48, or DTC 72MX). Security level: 2. Syntax T[RACE] Description After the command is entered, the following prompt is printed on the terminal: (TIO or X25) TIo X25 (carriage return to exit) ? TIO specifies tracing on a selected port of an asynchronous processor board (mux card) of a DTC 72MX.
TermDSM Commands T[RACE] These are the subcommands that can then be entered. The following pages describes these options. If you press [Return] instead of one of these subcommands, you will be returned to the TRACE main prompt and then may specify TRACE TIO or TRACE X25. T[RACE] TI[O] TRACEON Starts extended tracing on a selected port of an asynchronous processor board in a DTC 72MX.
TermDSM Commands T[RACE] Parameters dtcnum Number of the DTC that contains the asynchronous board with a port that is being traced. This is the number TermDSM associates with this DTC. boardnum Number of the asynchronous board that contains the port being traced. Description TRACEOFF turns off extended trace on a port. You must turn off tracing on a port before starting extended tracing on another port on the same board. After TRACEOFF is issued, the trace information will be overwritten.
TermDSM Commands T[RACE] When you specify tracing on an X.25 card, you will also be prompted to enter a file name for the trace file. You can specify the name of the file that will contain the trace information by entering a valid MPE file name. If you want to use the default trace file (X25TRACE.PUB.SYS), press return without specifying a file name. T[RACE] X2[5] TRACEON Turns on a trace for a particular VC on an X.25 card. Security level: 2.
TermDSM Commands T[RACE] Please enter a filename for the X.25 trace or press carriage return to use the default (TRACE.PUB.SYS). Trace file will be kept in PUB.SYS. (carriage return to accept default) ? Trace Option 2 Use trace option 2 to trace level 2 information for the specified SNP card.
TermDSM Commands T[RACE] (carriage return to exit) ? Enter the link name of the X.25 link as configured in NMMGR. The link name may be up to eight (8) ASCII characters. You will then see the following prompt at the terminal: (filter) HDr (Header only) FUll (Full Packet) (carriage return to exit) ? Enter HDr if you want only header information (including TCP/IP headers) included in the trace. Enter FUll if you want full packet information included in the trace.
TermDSM Commands X25SITE X25SITE The X.25 Site Management function displays information on X.25 system-to-system connections between MPE/iX systems.. Security level: 2. Syntax X[25site] Description The connection information that can be displayed covers three areas. • Information on the DTCs managed by the MPE/iX system where TermDSM is running • Information on the an X.25 link between the DTC and the PSN • Information about the second system.
TermDSM Commands X25SITE MAP The MAP command displays the X.25 Active Site Network table. This table lists all the NS links that are configured through all the DTCs that the system is managing. Security level: 2. Syntax M[ap] Description When this command is executed, TermDSM will query all the X.
TermDSM Commands X25SITE Description When this command is executed, TermDSM will gather information about all the connections that are established through the selected link. This informtion is displayed in the Connectivity List. The connectivity list consists of the header that contains detailed information about the Link, and a table that lists information about each connection.
TermDSM Commands X25SITE Parameter vcnbr This is the Virtual Circuit number that is displayed for each connection in the Connectivity table by the LIST subcommand. There can be up to 256 VCs on a DTC 72MX or DTC48 and up to 32 VCs on a DTC16. Description When this subcommand is entered, detailed information on many parameters and counters for a selected Virtual Circuit is displayed on the terminal.
A TermDSM Messages (TDSM 15) MESSAGE: You have entered an unknown or incorrect command. Please try again. (TDSM 15) CAUSE: You have entered something that is not a TermDSM command or a command that is not valid in this context. ACTION: Commands that are valid at this time are listed in the prompt. Please try again. Type HELP or refer to Chapter 4, “TermDSM Commands,” for more information. (TDSM 16) MESSAGE: TermDSM has compiled without $partial eval$ in effect. It cannot continue.
TermDSM Messages (TDSM 22) MESSAGE: You have entered an invalid SIC card number. SIC card numbers range from 0 to 5. (TDSM 22) CAUSE: The card number that you entered is not in the range from zero to five. Card number range from 0 to 1 for DTC 16, 1 for DTC 16iX/16MX, from 0 to 5 for DTC 48, and from 0 to 3 for DTC 72MX. ACTION: Double check the card numbers by looking at the back of the DTC. Enter the card number again. (TDSM 23) MESSAGE: The SIC card number is missing or invalid.
TermDSM Messages ACTION: Enter the LIST command to generate the X.25 Connectivity List for a selected link. (TDSM 32) MESSAGE: Your security level (3) is too low to take dumps. Please log on with level 2 security to dump ports, or level 1 security to dump ports and DTCs. (TDSM 32) For level 1, you need SM or DI capability. For level 2, you need SM or DI or OP capability. CAUSE: You do not have the correct user capabilities to use this function. ACTION: Log on with level 0, 1, or 2 security.
TermDSM Messages ACTION: Contact your HP support representative. (TDSM 38) MESSAGE: The data area is longer than TermDSM's dump buffer. (TDSM 38) CAUSE: Internal error. ACTION: Contact your HP support representative. (TDSM 39) MESSAGE: TermDSM never received a reply to its dump data area request. (TDSM 39) CAUSE: Internal error. ACTION: Contact your HP support representative. (TDSM 42) MESSAGE: You must have high (1) security to perform this function.
TermDSM Messages (TDSM 50) MESSAGE: Warning: There will be no file created to keep the trace data. To get the trace data, please perform a port dump BEFORE stopping the trace. (TDSM 50) CAUSE: Extended tracing on a port on an asynchronous processor board will not be stored into a disk file. ACTION: Before terminating an extended tracing on a port with TRACEOFF, do a port dump to keep the trace data into a disk file. (TDSM 51) MESSAGE: Warning: The trace data will be overwritten by this command.
TermDSM Messages (TDSM 71) MESSAGE: There are more DTCs on your system than TermDSM can reference. Here are the ones TermDSM can reference. (TDSM 71) CAUSE: You are using more than 120 DTCs on the system. You will not be able to perform any TermDSM functions on any DTCs that are not listed in this message. ACTION: Contact your HP support representative. (TDSM 80) MESSAGE: You can’t reset your own port or ldev. Please run TermDSM from a different port or ldev to do this.
TermDSM Messages For level 2, you need SM or DI or OP capability. CAUSE: You do not have the correct user capabilities to do this function. ACTION: Logon as a user with the correct capabilities for the functions you wish to use. Refer to Chapter 4, “TermDSM Commands,” for the security level of each command and subcommand. (TDSM 93) MESSAGE: TermDSM could not open the DTC manager, so the DTC dump could not be obtained.
TermDSM Messages (TDSM 122) MESSAGE: You can’t reset your own SIC. Please run TermDSM from another SIC or DTC, or from the console. (TDSM 122) CAUSE: Your own session is on this SIC (serial interface card). If you wish to reset a SIC, you cannot be logged onto that card; the operation will abort your session and you will be unable to obtain the results. ACTION: Move to a port on a different DTC or SIC, or to the system console, to run TermDSM. (TDSM 123) MESSAGE: You can’t reset your own SNP.
TermDSM Messages ACTION: Contact you HP support representative. You can obtain additional information by running the card selftest (through the SIC subcommand of the TermDSM RESET command), the DTC selftest, and the DTC offline diagnostics. (TDSM 220) MESSAGE: Parity error. Time = xx msec. (TDSM 220) CAUSE: Probable hardware failure. ACTION: Contact you HP support representative.
TermDSM Messages If this is a terminal loopback, verify that a supported, powered on terminal is securely connected to the proper port. Check baud rate, parity, etc. Note that the terminal configuration must match the configuration file, not the state the terminal was in when it was last used. If this does not help, run internal, then external loopback to discriminate between a DTC problem and a terminal/cabling problem. (TDSM 230) MESSAGE: Alternate end-of-record received. Time = xx msec.
TermDSM Messages ACTION: Refer to the cause and action descriptions for the actual error message preceding message 241. (TDSM 242) MESSAGE: During a DTC upload (dump) operation. (TDSM 242) CAUSE: Informational message which may be printed after an error message. It describes in which phase of an operation the error occurred. ACTION: Refer to the cause and action descriptions for the actual error message preceding message 242. (TDSM 243) MESSAGE: Bad parameter from TermDSM.
TermDSM Messages CAUSE: The DTC was trying to power up at the same time you were trying to access it. ACTION: Wait for the download, or upload/download, to complete (as shown by the console messages). Verify then that the DTC is operational. If not, contact your HP support representative. (TDSM 249) MESSAGE: The DTC requested that it be dumped during the operation. (TDSM 249) CAUSE: The DTC detected an internal error at the same time you were trying to access it through TermDSM.
TermDSM Messages (TDSM 262) MESSAGE: The DTC subsystem has reported that an error was detected. Here is the specific message: (TDSM 262) CAUSE: This is the standard message that precedes specific error messages. ACTION: Contact your HP support representative. (TDSM 263) MESSAGE: An error of unknown type was reported by the DTS subsystem. (TDSM 263) CAUSE: An error unknown to TermDSM was reported by the Distributed Terminal Subsystem. ACTION: Contact your HP support representative.
TermDSM Messages CAUSE: Possible hardware problem or no card is installed in that slot. ACTION: Double check that the SIC number you specified is correct. If it is, it is likely that the SIC is defective. Contact you HP support representative. You can obtain additional information by running the card selftest (through the SIC subcommand of the TermDSM RESET command), the DTC selftest, and the DTC offline diagnostics. (TDSM 275) MESSAGE: The loopback is too long. (TDSM 275) CAUSE: Internal error.
TermDSM Messages CAUSE: It has finished the download of its operating firmware before the DTCM expected it. ACTION: Look on the console for a “boot complete” message. Otherwise, enter the command again. If the problem persists, contact your HP support representative. (TDSM 308) MESSAGE: Unable to get an LLIO message frame. (TDSM 308) CAUSE: Internal error. ACTION: Contact your HP support representative. (TDSM 309) MESSAGE: DTCM produced an unknown action code. (TDSM 309) CAUSE: Internal error.
TermDSM Messages ACTION: Verify the number that TermDSM associated with the DTC containing the DTC/X.25 XL Network Access card. Reenter the command with the correct DTC number specified. (TDSM 325) MESSAGE: Some other DTC is already tracing. (TDSM 325) CAUSE: Only one DTC can be tracing at a time. ACTION: Turn off tracing on the other DTC and try again. (TDSM 326) MESSAGE: This requested DTC is already tracing. (TDSM 326) CAUSE: Tracing has already been turned on for the specified DTC.
TermDSM Messages CAUSE: Informational message. ACTION: Issue the TRACESHOW command to see which ports on the DTC are currently under extended trace. (TDSM 336) MESSAGE: Another port on this MUX is already under extended trace. (TDSM 336) CAUSE: Only one port on an asynchronous processor board (mux card) can have extended trace at one time. ACTION: Turn off extended tracing on a traced port before activating extended tracing on another port on the same asynchronous processor board.
TermDSM Messages ACTION: Verify the DTC number on the TermDSM command. Make sure the DTC is a not a DTC 72MX, DTC 16iX, or DTC 16MX. (TDSM 400) MESSAGE: The DTC returned an NMP error code of !. (TDSM 400) CAUSE: Internal error. ACTION: Contact your HP support representative. (TDSM 401) MESSAGE: The DTC reported an NMP version mismatch. (TDSM 401) CAUSE: Internal error. ACTION: Contact your HP support representative.
TermDSM Messages (TDSM 500) MESSAGE: The DTC reported a SIC board not up. (TDSM 500) CAUSE: The serial interface card (SIC) in the DTC is not working. ACTION: Contact your HP support representative. (TDSM 590) MESSAGE: The llio error occurred when TERMDSM tried to get SYSBASE. (TDSM 590) CAUSE: Internal Error. ACTION: Contact your HP support representative. (TDSM 591) MESSAGE: The system is PC BASED. TERMDSM doesn’t support PC BASED.
TermDSM Messages For example, to execute a DUmp command for an SNP card contained in slot 3 of the DTC designated as DTC #1, you would enter the following subcommand at the DUmp subcommand prompt: SN 1,3 (TDSM 606) MESSAGE: You have entered a bad VC number. VC numbers range from 0 to 4095. (TDSM 606) CAUSE: The user entered an invalid number when asked to specify the VC number associated with the virtual circuit on which the TermDSM function is to be performed.
TermDSM Messages CAUSE: The user entered an invalid status option for the SNp subcommand of the TermDSM STatus function.
TermDSM Messages 2 = Level 2 3 = Level 3 For example, to turn on a level 2 trace for an SNP card contained in slot 3 of the DTC designated as DTC #1, you would enter the following: TRACEON 1,3,2 (TDSM 614) MESSAGE: You have entered a bad linkname. X25 linkname may be up to 8 ASCII characters. (TDSM 614) CAUSE: During execution of the TRACEON function, the user entered an invalid linkname. ACTION: Enter a valid linkname for the trace file.
TermDSM Messages (TDSM 631) MESSAGE: The ROM version is missing or invalid. The ROM version is made up of 8 ASCII characters. (TDSM 631) CAUSE: During execution of the reprogramming EEPROM process, the user failed to enter a ROM version or entered an invalid ROM version. ACTION: Enter a valid ROM version for the reprogramming EEPROM process. (TDSM 634) MESSAGE: TermDSM did not set the DTC to IDLE during EEPROM reprogramming. (TDSM 634) CAUSE: Internal error.
TermDSM Messages ACTION: Double check the port number by looking at the device connection on the DTC. Enter the port number again. This command is only supported for ports on DTC 72MX. (TDSM 683) MESSAGE: The port number is missing or invalid. Port numbers range from 0 to 23. (TDSM 683) CAUSE: The port number was not entered or is unrecognizable. ACTION: Enter the port number again. Refer to the prompt or Chapter 4, “TermDSM Commands,” for syntax. This command is only supported for ports on DTC 72MX.
TermDSM Messages ACTION: Run NMMGR and correct the X.25 address configured for loopback on the level 3 configuration screen. (TDSM 802) MESSAGE: The call has been refused by the network. Verify the address configuration and the number of VCs configured. (TDS M802) CAUSE: The user was attempting to perform a loopback test on an SNP card but the network would not accept the call. ACTION: Run NMMGR to correct any problems with the DTC/X.25 Network Access card (SNP card) configuration.
TermDSM Messages 112 Appendix A
Glossary A access port A special interface card in the system cabinet through which the MPE/iX system console is connected. ADCP Avesta Device Control Protocol. An HP proprietary protocol which provides device control features. ADCP is optimized for communications between a DTC and MPE/iX systems. address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key.
Glossary banner banner A welcome message displayed on your screen. On the local OpenView workstation a banner appears when a remote connection is established with the OpenView DTC Manager. A banner also can appear when you log on to MPE. baud The measure of the speed at which information travels between devices, most commonly used in reference to terminal speed settings. Baud represents signal events per second. When one bit represents each signal change, baud is the same as “bits per second.
Glossary DCE configuration 1) The way in which computer equipment is physically interconnected and set up to operate as a system. 2) The layout of the computer system, including the MPE table, memory, and buffer sizes, that tells which peripheral devices are (or can be) connected to the computer and how they can be accessed. 3) The process of defining the characteristics of a network in software. CSMA/CD Carrier Sense Multiple Access with Collision Detect, transmission access method used by the IEEE 802.
Glossary DDX transmission circuit. Synonyms: data communications equipment, dataset. A modem is an example of a DCE. device independence A characteristic of the operating system that allows users to selectively redirect input/output from a program, session, or job without regard to the nature of the device. DDX The national public PSN of Japan. device name See PAD name. DDFA DTC Device File Access Utilities.
Glossary DTE DTC 16 HP 2340A product. A DTC that provides 2 slots for asynchronous connections with each slot allowing up to 8 direct connections or 6 modem connections, plus an optional X.25 link supporting up to 32 virtual circuits. DTC node name A unique name used to identify a DTC on a LAN. The node name format is nodename.domain.organization, with each of the three parts having up to 16 characters. The name begins with either a letter or a digit. DTC 16iX HP J2062A product.
Glossary DTS event log One of three circular files stored on the OpenView windows workstation. It contains lists of events that are reported by the DTCs for which it is responsible. DTS Distributed Terminal Subsystem. This consists of all of the Datacommunications and Terminal Controllers (DTCs) on a LAN, their LANIC cards (attached to the host), the LAN cable, and the host and DTC software that controls all related DTS hardware. F duplex A transmission method that allows two-way communication.
Glossary HP TS8 flow control negotiation One of the network subscribed facilities selected at subscription time. This facility allows the Flow Control parameter to be negotiated at call set-up time, as opposed to having a predefined value. formal file designator A name that can be used programmatically or in a file equation to refer to a file. FOS Fundamental Operating System.
Glossary idle device timeout I idle device timeout A timeout defined by the Configure:CPU command. When the timer lapses, a device connected to the DTC user interface that is still inactive will be disconnected. IEEE 802.3 A standard for a broadcast local area network published by the Institute for Electrical and Electronics Engineers (IEEE). This standard is used for both the ThinLAN and ThickLAN implementations of the LAN. IEEE 802.3 multicast address A hexadecimal number that identifies a set of nodes.
Glossary map, network LANIC physical path The physical location (slot number) of the LANIC within the SPU. LANIC Self-Test A ROM-based program on a LANIC card that tests and reports the status of the LANIC hardware. LAP Link Access Protocol. The data link protocol specified by older versions (prior to 1980) of X.25 at Level 2 but still permitted and therefore usable. All new implementations of X.25 must use LAP-B, and all old implementations must migrate to LAP-B at a future date.
Glossary mapping mapping A set of characteristics that describe a route taken by messages to reach a destination node. This set of characteristics is configured with NMMGR at every node on a point-to-point network. One mapping is configured at each node for every other node on the network to which messages will be sent. MAU Medium Attachment Unit. A device attached to a ThickLAN coaxial cable that provides the physical and electrical connection from the AUI cable to the coaxial cable. M bit More data bit.
Glossary NS 3000/iX Link network map A drawing that shows the topology of the network. For networks managed by the OpenView DTC Manager, a network map must be created using the OVDraw capability provided with the management software. Network Services NS. Software application products that can be used to access data, initiate processes, and exchange information among nodes in the network. The HP 3000/iX Network Services include RPM, VT, RFA, RDBA, and NFT.
Glossary NS 3000/iX Network Services the DTC/X.25 iX Network Link, the NS Point-to-Point 3000/iX Link, and the StarLAN 10 3000/iX link. Terminal Controller (DTC). The configuration software that runs on this workstation is called the OpenView DTC Manager software. NS 3000/iX Network Services Software applications that can be used to access data, initiate processes, and exchange information among nodes in a network. The services are RPM, VT, RFA, RDBA, and NFT.
Glossary Q bit path name When configuring with NMMGR, you can type a string in the COMMAND: field on a screen to branch to another screen. Each screen has a unique path name that corresponds to its location in the hierarchy of configuration screens presented by NMMGR. PDN Public data network. A data communication network whose services are available to any user willing to pay for them. Most PDNs use packet switching techniques.
Glossary Q bit Q Q bit Qualified bit. When set in DATA packets the Q bit signifies that the packet’s user data is a control signal for the remote device, not a message for its user. QuickVal A software program that tests whether Network Services are operating correctly between nodes. R RDBA Remote Data Base Access. A network service that allows users to access data bases on remote nodes.
Glossary terminal profile SIC Serial Interface Card. A card installed in the front of the DTC that acts as an interface between a corresponding Connector Card (CC) and the DTC’s processor. slaved device A device that shares the same DTC port as another device and is connected, to the other device, referred to as its master, by a cable. The actions of the slaved device are controlled by the master device. SNMP Simple Network Management Protocol.
Glossary terminal type type, line speed, device class assignment, and other values relevant to terminals connected through a DTC. All other characters are considered to be data and are passed through with no control actions being taken. terminal type A collection of characteristics that cause a terminal connected to an MPE/iX system to act and react in a specified manner.
Glossary X.Series (X.##) CCITT recommendations virtual circuit A logical association between two physically separate DTEs. X.25 address key An X.25 address key is a label that maps a node’s IP address to its X.25 address and its associated X.25 parameters. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. Virtual Terminal A network service that allows a user to establish interactive sessions on a node. X.25 LUG address X.25 address of a node belonging to a LUG.
Glossary X.
Index Numerics 10Base-T, 20 25-pin connectors, 34 25-pin RS-232 , 17 3-pin connectors, 34 3-pin RS-232 , 17 5-pin connectors, 34 5-pin RS-422 , 17 A abort sessions, 34 aborting sessions, 36 access port, 16 application software , 22, 25 ASC, 33 Asynchronous Serial Communications ASC, 20 asynchronous serial devices, 16, 33, 34 B block mode, 21, 22 BNCT-connector, 19 C cabinet space, 16 character mode , 21, 22 coaxial cable, 18 collect information, 22 command-based utility, 36 COMMENT command, 37 configuration
Index check, 22 connections, 21 N NMMGR, 20 node address, 18 Node Management Configuration Manager NMMGR, 20 nodes, 18 P parity sensing , 28 PC-based management, 17 PCs, 25 plotters, 25 port, 34, 36 port buffers , 29 power cord , 28 powerfail recovery , 21 printers, 16 connections, 21 Print-to-Port Test , 29 R remote devices, 17 remote mode, 28 RESET command, 37, 67 DTC, 67 Ldev, 68 Port, 69 SIC, 69 SNP, 70 VC, 70 reset functions, 29 RS-232-C direct-connect cards, 34 RS-422 direct-connect cards , 34 S secur
Index TRACE X25 command, 79 TRACEOFF mux ports, 78 VC, 82 TRACEON mux ports, 78 VC, 80 TRACESHOW mux ports, 79 troubleshooting at the device , 26 U user capabilities, 34 V VC trace, 80 VPLUS applications, 21 X XON/XOFF protocol, 28 133
Index 134
