SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Transcription

1 SWAN Concentrator and WAN Subsystem Troubleshooting Guide Abstract This guide describes how to troubleshoot the SWAN concentrator, SWAN 2 concentrator, and WAN subsystem on an HP Integrity NonStop BladeSystem, HP Integrity NonStop NS-series, and HP NonStop S-series server. This guide is for anyone who configures, manages, or maintains the ServerNet wide area network (SWAN) or SWAN 2 concentrator and WAN subsystem. Product Version WAN G06 and H01 Supported Release Version Update (RVUs) This publication supports G06.23 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J06.03 and all subsequent J-series RVUs until otherwise indicated by its replacement publication. Part Number Published August 2010

2 Document History Part Number Product Version Published WAN F40 September WAN G06 and H01 August WAN G06 and H01 July WAN G06 and H01 August WAN G06 and H01 August 2010

3 SWAN Concentrator and WAN Subsystem Troubleshooting Guide Glossary Index Examples Figures Tables What s New in This Guide vii Guide Information vii New and Changed Information vii HP Encourages Your Comments viii About This Guide ix Who Should Use This Guide How This Guide Is Organized Related Manuals xi Notation Conventions xii Abbreviations xvii ix x 1. Troubleshooting the SWAN Concentrator and WAN Subsystem SWAN/WAN Troubleshooting Process 1-2 What to Do if You Can't Solve a Problem 1-3 Gathering Files for GMCSC Analysis 1-3 Tracing a Communications Line 1-4 Finding SWAN Concentrator and WAN Subsystem Event Messages in the Event Log 1-4 Viewing SWAN Concentrator Alarms 1-6 Recovering From a SWAN Concentrator Alarm 1-6 SWAN Download Error Alarm 1-7 Network Error Alarm 1-7 I/O Process Error Alarm 1-8 SWAN Memory Error Alarm 1-8 Hardware Error Alarm 1-8 IOP Line Parameters Error Alarm 1-8 SWAN Kernel Error Alarm 1-8 Incorrect Logical Configuration Alarm 1-9 Clearing a SWAN Concentrator Alarm 1-10 Hewlett-Packard Company i

4 Contents 2. Verifying the SWAN Configuration 2. Verifying the SWAN Configuration Verifying a SWAN Concentrator Configuration 2-1 Correcting SWAN Concentrator Configuration Errors 2-5 Correcting the Ethernet Adapter Configuration 2-5 Correcting the TCP/IP Process Configuration 2-7 Correcting the SWAN Concentrator IP Addresses 2-8 Correcting a WAN Subsystem Process Configuration Problem 2-9 Verifying a WAN Subsystem Device Configuration 2-9 Changing a WAN Subsystem Device Configuration 2-11 HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) 2-13 G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) 2-15 HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and J06.03 and Later RVUs) Verifying the WAN Subsystem Verifying the WAN Subsystem Processes and Objects 3-1 Starting the WAN Subsystem Processes and Objects 3-4 Identifying the WAN Subsystem Processes and Objects 3-6 Determining the Name of the SWAN Concentrator Used by a WAN Subsystem IOP or the Names of the WAN Subsystem IOPs Configured to Use a SWAN Concentrator 3-6 Determining the TCP/IP Processes and IP Addresses That Support a SWAN Concentrator 3-7 Determining the LIFs Associated With the TCP/IP Processes and IP Addresses That Support a SWAN Concentrator 3-7 Determining the E4SAs, FESAs, GESAs, or G4SAs to Which a SWAN Concentrator is Connected 3-8 Determining the WANMgr Processes 3-8 Determining the ConMgr, SNMP Trap Multiplexer, TFTP Server, WANBoot, and SNMP Agent Processes That Support a SWAN Concentrator 3-8 Determining the Names of the SWAN Concentrators Configured on a System Verifying the SWAN Hardware Verifying the SWAN Concentrator Hardware 4-2 How to Run a Test Action 4-2 Correcting SWAN Concentrator Hardware Problems 4-3 Firmware and Battery Problems 4-3 Error IDs related to OSM or TSM Test Action Failure 4-4 SWAN Concentrator Cabling 4-10 Common Cabling Problems 4-11 SWAN Concentrator and WAN Subsystem Troubleshooting Guide ii

5 Contents 4. Verifying the SWAN Hardware (continued) 4. Verifying the SWAN Hardware (continued) Verifying SWAN Concentrator Cabling 4-11 Correcting SWAN Concentrator Cabling 4-13 Verifying the SWAN Concentrator Track-ID 4-13 Verifying LAN Hardware for a SWAN Concentrator 4-15 Correcting a LAN Hardware Problem for a SWAN Concentrator 4-15 SWAN Concentrator LEDs 4-15 Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update 4-19 Preparing a CLIP 4-19 Resuming Operation on a CLIP Installing and Using the SWAN Tools CLIP Dump 5-1 QUEST 5-2 Dump Formats 5-2 QUEST Command Syntax 5-3 Bus Error Dumps 5-7 SWT Error Dumps 5-9 psos/pna Error Dumps 5-9 QUEST Differences Between QUEST and QUEST QUEST2 Output 5-10 Dump Formats 5-11 QUEST2 Interfaces 5-11 QUEST 2 Command Syntax 5-15 WANDUMP 5-28 WANDUMP Command Syntax 5-28 WANDUMP Command Example 5-29 WANLNCK 5-29 WAN LINE Diagnostic Information Test 5-29 External Loopback Test 5-29 WANLNCK Command Syntax 5-30 Configuration Setup for a Modem or a DCE 5-32 WANLNCK Command Example 5-32 WANFBT 5-37 WANFBT Command Syntax 5-37 WANFBT Command Example 5-37 SWAN Concentrator and WAN Subsystem Troubleshooting Guide iii

6 Contents 5. Installing and Using the SWAN Tools (continued) 5. Installing and Using the SWAN Tools (continued) WANTCB 5-38 WANTCB Command Syntax 5-38 WANTCB Command Example Troubleshooting Tips for the SWAN Concentrator and the WAN Subsystem Latent Failure Detection (LFD) 6-2 CLIP Dump Detection and Recovery 6-3 Device Configuration Guidelines for Optimum Performance 6-5 Ownership Errors and Resolutions 6-5 Finding the VPROC of the Firmware 6-7 Checking CLIP Accessibility 6-8 Restarting and Resetting the CLIP Through the Software 6-9 Finding the MAC Address of the CLIP 6-10 Finding the Current PATH Status of the CLIP 6-11 TCP/IP, Parallel Library TCP/IP, and NonStop TCP/IPv Configuring the Correct Track-ID 6-13 Troubleshooting if the CLIP is Inaccessible Error and Informational Messages With Recovery Actions BOOTP Error Messages 7-2 PATH and SNMP Error Messages 7-7 ConMgr Error Messages 7-10 Format (Example 1) 7-10 Format (Example 2) 7-12 Format (Example 3) 7-12 Error Messages 7-12 FIRMUP Error Messages 7-23 Format 7-23 Error Messages 7-24 A. Examples Determining the SWAN Concentrator Used by a Communications Line A-2 Determining the WAN Subsystem IOPs That Use a SWAN Concentrator A-3 Determining the Location of a WAN Subsystem Device A-4 Displaying Modifiers for a WAN Subsystem Device A-5 Displaying Modifiers for a Communications Line A-6 Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator A-7 SWAN Concentrator and WAN Subsystem Troubleshooting Guide iv

7 Contents A. Examples (continued) A. Examples (continued) Determining the TCP/IP Process and IP Address for a LIF A-8 Determining the LIFs Used by a SWAN Concentrator A-9 Determining the LIFs and PIFs for an Adapter A-10 Identifying the LAN Adapters on a System A-11 Determining the LAN Adapters Used by a SWAN Concentrator A-12 Determining the Location of a LAN Adapter A-13 Displaying Information for a WAN Subsystem Process A-14 Verifying That the TFTP Server Process is Started A-15 Verifying That the WANBoot Process is Started A-16 Verifying That the SNMP Trap Multiplexer Process is Started A-17 Verifying That the WAN Manager Process is Started A-18 Verifying That the LAN Manager Process is Started A-19 Verifying That the ADAPTER Object for a LAN Adapter is Started A-20 Verifying That the SACs for a LAN Adapter Are Started A-21 Verifying That a PIF is Started A-22 Verifying That a LIF is Started A-23 Verifying That a TCP/IP Process is Started A-24 Verifying That a TCP/IP SUBNET is Started A-25 Verifying That a TCP/IP Route is Started A-26 Verifying That the WAN Subsystem Processes Are Started A-27 Verifying That a WAN Subsystem Device is Started A-28 Determining the IP Addresses for a SWAN Concentrator A-29 Verifying That a SWAN Concentrator is Started A-30 Verifying That a SWAN Concentrator Path is Started A-31 Glossary Index Examples Figures Figure 1-1. SWAN/WAN Troubleshooting Process Flowchart 1-2 Figure 3-1. WAN Subsystem Process and Objects 3-6 Figure 4-1. SWAN Concentrator Label, Configuration Track-ID 4-13 Figure 4-2. SWAN 2 Concentrator Label 4-14 SWAN Concentrator and WAN Subsystem Troubleshooting Guide v

8 Contents Tables Tables Table i. Contents x Table 1-1. Names of Associated Processes and Objects 1-5 Table 1-2. Related Subsystems 1-5 Table 2-1. Communications Subsystems Manuals 2-12 Table 2-2. Naming Convention for WAN Subsystem, SWAN Concentrator, Related Processes, Devices, and Adapters (G06.26 and Earlier RVUs) 2-13 Table 2-3. Naming Convention for the WAN Subsystem, SWAN Concentrator, and Related Processes, Devices, and Adapters (G06.27 and Later RVUs, H06.03 and Later RVUs, and J06.03 and Later RVUs) 2-17 Table 4-1. SWAN Concentrator LEDs 4-16 Table 4-2. SWAN 2 Concentrator LEDs 4-17 Table 5-1. Dump Information 5-3 Table 5-2. Comparison of QUEST AND QUEST2 Parameters and Options 5-13 Table 5-3. Compatibility between WANLNCK (T0465) and Diag (T8155) 5-30 SWAN Concentrator and WAN Subsystem Troubleshooting Guide vi

9 What s New in This Guide Guide Information Abstract SWAN Concentrator and WAN Subsystem Troubleshooting Guide This guide describes how to troubleshoot the SWAN concentrator, SWAN 2 concentrator, and WAN subsystem on an HP Integrity NonStop BladeSystem, HP Integrity NonStop NS-series, and HP NonStop S-series server. This guide is for anyone who configures, manages, or maintains the ServerNet wide area network (SWAN) or SWAN 2 concentrator and WAN subsystem. Product Version WAN G06 and H01 Supported Release Version Update (RVUs) This publication supports G06.23 and all subsequent G-series RVUs, H06.03 and all subsequent H-series RVUs, and J06.03 and all subsequent J-series RVUs until otherwise indicated by its replacement publication. Part Number Published August 2010 Document History Part Number Product Version Published WAN F40 September WAN G06 and H01 August WAN G06 and H01 July WAN G06 and H01 August WAN G06 and H01 August 2010 New and Changed Information Changes to the H06.21 and J06.10 Manual ( Version) Added updated HP contact information to HP Encourages Your Comments on page -viii. Updated information for how to contact the Global Critical Mission Solution Center and how to prepare files for analysis to What to Do if You Can't Solve a Problem on page 1-3. SWAN Concentrator and WAN Subsystem Troubleshooting Guide vii

10 What s New in This Guide Change to the H06.07 Manual Added J-series naming conventions for SWAN concentrators to HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and J06.03 and Later RVUs) on page Added important information related to SWAN firmware and SWAN 2 battery problems to Correcting SWAN Concentrator Hardware Problems on page 4-3. Added minor updates to Troubleshooting Tips for the SWAN Concentrator and the WAN Subsystem on page 6-1. Change to the H06.07 Manual Updated the WANLNCK command on page 5-29 to support systems running H-series RVUs. Change to the G06.29 Manual Updated WANLNCK on page 5-29 to include the support for the WAN LINE Diagnostic Information test and External Loopback test for SWAN and SWAN 2 concentrators. Changes to the H06.03 Manual About This Guide Section 1, Troubleshooting the SWAN Concentrator and WAN Subsystem Section 2, Verifying the SWAN Configuration Section 4, Verifying the SWAN Hardware Section 6, Troubleshooting Tips for the SWAN Concentrator and the WAN Subsystem Appendix A, Examples HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement concerning this document. SWAN Concentrator and WAN Subsystem Troubleshooting Guide viii

