ServerNet Cluster Supplement for HP Integrity NonStop NS-Series Servers

Transcription

1 ServerNet Cluster Supplement for HP Integrity NonStop NS-Series Servers Abstract This supplement describes adding, configuring, and managing an HP Integrity NonStop NS-series server in an HP NonStop ServerNet Cluster. Product Version NA Supported Release Version Updates (RVUs) This publication supports H06.08 and all subsequent H-series RVUs until otherwise indicated by its replacement publication. Part Number Published August 2009

2 Document History Part Number Product Version Published NA July NA February NA November NA August 2009

3 Contents 1. Table of Contents What s New in This Manual iii Manual Information iii New and Changed Information About This Supplement v Where to Get More Information Notation Conventions v 1. iii v Requirements for Clustering 1-2 Software Requirements 1-2 Hardware Requirements 1-3 OSM Support for NonStop NS-Series Nodes in a ServerNet Cluster 1-5 Preparing Integrity NonStop NS16000 System 1-5 Preparing Integrity NonStop NS14000 System with IOAM Enclosure 1-7 Preparing Integrity NonStop NS14000 System with VIO Enclosures 1-8 SCF Displays for NonStop NS-Series Nodes in a ServerNet Cluster 1-10 INFO CONNECTION Command (6780 Switch) 1-10 INFO CONNECTION Command Display (6770 Switch) 1-13 STATUS CONNECTION Command (6780 Switch) 1-14 STATUS CONNECTION Command (6770 Switch) 1-17 Examples Tables Example 1-1. INFO CONNECTION Display for a 6780 Switch (NS16000 system) 1-11 Example 1-2. INFO CONNECTION Display for a 6780 Switch (NS14000 system) 1-12 Example 1-3. INFO CONNECTION Display for a 6770 Switch 1-13 Example 1-4. STATUS CONNECTION Display for a 6780 Switch 1-16 Example 1-5. STATUS CONNECTION Display for 6770 Switches 1-18 Table 1-1. Minimum Software Requirements for Integrity NonStop NS Table 1-2. Integrity NonStop NS-Series Node Hardware Requirements 1-4 Table 1-3. INFO CONNECTION Attributes for Integrity NonStop NS-series Nodes 1-10 Table 1-4. INFO CONNECTION Attributes for Integrity NonStop NS-series Nodes 1-13 i

4 Contents Table 1-5. Table 1-6. STATUS CONNECTION Attributes for Integrity NonStop NS-Series Nodes 1-14 STATUS CONNECTION Attributes for Integrity NonStop NS-Series Nodes 1-17 ii

5 What s New in This Manual Manual Information Abstract ServerNet Cluster Supplement for HP Integrity NonStop NS-Series Servers This supplement describes adding, configuring, and managing an HP Integrity NonStop NS-series server in an HP NonStop ServerNet Cluster. Product Version NA Supported Release Version Updates (RVUs) This publication supports H06.08 and all subsequent H-series RVUs until otherwise indicated by its replacement publication. Part Number Published August 2009 Document History Part Number Product Version Published NA July NA February NA November NA August 2009 New and Changed Information For H06.14, this supplement was updated to include HP Integrity NonStop NS16200 systems as part of the NonStop NS16000 series and HP Integrity NonStop NS14200 series systems as part of the NonStop NS14000 series. It was also updated to provide BladeCluster Solution information for NonStop NS16000 series systems and NonStop NS14000 series systems. Recent Change History For H06.08, this supplement was updated to provide ServerNet cluster details for HP Integrity NonStop NS14000 systems consisting of VIO enclosures instead of an IOAM enclosure. At H06.05, this supplement was updated to include support for HP Integrity NonStop NS14000 systems (which have no processor switches). iii

6 What s New in This Manual Recent Change History iv

7 About This Supplement The information in this manual is intended supplement the existing ServerNet cluster manual set, providing details specific to HP Integrity NonStop NS-series systems. Where to Get More Information For general information on ServerNet clusters, refer to: 6770 Switch: ServerNet Cluster Manual 6780 Switch: ServerNet Cluster 6780 Planning and Installation Guide and ServerNet Cluster 6780 Operations Guide BladeCluster Solution: BladeCluster Solution 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 This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type 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. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c v

