ServerNet/FX Adapter Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Table Of Contents

ServerNet/FX Adapter

Configuration and

Management Manual

Abstract

This manual explains how to configure, operate, and manage the ServerNet/FX

adapter subsystem on HP NonStop™ S-series servers. Included are detailed

descriptions of the Subsystem Control Facility (SCF) commands used with the

ServerNet/FX adapter subsystem and a quick-reference section showing the command

syntax. It is assumed that the reader is already familiar with the Expand subsystem. In

this manual, the term ServerNet/FX adapter refers to the ServerNet/FX and the

ServerNet/FX 2 adapter hardware.

Product Version

G07

Supported Release Version Updates (RVUs)

This manual supports G06.22 and all subsequent G-series RVUs until otherwise

indicated in a new edition.

Part Number Published

426872-002 April 2004

Summary of content (176 pages)

PAGE 1
ServerNet/FX Adapter Configuration and Management Manual Abstract This manual explains how to configure, operate, and manage the ServerNet/FX adapter subsystem on HP NonStop™ S-series servers. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the ServerNet/FX adapter subsystem and a quick-reference section showing the command syntax. It is assumed that the reader is already familiar with the Expand subsystem.
PAGE 2
Document History Part Number Product Version Published 143002 G05.
PAGE 3
ServerNet/FX Adapter Configuration and Management Manual Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information Figures Tables vii About This Manual ix Overview ix Who Should Use This Manual ix How This Manual Is Organized ix Where to Get More Information x Notation Conventions x 1.
PAGE 4
Contents 2. Configuring the ServerNet/FX Adapter Subsystem (continued) 2. Configuring the ServerNet/FX Adapter Subsystem (continued) Starting the FOX Monitor Process 2-6 Using the SCF START PROCESS Command 2-6 Example 2-6 Verifying the FOX Monitor Process 2-6 Example 2-7 Creating ServerNet/FX Adapter LBUs 2-7 Using the SCF ADD LBU Command 2-7 ServerNet/FX 2 Adapter LBU Examples 2-7 ServerNet/FX Adapter LBU Examples 2-8 Adding a NonStop S-Series Server to a FOX Ring Overview 2-8 3.
PAGE 5
4. ServerNet/FX Adapter Subsystem SCF Commands Contents 4.
PAGE 6
4. ServerNet/FX Adapter Subsystem SCF Commands (continued) Contents 4. ServerNet/FX Adapter Subsystem SCF Commands (continued) STATUS Command 4-42 STATUS SUBNET Command 4-42 STATUS PROCESS Command 4-48 STATUS LBU Command 4-49 STATUS PATH Command 4-53 STOP Command 4-60 Considerations 4-60 Example 4-60 VERSION Command 4-61 Examples 4-61 5.
PAGE 7
A. SCF Command Summary (continued) Contents A. SCF Command Summary (continued) STATS Command A-2 STATUS SUBNET Command A-3 STATUS PROCESS Command A-3 STATUS LBU Command A-3 STATUS PATH Command A-3 STOP Command A-3 VERSION Command A-3 B. Error Messages FOX SCF Command Error Messages B-1 C. ServerNet/FX Adapter Self-test Codes Glossary Index Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 3-1. Figure 3-2. Figure 3-3. Figure 4-1.
PAGE 8
Contents ServerNet/FX Adapter Configuration and Management Manual—426872-002 vi
PAGE 9
What’s New in This Manual Manual Information ServerNet/FX Adapter Configuration and Management Manual Abstract This manual explains how to configure, operate, and manage the ServerNet/FX adapter subsystem on HP NonStop™ S-series servers. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the ServerNet/FX adapter subsystem and a quick-reference section showing the command syntax. It is assumed that the reader is already familiar with the Expand subsystem.
PAGE 10
What’s New in This Manual New and Changed Information ServerNet/FX Adapter Configuration and Management Manual—426872-002 viii
PAGE 11
About This Manual This section offers a general overview of this manual and outlines this manual’s intended audience. Overview The ServerNet/FX Adapter Configuration and Management Manual explains how to configure, operate, and manage the ServerNet/Fiber eXtension (ServerNet/FX) adapter subsystem on a NonStop S-series server.
PAGE 12
Where to Get More Information About This Manual Section Title This section... 4 ServerNet/FX Adapter Subsystem SCF Commands Provides a detailed description and the complete syntax for the Subsystem Control Facility (SCF) commands applicable to the ServerNet/FX adapter subsystem and provides examples of how to use those commands. 5 Troubleshooting Provides troubleshooting information for the ServerNet/FX adapter subsystem.
PAGE 13
About This Manual General Syntax Notation This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters.
PAGE 14
General Syntax Notation About This Manual … 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-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... 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.
PAGE 15
Notation for Messages About This Manual !i:i. In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length , filename2:length ) ; !i:i !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
PAGE 16
About This Manual Change Bar Notation { } 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.
PAGE 17
1 Overview of the ServerNet/FX Adapter Subsystem This section provides an overview of the ServerNet/FX adapter subsystem.
PAGE 18
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapter Subsystem Overview ServerNet/FX Adapter Subsystem Overview The ServerNet/FX adapter subsystem is a fiber-optic extension of the ServerNet X-fabric and Y-fabric on NonStop S-series servers. The ServerNet/FX adapter subsystem allows a NonStop S-series server to participate in an existing FOX ring. Note.
PAGE 19
Logical Layout of a FOX Ring Overview of the ServerNet/FX Adapter Subsystem Logical Layout of a FOX Ring A FOX network is physically connected as a ring; however, it is logically configured with the Expand subsystem as a fully connected mesh (that is, each cluster is only one logical hop from any other cluster in the FOX network). Figure 1-1 shows the physical and logical layout of a FOX ring with four clusters. Figure 1-1.
PAGE 20
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapter Subsystem Management ServerNet/FX Adapter Subsystem Management The Subsystem Control Facility (SCF) handles management of the ServerNet/FX adapter subsystem network, the FOX monitor process ($ZZFOX), and the logical interfaces to FOX direct logical paths (XL, XR, YL, and YR), and configuration and management of the logical interfaces ($ZZFOX.#X and $ZZFOX.#Y) associated with ServerNet/FX adapters.
PAGE 21
Software and Hardware Components Overview of the ServerNet/FX Adapter Subsystem Figure 1-2. Physical Components and Object Types of a FOX Cluster Processor SUBNET Object SCF $ZZFOX PROCESS Object $ZZFOX Expand-over-FOX Line-Handler Process N A M Expand PROCESS and LINE objects FOX Driver X Y Y-Fabric X-Fabric LBU Objects $ZZFOX.#X Receive Transmit ServerNet/FX Adapter Left Transmit $ZZFOX.#Y Receive Transmit Receive Right ServerNet/FX Adapter Left Transmit Right Receive VST002.
PAGE 22
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapter Object Types and Names ServerNet/FX Adapter Object Types and Names You can manipulate and monitor the ServerNet/FX adapter subsystem through SCF by entering commands that act on the ServerNet/FX adapter subsystem objects. Each object has an object type and an object name. The object type categorizes the object. The object name uniquely identifies each object within the subsystem.
PAGE 23
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapter Object Types and Names PATH Object The PATH object identifies a single FOX direct logical path from a processor in the local cluster to a processor in one of the other clusters on a FOX ring. Within each cluster on a FOX ring, every processor maintains a FOX direct logical connection, consisting of four unidirectional FOX direct logical paths, to any other processor in any other cluster on the FOX ring.
PAGE 24
Expand-Over-FOX Line-Handler Processes Overview of the ServerNet/FX Adapter Subsystem Figure 1-4. FOX Direct Logical Connections Between Processors 4 FOX Direct Logical Paths from processor 2 in \B to processor 3 in \A FOX Direct Logical Connection Cluster \A XL XR YL YR XL XR YL YR FOX Direct Logical Connection Cluster \B CPU 3 CPU 2 4 FOX Direct Logical Paths from processor 3 in \A to processor 2 in \B VST005.
PAGE 25
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapters ServerNet/FX Adapters The ServerNet/FX adapters logically extend the ServerNet fabrics via fiber-optic lines to other clusters in the FOX ring. Two ServerNet/FX adapters are used: one for the Xring and one for the Y-ring. The ServerNet/FX adapters must be installed and the fiber-optic cabling connected before the Expand-over-FOX lines can be started.
PAGE 26
Overview of the ServerNet/FX Adapter Subsystem ServerNet/FX Adapters ServerNet/FX Adapter Configuration and Management Manual—426872-002 1- 10
PAGE 27
2 Configuring the ServerNet/FX Adapter Subsystem This section explains the configuration process for the ServerNet/FX adapter subsystem.
PAGE 28
Configuring the ServerNet/FX Adapter Subsystem Planning for FOX Monitor Process Configuration Planning for FOX Monitor Process Configuration The availability of the ServerNet/FX adapter subsystem can be optimized by coordinating the configured location of the FOX monitor process, FOXMON, with the physical location of the ServerNet/FX adapters. Note. ServerNet/FX adapters must be installed by a HP-trained service provider.
PAGE 29
Configuring the ServerNet/FX Adapter Subsystem Both ServerNet/FX Adapters in the Same Processor Enclosure Both ServerNet/FX Adapters in the Same Processor Enclosure One ServerNet/FX adapter must be connected to the X-fabric (slot 51 or 53), and the other ServerNet/FX adapter must be connected to the Y-fabric (slot 52 or 54). The suggested configuration is to configure the primary and backup FOX monitor processes in the same enclosure containing the ServerNet/FX adapters.
PAGE 30
Configuring the ServerNet/FX Adapter Subsystem Using the SCF ADD PROCESS Command PRIMARYCPU n specifies the processor in which the primary process starts. n can be from 0 through the maximum number of processors. The PRIMARYCPU value cannot be the same as the BACKUPCPU value. BACKUPCPU n specifies the processor in which the backup process starts. n can be from 0 through the maximum number of processors. The BACKUPCPU value cannot be same as the PRIMARYCPU value. Caution.
PAGE 31
Configuring the ServerNet/FX Adapter Subsystem Example Example The following command creates the primary FOX monitor process, named ZZFOX, in processor 0 and the backup FOX monitor process in processor 3: ADD PROCESS $ZZKRN.#ZZFOX, NAME $ZZFOX, TYPE FOXMON, & PRIMARYCPU 0, BACKUPCPU 3, HOMETERM $ZHOME, PRIORITY 199, & STARTMODE MANUAL, PROGRAM $SYSTEM.SYSTEM.
PAGE 32
Configuring the ServerNet/FX Adapter Subsystem Example Refer to the SCF Reference Manual for the Kernel Subsystem for complete syntax information for the SCF STATUS PROCESS command. Note. You can also use the ServerNet/FX adapter subsystem SCF STATUS PROCESS command to check the status of $ZZFOX. This command is explained in Section 4, ServerNet/FX Adapter Subsystem SCF Commands. Example The following shows an example of the Kernel subsystem SCF STATUS PROCESS command. -> STATUS PROCESS $ZZKRN.
PAGE 33
Configuring the ServerNet/FX Adapter Subsystem ServerNet/FX 2 Adapter LBU Examples ServerNet/FX 2 Adapter LBU Examples The following is an example of creating an LBU for the ServerNet/FX 2 adapter connected to the X-ring: ADD LBU $ZZFOX.#X, LOCATION (1,1,53), & PROGRAM $SYSTEM.SYSTEM.M6742, MODULE STANDARD, & SAMPLEINT 1:00:00.
PAGE 34
Configuring the ServerNet/FX Adapter Subsystem Adding a NonStop S-Series Server to a FOX Ring Overview This task must be performed by a HP-trained service provider. Fiber-optic cabling instructions are provided for the ServerNet/FX adapter in the ServerNet/FX Adapter Installation and Support Guide and for the ServerNet/FX 2 adapter in the ServerNet/FX 2 Adapter Installation and Support Guide. 3. Connect the corresponding LBUs at the new cluster’s cable neighbors. 4.
PAGE 35
3 Managing the ServerNet/FX Adapter Subsystem This section explains how to monitor, reconfigure, and control the ServerNet/FX adapter subsystem, recover FOX direct logical paths, and prepare ServerNet/FX adapters for PMF or IOMF CRU replacement.
PAGE 36
Managing the ServerNet/FX Adapter Subsystem Recovery Tasks: • Recovering Down or Stuck FOX Direct Logical Paths Page 3-24 ServerNet/FX Adapter Preparation: • Preparing ServerNet/FX Adapters for Processor Multifunction (PMF) or I/O Multifunction (IOMF) CRU Replacement Page 3-29 Refer to Section 4, ServerNet/FX Adapter Subsystem SCF Commands, for complete syntax information about all the ServerNet/FX adapter subsystem Subsystem Control Facility (SCF) commands used in this section.
PAGE 37
Managing the ServerNet/FX Adapter Subsystem Monitoring FOX Ring Activity Monitoring FOX Ring Activity Monitoring tasks include the following: • • • • • Running SCF Remotely Displaying ServerNet/FX Adapter Subsystem Information Gathering Statistical Information Checking Status Information Running Diagnostic Tests Displaying Expand-over-FOX line-handler process information is explained in the Expand Configuration and Management Manual.
PAGE 38
Displaying ServerNet/FX Adapter Subsystem Information Managing the ServerNet/FX Adapter Subsystem Using SCF Commands for the ServerNet/FX Adapter Subsystem The following ServerNet/FX adapter subsystem SCF commands display static information about ServerNet/FX adapter subsystem components. SCF Command Information Reported INFO LBU Displays information for a specified LBU, including the configured sample time interval. Use the DETAIL option to display the configured left and right power levels.
PAGE 39
Managing the ServerNet/FX Adapter Subsystem Gathering Statistical Information attributes can be viewed in the OSM or TSM Low-Level Link. Informational attributes for a ServerNet/FX adapter include: • • • • • • • FOX Cluster Number Frimware Version Hardware Revision Logical Name (location in terms of group, module, and slot) Part Number Right and Left Transmitter Power Level Track ID Note.
PAGE 40
Managing the ServerNet/FX Adapter Subsystem Running Diagnostic Tests Using SCF Commands for the Kernel Subsystem You can use the Kernel subsystem SCF STATUS PROCESS command to check the status of the FOX monitor process ($ZZFOX). The following shows an example of the Kernel subsystem SCF STATUS PROCESS command. -> STATUS PROCESS $ZZKRN.#ZZFOX NONSTOP KERNEL - Status Process \EAST.$ZZKRN.
PAGE 41
Managing the ServerNet/FX Adapter Subsystem Altering Configuration Attributes Altering Configuration Attributes Reconfiguration tasks include the following: • • Altering an LBU Configuration Altering the FOX Monitor Process ($ZZFOX) Configuration using the Kernel Subsystem Altering Expand-over-FOX line-handler processes is explained in the Expand Configuration and Management Manual.
PAGE 42
Managing the ServerNet/FX Adapter Subsystem • • Altering the FOX Monitor Process ($ZZFOX) Configuration using the Kernel Subsystem Start Stop Note. For complete information about using OSM or TSM to perform actions, refer to the OSM User's Guide, the TSM Online User Guide, or the online help within each application. Altering the FOX Monitor Process ($ZZFOX) Configuration using the Kernel Subsystem Caution.
PAGE 43
Managing the ServerNet/FX Adapter Subsystem Controlling FOX Rings Controlling FOX Rings FOX ring control tasks include the following: • • • • • • • • Starting a FOX Direct Logical Path Starting an LBU Stopping an LBU Starting the FOX Monitor Process Switching Primary and Backup Processors for the FOX Monitor Process Deleting the FOX Monitor Process ($ZZFOX) using the Kernel Subsystem Adding a Cluster to a FOX Ring Removing a Cluster From a FOX Ring Controlling Expand-over-FOX line-handler processes and
PAGE 44
Managing the ServerNet/FX Adapter Subsystem Stopping an LBU Using SCF Commands for the ServerNet/FX Adapter Subsystem The ServerNet/FX adapter subsystem SCF START LBU command starts the flow of messages from the FOX ring through a specified LBU. Successful completion of the command leaves the specified LBU in the STARTED state. Note.
PAGE 45
Managing the ServerNet/FX Adapter Subsystem Stopping an LBU Using SCF Commands for the ServerNet/FX Adapter Subsystem The ServerNet/FX adapter subsystem SCF STOP LBU command stops the flow of messages from the FOX ring through a specified LBU. Successful completion of the command leaves the specified LBU is the STOPPED state.
PAGE 46
Managing the ServerNet/FX Adapter Subsystem Stopping an LBU At the right cable neighbor: If the right cable neighbor is running the D-series NonStop Kernel operating system, enter the following SCF command: SCF> DISCONNECT LBU $IPB.#Y,LEFT If the right cable neighbor is running the G-series NonStop Kernel operating system, enter the following SCF command: SCF> DISCONNECT LBU $ZZFOX.
PAGE 47
Managing the ServerNet/FX Adapter Subsystem Starting the FOX Monitor Process To stop the LBU for the ServerNet/FX adapter connected to the X-ring on the local cluster, issue the following ServerNet/FX adapter subsystem SCF command : SCF> STOP LBU $ZZFOX.#X Task 4: Verify that the LBU is down You can use the SCF STATUS LBU command to verify that an LBU is down.
PAGE 48
Managing the ServerNet/FX Adapter Subsystem Switching Primary and Backup Processors for the FOX Monitor Process Switching Primary and Backup Processors for the FOX Monitor Process Use the ServerNet/FX adapter subsystem SCF PRIMARY PROCESS command to switch the primary configured processor for the FOX monitor process ($ZZFOX) to the backup configured processor or to switch the backup configured processor to the primary configured processor.
PAGE 49
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring If the left cable neighbor is running the D-series NonStop Kernel operating system, enter the following SCF commands: SCF> DISCONNECT LBU $IPB.#Y, RIGHT SCF> DISCONNECT LBU $IPB.#X, RIGHT If the left cable neighbor is running the G-series NonStop Kernel operating system, enter the following SCF commands: SCF> DISCONNECT LBU $ZZFOX.#Y, RIGHT SCF> DISCONNECT LBU $ZZFOX.
PAGE 50
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring Task 3: Insert the new cluster in the FOX ring Detach the cables between the left and right cable neighbors, and then install the new cluster in the FOX ring. Note. This task must be performed by a HP-trained service provider.
PAGE 51
Adding a Cluster to a FOX Ring Managing the ServerNet/FX Adapter Subsystem Figure 3-1 illustrates physically and logically disconnecting the FOX links at the right and left cable neighbors. Figure 3-1. Disconnecting FOX Cable Neighbors New Cluster 4 will be inserted here Left Cable Neighbor Cluster 3 Right Cable Neighbor X X Y Y $LINE1 $LINE3 Cluster 1 $X252 $LINE2 $LINE2 Y $LINE3 X Y X $LINE1 Cluster 2 Key Expand C onfigured path FOX ring physical and logical path VST047.
PAGE 52
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring Task 4: Connect the corresponding LBUs at the cable neighbors To bring up the links at the cable neighbors (the servers between which the NonStop S-series server was inserted), issue the following SCF commands: At the left cable neighbor: If the left cable neighbor is running the D-series NonStop Kernel operating system, enter the following SCF commands: SCF> CONNECT LBU $IPB.#X, RIGHT SCF> CONNECT LBU $IPB.
PAGE 53
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring Figure 3-2. Bringing Up New FOX Links New Cluster 4 X Left Cable Neighbor Cluster 3 X Y Y Right Cable Neighbor $LINE1 $LINE3 Cluster 1 $X252 $LINE2 $LINE2 Y $LINE3 X Y X $LINE1 Cluster 2 Key Expand C onfigured path FOX ring physical and logical path VST048.
PAGE 54
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring Task 6: Create and start the Expand-over-FOX line-handler processes Because a FOX ring is configured as a logical, fully connected mesh, you must create and start an Expand-over-FOX line-handler process on the new cluster for each remote cluster in the FOX ring. Each remote cluster also requires a corresponding Expand-over-FOX line-handler process for the new cluster.
PAGE 55
Managing the ServerNet/FX Adapter Subsystem Adding a Cluster to a FOX Ring Figure 3-3 on page 3-21 illustrates on what cluster the Expand-over-FOX lines are started. Figure 3-3.
PAGE 56
Managing the ServerNet/FX Adapter Subsystem Removing a Cluster From a FOX Ring Task 9: Verify that the new links are up You can verify that the NonStop S-series server is connected to the FOX ring using the commands outlined in Monitoring FOX Ring Activity on page 3-3. For a complete view of the entire FOX ring, use the SCF STATUS SUBNET command: SCF> STATUS SUBNET $ZZFOX, DETAIL The ring status is displayed in the Ring Termination Status field.
PAGE 57
Managing the ServerNet/FX Adapter Subsystem Removing a Cluster From a FOX Ring Task 3: Disconnect the corresponding LBUs at the cable neighbors To disconnect the LBUs, issue the following SCF commands at the cluster’s cable neighbors: At the left cable neighbor: If the left cable neighbor is running the D-series NonStop Kernel operating system, enter the following SCF commands: SCF> DISCONNECT LBU $IPB.#Y,RIGHT SCF> DISCONNECT LBU $IPB.
PAGE 58
Managing the ServerNet/FX Adapter Subsystem Recovering Down or Stuck FOX Direct Logical Paths Task 5: Verify that the LBUs are down To check the status of the LBUs for the ServerNet/FX adapters connected to the Xand Y-rings on the local cluster, issue the following ServerNet/FX adapter subsystem SCF commands: SCF> STATUS LBU $ZZFOX.#X SCF> STATUS LBU $ZZFOX.#Y The summary state displayed for each LBU should be STOPPED.
PAGE 59
Managing the ServerNet/FX Adapter Subsystem Recovering Down or Stuck FOX Direct Logical Paths and CPU Stuck fields which indicates FOX direct logical paths are down from the local cluster to remote clusters. SCF> STATUS PATH $ZZFOX.*, TO \*.* FOX Status PATH On \GATE3 FOX Status PATH \GATE3.$ZZFOX.* TO *.* Cluster Number... 3 System Name...... \GATE3 System Number.... 56 Cluster Number ------5 12 System Name -----\GATE5 \GATE12 At 11 May 2001, 15:32:45.
PAGE 60
Managing the ServerNet/FX Adapter Subsystem Recovering Down or Stuck FOX Direct Logical Paths The following example of a STATUS PATH command with the DETAIL option shows the processors that are reporting FOX direct logical paths that are down (D) or in a stuck state (-STUCK-) from \GATE3 to \GATE5 . SCF> STATUS PATH $ZZFOX.*, TO \GATE5.*, DETAIL FOX Detailed Status PATH \GATE3.$ZZFOX.*, TO \GATE5.* At 11 May 2001, 15:40:05.327 Cluster Number... 3 System Name...... \GATE3 System Number....
PAGE 61
Managing the ServerNet/FX Adapter Subsystem Recovering Down or Stuck FOX Direct Logical Paths Task 3: Recover FOX direct logical paths To recover FOX direct logical paths that are down (D) or in a stuck state (-STUCK-), use the ServerNet/FX adapter subsystem SCF START PATH command. Caution.
PAGE 62
Managing the ServerNet/FX Adapter Subsystem Recovering Down or Stuck FOX Direct Logical Paths Recovering stuck (-STUCK-) FOX direct logical paths For each stuck state (-STUCK-), start all four FOX direct logical paths between the local processor and a specified remote processor by issuing the following ServerNet/FX adapter subsystem SCF command: SCF> START PATH $ZZFOX.local-processor, TO remote-cluster.
PAGE 63
Managing the ServerNet/FX Adapter Subsystem Preparing ServerNet/FX Adapters for Processor Multifunction (PMF) or I/O Multifunction (IOMF) CRU The following example of a STATUS PATH command shows values of zero (0) in the Path Down and CPU Stuck fields which indicates all FOX direct logical paths are up from the local cluster to remote clusters. SCF> STATUS PATH $ZZFOX FOX Status PATH \GATE3.$ZZFOX At 29 Feb 2001, 15:32:45.556 Cluster Number... 3 System Name...... \GATE3 System Number....
PAGE 64
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement When a PMF CRU will be replaced in a NonStop S-series system that is part of a FOX ring, the location of the ServerNet/FX adapters determines the procedure to be performed to ensure continued connectivity with the X or Y ServerNet fabric associated with the PMF CRU being replaced. The procedures are as follows: WARNING.
PAGE 65
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement If the primary FOX monitor process is not running on a processor in the enclosure containing the PMF CRU to be replaced, go to Task 3: Replace the PMF CRU; if it is running on a processor in the enclosure containing the PMF CRU to be replaced continue on to Task 2: Switch the primary FOX monitor process to its backup.
PAGE 66
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement Task 5: Bring up the connections affected by the replacement of the PMF CRU Verify the status of the ServerNet fabric that was affected by the PMF CRU replacement. Use the SCF Kernel subsystem STATUS SERVERNET command as follows: SCF> STATUS SERVERNET $ZSNET Make sure that all the affected fabrics came up in the processor that had its PMF CRU replaced and in the companion processor.
PAGE 67
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement ServerNet fabric that was affected by the replacement of the PMF CRU must be stopped and then restarted. WARNING. This step is necessary if the enclosure containing the replaced PMF CRU contains another running processor. The availability of FOX logical paths will be temporarily lowered. There must be another LBU available for other processors to use while this step is carried out.
PAGE 68
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement ServerNet/FX adapters located in the same enclosure as the PMF CRU being replaced If the PMF CRU to be replaced is located in an enclosure that contains ServerNet/FX adapters, perform the following tasks: Task 1: Verify the status of the surviving ServerNet fabric To check the status of the X (Y) ServerNet fabric that will remain fully connected during the PMF CRU replacement, issue the foll
PAGE 69
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement To stop the LBU to the Y ServerNet fabric associated with the PMF CRU to be replaced, issue the following ServerNet/FX adapter subsystem SCF command: SCF> STOP LBU $ZZFOX.#Y Task 5: Replace the PMF CRU To replace one or more PMF CRUs, use the Replace PMF guided replacement tool. Replace PMF is a graphical user interface (GUI) that guides you step by step through the replacement process.
PAGE 70
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement To start the LBU to the Y ServerNet fabric that was stopped in Task 4 above, issue the following ServerNet/FX adapter subsystem SCF command: SCF> START LBU $ZZFOX.
PAGE 71
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement ServerNet/FX adapters located in an I/O enclosure that is connected to and on the same ServerNet fabric as the PMF CRU being replaced If the PMF CRU to be replaced is located in an enclosure that connects to an I/O enclosure that contains ServerNet/FX adapters on the same ServerNet fabric as the PMF CRU, perform the following tasks: Task 1: Verify the status of the surviving ServerNet fabric
PAGE 72
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement To stop the LBU to the X ServerNet fabric associated with the PMF CRU to be replaced, issue the following ServerNet/FX adapter subsystem SCF command: SCF> STOP LBU $ZZFOX.#X To stop the LBU to the Y ServerNet fabric associated with the PMF CRU to be replaced, issue the following ServerNet/FX adapter subsystem SCF command: SCF> STOP LBU $ZZFOX.
PAGE 73
Managing the ServerNet/FX Adapter Subsystem Procedures for Preparing ServerNet/FX Adapters for PMF CRU Replacement Task 7: Bring up the connections affected by the replacement of the PMF CRU To bring up the connections affected by the replacement of the PMF CRU, use one of the following procedures based on your specific system configurations: If the primary FOX monitor process is running in any other enclosure than the PMF CRU that was replaced and if software supporting the ServerNet/FX Path Management F
PAGE 74
Managing the ServerNet/FX Adapter Subsystem Procedure for Preparing ServerNet/FX Adapters for IOMF CRU Replacement To bring up the connection from the LBU for the ServerNet FX adapter connected to the Y-ring to the Y ServerNet fabric, issue the following ServerNet/FX adapter subsystem commands: SCF> START LBU $ZZFOX.
PAGE 75
Managing the ServerNet/FX Adapter Subsystem Procedure for Preparing ServerNet/FX Adapters for IOMF CRU Replacement 4. Click Perform Action. This action launches the guided procedure interface, which guides you through the CRU replacement process. To access Replace IOMF from TSM, start from the toolbar located on the desktop of your TSM console.
PAGE 76
Managing the ServerNet/FX Adapter Subsystem Procedure for Preparing ServerNet/FX Adapters for IOMF CRU Replacement ServerNet/FX Adapter Configuration and Management Manual—426872-002 3- 42
PAGE 77
4 ServerNet/FX Adapter Subsystem SCF Commands This section explains the Subsystem Control Facility (SCF) commands interpreted for the ServerNet/FX adapter subsystem.
PAGE 78
ServerNet/FX Adapter Subsystem SCF Commands Supported Commands and Object Types Supported Commands and Object Types This section explains the SCF commands that are interpreted specifically for the ServerNet/FX adapter subsystem. Other commands that are generally supported by SCF, such as the ASSUME and ENV commands, are not documented in this manual. The SCF Reference Manual for G-Series Releases provides general information about SCF commands.
PAGE 79
ServerNet/FX Adapter Subsystem SCF Commands VERSION Command Requires No Object member of the group of the owner of the subsystem. When used with the security features of the system services, SCF provides effective access control for sensitive commands. Commands that request information or status but that do not affect operation are called nonsensitive commands and are available to all users. Each command in the following section is identified as either sensitive or nonsensitive.
PAGE 80
ServerNet/FX Adapter Subsystem SCF Commands LBU Object Logical States Table 4-2. SCF Object Summary States Summary State Description STARTED The object is initialized and ready for normal data traffic. The flow of information is unrestricted. STARTING The object is being initialized and is in transition to the STARTED state. STOPPED The object is configured, there are no links either to or from the object, and no new links may be established.
PAGE 81
ServerNet/FX Adapter Subsystem SCF Commands ServerNet/FX Adapter Physical States Table 4-4. SCF Commands Logical States SCF Commands UNDEFINED ABORT X ADD X ALTER UNKNOWN ABSENT STOPPED X X X STARTED X X CONNECT X X DELETE X X DISCONNECT X INFO X X X X X PRIMARY X X X X X START X X STATS X X X X X STATUS X X X X X STOP X ServerNet/FX Adapter Physical States This section explains the physical states for a ServerNet/FX adapter.
PAGE 82
ServerNet/FX Adapter Subsystem SCF Commands ServerNet/FX Adapter Physical States Table 4-5. ServerNet/FX Adapter Physical States Physical State Description UNLOADED The ServerNet/FX adapter has not had the firmware downloaded and the ServerNet/FX adapter is in Hardware Passthrough mode. If the ServerNet/FX adapter is connected to the FOX ring, then packets pass through the ServerNet/FX adapter to the left (right) physical neighbor on the FOX ring.
PAGE 83
ServerNet/FX Adapter Subsystem SCF Commands ABORT Command ABORT Command The ABORT command terminates execution of the operational firmware in the specified ServerNet/FX adapter. An aborted ServerNet/FX adapter does not process data or control frames. Instead, it passes frames through to its FOX neighbor. An aborted LBU is reset to the STOPPED summary state. ABORT is a sensitive command.
PAGE 84
ServerNet/FX Adapter Subsystem SCF Commands Example To fully abort a FOX cluster, issue the following two commands: SCF> ABORT LBU $ZZFOX.#X SCF> ABORT LBU $ZZFOX.
PAGE 85
ServerNet/FX Adapter Subsystem SCF Commands ADD Command ADD Command The ADD command adds the configuration records for the LBU object and the specified ServerNet/FX adapter to the system configuration database. ADD is a sensitive command. The ADD command syntax is ADD [ /OUT file-spec/ ] LBU LBU-name { attribute-spec }... OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LBU is a keyword specifying that an LBU name comes next on the command line.
PAGE 86
ServerNet/FX Adapter Subsystem SCF Commands ADD Command LOCATION Units Not applicable Range Group: 1 Module: 1 Slot: 51 and 52, or 53 and 54 of an I/O or processor enclosure The LOCATION attribute specifies the group (group), module (module), and slot (slot) where the ServerNet/FX adapter specified by this LBU is physically located. Note. More than one enclosure requires SEBs in slots 51 and 52 of enclosure 1. PROGRAM Default ServerNet/FX adapter: $SYSTEM.SYSTEM.
PAGE 87
ServerNet/FX Adapter Subsystem SCF Commands ADD Command CLUSTERNUM Default 0 Units Not applicable Range 1 through 14 The CLUSTERNUM attribute specifies the unique cluster number (cluster-number) of the server. If the cluster number is not specified, it defaults to 0 and the specified ServerNet/FX adapter cannot be started until the cluster number is changed to a valid value.
PAGE 88
ServerNet/FX Adapter Subsystem SCF Commands Considerations POWERRIGHT Default 0 Units Not applicable Range 0 to 1 The POWERRIGHT attribute specifies the power level (powerlevel) for the link to the right cluster. The Right Out fiber connector on the ServerNet/FX adapter provides the link from the adapter to the right cluster. A value of 0 specifies a low power level and is used for distances up to 2 Km. A value of 1 specifies a high power level and is used for distances from 2 Km to 4 Km. WARNING.
PAGE 89
ServerNet/FX Adapter Subsystem SCF Commands ALTER Command ALTER Command The ALTER command changes the values of the attributes of an existing object. This command changes only the specified attributes of the target object. ALTER is a sensitive command. The ALTER command syntax is ALTER [ /OUT file-spec/ ] LBU LBU-name [ , DEFAULT ] { attribute-spec }... OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 90
ServerNet/FX Adapter Subsystem SCF Commands ALTER Command PROGRAM Default ServerNet/FX adapter: $SYSTEM.SYSTEM.M6740 ServerNet/FX 2 adapter: $SYSTEM.SYSTEM.M6742 Units Not applicable Range Not applicable The PROGRAM attribute is the name of the file (file-spec) containing the downloadable operational microcode for the ServerNet/FX adapter specified by the LBU. Caution. Never put a copy of M6740 or M6742 in the $SYSTEM.SYSTEM subvolume.
PAGE 91
ServerNet/FX Adapter Subsystem SCF Commands ALTER Command STARTSTATE Default STARTED Units Not applicable Range STARTED/STOPPED The STARTSTATE attribute specifies the start mode of the ServerNet/FX adapter. A value of STARTED specifies that the ServerNet/FX adapter will be started automatically when the system is loaded.
PAGE 92
ServerNet/FX Adapter Subsystem SCF Commands Considerations Considerations • • • • • Use the DEFAULT parameter for configuration changes to the LBU that are to be retained during subsequent cold loads of the system. Changes to PROGRAM, MODULE, or CLUSTERNUM will not take effect until the next time the ServerNet/FX adapter specified by the LBU is started using the START LBU command.
PAGE 93
ServerNet/FX Adapter Subsystem SCF Commands CONNECT Command CONNECT Command The CONNECT command logically connects a link on the FOX ring subnetwork for the specified LBU object. You need to use the CONNECT command only after disconnecting a link on the FOX ring by using the DISCONNECT command. When a ServerNet/FX adapter is started using the START LBU command, the ServerNet/FX adapter is automatically connected logically to its neighbors. CONNECT is a sensitive command.
PAGE 94
ServerNet/FX Adapter Subsystem SCF Commands Consideration Figure 4-1. Comparison of START LBU, STOP, ABORT, CONNECT, and DISCONNECT Commands Processor X Processor X Y Processor Y X Y Y-Fabric X-Fabric START LBU, STOP, and ABORT Commands Act Here Receive Transmit ServerNet/FX Adapter Transmit Transmit Receive ServerNet/FX Adapter Receive Transmit Receive CONNECT and DISCONNECT Commands Act Here VST001.
PAGE 95
ServerNet/FX Adapter Subsystem SCF Commands Example Example The following commands fully connect a FOX cluster to the ServerNet system area network (ServerNet SAN): SCF> SCF> SCF> SCF> CONNECT CONNECT CONNECT CONNECT LBU LBU LBU LBU $ZZFOX.#X, $ZZFOX.#X, $ZZFOX.#Y, $ZZFOX.
PAGE 96
ServerNet/FX Adapter Subsystem SCF Commands DELETE Command DELETE Command The DELETE command deletes the configuration records for the LBU object and the specified ServerNet/FX adapter from the system configuration database. DELETE is a sensitive command. The DELETE command syntax is DELETE [ /OUT file-spec/ ] LBU LBU-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LBU is a keyword specifying that an LBU name comes next on the command line.
PAGE 97
ServerNet/FX Adapter Subsystem SCF Commands DISCONNECT Command DISCONNECT Command The DISCONNECT command logically disconnects a link on the FOX ring subnetwork for the specified LBU object, preventing packets from traveling in the specified direction. DISCONNECT is a sensitive command. The DISCONNECT command syntax is DISCONNECT [ /OUT file-spec/ ] LBU LBU-name , { LEFT | RIGHT } OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 98
ServerNet/FX Adapter Subsystem SCF Commands • • Example After you issue the DISCONNECT command on a particular adapter, a few seconds may pass on the FOX ring before all clusters notice that the adapter is unusable in the specified direction. The DISCONNECT command fails unless the ServerNet/FX adapter is in the STARTED summary state.
PAGE 99
ServerNet/FX Adapter Subsystem SCF Commands INFO Command INFO Command INFO is a nonsensitive command that is used to display static configuration information about the specified object. INFO PROCESS Command Use the INFO PROCESS command to return the current or default values for the specified PROCESS object.
PAGE 100
ServerNet/FX Adapter Subsystem SCF Commands INFO LBU Command Example The following example is similar to the display returned by the INFO command for the PROCESS object: SCF> INFO PROCESS $ZZFOX FOX Info PROCESS $ZZFOX On \GATE3 Name $ZZFOX Primary CPU 0 Backup CPU 3 Please see the LISTDEV $ZZFOX command for device type information. The following descriptions explain the fields returned by the INFO PROCESS command; Name identifies the name of the FOX monitor process, which must be $ZZFOX.
PAGE 101
ServerNet/FX Adapter Subsystem SCF Commands INFO LBU Command OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LBU is a keyword specifying that an LBU name comes next on the command line. LBU-name is the name of the LBU ($ZZFOX.#X or $ZZFOX.#Y) associated with the ServerNet/FX adapter you are examining. DETAIL specifies that the display is to include additional detailed information about the LBU object.
PAGE 102
ServerNet/FX Adapter Subsystem SCF Commands INFO LBU Command The following example is similar to the display returned by the INFO LBU command with the DETAIL option: SCF> INFO LBU $ZZFOX.#X, DETAIL FOX Detailed Info LBU \GATE3.$ZZFOX.#X System Number..... Cluster Number.... Controller Type... Power Right....... Location.......... Startstate........ 56 1 FX2SA 0 1 ,1 ,53 STARTED At 08 May 2001, 16:49:05.606 *Sample Interval.. Poll Interval..... Power Left........ Prod ID........... 1:00:00.000 0.
PAGE 103
ServerNet/FX Adapter Subsystem SCF Commands INFO LBU Command *Sample Interval identifies the time interval during which statistics were gathered. time has the form hh:mm:ss.lll, where hh is hours, mm is minutes, ss is seconds, and lll is milliseconds. $ZZFOX gathers statistics during this interval and then resets the statistical counters. You can see these statistics by using the STATS LBU command. The interval can be changed using the ALTER command explained on page 4-13.
PAGE 104
ServerNet/FX Adapter Subsystem SCF Commands PRIMARY Command PRIMARY Command The PRIMARY command is used to toggle the primary and backup processors of the FOX monitor process ($ZZFOX). PRIMARY is a sensitive command. The PRIMARY command syntax is PRIMARY [ /OUT file-spec/ ] PROCESS FOX-process-name , CPU-number OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS is a keyword specifying that a FOX process name comes next on the command line.
PAGE 105
ServerNet/FX Adapter Subsystem SCF Commands START Command START Command START is a sensitive command that initiates the operation of a specified object. START LBU Command Use the START LBU command to initiate the operation of the specified ServerNet/FX adapter. Successful completion of the START LBU command leaves the specified LBU in the STARTED summary state.
PAGE 106
ServerNet/FX Adapter Subsystem SCF Commands START LBU Command Example The following example is similar to the display returned when a START LBU command fails to start LBU $ZZFOX.#X: SCF> START LBU $ZZFOX.#X FOX Start Failed for LBU \GATE3.$ZZFOX.#X Summary State..... Selftest Code..... Last Reset Code... File System Error. STARTING %000000 1 11 Physical State.... LOADED Download Error.... Open Failed Controller Type... FX2SA FOX E00006 LBU could not be started. Type HELP FOX 6 for information.
PAGE 107
ServerNet/FX Adapter Subsystem SCF Commands START PATH Command Physical State identifies the physical state reported by the ServerNet/FX adapter. Possible states are UNLOADED, LOADED, OPERATIONAL, NO RESPONSE and ???. Refer to ServerNet/FX Adapter Physical States on page 4-5 for additional information. Download Error identifies the download error status. Possible download errors are Download Succeeded No error. Microcode download completed successfully.
PAGE 108
ServerNet/FX Adapter Subsystem SCF Commands START PATH Command $ZZFOX is the FOX monitor process in the local cluster for which you are requesting the START PATH command. local-processor is the processor number in the local cluster that specifies the starting point of the FOX direct logical path. A local-processor or an asterisk (*) must be explicitly specified. remote-cluster is the system name of one of the clusters (other than the local cluster) on the FOX ring to which remote-processor belongs.
PAGE 109
ServerNet/FX Adapter Subsystem SCF Commands START PATH Command Examples The following command starts the FOX direct logical path XR from processor 10 in the local cluster to processor 3 in \GATE5: SCF> START PATH $ZZFOX.10, TO \GATE5.3, SUB XR The output from the above START PATH command shows that the XR FOX direct logical path from processor 10 on \GATE3 to processor 3 on \GATE5 was successfully started. SCF> START PATH $ZZFOX.10, TO \GATE5.3, SUB XR FOX Detailed Status PATH \GATE3.$ZZFOX.10, TO \GATE5.
PAGE 110
ServerNet/FX Adapter Subsystem SCF Commands START PATH Command The output from the above START PATH command shows that all FOX direct logical paths from processor 12 on \GATE3 to processor 0 on \GATE7 were successfully started. SCF> START PATH $ZZFOX.12, TO \GATE7.0 FOX Detailed Status PATH \GATE3.$ZZFOX.12, TO \GATE7.0 At 11 May 2001, 15:40:05.327 Cluster Number... 3 System Name...... \GATE3 System Number....
PAGE 111
ServerNet/FX Adapter Subsystem SCF Commands STATS Command STATS Command The STATS command returns statistical information on the specified ServerNet/FX adapter during the current sample period. STATS is a nonsensitive command unless it used RESET. The STATS command syntax is STATS [ /OUT file-spec/ ] LBU LBU-name [ , RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LBU is a keyword specifying that an LBU name comes next on the command line.
PAGE 112
ServerNet/FX Adapter Subsystem SCF Commands STATS LBU Command Example STATS LBU Command Example The following example is similar to the display returned by the STATS LBU command for a ServerNet/FX adapter: SCF> STATS LBU $ZZFOX.#X FOX Stats LBU \GATE7.$ZZFOX.#X At 08 May 2001, 12:48:39.796 System Number..... 54 Cluster Number.... 5 Last Reset Time... 11:57:48.019 Controller Type... FX2SA Controller Interface Errors --------------------------Chk Sum........... 0 SNET Pkt.......... 0 SNET Aged.........
PAGE 113
ServerNet/FX Adapter Subsystem SCF Commands STATS LBU Command Example Controller Interface Errors identifies the type of counters being reported in the following section of the display. Note. The values displayed are since the statistical counters were last reset. Chk Sum indicates the number of checksum errors detected by the ServerNet/FX adapter. A nonzero value in this field can indicate a FOX adapter hardware error in an adapter on the ring.
PAGE 114
ServerNet/FX Adapter Subsystem SCF Commands STATS LBU Command Example Packets Sent: identifies the number of packets sent (from the left neighbor, the right neighbor, and the local cluster). Note. The values displayed are since the statistical counters were last reset. To Left indicates the number of packets sent to the left neighbor from the right neighbor and the local cluster. To Right indicates the number of packets sent to the right neighbor from the left neighbor and the local cluster.
PAGE 115
ServerNet/FX Adapter Subsystem SCF Commands STATS LBU Command Example 3. The condition of the sending FOX adapter and have it replaced if necessary. Note. A few CRC errors occur normally when the FOX microcode is downloaded; these do not indicate a failure. Framing Left Right identifies the number of framing errors that have been detected on the left (right) link. A framing error indicates receipt of a corrupted piece of data. The corrupted data is discarded and recovery is automatic.
PAGE 116
ServerNet/FX Adapter Subsystem SCF Commands Out Seq Left STATS LBU Command Example Right identifies the number of packets received on the left (right) link that were dropped because of an out-of-sequence ID. A nonzero value in this field can indicate a hardware or firmware problem in the adapter of the sending cluster. Contact your service provider for assistance in diagnosing and correcting the problem.
PAGE 117
ServerNet/FX Adapter Subsystem SCF Commands STATUS Command STATUS Command STATUS is a nonsensitive command that is used to display current status and configuration information for a specified object. STATUS SUBNET Command Use the STATUS SUBNET command to display current status and configuration information about the specified SUBNET object.
PAGE 118
ServerNet/FX Adapter Subsystem SCF Commands STATUS SUBNET Command The following descriptions explain the fields returned by the STATUS command for the SUBNET object: Name identifies the name of the FOX monitor process, which must be $ZZFOX. State identifies the summary state of the SUBNET object, which must be STARTED. System# identifies the system number of the node on which the ServerNet/FX adapter is located. Cluster# identifies the cluster number currently being used by the ServerNet/FX adapter.
PAGE 119
ServerNet/FX Adapter Subsystem SCF Commands STATUS SUBNET Command System Number identifies the system number of the node on which the ServerNet/FX adapter is located. Cluster Number identifies the cluster number currently being used by the ServerNet/FX adapter. Cluster identifies the cluster number of other known clusters on the FOX ring. Name identifies the system name of operating clusters on the FOX ring.
PAGE 120
ServerNet/FX Adapter Subsystem SCF Commands STATUS SUBNET Command remote Expand-over-FOX line-handler process; the local and remote clusters cannot communicate. View Ring Topology indicates the view of the ring from each logical path. Reading left to right, these are the clusters encountered on a specified path. The clusters seen by $ZZFOX.#X and $ZZFOX.#Y in the same direction should always match. The left and right directions should be transpositions of each other.
PAGE 121
ServerNet/FX Adapter Subsystem SCF Commands STATUS SUBNET Command Table 4-6. Ring Termination States of the FOX Ring Subnetwork (page 2 of 3) Ring Termination Status Description No Neighbor Available No ServerNet/FX adapter has been started along the path. This occurs if the serial links from the local cluster are physically broken or disconnected. Poor Quality Of the 10,000 special control packets transmitted to test line quality, less than 9990 arrived. The serial link in this direction failed.
PAGE 122
ServerNet/FX Adapter Subsystem SCF Commands STATUS SUBNET Command Table 4-6. Ring Termination States of the FOX Ring Subnetwork (page 3 of 3) Ring Termination Status Description Disconnected By Operator The operator has issued the DISCONNECT command to detach the link. Status Changing This is the transition code for termination codes. This is a temporary condition. Check the subnet status again in two minutes.
PAGE 123
ServerNet/FX Adapter Subsystem SCF Commands STATUS PROCESS Command STATUS PROCESS Command Use the STATUS PROCESS command to display current status and configuration information about the specified PROCESS object. The STATUS PROCESS command syntax is STATUS [ /OUT file-spec/ ] PROCESS FOX-process-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS is a keyword specifying that a FOX process name comes next on the command line.
PAGE 124
ServerNet/FX Adapter Subsystem SCF Commands STATUS LBU Command Name identifies the name of the FOX monitor process, which must be $ZZFOX. State identifies the summary state of the PROCESS object. The valid states are STARTED, STOPPED, STARTING, ABORTING, DIAGNOSING, and UNKNOWN. Refer to SCF and LBU Object States on page 4-3 for additional information. STATUS LBU Command Use the STATUS LBU command to display current status and configuration information about the specified LBU object.
PAGE 125
ServerNet/FX Adapter Subsystem SCF Commands STATUS LBU Command Example The following example is similar to the display returned by the STATUS command for an LBU object with the DETAIL option: SCF> STATUS LBU $ZZFOX.#X,DETAIL FOX Detailed Status LBU \GATE7.$ZZFOX.#X Summary State..... STARTED Physical State.... LOADED Controller Type... FX2SA Serial Links: Quality Phy-Neighbor Left: 0.9995 2 Right: 0.9995 5 Bootcode ID: Firmware ID: At 08 May 2001, 13:02:35.543 Logical State..... STARTED System Number...
PAGE 126
ServerNet/FX Adapter Subsystem SCF Commands STATUS LBU Command System Number identifies the system number of the node on which the ServerNet/FX adapter is located. Cluster Number identifies the cluster number currently being used by the ServerNet/FX adapter. Serial Links Left Right indicates the left (right) serial link associated with the specified LBU object ($ZZFOX.#X or $ZZFOX.#Y) Quality Left Right identifies the quality of the transmissions received by the specified LBU object ($ZZFOX.
PAGE 127
ServerNet/FX Adapter Subsystem SCF Commands STATUS LBU Command Table 4-7. Serial Link Status Serial Link Status Description LBU Not Operational An operator stopped an LBU on the FOX ring, or the neighboring ServerNet/FX adapter detected an error and entered the STOPPED state. Check the Ring Topology field using STATUS SUBNET $ZZFOX, DETAIL to see where the break in the ring occurred. If the Ring Topology field lists no clusters along the path for $ZZFOX.#X or $ZZFOX.
PAGE 128
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command Server Net Aging Interval: identifies the ServerNet input area aging interval, in microseconds. Server Net Packet Timeout: identifies the ServerNet packet timeout, in microseconds. Barrier Packet Timeout: identifies the barrier packet timeout, in microseconds. Time Since LBU Start identifies the elapsed time, in microseconds, since the last time the adapter was powered on. This value will wrap around in approximately 500 days.
PAGE 129
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command local-processor is the processor number in the local cluster that specifies the beginning of the FOX direct logical path for which you are requesting status information. A localprocessor or an asterisk (*) must be explicitly specified. remote-cluster is the system name of one of the clusters (other than the local cluster) on the FOX ring to which remote-processor belongs. A remote-cluster or an asterisk (*) must be explicitly specified.
PAGE 130
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command by using the DETAIL option. The example shows the FOX connectivity status from the local cluster (\GATE3) to \GATE5: SCF> STATUS PATH $ZZFOX.*, TO \GATE5.* FOX Status PATH \GATE3.$ZZFOX.*, TO \GATE5.* At 11 May 2001, 15:32:45.556 Cluster Number... 3 System Name...... \GATE3 System Number.... 56 Cluster Number ------5 System Name -----\GATE5 Local Cluster ------------XLBU Logical State.... STARTED YLBU Logical State....
PAGE 131
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command CPU Stuck identifies the number of CPU stuck states for the specified FOX connection. Note. Although a CPU stuck state is symmetric on two processors over different clusters, the STATUS PATH command returns CPU stuck state details from the perspective of the local cluster. The remote cluster may take up to 10 minutes to declare a CPU stuck state for the same FOX direct logical connection.
PAGE 132
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command The following example is similar to the display returned by the STATUS PATH command with the DETAIL option. The example shows the FOX connectivity and FOX direct logical path status from the local cluster (\GATE3) to \GATE5: SCF> STATUS PATH $ZZFOX.*, TO \GATE5.*, DETAIL FOX Detailed Status PATH \GATE3.$ZZFOX.*, TO \GATE5.* At 11 May 2001, 15:40:05.327 Cluster Number... 3 System Name...... \GATE3 System Number....
PAGE 133
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command Cluster Number identifies the FOX cluster number. System Name identifies the system name of the cluster. System Number identifies the system number of the cluster. X(Y)LBU Logical State identifies the current logical state of the LBU object ($ZZFOX.#X and $ZZFOX.#Y) in the local cluster. States are UNDEFINED, UNKNOWN, ABSENT, STOPPED, and STARTED. Refer to LBU Object Logical States on page 4-4 for additional information.
PAGE 134
ServerNet/FX Adapter Subsystem SCF Commands STATUS PATH Command -STUCKindicates all four FOX direct logical paths are down. The processor in the local cluster is in the stuck state. --UNA-indicates the processor in the remote cluster is down or nonexistent. --UNA-overrides all the other status notations. <-DOWN indicates the processor in the local cluster is down or nonexistent.
PAGE 135
ServerNet/FX Adapter Subsystem SCF Commands STOP Command STOP Command The STOP command terminates the execution of the operational firmware in the specified ServerNet/FX adapter. The LBU is reset to the STOPPED summary state. STOP is nearly identical to the ABORT command. Unlike ABORT, however, STOP terminates a ServerNet/FX adapter only if the adapter is in a STARTED state. STOP is a sensitive command.
PAGE 136
ServerNet/FX Adapter Subsystem SCF Commands VERSION Command VERSION Command The VERSION command displays the version of the FOX subsystem. It requires no object, but it does require the FOX monitor process ($ZZFOX) name. VERSION is a nonsensitive command. The VERSION command syntax is VERSION [ /OUT file-spec/ ] FOX-process-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 137
ServerNet/FX Adapter Subsystem SCF Commands Examples GUARDIAN - T9050 - (Q06) identifies the version of the NonStop Kernel operating system. SCF KERNEL - T9082G02 - (26JUN00) (20MAR00) identifies the version of the SCF Kernel (T9082G02), the release date (26JUN00), and the compile date (20MAR00). FOX PM - T9533G05 - (28MAR01) - (23APR91) identifies the version of the FOX/SCF Interface (T9533G05), the release date (28MAR01), and the compile date (23APR91).
PAGE 138
ServerNet/FX Adapter Subsystem SCF Commands ServerNet/FX Adapter Configuration and Management Manual—426872-002 4- 62 Examples
PAGE 139
5 Troubleshooting This section explains the various steps required to troubleshoot the ServerNet/FX adapter subsystem and how and when to use various utilities to identify and resolve problems.
PAGE 140
Troubleshooting Troubleshooting Methodology Troubleshooting Methodology To quickly and efficiently identify and resolve ServerNet/FX adapter subsystem problems, HP recommends that you use a standard troubleshooting methodology.
PAGE 141
Troubleshooting OSM and TSM Client Software OSM and TSM Client Software You can use the OSM Service Connection or the TSM Service Application to display attributes for a selected ServerNet/FX adapter. You can also use the OSM or TSM Low-Level Link to view a limited set of attributes. The attributes for a selected ServerNet/FX adapter appear in the attributes pane of each application. Refer to Monitoring FOX Ring Activity on page 3-3 for detailed information about using OSM and TSM to monitor attributes.
PAGE 142
Troubleshooting Subsystem Control Facility (SCF) For more detailed information about using the TSM EMS Event Viewer, refer to the TSM Online User Guide. Subsystem Control Facility (SCF) The SCF interface to the ServerNet/FX adapter subsystem provides several commands that display information to help you determine the normal operation of your FOX ring. These commands are outlined in Monitoring FOX Ring Activity on page 3-3.
PAGE 143
Troubleshooting Resolving Problems Scanning for Alarms and Running Diagnostics with TSM In addition to displaying attributes as explained in OSM and TSM Client Software on page 5-3, you can also use the OSM Service Connection or the TSM Service Application to scan for alarms and run diagnostic tests. For more information on viewing alarms, refer to the online help within each application. An alarm is a message, similar to an event message, that reports detected faults or abnormal conditions.
PAGE 144
Troubleshooting Escalating Problems more information about using the TMDS STATUS RING command, refer to the TMDS Reference Manual. Escalating Problems If you need to bring a problem to the attention of your HP representative, HP recommends that you have the following information available: • • • • • • A description of the problem (either verbal or written). Any related error messages. Action taken to resolve the problem. Results of traces taken up to the point of failure.
PAGE 145
A SCF Command Summary This appendix summarizes the syntax for the ServerNet/FX adapter subsystem SCF commands explained in Section 4, ServerNet/FX Adapter Subsystem SCF Commands. ABORT Command The ABORT command syntax is ABORT [ /OUT file-spec/ ] LBU LBU-name ADD Command The ADD command syntax is ADD [ /OUT file-spec/ ] LBU LBU-name { attribute-spec }... ALTER Command The ALTER command syntax is ALTER [ /OUT file-spec/ ] LBU LBU-name [ , DEFAULT ] { attribute-spec }...
PAGE 146
SCF Command Summary INFO PROCESS Command INFO PROCESS Command The INFO PROCESS command syntax is INFO [ /OUT file-spec/ ] PROCESS FOX-process-name [ , DETAIL ] [ , DEFAULT ] INFO LBU Command The INFO LBU command syntax is INFO [ /OUT file-spec/ ] LBU LBU-name [ , DETAIL ] [ , DEFAULT ] PRIMARY Command The PRIMARY command syntax is PRIMARY [ /OUT file-spec/ ] PROCESS FOX-process-name , CPU-number START LBU Command The START LBU command syntax is START [ /OUT file-spec/ ] LBU LBU-name START PATH Command
PAGE 147
SCF Command Summary STATUS SUBNET Command STATUS SUBNET Command The STATUS SUBNET command syntax is STATUS [ /OUT file-spec/ ] SUBNET FOX-process-name [ , DETAIL] STATUS PROCESS Command The STATUS PROCESS command syntax is STATUS [ /OUT file-spec/ ] PROCESS FOX-process-name [ , DETAIL ] STATUS LBU Command The STATUS LBU command syntax is STATUS [ /OUT file-spec/ ] LBU LBU-name [ , DETAIL ] STATUS PATH Command The STATUS PATH command syntax is STATUS [ /OUT file-spec/ ] PATH $ZZFOX [.local-processor | .
PAGE 148
SCF Command Summary VERSION Command ServerNet/FX Adapter Configuration and Management Manual—426872-002 A- 4
PAGE 149
B Error Messages This appendix lists and explains the error messages returned by the FOX SCF command interpreter. FOX SCF Command Error Messages The following error messages can be returned by the FOX SCF command interpreter. Each message has a Cause, an Effect, and a Recovery explanation. FOX E00001 LBU is already connected in that direction. Cause. The LBU ($ZZFOX.#X or $ZZFOX.#Y) associated with the ServerNet/FX adapter is already connected in the direction specified. Effect.
PAGE 150
Error Messages FOX SCF Command Error Messages FOX E00006 LBU Could not be started. See the status above for the reason. Cause. The cause is displayed in the error codes returned when you issue the START command. Possible errors include a file system error in accessing the microcode file and a missing module name in the microcode file. Effect. The START command failed. The LBU ($ZZFOX.#X or $ZZFOX.#Y) associated with the ServerNet/FX adapter could not be started. Recovery.
PAGE 151
Error Messages FOX SCF Command Error Messages FOX E00009 LBU could not be altered because there was no record defined in the database. Cause. There is no record for the LBU ($ZZFOX.#X or $ZZFOX.#Y) associated with the ServerNet/FX adapter in the configuration database. Effect. The ALTER command failed. The specified LBU ($ZZFOX.#X or $ZZFOX.#Y) associated with the ServerNet/FX adapter could not be altered. Recovery. Issue the ADD command and then reissue the ALTER command.
PAGE 152
Error Messages FOX SCF Command Error Messages FOX E00014 Remote line handler down to the local system. Cause. The Expand-over-FOX line-handler process for the local cluster is not up in the remote system. Effect. The path to the remote system cannot be started. Recovery. Issue the STATUS SUBNET command to check the status of the FOX ring, and take the necessary action to start the Expand-over-FOX line-handler processes for the local cluster in the remote system and bind them to $ZZFOX.
PAGE 153
Error Messages FOX SCF Command Error Messages FOX E00101 Duplicate Attribute. Cause. The ALTER command line contains duplicate attributes (PROGRAM, MODULE, or SAMPLEINT is repeated in the SCF command line). Specify an attribute only once for each ALTER command. Effect. The ALTER command failed. Recovery. Eliminate the duplicate attribute and reissue the command. FOX E00102 Duplicate Modifier. Cause. The STATS command modifier (RESET) is repeated in the SCF command line.
PAGE 154
Error Messages FOX SCF Command Error Messages FOX E00105 Invalid LBU name. Please specify $ZZFOX.#X or $ZZFOX.#Y. Cause. An invalid name was given for the ServerNet/FX adapter. The ServerNet/FX adapter can have only one of two names: $ZZFOX.#X or $ZZFOX.#Y. Effect. The command failed. Recovery. Use $ZZFOX.#X for a ServerNet/FX adapter connected to the X-fabric (slot 51 or 53) or $ZZFOX.#Y for a ServerNet/FX adapter connected to the Y-fabric (slot 52 or 54), and reissue the command.
PAGE 155
Error Messages FOX SCF Command Error Messages FOX E00109 CPU valid values 0 - 15. Cause. The value specified for the processor is out of range or the processor is nonexistent. Effect. The START PATH command was not executed. Recovery. Reissue the START PATH command with valid processor values. FOX E00110 Path name specified is invalid. Cause. The name specified for the path is invalid. Valid values are XL, XR, YL, YR, or ALL. Effect. The START PATH command was not executed. Recovery.
PAGE 156
Error Messages FOX SCF Command Error Messages ServerNet/FX Adapter Configuration and Management Manual—426872-002 B- 8
PAGE 157
C ServerNet/FX Adapter Self-test Codes ServerNet/FX adapter Self-test Codes are returned by the ServerNet/FX adapter subsystem SCF START command when an attempt to start an LBU fails. The START command is explained in Section 4, ServerNet/FX Adapter Subsystem SCF Commands.
PAGE 158
ServerNet/FX Adapter Self-test Codes Code Description 0x2220 Processor Stack Pointers Test 0x2230 Processor Access Control Unit Test 0x2240 Processor Caches Enable Test 0x3110 QUICC Register Address Test 0x3120 QUICC Register Data Test 0x3130 QUICC Register Alignment Test 0x3140 QUICC Register Byte Write Test 0x3210 QUICC Internal RAM Test 0x3310 QUICC Periodic Interval Timer Test 0x3410 QUICC Interrupt Test 0x3510 QUICC Software Watchdog Timer Test 0x3610 QUICC Bus Access Timer Te
PAGE 159
ServerNet/FX Adapter Self-test Codes Code Description 0x7230 Tioga Unmasking Interrupt Test 0x7240 Tioga Interrupt Level Test 0x7310 Tioga Pass through Data Test 0x7320 Tioga Pass through Line Data Test 0x7410 Tioga Pass through Write Bus Time-out Test 0x7450 Tioga Pass through Read Bus Time-out Test 0x7510 Tioga Pass through Parity Test 0x7610 Tioga Reg Line Access Error Test 0x8110 SAR RAM Data Test 0x8120 SAR RAM Alignment Test 0x8130 SAR RAM Byte Write Test 0x8140 SAR RAM Line
PAGE 160
ServerNet/FX Adapter Self-test Codes Code Description 0xC080 Tioga DMA SAR RAM Sol In D Test 0xC090 Tioga DMA SAR RAM Sol Out D Test 0xC0A0 Tioga DMA SAR RAM Sol In C Test 0xC0B0 Tioga DMA SAR RAM Sol Out C Test 0xC110 Tioga DMA Sol In C Port 0 Test 0xC120 Tioga DMA Sol In D Port 0 Test 0xC130 Tioga DMA Sol Out C Port 0 Test 0xC140 Tioga DMA Sol Out D Port 0 Test 0xC150 Tioga DMA Sol In C Port 1 Test 0xC160 Tioga DMA Sol In D Port 1 Test 0xC170 Tioga DMA Sol Out C Port 1 Test 0xC180
PAGE 161
ServerNet/FX Adapter Self-test Codes Code Description 0xCB30 Tioga DMA Multi Channel Test 0xCB40 Tioga DMA Clean Stop Test 0xCB50 Tioga DMA Panic Stop Test 0xCB60 Tioga External SNet Loopback Test 0xCC10 Tioga DMA LP Bus Write Parity Test 0xCC20 Tioga DMA LP Bus Read Parity Tests 0xCC40 Tioga DMA IO Bus Read Parity Tests 0xCC50 Tioga DMA LP Bus Write Time-out Test 0xCC60 Tioga DMA LP Bus Read Time-out Test 0xCC70 Tioga DMA IO Bus Write Time-out Test 0xCC80 Tioga DMA IO Bus Read Time-
PAGE 162
ServerNet/FX Adapter Self-test Codes Code Description 0x8090 Sram_2 to Dram Block Move 0x80A0 Sram_1 to Sram_2 Block Move 0x80B0 Sram_2 to Sram_1 Block Move 0x80C0 No Transfer Block Move 0x80D0 Dram Bus Others Parity Error 0x80E0 Dram Bus Nonmove Parity Error 0x80F0 Dram Bus Move Parity Error 0x8100 Sram Bus Others Parity Error 0x8110 Sram Bus Nonmove Parity Error 0x8130 Sram Bus Move Parity Error 0x9010 TXRX_1 Register Data Test 0x9020 TXRX_1 Register Address Test 0x9040 TXRX_2
PAGE 163
Glossary ABORT command. A sensitive SCF command that terminates the operation of a specified object abruptly without regard for interruption of data transfer. adapter. See ServerNet/FX adapter. ADD command. A sensitive SCF command that adds the configuration records for the specified object to the system configuration database. ALTER command. A sensitive SCF command that changes the values of the attributes of an existing object. This command changes only the specified attributes of the named object.
PAGE 164
Glossary customer-replaceable unit (CRU) customer-replaceable unit (CRU). A subset of field-replaceable units (FRUs) that can be installed and serviced (replaced) by customers, without using special tools or special HP training. CRUs can be replaced while the system is running. See also field-replaceable unit (FRU). DELETE command. A sensitive SCF command that deletes the configuration records for the specified object from the system configuration database. DISCONNECT command.
PAGE 165
Glossary Expand bypass Expand bypass. The NonStop message system bypasses the Expand subsystem when sending certain messages between neighbor systems on the same FOX ring. These messages are handled directly by the ServerNet X and Y fabrics and the ServerNet/FX adapters. Expand neighbors. Two adjacent Expand systems that have a path between them. fabric. A complex set of interconnections through which there can be multiple and (to the user) unknown paths from point to point.
PAGE 166
Glossary FOX logical neighbors FOX logical neighbors. Two FOX clusters, each running operational microcode and a working FOX monitor process ($ZZFOX). The two FOX clusters must be either FOX physical neighbors or separated only by FOX clusters in any adapter passthrough mode; that is, the intervening nodes must act as hardware or software repeaters. The $ZZFOXs in FOX logical neighbors are communicating with each other. FOX Physical Neighbors.
PAGE 167
Glossary input source input source. The resource from which Subsystem Control Facility (SCF) accepts command input. SCF can accept input from a terminal or a disk file. The initial input source is determined by the form of the RUN command used to initiate SCF. At any time during an SCF session, the input source can be temporarily changed to execute a series of commands from a command file. I/O enclosure.
PAGE 168
Glossary network access method network access method. The interface through which an Expand-over-FOX line-handler process communicates with the FOX monitor process ($ZZFOX). nonsensitive command. A command that can be issued by any user or program that is allowed access to the subsystem—that is, a command on which the subsystem imposes no further security restrictions.
PAGE 169
Glossary Passthrough modes Passthrough modes. Hardware Passthrough: the ServerNet/FX adapter has power but is not running operational microcode; it acts only as a hardware repeater. Packets pass directly from one fiber-optic cable to another; they are regenerated but not reshaped or resynchronized. Packets that travel though two or more hardware passthrough clusters might be damaged. Physical Passthrough: same as hardware passthrough.
PAGE 170
Glossary product module (PM) product module (PM). The part of the Subsystem Control Facility (SCF) subsystem that is responsible for subsystem-specific command processing. SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP). sensitive command. A Subsystem Control Facility (SCF) command that can be issued only by a user with super-group access, by the owner of the subsystem, or by a member of the group of the owner of the subsystem.
PAGE 171
Glossary STOP command. STOP command. A sensitive SCF command that normally terminates the activity of an object. It deletes all connections to and from the object in a nondisruptive way. SUBSYS object type. The Subsystem Control Facility (SCF) object type for most subsystems that use SCF as the user interface. subsystem. (1) A secondary or subordinate system, usually capable of operating independently of or asynchronously with a controlling system.
PAGE 172
Glossary system system. A node. All the processors, controllers, firmware, peripheral devices, software, and related components that are directly connected together to form an entity that is managed by one operating system image and operated as one computer. system enclosure. An enclosure for system components. Processor enclosures and I/O enclosures are both system enclosures. TACL. See HP Tandem Advanced Command Language (TACL) VERSION command.
PAGE 173
Index A D ABORT command 4-7 comparison to START, STOP, CONNECT, and DISCONNECT 4-17 example 4-8 syntax 4-7, A-1 ADD command 4-9 example 4-12 syntax 4-9, A-1 ALTER command 4-13 example 4-16 syntax 4-13, A-1 altering FOX Monitor Process($ZZFOX) using SCF 3-8 LBU configurations using SCF 3-7 using TSM 3-7 DELETE command 4-20 example 4-20 syntax 4-20, A-1 DISCONNECT command 4-21 comparison to START, STOP, ABORT, and CONNECT 4-17 example 4-22 syntax 4-21, A-1 C checking status using SCF 3-5 using TSM 3-6 clu
PAGE 174
Index F (continued) F (continued) FOX ring adding a cluster to 3-14 controlling 3-9 definition 1-6 hardware components 1-4 overview 1-2 removing a cluster from 3-22 software components 1-4 status as seen from $ZZFOX 4-45 FOX SUBNET status of FOX ring as seen from $ZZFOX 4-45 modifying attributes for 3-7 starting after system name change 3-10, 4-12, 4-16, 4-20, 4-29 using SCF 3-10 stopping 3-10 Line Handlers, FOX See Expand-over-FOX line handler process LISTDEV command 4-23, 4-48 Logical Layout FOX Ring 1
PAGE 175
Index P P Path Down Recovery from 3-24 PATH object defined 1-7 STATUS command 4-53 Path object START command 4-31 Physical Layout FOX Ring 1-2 physical states 4-6 PMF CRU replacement preparing ServerNet/FX adapters 3-29 PRIMARY command 4-28 example 4-28 syntax 4-28, A-2 Primary CPU switching 4-28 PROCESS object defined 1-6 INFO command 4-24 STATUS command 4-48 R Recovering FOX direct logical paths 3-24 Ring configuration logical 1-3 physical 1-2 S SCF running remotely 3-3 SCF objects summary states 4-3
PAGE 176
Index S (continued) S (continued) Y STATUS SUBNET command 4-42 example 4-42 syntax 4-42, A-3 STOP command 4-60 comparison to START, ABORT, CONNECT, and DISCONNECT 4-17 example 4-60 syntax 4-60, A-3 SUB command parameter support for 4-2 SUBNET status of FOX ring as seen from $ZZFOX 4-45 SUBNET object defined 1-6 STATUS command 4-42 YL YR defined 1-7 Special Characters $ZZFOX defined 1-6 preparing for PMF or IOMF CRU replacement 3-29 switching primary and backup processors for 3-14 $ZZFOX.