11 About This Guide The SWAN Concentrator and WAN Subsystem Troubleshooting Guide describes how to troubleshoot the SWAN concentrator, the SWAN 2 concentrator, and the WAN subsystem on an Integrity NonStop NS-series or NonStop S-series server. This guide includes: A flowchart to guide you through the SWAN/WAN troubleshooting process. What to do if you can t solve a problem, including information about how to report problems to the Global MIssion Critical Solution Center (GMCSC) for analysis. How to gather SWAN information by examining event messages and viewing OSM and TSM alarms. How to verify the SWAN concentrator configuration and correct configuration errors by using SCF commands. How to verify the WAN subsystem software and how to correct configuration errors by using SCF commands. How to verify the SWAN concentrator hardware and fix SWAN concentrator hardware problems. A procedure for installing and using the SWAN tool collection to debug the WAN subsystem. Troubleshooting tips for your SWAN configuration. Error messages, including cause, effect, and recovery information for the SWAN concentrator and WAN subsystem. Examples showing various SCF tasks and associated displays for the SWAN concentrator and WAN subsystem. Who Should Use This Guide This guide is for anyone who is responsible for configures, manages, troubleshoots, or maintains the ServerNet wide area network (SWAN), the SWAN 2 concentrator, and the WAN subsystem. You must understand the architecture of an Integrity NS-series or NonStop S-series system and the features of the G-series or H-series RVUs well enough to install, configure, and maintain the SWAN or SWAN 2 concentrators and WAN subsystem. SWAN Concentrator and WAN Subsystem Troubleshooting Guide ix

12 About This Guide How This Guide Is Organized How This Guide Is Organized Table i. Contents Section or Appendix Title Contents 1 Troubleshooting the SWAN Concentrator and WAN Subsystem 2 Verifying the SWAN Configuration 3 Verifying the WAN Subsystem 4 Verifying the SWAN Hardware 5 Installing and Using the SWAN Tools 6 Troubleshooting Tips for the SWAN Concentrator and the WAN Subsystem 7 Error and Informational Messages With Recovery Actions Provides a flowchart to guide you through the SWAN/WAN troubleshooting process. Also includes what to do if you can t solve a problem and how to view OSM and TSM alarms. Describes how to verify the SWAN and SWAN 2 concentrator configuration and how to correct configuration errors by using SCF commands. Describes how to verify the WAN subsystem software and correct configuration errors by using SCF commands. Describes how to verify the SWAN concentrator hardware and fix SWAN concentrator hardware problems. Describes the SWAN and SWAN 2 tools available to debug the SWAN concentrator. Provides troubleshooting tips for your SWAN and SWAN 2 configuration. Lists cause, effect, and recovery information for SWAN concentrator and WAN subsystem error messages. A Examples Provides a comprehensive list of examples showing various SCF tasks and associated displays for the SWAN concentrator and WAN subsystem. SWAN Concentrator and WAN Subsystem Troubleshooting Guide x

13 About This Guide Related Manuals Related Manuals Depending on the tasks you are performing, you might require these manuals: SWAN Concentrator Installation and Support Guide SWAN 2 Concentrator Installation and Support Guide TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IPv6 Configuration and Management Manual WAN Subsystem Configuration and Management Manual To configure one or more SWAN concentrators, you can use a configuration tool called WAN Wizard Pro. WAN Wizard Pro WAN Wizard Pro is a graphical user interface (GUI) that guides you step-by-step through the configuration process of one or more SWAN concentrators. It is an efficient alternative to using multiple Subsystem Control Facility (SCF) commands. Depending on your RVU, you gain access to WAN Wizard Pro through the taskbar on your system console by using one of these methods: For G06.21 RVU and later RVUs and H06.03 and later RVUs: Start>Programs>HP WAN Wizard Pro>WAN Wizard Pro For G06.20 RVU and earlier RVUs: Start>Programs>Compaq TSM>Guided Configuration Tools>WAN Wizard Pro Configuring Data Communications Subsystems The WAN subsystem configures and manages both wide area network (WAN) and local area network (LAN) connectivity for the following communications subsystems: AM3270 ATP6100 CP6100 Envoy EnvoyACP/XF Expand SNAX/APN SNAX/XF TR3271 X25AM SWAN Concentrator and WAN Subsystem Troubleshooting Guide xi

14 About This Guide Understanding Event Messages For information about configuring the subsystems, see these manuals: AM3270 and TR3271 Configuration and Management Manual Asynchronous Terminals and Printer Processes Configuration and Management Manual CP6100 Configuration and Management Manual Envoy Configuration and Management Manual EnvoyACP/XF Configuration and Management Manual Expand Configuration and Management Manual SNAX/XF and SNAX/APN Configuration and Management Manual X25AM Configuration and Management Manual Understanding Event Messages The event messages generated by the WAN subsystem and the SWAN concentrator are described in the WANMGR and TRAPMUX sections of the Operator Messages Manual. Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c SWAN Concentrator and WAN Subsystem Troubleshooting Guide xii

15 About This Guide General Syntax Notation italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [, new-value ] [ - ] { } An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char " Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name SWAN Concentrator and WAN Subsystem Troubleshooting Guide xiii

16 About This Guide General Syntax Notation Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [, attribute-spec ]!i and!o. In procedure calls, the!i notation follows an input parameter (one that passes data to the called procedure); the!o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id!i, error ) ;!o!i,o. In procedure calls, the!i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ;!i,o!i:i. In procedure calls, the!i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length!i:i, filename2:length ) ;!i:i!o:i. In procedure calls, the!o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum!i, [ filename:maxlen ] ) ;!o:i SWAN Concentrator and WAN Subsystem Troubleshooting Guide xiv

17 About This Guide Notation for Messages Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE?123 CODE RECEIVED: The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object Operator Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } SWAN Concentrator and WAN Subsystem Troubleshooting Guide xv

18 About This Guide Notation for Management Programming Interfaces Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: % %B %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces The following list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type!r.!o. The!r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.!r The!o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.!o Notation for Subnet The following list describes the notation conventions for SUBNET and subnet used in this guide. UPPERCASE LETTERS. Uppercase letters indicate the NonStop TCP/IP, Parallel Library TCP/IP, or NonStop TCP/IPv6 SCF SUBNET object. For example: Port A is identified by logical interface (LIF) 018, which uses a SUBNET on the TCP/IP process named $ZB018 in processor 0. SWAN Concentrator and WAN Subsystem Troubleshooting Guide xvi

19 About This Guide Change Bar Notation lowercase letters. Lowercase letters indicate the general networking term for subnet. For example: Multicast datagrams that have a Time-To-Live (TTL) value of 1 are forwarded only to hosts on the local subnet. Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. Abbreviations ATM. Asynchronous Transfer Mode ATM3SA. ATM 3 ServerNet adapter CCSA. Common Communication ServerNet adapter CTS. clear to send DIH. Driver Interrupt Handler DCE. data communications equipement DSM. Distributed Systems Management DTE. data terminal equipment DTR. data terminal ready DSR. data set ready E4SA. Ethernet 4 ServerNet adapter EMS. Event Management Service FCSA. Fibre-Channel ServerNet adapter FESA. Fast Ethernet ServerNet adapter FRU. field-replaceable unit SWAN Concentrator and WAN Subsystem Troubleshooting Guide xvii

20 About This Guide Abbreviations GESA. Gigabit Ethernet ServerNet adapter G4SA. Gigabit Ethernet 4-Port ServerNet adapter HDLC. high-level data-link control IOAM. I/O adapter module IPX/SPX. Internet Packet Exchange/Sequenced Packet Exchange I/O. input/output LAN. local area network LANMAN. LAN Manager LANMON. LAN monitor LIF. logical interface MAC. media access control mbps. megabits/second MAU. medium attachment unit MFIOB. multifunction I/O board MODEM. MOdulator DEModulator MSEB. modular ServerNet expansion board PIF. physical interface POST. power-on self-test PVC. permanent virtual circuit QIO. Queued Input/Output RTS. request to send SAC. ServerNet addressable controller SAN. System Area Network SCF. Subsystem Control Facility SCP. Subsystem Control Point SEB. ServerNet expansion board SMB. serial maintenance bus SWAN Concentrator and WAN Subsystem Troubleshooting Guide xviii

21 About This Guide Abbreviations SLSA. ServerNet LAN Systems Access SP. service processor TCP/IP. Transmission Control Protocol/Internet Protocol TRSA. Token-Ring ServerNet adapter SWAN. ServerNet wide area Network VCC. Virtual Channel Connection WAN. wide area network WAN IOP. wide area network input/output process SWAN Concentrator and WAN Subsystem Troubleshooting Guide xix

22 About This Guide Abbreviations SWAN Concentrator and WAN Subsystem Troubleshooting Guide xx

23 1 Troubleshooting the SWAN Concentrator and WAN Subsystem Note. Throughout this guide when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section provides a flowchart to guide you through the ServerNet Wide Area Network (SWAN) and WAN troubleshooting process (see Figure 1-1 on page 1-2). Topics described in this section include: SWAN/WAN Troubleshooting Process on page 1-2 What to Do if You Can't Solve a Problem on page 1-3 Gathering Files for GMCSC Analysis on page 1-3 Tracing a Communications Line on page 1-4 Finding SWAN Concentrator and WAN Subsystem Event Messages in the Event Log on page 1-4 Viewing SWAN Concentrator Alarms on page 1-6 Recovering From a SWAN Concentrator Alarm on page 1-6 SWAN Concentrator and WAN Subsystem Troubleshooting Guide

24 Troubleshooting the SWAN Concentrator and WAN Subsystem SWAN/WAN Troubleshooting Process SWAN/WAN Troubleshooting Process Figure 1-1 outlines the troubleshooting process for SWAN or SWAN 2 concentrator and WAN subsystem. Always begin at Step 1: Gather Information. The order of the remaining steps is determined by the event messages and alarms received in Step 1. Figure 1-1. SWAN/WAN Troubleshooting Process Flowchart Step 1: Gather Information Examine Event Messages View OSM or TSM Alarms Step 2: Verify the Configuration Verify the SWAN Configuration How to Fix the SWAN Configuration Verify the Device Object Configuration How to Fix a Device Object Configuration Step 3: Verify the Software Verify the WAN Processes and Objects How to Start WAN Processes and Objects Step 4: Verify the Hardware Verify the SWAN Hardware How to Fix SWAN Hardware Verify the SWAN Cabling How to Fix SWAN Cabling Verify the LAN Hardware How to Fix LAN Hardware VST002.vsd For more information about the steps in this flowchart, for: Step 1: Gathering information, see: Finding SWAN Concentrator and WAN Subsystem Event Messages in the Event Log on page 1-4 and Viewing SWAN Concentrator Alarms on page 1-6. Step 2, see: Verifying the SWAN Configuration on page 2-1. Step 3, see: Verifying the WAN Subsystem on page 3-1. Step 4, see: Verifying the SWAN Hardware on page 4-1. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

25 Troubleshooting the SWAN Concentrator and WAN Subsystem What to Do if You Can't Solve a Problem If you receive an error message, see Section 7, Error and Informational Messages With Recovery Actions to help you diagnose and recover from the error. What to Do if You Can't Solve a Problem If you cannot solve a SWAN concentrator or WAN subsystem problem, contact the Global Mission Critical Solution Center (GMCSC) for an analysis of the problem. For more information about the GMCSC or how to contact them, see: In some cases, it might also be appropriate to trace a communications line and provide trace information to the GMCSC. Note. There is currently no officially released trace facility for the WAN subsystem processes and objects. Gathering Files for GMCSC Analysis Before gathering files for analysis, you might want to contact the GMCSC to determine the best procedure for analyzing the problem. If information needs to be gathered, the following information can be useful for analysis: A readme file that describes what you were doing at the time the error occurred and just prior to that time. Include this information (as appropriate): VPROC information for WANMgr, ConMgr, WANBoot, and the SWAN communications line interface processor (CLIP) firmware. Current version of the operating system, service processor (SP) firmware, and related applications. SCF INFO for $ZZWAN.* (include ADAPTER, SERVER, and PATH objects). SCF STATUS for $ZZWAN.* (include ADAPTER, SERVER, and PATH objects). EMS logs for the period when the problem occurred. Associated TCP/IP configuration for the listed SWAN ADAPTERS. Any CLIP dump file found in $SYSTEM.ZWANDUMP. Any other information required by the GMCSC or Development for analysis. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