8 About This Supplement 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 can 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 can 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 typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name vi

9 About This Supplement Change Bar Notation Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type 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, no spaces are 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 ] Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. 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 COBOL 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. vii

10 About This Supplement Change Bar Notation viii

11 1 Integrity NonStop NS-series Server Supplement Except for the differences noted in this supplement, installing and managing an HP Integrity NonStop NS-series node in a 6770 or 6780 ServerNet cluster is the same as described in these manuals: 6770 Switch: ServerNet Cluster Manual 6780 Switch: ServerNet Cluster 6780 Planning and Installation Guide and ServerNet Cluster 6780 Operations Guide To install and manage an HP Integrity NonStop NS-series node in a BladeCluster ServerNet cluster, also refer to the BladeCluster Solution Manual. Requirements for Clustering on page 1-3 Software Requirements on page 1-3 Hardware Requirements on page 1-5 OSM Support for NonStop NS-Series Nodes in a ServerNet Cluster on page 1-6 Preparing Integrity NonStop NS16000 Series System on page 1-6 Checking the Cluster PICs on page 1-6 Replacing the Cluster PIC in a Processor Switch on page 1-7 Adding a Cluster PIC on page 1-7 Adding the Node to a ServerNet Cluster on page 1-7 Preparing Integrity NonStop NS14000 System with IOAM Enclosure on page 1-8 Checking the ServerNet Switch Boards on page 1-8 Replacing a ServerNet Switch Board on page 1-8 Adding a ServerNet Switch Board on page 1-9 Adding the Node to a ServerNet Cluster on page 1-9 Preparing Integrity NonStop NS14000 Series System with VIO Enclosures on page 1-9 Checking the Optical Extender PICs on page 1-9 Replacing an Optical Extender PIC on page 1-10 Adding an Optical Extender PIC on page 1-10 Adding the Node to a ServerNet Cluster on page 1-10 SCF Displays for NonStop NS-Series Nodes in a ServerNet Cluster on page 1-11 INFO CONNECTION Command (6780 Switch) on page

12 INFO CONNECTION Command Display (6770 Switch) on page 1-14 STATUS CONNECTION Command (6780 Switch) on page 1-15 STATUS CONNECTION Command (6770 Switch) on page

13 Requirements for Clustering Requirements for Clustering Configuring an Integrity NonStop NS-series system for inclusion in a ServerNet cluster requires a minimum level of software, hardware, and firmware. These requirements, as well as how to physically connect to the cluster, vary depending on the type of Integrity NonStop NS-series system: Integrity NonStop NS16000 series systems can utilize any of the topology, cluster switch, or node interconnect cable options listed in Table 1-2. For these systems, the cluster switches are connected to cluster plug-in cards (PICs) located in slot 2 of the processor switches. Integrity NonStop NS16000 series systems can also be connected to BladeCluster Solutions. BladeCluster Solution is a type of ServerNet cluster. For information, see the BladeCluster Solution Manual. Integrity NonStop NS14000 series systems can only be connected to a layered topology cluster and must use the MMF option. There are no processor switches. For NS14000 systems containing an IOAM enclosure, the cluster switches are connected to port 1 on the ServerNet switch boards in the IOAM enclosure. For NS14000 series systems containing VIO enclosures (instead of an IOAM enclosure), the cluster switches are connected to port 1 on the Optical Extender PICs in slot 5 of the VIO enclosure for each fabric. Integrity NonStop NS14000 series systems can also be part of a BladeCluster Solution via connection through the 6770 or 6780 ServerNet cluster switches. For information, see the BladeCluster Solution Manual. Use the Add Node to ServerNet Cluster guided procedure launched by an action of the same name under the System object in the OSM Service Connection to connect your system to a ServerNet cluster. OSM automatically detects your system type and displays the appropriate guided procedure for you. The guided procedure online help contains diagrams of the hardware configurations described in this supplement as well as step-by-step instructions to accompany the guided procedure. Software Requirements Install all software before connecting any cables or making any hardware changes. Before you add an Integrity NonStop NS-series system to a ServerNet cluster: Check that all required H-series software is installed on all Integrity NonStop NS-series nodes. Integrity NonStop NS16000 series systems require the software listed in Table 1-1. These software components are included in the H06.03 release version update (RVU) with the exception of the Expand/ServerNet profile, which is an optional product on the site update tape (SUT). Note. To take advantage of the two- or three-zone long-distance options, see the Recommended SPR for Multi-Zone Long-Distance Options on page

