ServerNet Cluster 6780 Operations Guide Abstract This guide describes operations and troubleshooting tasks for ServerNet clusters that use the HP NonStopTM ServerNet Switch (model 6780) in a layered topology. Product Version NA Supported Release Version Updates (RVUs) This guide supports G06.29 and subsequent G-series RVUs, and H06.06 and subsequent H-series RVUs, unless otherwise indicated in its replacement publication.
Document History Part Number Product Version Published 525606-001 NA September 2003 525606-002 NA December 2003 525606-003 NA February 2006 525606-004 NA July 2006
ServerNet Cluster 6780 Operations Guide Index Examples Figures What’s New in This Manual ix Manual Information ix New and Changed Information About This Manual xi Notation Conventions Tables ix xii 1.
Contents 2. Controlling ServerNet Cluster Processes 2.
Contents 4.
Contents 5. SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SUBNET Command 4-13 Considerations 4-14 STATUS SUBNET Command Example 4-15 STATUS SUBNET, PROBLEMS Command Example 4-18 STATUS SUBNET, RANGE Command Example 4-19 STATUS SUBNET, DETAIL Command Example 4-20 STATUS SUBSYS Command 4-26 STATUS SUBSYS Command Example 4-26 STOP Command 4-27 Considerations 4-27 Example 4-28 VERSION Command 4-29 Examples 4-29 5.
6.
A. ServerNet Cluster Software Contents A. ServerNet Cluster Software NonStop Kernel Message System A-1 MSGMON A-2 SANMAN Subsystem A-2 ServerNet Cluster Subsystem A-3 SNETMON A-3 Expand-Over-ServerNet Line-Handler Processes A-5 B. Cable Connections in a Layered Topology Handling Fiber-Optic Cables B-1 Labeling Cables B-1 Connections Between Layers B-2 Connections Between Two Zones B-3 Connections For Three Zones B-5 C. Part Numbers C-2 D. ESD Information E.
Figures Contents Example 1-13. Example 1-14. Example 1-15. Example 1-16. Example 1-17. STATS PATH Command 1-23 INFO LINE, DETAIL Command 1-24 INFO PATH, DETAIL Command 1-24 INFO PROCESS $NCP, LINESET Command INFO PROCESS $NCP, NETMAP Command 1-25 1-25 Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7. Figure 1-8. Figure 1-9. Figure 1-10. Figure 1-11. Figure 1-12. Figure 1-13. Figure 1-14. Figure 1-15. Figure 1-16. Figure 1-17. Figure 1-18. Figure 1-19.
Tables Contents Figure D-1. Using ESD Protection When Servicing CRUs D-2 Tables Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 3-5. Table 4-1. Table 4-2. Table 4-3. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table B-1. Table B-2. Table B-3. Table B-4. Table B-5.
What’s New in This Manual Manual Information ServerNet Cluster 6780 Operations Guide Abstract This guide describes operations and troubleshooting tasks for ServerNet clusters that use the HP NonStopTM ServerNet Switch (model 6780) in a layered topology. Product Version NA Supported Release Version Updates (RVUs) This guide supports G06.29 and subsequent G-series RVUs, and H06.06 and subsequent H-series RVUs, unless otherwise indicated in its replacement publication.
Other Recent Changes What’s New in This Manual ServerNet Cluster 6780 Operations Guide—525606-004 x
About This Manual This table describes the sections of the manual: Note. If you are using Integrity NonStop NS-series servers, refer to the ServerNet Cluster Supplement for NonStop NS-Series Servers for additional information. Section Title This section... 1 Monitoring a ServerNet Cluster Describes tasks for monitoring a layered topology ServerNet cluster and its components. 2 Controlling ServerNet Cluster Processes Describes tasks for controlling process in a ServerNet cluster.
Notation Conventions About This 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.
General Syntax Notation About This Manual | 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.
Notation for Messages About This Manual !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:i. !i,o 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.
Change Bar Notation About This Manual 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.
Change Bar Notation About This Manual ServerNet Cluster 6780 Operations Guide— 525606-004 xvi
1 Monitoring a ServerNet Cluster This section describes how to perform tasks that allow you to check the general health of the ServerNet Cluster without altering the state of the cluster or any of its components.
Monitoring a ServerNet Cluster 6780 Switch and Component Names 6780 Switch and Component Names The layered topology is built with 6780 switches. A 6780 switch is represented in OSM as a switch module. The full OSM switch name takes this form: Switch Module $ZZSMN.Y23 (1021.3) In this example: • • Y21 indicates the fabric (Y), zone (2), and layer (3) of the switch. (1021.3) contains the group and module number. The first two digits of all switch group numbers is always 10.
Monitoring a ServerNet Cluster • Using OSM to Monitor a ServerNet Cluster With SCF, you can compare information by logging on to a remote TACL process and then running SCF at the remote node or by entering \nodename.$ZZSMN at a TACL prompt. Both methods require matching remote passwords.
Monitoring a ServerNet Cluster Starting an OSM Session Figure 1-1. OSM Management Window VST1017.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster Using OSM to View Cluster Resource Attributes 1. In the tree pane, expand Group 1 and then Module 1.1 to display all of the components in the Group 1 processor enclosure. 2. Select a Modular ServerNet Expansion Board (MSEB). 3. In the details pane, click the Attributes tab. Figure 1-2 shows the attributes for this resource. Figure 1-2. Attributes for the MSEB VST1001.vsd 4.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster Figure 1-4. Attributes for the ServerNet Cluster Resource VST1002.vsd 7. In the tree pane, expand the ServerNet Cluster resource. The tree pane displays the high-level cluster resources below it. See Figure 1-5. Figure 1-5. Tree Pane With ServerNet Cluster Resource Expanded VST1015.vsd 8. Select the local node. Figure 1-6 shows the attributes for this resource.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster Figure 1-6. Attributes for the ServerNet Local Node VST1004.vsd VST1004.vsd 9. In the tree pane, select a remote node. Figure 1-7 shows the attributes for this resource. Figure 1-7. Attributes for a ServerNet Remote Node VST1007.vsd 10. In the tree pane, select either External_ServerNet_X_Fabric or External_ServerNet_Y_Fabric. Figure 1-8 shows the attributes for this resource. Figure 1-8.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster 11. In the tree pane, expand the External_ServerNet_X_Fabric object, and then select a switch group, such as Switch Group 1010. Figure 1-10 shows the attributes for the switch group. Figure 1-9. Attributes for a Switch Group VST1030.vsd 12. In the tree pane, expand Switch Group 1010, and then select Switch Module $ZZSMN.X11. Figure 1-10 shows the attributes for the 6780 switch module. Figure 1-10.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster Figure 1-11. Attributes for the Switch PIC 14. In the tree pane, expand the switch PIC in slot 6, and then select a switch port under it. This type of port is a transceiver that connects the switch module to an MSEB on a ServerNet node. In this manual, this type of port is called a switch-tonode port. Only the PICs in slots 6 through 9 contain switch-to-node ports. Figure 1-12 shows the attributes for this resource.
Using OSM to View Cluster Resource Attributes Monitoring a ServerNet Cluster switch in another zone or layer. In this manual, this type of port is called a switchto-switch port. The PICs in slots 2 and 3 contain the ports that connect to another switch zone. The PICs in slots 11 through 13 contain the ports that connect to another cluster switch layer. Figure 1-13 shows the attributes for this resource.
Monitoring a ServerNet Cluster Using OSM to View Cluster Resource Attributes Figure 1-14. Attributes for the Switch Logic Board VST1009.vsd 17. In the tree pane, under the Switch Module, select the Power Supply. The Switch Module has two power supplies that plug in to slots 15 and 18 of the switch logic board. Figure 1-15 shows the attributes for a switch power supply. Figure 1-15.
Monitoring a ServerNet Cluster Using OSM to View Cluster Resource Attributes 18. In the tree pane, under the Switch Module, select a Switch Fan. A switch module has two fans that plug into slots 16 and 17 of the switch logic board. Figure 1-16 shows the attributes for a switch fan. Figure 1-16.
Monitoring a ServerNet Cluster Using OSM to Display the Physical View of a Fabric Using OSM to Display the Physical View of a Fabric 1. In the tree pane, select External_ServerNet_X_Fabric or External_ServerNet_Y_Fabric. 2. From the View menu, select Physical. The view pane displays a physical representation of the nodes, cluster switches, and connections on the external fabric. Figure 1-17 shows the External_ServerNet_X_Fabric in a cluster with two zones and two layers. Figure 1-17.
Monitoring a ServerNet Cluster Using OSM to Check the Status of the ServerNet Cluster Subsystem Using OSM to Check the Status of the ServerNet Cluster Subsystem 1. In the Tree pane, select the ServerNet Cluster resource. 2. In the Details pane, click the Attributes tab. 3. Check the ServerNet Cluster State attribute. See Figure 1-18 on page 1-14 Figure 1-18. ServerNet Cluster State VST1002.
Using OSM to Monitor Expand-Over-ServerNet Lines Monitoring a ServerNet Cluster Using OSM to Monitor Expand-Over-ServerNet Lines You can use two methods to monitor Expand-over ServerNet lines: • • Check the attributes of the remote node in the OSM Service Connection. Perform the Add Node to ServerNet Cluster action on the local node. Using the OSM Service Connection 1. Expand the ServerNet Cluster resource. 2.
Monitoring a ServerNet Cluster Using OSM to Monitor Expand-Over-ServerNet Lines 3. Click Perform Action. The procedure quickly cycles through its list of software checks and displays the ServerNet Cluster Connection Status dialog box. See Figure 1-20. The online help can help you understand the dialog boxes. Figure 1-20. ServerNet Cluster Connection Status Dialog Box vst058.
Monitoring a ServerNet Cluster Using OSM to Generate ServerNet Cluster Statistics Using OSM to Generate ServerNet Cluster Statistics Each processor in every node of a ServerNet cluster keeps message system counters regarding communication with each node in the cluster, including the local node. In addition, each processor keeps a set of generic counters that are not associated with any particular node.
Monitoring a ServerNet Cluster Using SCF to Monitor a ServerNet Cluster Using SCF to Monitor a ServerNet Cluster The Subsystem Control Facility (SCF) provides commands that display general information about the ServerNet Cluster subsystem.
Using SCF to Check SNETMON Status Monitoring a ServerNet Cluster Using SCF to Check SNETMON Status You can use the Kernel subsystem SCF STATUS PROCESS command to check the status of SNETMON. Example 1-3 shows an SCF STATUS PROCESS command and its output. Example 1-3. STATUS PROCESS Command > STATUS PROCESS $ZZKRN.#ZZSCL NONSTOP KERNEL - Status Process \MINDEN.$ZZKRN.
Using SCF to Check ServerNet Cluster Connections Monitoring a ServerNet Cluster Using SCF to Check ServerNet Cluster Connections You can use the SCF STATUS SUBNET command to check connections to other systems in the ServerNet cluster. Example 1-6 shows the output of a STATUS SUBNET command. Example 1-6.
Using SCF to Check the Version of the ServerNet Cluster Subsystem Monitoring a ServerNet Cluster Using SCF to Check the Version of the ServerNet Cluster Subsystem You can use the SCF VERSION command to display version information about the ServerNet cluster subsystem. Example 1-7 shows the information returned by the VERSION, DETAIL command. Example 1-7. VERSION SUBSYS, DETAIL Command > VERSION SUBSYS $ZZSCL, DETAIL Detailed VERSION SUBSYS \SYS.
Using SCF to Monitor Expand-Over-ServerNet Lines and Paths Monitoring a ServerNet Cluster For more information about using SCF commands for the Expand subsystem, refer to the Expand Configuration and Management Manual. Using the SCF STATUS LINE, DETAIL Command Use the STATUS LINE, DETAIL command to check the status for the Expand-overServerNet line. Example 1-10 shows an SCF STATUS LINE, DETAIL command and output for an Expand-over-ServerNet line named $SC003. Example 1-10.
Using SCF to Monitor Expand-Over-ServerNet Lines and Paths Monitoring a ServerNet Cluster Example 1-12. STATS LINE Command > STATS LINE $SC003 EXPAND Stats LINE $SC003, PPID Resettime... MAY 17,2003 17:15:59 MsgSent RepRecv MsgTout ErrRecv LastErr Bind 2 2 0 0 0 Aconn 4 4 0 3 140 MsgSent RepRecv MsgTout ErrRecv LastErr Unbind 1 1 0 1 201 Data 178016 178016 0 1 201 Proc lookup failures 0 ( 0, 22), BPID ( 1, 18) Sampletime...
Using SCF to Monitor Expand-Over-ServerNet Lines and Paths Monitoring a ServerNet Cluster Using the SCF INFO LINE, DETAIL Command Use the INFO LINE, DETAIL command to check operational information for an Expand-over-ServerNet line. Example 1-14 shows an SCF INFO LINE, DETAIL command and output for an Expand-over-ServerNet line named $SC002. Example 1-14. INFO LINE, DETAIL Command > INFO LINE $SC002, DETAIL EXPAND Detailed Info LINE $SC002 (LDEV L2Protocol Net^Nam TimeFactor ... 1 Framesize....
Using SCF to Monitor Expand-Over-ServerNet Lines and Paths Monitoring a ServerNet Cluster Using the SCF INFO PROCESS $NCP, LINESET Command Use the INFO PROCESS $NCP, LINESET command to display the status of all the Expand lines currently active on the system. Example 1-16 shows this command. Example 1-16.
Monitoring a ServerNet Cluster Using SCF to Monitor Expand-Over-ServerNet Lines and Paths ServerNet Cluster 6780 Operations Guide—525606-004 1- 26
2 Controlling ServerNet Cluster Processes This section describes how to perform tasks that control the state of the ServerNet cluster processes. The Subsystem Control Facility (SCF) is the primary tool for performing these tasks. For detailed syntax and descriptions of the SCF commands used in this section, see Section 4, SCF Commands for SNETMON and the ServerNet Cluster Subsystem, and Section 5, SCF Commands for the External ServerNet SAN Manager Subsystem.
Controlling ServerNet Cluster Processes ServerNet Cluster Processes ServerNet Cluster Processes This table describes the ServerNet cluster processes that are affected by the tasks in this section: MSGMON A monitor process that resides in each processor of a server and executes functions required by the message system. MSGMON is a helper for SNETMON. MSGMON handles communications between SNETMON and individual processors. MSGMON also logs events from and generates events on behalf of the message system.
Controlling ServerNet Cluster Processes Starting the Message Monitor Process (MSGMON) Starting the Message Monitor Process (MSGMON) For details about adding MSGMON to the configuration database, see the ServerNet Cluster 6780 Planning and Installation Guide. To run MSGMON after adding it but before the next system load, or after stopping it by using the SCF ABORT PROCESS $ZZKRN.#MSGMON command, use the SCF START command: > START PROCESS $ZZKRN.#MSGMON Note.
Controlling ServerNet Cluster Processes Starting the External ServerNet SAN Manager Process (SANMAN) Starting the External ServerNet SAN Manager Process (SANMAN) For details about adding the external ServerNet SAN manager process (SANMAN) to the configuration database, see the ServerNet Cluster 6780 Planning and Installation Guide. HP recommends that you set the STARTMODE attribute for SANMAN to SYSTEM. If you do so, SANMAN starts automatically after a system load or a processor reload.
Controlling ServerNet Cluster Processes Restarting the External ServerNet SAN Manager Process (SANMAN) Restarting the External ServerNet SAN Manager Process (SANMAN) You might restart SANMAN for one of the following reasons: • • Both processors in which the SANMAN process pair is running are stopped. The $ZPM persistence manager automatically restarts the process pair as soon as any processor in its processor list becomes available. An operator issues an SCF ABORT PROCESS $ZZKRN.
Controlling ServerNet Cluster Processes Starting ServerNet Cluster Services any of the SNETMON process configuration attributes if you configured SNETMON with the TACL macro documented in the ServerNet Cluster 6780 Planning and Installation Guide. Aborting SNETMON on a node does not change the state of ServerNet Cluster IPC connectivity to and from that node.
Controlling ServerNet Cluster Processes When a System Joins a ServerNet Cluster When a System Joins a ServerNet Cluster These steps describe what happens when a system joins a ServerNet cluster: 1. The ServerNet cluster monitor process is started (by the $ZPM persistence manager or with an SCF START PROCESS command, depending on the STARTMODE configuration). 2.
Controlling ServerNet Cluster Processes Stopping ServerNet Cluster Services Stopping ServerNet Cluster Services You can use OSM or SCF to stop ServerNet cluster services. Using OSM to Stop ServerNet Cluster Services 1. In the tree pane of the OSM Management window, right-click the ServerNet Cluster resource, and select Actions. 2. From the Actions list, select Set ServerNet Cluster State and click Perform Action. 3. In the drop-down list, select Stopped and click OK.
Controlling ServerNet Cluster Processes Switching SNETMON or SANMAN Primary and Backup Processes change. Only the subsystem state changes are logged. Individual path state changes are not logged. 5. On remote systems, as the ServerNet cluster monitor processes receive word that a ServerNet cluster member has departed, they instruct their local processors to bring down the ServerNet connections with the departing system.
Controlling ServerNet Cluster Processes Using SCF to Switch the Primary and Backup Processes 3. Click Perform action. A confirmation dialog box asks if you are sure you want to perform the action. 4. Click OK. The Action Status window shows the progress of the action. 5. Click Close to close the Actions dialog box. Using SCF to Switch the Primary and Backup Processes Use the SCF PRIMARY PROCESS command to switch the primary and backup processes for SNETMON or for SANMAN.
3 Troubleshooting and Replacement Procedures This section describes how to use software tools to diagnose and troubleshoot a ServerNet Cluster. The software tools available to you are: • • Components of the HP NonStop Open System Management (OSM) Interface: the OSM Service Connection, the OSM Event Viewer, and the OSM Guided procedures The Subsystem Control Facility (SCF) This section also contains replacement procedures for the main hardware components of a ServerNet cluster.
Software Problem Areas Troubleshooting and Replacement Procedures • • • • Use the OSM Service Connection to obtain more information about a problem. In many cases, the OSM Service Connection not only identifies the problem component but can tell you how to fix it. If possible, gather information about a problem from multiple perspectives.
Software Problem Areas Troubleshooting and Replacement Procedures Table 3-1. Software Problem Areas (page 2 of 3) Problem Area Symptom Recovery ServerNet communication Communication on an external fabric is disrupted. Use OSM to check for alarms and repair actions for the External Fabric resource. See Using OSM Alarms on page 3-11. Use the Node Connectivity ServerNet Path Test. See Checking the External ServerNet X and Y Fabrics on page 3-23.
Software Problem Areas Troubleshooting and Replacement Procedures Table 3-1. Software Problem Areas (page 3 of 3) Problem Area Symptom Recovery ServerNet Communication The OSM Service Connection shows the remote node name as \UNKNOWN_Re mote_\Node_n, where n is the ServerNet node number. Verify that SNETMON is operating properly on the remote node. See Troubleshooting SNETMON on page 3-13.
Hardware Problem Areas Troubleshooting and Replacement Procedures Hardware Problem Areas Table 3-2 lists some common hardware problem areas, describes troubleshooting steps, and provides references for more information. Table 3-2. Hardware Problem Areas (page 1 of 4) Problem Area Symptom Recovery MSEB Any 1. Use OSM to check for alarms and repair actions for the MSEB resource. See Using OSM Alarms on page 3-11. 2.
Hardware Problem Areas Troubleshooting and Replacement Procedures Table 3-2. Hardware Problem Areas (page 2 of 4) Problem Area Symptom Recovery ServerNet cable (SEB to SEB, SEB to MSEB, or MSEB to MSEB) Internal fabric communication 1. Use OSM to check for alarms and repair actions for the Internal Fabric resource. See Using OSM Alarms on page 3-11. 2. To get more information, perform SCF and OSM diagnostic actions. See Checking the Internal ServerNet X and Y Fabrics on page 3-20. 3.
Hardware Problem Areas Troubleshooting and Replacement Procedures Table 3-2. Hardware Problem Areas (page 3 of 4) Problem Area Symptom Recovery Switch logic board Any 1. Use OSM to check for alarms and repair actions for the switch logic board. See Using OSM Alarms on page 3-11. 2. Check the LEDs on the front panel of the logic board. See Figure 3-8 on page 3-27. 3. See Replacing a Switch Logic Board (Slot 14) on page 3-33. Switch PIC Switch port Power LED not lit.
Hardware Problem Areas Troubleshooting and Replacement Procedures Table 3-2. Hardware Problem Areas (page 4 of 4) Problem Area Symptom Recovery Switch fan Any 1. Use OSM to check for alarms and repair actions for the switch fan. See Using OSM Alarms on page 3-11. 2. Check the power and fault LEDs on the switch fan. See Figure 3-8 on page 3-27. 3. See Replacing a 6780 Switch Fan (Slots 16 and 17) on page 3-34 Switch power supply Power LED is not lit. See Green Power LED Is Not Lit on page 3-9.
Troubleshooting and Replacement Procedures Green Power LED Is Not Lit Green Power LED Is Not Lit If the green power LED does not light: 1. If the CRU has just been replaced, wait several minutes for the power-on self tests (POSTs) to complete. 2. Make sure the power cords are properly connected. 3. Make sure that the switch components are properly seated in their slots. 4. If you continue to have problems, disconnect and reconnect the power cord.
Troubleshooting and Replacement Procedures ServerNet Cluster Resource Missing From Tree Pane ServerNet Cluster Resource Missing From Tree Pane The ServerNet Cluster resource appears in the tree pane of the OSM Management window if the external ServerNet SAN manager process (SANMAN) can communicate with at least one cluster switch. The ServerNet Cluster resource does not appear if SANMAN cannot communicate with a cluster switch.
Using OSM Alarms Troubleshooting and Replacement Procedures Using OSM Alarms An alarm is a message, similar to an event message, that reports detected faults or abnormal conditions for a CRU or component. In he tree pane, an alarm appears as a bell-shaped icon. Figure 3-2 shows alarms displayed in the tree pane of the OSM Management window. Figure 3-2. Alarm Example VST1024.vsd You can use the OSM Service Connection to gather information about an alarm in order to diagnose a problem.
Troubleshooting and Replacement Procedures Using OSM Alarms Figure 3-3. Alarms Tab Example VST1027.vsd 4. In the Alarms tab, right-click the alarm icon and select Details from the menu. The Alarm Detail dialog box appears, showing detailed information about the alarm. See Figure 3-4. 5. Check the Repair Actions window for a list of steps you can take to respond to the alarm. Perform the repair actions to fix the problem and remove the alarm. Figure 3-4. Alarm Detail Example VST1028.
Troubleshooting and Replacement Procedures Troubleshooting SNETMON Using ZZAA* (Attachment) Files More detailed information is provided in the OSM alarm attachment file for the alarm. OSM alarm attachment files are named ZZAA* and are attached to problem incident reports. To find the ZZAA* file for the alarm you are interested in: • List all of the ZZAA* files in the $SYSTEM.ZSERVICE subvolume using the FILEINFO command: TACL> FILEINFO $SYSTEM.ZSERVICE.
Troubleshooting MSGMON Troubleshooting and Replacement Procedures Figure 3-5. ServerNet Cluster Attributes Showing ServerNet Cluster State VST1002.vsd 2. If $ZZKRN.#ZZSCL is not configured, refer to the ServerNet Cluster 6780 Planning and Installation Guide for information about configuring and starting it. If $ZZKRN.#ZZSCL is configured but not started, try starting it at an SCF prompt: -> START PROCESS $ZZKRN.#ZZSCL 3.
Troubleshooting and Replacement Procedures Troubleshooting SANMAN 1. Verify that MSGMON is started. At an SCF prompt, type: -> STATUS PROCESS $ZZKRN.#MSGMON Note. If $ZZKRN.#MSGMON does not appear to be available, it might be configured using a different symbolic name. Use the SCF INFO PROCESS $ZZKRN.* command to display a list of all currently configured generic processes. 2. If $ZZKRN.
Troubleshooting and Replacement Procedures Troubleshooting Expand-Over-ServerNet LineHandler Processes and Lines Troubleshooting Expand-Over-ServerNet Line-Handler Processes and Lines The Expand-over-ServerNet line-handler processes are responsible for managing security-related messages and forwarding packets outside the ServerNet cluster. For general information about Expand-over-ServerNet lines and line-handler processes, see Appendix A, ServerNet Cluster Software.
Troubleshooting and Replacement Procedures Troubleshooting Expand-Over-ServerNet LineHandler Processes and Lines Figure 3-6. Remote Node Attributes Showing Expand Information VST1007.vsd 5. If the Expand-over-ServerNet lines are stopped, start them. Either: • Use the guided procedure to Add a node to a ServerNet cluster. To start the procedure from OSM: 1. Right-click the local node and select Actions. 2. In the Actions list, select Add Node to ServerNet Cluster. 3. Click Perform Action.
Troubleshooting and Replacement Procedures Checking Communications With a Remote Node Checking Communications With a Remote Node Use the Node Responsive Test action in the OSM Service Connection to test communications with a remote node. This action pings the remote node, verifying whether or not the node is connected and responding. To ping a remote node: 1. In the tree pane, right-click the X or Y Switch Port for the node that you want to ping, and select Actions. The Actions dialog box appears. 2.
Troubleshooting and Replacement Procedures Methods for Repairing ServerNet Connectivity Problems Switching the SNETMON Primary and Backup Processes The SCF PRIMARY PROCESS $ZZSCL command forces a takeover of the SNETMON primary process. The backup process, upon becoming the new primary, queries all processors in the node to find the state of ServerNet connections to all other nodes. If it finds any connections that are down, it initiates a sequence to bring the connections to an online state.
Troubleshooting and Replacement Procedures Checking the Internal ServerNet X and Y Fabrics HP does not recommend stopping and starting the ServerNet cluster subsystem to repair ServerNet connectivity. The SCF STOP SUBSYS $ZZSCL command is used primarily to ensure the orderly removal of a node from the cluster.
Troubleshooting and Replacement Procedures • Checking the Internal ServerNet X and Y Fabrics SEBs 1. Using an OSM workstation attached to the node whose internal fabric you want to check, log on to the OSM Service Connection. The Management window appears. 2. In the tree pane, right-click either Internal_ServerNet_X_Fabric or Internal_ServerNet_Y_Fabric and select Actions. The Actions dialog box appears. 3. From the Actions list, select Group Connectivity ServerNet Path Test. 4. Click Perform action.
Checking the Internal ServerNet X and Y Fabrics Troubleshooting and Replacement Procedures The system displays: NONSTOP KERNEL X-FABRIC TO 0 1 FROM 00 UP UP 01 UP UP 02 UP UP 03 UP UP 04 UP UP 05 UP UP 06 UP UP 07 UP UP 08 <- DOWN 09 <- DOWN 10 <- DOWN 11 <- DOWN 12 <- DOWN 13 <- DOWN 14 <- DOWN 15 <- DOWN Y-FABRIC TO FROM 00 01 02 03 04 05 06 07 08 <09 <10 <11 <12 <13 <14 <15 <- 0 1 UP UP UP UP UP UP UP UP DN DN DN DN UP UP UP UP DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN Status SERVERNET 2 3 4 5 6
Troubleshooting and Replacement Procedures Checking the External ServerNet X and Y Fabrics Checking the External ServerNet X and Y Fabrics You use the OSM Service Connection to check the external ServerNet X and Y fabrics. You can also perform internal and external loopback tests on an NNA PIC in an MSEB. If no alarms are visible on the external fabrics, but you still want to check the connectivity between the local node and the cluster switch, you can use the Node Connectivity ServerNet Path Test action.
Troubleshooting and Replacement Procedures Using the Internal Loopback Test Action 3. In the tree pane, right-click either External_ServerNet_X_Fabric or External_ServerNet_Y_Fabric and select Actions. The Actions dialog box appears. 4. From the Actions list, select Node Connectivity ServerNet Path Test. 5. Click Perform action. The Action Status window shows the progress of the action. 6. Check for an alarm on External_ServerNet_X_Fabric or External_ServerNet_Y_Fabric.
Using SCF to Check Processor-to-Processor Connections Troubleshooting and Replacement Procedures If the action failed, click the Action detail button to get more information. 6. Click Close to close the Action dialog box. Using SCF to Check Processor-to-Processor Connections You can use the SCF STATUS SUBNET command to check processor-to-processor connections. For details, see the STATUS SUBNET, DETAIL Command Example on page 4-20.
MSEB LEDs Troubleshooting and Replacement Procedures MSEB LEDs You can use the LEDs on the MSEB to help diagnose problems. Figure 3-8 describes the LEDs on the MSEB. Figure 3-7. MSEB LEDs MSEB 1 No. LED Type Color 1 Fault Amber 2 3 10 9 5 3 Lights when the MSEB or one of its PICs is not in a fully functional state. Possibly, a fault was detected on the MSEB or one of its PICs or the MSEB or PIC has not been successfully intiialized and configured for use as a system resource.
LEDs on the 6780 Switch Troubleshooting and Replacement Procedures LEDs on the 6780 Switch You can use the LEDs on the different components of the 6780 switch to help diagnose problems. Figure 3-8 shows the LEDS on the 6780 switch. Figure 3-8.
Logic Board Display on the 6780 Switch Troubleshooting and Replacement Procedures Logic Board Display on the 6780 Switch You can use the liquid-crystal display (LCD) on the logic board of the 6780 switch to help diagnose problems associated with the switch. Use the UP and DOWN buttons to scroll through the display. Figure 3-9 shows the Switch Logic Board. Figure 3-9.
Logic Board Display on the 6780 Switch Troubleshooting and Replacement Procedures • Check settings that are inconsistent with the position of the switch in the layered topology. For example, switch X22 on the X fabric, zone 2, layer 2 should have a numeric selector setting of 9622. See Table 3-5, 6780 Switch Identifiers for a complete listing of numeric selector settings and what they represent. Note.
Troubleshooting and Replacement Procedures Replacement Procedures Replacement Procedures This subsection includes these replacement procedures: Procedure Page Replacing an MSEB 3-30 Replacing a PIC in an MSEB 3-30 Replacing a Fiber-Optic Cable Between an MSEB and a Switch-to-Node Port 3-31 Replacing a Fiber-Optic Cable Between Cluster Switches 3-31 Replacing a 6780 Switch 3-32 Replacing a Switch Logic Board (Slot 14) 3-33 Replacing a Node PIC (Slots 6 Through 9) 3-33 Replacing a Layer PIC
Troubleshooting and Replacement Procedures Replacing a Fiber-Optic Cable Between an MSEB and a Switch-to-Node Port Perform each step in the guided procedure up to and including removing the MSEB from the enclosure. Then refer to the guided procedure online help for instructions on replacing the PIC. When the PIC is replaced, use the guided procedure to reinstall the MSEB in the enclosure.
Troubleshooting and Replacement Procedures Replacing a 6780 Switch 2. Label the connectors of the replacement cable with the cluster switch names and port numbers to which the suspected bad cable is connected (such as X11, slot 12, port 1 at one end, and X13, slot 12, port 1 at the other end). If necessary, refer to the cabling tables in Appendix B, Cable Connections in a Layered Topology. 3. Physically route the replacement cable along the same path as the suspected bad cable. 4.
Troubleshooting and Replacement Procedures Replacing a CRU in a 6780 Switch Replacing a CRU in a 6780 Switch You also use the guided procedure to replace a Switch Logic Board or a Switch PIC in slots 6 through 9. The remaining CRUs in a 6780 switch require a manual procedure. Replacing a Switch Logic Board (Slot 14) To replace a 6780 switch logic board using the OSM guided procedure: 1. In the tree pane, navigate to the switch logic board you need to replace and rightclick. 2. Select Actions.
Troubleshooting and Replacement Procedures Replacing a CRU in a 6780 Switch Replacing a Zone PIC (Slots 2 and 3) The PICs is slots 2 and 3 are used for connections to another switch zone. To replace a PIC in slot 2 or 3: 1. Use OSM or SCF to check the health of the other zone PICs on the same fabric. If there are any problems on the other PICs, resolve them before continuing. 2. Check that the cables connected to the PIC are properly labeled. 3.
Troubleshooting and Replacement Procedures Diagnosing Performance Problems 1. Remove the power supply. 2. Wait at least five seconds and then install a replacement power supply in the same slot. Be sure it is fully seated. 3. Wait for power LED to light. Be sure the fault LED does not light. Diagnosing Performance Problems Diagnosis of performance problems in any environment involves multiple steps and requires extensive knowledge of performance fundamentals and methodologies.
Troubleshooting and Replacement Procedures Diagnosing Performance Problems ServerNet Cluster 6780 Operations Guide—525606-004 3- 36
4 SCF Commands for SNETMON and the ServerNet Cluster Subsystem This section describes the SCF commands that are supported specifically for SNETMON and the ServerNet cluster (SCL) subsystem. For a complete description of SNETMON, see Appendix A, ServerNet Cluster Software. For information on starting SNETMON, see Starting the ServerNet Cluster Monitor Process (SNETMON) on page 2-5. For information on adding SNETMON to the configuration database, see the ServerNet Cluster 6780 Planning and Installation Guide.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem SCF Objects for ServerNet Cluster SCF Objects for ServerNet Cluster These SCF objects are supported for SNETMON and the ServerNet cluster (SCL) subsystem: PROCESS Use this object to issue commands for SNETMON ($ZZSCL). SUBNET Use this object to gather information about connections within the ServerNet cluster subsystem ($ZZSCL). SUBSYS Use this object to issue commands for the ServerNet cluster subsystem itself ($ZZSCL).
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Summary States for the SCL SUBSYS Object Table 4-2. SCL SUBSYS Object Summary States Summary State Description STARTING The ServerNet cluster subsystem is attempting to establish ServerNet connectivity with the other nodes in the ServerNet cluster. STARTED The STARTING phase is complete. For all ServerNet nodes, either connectivity has been established, or the attempt failed. It is possible to be in the STARTED state with no connectivity.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STARTSTATE Attribute for the ServerNet Cluster Subsystem Figure 4-1. ServerNet Cluster Subsystem States STARTED STOP STARTING STOP STOPPING START STOPPED vst011.vsd STARTSTATE Attribute for the ServerNet Cluster Subsystem The start state configuration (STARTSTATE attribute) of the SCL subsystem SUBSYS object controls the way in which the ServerNet cluster monitor process joins the system to the ServerNet cluster.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem ALTER SUBSYS Command To set the STARTSTATE attribute, use the ALTER SUBSYS command. (See the ALTER SUBSYS Command on page 4-5.) If STARTSTATE is set to . . . Then STARTED The ServerNet cluster subsystem automatically moves into the STARTED logical state and joins the system to the ServerNet cluster.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Considerations STATSEVENT [ ON | OFF | LOCALONLY ] The STATSEVENT attribute specifies whether ServerNet cluster statistics are generated as EMS events (SCL event 1200). Statistical counters in all local processors for all nodes are reset at one-hour intervals even if statistics events are not generated. If statistics events are specified, statistics are generated at the end of each one hour interval.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem INFO Command START SUBSYS command before moving into the STARTED state and joining the system to the ServerNet cluster: > ALTER SUBSYS $ZZSCL, STARTSTATE STOPPED This command alters the STATSEVENT attribute for the ServerNet cluster subsystem.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Example The INFO SUBSYS command returns these fields: Start state shows the current value of the STARTSTATE attribute for the ServerNet cluster subsystem. Possible values are: STARTED The ServerNet cluster subsystem is configured to move into the STARTED state automatically and join the system to the ServerNet cluster after a system load.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem PRIMARY Command Stats event shows the current value of the STATSEVENT attribute for the ServerNet cluster subsystem. Possible values are: ON The ServerNet cluster subsystem is configured so that statistics events are generated by each local processor for every node in the cluster known to the local node, including the local node itself. This value is the default.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Example Example This command causes the previously configured backup processor for the ServerNet cluster monitor process (processor 3) to become the primary processor: > PRIMARY PROCESS $ZZSCL, 3 ServerNet Cluster 6780 Operations Guide—525606-004 4- 10
SCF Commands for SNETMON and the ServerNet Cluster Subsystem START Command START Command The START command moves the ServerNet cluster subsystem into the logical STARTED state and joins the system to the ServerNet cluster. START is a sensitive command. The START command syntax is: START [ /OUT file-spec / ] SUBSYS $ZZSCL OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem • • Example The ServerNet cluster monitor process has a list of all systems known to be in the ServerNet cluster. ServerNet connections are established with each system. If ServerNet connection attempts fail or if successful connections subsequently fail, periodic attempts are made to establish or reestablish the connection. Failures and successful reconnections are logged to the event log.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET Command STATUS SUBNET Command The STATUS SUBNET command returns information about the state of the ServerNet cluster subsystem connections to other systems within the ServerNet cluster. STATUS is a nonsensitive command.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Considerations PROBLEMS if specified, automatically queries the SNETMON processes in all nodes and displays any connectivity problems. The PROBLEMS option provides a quick way to check connectivity problems without having to issue separate STATUS SUBNET commands for each node. No other options can be specified with this option. Remote passwords must be established for nodes to report problems.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET Command Example STATUS SUBNET Command Example This example shows the STATUS SUBNET $ZZSCL command with no options specified: > STATUS SUBNET $ZZSCL SNETMON Remote ServerNet SNETMON SysName Num 0<--CPU States-->15 LocLH RemLH SCL EXPAND State,Cause Node------------------------------------------------------------------------1| RMT \SCQA35 35 1100,0000,0000,0000 UP 150 UP CONN CONN . . . . . .
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET Command Example SNETMON CPU States provides an individual path state summary code for the connections between the local node and a particular processor of a particular ServerNet node. The path state codes are as follows: Path State Code Description 0 The paths are down because the processor is down or the processor does not exist. 1 The paths and processor are up without errors.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET Command Example SNETMON State,Cause is the local SNETMON state and cause status, where the possible state codes for the ServerNet cluster subsystem are: State Code Description STRG Currently starting STRD Successfully started STPG Currently stopping STPD Stopped and not currently active The possible cause codes are: Cause Code Description UNKN Unknown cause PRTC Protocol error registering with SANMAN AUTO Automatic
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, PROBLEMS Command Example STATUS SUBNET, PROBLEMS Command Example This example shows the STATUS SUBNET $ZZSCL command with the PROBLEMS option: > STATUS SUBNET $ZZSCL, PROBLEMS Node SysName Nodes With Connectivity Problems ---------------------------------------------------------------------------1) \SCQA35 | ( 27, 28, 31, 32 ) 2) \SCQA40 | ( 27, 28, 31, 32 ) 3) \SCQA33 | ( 27, 28, 31, 32 ) 4) \SCQA36 | ( 27, 28, 31, 32 ) 5) \SC
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, RANGE Command Example Nodes With Connectivity Problems lists ServerNet node numbers of the nodes with which SysName is having connectivity problems. If there are no connectivity problems between SysName and the other nodes, “No connectivity problems” detected appears in the display. Other information, such as error messages, might appear in this field.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, DETAIL Command Example STATUS SUBNET, DETAIL Command Example This example shows a partial display of the STATUS SUBNET $ZZSCL, command with the DETAIL option. The command displays a series of tables containing status codes for paths between source and destination processors.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem 04 05 06 07 08 09 10 11 12 13 14 15 | | | | | | | | | | | | 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 STATUS SUBNET, DETAIL Command Example 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, DETAIL Command Example The STATUS SUBNET, DETAIL command returns these fields: DST is the destination processor (00 through 15) for ServerNet packets originating from processors listed in the left column of the table. SRC is the source processor (00 through 15) of ServerNet packets intended for processors listed in the top row of the table.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, DETAIL Command Example Table 4-3. Path State Values Returned by the STATUS SUBNET, DETAIL Command (page 2 of 3) No. Path State Value Meaning 11 Dst brought down conn The destination processor brought down direct ServerNet connectivity along the path because it believes the source processor is down or the source node is unreachable via ServerNet.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, DETAIL Command Example Table 4-3. Path State Values Returned by the STATUS SUBNET, DETAIL Command (page 3 of 3) No. Path State Value Meaning 25 Sft dwn unknown reason The path is in soft down state for an unknown reason. 26 Sft dwn max rvival tries The path is in hard down state because it failed and was automatically revived more than 10 times in the last 1-hour interval.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBNET, DETAIL Command Example If Path State Problems Are Indicated If the output of the STATUS SUBNET, DETAIL command indicates path-state problems, see Methods for Repairing ServerNet Connectivity Problems on page 3-18. You can also use the OSM Service Connection to investigate path-related problems. If an alarm appears on a component of the path, perform any associated repair actions. For details, see Using OSM Alarms on page 3-11.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STATUS SUBSYS Command STATUS SUBSYS Command The STATUS SUBSYS command returns information about the state of the ServerNet cluster subsystem. STATUS SUBSYS is a nonsensitive command. The ServerNet cluster subsystem state is maintained by the ServerNet cluster monitor process. There is no aggregate ServerNet cluster subsystem state.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem STOP Command STOP Command The STOP command terminates access to the ServerNet cluster subsystem in an orderly manner. It stops ServerNet cluster services on the local system, terminates ServerNet connections with other systems in the ServerNet cluster, and moves the subsystem to the STOPPED state. Note. The ServerNet cluster monitor process (SNETMON) itself does not stop. It remains running in the STARTED logical state.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Example 6. Only the subsystem state changes are logged. The individual path state changes are not logged. 7. On remote systems, when the ServerNet cluster monitor processes are notified of the STOP, they instruct their local processors to terminate ServerNet connectivity with the stopping system. These remote ServerNet cluster monitor processes then log the node disconnection to the event log.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem VERSION Command VERSION Command The VERSION command displays version information about the ServerNet cluster monitor process. VERSION is a nonsensitive command. The VERSION command syntax is: VERSION [ / OUT file-spec / ] { PROCESS | SUBNET | SUBSYS } $ZZSCL [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. DETAIL designates that complete version information is returned.
SCF Commands for SNETMON and the ServerNet Cluster Subsystem Examples SCF KERNEL - T9082G02 - (14JAN02) (03JAN02) identifies the product version of the SCF Kernel (T9082G02), the RVU date (14JAN02), and the compile date (03JAN02). SCL PM - T0294G08 - (01JUN03) - (28APR03) - (AAK) identifies the version of the SCF product module (T0294G08), the RVU date (01JUN03), the compile date (28APR03), and the software product revision (SPR) identifier (AAK).
5 SCF Commands for the External ServerNet SAN Manager Subsystem This section describes the SCF commands for the external ServerNet system area network (SAN) manager subsystem (SMN). The SMN subsystem is used to manage the external ServerNet SAN manager process (SANMAN). For a complete description of SANMAN, see Appendix A, ServerNet Cluster Software. For information on starting SANMAN, see Starting the External ServerNet SAN Manager Process (SANMAN) on page 2-4.
SCF Commands for the External ServerNet SAN Manager Subsystem SANMAN SCF Objects SANMAN SCF Objects These SCF objects are supported for SANMAN: CONN Use this object to gather information about external fabric connections to a cluster switch. PROCESS Use this object to issue commands for the external ServerNet SAN manager process. SUBSYS Use this object to control and display attributes that specify distances between zones .
SCF Commands for the External ServerNet SAN Manager Subsystem ALTER SUBSYS Command ALTER SUBSYS Command ALTER SUBSYS is a sensitive command. It allows you to change the values of SMN subsystem attributes, specifically the distance between nodes in a three-zone longhaul configuration. Changes take effect immediately. The command syntax is: ALTER [ /OUT file-spec/ ] SUBSYS $ZZSMN { , attribute-spec } OUT file-spec causes any SCF output for this command to be directed to the specified file.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations: Considerations: • • • • • Wild cards are not applicable to the ALTER SUBSYS command. You may alter only one attribute at a time. To specify values for all three distance attributes, use three ALTER SUBSYS commands.
SCF Commands for the External ServerNet SAN Manager Subsystem ALTER SWITCH Command ALTER SWITCH Command ALTER SWITCH is a sensitive command. It allows you to: • • • Assign or change a locator string for the cluster switch. Make the LEDs on the switch blink or stop blinking. Specify the fabric setting for 6770 switches.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations BLINK { ALL | FAULTLEDS | NONE } causes LEDs on the specified switch to blink as follows: For 6770 switches, causes all switch port LEDs to blink. ALL For 6780 switches, causes the fault LEDs on all CRUs to blink. FAULTLEDS Causes the fault LEDs for all CRUs on the 6780 switch to blink. FAULTLEDS is synonymous with ALL, but can only be used with a 6780 switch.
SCF Commands for the External ServerNet SAN Manager Subsystem ALTER SWITCH Command Examples This example blinks the LEDs on a 6780 switch in zone 3, layer 4 on the external ServerNet X fabric: > ALTER SWITCH $ZZSMN, FABRIC X, ZONE 3, LAYER 4, BLINK ALL If the command is successful, SCF displays: The ServerNet switch blink setting has been altered.
SCF Commands for the External ServerNet SAN Manager Subsystem DUMP SWITCH Command DUMP SWITCH Command The DUMP SWITCH command copies a memory image from a 6780 switch to a specified file on the local system.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations ONLINE specifies that the current memory image be collected. This is the default value. FORCED specifies that the current memory image be collected even if an image saved by firmware (as a result of a runtime error) has not been collected. Considerations • • • • The DUMP SWITCH command is a sensitive command and can be used only by a super-group user (255, n) ID. The DUMP SWITCH command is not valid for a 6770 switch.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO CONNECTION Command INFO CONNECTION Command The INFO CONNECTION command obtains information about the external ServerNet fabric connection to the nearest cluster switch. Unless specified otherwise, information appears for both fabrics. This information is returned by the external ServerNet SAN manager process ($ZZSMN). INFO is a nonsensitive command.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO CONNECTION Command Example In this example: Reponse Status is the general condition of the connection. For a list of possible values, see Response Status Enumeration on page 5-53. Rsp Status Detail is the specific condition of the connection. For a list of possible values, see Response Status Detail Enumeration on page 5-53. Switch Type indicates the type of switch on the fabric. Possible values are Model 6780 and Model 6770.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO CONNECTION Command Example CRU Slot is the slot number of the switch PIC that contains the port for this node connection. Valid Switch PIC slot numbers for node connections are 6, 7, 8, and 9. CRU Port is the port number (on the switch PIC) used for this node connection. Valid port numbers are 1 or 2. PIC Type (switch) is the type of switch PIC used for this node connection.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SUBSYS Command Table 5-2. Neighbor Checks Type of Neighbor Check Description No Query Assume Pass Performs no query of neighbor, assumes it passes, and enables the port No Query Assume Fail Performs no query of neighbor and assumes it fails. Disables port by default.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SUBSYS Command Example INFO SUBSYS Command Example -> INFO SUBSYS $ZZSMN SanMan - Info SUBSYS \YUMA.$ZZSMN Command time.... 18 Aug 2005, 8:36:39.377 Zone 1 to zone 2 distance..... 8000 meters Zone 1 to zone 3 distance..... 10000 meters Zone 2 to zone 3 distance.....
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SWITCH Command INFO SWITCH Command The INFO SWITCH command obtains information about a specific cluster switch. Unless specified otherwise, information is displayed for the X and Y switches. This information is returned by the external ServerNet SAN manager process ($ZZSMN). INFO is a nonsensitive command.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations Table 5-3. CRU Slots for the 6780 Switch Slot Number CRU Type 1 Maintenance PIC 2,3 Dual SMF or Quad MMF. (Used for zone-to-zone connections.) 4,5,10 Router Interconnect 6,7,8,9 Dual SMF. (Used for switch-to-node connections.) 11,12,13 Quad MMF. (Used for layer-to-layer connections.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SWITCH Command Example | Packetizer SvNetID | 0x000fc400 | 0x000fc400 | | | | | | Router Instances | 1-5 | 1-5 | | Router ASIC Type | Router 2 | Router 2 | | | | | | Switch Poll Intrvl | 49 seconds | 49 seconds | | | | | | Load Num Selector | 9612 | 9712 | | Prev Num Selector | 9612 | 9712 | | Curr Num Selector | 9612 | 9712 | | Globally Unique ID | 0x000008008e047f52 | 0x000008008e037f48 | | | | | | Firmware Revision | 5_20 | 5_20 | | Fir
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SWITCH Command Example Switch Type indicates the type of switch on the fabric. The 6780 switch is used in the layered topology. Switch Zone is the zone within the layered topology where the switch is located. Possible values are 1, 2, or 3. Switch Layer is the layer within the switch zone. Possible values are 1, 2, 3, or 4. The switch layer is equivalent to the switch module number, and the two values should match.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SWITCH Command Example Load Num Selector represents a supported configuration image that is loaded in the 6780 switch based on the numeric selector setting when the switch was reset. Each switch in a layered topology has a unique 4-digit numeric selector setting. For a list of possible numeric selector settings, see Table 3-5 on page 3-29. Prev Num Selector is the previous value of the numeric selector.
SCF Commands for the External ServerNet SAN Manager Subsystem INFO SWITCH Command Example Image A VPROC (FPGA) is the VPROC string for the version of the FPGA stored in image A on the cluster switch. Image B VPROC (FPGA) is the VPROC string for the version of the FPGA stored in image B on the cluster switch. Config Version ID is the version of the configuration running on the cluster switch.
SCF Commands for the External ServerNet SAN Manager Subsystem LOAD SWITCH Command LOAD SWITCH Command The LOAD SWITCH command is a sensitive command. It allows you to download a configuration, firmware, or field-programmable gate array (FPGA) file from the server to the cluster switch. Note. The LOAD command is intended for service providers only. To load firmware, configuration, or FPGA for a cluster switch, use the OSM Service Connection.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations CONFIG file, POSITION id, TOPOLOGY topo-id specifies the configuration file, position, and topology to be configured for a 6770 switch in one of the star topologies. CONFIG file specifies the name of the configuration file to be downloaded, specified in the standard file system external format. The file must be located on the local system.
SCF Commands for the External ServerNet SAN Manager Subsystem LOAD SWITCH Command Examples check the value of the Hardware Data ID attribute. If the value is MISMATCH, perform a hard reset. If the value is match, perform a soft reset. • • Wild cards are not supported for the LOAD SWITCH command. You must perform a hard reset of the 6780 switch after an FPGA download. LOAD SWITCH Command Examples This example downloads the firmware file $SYSTEM.SYS05.
SCF Commands for the External ServerNet SAN Manager Subsystem PRIMARY PROCESS Command PRIMARY PROCESS Command The PRIMARY PROCESS command is a sensitive command. It causes a processor switch, where the backup processor becomes the primary processor, and the primary processor becomes the backup processor. It does not cause the ServerNet SAN manager process to stop running.
SCF Commands for the External ServerNet SAN Manager Subsystem RESET SWITCH Command RESET SWITCH Command The RESET SWITCH command is a sensitive command. It allows you to perform a hard or soft reset of a cluster switch. The RESET command syntax is: RESET [ / OUT file-spec / ] SWITCH $ZZSMN { , FABRIC { X | Y } | , NEAREST { X | Y } } { , FABRIC { X | Y } , ZONE znum , LAYER lnum } { HARD | SOFT } OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations Considerations • • The RESET command is a sensitive command and can be used only by a supergroup user (255, n) ID. Wild cards are not supported for the RESET command.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION Command STATUS CONNECTION Command The STATUS CONNECTION command obtains status information for the external ServerNet fabric connections between the MSEB of the local node and the switch port. This information is returned by the external ServerNet SAN manager process ($ZZSMN). STATUS CONNECTION is a nonsensitive command.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION Command Example STATUS CONNECTION Command Example This example shows the STATUS CONNECTION $ZZSMN command: -> scf status conn $zzsmn |--------------------|---------------------------|---------------------------| | Response Status | ok | ok | | Rsp Status Detail | No Status Detail | No Status Detail | |--------------------|---------------------------|---------------------------| | Fabric Access | No Error | No Error | |--------
SCF Commands for the External ServerNet SAN Manager Subsystem • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • STATUS CONNECTION Command Example NO NNA PIC WRONG FABRIC BAD SWITCH PORT NUMBER BAD SCB LOADED BAD SWITCH PIC TYPE BAD SWITCH GUID NODE NUMBER MISMATCH NNA VERIFY FAIL SP I/O LIBRARY CALL ERROR SYSTEM POWER UP NO MSEB CONFIG RECORD BAD MSEB CONFIG RECORD MSEB CONFIG FETCH ERROR INTERNAL SYS FABRIC DOWN BOTH LEDS SET TNET INITIALIZATION ERROR INVALID FABRIC PARAMETER TOO MAN
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION Command Example Port Status indicates the status of the MSEB or switch port. Possible values for the MSEB are: • • • • • link alive LINK DEAD RESET LA, DISABLED UNINSTALLED Possible values for the switch port are listed in Table 5-4, Router Status Codes. Link Lvl Rx indicates whether Link Receive is enabled. Possible values are enabled or DISABLED. Link Lvl Tx indicates whether Link Transmit is enabled.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION, NNA Command Example CRU Port is the transceiver port number (on the switch PIC) used for this node connection. Valid port numbers are 1 or 2. Transceiver Enabled indicates whether the transceiver port for this connection is enabled Transceiver Status indicates the state of the transceiver port for this connection. LED State indicates whether the transceiver port link-alive LED is on.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION, NNA Command Example In this example: Response Status is the general condition of the connection. For a list of possible values, see Response Status Enumeration on page 5-53. Rsp Status Detail is the specific condition of the connection. For a list of possible values, see Response Status Detail Enumeration on page 5-53.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS CONNECTION, NNA Command Example Low Threshold shows the contents of the NNA low threshold registers (outbound and inbound) for both external fabrics. The low threshold registers are used to set the lower limit for comparison to the accumulator contents. Accumulator shows the contents of the NNA accumulators (outbound and inbound) for both external fabrics. DID Check Error indicates whether a Destination ServerNet ID check error occurred.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command STATUS SWITCH Command The STATUS SWITCH command obtains status information for the cluster switches. This information is returned by the external ServerNet SAN manager process ($ZZSMN). STATUS SWITCH is a nonsensitive command.
SCF Commands for the External ServerNet SAN Manager Subsystem Considerations ROUTER specifies that router register data be displayed. This option is valid only for 6770 switches. ROUTER rnum, [ PORT pnum ] specifies that router register and neighbor data be displayed. rnum must be in the range 1 through 5. Specifying the optional PORT parameter limits the display to the specified router port. pnum must be in the range 0 through 11. This option is valid only for 6780 switches. Note.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command Example STATUS SWITCH Command Example This example shows the STATUS SWITCH $ZZSMN command: > SCF STATUS SWITCH $ZZSMN STATUS SWITCH X Fabric Y Fabric |----------------------------------------------------------------------------| | Response Status | ok | ok | | Rsp Status Detail | No Status Detail | No Status Detail | |--------------------|---------------------------|---------------------------| | Switch Type | Model 6780 |
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command Example | CRU Slot (06) | Dual SMF en off | Dual SMF en off | | CRU Slot (07) | Dual SMF en off | Dual SMF en off | | CRU Slot (08) | Dual SMF en off | Dual SMF en off | | CRU Slot (09) | Quad SMF AB off | Dual SMF en off | | CRU Slot (10) | Rtr InterConn en off | Rtr InterConn en off | | CRU Slot (11) | Quad MMF en off | Quad MMF en off | | CRU Slot (12) | Quad MMF en off | Quad MMF en off | | CRU Slot (13) | Quad MMF ER
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command Example Last Hard Rset indicates the time (in Greenwich mean time) of the last hard reset command. Last Soft Rset indicates the time (in Greenwich mean time) of the last soft reset command. Soft Reset SrcSNID is the ServerNet ID of the client that issued a soft reset command if the last reset command was a soft reset.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command Example Config Image B indicates the condition of the configuration stored in Image B of the switch. Two images are stored for fault tolerance. Possible values are ok, CRC ERROR, and UNKNOWN. Logic Board Temp indicates the temperature (in degrees centigrade) of the switch logic board. Power (nn) indicates the status for the switch power supply in slot nn.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH Command Example State is the state of the switch CRU in slot nn. Possible values are: DS Disabled ER Error en Enabled F-LED is the state of the fault LED on the switch CRU in slot nn. Possible values are BL (blinking), ON, and off. If there are transceiver problems, SEE CRU STAT appears across the State and FLED columns. Use the CRU option of the STATUS SWITCH command to get more information. Table 5-4.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, ONLY, CRU Command Example STATUS SWITCH, ONLY, CRU Command Example This example shows the STATUS SWITCH command with the ONLY and CRU options: > SCF STATUS SWITCH $ZZSMN, ONLY X, CRU 6 STATUS SWITCH X Fabric Y Fabric |----------------------------------------------------------------------------| | Response Status | ok | | | Rsp Status Detail | No Status Detail | | |--------------------|---------------------------|-----------------
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, ONLY, CRU Command Example CRU Type is the type of CRU located in the specified slot. CRU State is the state of the specified CRU. Possible values are enabled, DISABLED, ABSENT, and ERROR. CRU Fault LED indicates whether the fault LED for the specified CRU is on. Transceiver n is the type of transceiver in port n of the specified CRU. Transceiver Enabled indicates whether the transceiver in port n of the specified CRU is enabled.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, ROUTER Command Example STATUS SWITCH, ROUTER Command Example This example shows the STATUS SWITCH command with the ROUTER option: > STATUS SWITCH $ZZSMN, ROUTER 2 STATUS SWITCH X Fabric Y Fabric |----------------------------------------------------------------------------| | Response Status | ok | ok | | Rsp Status Detail | No Status Detail | No Status Detail | |--------------------|---------------------------|-------------------
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, ROUTER Command Example Switch Zone is the zone where the switch is located within the layered topology. Possible values are 1, 2, or 3. Switch Layer is the layer the switch occupies within the switch zone. Possible values are 1, 2, 3, or 4. Router Instance is the router instance number. Possible values are in the range 1 through 5.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, ROUTER Command Example CRU S,P is the slot number (S) and port number (P) of the switch PIC to which the router port is connected. For a router interconnect PIC, only the slot number appears because it has no ports. Port Neighbor Data contains information about the neighbor port, if it is a connected external port.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, SWITCHPORTS Command Example Expected GUID is the expected Globally Unique ID of the neighbor switch. Received GUID is the Globally Unique ID received from the neighbor switch.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, SWITCHPORTS Command Example Rsp Status Detail is the specific condition of the connection. For a list of possible values, see Response Status Detail Enumeration on page 5-53 Switch Type is the type of switch as indicated by the switch model number. The SWITCHPORTS option is valid only for 6780 switches. Switch Zone is the zone within the layered topology where the switch is located. Possible values are 1, 2, or 3.
SCF Commands for the External ServerNet SAN Manager Subsystem STATUS SWITCH, SWITCHPORTS Command Example Stat indicates the status of the transceiver. Possible values are ok and FAULT. LED indicates the state of the transceiver LED. Possible values are on, OF (off), and BL (blinking). OS indicates the state of the optical signal for the transceiver. Possible values are pr (present) and LOS (lost optical signal).
SCF Commands for the External ServerNet SAN Manager Subsystem VERSION PROCESS Command VERSION PROCESS Command The VERSION PROCESS command displays release version update (RVU) and software product revision (SPR) information about the ServerNet SAN manager process. VERSION is a nonsensitive command. The VERSION command syntax is: VERSION [ / OUT file-spec / ] PROCESS $ZZSMN [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for the External ServerNet SAN Manager Subsystem VERSION PROCESS Command Examples GUARDIAN - T9050 - (Q06) identifies the SPR of the NonStop Kernel operating system. SCF KERNEL - T9082G02 - (30APR03) (29JAN02) identifies the product number and product version of the SCF Kernel, the RVU date, and the compile date. SMN PM - T0502G08 - (11AUG03) - (28APR03) - (AAL) identifies the product number and product version of the SCF product module, the RVU date, the compile date, and the SPR identifier.
SCF Commands for the External ServerNet SAN Manager Subsystem VERSION SUBSYS Command VERSION SUBSYS Command The VERSION SUBSYS command displays release version update (RVU) and software product revision (SPR) information about the ServerNet SAN manager process. VERSION is a nonsensitive command. The VERSION command syntax is: VERSION [ / OUT file-spec / ] SUBSYS $ZZSMN [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
SCF Commands for the External ServerNet SAN Manager Subsystem VERSION SUBSYS Command Examples GUARDIAN - T9050 - (Q06) identifies the SPR of the NonStop Kernel operating system. SCF KERNEL - T9082G02 - (17DEC04) (30NOV04) identifies the product number and product version of the SCF Kernel, the RVU date, and the compile date. SMN PM - T0502G08 - (15NOV05) - (11OCT05) - (AAQ) identifies the product number and product version of the SCF product module, the RVU date, the compile date, and the SPR identifier.
SCF Commands for the External ServerNet SAN Manager Subsystem Response Status Enumeration Response Status Enumeration This list contains the values that might appear in the Response Status field of the INFO CONNECTION, INFO SWITCH, STATUS CONNECTION, and STATUS SWITCH command displays: • • • • • • • • • • • • • • • • • ok LOW RESOURCES INVALID PARAMETER NO RESPONSE NEGATIVE ACKNOWLEDGMENT PARTIAL RESPONSE ABORT DUE TO POWER FAIL FILE DOWNLOAD FAILED OWNERSHIP ERROR NOT SUPPORTED CRC ERROR SWITCH OBJECT
SCF Commands for the External ServerNet SAN Manager Subsystem • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Response Status Detail Enumeration TOO MANY SWITCHES MEMORY ALLOCATION FAILURE FILE NAME CONVERSION ERR FILE OPEN ERROR BAD FILE CODE FILE READ ERROR BAD FILE HEADER SIZE EMPTY FILE BAD FILE TYPE FILE POSITION CALL FAILED BAD READ SIZE BAD DIRECTORY COUNT NO MODULE BAD DOWNLOAD BLOCK COUNT BAD ATTRIBUTE LENGTH WRONG SUBSYSTEM ID WRONG ATTRIBUTE TYPE W
SCF Commands for the External ServerNet SAN Manager Subsystem • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Response Status Detail Enumeration INITIAL CRC CHECK FAILED FLASH IMAGE UPDATE FAILED SEEROM UPDATE FAILED BAD TYPE ID SEEROM BOUNDS ERROR BAD CRU SLOT BAD SEEROM INSTANCE BAD USER DATA CRC UNDEFINED BITS TO BLINK BAD LED STATE INVALID ASIC TYPE INVALID ASIC INSTANCE INVALID ASIC REG ADDRESS INVALID NUM OF REGISTERS TEST VALUE MISMATCH LOCK HIERARCHY
SCF Commands for the External ServerNet SAN Manager Subsystem • • • • Response Status Detail Enumeration NACK SAVED DUMP EXISTS NACK INVALID DUMP ACTION NACK INVALID DUMP OPTION FILE ALREADY EXISTS ServerNet Cluster 6780 Operations Guide— 525606-004 5- 56
6 SCF Error Messages This section describes the types of error messages generated by SCF and provides the cause, effect, and recovery information for the SCF error messages specific to the ServerNet cluster subsystem and the external system area network manager process (SANMAN).
SCF Error Message Help SCF Error Messages Like common errors, subsystem-specific error messages are divided into two classes—critical and noncritical: • • Critical messages can be serious, such as the notification of software errors for which there is no automatic recovery. Critical messages are preceded by an E. Noncritical messages are generally informational. Noncritical messages are preceded by a W.
ServerNet Cluster (SCL) Error Messages SCF Error Messages SCL Error 00002 SCL E00002 Duplicate attribute Cause. You specified the same attribute more than once in the command. Effect. The command is not executed. SCF waits for the next command. Recovery. Remove the duplicate attribute and reissue the command. SCL Error 00003 SCL E00003 Internal error. Case value out of range. Cause. An invalid case value was generated with no associated case label. Effect. The command is not executed.
ServerNet Cluster (SCL) Error Messages SCF Error Messages SCL Error 00006 SCL E00006 Not supported by the down-version system (version). Cause. The command was rejected by the ServerNet cluster monitor process ($ZZSCL) because the information requested by the command is for an earlier product version. Effect. The command is not executed. SCF waits for the next command. Recovery. It is not possible to request information from a system running an incompatible product version of SCF.
ServerNet Cluster (SCL) Error Messages SCF Error Messages Recovery. Verify the database record using the SCF INFO command. If necessary, reload the system using a saved version of the system configuration database. If the problem persists, contact your service provider. (See If You Have to Call Your Service Provider on page 6-20.) SCL Error 00009 SCL E00009 Processor switch failed, reason-text. reason-text is a text string that describes the reason the processor switch failed. Cause.
ServerNet Cluster (SCL) Error Messages SCF Error Messages SCL Error 00012 SCL E00012 Subsystem shutdown failure. Cause. The subsystem failed to initiate shutdown processing. Effect. The command is not executed. SCF waits for the next command. Recovery. Check the event logs for error messages. Once you have resolved any problems, reissue the command. SCL Error 00013 SCL E00013 Trace command error. reason-text. error-code. reason-text is a text string that describes the reason the processor switch failed.
ServerNet Cluster (SCL) Error Messages SCF Error Messages SCL Error 00015 SCL E00015 MSGMON. BACKUP attribute is not allowed when tracing Cause. A TRACE operation of a MSGMON process specified the BACKUP option, which is not allowed. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command without the BACKUP attribute.
SANMAN (SMN) Error Messages SCF Error Messages SANMAN (SMN) Error Messages The ServerNet SAN Manager subsystem SCF error messages are listed in numeric order. SMN Error 00001 SMN E00001 Internal error: Result code num returned from sysproc. num is the result code. sysproc is the name of the system procedure. Cause. An internal error was caused by an unexpected return code from a system procedure. Effect. The command is not executed. SCF waits for the next command. Recovery. Contact your service provider.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00004 SMN E00004 Not supported by the down revision SANMAN; SPI version version-num Cause. The command was rejected by the external ServerNet SAN manager process ($ZZSMN) because the information requested by the command is for an earlier product version. Effect. The command is not executed. SCF waits for the next command. Recovery. You cannot request information from a system running an incompatible version of SCF.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00007 SMN E00007 Trace command error. reason-text. error-code reason-text is a text string that describes the reason the processor switch failed. error-code is the error code. Cause. The subsystem could not execute the TRACE PROCESS command. Effect. The command is not executed. SCF waits for the next command. Recovery. Retype the command, making sure you type it correctly.
SANMAN (SMN) Error Messages SCF Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Verify the database record using the SCF INFO SUBSYS command. Also, check the EMS log for an occurrence of SMN event 4224. If necessary, reload the system using a saved version of the system configuration database. If the problem persists, contact your service provider. (See If You Have to Call Your Service Provider on page 6-20.
SANMAN (SMN) Error Messages SCF Error Messages Recovery. Reissue the command first specifying the X switch and then again specifying the Y switch. SMN Error 00034 SMN E00034 This command can only be executed interactively. Cause. A sensitive command was executed noninteractively (that is, with a command file). Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command from an interactive SCF session.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00038 SMN E00038 FABRICSETTING attribute is not allowed for the specified switch. Cause. The command specified a FABRICSETTING attribute, but the specified switch does not support the FABRICSETTING attribute. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. SMN Error 00039 SMN E00039 An FPGA file can not be downloaded to the specified switch. Cause.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00042 SMN E00042 Switch incorrectly specified. Cause. The command was issued with an incorrect switch specifier. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. The FABRIC, ZONE, LAYER specification can be used only for switches in a layered topology. SMN Error 00043 SMN E00043 POSITION attribute is not allowed for the specified switch. Cause.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00046 SMN E00046 TOPOLOGY attribute is not allowed for the specified switch. Cause. The command specified a TOPOLOGY attribute, but the specified switch does not support the TOPOLOGY attribute. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. SMN Error 00047 SMN E00047 HARD or SOFT must be specified. Cause. Neither HARD nor SOFT was specified in the command. Effect.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00050 SMN E0050 Incorrect combination of DUMP SWITCH attributes. Cause. The command specified an incorrect combination of DUMP SWITCH attributes. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. Refer to the help text for STATUS SWITCH. SMN Error 00051 SMN E0051 FAULTLEDS attribute is not allowed for the specified switch Cause.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00070 SMN E00070 LOCATOR string longer that 32 characters. Cause. The LOCATOR string specified exceeds the 6770 switch limit of 32 characters. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. SMN Error 00071 SMN E00071 Incorrect specification of model 6770 switch. Cause. The command incorrectly specified a switch. Specify a model 6770 switch using either the NEAREST or FABRIC specifier.
SANMAN (SMN) Error Messages SCF Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. SMN Error 00075 SMN E00075 ROUTER router-instance is not allowed for model 6770 switches. Cause. The command specified a router-instance value. To display ROUTER status from a 6770 switch, omit the router-instance value. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command.
SANMAN (SMN) Error Messages SCF Error Messages SMN Error 00082 SMN E00082 PORT router-port-number must be 0 to 11 for 6780 switch. Cause. When displaying router port status from a 6780 switch, router-portnumber must be in the range 0 to 11. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command.
If You Have to Call Your Service Provider SCF Error Messages If You Have to Call Your Service Provider If the recovery for an error message indicates you should contact your service provider, be prepared to supply the following information. (If the error caused SCF to terminate, reenter SCF.) 1. Enter a LOG command to collect the following displays into a single file. For example: -> LOG PROBLEM ! 2.
A ServerNet Cluster Software This section describes the software components of a ServerNet cluster including: NonStop Kernel Message System on page A-1 MSGMON on page A-2 SANMAN Subsystem on page A-2 ServerNet Cluster Subsystem on page A-3 SNETMON on page A-3 Expand-Over-ServerNet Line-Handler Processes on page A-5 Figure A-1 is a logical diagram that shows the interaction of ServerNet cluster processes. Figure A-1.
MSGMON ServerNet Cluster Software MSGMON MSGMON is a monitor process that resides in each processor of a server and executes functions required by the message system. It handles communications between SNETMON and individual processors. MSGMON was created to relieve the system monitor subsystem from being involved in ServerNet cluster duties. It is a helper for SNETMON. MSGMON is a persistent process but not a process pair.
ServerNet Cluster Subsystem ServerNet Cluster Software The External System Area Network Manager is a process pair that runs in every NonStop S-series server connected to a ServerNet cluster. SANMAN can be run in any processor. This list shows the details for the SANMAN process: Abbreviation SANMAN Description External system area network manager process Subsystem Name SMN Subsystem Acronym ZSMN Subsystem Number 237 Recommended Generic Process Name $ZZKRN.
SNETMON ServerNet Cluster Software • • • • • • Detects the presence of other systems in the ServerNet cluster and establishes the ServerNet message-system connections. Monitors and responds to events that affect the message-system connections, such as processor failures, reloads, and path events. Receives path-event information from the individual processors in the node and translates this information into system-connection status information and EMS events.
ServerNet Cluster Software Expand-Over-ServerNet Line-Handler Processes SNETMON Interaction With the Expand Line-Handler Processes SNETMON interacts with the Expand line-handler processes using the NAM protocol to: • • • Enable Expand line-handler processes to synchronize with each other during startup. Enable detection that the remote Expand line-handler process is down. Inform the appropriate local line-handler process when the ServerNet cluster connection to a remote node goes down.
Expand-Over-ServerNet Line-Handler Processes ServerNet Cluster Software This list summarizes information about the line-handler process: Description Expand-over-ServerNet line-handler process Type 63 Subtype 4 Profile PEXPSSN ASSOCIATEDEV Default $ZZSCL (SNETMON) Figure A-2 shows the Expand-over-ServerNet line-handler processes for a four-node ServerNet cluster.
Expand-Over-ServerNet Line-Handler Processes ServerNet Cluster Software Figure A-2. Line-Handler Processes in a Four-Node Cluster \NODE1 (Expand Node Number 001) $SC002 $SC003 $SC004 $SC001 \NODE4 (Expand Node Number 004) $SC001 X-Fabric $SC002 $SC004 $X252 $SC003 Y -Fabric \NODE2 (Expand Node Number 002) $SC003 $SC004 $SC001 $SC002 \NODE3 (Expand Node Number 003) Key Configured Single-Line Path VST092.
ServerNet Cluster Software Expand-Over-ServerNet Line-Handler Processes ServerNet Cluster 6780 Operations Guide—525606-004 A- 8
B Cable Connections in a Layered Topology This appendix list the cable connections between cluster switches in a layered topology. For more detail on cabling, see the ServerNet Cluster 6780 Planning and Installation Guide. • • • Connections between the layers within a zone appear in Table B-1. Connections between two zones appear in Table B-2 and Table B-3. Connections for three zones appear in Table B-4 and Table B-5 Handling Fiber-Optic Cables Caution.
Connections Between Layers Cable Connections in a Layered Topology Connections Between Layers Each layer cable connects to another switch in the same fabric and group with the same PIC slot and port number. Table 6-1 shows the connections for zone 1. Connections between layers are similar for zones 2 and 3. Table B-1.
Cable Connections in a Layered Topology Connections Between Two Zones Connections Between Two Zones Table B-2 and Table B-3 list the X-fabric and Y-fabric connections between zones in a two-zone cluster. . Table B-2. X Fabric Connections Between Two Zones Connects to ...
Cable Connections in a Layered Topology Connections Between Two Zones eft Table B-3. Y Fabric Connections Between Two Zones Connects to ...
Connections For Three Zones Cable Connections in a Layered Topology Connections For Three Zones Table B-4 and Table B-5 list the X-fabric and Y-fabric connections between zones in a three-zone cluster. Table B-4. X Fabric Connections for a Three-Zone ServerNet Cluster Connects to ...
Connections For Three Zones Cable Connections in a Layered Topology Table B-5. Y Fabric Connections for a Three-Zone ServerNet Cluster Connects to ...
C Part Numbers For part numbers, refer to: NTL Support and Service Library > Service Information > Part Numbers > Part Number List for NonStop S-Series Customer Replaceable Units (CRUs) > ServerNet Switch (Model 6780).
Part Numbers ServerNet Cluster 6780 Operations Guide—525606-004 C- 2
D ESD Information Observe these ESD guidelines when servicing electronic components: • • • • • • • Obtain an electrostatic discharge (ESD) protection kit and follow the directions that come with the kit. You can purchase an ESD kit from HP (T99247-A00) or from a local electronics store. Ensure that your ESD wriststrap has a built-in series resistor and that the kit includes an antistatic table mat.
ESD Information Figure D-1. Using ESD Protection When Servicing CRUs System enclosure (appearance side) ESD wriststrap with grounding clip ESD wriststrap clipped to door latch stud ESD floor mats ESD antistatic table mat. Mat should be connected to a soft ground (1 megohm min. to 10 megohm max.) Clip 15-foot straight ground cord to screw on grounded outlet cover. VST 001.
E Numeric Selector Settings for the Long-Distance Option Specific numeric selector settings are reserved for the long-distance option of the layered topology. This option is available only if all required software components are installed. For a list of numeric selectors and other details about the long-distance option, see the ServerNet Cluster 6780 Planning and Installation Guide .
Numeric Selector Settings for the Long-Distance Option ServerNet Cluster 6780 Operations Guide— 525606-004 E- 2
Safety and Compliance Regulatory Compliance Statements The following warning and regulatory compliance statements apply to the products documented by this manual. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Regulatory Compliance Statements Safety and Compliance Taiwan (BSMI) Compliance Japan (VCCI) Compliance This is a Class A product based on the standard or the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case the user may be required to take corrective actions.
Regulatory Compliance Statements Safety and Compliance DECLARATION OF CONFORMITY Supplier Name: HP COMPUTER CORPORATION Supplier Address: HP Computer Corporation, NonStop Enterprise Division 10300 North Tantau Ave Cupertino, CA 95014 USA Represented in the EU By: Hewlett Packard Company P.O.
Consumer Safety Statements Safety and Compliance Consumer Safety Statements Customer Installation and Servicing of Equipment The following statements pertain to safety issues regarding customer installation and servicing of equipment described in this manual. Do not remove the covers of an HP ServerNet switch. CAUTION: This unit has more than one power supply cord. Disconnect all power supply cords to completely remove power from this unit. Attention: Cet appareil comporte plus d'un cordon d'alimentation.
Index Numbers E 6780 switch numeric selector 3-28, 3-29 troubleshooting 3-6 Error messages SCL 6-2/6-7 SMN 6-8/6-19 ESD guidelines D-1 Event messages 3-25 Expand-over-ServerNet lines monitoring 1-21 troubleshooting 3-16 External fabric attributes 1-7 testing 3-23 A Alarm Detail dialog box 3-12 Alarms 3-11, 3-13 Attributes external fabric resource 1-7 local node resource 1-7 MSEB 1-5 PIC 1-5 remote node resource 1-7 ServerNet cluster resource 1-6 switch resource 1-8 B Bend radius B-1 C Cables connectio
L Index L R LEDs 3-26 Line-handler process, monitoring 1-21 Link to node 3-4 Loopback See Internal Loopback Test Remote node attributes 1-7 checking communications with 3-18 Repair actions 3-12 Replacement procedures 3-30 M S MSEB attributes 1-5 LEDs 3-26 replacement 3-30, 3-32 troubleshooting 3-5 MSGMON aborting 2-3 functions 2-2, A-2 starting 2-3 SANMAN aborting 2-4 defined 2-2 functions A-3 restarting 2-5 SCF commands 5-1 starting 2-4 switching primary and backup 2-9 SCF ABORT PROCESS command 2-
S Index SCF (continued) PRIMARY PROCESS command 3-18, 3-19, 4-9, 5-24 remote 1-2 RESET SWITCH command 5-25, 5-26 SANMAN objects 5-2 sensitive commands 4-2 ServerNet cluster objects 4-2 START PROCESS command 2-7 START SERVERNET command 3-19 START SUBSYS command 3-19, 4-11 STATS LINE command 1-22 STATS PATH command 1-23 STATUS CONNECTION command 5-28 STATUS CONNECTION, NNA command 5-31 STATUS DEVICE command 1-21 STATUS LINE command 1-22 STATUS PATH, DETAIL command 1-22 STATUS PROCESS command 1-19 STATUS SER
T Index T Special Characters Tree pane 1-6 Troubleshooting 6780 switch 3-6 Expand-over-ServerNet lines 3-16 Expand-over-ServerNet line-handler processes 3-16 external fabric 3-3 fiber-optic ServerNet cable 3-6 guided procedures interface 3-2 internal fabric 3-2 MSEB 3-5 MSGMON 3-14 PIC installed in MSEB 3-5 procedures 3-1/3-30 remote node communication 3-3 SANMON 3-15 ServerNet cable 3-6 ServerNet communications 3-2 SNETMON 3-13 switch fans 3-8 switch logic board 3-7 switch PICs 3-7 switch ports 3-7 swi