26 Troubleshooting the SWAN Concentrator and WAN Subsystem Tracing a Communications Line Tracing a Communications Line To start tracing a communications line, use the SCF TRACE command. Tracing enables you to see the history of a communications line, including significant points in the internal processing of the traced entity. For tracing to be an effective, fault-finding tool, follow these guidelines: Always trace both ends of a communications path. Ensure that all traces for a particular problem are taken at the same time. If the data rate is high or if the trace is expected to run for many hours, preallocate the file space for the trace file by using the File Utility Program (FUP). A 3-megabyte or 4-megabyte file is generally enough for all but the longest or most work-intensive traces. For Expand lines, gather a $NCP trace even if you do not think the problem involves $NCP. It is preferable to have too much rather than too little information. You can display trace files by using the commands available in the PTrace program. For information about PTrace, see the PTrace Reference Manual. For information about the SCF TRACE command and the communications subsystem you want to trace, see the Configuration and Management Manual. Finding SWAN Concentrator and WAN Subsystem Event Messages in the Event Log Before you search the event log ($ZLOG) for SWAN concentrator and WAN subsystem event messages, you should be familiar with the names of the processes and objects that support the SWAN and SWAN 2 concentrators and WAN subsystem devices (DEVICE object). For information about how to identify these processes and objects, see Identifying the WAN Subsystem Processes and Objects on page 3-6. Look for messages generated by the subsystems listed in Table 1-1. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

27 Troubleshooting the SWAN Concentrator and WAN Subsystem Finding SWAN Concentrator and WAN Subsystem Event Messages in the Event Log Table 1-1. Names of Associated Processes and Objects Subsystem Subsystem Name Subsystem Number What to Look For SLSA (LAN) SLSA 193 Messages that identify the Ethernet adapter ADAPTER, LIF, PIF, and SAC objects that support the SWAN concentrators. SWAN or SWAN 2 concentrator TRAPMUX 185 Messages that identify the SNMP trap multiplexer process that supports the SWAN concentrators. TCP/IP ZTCI 80 Messages that identify the preferred and alternate TCP/IP processes that support the SWAN concentrators. WAN WANMGR 176 Messages that identify the WANBoot, TFTP server, SNMP trap multiplexer, and ConMgr processes that support the SWAN concentrators. Also look for messages that identify the SWAN concentrators ADAPTER, SERVER, PATH, and TASK objects and the WAN subsystem devices. Depending on the types of communications lines configured, you should also look for messages generated by the subsystems listed in Table 1-2. Table 1-2. Related Subsystems Subsystem Subsystem Name Subsystem Number AM3270 AM ATP6100 ATP CP6100 CP Envoy ENVOY 107 EnvoyACP/XF EXF 88 Expand EXPAND 30 SNAX/XF and SNAX 36 SNAX/APN TR3271 TR X25AM X25 41 SWAN Concentrator and WAN Subsystem Troubleshooting Guide

28 Troubleshooting the SWAN Concentrator and WAN Subsystem Viewing SWAN Concentrator Alarms When you view events using the OSM or TSM Event Viewers, the subsystem name (or, in rare cases, the subsystem number) is shown in the SSID column. Both allow you to specify the date and time ranges of the events you want displayed; the logs (such as $0 and $ZLOG) from which you want events displayed; and the subsystems from which you want events displayed. To learn more about the differences between the OSM Event Viewer and the TSM Event Viewer, see the OSM Migration Guide. Cause, effect, and recovery information for event messages is available in event details within the event viewers and also in the Operator Messages Manual. Viewing SWAN Concentrator Alarms To view an alarm generated by a ServerNet wide area network (SWAN) concentrator, use the OSM Service Connection or the TSM Service Application: 1. In either the tree pane or the view pane, click on the resource. 2. In the details pane, click the Alarms tab. Alarms for the selected resource appear in the Alarms tab in the details pane. 3. In the Alarms tab in the details pane, right click on the alarm and select Details from the menu. The Alarm Detail dialog box appears. 4. To display repair actions for the alarm, in the Alarm Detail dialog box, check Repair Actions or Repair Steps (depending on your version of client software). If you need more detailed information about how to recover from a specific alarm, see Recovering From a SWAN Concentrator Alarm. Recovering From a SWAN Concentrator Alarm This section explains how to recover from a ServerNet wide area network (SWAN) concentrator alarm displayed by the OSM Service Connection or TSM Service Application. The SWAN concentrator alarms and recovery information is described in this subsections: SWAN Download Error Alarm Network Error Alarm I/O Process Error Alarm SWAN Memory Error Alarm Hardware Error Alarm IOP Line Parameters Error Alarm SWAN Kernel Error Alarm SWAN Concentrator and WAN Subsystem Troubleshooting Guide

29 Troubleshooting the SWAN Concentrator and WAN Subsystem SWAN Download Error Alarm Incorrect Logical Configuration Alarm SWAN Download Error Alarm This alarm is generated when a problem occurs during the downloading of a data link control (DLC) task to a communications line interface processor (CLIP) on the SWAN concentrators. Possible causes of this alarm include: A problem in the DLC task object code file (specified by the PROGRAM attribute). A problem in the ConMgr process, the WAN manager process, or the TFTP server process. These processes work together to download a DLC task to a CLIP. A problem in the software or hardware connection between the SWAN concentrators and the NonStop S-series server. There are two types of DLCs: one for SWAN (xxxxxpxx) and one for SWAN 2 (xxxxxqxx). If the wrong DLC is downloaded, a download error will occur when an attempt is made to start the line. To recover from this alarm: 1. Make sure that the DLC task object code files are secured with "N" read access. The DLC task object code files should be located in the $SYSTEM.CSSnn subvolume. 2. Make sure that the TFTP server process is configured to use the correct location for the DLC task object code files. (The TFTP server process is automatically configured by the WAN manager process.) The location of download is specified by the STARTUP attribute. (The default location is $SYSTEM.CSSnn subvolume.) 3. Check the status of the required WAN subsystem processes and objects and their supporting processes, then restart any processes and objects that are not in the STARTED state. 4. Check the cable connections between the E4SAs, FESAs, GESAs, or G4SAs and the SWAN concentrator, and correct any cabling problems. 5. Check the LAN hardware, then correct any LAN hardware problems. Network Error Alarm This alarm is generated when the software or hardware connection between the NonStop S-series server and the SWAN concentrator is not operational. To recover from this alarm, perform Steps 2 through 5 as described for SWAN Download Error Alarm on page 1-7. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

30 Troubleshooting the SWAN Concentrator and WAN Subsystem I/O Process Error Alarm I/O Process Error Alarm This alarm is generated when the connection between a WAN subsystem input/output process (IOP) and the SWAN concentrator is not operational. To recover from this alarm, perform Steps 2 through 5 as described for SWAN Download Error Alarm on page 1-7. SWAN Memory Error Alarm This alarm is generated when a checksum or memory error occurs. To recover from this alarm, you must reboot the SWAN kernel by power-cycling the SWAN concentrator. Hardware Error Alarm This alarm is generated when there is a problem with the battery, the power-on self-test (POST) fails, the fan in the SWAN concentrator stops rotating, or the power supply in the SWAN concentrator is not operational. IOP Line Parameters Error Alarm This alarm is generated when one or more of the attributes for a WAN subsystem device (DEVICE object) is set to an invalid or out-of-range value, or if conflicting attributes are configured. To recover from this alarm, verify that the WAN subsystem devices are configured correctly, and correct any WAN subsystem device configuration errors. Note. If you do not know the names of the WAN subsystem devices that use the SWAN concentrator, use the SCF STATUS SERVER command. For more information, see the WAN Subsystem Configuration and Management Manual. SWAN Kernel Error Alarm This alarm is generated when a problem is detected in the SWAN firmware on the SWAN concentrator. This alarm can indicate: The CLIP was not in STOPPED state when you tried to execute the OSM or TSM Test Verify action. The SWAN firmware object code file (specified by the KERNELCODE attribute) could not be downloaded to the SWAN concentrator. The SWAN firmware needs to be updated. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

31 Troubleshooting the SWAN Concentrator and WAN Subsystem Incorrect Logical Configuration Alarm To recover from this alarm: 1. Stop the CLIP and retry the Test Verify action. For more information, see Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update on page Try to clear the alarm. If the alarm persists: 1. Determine if the problem is related to Firmware and Battery Problems on page Make sure that the SWAN firmware object code file is secured with "N" read access. The SWAN firmware object code file should be located in the $SYSTEM.CSSnn subvolume. 3. Make sure that the TFTP server process is configured to use the correct location for the SWAN firmware object code file. (The TFTP server is automatically configured by the WAN manager process.) The location of download files is specified by the STARTUP attribute. (The default location is $SYSTEM.CSSnn.) 4. Run the Test Basic Online test action on the communications line interface processor (CLIP) that generated the alarm. 5. Update the SWAN firmware, if necessary. You can update SWAN firmware by using the OSM Service Connection or the TSM Service Application. For more information, see the online help within each application or the SWAN manual for your type of concentrator (for example, the SWAN 2 Concentrator Installation and Support Guide)... Note. You must stop the CLIP you are testing and shut down any active communications lines that are using the CLIP before you update its firmware using the TSM Service Application. For more information, see Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update on page Incorrect Logical Configuration Alarm This alarm is generated when the SWAN concentrator is incorrectly configured or when a WAN subsystem process or supporting process or object (such as a TCP/IP process, SUBNET, or LIF) is not operational. If you need more information about correcting a configuration problem, see Correcting SWAN Concentrator Configuration Errors on page 2-5. If you need more information about starting a required process or object, see the WAN Subsystem Configuration and Management Manual. To recover from this alarm: 1. Verify that the SWAN concentrator is configured correctly. 2. Correct any configuration errors. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

32 Troubleshooting the SWAN Concentrator and WAN Subsystem Clearing a SWAN Concentrator Alarm 3. Check the status of the required WAN subsystem processes and objects and their supporting processes. 4. Restart any processes and objects that are not in the STARTED state. Clearing a SWAN Concentrator Alarm You must manually clear a SWAN concentrator alarm. To clear an alarm: 1. Open a Physical view. 2. From the Summary menu, choose Alarms. The Alarm Summary dialog box appears, listing all current alarms on the NonStop S-series server. 3. Click the alarm you want to clear. 4. Click Delete. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

33 2 Verifying the SWAN Configuration Note. Throughout this guide when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes how to verify the SWAN concentrator configuration and correct configuration errors by using SCF commands. Topics described in this section include: Verifying a SWAN Concentrator Configuration on page 2-1 Correcting SWAN Concentrator Configuration Errors on page 2-5 Verifying a WAN Subsystem Device Configuration on page 2-9 Changing a WAN Subsystem Device Configuration on page 2-11 HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) on page 2-13 HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and J06.03 and Later RVUs) on page 2-17 Verifying a SWAN Concentrator Configuration This section summarizes the SWAN configuration requirements and recommendations, and describes the SCF commands used to determine if a SWAN concentrator is configured correctly. 1. HP recommends that you connect the SWAN concentrator to ports on two different Ethernet adapters (E4SAs, FESAs, GESAs, or G4SAs) for improved fault tolerance. To determine which Ethernet adapters a SWAN concentrator is connected to: a. Display the TCP/IP processes used by the SWAN concentrator by using the SCF INFO ADAPTER command: INFO ADAPTER $ZZWAN.#adapter-name Make a note of the names of the TCP/IP processes and host IP addresses used by the SWAN concentrator. Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator on page A-7 shows the output of this command and explains how to interpret that output. b. Display the SUBNETs configured on each identified TCP/IP process by using the SCF INFO SUBNET command: INFO SUBNET $tcpip-process-name.* INFO SUBNET $tcpip-process-name.* SWAN Concentrator and WAN Subsystem Troubleshooting Guide

34 Verifying the SWAN Configuration Verifying a SWAN Concentrator Configuration Scan the command output for the TCP/IP processes and IP addresses you found using the SCF INFO ADAPTER command. Note the logical interfaces (LIFs) associated with the host IP addresses used by the SWAN concentrator. Determining the TCP/IP Process and IP Address for a LIF on page A-8 shows the output of these commands and explains how to interpret that output. c. Determine the name of the E4SA, FESA, GESA, or G4SA on which each LIF is configured by using use the SCF INFO LIF command for each LIF you found in Step b: INFO LIF $ZZLAN.lif-name INFO LIF $ZZLAN.lif-name Determining the LIFs and PIFs for an Adapter on page A-10 shows the output of this command and explains how to interpret that output. 2. The SWAN concentrator must be configured to use the TCP/IP processes and IP addresses that are configured for the ports on the Ethernet adapters to which the SWAN concentrator is connected. You identified the Ethernet adapters and ports configured for the SWAN concentrator in Step 1, substep a and the physical location of the Ethernet adapters in Step 1, substep b. To determine if the SWAN concentrator is physically connected to the correct Ethernet adapters and ports, go to the service side of the processor or I/O enclosure and verify that the SWAN concentrator's Ethernet cables are properly connected. Note. The FESA and GESA have only one port. 3. Verify that the IP addresses associated with the preferred and alternate TCP/IP processes configured for the SWAN concentrator are on different subnets. You identified the TCP/IP processes and IP addresses configured for the SWAN concentrator in Step 1, substep a using the SCF INFO ADAPTER command. 4. Verify that the IP addresses associated with the SWAN concentrator's Ethernet path A are on the same subnet as the IP address for the preferred TCP/IP process and the IP addresses associated with the SWAN concentrator's Ethernet path B are on the same subnet as the IP address for the alternate TCP/IP process. (Note this is true only if the SWAN concentrator is not connected through a router.) Use the SCF INFO PATH command to display the IP addresses for each path on the SWAN concentrator: INFO PATH $ZZWAN.#adapter-name.* Determining the IP Addresses for a SWAN Concentrator on page A-29 shows the output of this command. 5. Verify that the IP addresses associated with the SWAN concentrator's Ethernet path A are on a different subnet than the IP addresses associated with the SWAN SWAN Concentrator and WAN Subsystem Troubleshooting Guide