14 Software Requirements Integrity NonStop NS14000 systems with an IOAM enclosure require the H06.05 RVU, which includes all required SPRs. Integrity NonStop NS14000 series systems with VIO enclosures require the H06.08 RVU, which includes all required SPRs. Depending on your cluster configuration, you might also need to install G-series software on any NonStop S-series nodes in the ServerNet cluster (see Table 1-1). For RVU and SPR software requirements for Integrity NonStop NS-series systems to be connected to a BladeCluster, refer to the BladeCluster Solution Manual. Table 1-1. Minimum Software Requirements for Integrity NonStop NS16000 Series Software Component H-Series PVU G-Series PVU Expand/ServerNet profile ServerNet Management Driver T0509H01 For 6780 switches: T2800H01 The Product Version Update (PVU) required is the same as documented in existing manuals. The PVU required is the same as documented in existing manuals. SNETMON/MSGMON T0294H01 T0294AAP is required on any NonStop S-series nodes in the cluster. SANMAN T0502H01 The PVU required is the same as documented in existing manuals. T0502AAN and earlier PVUs report WRONG TYPE for the CRU TYPE if a 6780 switch contains quad MMF PICs in any of the slots 6 through 9. OSM Service Connection Suite T0682H01^AAE T0682AAA is required on all NonStop S-series nodes in the cluster if you use a 6780 switch containing quad MMF PICs in at least one of the slots 6 through 9 to connect NonStop S-series servers to the cluster. Recommended SPR for Multi-Zone Long-Distance Options For long-distance clusters using either the two or three zone options, HP strongly recommends T9050H02^AQD or later. (T9050H02^AQD was released at H06.05, so it is already part of the base software platform for Integrity NonStop NS14000 series systems.) For more information about the long-distance options, see the ServerNet Cluster 6780 Planning and Installation Guide. 1-4

15 Hardware Requirements Hardware Requirements For hardware requirements for Integrity NonStop NS-series systems to be connected to a BladeCluster, refer to the BladeCluster Solution Manual. At least two 6770 switches or 6780 switches (one for the X fabric and one for the Y fabric) are required. A cable management assembly is required for each 6780 switch. The switches must be installed and powered on. For Integrity NonStop NS16000 series nodes in a layered topology, you can use either the single-mode fiber (SMF) option or multimode fiber (MMF) option as described in Table 1-2. For example, if you use the MMF option, you must have MMF PICs installed in both the 6780 switches and the p-switches. Integrity NonStop NS14000 series nodes are only supported in a layered topology using the MMF option. Table 1-2. Integrity NonStop NS-Series Node Hardware Requirements Topology Star, split-star or tri-star topology Cluster Connectivity Point on the Node Cluster Switches Node Interconnect Cables Dual SMF PIC in slot 2 of each p-switch (NS16000 series only) A 6770 switch with at least one port in the range 0 through 7 must be available on each ServerNet II Switch (a subcomponent of the 6770 switch) for connecting a fiberoptic cable. SMF cables with duplex LC connectors on one end and duplex subscriber connectors (SC) on the other end Layered topology, SMF option Dual SMF PIC in slot 2 of each p-switch (NS16000 series only) A 6780 switch with a dual SMF PIC in at least one of the slots 6 through 9. At least one port on each PIC in the range 1 or 2 must be available. SMF cables with duplex LC connectors on both ends Layered topology MMF option For NS16000 series: Quad MMF PIC in slot 2 of each p-switch A 6780 switch with a quad MMF PIC in at least one of the slots 6 through 9. At least one port on each PIC in the range 1 or 2 must be available. For the MMF option, OSM version T0682AAA is required on all NonStop S-series nodes in the ServerNet cluster. MMF cables with duplex LC connectors on both ends For NS14000 with IOAM enclosure: port 1 of the ServerNet switch board in each IOAM For NS14000 series system with VIO enclosures: port 1 of the Optical Extender PIC in slot 5 of each VIO enclosure For the MMF option, OSM version T0682AAA is required on all NonStop S-series nodes in the ServerNet cluster. 1-5

16 OSM Support for NonStop NS-Series Nodes in a ServerNet Cluster OSM Support for NonStop NS-Series Nodes in a ServerNet Cluster For an Integrity NonStop NS-series node, the attributes and actions for the cluster switches are the same as described in the existing manuals and the OSM online help: 6770 switch ServerNet Cluster 6770 Supplement 6780 switch ServerNet Cluster 6780 Operations Guide Depending on your system type and configuration, see: Preparing Integrity NonStop NS16000 Series System on page 1-6 Preparing Integrity NonStop NS14000 System with IOAM Enclosure on page 1-8 Preparing Integrity NonStop NS14000 Series System with VIO Enclosures on page 1-9 Preparing Integrity NonStop NS16000 Series System Checking the Cluster PICs 1. To locate and check a cluster PIC in the OSM Service Connection, expand the system object in the tree pane and navigate to: Fabric Group 100 > Internal ServerNet X/Y Fabric > Processor Switch 2. Expand the Processor Switch and select the ServerNet PIC in slot 2 to check for alarms or problem attributes. VST001.vsd 1-6

17 Preparing Integrity NonStop NS16000 Series System 3. If the ServerNet PIC icon contains a yellow arrow, double-click to expand it and select the Port object. In this example, the degraded Service State is caused by an alarm. In the Alarms tab, select the individual alarm, then right-click and select Detail to get more information, including suggested repair actions, for the alarm. VST002.vsd Replacing the Cluster PIC in a Processor Switch To change the type of cluster PIC from MMF or SMF or to replace the PIC, right-click on the ServerNet PIC object in slot 2 and select Actions. Perform the Replace action to launch an OSM guided procedure to help you replace the PIC. The MSEB Replace action documented in the existing ServerNet cluster manuals does not apply to Integrity NonStop NS-series nodes. Adding a Cluster PIC 1. Determine if you need an MMF PIC or SMF PIC. 2. In slot 2 of the p-switch, insert the PIC until it is fully seated. 3. Check that the green power LED on the PIC is lit, and that the amber fault LED is not lit. 4. Refer to Adding the Node to a ServerNet Cluster. Do not connect the cables until instructed to do so by the guided procedure. Adding the Node to a ServerNet Cluster 1. On both the X-fabric and Y-fabric, check that the PICs used to connect the p-switch to the cluster switch are the correct type (either SMF or MMF) as described in Hardware Requirements on page If the PICs in both the cluster switch and p-switch do not match or are not supported for the type of cluster switch, replace or add the correct type of PIC to either the cluster switch or p-switch as needed. 3. Start the guided procedure for adding an Integrity NonStop NS-series node to a new or existing ServerNet cluster: a. In the tree pane of the OSM Service Connection, right-click the system resource and select Actions. b. Select Add Node to ServerNet Cluster and click Perform Action. c. In the guided procedure, click Start. 1-7