35 Verifying the SWAN Configuration Verifying a SWAN Concentrator Configuration concentrator's Ethernet path B. (Note this is true only if the SWAN concentrator is not connected through a router.) You identified the IP addresses associated with the SWAN concentrator's path A and path B in Step 4, using the SCF INFO PATH command. 6. One ConMgr process is required for each processor that supports a device (DEVICE object). To check where ConMgr processes and devices are configured: a. Display the locations of all the configured ConMgr processes by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command and explains how to interpret that output. b. Display the locations of all the configured devices by using the SCF INFO DEVICE command: INFO DEVICE $ZZWAN.#* Determining the Location of a WAN Subsystem Device on page A-4 shows the output of this command and explains how to interpret that output. 7. One WANBoot process is required for each TCP/IP process that supports a SWAN concentrator and is automatically configured by the WAN messages process. Display the WANBoot processes configured on the system by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command and explains how to interpret that output. 8. Although SNMP trap multiplexer processes are not required by the SWAN concentrator, an SNMP trap multiplexer process is automatically configured by the WAN Manager Process. Use the SCF INFO PROCESS command to show the SNMP trap multiplexer processes configured on the system: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command and explains how to interpret that output. SNMPCODE is an optional attribute of the SWAN adapter and need not be specified for the SWAN 2 concentrator. 9. One SNMP trap multiplexer process is associated with one or more TCP/IP processes that support the SWAN concentrator. You can configure one SNMP trap mulitplexer process for each TCP/IP process, or you can configure one SNMP trap SWAN Concentrator and WAN Subsystem Troubleshooting Guide

36 Verifying the SWAN Configuration Verifying a SWAN Concentrator Configuration multiplexer for several TCP/IP processes. One SNMP trap multiplexer process can accommodate 6 TCP/IP processes or up to 35 TCP/IP processes (G05.00 and later RVUs). Display the TCP/IP processes associated with an SNMP trap multiplexer process by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command and explains how to interpret that output. 10. One TFTP server process is required for each TCP/IP process that supports the SWAN concentrator. A TFTP server process is automatically configured by the WAN manager process. Display the TFTP server processes configured on the system by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command and explains how to interpret that output. 11. Each TFTP server process is automatically configured to download files from the correct location. The download files accessed by a TFTP server process include the SWAN kernel object-code file and the data link control (DLC) task microcode object code files. The download file location is specified by the STARTUP attribute. The default location is $SYSTEM.CSSnn. Display the download file locations used by a TFTP server process by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command. Note. Make sure that the download files accessed by the TFTP server process are secured with N read access. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

37 Verifying the SWAN Configuration Correcting SWAN Concentrator Configuration Errors Correcting SWAN Concentrator Configuration Errors This procedure explains how to correct these common ServerNet wide area network (SWAN) configuration errors: The ServerNet wide area network (SWAN) concentrator is configured to use the wrong Ethernet adapters. The SWAN concentrator is configured to use the wrong TCP/IP processes. The wrong Internet Protocol (IP) addresses are configured for the SWAN concentrator. A ConMgr process, WANBoot process, SNMP trap multiplexer process, or TFTP server process has not been added or is not configured correctly. Correcting the Ethernet Adapter Configuration These are common causes of incorrect Ethernet adapter configurations: The SWAN concentrator is configured to use a port on one Ethernet adapter but is physically connected to another Ethernet adapter. To solve this problem, you can either reconnect the cable to the configured Ethernet adapter port or reconfigure the SWAN concentrator to use the Ethernet adapter port to which it is physically connected. The SWAN concentrator is connected to Ethernet adapters located in different processor or I/O enclosures. To solve this problem, you must select a port on an Ethernet adapter in the same processor enclosure or I/O enclosure as one of the Ethernet adapters to which the SWAN concentrator is connected, and then reconfigure the SWAN concentrator to use the new Ethernet adapter port. Note. If active communications lines are using the SWAN concentrator, you must stop them by using the SCF STOP LINE or SCF ABORT LINE command (for example, STOP LINE $LINE1). If you do not know the names of the communications lines that are using the SWAN concentrator, use the SCF STATUS SERVER command to identify them. To change an Ethernet adapter configuration for a SWAN concentrator: 1. Select a port on an Ethernet adapter that is located in the same processor enclosure or I/O enclosure as one of the Ethernet adapters to which the SWAN concentrator is currently connected. Display the E4SAs, FESAs, GESAs, and G4SAs on the system by using the SCF INFO ADAPTER command: INFO ADAPTER $ZZLAN.* Identifying the LAN Adapters on a System on page A-11 shows the output of this command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

38 Verifying the SWAN Configuration Correcting the Ethernet Adapter Configuration 2. Identify the TCP/IP process that supports the new Ethernet adapter port. Display the TCP/IP process associated with each LIF you identified in Step 1 by using the SCF INFO SUBNET command: INFO SUBNET *.* Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator on page A-7 shows the output of this command. Make a note of the TCP/IP process and IP address that support the port on the Ethernet adapter that you want to use. 3. WANMgr automatically configures and automatically reconfigures (if necessary) the SMTP trax multiplexer, TFTP server, and WANBoot processes whenever an adapter object is added or altered through a new subnet configuration. An additional optional attribute HOSTIP is provided to configure the WANBoot, TFTP, and SNMP trap multiplexer processes. The ADD command accepts the new HOSTIP attribute and the INFO command displays the configured HOSTIP for these processes. 4. Reconfigure the SWAN concentrator to use the new Ethernet adapter port. a. Stop the SWAN concentrator by using the SCF STOP ADAPTER command: STOP ADAPTER $ZZWAN.#adapter-name, SUB ALL b. Alter the appropriate TCP/IP process by using the SCF ALTER ADAPTER command. To alter the preferred TCP/IP process, type: ALTER ADAPTER $ZZWAN.#adapter, TCPIP $tcpip-process, HOSTIP ip-address To alter the alternate TCP/IP process, type: ALTER ADAPTER $ZZWAN.#adapter, ALTTCPIP $tcpip-process, ALTHOSTIP ip-address adapter is the name of the SWAN concentrator. tcpip-process is the name of the TCP/IP process that supports the new Ethernet adapter port. ip-address is the IP address associated with the TCP/IP process that supports the new Ethernet adapter port. (You identified this IP address in Step 2.) Note. For pre-g06.06 RVUs, the ALTER ADAPTER command takes effect immediately. You should issue only one ALTER ADAPTER command. This change causes the SWAN CLIP to restart. If two ALTER ADAPTER commands are issued, then you will be restarting the CLIPs again. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

39 Verifying the SWAN Configuration Correcting the TCP/IP Process Configuration c. Restart the SWAN concentrator by using the SCF START ADAPTER command: START ADAPTER $ZZWAN.#adapter, SUB ALL d. Verify that the SWAN concentrator is in the STARTED state by using the SCF STATUS ADAPTER command: STATUS ADAPTER $ZZWAN.#adapter, SUB ALL Verifying That a SWAN Concentrator is Started on page A-30 shows the output of this command. Correcting the TCP/IP Process Configuration If the SWAN concentrator is configured to use the wrong TCP/IP process, you must reconfigure the SWAN concentrator to use the correct TCP/IP process by performing these steps: Note. If active communications lines are using the SWAN concentrator, you must stop them by using the SCF STOP LINE or SCF ABORT LINE command (for example, STOP LINE $LINE1). If you do not know the names of the communications lines that are using the SWAN concentrator, use the SCF STATUS SERVER command (not the SCF STATUS ADAPTER) to identify them. 1. Reconfigure the SWAN concentrator to use the new TCP/IP process. a. Stop the SWAN concentrator by using the SCF STOP ADAPTER command: STOP ADAPTER $ZZWAN.#adapter, SUB ALL b. Alter the appropriate TCP/IP process by using the SCF ALTER ADAPTER command. To alter the preferred TCP/IP process, type: ALTER ADAPTER $ZZWAN.#adapter, TCPIP $new-preferred-tcpip-process, HOSTIP new-preferred-ip-address To alter the alternate TCP/IP process, type: ALTER ADAPTER $ZZWAN.#adapter, ALTTCPIP $new-alternate-tcpip-process, ALTHOSTIP new-alternate-ip-address Note. For pre-g06.06 RVUs, the ALTER ADAPTER command takes effect immediately. You should issue only one ALTER ADAPTER command. This change causes the SWAN CLIP to restart. If two ALTER ADAPTER commands are issued, then you will be restarting the CLIPs again. c. Restart the SWAN concentrator by using the SCF START ADAPTER command: START ADAPTER $ZZWAN.#adapter, SUB ALL SWAN Concentrator and WAN Subsystem Troubleshooting Guide

40 Verifying the SWAN Configuration Correcting the SWAN Concentrator IP Addresses d. Verify that the SWAN concentrator is in the STARTED state by using the SCF STATUS ADAPTER command: STATUS ADAPTER $ZZWAN.#adapter, SUB ALL Verifying That a SWAN Concentrator Path is Started on page A-31 shows the output of this command. Note. If the new TCP/IP process is on a different subnet than the TCP/IP process that you changed, the PATH objects for that path (A or B) must be reconfigured using new IP addresses. For more information, see Correcting SWAN Concentrator Configuration Errors on page 2-5. Correcting the SWAN Concentrator IP Addresses If the wrong IP addresses are configured for the SWAN concentrator, you must reconfigure the addresses by performing these steps for each IP address that must be changed. Note. If active communications lines are using the SWAN concentrator, you must stop them by using the SCF STOP LINE or SCF ABORT LINE command (for example, STOP LINE $LINE1). If you do not know the names of the communications lines that are using the SWAN concentrator, use the SCF STATUS SERVER command (not the SCF STATUS ADAPTER) to identify them. (Shut down only the lines running through the CLIP that is configured with the affected path.) 1. Stop the affected PATH object by using the SCF STOP PATH command: STOP PATH $ZZWAN.#adapter.clip-num.path 2. Reconfigure the PATH object with the new IP address by using the SCF ALTER PATH command: ALTER PATH $ZZWAN.#adapter.clip.path, IPADDRESS new-ip-address 3. Start the PATH object by using the SCF START PATH command: START PATH $ZZWAN.#adapter.clip.path 4. Verify that the PATH object is in the STARTED state by using the SCF STATUS PATH command: STATUS PATH $ZZWAN.#adapter.clip.path Verifying That a SWAN Concentrator Path is Started on page A-31 shows the output of this command. Note. For G06.06 Software Product Revisions (SPRs) and later RVUs, you need to execute a START SERVER command to change the IP address. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

41 Verifying the SWAN Configuration Correcting a WAN Subsystem Process Configuration Problem Correcting a WAN Subsystem Process Configuration Problem If a ConMgr process, TFTP server process, WANBoot process, or SNMP trap multiplexer process has not been added or is not configured correctly, you must add or modify it. Note. You must use the SCF STOP PROCESS command to stop a WAN subsystem process before altering it. You must use the SCF START PROCESS command to start a WAN subsystem process after adding or altering it. ConMgr Process To add a ConMgr process, see the WAN Subsystem Configuration and Management Manual. You can only modify the executable object code file name (IOPOBJECT attribute) for the ConMgr process by using the SCF ALTER PROCESS command: ALTER PROCESS $ZZWAN.#cpu-num, IOPOBJECT object-file Verifying a WAN Subsystem Device Configuration Note. If a device is a line-handler process (also referred to as a WAN subsystem IOP), the primary and backup processes should be configured in the same processors as the preferred and alternate TCP/IP processes that support the SWAN concentrator; for example, in processors 0 and 1 or in processors 2 and 3. This is required to achieve optimum performance. This section describes the SCF commands used to determine if a WAN subsystem device (DEVICE object) is configured correctly. 1. Determine the location of a WAN subsystem IOP by using the SCF INFO DEVICE command: INFO DEVICE $ZZWAN.#* Determining the Location of a WAN Subsystem Device on page A-4 shows the output of this command and explains how to interpret that output. Note. If you do not know where the preferred and alternate TCP/IP processes are configured, see Identifying the WAN Subsystem Processes and Objects on page 3-6. Note. Depending on which TCP/IP product you are using, for more information, see one of these manuals: TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IPv6 Configuration and Management Manual SWAN Concentrator and WAN Subsystem Troubleshooting Guide

42 Verifying the SWAN Configuration Verifying a WAN Subsystem Device Configuration 2. Each device has requirements imposed on its configuration by the data communications subsystem to which it belongs. Check the device-specific modifiers for the device by using the SCF INFO DEVICE command with the DETAIL option: INFO DEVICE $ZZWAN.#<device-name>, DETAIL Displaying Modifiers for a WAN Subsystem Device on page A-5 shows the output of this command. Note. You must read the Configuration and Management Manual for the data communications subsystem for product-specific requirements. 3. If the device is a line-handler process, check the current modifiers used by the communications line by using the SCF INFO LINE command using the DETAIL option. Checking current modifiers might be necessary because changes made with the subsystem-specific SCF ALTER command are not displayed by the SCF INFO DEVICE command. For example, to check the current Layer 4 attribute settings for an Expand line, use the SCF INFO LINE command with the DETAIL option: INFO LINE $LINE1, DETAIL Note. Changes made through the WAN subsystem's SCF ALTER DEVICE command are permanent (they persist through system and processor reloads). Changes made through the subsystem-specific SCF ALTER LINE commands are temporary (they do not persist through system and processor reloads). 4. Make sure that subsystem-specific objects (such as SU objects for X25AM lines) are configured correctly. Note. For the appropriate communications subsystem information about valid modifiers, see the Configuration and Management Manual. For information about configuring subsystem-specific objects, see Table 2-1 on page For information about fixing a WAN subsystem device configuration error, see Changing a WAN Subsystem Device Configuration. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

43 Verifying the SWAN Configuration Changing a WAN Subsystem Device Configuration Changing a WAN Subsystem Device Configuration If a WAN subsystem device (DEVICE object) is configured incorrectly or a WAN subsystem device requires configuration: 1. Stop the communications line (if the device is a line-handler process) and then stop the device. For specific instructions and SCF commands for your communications subsystem, see the appropriate manual (see Table 2-1 on page 2-12). 2. Modify the device using the SCF ALTER DEVICE command: ALTER DEVICE $ZZWAN.#device-name [, ADAPTER adapter ] [, CLIP clip-num ] [, HIGHPIN setting ] [, IOPOBJECT object-file ] [, LINE line-num ] [, PATH path ] [, RECSIZE RSIZE max-rec-size ] [, RESET modifier ] [, TYPE (type,subtype) ] [, modifier-keyword modifier-value ] The attributes for the SCF ALTER DEVICE command are the same as the attributes for the SCF ADD DEVICE command. For more information about the SCF ADD DEVICE command, see the WAN Subsystem Configuration and Management Manual. You can also use the SCF ALTER command provided for a specific communications subsystem (such as Expand) to make configuration changes. Keep in mind that changes made using the subsystem-specific SCF ALTER command are temporary (they do not remain across system loads) while changes made using the WAN subsystem's SCF ALTER DEVICE command are permanent and remain across system loads. 3. Restart the device and the communications line (if applicable). See the appropriate communications subsystems manual for specific instructions. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

44 Verifying the SWAN Configuration Changing a WAN Subsystem Device Configuration Table 2-1. Communications Subsystems Manuals Communications Subsystem AM3270 communications line and line-handler process ATP6100 line-handler process CP6100 communications line and line-handler process Envoy communications line and line-handler process EnvoyACP/XF communications line and line-handler process Expand communications line and line-handler process Expand network control process ($NCP) SNAX/APN or SNAX/XF communications line or linehandler process SNAX/APN or SNAX/XF service-manager process TCP/IP TR3271 communications line or line-handler process X25AM communications line or line-handler process Manual AM3270 and TR3271 Configuration and Management Manual (G06.01 and later RVUs) AM3270 and TR3271 Configuration Manual and SCF Reference Manual for AM3270 and TR3271 (RVUs before G06.01) Asynchronous Terminals and Printer Processes Configuration and Management Manual. CP6100 Configuration and Management Manual (G06.01 and later RVUs) CP6100 Configuration Manual and the SCF Reference Manual for CP6100 (RVUs before G06.01) SCF Reference Manual for Envoy or the Envoy Configuration and Management Manual EnvoyACP/XF Configuration and Management Manual Expand Configuration and Management Manual Expand Configuration and Management Manual SNAX/XF and SNAX/APN Configuration and Management Manual SNAX/XF and SNAX/APN Configuration and Management Manual TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IPv6 Configuration and Management Manual AM3270 and TR3271 Configuration and Management Manual (G06.01 and later RVUs) AM3270 and TR3271 Configuration Manual and SCF Reference Manual for AM3270 and TR3271 (RVUs before G06.01) X25AM Configuration and Management Manual SWAN Concentrator and WAN Subsystem Troubleshooting Guide

45 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) For G06.26 and earlier RVUs, HP manufacturing uses a naming convention for processes and devices that relates logical names to the physical location of devices. This information is also included in the $SYSTEM.ZSYSCONF.SCF0000 file. Table 2-2. Naming Convention for WAN Subsystem, SWAN Concentrator, Related Processes, Devices, and Adapters (G06.26 and Earlier RVUs) Process or Device Type Convention Example Disk drives $Dcabid-slot $D3217 Tape drives $Tcabid-slot $T0150 Logical interface (LIF) $ZZLAN.Lcabid-portid $ZZLAN.L018 LAN adapters (E4SA, FESA, GESA, G4SA, CCSA, or TRSA) $ZZLAN.Ecabid-slot For G4SAs, see G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) on page cabid is the two-digit number that identifies the enclosure. $ZZLAN.E0153 NonStop TCP/IP process $ZBcabid-portid $ZB018 Telnet processes $ZNcabid-portid $ZN018 Listner processes $ZPcabid-portid $ZP018 TFTP server processes $ZTFmn $ZTFAC WANBoot processes $ZWBmn $ZWBac SNMP trap multiplexer processes $ZTXmn $ZTXAC SNMP agent processes $ZTMXA, $ZTMXB, and so on $ZTMXA SWAN or SWAN 2 concentrator Sconcnum S01 cabid Description Range of Values 0n The object is in processor enclosure n n1 The object is in I/O enclosure 1 attached to processor enclosure n. n2 The object is in I/O enclosure 2 attached to processor enclosure n. n3 The object is in I/O enclosure 3 attached to processor enclosure n. 11, 21, 31, 41, 51, 61, 71, or 81 12, 22, 32, 42, 52, 62, 72, or 82 13, 23, 33, 43, 53, 63, 73, or 83 SWAN Concentrator and WAN Subsystem Troubleshooting Guide

46 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) portid is the combination of the slot number and port number mapped in this way: Slot Number Port Number portid Slot Number Port Number portid A B C D E F slot is the actual physical slot number in the enclosure: Number Description 51 to 54 A LAN adapter m n is an alphabetic value (A-Z) assigned automatically by the WAN manager process. is an alphanumeric value (A-Z or 0-9) assigned automatically by the WAN manager process. Note. The WAN manager process does not impose any restrictions on adding a PROCESS using the convention name, but when you add WAN processes, use these names to distinguish between the generated process names and the user-supplied process names. concnum is the incremental number of the SWAN concentrator. For example, the first SWAN concentrator would be 01, the second SWAN concentrator would be 02, and so on. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

47 Verifying the SWAN Configuration G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) Process or Device Type Convention Example LIF object Lcabid-module-portid $ZZLAN.L112A G4SA ADAPTER object Ggroup-module-slot A G4SA must be installed in an I/O adapter module (IOAM) enclosure. $ZZLAN.G1123 Processor multifunction (PMF) or I/O multifunction (IOMF) CRU TCP/IP process TELSERV process LISTNER process $ZZLAN.MIOEprocessorid $ZBprocessor cabid-ioam position module-portid Considerations: $ZB is reserved in the HP NonStop operating system for the NonStop TCP/IP process Every IOAM group contains two modules. Twenty G4SA ports are available for each module, and forty G4SA ports are available for each IOAM group. The TCP/IP naming convention is limited to six characters: the three initial characters are reserved ($ZB) and the final three characters must include: processor cabid-ioam position module-portid portid can be any letter from A to U; these letters can be repeated for modules 2 and 3. $ZN (plus the last three characters of the NonStop TCPIP process name) $ZP (plus the last three characters of the NonStop TCPIP process name) $ZZLAN.MIOE1 $ZB1AA $ZN1AA $ZP1AA SWAN Concentrator and WAN Subsystem Troubleshooting Guide

48 Verifying the SWAN Configuration G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) cabid is the two-digit group number that identifies the processor enclosure that is connected to the IOAM or to the IOAM enclosure that contains the G4SA; cabid is also the group number. group Description Range of Values 0n The object is in processor enclosure n n The object is in I/O enclosure n. The IO enclosure can be physically attached to as many as four processors in the inner tetrahedron, but the processor enclosure number is always 1. 11,12,13,14,15 module identifies whether the G4SA is installed in module 2 or 3 of an IOAM. A module is either 2 or 3. slot is the G4SA s physical slot number in the IOAM: Number Description 1 to 5 For the G4SA. The supported G4SA installation slots differ by system type. To determine the supported installation slots for your G4SA, see the planning guide for your system (for example, the Integrity NonStop S-Series Planning Guide) processorid specifies the processor in which the LANMON process is running. For example, #ZLM01 specifies the LANMON in processor 1. IOAM position Module is the IOAM group's position in the topology where one of the IOAMs is connected to a processor enclosure; this convention uses alphabetical letters A through J: A B C D E F G H I J 1, 2 1, 3 2, 2 2, 3 3, 2 3, 3 4, 2 4,3 5, 2 5, 3 In the above table, A is Module 2 of the IOAM connected to the first port of the processor enclosure's ServerNet Expansion Board (SEB). SWAN Concentrator and WAN Subsystem Troubleshooting Guide

49 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and portid is the combination of the slot number and port number mapped in this way for G4SA; this convention uses alphabetical letters A through U: Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Port Number A E I M R A B F J N S B C G K P T C D H L Q U D In the above table, G is the portid for Port C of the G4SA installed in slot 2 of an IOAM. concnum is the incremental number of the SWAN concentrator. For example, the first SWAN concentrator would be 01, the second SWAN concentrator would be 02, and so on. HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and J06.03 and Later RVUs) For G06.27 and later RVUs, H06.03 and later RVUs, and J06.03 and later RVUs, HP manufacturing uses a naming convention for processes and devices that relates logical names to the physical location of devices. This information is also included in the $SYSTEM.ZSYSCONF.SCF0000 file. Table 2-3. Naming Convention for the WAN Subsystem, SWAN Concentrator, and Related Processes, Devices, and Adapters (G06.27 and Later RVUs, H06.03 and Later RVUs, and J06.03 and Later RVUs) (page 1 of 2) Process or Device Type Convention Example Fibre Channel disk drive $FCnumber $FC10 Tape drives $TAPEnumber $TAPE01 G4SA adapter object Ggroup-module-slot $ZZLAN.G11123 G4SA LIF object Lgroup-module-slot-PIF $ZZLAN.L11123A TCP/IP process $ZTCnumber $ZTC0 is the first TCP6SAM process for the system TELSERV process $ZTNnumber $ZTN0 is the first Telserv process for the system SWAN Concentrator and WAN Subsystem Troubleshooting Guide