18 Preparing Integrity NonStop NS14000 System with IOAM Enclosure Preparing Integrity NonStop NS14000 System with IOAM Enclosure Because an Integrity NonStop NS14000 system with IOAM enclosure has no processor switches or cluster PICs, ServerNet cluster connectivity is established through the ServerNet switch boards in each of the two I/O adapter modules (IOAMs). Checking the ServerNet Switch Boards 1. To locate and check a ServerNet switch board in an Integrity NonStop NS14000 system, expand the system object in the tree pane and navigate to: Fabric Group 100 > IOAM Enclosure > IOAM 100.n* > ServerNet Switch Board * IOAM for X-fabric, IOAM for Y-fabric 2. Select the ServerNet Switch Board and check for alarms or problem attributes. 3. If the ServerNet Switch Board icon contains a yellow arrow, double-click to expand it and select Port 1 (the port used for cluster connectivity) to check for alarms or problem attributes. VST003.vsd Replacing a ServerNet Switch Board To replace the ServerNet switch board in an Integrity NonStop NS14000 system, right-click on the ServerNet switch board object and select Actions. Perform the Replace action to launch a documented service procedure that describes how to replace the ServerNet switch board. 1-8

19 Preparing Integrity NonStop NS14000 Series System with VIO Enclosures Adding a ServerNet Switch Board Use can use the Add Node to ServerNet Cluster guided procedure to add a ServerNet switch board. (See Adding the Node to a ServerNet Cluster.) Do not connect the cables until instructed to do so by the guided procedure. Adding the Node to a ServerNet Cluster 1. As noted in Table 1-2, the 6780 cluster switch slot used for connecting to an Integrity NonStop NS14000 system must have a quad MMF PIC. Replace or add a PIC as needed. 2. Start the guided procedure for adding an Integrity NonStop NS14000 node to a new or existing ServerNet cluster: a. In the tree pane of the OSM Service Connection, right-click the system object and select Actions. b. Select Add Node to ServerNet Cluster and click Perform Action. c. In the guided procedure, click Start. Preparing Integrity NonStop NS14000 Series System with VIO Enclosures For Integrity NonStop NS14000 series systems with VIO enclosures, ServerNet cluster connectivity is established through the Optical Extender PIC in slot 5 of the VIO enclosure on each fabric. Checking the Optical Extender PICs 1. To locate and check an Optical Extender PIC in an Integrity NonStop NS14000 series system, expand the system object in the tree pane and navigate to: Fabric Group 100 > Internal ServerNet Fabric > VIO Module 100.n* > Optical Extender PIC * VIO Module for X-fabric, VIO Module for Y-fabric 2. Select the Optical Extender PIC and check for alarms or problem attributes. 3. If the Optical Extender PIC icon contains a yellow arrow, double-click to expand it and select Port 1 (the port used for cluster connectivity) to check for alarms or problem attributes. 1-9

20 Preparing Integrity NonStop NS14000 Series System with VIO Enclosures VST004.vsd Replacing an Optical Extender PIC To replace the Optical Extender PIC, right-click on the Optical Extender PIC object and select Actions. Perform the Replace action to launch a documented service procedure that describes how to replace the Optical Extender PIC. Adding an Optical Extender PIC Use can use the Add Node to ServerNet Cluster guided procedure to add a Optical Extender PIC. (See Adding the Node to a ServerNet Cluster.) Do not connect the cables until instructed to do so by the guided procedure. Adding the Node to a ServerNet Cluster 1. You must have an Optical Extender PIC installed in slot 5 of each VIO enclosure. If not, see Adding an Optical Extender PIC. 2. Start the guided procedure for adding an Integrity NonStop NS14000 series node to a new or existing ServerNet cluster: a. In the tree pane of the OSM Service Connection, right-click the system object and select Actions. b. Select Add Node to ServerNet Cluster and click Perform Action. c. In the guided procedure, click Start. 1-10

21 SCF Displays for NonStop NS-Series Nodes in a ServerNet Cluster SCF Displays for NonStop NS-Series Nodes in a ServerNet Cluster For detailed syntax and descriptions of the Subsystem Control Facility (SCF) commands, refer to: 6770 Switch ServerNet Cluster Manual 6780 Switch ServerNet Cluster 6780 Operations Guide For an Integrity NonStop NS-series node, the commands and displays are the same as described in the existing manuals except for the differences noted here. INFO CONNECTION Command (6780 Switch) The output display for the INFO CONNECTION command varies, depending on the type of Integrity NonStop NS-series system. Example 1-1 on page 1-12, shows an example of a 6780 switch connected to an Integrity NonStop NS16000 series node. Example 1-2 on page 1-13, shows an example of a 6780 switch connected to an Integrity NonStop NS14000 series node. The Node port heading replaces the MSEB port heading displayed for NonStop S-series nodes. The Node port heading contains information about the port on the p-switch (NS16000 series), ServerNet switch board (NS14000 with IOAM), or Optical Extender PIC (NS14000 series with VIO) that connects to the cluster switch. The NNA Version attribute does not appear in the displays for the Node Port. Table 1-3 lists the attributes whose descriptions have changed for Integrity NonStop NS-series nodes. Table 1-3. INFO CONNECTION Attributes for Integrity NonStop NS-series Nodes Attribute Port PIC or CRU Type Node Routing ID Description The port number on the ServerNet switch board (NS14000 with IOAM), Optical Extender PIC (NS14000 series with VIO), or p-switch PIC (NS16000 series) to which the ServerNet cable is attached. The type of plug-in card used in the cluster switch, p-switch, ServerNet switch board, or Optical Extender PIC. Routing ID on the cluster switch, p-switch, ServerNet switch board, or Optical Extender PIC. 1-11

22 INFO CONNECTION Command (6780 Switch) Example 1-1. INFO CONNECTION Display for a 6780 Switch (NS16000 series system) INFO CONNECTION X Fabric Y Fabric Response Status ok ok Rsp Status Detail No Status Detail No Status Detail Switch Type Model 6780 Model Node Port Port Configuration Port Configuration Port 1 1 PIC Type Dual SMF Dual SMF Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number SvNet Switch Port Port Configuration Port Configuration CRU Slot 7 7 CRU Port 1 1 PIC Type Dual SMF Dual SMF Transceiver 9/125u SMF 9/125u SMF Desired Port State n/a n/a Neighbor ID Check Query No Resp Expected Query No Resp Expected Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number

23 INFO CONNECTION Command (6780 Switch) Example 1-2. INFO CONNECTION Display for a 6780 Switch (NS14000 series system) INFO CONNECTION X Fabric Y Fabric Response Status ok ok Rsp Status Detail No Status Detail No Status Detail Switch Type Model 6780 Model Node Port Port Configuration Port Configuration Port 1 1 PIC or CRU Type Switch 4 Logical Board Switch 4 Logical Board Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number SvNet Switch Port Port Configuration Port Configuration CRU Slot 7 7 CRU Port 1 1 PIC or CRU Type Dual SMF Dual SMF Transceiver 9/125u SMF 9/125u SMF Desired Port State n/a n/a Neighbor ID Check Query No Resp Expected Query No Resp Expected Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number

24 INFO CONNECTION Command Display (6770 Switch) INFO CONNECTION Command Display (6770 Switch) The syntax for INFO CONNECTION has not changed. Example 1-3 shows the display for a 6770 switch connected to an Integrity NonStop NS-series node: The Node port heading contains information about the p-switch port that connects to the cluster switch. This port heading replaces the MSEB port heading used for NonStop S-series nodes. The NNA Version attribute does not appear in the displays for the Node Port. Table 1-4 lists the attributes that have different descriptions for Integrity NonStop NS-series nodes. Table 1-4. INFO CONNECTION Attributes for Integrity NonStop NS-series Nodes Attribute Port number PIC Functional ID Node Routing ID Description The port number on the PIC located in slot 2 of the p-switch to which the ServerNet cable is attached The type of plug-in card used in the p-switch and cluster switch The node routing ID on the p-switch and cluster switch Example 1-3. INFO CONNECTION Display for a 6770 Switch INFO CONNECTION X Fabric Y Fabric Response Status ok ok Rsp Status Detail No Status Detail No Status Detail Switch Type Model 6770 Model Configuration Node Port Switch Port Node Port Switch Port Port Info Valid true true true true Port Number Desired Port State n/a TX/RX Auto n/a TX/RX Auto Neighbor ID Check n/a No Qry pass n/a No Qry pass Node Number Mask 0x000fc000 0x000fc000 0x000fc000 0x000fc000 Node Routing ID 0x000dc000 0x000dc000 0x000dc000 0x000dc000 SvNet Node Number PIC Functional ID SMF Optical SMF Optical SMF Optical SMF Optical