50 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and Table 2-3. Naming Convention for the WAN Subsystem, SWAN Concentrator, and Related Processes, Devices, and Adapters (G06.27 and Later RVUs, H06.03 and Later RVUs, and J06.03 and Later RVUs) (page 2 of 2) Process or Device Type Convention Example LISTNER process $LSNnumber $LSN0 is the first Listner process for the system WAN manager process Must be $ZZWAN $ZZWAN WanBoot process Automatically created by WANMGR TFTP server process Automatically created by WANMGR SNMP agent process $ZTMXA, $ZTMXB, and so on $ZTMXA SNMP trap multiplexer Automatically created by WANMGR process SWAN concentrator Sconcnum S01 group is a a two-digit number for G-series RVUs and a 3-digit number for H-series and J-series RVUs. module identifies whether the G4SA is installed in module 2 or 3 of an IOAM. A module is either 2 or 3. slot is the G4SA s physical slot number in the IOAM: Number Description 1 to 5 For the G4SA. The supported G4SA installation slots differ by system type. To determine the supported installation slots for your G4SA, see the planning guide for your system (for example, the Integrity NonStop S-Series Planning Guide) pif is the G4SA s physical interface (PIF). G4SA ports and PIFs are interchangeable terms. A PIF is part of the SLSA subsystem and represents the physical port on the G4SA. A G4SA has four PIFs: A, B, C, and D. number is the identifier for the first TCP/IP, TELSERV, or LISTNER process that is automatically configured for a corresponding LIF. HP automatically configures the first identifier for these processes; thereafter, you should configure the remaining identifiers to their corresponding LIFs. Note that the value of number used by HP for the first identifier is always 0 (that is, the processes are $ZTC0, $LSN0, and so SWAN Concentrator and WAN Subsystem Troubleshooting Guide

51 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and on). Thereafter, the second set of processes should use the value 1 (for example, $ZTC1), the third set of processes should use the value 2, and so on. m is an alphabetic value (A-Z) assigned automatically by the WAN manager process. n is an alphanumeric value (A-Z or 0-9) assigned automatically by the WAN manager process concnum is the incremental number of the SWAN concentrator. For example, the first SWAN concentrator would be 01, the second SWAN concentrator would be 02, and so on. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