25 STATUS CONNECTION Command (6780 Switch) STATUS CONNECTION Command (6780 Switch) The STATUS CONNECTION syntax has not changed, except that the NNA option is not supported for Integrity NonStop NS-series nodes. Example 1-4 on page 1-17 shows the display for a 6780 switch connected to an Integrity NonStop NS-series node. The Node port heading replaces the MSEB port heading displayed for NonStop S-series nodes. The Node port heading contains information about the port on the p-switch (NS16000 series), ServerNet switch board (NS14000 with IOAM), or Optical Extender PIC (NS14000 series with VIO) that connects to the cluster switch. Table 1-5 lists the attributes that have different descriptions for Integrity NonStop NS-series nodes. Table 1-5. STATUS CONNECTION Attributes for Integrity NonStop NS-Series Nodes (page 1 of 2) Attribute Fabric Access Port Description The status of the external X and Y fabric connections. The possible values are the same as documented in the ServerNet Cluster 6780 Operations Guide, except for: WRONG CRU TYPE indicates that a PIC other than a dual SMF or quad MMF PIC is installed in slot 2 of the p-switch. For NS14000 series, only an MMF connection to the IOAM ServerNet switch board or the VIO Optical Extender PIC is supported. The NonStop S-series equivalent is CRU TYPE NOT MSEB. CRU MISSING indicates that a p-switch (or p-switch logic board) (NS16000 series), a ServerNet switch board (NS14000 with IOAM), or an Optical Extender PIC (NS14000 series with VIO) is missing. The NonStop S-series equivalent is MSEB MISSING. PIC MISSING indicates that a dual SMF PIC or quad MMF PIC is missing from slot 2 of the p-switch. The NonStop S-series equivalent is NO NNA PIC. NO CRU CONFIG RECORD indicates a configuration problem. The NonStop S-series equivalent is NO MSEB CONFIG RECORD. BAD CRU CONFIG RECORD indicates a configuration problem. The NonStop S-series equivalent is BAD MSEB CONFIG RECORD. CRU CONFIG FETCH ERR indicates a configuration problem. The NonStop S-series equivalent is MSEB CONFIG FETCH ERROR. The port number on the ServerNet switch board (NS14000 with IOAM), Optical Extender PIC (NS14000 series with VIO), or p-switch PIC (NS16000 series) to which the ServerNet cable is attached. 1-15

26 STATUS CONNECTION Command (6780 Switch) Table 1-5. STATUS CONNECTION Attributes for Integrity NonStop NS-Series Nodes (page 2 of 2) Attribute Port Status NNA Prog State Node Routing ID Description The status of the cluster switch port and the port on the p-switch (NS16000 series), ServerNet switch board (NS14000 with IOAM), or Optical Extender PIC (NS14000 series with VIO). The possible values are: link alive LINK DEAD RESET LA, DISABLED UNINSTALLED The programming state of the NNA on the p-switch Possible values are enabled, DISABLED, RESET, ENABLED FOR IBC ONLY, and CONFIG ERR. Routing ID on the cluster switch, p-switch, ServerNet switch board, or Optical Extender PIC. 1-16

27 STATUS CONNECTION Command (6780 Switch) Example 1-4. STATUS CONNECTION Display for a 6780 Switch STATUS CONNECTION X Fabric Y Fabric Response Status ok ok Rsp Status Detail No Status Detail No Status Detail Fabric Access No Error No Error Node Port Port Status Port Status Port 1 1 Link Speed 125 MB/S 125 MB/S Optical Signal present present Port Status link alive link alive Link Level Rx enabled enabled Link Level Tx enabled enabled Packet Level Rx enabled enabled Packet Level Tx enabled enabled NNA Prog State enabled enabled Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number SvNet Switch Port Port Status Port Status CRU Slot 7 7 CRU Port 1 1 Transceiver Enabled yes yes Transceiver Status ok ok LED State on on Link Speed 125 MB/S 125 MB/S Optical Signal present present Port Status enabled enabled Node Number Mask 0x000ff000 0x000ff000 Node Routing ID 0x000c7000 0x000c7000 SvNet Node Number

28 STATUS CONNECTION Command (6770 Switch) STATUS CONNECTION Command (6770 Switch) The STATUS CONNECTION syntax has not changed, except that the NNA option is not supported for Integrity NonStop NS-series nodes. Example 1-5 shows the display for a 6770 switch connected to an Integrity NonStop NS-series node: The Node port heading contains information about the p-switch port that connects to the cluster switch. The NonStop S-series equivalent is MSEB port. Table 1-6 lists the attributes that have different descriptions for Integrity NonStop NS-series nodes. Table 1-6. STATUS CONNECTION Attributes for Integrity NonStop NS-Series Nodes Attribute Fabric Access Port Port Status NNA Prog State Node Routing ID Status for Neighbor Description The status of the external X and Y fabric connections. The possible values are the same as documented in the ServerNet Cluster Manual, except for: WRONG CRU TYPE indicates that a PIC other than a dual SMF or quad MMF PIC is installed in slot 2 of the p-switch. The NonStop S-series equivalent is CRU TYPE NOT MSEB. CRU MISSING indicates that a p-switch or p-switch logic board is missing. The NonStop S-series equivalent is MSEB MISSING. PIC MISSING indicates that a dual SMF PIC or quad MMF PIC is missing from slot 2 of the p-switch. The NonStop S-series equivalent is NO NNA PIC. NO CRU CONFIG RECORD indicates a configuration problem. The NonStop S-series equivalent is NO MSEB CONFIG RECORD. BAD CRU CONFIG RECORD indicates a configuration problem. The NonStop S-series equivalent is BAD MSEB CONFIG RECORD. CRU CONFIG FETCH ERR indicates a configuration problem. The NonStop S-series equivalent is MSEB CONFIG FETCH ERROR. The port number on the PIC located in slot 2 of the p-switch to which the ServerNet cable is attached The status of the p-switch port or cluster switch port. Possible values for are: link alive LINK DEAD RESET LA, DISABLED UNINSTALLED The programming state of the NNA on the p-switch. Possible values are enabled, DISABLED, RESET, ENABLED FOR IBC ONLY, and CONFIG ERR The node routing ID on the p-switch and cluster switch This attribute does not apply to ports on the p-switch 1-18

29 STATUS CONNECTION Command (6770 Switch) Example 1-5. STATUS CONNECTION Display for 6770 Switches STATUS CONNECTION X Fabric Y Fabric Response Status ok ok Rsp Status Detail No Status Detail No Status Detail Fabric Access No Error No Error Status Result Node Port Switch Port Node Port Switch Port Port Status Valid true true true true Port Status link alive link alive link alive link alive Link Speed 125 MB/S 125 MB/S 125 MB/S 125 MB/S Link Lvl Prtcl Rcv enabled enabled enabled enabled Link Lvl Prtcl Trn enabled enabled enabled enabled Pckt Lvl Prtcl Rcv enabled enabled enabled enabled Pckt Lvl Prtcl Trn enabled enabled enabled enabled Lost Optical Signl false false false false Status For Neighbr n/a ok n/a ok Target Output Port enabled enabled enabled enabled Node Number Mask 0x000fc000 0x000fc000 0x000fc000 0x000fc000 Node Routing ID 0x000dc000 0x000dc000 0x000dc000 0x000dc000 SvNet Node Number NNA Prog State enabled n/a enabled n/a

30 STATUS CONNECTION Command (6770 Switch) 1-20