52 Verifying the SWAN Configuration HP Manufacturing Naming Conventions (for G06.27 and Later RVUs and H06.03 and Later RVUs and SWAN Concentrator and WAN Subsystem Troubleshooting Guide

53 3 Verifying the WAN Subsystem Note. Throughout this guide when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes how to verify the WAN subsystem software and correct configuration errors by using SCF commands. Topics described in this section include: Verifying the WAN Subsystem Processes and Objects Starting the WAN Subsystem Processes and Objects on page 3-4 Identifying the WAN Subsystem Processes and Objects on page 3-6 Verifying the WAN Subsystem Processes and Objects This procedure describes how to verify that the required WAN subsystem processes and objects are started. It also describes how to verify that the processes and objects that support a SWAN concentrator are started (for example, E4SAs, FESAs, GESAs, G4SAs, TCP/IP processes, and so forth). If you do not know the names of the WAN subsystem processes and objects, see Identifying the WAN Subsystem Processes and Objects on page Verify that the WAN manager process is in the STARTED state by using the SCF STATUS PROCESS command for the WAN subsystem: STATUS PROCESS $ZZKRN.#ZZWAN Verifying That the WAN Manager Process is Started on page A-18 shows the output of this command. 2. Verify that the LAN manager process is in the STARTED state by using the SCF STATUS PROCESS command for the ServerNet LAN Systems Access (SLSA) subsystem: STATUS PROCESS $ZZKRN.#ZZLAN Verifying That the LAN Manager Process is Started on page A-19 shows the output of this command. 3. Verify that the preferred and alternate TCP/IP processes used by SWAN concentrators are operational. a. Verify that the preferred and alternate TCP/IP processes are in the STARTED state by using the SCF STATUS PROCESS command for the TCP/IP subsystem: STATUS PROCESS $tcpip-process Verifying That a TCP/IP Process is Started on page A-24 shows the output of this command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

54 Verifying the WAN Subsystem Verifying the WAN Subsystem Processes and Objects b. Verify that the SUBNETS associated with the LIFs used by the SWAN concentrator are in the STARTED state by using the SCF STATUS SUBNET command: STATUS SUBNET $tcpip-process.#subnet Verifying That a TCP/IP SUBNET is Started on page A-25 shows the output of this command. c. Verify that the routes on the preferred and alternate TCP/IP processes are in the STARTED state by using the SCF STATUS ROUTE command: STATUS ROUTE $<tcpip-process>.* Verifying That a TCP/IP Route is Started on page A-26 shows the output of this command. 4. Verify that the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator is connected are operational. a. Verify that the ADAPTER object for each E4SA, FESA, GESA, or G4SA is in the STARTED state by using the SCF STATUS ADAPTER command for the SLSA subsystem: STATUS ADAPTER $ZZLAN.adapter Verifying That the ADAPTER Object for a LAN Adapter is Started on page A-20 shows the output of this command. b. Verify that the ServerNet addressable controllers (SACs) for each E4SA, FESA, GESA, or G4SA are in the STARTED state by using the SCF STATUS SAC command: STATUS SAC $ZZLAN.adapter.* Verifying That the SACs for a LAN Adapter Are Started on page A-21 shows the output of this command. c. Verify that the physical interfaces (PIFs) used by the SWAN concentrator on each E4SA, FESA, GESA, or G4SA are in the STARTED state by using the SCF STATUS PIF command: STATUS PIF $ZZLAN.pif-name Verifying That a PIF is Started on page A-22 shows the output of this command. d. Verify that the logical interfaces (LIFs) used by the SWAN concentrator on each E4SA, FESA, GESA, or G4SA are in the STARTED state and that the access state is UP by using the SCF STATUS LIF command: STATUS LIF $ZZLAN.lif-name Verifying That a LIF is Started on page A-23 shows the output of this command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

55 Verifying the WAN Subsystem Verifying the WAN Subsystem Processes and Objects 5. Verify that the SNMP agent processes that support the SNMP trap multiplexer processes are in the STARTED state by using the SCF STATUS PROCESS command: STATUS PROCESS $snmp-agent-process 6. Verify that the WAN subsystem processes (ConMgr, TFTP server, SNMP trap multiplexer, and WANBoot processes) are in the STARTED state by using the SCF STATUS PROCESS command: STATUS PROCESS $ZZWAN.#* Verifying That the WAN Subsystem Processes Are Started on page A-27 shows the output of this command. 7. Verify that the SWAN concentrator ADAPTER object and its subordinate objects are in the STARTED state by using the SCF STATUS ADAPTER command with the SUB ALL option: STATUS ADAPTER $ZZWAN.#adapter, SUB ALL Verifying That a SWAN Concentrator is Started on page A-30 shows the output of this command. 8. Verify that the WAN subsystem devices (DEVICE object) are in the STARTED state by using the SCF STATUS DEVICE command: STATUS DEVICE $ZZWAN.#device-name Verifying That a WAN Subsystem Device is Started on page A-28 shows the output of this command. For information about starting a WAN subsystem process or object, see Starting the WAN Subsystem Processes and Objects on page 3-4. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

56 Verifying the WAN Subsystem Starting the WAN Subsystem Processes and Objects Starting the WAN Subsystem Processes and Objects This procedure describes how to start the required WAN subsystem processes and objects. It also describes how to start the processes and objects that support a SWAN concentrator (for example, E4SAs, FESAs, GESAs, G4SAs, TCP/IP processes, and so forth). 1. Start the WAN manager process by using the SCF START PROCESS command: START PROCESS $ZZKRN.#ZZWAN 2. Start the LAN manager process by using the SCF START PROCESS command: START PROCESS $ZZKRN.#ZZLAN 3. Start the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator is connected by using the SCF START ADAPTER command with the SUB ALL option: START ADAPTER $ZZLAN.adapter-name1, SUB ALL START ADAPTER.$ZZLAN.adapter-name2, SUB ALL Use the SCF START LIF command to start the logical interfaces (LIFs) used by the SWAN concentrator on each E4SA, FESA, GESA, or G4SA: START LIF $ZZLAN.lif-name1 START LIF $ZZLAN.lif-name2 4. Start the TCP/IP stacks associated with each LIF: a. If a preferred and/or alternate TCP/IP process no longer exists, you must recreate it using the following Tandem Advanced Command Language (TACL) command: TCPIP / NAME $tcpip-process, NOWAIT, CPU primary-cpu-num, PRI priority-num, TERM $ZHOME / backup-cpu-num Note. Always run TCP/IP as a process pair. Otherwise, the TCP/IP process loses all LAN access if the data path to the LIF changes. Note. Depending on which TCP/IP product you are using, for more information, see one of these manuals: TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IPv6 Configuration and Management Manual b. If the SUBNETS associated with the LIFs are not started, use the SCF START SUBNET command to start them: START SUBNET $pref-tcpip-process.#subnet-name START SUBNET $alt-tcpip-process.#subnet-name SWAN Concentrator and WAN Subsystem Troubleshooting Guide

57 Verifying the WAN Subsystem Starting the WAN Subsystem Processes and Objects c. If the routes on the preferred and alternate TCP/IP processes are not started, use the SCF START ROUTE command to start them: START ROUTE $pref-tcpip-process.#route-name START ROUTE $alt-tcpip-process.#route-name 5. Start the SNMP agent processes that support the SNMP trap multiplexer processes by using the SCF START PROCESS command: START PROCESS $snmp-agent-process 6. Start a WAN subsystem ConMgr process by using the SCF START PROCESS command: START PROCESS $ZZWAN.#process-name 7. Start the SWAN concentrator by using the SCF START ADAPTER command with the SUB ALL option: START ADAPTER $ZZWAN.#adapter-name, SUB ALL 8. Start a WAN subsystem device (DEVICE object) by using the SCF START DEVICE command: START DEVICE $ZZWAN.#device-name 9. Verify that each process and object is in the STARTED state by using the SCF STATUS command as described in Verifying the WAN Subsystem Processes and Objects on page 3-1. Note. The SNMP, TFTP, and WANBoot processes are automatically configured starting with the G06.13 RVU. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

58 Verifying the WAN Subsystem Identifying the WAN Subsystem Processes and Objects Identifying the WAN Subsystem Processes and Objects Figure 3-1 on page 3-6 illustrates the WAN subsystem processes and objects, including the WAN subsystem input/output processes (IOPs), that comprise a SWAN concentrator configuration. Note. A SWAN 2 concentrator has 6 CLIPs. Figure 3-1. WAN Subsystem Process and Objects ConMgr WANMgr (P) WANMgr (B) ConMgr WAN IOP SNMP Agent WAN IOP Trap Mode WANBoot TFTP Server TFTP Server WANBoot TCP/IP TCP/IP LAN Adapter LAN Adapter LIF SAC LIF SAC PIF PIF Ethernet Path A SWAN CLIP 1 CLIP 2 CLIP 3 Ethernet Path B VST999.vsd Determining the Name of the SWAN Concentrator Used by a WAN Subsystem IOP or the Names of the WAN Subsystem IOPs Configured to Use a SWAN Concentrator Determine the name of the SWAN concentrator used by a specific WAN subsystem IOP by using the SCF INFO DEVICE command: INFO DEVICE $ZZWAN.#device-name SWAN Concentrator and WAN Subsystem Troubleshooting Guide

59 Verifying the WAN Subsystem Determining the TCP/IP Processes and IP Addresses That Support a SWAN Concentrator Determining the SWAN Concentrator Used by a Communications Line on page A-2 shows the output of this command and explains how to interpret it. Determine the names the WAN subsystem IOPs configured to use a specific SWAN concentrator by using the SCF STATUS ADAPTER command: STATUS ADAPTER $ZZWAN.#adapter-name, SUB ALL Determining the WAN Subsystem IOPs That Use a SWAN Concentrator on page A-3 shows the output of this command and explains how to interpret it. Determining the TCP/IP Processes and IP Addresses That Support a SWAN Concentrator Determine the TCP/IP processes and the IP addresses that support a SWAN concentrator by using the SCF INFO ADAPTER command: INFO ADAPTER $ZZWAN.#adapter-name Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator on page A-7 shows the output of this command and explains how to interpret it. Determine the processors where the primary and backup TCP/IP processes are running by using the SCF STATUS PROCESS command: STATUS PROCESS $tcpip-process Determining the LIFs Associated With the TCP/IP Processes and IP Addresses That Support a SWAN Concentrator Determine the LIFs associated with the TCP/IP processes and IP addresses that support the SWAN concentrator by using the SCF INFO SUBNET command for the preferred and alternate TCP/IP processes: INFO SUBNET $pref-tcpip-process.* INFO SUBNET $alt-tcpip-process.* Scan each SCF INFO SUBNET display for the preferred and alternate IP addresses for the SWAN concentrator. The LIF name associated with an IP address is shown in the Devicename column of the SCF INFO SUBNET display. Determining the TCP/IP Process and IP Address for a LIF on page A-8 shows the output of the SCF INFO SUBNET command. If you do not know the names of the TCP/IP processes and the IP addresses that support the SWAN concentrator, use the SCF INFO ADAPTER command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

60 Verifying the WAN Subsystem Determining the E4SAs, FESAs, GESAs, or G4SAs to Which a SWAN Concentrator is Connected Determining the E4SAs, FESAs, GESAs, or G4SAs to Which a SWAN Concentrator is Connected Determine the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator is connected by using the SCF INFO LIF command for each LIF associated with the TCP/IP processes that support the SWAN concentrator: INFO LIF $ZZLAN.lif-name INFO LIF $ZZLAN.lif-name Determining the LIFs and PIFs for an Adapter on page A-10 shows the output of this command. Note. If you do not know the names of the TCP/IP processes that support the SWAN concentrator, use the SCF INFO ADAPTER command. If you do not know the names of the LIFs associated with the TCP/IP processes that support the SWAN concentrator, use the SCF INFO SUBNET command. Determining the WANMgr Processes The primary WANMgr process is always configured in processor 0 and the backup WANMgr process is always configured in processor 1. Determining the ConMgr, SNMP Trap Multiplexer, TFTP Server, WANBoot, and SNMP Agent Processes That Support a SWAN Concentrator Determine the names of the ConMgr processes, SNMP trap multiplexer processes, TFTP server processes, WANBoot processes, and SNMP agent processes that support the SWAN concentrators by using the SCF INFO PROCESS command: INFO PROCESS $ZZWAN.#* Scan the output for the TCP/IP processes that support your SWAN concentrator. The SNMP trap multiplexer, TFTP server, and WANBoot processes associated with these TCP/IP processes are the processes that support that SWAN concentrator. Displaying Information for a WAN Subsystem Process on page A-14 shows the output of this command. Note. If you do not know the names of the TCP/IP processes that support the SWAN concentrator, use the SCF INFO ADAPTER command. Determining the Names of the SWAN Concentrators Configured on a System Determine the names of the SWAN concentrators configured on a system by using the SCF NAMES ADAPTER command: NAMES ADAPTER $ZZWAN.#* SWAN Concentrator and WAN Subsystem Troubleshooting Guide

61 4 Verifying the SWAN Hardware Note. Throughout this guide when a distinction between a SWAN concentrator (T3880) and a SWAN 2 concentrator (T3881) is not required, SWAN concentrator is used as a collective term. This section describes how to verify the SWAN concentrator hardware and fix SWAN concentrator hardware problems. Topics described in this section include: Verifying the SWAN Concentrator Hardware Correcting SWAN Concentrator Hardware Problems on page 4-3 SWAN Concentrator Cabling on page 4-10 Verifying SWAN Concentrator Cabling on page 4-11 Common Cabling Problems on page 4-11 Correcting SWAN Concentrator Cabling on page 4-13 Verifying the SWAN Concentrator Track-ID on page 4-13 Verifying LAN Hardware for a SWAN Concentrator on page 4-15 Correcting a LAN Hardware Problem for a SWAN Concentrator on page 4-15 SWAN Concentrator LEDs on page 4-15 Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update on page 4-19 SWAN Concentrator and WAN Subsystem Troubleshooting Guide

62 Verifying the SWAN Hardware Verifying the SWAN Concentrator Hardware Verifying the SWAN Concentrator Hardware The OSM Service Connection or TSM Service Application provide the following test actions for a SWAN communications line interface processor (CLIP): Test Action Test Primary Path Access Test Backup Path Access Test Full Path Access Test Basic Online Test Verify Description Tests two-way access to the primary path to a selected CLIP. If you suspect a problem in the primary path to a CLIP, use this test action. Tests two-way access to the backup path to a selected CLIP. If you suspect a problem with the backup path to the CLIP, use this test action. Tests two-way access to a selected CLIP using both the primary and backup paths (equivalent to running both the Test Primary Path Access and Test Backup Path Access test actions). If you suspect a problem in both paths to CLIP, or if you do not know which path might have a problem, use this test action. If this test action fails, use the Test Basic Online test action. Runs an online test to determine if a selected CLIP is functional and tests two-way access to both the primary and backup paths to a selected CLIP (equivalent to the Test Full Path Access test action but also tests the hardware registers). If this test action fails, use the Test Verify test action. Runs the power-on self-test (POST) for a selected CLIP. During POST, status light-emitting diodes (LEDs) light. These status LEDs and their functions are described in Table 4-1 on page 4-16 and Table 4-2 on page You must stop the CLIP you are testing and shut down any active communications lines using the CLIP before executing the Test Verify test action. For more information, see Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update on page How to Run a Test Action The OSM Service Connection is similar to the TSM Service Application, in that you can locate and select the CLIP you want to test and launch the appropriate action from the Actions dialog box. An enhanced feature in OSM is the Multi-Resource Actions dialog box. It enables you to select any or all resources of the same type (such as SWAN CLIPs) and perform an action on them simultaneously. For more information, see the OSM Service Connection online help. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

63 Verifying the SWAN Hardware Correcting SWAN Concentrator Hardware Problems Correcting SWAN Concentrator Hardware Problems Firmware and Battery Problems Error IDs related to OSM or TSM Test Action Failure Firmware and Battery Problems There are new updates for T7954 AAP firmware (FW) update and SWAN 2 battery replacement procedures. T7954 AAP Firmware Update Instructions: When updating T7954 AAN or earlier firmware to T7954 AAP or later firmware, refresh the SWAN 2 battery status with one of the following actions: System running OSM Issue OSM Rediscover actions on all SWAN-2 batteries Restart $ZCMOM for the system running OSM System running TSM Stop and restart proc $zzkrn.#tsm-srm In the next 24 hours, if any battery reports a failure event, it is a bad battery, and must be replaced. For the battery replacement procedure, see the SWAN 2 Installation and Support Guide. SWAN 2 Battery Replacement Instructions After replacing a battery, refresh the battery status of the new battery and clear the hardware alarm of the failed battery with one of the following actions: System running OSM Issue OSM Rediscover actions on all SWAN-2 batteries Restart $ZCMOM for the system running OSM System running TSM Stop and restart proc $zzkrn.#tsm-srm In the next 24 hours, if any battery reports a failure event, it is a dead-on-arrival (DOA) battery and must be replaced. For the battery replacement procedure, see the SWAN 2 Installation and Support Guide. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

64 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure Error IDs related to OSM or TSM Test Action Failure If an OSM or TSM test action fails, an error ID is returned. To display a brief explanation of an error, from the Actions dialog box, click Show detail. If you want more detailed information about how to recover from an specific error, see the error ID you are interested in from the table below: Error ID This error indicates conditional success. For example, for the Test Full Path Access test action, this error is returned if the backup path is functional but the primary path is not. Error ID This error is returned when a serious internal error has occurred in the WAN subsystem software. There is no recovery for this error. Error ID This error is returned if there is a problem in the Ethernet 4 ServerNet adapters (E4SAs), Fast Ethernet ServerNet adapters (FESAs), Gigabit Ethernet ServerNet adapters (GESAs), or Gigabit Ethernet 4-port ServerNet adapters (G4SAs) to which the SWAN concentrator is connected.this error is also returned if a problem exists in the preferred and/or alternate TCP/IP processes that support the SWAN concentrator. To recover from this error: 1. Verify that the E4SAs, FESAs, GESAs, or G4SAs to which the SWAN concentrator is connected are operational. a. Verify that the ADAPTER object for each E4SA, FESA, GESA, or G4SA is in the STARTED state by using the SCF STATUS ADAPTER command for the SLSA subsystem: STATUS ADAPTER $ZZLAN.adapter-name1 STATUS ADAPTER.$ZZLAN.adapter-name2 Verifying That the ADAPTER Object for a LAN Adapter is Started on page A-20 shows the output of this command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

65 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure b. Verify that the ServerNet addressable controllers (SACs) for each E4SA, FESA, GESA, or G4SA are in the STARTED state by using the SCF STATUS SAC command: STATUS SAC $ZZLAN.adapter-name1.* STATUS SAC $ZZLAN.adapter-name2.* Verifying That the SACs for a LAN Adapter Are Started on page A-21 shows the output of this command. c. Verify that the physical interfaces (PIFs) used by the SWAN concentrator on each E4SA, FESA, GESA, or G4SA are in the STARTED state by using the SCF STATUS PIF command: STATUS PIF $ZZLAN.adapter-name1.pif-name1 STATUS PIF $ZZLAN.adapter-name2.pif-name2 Verifying That a PIF is Started on page A-22 shows the output of this command. d. Verify that the logical interfaces (LIFs) used by the SWAN concentrator on each E4SA, FESA, GESA, or G4SA are in the STARTED state and that the access state is UP by using the SCF STATUS LIF command: STATUS LIF $ZZLAN.lif-name1 STATUS LIF $ZZLAN.lif-name2 Verifying That a LIF is Started on page A-23 shows the output of this command. 2. Restart any E4SA, FESA, GESA, or G4SA objects that are not in the STARTED state. a. If an ADAPTER object is not in the STARTED state, use the SCF START ADAPTER command with the SUB ALL option. This command starts the subordinate SAC and PIF objects. START ADAPTER $ZZLAN.adapter-name, SUB ALL b. If one or more of the LIF objects are not in the STARTED state, use the SCF START LIF command: START LIF $ZZLAN.lif-name 3. Verify that the TCP/IP stacks that support the SWAN concentrator are operational. a. Verify that the preferred and alternate TCP/IP processes are in the STARTED state by using the SCF STATUS PROCESS command: STATUS PROCESS $pref-tcpip-process STATUS PROCESS $alt-tcpip-process Verifying That a TCP/IP Process is Started on page A-24 shows the output of this command. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

66 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure b. Verify that the SUBNETS on the preferred and alternate TCP/IP processes that are associated with the LIFs are in the STARTED state by using the SCF STATUS SUBNET command: STATUS SUBNET $pref-tcpip-process.#subnet-name STATUS SUBNET $alt-tcpip-process.#subnet-name Verifying That a TCP/IP SUBNET is Started on page A-25 shows the output of this command. c. Verify that the routes on the preferred and alternate TCP/IP processes are in the STARTED state by using the SCF STATUS ROUTE command: STATUS ROUTE $pref-tcpip-process.#route-name STATUS ROUTE $alt-tcpip-process.#route-name Verifying That a TCP/IP Route is Started on page A-26 shows the output of this command. 4. Restart any TCP/IP processes or objects that are not in the STARTED state. a. If a TCP/IP process no longer exists, you must recreate it by using this TACL command: TCPIP / NAME $tcpip-process, NOWAIT, CPU primary-cpu-num, PRI priority-num, TERM $ZHOME / backup-cpu-num Note. Always run TCP/IP as a process pair. Otherwise, the TCP/IP process loses all LAN access if the data path to the LIF changes. b. If a SUBNET is not in the started state, use the SCF START SUBNET command: START SUBNET $tcpip-process.#subnet-name c. If a route is not in the started state, use the SCF START ROUTE command: START ROUTE $tcpip-process.#route-name Error ID This error is returned when you run the OSM or TSM Test Verify action and the CLIP is not in a STOPPED state. To recover from this error, stop the CLIP then retry the test action. For more information, see Preparing a SWAN CLIP for the OSM or TSM Test Verify Test Action or Firmware Update on page SWAN Concentrator and WAN Subsystem Troubleshooting Guide

67 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure Error ID This error is returned if a problem exists in the adapters to which the SWAN concentrator is connected. This error is also returned if a problem exists in the preferred and/or alternate TCP/IP processes that support the SWAN concentrator or if the SWAN concentrator is configured incorrectly. To recover from this error: Perform the recovery steps described for Error ID Verify that the SWAN concentrator is configured correctly, and correct any SWAN concentrator configuration errors. Retry the test action. Error ID This error is returned when the specified firmware object code file does not exist. To recover from this error, make sure that the required firmware object code file exists, then retry the Firmware Update action. Error ID This error is returned when the VPROC for the specified firmware object code file could not be obtained. To recover from this error, make sure that the correct firmware object code file is specified, then retry the Firmware Update action. Error ID This error is returned if the firmware object code file attribute (KERNELCODE) for the SWAN concentrator is not configured. To recover from this error, you must alter the KERNELCODE attribute, then retry the Firmware Update action. To alter the firmware object code file attribute for a SWAN concentrator: 1. Stop the active customer applications that use the communications lines configured for the SWAN concentrator. 2. Stop active communications lines that are configured for the SWAN concentrator: STOP LINE $LINE1 If you do not know the names of the communications lines that are configured for the SWAN concentrator, use the SCF STATUS ADAPTER command with the SUB ALL option to identify them: STATUS ADAPTER $ZZWAN.#adapter-name, SUB ALL SWAN Concentrator and WAN Subsystem Troubleshooting Guide

68 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure Determining the WAN Subsystem IOPs That Use a SWAN Concentrator on page A-3 shows the output of this command and explains how to interpret it. Note. Numerous Event Message Service (EMS) events will be generated if communications lines are not stopped before the CLIP is stopped. 3. Stop the ADAPTER object and all of its subordinate objects by using the SCF STOP ADAPTER command with the SUB ALL option: STOP ADAPTER $ZZWAN.#conc-name, SUB ALL 4. Alter the KERNELCODE attribute to specify the correct firmware object code file by using the SCF ALTER ADAPTER command: ALTER ADAPTER $ZZWAN.#conc-name, KERNELCODE $SYSTEM.CSSnn.firmware-file The KERNELCODE file is C7953P00 for the SWAN concentrator (T3880) and C7953Q00 for the SWAN 2 concentrator (T3881). If you are using the 6763 Common Communications ServerNet adapter (commonly known as SS7), the KERNELCODE file is C0099P00. For all other protocols, the firmware file name is C7953P Restart the ADAPTER object and all of its subordinate objects by using the SCF START ADAPTER command with the SUB ALL option: START ADAPTER $ZZWAN.#conc-name, SUB ALL 6. If you stopped communications lines in Step 2, restart them. START LINE $LINE1 7. Resume customer applications that use the communications lines configured for the SWAN concentrator. Error ID This error is returned if a previously initiated test action is still running in the selected CLIP. To recover from this error, wait until the previously initiated test action is finished, then retry the test action. Error ID This error is returned if the firmware object code file attribute (KERNELCODE) for the SWAN concentrator is invalid. The recovery for this error is the same as for Error ID Error ID This error is returned if the selected CLIP is inaccessible. To recover from this error, verify that the SWAN concentrator is configured properly, correct any configuration errors, then retry the test action. For more information, see Verifying a SWAN Concentrator Configuration on page 2-1. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

69 Verifying the SWAN Hardware Error IDs related to OSM or TSM Test Action Failure Error ID This error is returned if the test action could not be downloaded to the selected CLIP. This problem may occur because another test action is currently running in the CLIP. To recover from this error, wait until the previously initiated test action is finished, then retry the test action. Error ID This error is returned if the test action could not be performed because its associated DIAG task file could not be found. To recover from this error, make sure that the file D8155P00 or D8155Q00 (for the SWAN 2 concentrator) exists in the current $SYSTEM.CSSnn subvolume, then retry the test action. Error ID This error is returned if the primary path to the selected CLIP is down. To recover from this error, verify that the primary path to the CLIP is configured properly, correct any configuration errors, then retry the test action. For more information, see Verifying a SWAN Concentrator Configuration on page 2-1. Error ID This error is returned if the backup path to the selected CLIP is down. To recover from this error, verify that the backup path to the CLIP is configured properly, correct any configuration errors, then retry the test action. For more information, see Verifying a SWAN Concentrator Configuration on page 2-1. Error ID This error is returned if both the primary and backup paths to the selected CLIP are down. To recover from this error, verify that the SWAN concentrator is configured properly, correct any configuration errors, and then retry the test action. For more information, see Verifying a SWAN Concentrator Configuration on page 2-1. Error ID This error is returned if a hardware test on the selected CLIP failed because of a CLIP hardware fault. There is no recovery for this error. You must replace the SWAN concentrator. Error ID This error is returned if at least one of the power-on self-tests (POSTs) failed on the selected CLIP because of a CLIP hardware fault. For a SWAN concentrator (T3880) there is no recovery for this error; you must replace the SWAN concentrator. For a SWAN 2 concentrator (T3881), you must replace the CLIP (For information about the SWAN Concentrator and WAN Subsystem Troubleshooting Guide

70 Verifying the SWAN Hardware SWAN Concentrator Cabling CLIP replacement procedure, see the SWAN 2 Concentrator Installation and Support Guide). Error ID This error is returned if the OSM Service Connection or TSM Service Application could not obtain power-on self-test (POST) results because the selected CLIP could not be accessed. For a SWAN concentrator (T3880) there is no recovery for this error; you must replace the SWAN concentrator. For a SWAN 2 concentrator (T3881), you must replace the CLIP (For information about the CLIP replacement procedure, see the SWAN 2 Concentrator Installation and Support Guide). SWAN Concentrator Cabling The front panel of the ServerNet wide area network (SWAN) concentrator contains two RJ-45, 10 Base-T twisted-pair Ethernet ports, which connect the SWAN concentrator to the Integrity NonStop NS-series or NonStop S-series server. The back panel of the SWAN 2 concentrator contains two RJ-45, 10/100 Base-T twisted-pair Ethernet ports, which connect the SWAN 2 concentrator to the Integrity NonStop NS-series or NonStop S-series server. Ethernet connections to the server can be made: Directly to Ethernet 4 ServerNet adapters (E4SAs), Fast Ethernet ServerNet adapters (FESAs), Gigabit Ethernet ServerNet adapters (GESAs), and Gigabit Ethernet 4-port ServerNet adapters (G4SAs) using a customer-supplied crossover cable. Indirectly through customer-supplied, industry-standard Ethernet switches, hubs, or routers. For more information, see the SWAN Concentrator Installation and Support Guide or the SWAN 2 Concentrator Installation and Support Guide. For maximum fault-tolerance, HP recommends that you connect a SWAN concentrator directly to an E4SA, FESA, GESA, or G4SA rather than through an Ethernet hub. If you use an Ethernet hub, you must carefully monitor the state of the hub. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

71 Verifying the SWAN Hardware Common Cabling Problems Common Cabling Problems When the Ethernet cables are reversed or are connected to the same Ethernet segment, Event Message 1509 is generated: WANBoot: BOOTP received on wrong PATH for TRACKID configuration-track-id, CLIP clip-number, IP Address ip-address, PATH path-name Reversed Cables The SWAN concentrator has two distinct paths labeled path A and path B. Path A corresponds to the preferred TCP/IP process, SUBNET, and logical interface (LIF) and path B corresponds to the alternate TCP/IP process, SUBNET, and LIF. The cable connected to path A must be connected to the E4SA, FESA, GESA, or G4SA port associated with the preferred TCP/IP process, SUBNET, and LIF; the cable connected to path B must be connected to the E4SA, FESA, GESA, or G4SA port associated with the alternate TCP/IP process, SUBNET, and LIF. The cables cannot be reversed. For more information, see Verifying SWAN Concentrator Cabling and Correcting SWAN Concentrator Cabling. Cables Connected to the Same Ethernet Segment The Internet Protocol (IP) addresses associated with the preferred and alternate TCP/IP processes configured for the SWAN concentrator must be on different subnets. Therefore, the cables connected to path A and path B must be connected to different Ethernet segments. (Each physical segment of a local area network (LAN) is defined as a different subnet.) For more information, see Verifying SWAN Concentrator Cabling and Correcting SWAN Concentrator Cabling. Verifying SWAN Concentrator Cabling 1. Make sure that the Ethernet cables connected to path A and path B on the SWAN concentrator are connected to the correct ports on the correct Ethernet adapters. a. Determine the preferred and alternate TCP/IP processes and the IP addresses that support the SWAN concentrator by using the SCF INFO ADAPTER command: INFO ADAPTER $ZZWAN.#adapter-name Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator on page A-7 shows the output of this command and explains how to interpret it. b. Determine the LIFs associated with the TCP/IP processes and IP addresses that support the SWAN concentrator by using the SCF INFO SUBNET command for each TCP/IP process you found using the SCF INFO ADAPTER command: INFO SUBNET $pref-tcpip-process.* INFO SUBNET $alt-tcpip-process.* SWAN Concentrator and WAN Subsystem Troubleshooting Guide

72 Verifying the SWAN Hardware Verifying SWAN Concentrator Cabling Determining the TCP/IP Process and IP Address for a LIF on page A-8 shows the output of these commands. c. Determine the E4SA, FESA, GESA, or G4SA ports configured for the SWAN concentrator by using the SCF INFO LIF command for each LIF you found using the SCF INFO SUBNET command: INFO LIF $ZZLAN.lif-name INFO LIF $ZZLAN.lif-name Determining the LIFs and PIFs for an Adapter on page A-10 shows the output of this command. d. Examine the cable connected to path A on the SWAN concentrator and make sure that it is connected to the E4SA, FESA, GESA, or G4SA port associated with the preferred TCP/IP process. e. Examine the cable connected to path B on the SWAN concentrator and make sure that it is connected to the E4SA, FESA, GESA, or G4SA port associated with the alternate TCP/IP process. 2. Make sure that the cables connected to path A and path B on the SWAN concentrator are connected to different Ethernet segments. a. Determine the preferred and alternate TCP/IP processes and the IP addresses that support the SWAN concentrator by using the SCF INFO ADAPTER command: INFO ADAPTER $ZZWAN.#adapter-name Determining the TCP/IP Processes and IP Addresses for a SWAN Concentrator on page A-7 shows the output of this command and explains how to interpret it. b. Examine the preferred and alternate IP addresses (HOSTIP Address and ALTHOSTIP Address fields of the SCF INFO ADAPTER display). The IP addresses must be on different subnets. c. Examine the cables connected to path A and path B on the SWAN concentrator and make sure that they are connected to the correct Ethernet segments. 3. Determine if the SWAN concentrator's Ethernet cables are operational. Finding a bad cable involves standard network-troubleshooting techniques. SWAN Concentrator and WAN Subsystem Troubleshooting Guide

73 Verifying the SWAN Hardware Correcting SWAN Concentrator Cabling Correcting SWAN Concentrator Cabling If the Ethernet cables are reversed, switch the cables so that they are connected to the correct ports on the SWAN concentrator. If an Ethernet cable is connected to the wrong E4SA, FESA, GESA, or G4SA port, connect the cable to the configured E4SA, FESA, GESA, or G4SA port or reconfigure the SWAN concentrator to use the E4SA, FESA, GESA, or G4SA port to which it is connected. If both cables are connected to the same Ethernet segment, connect one of the cables to a different Ethernet segment. You must also reconfigure the SWAN concentrator to use a TCP/IP process and IP address on the new Ethernet segment and reconfigure the IP addresses for the corresponding SWAN concentrator path. If a cable is not operational, replace it with a good cable. Verifying the SWAN Concentrator Track-ID The nonshaded area of Figure 4-1 shows the location of the configuration track-id on the rear panel of a SWAN concentrator. Figure 4-2 on page 4-14 shows the location of the configuration track-id on the rear panel of a SWAN 2 concentrator. Figure 4-1. SWAN Concentrator Label, Configuration Track-ID PATH A B A B A B MODEL T/3880 ASM: XXX-XX XXXXXX VAC, 50/60 HZ, IA HI-POT THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES. OPERATION IS SUBJECT TO THE FOLLOWING TWO CONDITIONS: 1. THIS DEVICE MAY NOT CAUSE HARMFUL INTERFERENCE. 2. THIS DEVICE MUST ACCEPT ANY INTERFERENCE THAT MAY CAUSE UNDESIRED OPERATION. THIS CLASS A DIGITAL APPARATUS MEETS ALL REQUIREMENTS OF THE CANADIAN INTERFERENCE-CAUSING EQUIPMENT REGULATIONS. CET APPAREIL NUMERIQUE DE LA CLASSE A RESPECTE TOUTES LES EXIGENCES DU REGLEMENT SUR LE MATERIEL BROUILLEUR DE CANADA. PWA:106523XXX-XX TC XXXXXX LA: 08008EXXXXXX LA: 08008EXXXXXX LA: 08008EXXXXXX LA: 08008EXXXXXX LA: 08008EXXXXXX LA: 08008EXXXXXX CLIP Configuration Track- ID VST868.vsd To display the configuration track-id configured for your SWAN concentrator, use the SCF INFO ADAPTER command: INFO ADAPTER $ZZWAN.#conc_name, TRACKID conc_name is the name of the SWAN concentrator (ADAPTER object). SWAN Concentrator and WAN Subsystem Troubleshooting Guide

74 Verifying the SWAN Hardware Verifying the SWAN Concentrator Track-ID If the configuration track-id that is displayed by the SCF INFO ADAPTER command does not match the configuration track-id that is printed the rear panel of your SWAN concentrator, you must alter it. Figure 4-2. SWAN 2 Concentrator Label MAC Address Track ID VST996.vsd Altering the Configured Configuration Track-ID Before you can alter the configuration track-id, you must first stop the SWAN concentrator and all of its subordinate objects (SERVER, PATH, and TASK) using the SCF STOP ADAPTER command: STOP ADAPTER $ZZWAN.#conc_name, SUB ALL Use the SCF ALTER ADAPTER command to alter the configuration track-id: ALTER ADAPTER $ZZWAN.#conc_name, TRACKID "config-track-id" The configuration track-id is case sensitive. If you specify the value incorrectly, you will not be able to use the SWAN concentrator. Use the SCF START ADAPTER command to restart the SWAN concentrator and all of its subordinate objects (SERVER, PATH, and TASK) after you have altered the configuration track-id: START ADAPTER $ZZWAN.#conc_name, SUB ALL 4-14