LAN Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

LAN Configuration and

Management Manual

Abstract

This manual describes how to configure, operate, and manage the ServerNet

LAN Systems Access (SLSA) subsystem on an

HP Integrity Nonstop™ NS-series

or HP NonStop S-series server. This manual includes detailed descriptions of the

Subsystem Control Facility (SCF) commands used with the SLSA subsystem

and a quick-reference section showing SCF command syntax.

Product Version

SLSA G06

Supported Release Version Updates (RVUs)

This manual supports G06.24 and all subsequent G-series RVUs and H06.03 and all

subsequent H-series RVUs and J06.03 and all subsequent J-series RVUs until

otherwise indicated by its replacement edition.

Part Number Published

520469-012 August 2012

Summary of content (256 pages)

PAGE 1
LAN Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the ServerNet LAN Systems Access (SLSA) subsystem on an HP Integrity Nonstop™ NS-series or HP NonStop S-series server. This manual includes detailed descriptions of the Subsystem Control Facility (SCF) commands used with the SLSA subsystem and a quick-reference section showing SCF command syntax. Product Version SLSA G06 Supported Release Version Updates (RVUs) This manual supports G06.
PAGE 2
Document History Part Number Product Version Published 520469-007 SLSA G06 July 2005 520469-008 SLSA G06 September 2005 520469-009 SLSA G06 May 2006 520469-010 SLSA G06 November 2006 520469-011 SLSA G06 August 2010 520469-012 SLSA G06 August 2012
PAGE 3
Legal Notices  Copyright 2012 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 4
PAGE 5
LAN Configuration and Management Manual Index Figures Tables Legal Notices What’s New in This Manual 3 Manual Information 3 New and Changed Information 4 HP Encourages Your Comments 5 About This Manual vii Who Should Use This Manual vii What’s in This Manual vii Where to Get More Information viii Notation Conventions viii Abbreviations xiii 1.
PAGE 6
Contents 3.
PAGE 7
4.
PAGE 8
5.
PAGE 9
A. Command Summary Contents A. Command Summary B. SCF Error Messages Index Figures Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 3-1. Figure 3-2. Figure 4-1. Figure 4-2.
PAGE 10
Contents LAN Configuration and Management Manual—520469-012 vi
PAGE 11
What’s New in This Manual Manual Information LAN Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the ServerNet LAN Systems Access (SLSA) subsystem on an HP Integrity Nonstop™ NS-series or HP NonStop S-series server. This manual includes detailed descriptions of the Subsystem Control Facility (SCF) commands used with the SLSA subsystem and a quickreference section showing SCF command syntax.
PAGE 12
What’s New in This Manual New and Changed Information New and Changed Information New and Changed Information for the 520469-012 Edition This edition of the manual has been revised to inculde the following update:  Added a note to AUTONEGOTIATION on page 4-33 New and Changed Information for the 520469-011 Edition This edition of the manual has been updated for Token-Ring connectivity on NonStop BladeSystems and includes these updates:      ServerNet Architecture and SLSA on page 2-5 SLSA Subsys
PAGE 13
What’s New in This Manual New and Changed Information for the 520469-009 Edition New and Changed Information for the 520469-009 Edition The LAN Configuration and Management Manual has been revised to include:   Updated physical slot information for the Gigabit Ethernet 4-port ServerNet adapter (G4SA) (See slot on page 3-7.) Updated reference to planning guides (See LAN Configuration on page 3-9.) HP Encourages Your Comments HP encourages your comments concerning this document.
PAGE 14
What’s New in This Manual HP Encourages Your Comments LAN Configuration and Management Manual—520469-012 x
PAGE 15
About This Manual This manual describes how to configure, operate, and manage the ServerNet LAN Systems Access (SLSA) subsystem on an Integrity NonStop NS-series or NonStop S-series server. This manual includes descriptions of the Subsystem Control Facility (SCF) commands used with the SLSA subsystem and a quick-reference section showing the command syntax.
PAGE 16
Where to Get More Information About This Manual Where to Get More Information Depending on the tasks you are performing, you might need the following manuals:            NonStop NS-Series Planning Guide NonStop NS16000 Planning Guide (available in H06.08 and subsequent H-series RVUs) NonStop NS14000 Planning Guide (available in H06.08 and subsequent H-series RVUs) NonStop NS1000 Planning Guide (available in H06.
PAGE 17
General Syntax Notation About This Manual computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets.
PAGE 18
General Syntax Notation About This Manual Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing.
PAGE 19
Notation for Messages About This Manual !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal.
PAGE 20
Notation for Management Programming Interfaces About This Manual { } 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 can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
PAGE 21
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL environment and the Common Run-Time Environment (CRE).
PAGE 22
Abbreviations About This Manual LANMAN. LAN Manager LANMON. LAN Monitor LIF. logical interface MAC. media access control mbps. megabits per second MAU. medium attachment unit MFIOB. multifunction I/O board PIF. physical interface PMF CRU. processor multifunction customer replaceable unit POST. power-on self-test PVC. Permanent Virtual Circuit QIO. Queued input output SAC. servernet addressable controller SAN. system area network SCF. Subsystem Control Facility SCP. Subsystem Control Point SEB.
PAGE 23
1 Configuration Quick Start This section describes your initial ServerNet LAN Systems Access (SLSA) subsystem configuration and how to verify that required SLSA subsystem processes and objects are configured and started. Note. All adapters ordered with a NonStop system are configured by HP manufacturing in the initial system configuration. Only follow the procedures described in this section if you are altering the configuration of the SLSA subsystem provided by HP or are installing additional adapters.
PAGE 24
Configuration File Contents Configuration Quick Start Configuration File Contents HP manufacturing used the following configuration files to create your initial system configuration. These files are located in the $SYSTEM.ZSYSCONF subvolume.    SCF0000 STARTCOM STARTSCF Contents of the SCF0000 File The SCF0000 file contains Subsystem Control Facility (SCF) commands that configure the following LAN subsystem processes and objects:   LAN Manager (LANMAN) process ($ZZLAN).
PAGE 25
Checking the State of the LAN Manager (LANMAN) Process Configuration Quick Start Checking the State of the LAN Manager (LANMAN) Process Use the SCF STATUS PROCESS command to determine the current state of the LAN Manager (LANMAN) process: STATUS PROCESS $ZZLAN Checking the State of the LAN Monitor (LANMON) Processes Note. As of the G06.21 RVU, a new LANMON can be installed without a cold load. Refer to Replacing a LANMON Without a Cold Load on page 5-10 for more information.
PAGE 26
Checking the State of the SLSA Subsystem Objects Configuration Quick Start Checking the State of the Subnets Use the SCF STATUS SUBNET command to determine the state of each preconfigured subnet: For conventional TCP/IP: STATUS SUBNET $tcpip process-name.* Note. Parallel Library TCP/IP is not supported on Integrity NonStop NS-series servers. For Parallel Library TCP/IP and NonStop TCP/IPv6: STATUS SUBNET $ZZTCP.
PAGE 27
Troubleshooting Tips Configuration Quick Start Troubleshooting Tips All the required processes and objects described in Initial SLSA Subsystem Configuration should be started during the system-load sequence. If you discover that a process or object is in the STOPPED state, determine the cause of the problem, then start the process or other object.
PAGE 28
Starting a TCP/IP Process Configuration Quick Start Starting a TCP/IP Process Caution. NonStop TCP/IPv6 and Parallel Library TCP/IP are incompatible and cannot run on the same system. Parallel Library TCP/IP is not supported on Integrity NonStop NS-series servers.    If you are using conventional TCP/IP and there is no TCP/IP process, rerun the STARTCOM file. STARTCOM configures the TCP/IP processes and calls STARTSCF which starts the subnets and routes.
PAGE 29
Installing an Adapter Configuration Quick Start Starting a PIF Object If a PIF object is in the STOPPED state, use the SCF START PIF command to start it: START PIF $ZZLAN.pif-name pif-name is the name of the PIF object to start. Starting a LIF Object If a LIF object is in the STOPPED state, use the SCF START LIF command to start it: START LIF $ZZLAN.lif-name lif-name is the name of the LIF object to start. Starting an ATMSAP Object START ATMSAP $ZZLAN.
PAGE 30
Changing the Initial SLSA Subsystem Configuration Configuration Quick Start Adapter Manuals (page 2 of 2) SWAN 2 Concentrator Installation and Support Guide for the SWAN 2 Concentrator (T3881) Versatile I/O Manual WAN Subsystem Configuration and Management Manual (SWAN and SWAN 2 concentrator configuration information) Changing the Initial SLSA Subsystem Configuration After installing your adapter, you might want to change the initial SLSA subsystem configuration.
PAGE 31
2 Introduction to the SLSA Subsystem This section describes the ServerNet LAN Systems Access (SLSA) subsystem architecture. Overview of SLSA 2-1 ServerNet Architecture and SLSA 2-5 The SLSA Role Within the System 2-7 Architecture of the SLSA Subsystem 2-10 Fault Tolerance of the SLSA Subsystem 2-16 Overview of SLSA In the NonStop system, the communications adapter communicates with multiple processors simultaneously delivering data directly to the processor that contains the target client.
PAGE 32
Overview of SLSA Introduction to the SLSA Subsystem Table 2-1. SLSA Software Components SLSA Software Component LAN manager (LANMAN) process Description     Manages all SLSA objects in the system Receives management commands from the user through SCF and communicates the commands to a LANMON process Starts and stops the LANMON processes in each processor Manages the assignment of adapters to specific LANMON processes For more information about LAN manager, see Processes on page 2-11.
PAGE 33
Overview of SLSA Introduction to the SLSA Subsystem Table 2-2. SLSA Data Structures in Adapters SLSA Data Structure Description Logical interface (LIF) Allows QIO clients (NonStop TCP/IP and IPX/SPX) to connect their queues to one or more PIFs. For more information about LIFs, see Logical Interface (LIF) on page 2-15. Physical interface (PIF) Represents the physical connection to the LAN. The PIF is an abstraction that is used to transmit MAC-layer statistics and information.
PAGE 34
Overview of SLSA Introduction to the SLSA Subsystem Figure 2-1 shows that:  Data from an application is sent by TCP/IP or IPX/SPX into the SLSA QIO segment of the processor. Note. IPX/SPX is not supported on systems running H-series or J-series RVUs.   From the queue, the data goes to a LIF where the data is associated with one of the PIFs. The data then goes to a SAC, which gives the data the IP address of a LAN. From the SAC, the data moves to a PIF and is given a MAC address and sent to the LAN.
PAGE 35
Introduction to the SLSA Subsystem ServerNet Architecture and SLSA ServerNet Architecture and SLSA Note. J-Series RVUs and NonStop BladeSystems have different architecture and networking considerations. For more information, see the HP NonStop Networking Overview. The ServerNet architecture on Integrity NonStop NS-series or NonStop S-series servers allows up to 16 processors in a system to have direct access to a logical interface (LIF).
PAGE 36
ServerNet Architecture and SLSA Introduction to the SLSA Subsystem Figure 2-2. Multiple TCP/IP Processes for One DNS Entry Processor 0 Processor 1 Processor 2 Processor 3 Domain Name Server TCP1 1.2.3.4 TCP2 1.2.3.5 TCP3 1.2.3.6 TCP4 1.2.3.7 http://www.mycompany.com 1.2.3.4 1.2.3.6 1.2.3.5 1.2.3.7 ServerNet Fabrics Y X LAN Adapter VST807.
PAGE 37
The SLSA Role Within the System Introduction to the SLSA Subsystem Figure 2-3. Single TCP/IP Process for One DNS Entry Processor 0 Processor 1 Processor 2 Processor 3 Domain Name Server $ZPTM0 1.2.3.4 $ZPTM1 1.2.3.4 $ZPTM2 1.2.3.4 $ZPTM3 1.2.3.4 http://www.mycompany.com 1.2.3.4 ServerNet Fabrics Y X LAN Adapter VST808.vsd The SLSA Role Within the System The SLSA subsystem provides access to parallel LAN and WAN I/O for Integrity NonStop NS-series servers and NonStop S-series servers.
PAGE 38
System-Level Processes and Libraries Introduction to the SLSA Subsystem Figure 2-4. The SLSA Subsystem Role Within a NonStop System Processor User Applications Socket Library SCF File or Message System Interface I/O processes that use the WAN subsystem include: X25AM, AM, TR, CP6100, ENVOY, Envoy ACP/XF, Expand, SNAX/APN, and SNAX/XF.
PAGE 39
LAN Service Providers Introduction to the SLSA Subsystem ServerNet adapters and uses system-library routines accessible to LAN service-provider processes (such as TCP/IP). LAN Service Providers Local area network (LAN) service providers are processes that use the SLSA subsystem to send and receive data on a LAN attached to the system.
PAGE 40
Architecture of the SLSA Subsystem Introduction to the SLSA Subsystem Architecture of the SLSA Subsystem The SLSA subsystem includes hardware components and software processes. SCF provides the management interface for the SLSA subsystem.
PAGE 41
Introduction to the SLSA Subsystem SLSA Subsystem SCF Objects SLSA Subsystem SCF Objects The SCF objects for the SLSA subsystem consist of manager and monitor processes and several other objects that correspond to components of the adapters that connect the LANs to the server. The PROCESS and MONITOR objects correspond to the process used to manage (LANMAN) and monitor (LANMON) the SLSA subsystem through SCF. The SCF objects related to adapters are the ADAPTER, SAC, LIF, and PIF objects.
PAGE 42
Introduction to the SLSA Subsystem SLSA Subsystem SCF Objects Monitors Note. As of the G06.21 RVU, a new LANMON can be installed without a cold load. Refer to Replacing a LANMON Without a Cold Load on page 5-10 for more information. The monitor objects are the control processes in the SLSA subsystem. The LANMAN process creates a monitor in each processor. If a monitor process fails, LANMAN restarts it.
PAGE 43
Introduction to the SLSA Subsystem SLSA Subsystem SCF Objects Supported Adapters by NonStop System Type    Adapters for NonStop S-Series systems Adapters for NonStop NS-Series Adapters for NonStop BladeSystems (J06.
PAGE 44
SLSA Subsystem SCF Objects Introduction to the SLSA Subsystem For information about MFIOBs, see the NonStop S-Series Hardware Installation and Fast Path Guide. For information about the other adapters, see Adapter Manuals on page 1-7. For information about the NonStop BladeSystem, including its associated hardware components such as the IP CLuster I/O Module (CLIM), which is also used for Etherent connectivity on J-series RVUs, see the NonStop BladeSystem Planning Guide.
PAGE 45
SLSA Subsystem SCF Objects Introduction to the SLSA Subsystem ATMSAP and Expand The Expand product connects NonStop NS-series or NonStop S-series systems in networks of up to 256 nodes. The SLSA ATMSAP offers an ATM Native Mode network interconnect support similar to that offered by the PVC object within an ATM subsystem. Expand issues native mode frames directly to the ATM product via a LIF associated with an ATMSAP object. Figure 2-7 illustrates ATMSAP use by Expand. Figure 2-7.
PAGE 46
Introduction to the SLSA Subsystem Fault Tolerance of the SLSA Subsystem Fault Tolerance of the SLSA Subsystem The SLSA subsystem operates even after a loss of one of its components. This section describes how the SLSA subsystem maintains data paths to the LAN subsystem when a processor, SAC, media, or adapter is unavailable. Loss of a ServerNet Fabric When access through a ServerNet fabric is lost, all traffic goes through the remaining fabric.
PAGE 47
Introduction to the SLSA Subsystem Loss of a Processor When access to a SAC is lost, SLSA events are generated and stored in the EMS log. The following events may indicate that the SAC has become unavailable to a processor: Event Number Cause 4001 SAC transient fault with a fault number of 2011 to 2014, 2018, 2033, 2036, 2040, 2044, 2045, 3011 to 3018, 3025 to 3027, 3036, 3038, 3043, 3046, or 3047.
PAGE 48
Introduction to the SLSA Subsystem Loss of an Adapter When access to a SAC is lost, SLSA events are generated and stored in the EMS log. The following events may indicate that the SAC has become unavailable to a processor: Event Number Cause 4003 SAC unavailable. 4004 SAC state change. (A SAC that remains in the STARTING state for an unreasonable length of time indicates a problem with the SAC.) 4011 SAC dump file created. (Occurs only if the AUTODUMP option is enabled.
PAGE 49
3 SLSA Subsystem Installation and Configuration SLSA Subsystem Installation 3-1 SLSA Subsystem Configuration 3-2 HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) 3-2 HP Manufacturing Naming Conventions (For G06.27 and Later GSeries RVUs and HO6.03 and Later H-Series RVUs and J06.03 and Later J-Series RVUs) 3-6 LAN Configuration 3-9 Note. For instructions about how to install or replace adapters, see Adapter Manuals on page 1-7.
PAGE 50
SLSA Subsystem Configuration SLSA Subsystem Installation and Configuration SLSA Subsystem Configuration Your Integrity NonStop NS-series or NonStop S-series server is shipped with a generic preconfiguration of the SLSA subsystem, which you can modify. However, changes made to the configuration might also influence the placement and configuration of the connections to any ServerNet wide area network (SWAN) concentrators you plan to attach to your servers. Note.
PAGE 51
SLSA Subsystem Installation and Configuration HP Manufacturing Naming Conventions (G06.26 and Earlier RVUs) cabid is the two-digit number that identifies the enclosure. cabid Description Range of Values 0n The object is in processor enclosure n. 01-08 n1 The object is in I/O enclosure 1 attached to processor enclosure n. 11, 21, 31, 41, 51, 61, 71, or 81 n2 The object is in I/O enclosure 2 attached to processor enclosure n.
PAGE 52
SLSA Subsystem Installation and Configuration G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) Process or Device Type Convention Example LIF object Lcabid-module-portid $ZZLAN.L112A G4SA ADAPTER object Ggroup-module-slot $ZZLAN.G1123 A G4SA must be installed in an I/O adapter module (IOAM) enclosure. Processor multifunction (PMF) or I/O multifunction (IOMF) CRU $ZZLAN.MIOEprocessorid $ZZLAN.
PAGE 53
G4SA Naming Conventions (G06.24, G06.25, and G06.26 RVUs) SLSA Subsystem Installation and Configuration cabid is the two-digit group number that identifies the processor enclosure that is connected to the IOAM or to the IOAM enclosure that contains the G4SA; cabid is also the group number. group Description Range of Values 0n The object is in processor enclosure n. 01-08 1n The object is in I/O enclosure n.
PAGE 54
SLSA Subsystem Installation and Configuration HP Manufacturing Naming Conventions (For G06.27 and Later G-Series RVUs and HO6.
PAGE 55
SLSA Subsystem Installation and Configuration Suggested Naming Conventions for Adapters processorid specifies the process in which the LANMON is running. For example, #ZLM01 specifies the LANMON in processor 1. group is in the range of 110 through 115 for IOAM enclosures installed in NonStop NS16000 systems or NonStop BladeSystems. For IOAM enclosures installed in NonStop NS14000 and NS1000 servers and for VIO enclosures, the group is 100. (VIO enclosures are available in H06.
PAGE 56
SLSA Subsystem Installation and Configuration  Suggested Naming Conventions for Adapters Add the slot number and module number that the adapter is in to the adapter name. For example, a G4SA that is in slot 3 of module 2 of IOAM Group 111, would have the name G11123. Suggested Naming Conventions for ATMSAP Object $ZZLAN.adapter-id.sac-id.pif-id.atmsap-id adapter-id is a 1 to 8-character alpha-numeric string, beginning with an alpha character, that uniquely identifies the target SLSA ADAPTER object.
PAGE 57
SLSA Subsystem Installation and Configuration LAN Configuration Suggested Naming Conventions for SACs and PIFs The SLSA subsystem automatically names the SACs and PIFs based on the name you assign to the adapters. For example, if you assign the name G11123 to a G4SA, the system names the SAC G11123.0. The PIFs for SAC G11123.0 are G11123.0.A, G11123.0.B, G11123.0.C, and G11123.0.D. LAN Configuration 1.
PAGE 58
LAN Configuration SLSA Subsystem Installation and Configuration Figure 3-1.
PAGE 59
LAN Configuration SLSA Subsystem Installation and Configuration Figure 3-2. Example of a Completed Gigabit Ethernet 4-Port ServerNet Adapter (G4SA) Configuration Form \Case 1 System Name 11/04/04 Date Group Adapter Name: G11123 SAC Name: PIF Name: 111 IP Address: G11123.0 G11123.0.D IP Address: Adapter Name: G11123 G11123.0 SAC Name: G4SA PIF Name: G11123.0.C Adapter Name: G11123 PIF D SAC Name: PIF Name: PIF C 192.231.036.100 SAC Access List: LIF Name: (0, 1, 2, 3) L11123D 192.231.036.
PAGE 60
SLSA Subsystem Installation and Configuration LAN Configuration Configuration File To configure the adapters, use a command file to:      Add the adapters and LIFs to the system Start the adapter and its subordinate objects Associate LIFs with each PIF Start the LIFs Assign an IP address to each LIF The following TACL command file configures a single G4SA adapter: ?TACL MACRO PUSH #INLINEPREFIX SET VARIABLE #INLINEPREFIX + SCF /INLINE, OUT [#MYTERM], NAME/ + ASSUME PROCESS $ZZLAN + ADD ADAPTER G11
PAGE 61
4 SCF Commands for the SLSA Subsystem This section describes the Subsystem Control Facility (SCF) commands interpreted for the SLSA subsystem: Supported Commands and Object Types Page 4-2 SCF Objects Page 4-4 Generic Processes Page 4-6 ABORT Command Page 4-7 ADD Command Page 4-15 ALTER Command Page 4-27 DELETE Command Page 4-39 INFO Command Page 4-41 LISTOPENS Command Page 4-63 NAMES Command Page 4-64 RESET Command Page 4-75 START Command Page 4-76 STATISTICS Command Page 4-83 STAT
PAGE 62
Supported Commands and Object Types SCF Commands for the SLSA Subsystem Supported Commands and Object Types This section describes the Subsystem Control Facility (SCF) commands you can use to manage the SLSA subsystem. Table 4-1 lists the SLSA SCF commands and objects along with the page numbers where those commands are described in this manual. (A page number in the object column indicates that the command is supported on that object.
PAGE 63
Command Cancellation SCF Commands for the SLSA Subsystem Table 4-1.
PAGE 64
SCF Objects SCF Commands for the SLSA Subsystem Table 4-2.
PAGE 65
SCF Objects SCF Commands for the SLSA Subsystem The SAC object represents the ServerNet addressable controller and provides the SCF interface for managing the SACs. SCF Object Hierarchy The SCF objects for the SLSA subsystem correspond to process and hardware components within the subsystem. Some objects are subordinate to others. Figure 4-1 shows the hierarchy of the objects in the SLSA subsystem. Note. The PIF object is not subordinate to the LIF.
PAGE 66
SCF Object States SCF Commands for the SLSA Subsystem SCF Object States SCF objects can be in different states of operation, depending on the SCF command issued to that object. The operational states are: STARTED The object is running and is ready to accept requests from other subsystem components. This state results from the START command for most objects. STARTING The object is on its way to the STARTED state because a command was issued to start it.
PAGE 67
SCF Commands for the SLSA Subsystem ABORT Command Generic processes have the following characteristics:      You can configure a generic process to start in one processor, in more than one processor, or in each processor in the system. You can permanently change an attribute of a generic process by using the SCF ALTER command. This change takes effect the next time the process is started. You can create a generic process to run at a high pin or a low pin. The default is to run at a high pin.
PAGE 68
SCF Commands for the SLSA Subsystem ABORT ADAPTER Command SUB [ ONLY | ALL | NONE ] directs the command at a set of subordinate objects. ONLY specifies that only the subordinate objects are affected. ALL specifies that the named object and the subordinate objects are affected. NONE specifies that none of the subordinate objects are affected.
PAGE 69
SCF Commands for the SLSA Subsystem ABORT ATMSAP Command ABORT ATMSAP Command The ABORT ATMSAP command forces an ATMSAP object subordinate to a PIF object to halt operation as soon as possible. The object enters the STOPPED summary state if the command is successful. The command is rejected if the ATMSAP is already in the STOPPED summary state. Command Syntax ABORT [ /OUT file-spec/ ] ATMSAP atmsap-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 70
SCF Commands for the SLSA Subsystem ABORT LIF Command Example ABORT ATMSAP $ZZLAN.ATM01.0.A.ATMSAP01 ABORT LIF Command The ABORT LIF command stops the operation of the specified logical interface (LIF) as quickly as possible and places the LIF in the STOPPED state. Only enough processing is done to ensure that the LIF can run again when it is restarted.
PAGE 71
SCF Commands for the SLSA Subsystem ABORT MON Command ABORT MON Command The ABORT MON command stops the operation of the specified LAN Monitor (LANMON) and places the LANMON in the STOPPED state. Command Syntax ABORT [ /OUT file-spec/ ] MON lanmon OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON lanmon is the name of the LANMON to be aborted. The LANMON name has the form $ZZLAN.lanmon, for example, $ZZLAN.#ZLM01.
PAGE 72
SCF Commands for the SLSA Subsystem ABORT PIF Command Effects of the ABORT MON command on Clients/NonStop TCP/IP (page 2 of 2) Other Clients When a LANMON is aborted, other SLSA clients should handle the situation like NonStop TCP/IP. Other clients that may be affected include PAM, SS7/SHTI, and IPX/SPX. TSM/OSM and SNMP clients should not be affected.
PAGE 73
SCF Commands for the SLSA Subsystem ABORT SAC Command PIF pif-name is the name of the PIF to be aborted. The PIF name has the form $ZZLAN.adaptername.sac-unit#.pif-unit-letter, for example, $ZZLAN.G11123.0.A. SUB { ONLY | ALL | NONE } controls the set of objects and subordinate objects that the command targets:    ONLY specifies that only subordinate objects are targets of the command. ALL specifies that the named object and the subordinate objects are targets of the command.
PAGE 74
SCF Commands for the SLSA Subsystem ABORT SAC Command Command Syntax ABORT [ /OUT file-spec/ ] SAC sac-name [, SUB [ ONLY | ALL | NONE ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SAC sac-name is the name of the SAC to be aborted. The SAC name has the form $ZZLAN.adapter-name.sac-unit#, for example, $ZZLAN.G11123.0. SUB [ ONLY | ALL | NONE ] directs the command at a set of subordinate objects.
PAGE 75
SCF Commands for the SLSA Subsystem ADD Command ADD Command ADD is a sensitive command that defines an object to the SLSA subsystem. The fully-qualified name assigned to the created object must be unique. If an attribute for a given object is not assigned a value in the ADD command, the attribute's default value is used. However, some attributes do not have default values: use the ADD command to assign values. The ADD command does not support wild-card characters.
PAGE 76
ADD ADAPTER Command SCF Commands for the SLSA Subsystem TYPE { E4SA|MIOE|TRSA|FESA|GESA|G4SA|CCSA|ATM3SA } specifies the type of adapter:         E4SA specifies an Ethernet 4 ServerNet adapter (E4SA) MIOE specifies the Ethernet port on the multifunction I/O board (MFIOB) TRSA specifies the Token-Ring ServerNet adapter (TRSA) FESA specifies the Fast Ethernet ServerNet adapter GESA specifies the Gigabit Ethernet ServerNet adapter G4SA specifies the Gigabit Ethernet 4-port Ethernet ServerNet adapte
PAGE 77
SCF Commands for the SLSA Subsystem ADD ADAPTER Command AUTOFIRMUP { ON | OFF } specifies whether the SAC automatically downloads the firmware prior to downloading the operation code. The firmware is downloaded if the version of the firmware file is newer than the firmware version on the adapter. The AUTOFIRMUP option does not apply to MFIOB adapters. The default is ON. AUTOSTART { ON | OFF } specifies whether the SAC and its subordinated PIFs automatically start after a system cold start.
PAGE 78
ADD ADAPTER Command SCF Commands for the SLSA Subsystem        The following table lists the default values for DLFILENAME, FIRMWAREFILENAME and DUMPFILENAME: Adapter DLFILENAME FIRMWAREFILENAME DUMPFILENAME ATM3SA C0440P00 C8158R00 C0440D00 CCSA C0303P00 C0309R00 C0303D00 E4SA C7957P00 C7824R00 C7957D00 TRSA C0084P00 C0232R00 C0084D00 FESA C0301P00 C0283R00 C0301D00 GESA C0507P00 C0506R00 C0507D00 G4SA C0613P00 C0612R00 For MFIOB, the default file names are null.
PAGE 79
SCF Commands for the SLSA Subsystem ADD ADAPTER Command Examples The following example assigns the name E0153 to an E4SA adapter type, residing in module 1, group 1, slot 53 of the system enclosure. ADD ADAPTER $ZZLAN.E0153, TYPE E4SA, & LOCATION (1,1,53), ACCESSLIST (0,1,2,3) The following example assigns the name E0152 to a FESA adapter type, residing in module 1, group 1, slot 52 of the system enclosure. ADD ADAPTER $ZZLAN.
PAGE 80
SCF Commands for the SLSA Subsystem ADD ADAPTER Command The following example assigns the name G11123 to the Ethernet ports residing in module 2, group 100, slot 6 of a VIO enclosure.
PAGE 81
SCF Commands for the SLSA Subsystem ADD ATMSAP Command ADD ATMSAP Command The ADD ATMSAP command configures an ATMSAP object subordinate to a PIF object. The ATMSAP object is left in the STOPPED summary state if the command is successful. The command is rejected if the ATMSAP object name is already configured. The command is also rejected if the maximum ATMSAP objects subordinate to the PIF object have already been defined.
PAGE 82
SCF Commands for the SLSA Subsystem ADD ATMSAP Command MTU max-mtu-size configures the maximum message transfer unit size for the ATMSAP. Valid values: max-mtu-size is a decimal number in the range 1 through 9180. Default value: 9180 NATURE { PVC } configures the virtual connection nature of the ATMSAP component and selects the connection supported for the ATMSAP object. Only PVC type connections are supported.
PAGE 83
ADD LIF Command SCF Commands for the SLSA Subsystem Considerations    An ATMSAP object can be configured to interface to a permanent virtual circuit (PVC) object. A LIF object must be associated with the ATMSAP object in order to provide host access to the ATMSAP object. A PVC connection provides a static permanent virtual circuit. A PVC object is defined with a VCC attribute for the ATMSAP object. The VCC is comprised of a VPI, VCI pair. Use the ADD ATMSAP command to add an ATMSAP object.
PAGE 84
SCF Commands for the SLSA Subsystem ADD LIF Command Command Syntax ADD [ /OUT file-spec/ ] LIF lif-name , {PIF pif-name | ATMSAP atmsap-name } [ , DATAFORWARDMODE df-mode ] [ , DATAFORWARDUNIT df-unit ] [ , DATAFORWARDCOUNT df-count ] [ , DATAFORWARDTIME df-time ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LIF lif-name specifies the name of the LIF to be added. lif-name is in the form $ZZLAN.
PAGE 85
SCF Commands for the SLSA Subsystem ADD LIF Command DATAFORWARDCOUNT df-count specifies the maximum number of inbound frames queued before delivery occurs. df-count is the maximum number of frames queued. Valid values: df-count is a value in the range of 1 through 50. Default value: 10 frames if the DATAFORWARDMODE value is MANUAL; otherwise, DATAFORWARDCOUNT defaults to 15 frames. DATAFORWARDTIME df-time configures the maximum time an inbound frame waits before delivery. df-time is the time to wait.
PAGE 86
SCF Commands for the SLSA Subsystem ADD LIF Command DATAFORWARDUNIT of MICROSECONDS is specified for non-G4SA adapter types.  DATAFORWARDCOUNT and DATAFORWARDTIME are meaningful only when the specified PIF is a part of an Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet adapter (FESA), Gigabit Ethernet ServerNet adapter (GESA), Gigabit Ethernet 4-port ServerNet Adapter (G4SA), or Token Ring ServerNet adapter (TRSA).
PAGE 87
SCF Commands for the SLSA Subsystem ALTER Command Examples The following example adds a LIF named L11123B to the system and associates it with PIF B under SAC 0 on G4SA G11123: ADD LIF $ZZLAN.L11123B, PIF G11123.0.B The following example changes the DATAFORWARDCOUNT value to five frames: ADD LIF $ZZLAN.L11123B, PIF G11123.0.
PAGE 88
SCF Commands for the SLSA Subsystem ALTER ATMSAP Command $ZZLAN.adapter-id.sac-id.pif-id.atmsap-id where: adapter-id is a 1 to 8-character alpha-numeric string, beginning with an alpha character, that identifies the parent SLSA ADAPTER. Wildcard characters are not allowed. sac-id is a number that identifies the parent SAC object. The only valid sac-id for the ATM3SA adapter is the number “0.” Wildcard characters are not allowed. pif-id is an alpha character that identifies the parent PIF object.
PAGE 89
SCF Commands for the SLSA Subsystem ALTER LIF Command Valid values: Value Description vpi Configures the virtual path identifier. Only vpi 0 is supported. vci Configures the virtual circuit identifier. The virtual circuit identifier is a number in the decimal range of 0 to 4096. Response Display The ALTER ATMSAP command returns only a success or failure indication. Successful completion is indicated when SCF displays the prompt for the next command.
PAGE 90
SCF Commands for the SLSA Subsystem ALTER LIF Command DATAFORWARDMODE {ADAPTIVE | MANUAL} Note. HP recommends setting DATAFORWARDMODE to ADAPTIVE for G4SA adapters. select ADAPTIVE to allow a G4SA adapter type to choose the best DATAFORWARDCOUNT (DFC) and DATAFORWARDTIME (DFT) values depending on data-traffic. The G4SA automatically updates the DFC and DFT values whenever the data-traffic profile changes. The DATAFORWARDMODE ADAPTIVE value is supported for G4SA adapter types only.
PAGE 91
SCF Commands for the SLSA Subsystem ALTER LIF Command Valid range: 1 to 200000 microseconds Default value: If DATAFORWARDMODE is MANUAL, DATAFORWARDTIME defaults to either 10 milliseconds or 10000 microseconds depending on the setting of DATAFORWARDUNIT. If DATAFORWARDMODE is ADAPTIVE, DATAFORWARDTIME defaults to 1 millisecond. Considerations       An ALTER LIF command is accepted only when the LIF object is in the STOPPED state. You must specify at least one option.
PAGE 92
ALTER PIF Command SCF Commands for the SLSA Subsystem ALTER PIF Command The ALTER PIF command alters Token Ring ServerNet adapters (TRSAs), Ethernet 4 ServerNet adapters (E4SAs), ATM ServerNet Adapters (ATM3SA), Fast Ethernet ServerNet adapters (FESAs), Gigabit Ethernet ServerNet adapters (GESAs), and Gigabit Ethernet 4-port ServerNet adapters (G4SAs), after they are added to the SLSA subsystem through the ADD ADAPTER command.
PAGE 93
SCF Commands for the SLSA Subsystem ALTER PIF Command sac-id is a number that identifies the parent SAC objects. Wildcard characters are allowed. pif-id is an alpha character that identifies the target PIF objects. Wildcard characters are allowed. ACTIVEMONITOR { ON | OFF } specifies whether the adapter participates in the token-ring monitor function. Set it to ON for the node to participate as a standby or active monitor on the token-ring. The default is OFF. ACTIVEMONITOR is supported for TRSAs only.
PAGE 94
SCF Commands for the SLSA Subsystem ALTER PIF Command 10 through 200 milliseconds. The default value is 10 milliseconds. This attribute is supported for ATM3SAs only. The value of df-count is in the range of 1 through 50. The default is 2. This attribute is supported for ATM3SAs only. DUPLEX { HALF | FULL } Select HALF to set the FESA, GESA, or G4SA communication line to half duplex. Select FULL to set the FESA, GESA, or G4SA communication line to full duplex.
PAGE 95
SCF Commands for the SLSA Subsystem ALTER PIF Command only for FESAs and GESAs. The value must be set by the user. There is no default value. MAXSESSIONS max-sessions max-sessions specifies the maximum sessions that the adapter can handle. The adapter pre-allocates resources to handle the sessions. The trade-off involved is between the number of sessions and the number of transmit-and-receive buffers for data. The range is 1 through 2000 sessions. The default is 2000.
PAGE 96
ALTER SAC Command SCF Commands for the SLSA Subsystem   If your token-ring LAN is using 3616 Token Ring adapters, check the ring speed before inserting TRSAs into your LAN. The TRSAs have a default ring speed of 16Mbps which could cause a conflict at ring-insertion time if there is a 3616 Token Ring adapter using a ring speed of 4Mbps.
PAGE 97
SCF Commands for the SLSA Subsystem ALTER SAC Command SAC sac-name is the name of the SAC to be altered. The SAC name has the form $ZZLAN.adapter-name.sac-unit#, for example, $ZZLAN.G1123.0. ACCESSLIST ( n0 , n1,..., n15) specifies the processors allowed to access the SAC. The first processor in the list is the preferred owner. You must specify at least two processors in the access list. The allowed number of processors in the access list is 2 to 16.
PAGE 98
SCF Commands for the SLSA Subsystem ALTER SAC Command Considerations          To remove a processor from the access list or to add one, you must stop the SAC before executing the ALTER SAC command. You cannot have duplicate processor numbers in the access list. The system returns a duplicate-number error message if you specify the same processor more than once. For a SAC on an MFIOB, you can specify only two processors in the access list.
PAGE 99
SCF Commands for the SLSA Subsystem DELETE Command DELETE Command DELETE is a sensitive command that removes objects from the subsystem. DELETE ADAPTER Command The DELETE ADAPTER command removes an ADAPTER and its subordinate objects from the subsystem. Command Syntax DELETE [ /OUT file-spec/ ] ADAPTER adapter-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name is the name of the adapter to be deleted.
PAGE 100
SCF Commands for the SLSA Subsystem DELETE LIF Command Command Syntax DELETE [ /OUT file-spec/ ] ATMSAP atmsap-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ATMSAP atmsap-name is the name of the target ATMSAP object. atmsap-name is in the form $ZZLAN.adapter-id.sac-id.pif-id.atmsap-id where: adapter-id is a 1 to 8-character alpha-numeric string, beginning with an alpha character, that identifies the parent SLSA ADAPTER.
PAGE 101
SCF Commands for the SLSA Subsystem INFO Command Command Syntax DELETE [ /OUT file-spec/ ] LIF lif-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LIF lif-name is the name of the LIF to be deleted. The LIF name has the form $ZZLAN.lif-name, for example, $ZZLAN.L11123B. Considerations   The LIF must be in the STOPPED state and have no registered clients before it can be deleted.
PAGE 102
INFO ADAPTER Command SCF Commands for the SLSA Subsystem ADAPTER adapter-name is the name of the adapter for which information is to be displayed. DETAIL causes the INFO command to display a list of detailed information about the adapter. Without this parameter, the command displays only type, group, module, and slot information.
PAGE 103
INFO ADAPTER Command SCF Commands for the SLSA Subsystem Board PartNum indicates the part number of the adapter. Board Revision indicates the revision level of the adapter. Board Serial Number indicates the unique serial number of the adapter. Board TNum indicates the HP product number of the adapter. Group indicates the group that the adapter resides in. Module indicates the module that the adapter resides in. Slot indicates the slot that the adapter resides in. Type indicates the type of the adapter.
PAGE 104
SCF Commands for the SLSA Subsystem INFO ATMSAP Command INFO ATMSAP Command The INFO ATMSAP command returns the configuration information for an ATMSAP object subordinate to a PIF object. Command Syntax INFO [ /OUT file-spec/ ] ATMSAP atmsap-name [, {DETAIL | OBEYFORM} ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ATMSAP atmsap-name is the name of the target ATMSAP object. atmsap-name is in the form $ZZLAN.adapter-id.sac-id.pif-id.
PAGE 105
INFO ATMSAP Command SCF Commands for the SLSA Subsystem Response Display The INFO ATMSAP command returns the configuration information for the target objects. There are three possible display formats for the ATMSAP information: summary, detailed, and obeyform. These formats are shown below. If no object can be found, the failure is indicated when SCF displays an error message. Following is the display format for the ATMSAP INFO command with the DETAIL option not selected. 1-> info ATMSAP $zzlan.atm1.0.a.
PAGE 106
SCF Commands for the SLSA Subsystem INFO LIF Command Example INFO ATMSAP $ZZLAN.ATM01.0.A.ATMSAP01 INFO ATMSAP $ZZLAN.ATM01.0.A.ATMSAP01, DETAIL INFO ATMSAP $ZZLAN.ATM01.0.A.ATMSAP01, OBEYFORM INFO LIF Command The INFO LIF command displays the current attribute setting for the specified LIF. Command Syntax INFO [ /OUT file-spec/ ] LIF lif-name [ , DETAIL | OBEYFORM] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 107
INFO LIF Command SCF Commands for the SLSA Subsystem INFO LIF Displays The display for the INFO LIF command without the DETAIL option is: 1-> INFO LIF $ZZLAN.* SLSA Info LIF Name $ZZLAN.CC10A $ZZLAN.LANY $ZZLAN.LANX $ZZLAN.L018 $ZZLAN.L019 $ZZLAN.L01A $ZZLAN.L01B $ZZLAN.L11123A $ZZLAN.L01C $ZZLAN.L01A Associated Object CC1.0.A M0IE1.0.A M0IE1.0.A E0153.0.A E0153.0.B E0153.1.A E0153.1.B G11123.0.A T0154.0.A E0152.0.
PAGE 108
SCF Commands for the SLSA Subsystem INFO LIF Command DataForwardCount specifies the maximum number of inbound frames queued before delivery occurs. DataForwardTime specifies the maximum time an inbound frame waits before delivery. LIF Type indicates the type of network interface used. MAC Address indicates the MAC address of the given LIF (used by the associated PIF). PIF Name indicates the name of the PIF associated with the LIF.
PAGE 109
INFO MON Command SCF Commands for the SLSA Subsystem INFO MON Command The INFO MON command displays the attribute setting for the specified LAN Monitor (LANMON) process. Command Syntax INFO [ /OUT file-spec/ ] MON lanmon-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON lanmon-name is the name of the LANMON process for which information is to be displayed.
PAGE 110
SCF Commands for the SLSA Subsystem INFO PIF Command INFO PIF Command The INFO PIF command displays the physical interface (PIF) type and information about the attributes of the PIF. Command Syntax INFO [ /OUT file-spec/ ] PIF pif-name [ , DETAIL | OBEYFORM] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PIF pif-name is the name of the PIF for which information is to be displayed.
PAGE 111
INFO PIF Command SCF Commands for the SLSA Subsystem INFO PIF Display The attributes displayed for INFO PIF are the same as those that can be altered with the ALTER PIF command. See ALTER PIF for definitions of the attributes. The display for the INFO PIF command with neither the DETAIL nor OBEYFORM option selected is: 1>INFO PIF $ZZLAN.* SLSA Info PIF \ROO.$ZZLAN Name $ZZLAN.E0153.0.A $ZZLAN.E0153.0.B $ZZLAN.E0153.1.A $ZZLAN.E0153.1.B $ZZLAN.G11123.0.A $ZZLAN.G11123.0.B $ZZLAN.G11123.0.C $ZZLAN.G11123.0.
PAGE 112
SCF Commands for the SLSA Subsystem INFO PIF Command The display for the INFO PIF command with the OBEYFORM option for ATM3SAs is: -> INFO PIF $ZZLAN.ATM1.0.A.OBEYFORM ALTER PIF $ZZLAN.A0253.0.A & ,DATAFORWARDCOUNT 2 & ,DATAFORWARDTIME 1 & ,EMSVERBOSE OFF INFO PIF DETAIL Display for an E4SA The display for the INFO PIF command with the DETAIL option is: 1>INFO PIF $ZZLAN.E0153.0.A , DETAIL SLSA Detailed Info PIF \SYS.$ZZLAN.E0153.0.A Hardware MAC Address.... Interface Speed......... Max Frame Size.......
PAGE 113
SCF Commands for the SLSA Subsystem INFO PIF Command INFO PIF DETAIL Display for a FESA The display for the INFO PIF command with the DETAIL option for FESAs is: 1>SCF INFO PIF $ZZLAN.F0253.0.a.detail SLSA Detailed Info PIF \SYS.$ZZLAN.F0253.0.A Hardware MAC Address.... Interface Speed......... Max Frame Size.......... Min Frame Size.......... PIF Type................ 08:00:8E:00:90:13 100Mbit/sec 1516 60 Ethernet FESA Specific Info *AUTONEGOTIATION......... OFF *DUPLEX..................
PAGE 114
SCF Commands for the SLSA Subsystem INFO PIF Command The INFO PIF display with AUTONEGOTIATION OFF for a FESA is: 1>SCF INFO PIF \SYS.$ZZLAN.F0154.0.1, DETAIL SLSA Detailed Info PIF \SYS.$ZZLAN.F0154.0.1 Hardware MAC Address.... 08:00:8E:00:DD:FB *Autonegotiation..........OFF *Duplex...................FULL *Linespeed................100 Mbit/sec Max Frame Size.......... 1516 Min Frame Size.......... 60 *NodeMACAddress.......... 08:00:8E:00:DD:FB PIF Type................
PAGE 115
SCF Commands for the SLSA Subsystem INFO PIF Command The INFO PIF display with AUTONEGOTIATION ON for a FESA is: 1>SCF INFO PIF \SYS.$ZZLAN.F0154.0.A, DETAIL SLSA Detailed Info PIF \SYS.$ZZLAN.F0154.0.A Hardware MAC Address.... 08:00:8E:00:DD:FB *Autonegotiation..........ON *Duplex................... *Linespeed................ Max Frame Size.......... 1516 Min Frame Size.......... 60 *NodeMACAddress.......... 08:00:8E:00:DD:FB PIF Type................
PAGE 116
SCF Commands for the SLSA Subsystem INFO PIF Command INFO PIF DETAIL Display for a GESA The display format for INFO PIF with DETAIL selected for GESAs is: 1>INFO PIF $ZZLAN.G0253.0.A , DETAIL SLSA Detailed Info PIF \SYS.$ZZLAN.G0253.0.A Hardware MAC Address.... Interface Speed......... Max Frame Size.......... Min Frame Size.......... *NodeMACAddress.......... PIF Type................ 08:00:8E:00:78:B0 1000 Mbit/sec 9014 60 08:00:8E:00:78:B0 Ethernet GESA Specific Info *AutoNegotiation..........
PAGE 117
SCF Commands for the SLSA Subsystem INFO PIF Command Duplex indicates full-duplex or half-duplex operations. The value is not shown, because Autonegotiation is ON. Linespeed indicates the line speed. Value not shown, because Autonegotiation is ON. JumboFrame indicates the choice of normal or jumbo frames (activated by the Maximum Transmission Unit (MTU) setting in your Parallel Library TCP/IP or NonStop TCP/IPv6 configuration). Note.
PAGE 118
SCF Commands for the SLSA Subsystem INFO PIF Command Min Frame Size indicates the minimum frame size that the adapter can handle. NodeMACAddress indicates the primary MAC address used by this node for all transmitted and received frames. If the node MAC address is not supplied, the default MAC address from the SEEROM on the adapter is used (that is, the hardware MAC address). The high-order bit must be 0 and the next highest bit must be 1 for a locally administered address.
PAGE 119
SCF Commands for the SLSA Subsystem INFO PIF Command INFO PIF DETAIL Display for a TRSA The display for the INFO PIF command with the DETAIL option for TRSAs is: 1>SCF INFO PIF \SYS.$ZZLAN.T0154.0.A, DETAIL SLSA Detailed Info PIF \SYS.$ZZLAN.T0154.0.A Hardware MAC Address.... Interface Speed......... Max Frame Size.......... Min Frame Size.......... *NodeMACAddress.......... PIF Type................ 08:00:8E:00:DD:FB N/A 17832 32 08:00:8E:00:DD:FB Token Ring TRSA Specific Info *ActiveMonitor.........
PAGE 120
SCF Commands for the SLSA Subsystem INFO SAC Command EarlyTokenRelease specifies whether the adapter operates in Early Token Release mode (16 Mbps operation only). MaxSessions is the maximum number of sessions that can be added to the adapter by all I/O process methods. Currently, sessions can only be added by the SNATR MSAP. Use this attribute to tune the adapter to match the most-common maximum number of sessions being handled.
PAGE 121
SCF Commands for the SLSA Subsystem INFO SAC Command Considerations    The ServerNet identification (SvNet ID) is reset to 0x00000000 when CRU information is not available or when the physical CRU is missing. The firmware file version, firmware revision, and download version cannot be displayed for the Ethernet port on the multifunction I/O board (MFIOB). SvNet ID field is reset to 0x00000000 when CRU information is not available or physical CRU is missing.
PAGE 122
SCF Commands for the SLSA Subsystem INFO SAC Command AutoFirmup indicates whether the firmware revision file and the firmware currently in the SAC are compared during the startup sequence. The firmware revision file and the current firmware are always compared but not automatically updated. ON indicates that the firmware file is downloaded to the adapter if the firmware file is a newer revision than that currently running in the adapter. The default is ON.
PAGE 123
SCF Commands for the SLSA Subsystem LISTOPENS Command actual adapter type that’s in the slot. A value of No Adapter means that there is no adapter in the slot. Owner CPU indicates the processor that currently has ownership of the SAC. SvNet ID indicates the ServerNet ID of the SAC. Download Version indicates the version of the application microcode information. Firmware Revision indicates the version of the firmware code currently running on the SAC.
PAGE 124
NAMES Command SCF Commands for the SLSA Subsystem LISTOPENS LIF Display The display for the LISTOPENS LIF command is: SLSA Listopens LIF \SYS.$ZZLAN.LANX Openers $ZTCP0 $ZTCP0 $ZTCP0 PPID ( 0,280) ( 0,280) ( 0,280) BPID ( 1,301) ( 1,301) ( 1,301) Format Ethernet Ethernet Ethernet Filter $ZTCP0.#SN1.BR0 $ZTCP0.#SN1.IP0 $ZTCP0.#SN1.AR0 Total Number of Openers: 3 Openers is the process name of the opener of the LIF. PPID is the primary processor and process ID of the opener.
PAGE 125
NAMES null Command SCF Commands for the SLSA Subsystem object-name is the name of the LAN Manager (LANMAN) process, $ZZLAN. Omitting the object-name invokes the null object. NAMES null Display (Issued to the SLSA Manager Process) The display for the NAMES null command when issued to the SLSA manager process is: SLSA Names PROCESS \SYS. PROCESS $ZZLAN LIF $ZZLAN.LANX $ZZLAN.L01B $ZZLAN.L01C $ZZLAN.LANY $ZZLAN.L018 $ZZLAN.L019 $ZZLAN.L01D $ZZLAN.L01E $ZZLAN.L01F $ZZLAN.L01A ADAPTER $ZZLAN.
PAGE 126
NAMES null Command SCF Commands for the SLSA Subsystem (Names null display continued) SLSA Names PROCESS \SYS. PROCESS $ZZLAN LIF $ZZLAN.LANX $ZZLAN.L01B $ZZLAN.L01C $ZZLAN.LANY $ZZLAN.L018 $ZZLAN.L019 $ZZLAN.L01D $ZZLAN.L01E $ZZLAN.L01F $ZZLAN.L01A ADAPTER $ZZLAN.M0IE0 SAC $ZZLAN.M0IE0.0 PIF $ZZLAN.M0IE0.0.A ADAPTER $ZZLAN.M0IE1 SAC $ZZLAN.M0IE1.0 PIF $ZZLAN.M0IE1.0.A ADAPTER $ZZLAN.E0153 SAC $ZZLAN.E0153.0 PIF $ZZLAN.E0153.0.A $ZZLAN.E0153.0.B SAC $ZZLAN.E0153.1 PIF $ZZLAN.E0153.1.
PAGE 127
SCF Commands for the SLSA Subsystem NAMES ADAPTER Command NAMES ADAPTER Command The NAMES ADAPTER command displays the names of the SACs and PIFs subordinate to the specified adapter. Command Syntax NAMES [ /OUT file-spec / ] ADAPTER adapter-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name specifies the adapter for which a list of subordinate SAC and PIF objects is to be displayed. The adapter name has the form $ZZLAN.
PAGE 128
SCF Commands for the SLSA Subsystem NAMES ATMSAP Command Command Syntax NAMES [ /OUT file-spec/ ] ATMSAP atmsap-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ATMSAP atmsap-name is the name of the target ATMSAP object. atmsap-name is in the form $ZZLAN.adapter-id.sac-id.pif-id.atmsap-id where: adapter-id is a 1 to 8-character alpha-numeric string, beginning with an alpha character, that identifies the parent SLSA ADAPTER.
PAGE 129
SCF Commands for the SLSA Subsystem NAMES LIF Command Response Display (Issued to the SLSA Manager Process) 6-> names atmsap $ZZLAN.ATM2.0.A.ASAP101 SLSA Names ATMSAP \SYS.$ZZLAN.ATM2.0.A.ASAP101 ATMSAP $ZZLAN.ATM2.0.A.ASAP101 7-> names atmsap* SLSA Names ATMSAP \SYS.$ZZLAN.* ATMSAP $ZZLAN.ATM2.0.A.ASAP1 $ZZLAN.ATM2.0.A.ASAP10 $ZZLAN.ATM2.0.A.ASAP100 $ZZLAN.ATM2.0.A.ASAP101 $ZZLAN.ATM2.0.A.ASAP102 $ZZLAN.ATM2.0.A.ASAP103 Example NAMES ATMSAP $ZZLAN.ATM01.0.A.
PAGE 130
NAMES LIF Command SCF Commands for the SLSA Subsystem NAMES LIF Display (Issued to the SLSA Manager Process) -> SCF NAMES LIF $ZZLAN.* SLSA Names LIF \SYS.$ZZLAN LIF $ZZLAN.L11123A $ZZLAN.L11123B $L11123C $L11123D -> SCF NAMES LIF $ZZLAN.L11123A SLSA Names LIF \SYS.$ZZLAN.L11123A LIF $ZZLAN.
PAGE 131
SCF Commands for the SLSA Subsystem NAMES MON Command NAMES MON Command The NAMES MON command displays the names of LAN Monitor (LANMON) processes. Command Syntax NAMES [ /OUT file-spec / ] MON lanmon-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. MON lanmon-name specifies the monitor process for which a list of subordinate monitor objects is to be displayed. The monitor name has the form $ZZLAN.ZLMnn, for example, $ZZLAN.
PAGE 132
SCF Commands for the SLSA Subsystem NAMES PROCESS Command PIF pif-name specifies the PIF for which a list of subordinate objects is to be displayed. The PIF name has the form $ZZLAN.adapter-name.sac-unit#.pif-unit-letter, for example, $ZZLAN.G11123.0.A. SUB { ONLY | ALL | NONE } controls the set of objects and subordinate objects that the command targets: ONLY specifies that only the names of the subordinate object are returned.
PAGE 133
SCF Commands for the SLSA Subsystem NAMES PROCESS Command NAMES PROCESS Display (Issued to the SLSA Manager Process) -> NAMES PROCESS $ZZLAN SLSA Names PROCESS \SYS.$ZZLAN PROCESS $ZZLAN LIF $ZZLAN.LANX $ZZLAN.LANY $ZZLAN.E018 $ZZLAN.L019 $ZZLAN.L01A $ZZLAN.L01B $ZZLAN.L01C $ZZLAN.L01D $ZZLAN.L01E $ZZLAN.L01F ADAPTER $ZZLAN.MI0150 SAC $ZZLAN.M0IE0.0 PIF $ZZLAN.M0IE0.0.A ADAPTER $ZZLAN.M0IE1 SAC $ZZLAN.M0IE1.0 PIF $ZZLAN.M0IE1.0.A ADAPTER $ZZLAN.E0153 SAC $ZZLAN.E0153.
PAGE 134
NAMES PROCESS Command SCF Commands for the SLSA Subsystem (NAMES Process Display Continued.) PIF $ZZLAN.E0153.0.A $ZZLAN.E0153.0.B SAC $ZZLAN.E0153.1 PIF $ZZLAN.E0153.1.A $ZZLAN.E0153.1.B ADAPTER $ZZLAN.E0154 SAC $ZZLAN.E0154.0 PIF $ZZLAN.E0154.0.A $ZZLAN.E0154.0.A SAC $ZZLAN.E0154.1 PIF $ZZLAN.E0154.1.A MON $ZZLAN.#ZLM00 $ZZLAN.#ZLM04 $ZZLAN.#ZLM05 $ZZLAN.#ZLM09 $ZZLAN.#ZLM10 $ZZLAN.#ZLM14 $ZZLAN.#ZLM15 $ZZLAN.E0154.1.B $ZZLAN.#ZLM01 $ZZLAN.#ZLM02 $ZZLAN.#ZLM03 $ZZLAN.#ZLM06 $ZZLAN.
PAGE 135
SCF Commands for the SLSA Subsystem NAMES SAC Command NAMES SAC Command The NAMES SAC command displays the names of SACs in the SLSA subsystem. Command Syntax NAMES [ /OUT file-spec / ] SAC sac-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SAC sac-name specifies the SAC for which a list of subordinate objects is to be displayed. The SAC name has the form $ZZLAN.adapter-name.sac-unit#, for example, $ZZLAN.G11123.0.
PAGE 136
SCF Commands for the SLSA Subsystem RESET ADAPTER Command RESET ADAPTER Command The RESET ADAPTER command initiates a hardware reset of the adapter, putting it in a known state. The ADAPTER object must be in the STOPPED state before you issue this command. Command Syntax RESET [ /OUT file-spec / ] ADAPTER adapter-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name specifies which adapter to reset.
PAGE 137
SCF Commands for the SLSA Subsystem START ATMSAP Command Command Syntax START [ /OUT file-spec / ] ADAPTER adapter-name [ , SUB [ ONLY | ALL | NONE ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name specifies the adapter to start. SUB [ ONLY | ALL | NONE ] directs the command at a set of subordinate objects. ONLY specifies that only the subordinate objects are affected.
PAGE 138
SCF Commands for the SLSA Subsystem START ATMSAP Command OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ATMSAP atmsap-name is the name of the target ATMSAP object. atmsap-name is in the form $ZZLAN.adapter-id.sac-id.pif-id.atmsap-id where: adapter-id is a 1 to 8-character alpha-numeric string, beginning with an alpha character, that identifies the parent SLSA ADAPTER. Wildcard characters are allowed.
PAGE 139
SCF Commands for the SLSA Subsystem START LIF Command START LIF Command The START LIF command initiates the operation of the line interface (LIF) object. When the subsystem has completed processing this command, the LIF object is placed in the STARTED state. Command Syntax START [ /OUT file-spec / ] LIF lif-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file. LIF lif-name specifies the LIF to be placed in the STARTED state.
PAGE 140
SCF Commands for the SLSA Subsystem START PIF Command MON lanmon-name specifies the LANMON process to be started. LANMON names have the form $ZZLAN.#ZLM nn where nn indicates the particular processor in which the LANMON should start. Example The following example starts the LANMON named ZLM01 in processor 01: START MON $ZZLAN.ZLM01 START PIF Command The START PIF command initiates the operation of the physical interface (PIF) object.
PAGE 141
SCF Commands for the SLSA Subsystem START SAC Command NONE specifies that none of the subordinate objects are targets of the command. This is the default selected if the SUB keyword of the SUB keyword is not used. Considerations       The parent SAC object must be in the STARTED or STARTING state for the START PIF command to be accepted. The PIF object goes into the STARTED state only when the parent SAC object is in the STARTED state.
PAGE 142
SCF Commands for the SLSA Subsystem START SAC Command Command Syntax START [ /OUT file-spec/ ] SAC sac-name [ , SUB [ ONLY | ALL | NONE ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. SAC sac-name is the name of the SAC to be started. The SAC name has the form $ZZLAN.adapter-name.sac unit#, for example, $ZZLAN.G11123.0. SUB [ ONLY | ALL | NONE ] directs the command at a set of subordinate objects.
PAGE 143
SCF Commands for the SLSA Subsystem STATISTICS Command STATISTICS Command The STATISTICS command displays statistical information for the specified object. STATS ATMSAP Command The STATS ATMSAP command returns the usage information for an ATMSAP object subordinate to a PIF object. Command Syntax STATS [ /OUT file-spec/ ATMSAP atmsap-name [, RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 144
STATS PIF Command SCF Commands for the SLSA Subsystem Response Display The STATS ATMSAP command displays the usage statistics for ATMSAP objects. The display format is shown below. A failure is indicated when SCF displays an error message. 3-> stats ATMSAP $zzlan.atm1.0.a.atmsap01 STATS ATMSAP \SYS.$ZZLAN.ATM1.0.A.ATMSAP01 Sample Time Reset Time 26 August 1999, 17:18:04.643 26 August 1999, 17:07:03.
PAGE 145
SCF Commands for the SLSA Subsystem STATS PIF Command Command Syntax STATS [ /OUT file-spec / ] PIF pif-name [ , RESET ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PIF pif-name is the name of the PIF for which statistics are to be displayed. The PIF name has the form adapter-name.sac-unit#.pif-unit-letter, for example, G11123.0.A. RESET restores all the statistics counters to their initial values after the statistics are displayed.
PAGE 146
STATS PIF Command SCF Commands for the SLSA Subsystem STATS PIF Display Displays are slightly different for most adapters. STATS PIF Display for an ATM3SA Adapter -> stats pif $zzlan.a0154.0.A SLSA Stats PIF \SYS.$ZZLAN.A0154.0.A Sample Time......31 Jul 2001, 12:45:36.155 Reset Time.......30 Jul 2001, 14:26:05.772 DFC Events...............60587 DFTEvents................7614 Exec Rate (per sec)......52575 Exec Rate LWM............45462 Service Time (usec)......42 Service Time HWM.........
PAGE 147
SCF Commands for the SLSA Subsystem STATS PIF Command Service Time indicates the number of microseconds spent to complete processing of the last iteration of the main processing loop. This is an indication of loading similar to the exec rate. Service Time HWM indicates the longest time (in microseconds) spent in a single iteration of the main processing loop. TNet Halt 0 indicates the number of TNet Halt 0 exceptions. TNet Halt 1 indicates the number of TNet Halt 1 exceptions.
PAGE 148
SCF Commands for the SLSA Subsystem STATS PIF Command ATM3SA Line Stats Cells Received counts the number of cells received on the specified line. Cells Transmitted counts the number of cells transmitted on the specified line. Cells Dropped counts the number of cells dropped on the specified line. Frames Dropped counts the number of cells dropped on the specified line. Congestion counts the amount of congestion that has been experienced on the network.
PAGE 149
STATS PIF Command SCF Commands for the SLSA Subsystem T1 Error counts the number of times the packet did not arrive within the T1 time limit. Channel Deactivate counts the number of times the channel was deactivated by the REACTIVATED_CHANNEL command. Raw CRC Error counts the number of times an error occurred while NEC was receiving a non-AAL-5 packet. STATS PIF Display for an E4SA or FESA Adapter -> STATS PIF $ZZLAN.E0153.0.A SLSA Stats PIF \SYS.$ZZLAN.E0153.0.A Sample Time..... 30 March 2000, 10:41:56.
PAGE 150
SCF Commands for the SLSA Subsystem STATS PIF Command Octets Received OK indicates the number of bytes received from the LAN. General Send Stats Unicast Frames Transmitted indicates the number of unicast frames transmitted to the LAN. Non-Unicast Frames Transmit indicates the number of non-unicast frames transmitted to the LAN. Frames Discarded indicates the number of frames discarded due to resource problems or Ethernet errors. Errors indicates the number of frames discarded due to errors.
PAGE 151
SCF Commands for the SLSA Subsystem STATS PIF Command 802.3 Send Stats Transmit Underruns indicates the number of frames that had their transmission aborted because memory could not be accessed quickly enough to allow transmission. Defer Packets indicates the number of frames that could not be transmitted immediately because the LAN was in use. Send Late Collision indicates the number of frames that had their transmission aborted because a collision occurred before the completion of the retry process.
PAGE 152
STATS PIF Command SCF Commands for the SLSA Subsystem Receive Late Collision indicates the number of frames discarded because a collision occurred before the completion of the retry process. Alignment Errors indicates the number of frames discarded because the frame did not end on a byte boundary. Receive Long Frame indicates the number of frames discarded because the length of the frame was greater than the maximum frame size.
PAGE 153
SCF Commands for the SLSA Subsystem STATS PIF Command Octet Stats Octets Transmitted OK indicates the number of bytes successfully transmitted to the LAN. Octets Received OK indicates the number of bytes successfully received from the LAN. General Send Stats Unicast Frames Transmitted indicates the number of unicast frames transmitted to the LAN. Non-Unicast Frames Transmit indicates the number of non-unicast frames transmitted to the LAN.
PAGE 154
SCF Commands for the SLSA Subsystem STATS PIF Command Unknown Protocol Frames indicates the number of frames discarded because the filter could not identify a destination. 802.5 Stats Line Errors indicates that this adapter repeated or copied a frame or token and a violation of the hardware-clocking protocol was detected. A high count in this field might indicate a hardware problem with the upstream neighborhood of this adapter.
PAGE 155
SCF Commands for the SLSA Subsystem STATS PIF Command indicates line hits, an adapter with a duplicate address, or a malfunctioning adapter in the local ring. Token Errors is incremented only when this adapter is the active monitor and detects an error in the token protocol. High counts in this field might indicate a hardware problem in another adapter in the local ring. Soft Errors is incremented when this adapter transmits a soft-error MAC frame.
PAGE 156
STATS PIF Command SCF Commands for the SLSA Subsystem Singles is incremented each time this adapter recognizes that it is the only adapter on the ring. This field is provided for informational purposes only. Frequency Errors is incremented when this adapter detects that its incoming frames are being transmitted at the wrong frequency. A non-zero count might indicate a hardware problem in the adapter or its upstream neighbor. STATS PIF Display for a GESA SLSA Stats PIF \SYS.$ZZLAN.G0153.0.A Sample Time...
PAGE 157
STATS PIF Command SCF Commands for the SLSA Subsystem (STATS PIF display for a GESA continued) Packets Discards....................... Packets Errors......................... Total Collisions....................... Flow Control Done...................... 0 0 0 0 802.3 Receive Stats FCS Errors............................. Alignment Errors....................... Frames Too Long........................ XON Pause Frames Received.............. XOFF Pause Frames Received............. XOFF State Entered.......
PAGE 158
SCF Commands for the SLSA Subsystem STATS PIF Command TNET NACKS number of TNET NACKS seen by the SNET hardware. TNET Timeouts number of times TNET Time-out was seen by SNET Hardware. In Frames Discard Errors number of inbound frames discarded by software because of an internal resource problem. Out Frame Queue Length outbound frame queue length when stats are sampled. Out Frames Discard Errors number of outbound frames discarded by software because of an internal resource problem. 802.
PAGE 159
SCF Commands for the SLSA Subsystem STATS PIF Command Carrier Sense Errors the number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. Octets the number of octets transmitted out of the interface, including framing characters.
PAGE 160
SCF Commands for the SLSA Subsystem STATS PIF Command 802.3 Receive Stats FCS Errors a count of frames received on a particular interface that are an integer number of octets in length and do not pass the FCS check. Alignment Errors a count of frames received on a particular interface that are not an integer number of octets in length and do not pass the FCS check. Frames Too Long a count of frames received on a particular interface that exceed the maximum permitted frame size.
PAGE 161
SCF Commands for the SLSA Subsystem In Range Length Errors frames with length not equal to actual bytes received. Out Range Length Errors frames with type greater than 1522 and less than 1536. Packets Exceeded Jabbers Time frames exceeded jabber time. Undersize Packets frames with size less than 64 bytes. Fragments frame size less than 64 bytes with bad FCS Packets 64 Octets frame size equal to 64 bytes. Packets 65-127 Octets frame size between 65 and 127 bytes, inclusive.
PAGE 162
STATS PIF Command SCF Commands for the SLSA Subsystem STATS PIF Display for a G4SA -> STATS PIF $ZZLAN.G11123.0.A SLSA Stats PIF \SYS.$ZZLAN.G11123.0.A Sample Time..... 29 Sep 2003, 12:34:23.098 Reset Time...... 29 Sep 2003, 12:34:23.098 DFC Events............................. DFT Events............................. Exec Rate.............................. Exec Rate LWM.......................... Out Frame Queue Length................. In Frame Discard Errors................ In Filter Frame Discards........
PAGE 163
SCF Commands for the SLSA Subsystem STATS PIF Command Exec Rate LWM is the low water mark for exec rate. Out Frame Queue Length is the number of outbound frames queued when the stats were sampled. In Frame Discard Errors is the number of outbound frames discarded by the software because of internal resource problems. In Filter Frame Discards is the number of frames discarded by the G4SA adapter's filter logic.
PAGE 164
SCF Commands for the SLSA Subsystem STATS PIF Command Multi Collision Frames is a count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Deferred Transmissions is a count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. Excessive Collision is a count of frames for which transmission on a particular interface fails due to excessive collisions.
PAGE 165
SCF Commands for the SLSA Subsystem STATUS Command FCS Errors indicates a count of frames received on a particular interface that are an integral number of octets in length and do not pass the FCS check. Alignment Errors indicates a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. Control Pause Packets is the number of control pause packets received. Overrun Packets is the number of overrun packets received.
PAGE 166
SCF Commands for the SLSA Subsystem STATUS ADAPTER Command STATUS ADAPTER Command The STATUS ADAPTER command displays the current state of the specified adapter. The state of an ADAPTER object can be either STARTED or STOPPED. Command Syntax STATUS [ /OUT file-spec/ ] ADAPTER adapter-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. ADAPTER adapter-name is the name of the adapter for which the status is to be returned.
PAGE 167
SCF Commands for the SLSA Subsystem STATUS ATMSAP Command SP Cru Presence Status indicates service processor (SP) information about the presence of a physical adapter in the location associated with the specified adapter. SP Cru Test Status indicates SP information about the result of SP tests on the physical adapter in the location associated with the specified adapter. The values are Test OK and Config OK. State indicates the current state of the adapter.
PAGE 168
STATUS ATMSAP Command SCF Commands for the SLSA Subsystem atmsap-id is a 1 to 8-character alpha-numeric string that identifies the target ATMSAP object. Wildcard characters are allowed. DETAIL requests that detailed operational state information be displayed. The dynamically created ARP table entries subordinate to the ATMSAP object are displayed when this option is specified.
PAGE 169
SCF Commands for the SLSA Subsystem STATUS LIF Command VCC (VPI,VCI) identifies the ARP server virtual circuit connection with its virtual channel identifier (VCI) and virtual path identifier (VPI). VCC Nature identifies the connection as being from a PVC or an SVC. Remote ATM Address ATM address for the destination. Example STATUS ATMSAP $ZZLAN.ATM01.0.A.ATMSAP01 STATUS LIF Command The STATUS LIF command displays the current summary state and access state of the specified LIF.
PAGE 170
STATUS LIF Command SCF Commands for the SLSA Subsystem STATUS LIF Display The format of the display for the STATUS LIF command without the DETAIL option is: -> STATUS LIF $ZZLAN.L* SLSA Status LIF Name $ZZLAN.CC10A $ZZLAN.L11123A $ZZLAN.L11123B $ZZLAN.L11123C $ZZLAN.L11123D $ZZLAN.LANX $ZZLAN.LANY State STARTED STARTED STARTED STARTED STARTED STARTED STARTED Access State UP UP DOWN UP UP UP UP State indicates the current state of the LIF.
PAGE 171
SCF Commands for the SLSA Subsystem STATUS MON Command access-list attributes of the parent SAC of that PIF. The processors are listed in numerical order. State indicates the current state of the LIF. Trace Filename indicates the file name that stores the current trace information if TRACE is ON for this LIF. Trace Status indicates whether TRACE is active on the specified LIF. STATUS MON Command The STATUS MON command displays the current state of the LANMON processes.
PAGE 172
STATUS MON Command SCF Commands for the SLSA Subsystem STATUS MON Display The format of the display for the STATUS MON command without the DETAIL option is: -> STATUS MON $ZZLAN.#ZLM?? SLSA Status MON Name $ZZLAN.#ZLM03 $ZZLAN.#ZLM02 $ZZLAN.#ZLM01 $ZZLAN.#ZLM00 State STARTED STARTED STARTED STARTED PID ( 3,259) ( 2,259) ( 1,266) ( 0,273) Priority 180 180 180 180 Trace Status OFF OFF OFF OFF State indicates the current state of the LANMON process.
PAGE 173
SCF Commands for the SLSA Subsystem Considerations PID indicates the processor and process ID of the LANMON process. Is left blank if a LANMON has been aborted. Priority indicates the priority of the LANMON process. Is left blank if a LANMON has been aborted. QIO Pool Current indicates the current size of the QIO pool used by the LANMON process. QIO Pool Limit indicates the limit on the amount of QIO pool space that the LANMON process can allocate. 0 indicates no limit.
PAGE 174
STATUS PIF Command SCF Commands for the SLSA Subsystem Command Syntax STATUS [ /OUT file-spec/ ] PIF pif-name [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PIF pif-name specifies the PIF for which the status is to be displayed. The PIF name has the form $ZZLAN.adapter-name.sac-unit#.pif-unit-letter, for example, G1134.0.A. DETAIL specifies that additional status information is displayed.
PAGE 175
SCF Commands for the SLSA Subsystem STATUS PIF Command STATUS PIF DETAIL for an E4SA The format of the display for the STATUS PIF command with the DETAIL option for a PIF on an E4SA is: -> STATUS PIF $ZZLAN.E0153.0.A , DETAIL SLSA Detailed Status PIF \SYS.$ZZLAN.E0153.0.A CPUs with Data Path...... Last Error............... State.................... Trace Filename........... Trace Status............. ( 0 ) (0, 0, 0) STARTED OFF E4SA Controller Status Link Pulse State.........
PAGE 176
SCF Commands for the SLSA Subsystem STATUS PIF Command STATUS PIF DETAIL for a FESA The format of the display for the STATUS PIF command with the DETAIL option for the PIF on a FESA adapter is: -> STATUS PIF F0152.0.A , DETAIL CPUs with Data Path..... ( 0, 1 ) Last Error.............. (3, LANMON, 2038) State................... STARTED Trace Filename.......... Trace Status............. OFF FESA Controller Status Duplex...................... HALF Line Speed.................. 100 Mbit/sec Link Pulse State...
PAGE 177
SCF Commands for the SLSA Subsystem STATUS PIF Command Link Pulse State indicates the current state of the link pulse on the physical Ethernet link. This field is only applicable to the E4SA, FESA, GESA, and G4SA. The value of this field can be UP (normal condition) or DOWN. STATUS PIF DETAIL for a GESA The format of the display for the STATUS PIF command with the DETAIL option for the PIF on an GESA adapter is: -> STATUS PIF G0154.0.A , DETAIL CPUs with Data Path..... ( 0, 1, 2, 3 ) Interface Status . .
PAGE 178
STATUS PIF Command SCF Commands for the SLSA Subsystem Line Speed indicates the line speed. Values are 1000 Mbit/sec, 100 Mbit/sec, 10 Mbit/sec or Invalid. Invalid means that the adapter is not connected properly to the hub. For GESA, LINESPEED defaults to 1000 Mbit/s when the Interface Type is Fiber (SX) or Fiber (LX), even if you specified a LINESPEED of 10 or 100 Mbit/s. (Use the STATUS PIF command to check the actual LineSpeed of the communication line.
PAGE 179
SCF Commands for the SLSA Subsystem STATUS PIF Command Trace Filename indicates the name of the file that stores current trace information if TRACE is ON for the specified PIF. Trace Status indicates whether TRACE is active on the specified PIF. Duplex indicates whether the line is full-duplex, half-duplex, or invalid. Full-duplex means that data can be sent and received at the same time. Half-duplex means that data can be sent in only one direction at a time.
PAGE 180
STATUS PIF Command SCF Commands for the SLSA Subsystem STATUS PIF DETAIL for a TRSA -> STATUS PIF $ZZLAN.T0154.0.A , DETAIL SLSA Detailed Status PIF \SYS.$ZZLAN.T0154.0.A CPUs with Data Path...... Interface Status......... Last Error............... State.................... Trace Filename........... Trace Status............. ( 0 ) (0, 0, 0) STARTED OFF Interface Type ...........IP Duplex....................FULL Interface Speed...........100,000 Kbit/sec TRSA Controller Status Ring State...............
PAGE 181
STATUS PIF Command SCF Commands for the SLSA Subsystem Interface Type The interface type can be T1, J1, or IP. Duplex The duplex mode can be half or full duplex. Interface Speed The interface speed is in Kbit/sec. Ring State indicates the current state of the token ring. This field is only applicable to the TRSA (Token Ring ServerNet adapter).
PAGE 182
SCF Commands for the SLSA Subsystem STATUS PIF Command STATUS PIF DETAIL for an ATM3SA status pif $zzlan.a0253.0.a, detail SLSA Status DETAIL for PIF \SYS.$ZZLAN.A0253.0.A CPUs with Data Path............(0,1) Last Error.....................(0,0,0) State..........................STARTED Trace Filename................. Trace Status...................OFF ATM2 Controller Status Time Last STARTED..............30 Jul 2001, 14:26:05.791 Time Last STOPPED..............02 Jul 2001, 10:11:56.
PAGE 183
STATUS PROCESS Command SCF Commands for the SLSA Subsystem STATUS PROCESS Command The STATUS PROCESS command displays the current state of the LANMAN process. The state of LANMAN can only be STARTED. This is a nonsensitive command. Command Syntax STATUS [ /OUT file-spec/] PROCESS $ZZLAN [ , DETAIL ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file. PROCESS $ZZLAN specifies the LANMAN process for which the status is to be displayed.
PAGE 184
SCF Commands for the SLSA Subsystem STATUS PROCESS Command Trace Status indicates whether tracing has been enabled for the LANMAN process. The format of the display for the STATUS PROCESS command with the DETAIL option is: -> STATUS PROCESS $ZZLAN, DETAIL SLSA Detailed Status PROCESS \SYS.$ZZLAN Heap Memory Allocated.... Heap Memory Used......... PID Backup............... PID Primary.............. Priority................. QIO Pool Current......... QIO Pool Limit........... State....................
PAGE 185
SCF Commands for the SLSA Subsystem STATUS SAC Command Trace Filename indicates the name of the trace destination file if trace is ON. Trace Status indicates whether tracing is enabled for the LANMAN process. STATUS SAC Command The STATUS SAC command displays the current state of the specified SAC. The state of a SAC object can be STARTED, STARTING, or STOPPED.
PAGE 186
STATUS SAC Command SCF Commands for the SLSA Subsystem STATUS SAC Display The format of the display for the STATUS SAC command is: -> STATUS SAC $ZZLAN.E0153.0 SLSA Status SAC Name $ZZLAN.E0153.0 Owner 1 State STARTED Trace Status ON Name is the name of the SAC for which status information is being returned. Owner indicates the processor that currently has a data path to the specified SAC. State indicates the current state of the SAC specified in the preceding Name field.
PAGE 187
STATUS SAC Command SCF Commands for the SLSA Subsystem Last Download Time indicates the last time application microcode was downloaded into the adapter. Last Error indicates the last error encountered by the SAC in the form of (severity, origin, error code). (0, 0, 0) indicates no errors have occurred. The origins can be: MON QIO NSK Filter SvNet Int. NSK Config Service Processor DIH LMLIB XIO SvNet Proc. DSM LAN Manager Owner CPU is the processor that currently has ownership of the SAC.
PAGE 188
SCF Commands for the SLSA Subsystem STOP Command STOP Command STOP is a sensitive command that halts the operation of an object in an orderly manner. STOP ADAPTER Command The STOP ADAPTER command stops the operation of the specified ADAPTER object in an orderly manner and places it in the STOPPED state. Command Syntax STOP [ /OUT file-spec/ ] ADAPTER adapter-name [ , SUB [ ONLY | ALL | NONE ] ] OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
PAGE 189
SCF Commands for the SLSA Subsystem STOP ATMSAP Command Examples The following are examples of the STOP ADAPTER command: STOP ADAPTER $ZZLAN.G11123 STOP ADAPTER ($ZZLAN.G11021, $ZZLAN.G11123) STOP ADAPTER $ZZLAN.G* STOP ADAPTER $ZZLAN.G11123, SUB STOP ATMSAP Command The STOP ATMSAP command requests an ATMSAP object subordinate to a PIF object to halt operation. The ATMSAP object enters the STOPPED summary state if the command is successful.
PAGE 190
SCF Commands for the SLSA Subsystem STOP LIF Command atmsap-id is a 1 to 8-character alpha-numeric string that identifies the target ATMSAP object. Wildcard characters are allowed. Response Display The STOP ATMSAP command returns only a success or failure indication. Successful completion is indicated when SCF displays the prompt for the next command. A failure is indicated when SCF displays an error message. Example STOP ATMSAP $ZZLAN.ATM01.0.A.
PAGE 191
SCF Commands for the SLSA Subsystem  STOP PIF Command If the LIF and its associated PIF or ATMSAP are both in the STARTED summary state, then STOP LIF will be rejected. An ABORT command must be issued to the PIF or ATMSAP before a STOP LIF command can succeed. Examples The following are examples of the STOP LIF command: STOP LIF $ZZLAN.L11123A STOP LIF ($ZZLAN.L11123A, $ZZLAN.L11131B) STOP LIF $ZZLAN.
PAGE 192
SCF Commands for the SLSA Subsystem STOP PIF Command Considerations      An active client (registered user) dependent on the PIF (through a LIF associated with the specified PIF) can prevent the STOP PIF command from working. Use the ABORT PIF command if you cannot remove the client dependent on the specified PIF object. For E4SAs, FESAs, GESAs, G4SAs, ATM3SAs, and TRSAs, active clients are assumed to exist if the PIF and LIF objects are in the STARTED state.
PAGE 193
SCF Commands for the SLSA Subsystem STOP SAC Command STOP SAC Command The STOP SAC command stops the operation of the specified SAC and places it in the STOPPED state if there are no active data paths to the specified SAC. Use the ABORT SAC command to force a stop if there are active data paths. Command Syntax STOP [ /OUT file-spec/ ] SAC sac-name [ , SUB [ ONLY | ALL | NONE ] ] OUT causes any SCF output generated for this command to be directed to the specified file.
PAGE 194
SCF Commands for the SLSA Subsystem SWITCH Command Examples The following is an example of the STOP SAC command: STOP SAC $ZZLAN.G11123.0 SWITCH Command SWITCH is a sensitive command that switches the operation of a LAN Manager (LANMAN) process from one LANMAN to another. SWITCH PROCESS Command The SWITCH PROCESS command switches the operation of the specified LAN Manager (LANMAN) and places the LANMAN in the STOPPED state.
PAGE 195
TRACE Command SCF Commands for the SLSA Subsystem TRACE Command TRACE is a sensitive command that initiates trace-data collection on the specified object. You can use traces as a diagnostic tool. An SCF trace produces a trace file that can be displayed by using the commands available in the PTrace program. The Subsystem Control Point (SCP) creates the trace file. Refer to the PTrace Reference Manual for detailed information about PTrace.
PAGE 196
SCF Commands for the SLSA Subsystem TRACE MON Command Bulk I/O tracing is faster and should eliminate most data loss. The default is BULKIO. BULKIO cannot be used with NOCOLL. COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If count is omitted or if count equals -1, records are accumulated until the trace is stopped. LOCKSIZE locksize designates how much memory space, in units of pages, is locked down at one time.
PAGE 197
TRACE MON Command SCF Commands for the SLSA Subsystem SELECT select-spec select-spec is one of the following specifications: { { { { keyword } ( keyword [ , keyword ]) } number } ( number [ , number ]) } keyword is subsystem-specific. See Table 4-4 for the list of keywords that can be used for the MONITOR objects. number is the numeric value that a keyword represents. See Table 4-4 for the list of numbers that can be used for the MONITOR objects.
PAGE 198
TRACE PIF Command SCF Commands for the SLSA Subsystem Considerations    If TO file-spec is specified, a new trace is initiated unless the file-spec is invalid, the file cannot be opened, or trace is already active for the monitor process. If TO file-spec and STOP are both omitted, the TRACE command modifies the trace currently in progress, if any. If TO file-spec is omitted and STOP is specified, the TRACE command stops the trace currently in progress, if any.
PAGE 199
SCF Commands for the SLSA Subsystem TRACE PIF Command PIF pif-name is the name of the PIF. STOP discontinues the trace currently in progress. BULKIO | NOBULKIO designates whether TRACE should use bulk I/O for tracing. BULKIO specifies that the TRACE collector use bulk I/O to write data to the disk file, reducing the number of missing frame errors reported by PTrace. A limitation of BULKIO is that only one user can access the file at a time.
PAGE 200
SCF Commands for the SLSA Subsystem TRACE PIF Command segment are written to the disk file and the trace is stopped automatically. You do not need to issue a separate TRACE command to stop the trace. If NOCOLL is not specified, a trace collector process reads the trace records from the extended data segment and writes them to the disk file as they become available. The NOCOLL option cannot be used with the BULKIO option.
PAGE 201
TRACE PIF Command SCF Commands for the SLSA Subsystem Table 4-5.
PAGE 202
TRACE PIF Command SCF Commands for the SLSA Subsystem Example This example traces DIH state-machine operations and messages between a LANMON and DIH for the PIF named G11123.0.B. The maximum length of the traceddata record is 2048 bytes. The information is saved in the file named TRFIL1. TRACE PIF $ZZLAN.$ZZLAN.G11123.0.B, RECSIZE 2048, & SELECT (SMACH, LMOMSG), TO $M2.SUBV.TRFIL1 TRACE PROCESS Command The TRACE PROCESS command initiates a trace on the specified LANMAN process.
PAGE 203
SCF Commands for the SLSA Subsystem TRACE PIF Command COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If COUNT is omitted or if count equals -1, records are accumulated until the trace is stopped. LOCKSIZE locksize designates how much memory space, in units of pages, is locked down at one time. LOCKSIZE can be specified only when a trace is initiated. locksize is an integer in the range 4 through 1024.
PAGE 204
SCF Commands for the SLSA Subsystem TRACE PIF Command SELECT select-spec select-spec is one of the following specifications: { { { { keyword } ( keyword [ , keyword ] ) } number } ( number [ , number ] ) } keyword is subsystem-specific. ALL is the only keyword that you can use with the TRACE PROCESS command. number is the numeric value that a keyword represents. The numeric value of ALL is -1. TO file-spec specifies the file to which trace information is to be written.
PAGE 205
TRACE SAC Command SCF Commands for the SLSA Subsystem TRACE SAC Command The TRACE SAC command traces the SAC object in a processor. The TRACE operation can significantly increase the LAN DIH use of the processor; therefore, use the TRACE SAC command with caution. This is a sensitive command.
PAGE 206
SCF Commands for the SLSA Subsystem TRACE SAC Command CPU cpu-number specifies the CPU number from which the trace records are to be captured. cpu-number is an integer in the range 0 through 15. You can only specify the CPU that is on the parent SAC's ACCESSLIST, and the associated CPU must be loaded. If the CPU attribute is not specified, the owner CPU of the SAC is traced.
PAGE 207
TRACE SAC Command SCF Commands for the SLSA Subsystem SELECT select-spec select-spec is one of the following specifications: { { { { keyword } ( keyword [ , keyword ] ) } number } ( number [ , number ]) } keyword is subsystem-specific. ALL is the only keyword that you can use with the TRACE PROCESS command. number is the numeric value that a keyword represents. The numeric value of ALL is -1. TO file-spec specifies the file to which trace information is to be written.
PAGE 208
TRACE SAC Command SCF Commands for the SLSA Subsystem Table 4-6. select-spec for a SAC object (page 2 of 2) Keyword Number Meaning RXDATA 17 Trace SAC object inbound data LMOMSG 18 Trace messages between LANMON and DIH for SAC objects ERROR 19 Trace DIH errors for SAC object Considerations  You can initiate or terminate a SAC while it is in any state. The trace on a SAC is terminated automatically when:        It is deleted along with its parent adapter.
PAGE 209
VERSION Command SCF Commands for the SLSA Subsystem VERSION Command The VERSION command is a nonsensitive command that displays version information about the SLSA subsystem and the level of support for security and tracing. VERSION MON Command The VERSION MON command displays the version information of the LANMON monitor processes. Use the DETAIL option to display version information about the SCF Kernel and the SCF SLSA product module. This is a nonsensitive command.
PAGE 210
SCF Commands for the SLSA Subsystem VERSION null Command The format of the display for the VERSION MON command with the DETAIL option is: -> VERSION MON $ZZLAN.#ZLM01 , DETAIL Detailed VERSION MON \SYS.$ZZLAN.#ZLM01 SYSTEM \SYS LANMonitor - T8174G02_01MAY97_28FEB97_MON_V2 GUARDIAN - T9050 - (P40) SCF KERNEL - T9082F40 - (29FEB96) (01JAN96) SLSA PM - T7894G02 - (01MAY97) (01MAR97) - (SLSA) (V1) VERSION null Command The VERSION null command displays the version information of the LANMON process.
PAGE 211
SCF Commands for the SLSA Subsystem VERSION PROCESS Command The format of the display for the VERSION null command with the DETAIL option is: -> VERSION $ZZLAN , DETAIL Detailed VERSION SYSTEM \SYS LANManager - T8173G06_19JUL99_02JUL99AAJ GUARDIAN - T9050 - (Q06) SCF KERNEL - T9082G02 - (24SEP99) (26JUL99) SLSA PM - T7894G06 - (19JUL99) (11JUN99) - (SCF) (V1) VERSION PROCESS Command The VERSION PROCESS command displays the version information for the LANMAN process.
PAGE 212
SCF Commands for the SLSA Subsystem VERSION PROCESS Command The format of the display for the VERSION PROCESS command with the DETAIL option is: -> VERSION PROCESS $ZZLAN , DETAIL Detailed VERSION PROCESS \SYS.
PAGE 213
5 Managing the SLSA Subsystem This section describes management and failure recovery for the SLSA subsystem. The following management tasks are described in this section: Adding an Adapter to the System 5-1 Stopping and Starting an Adapter 5-4 Renaming an Adapter 5-7 Altering the Access List 5-8 Altering the LANMAN Process 5-9 Aborting the LANMAN Process 5-9 Replacing a LANMON Without a Cold Load 5-10 Adding an Adapter to the System Note.
PAGE 214
Adding an Adapter to the System Managing the SLSA Subsystem 3. Install the adapter in the system (see Adapter Manuals on page 1-7). 4. Use the SCF ADD ADAPTER command to add the adapter to the SLSA subsystem. For example: ADD ADAPTER $ZZLAN.G11021, TYPE G4SA, LOCATION (110,2,1), & ACCESSLIST (0, 1, 2, 3) In this example, SCF add a G4SA to slot 1 of IOAM group 110, module 2, and gives processor 0 primary access to the ServerNet addressable controllers (SACs).
PAGE 215
Adding an Adapter to the System Managing the SLSA Subsystem 7. Assign logical interfaces (LIFs) to the PIFs on the adapter you added in step 3 by using the SCF ADD LIF command. Use the names of the PIFs returned from the system in step 5. ADD ADD ADD ADD LIF LIF LIF LIF $ZZLAN.L11021A, $ZZLAN.L11021B, $ZZLAN.L11021C, $ZZLAN.L11021D, PIF PIF PIF PIF G11021.0.A G11021.0.B G11021.0.C G11021.0.D 8. Start the LIFs by using the START LIF command. START START START START LIF LIF LIF LIF $ZZLAN.
PAGE 216
Stopping and Starting an Adapter Managing the SLSA Subsystem Stopping and Starting an Adapter When performing maintenance of the SLSA subsystem, you may need to stop or start an adapter. This subsection describes the procedures to use. Stopping an Adapter Before you delete a ServerNet adapter, you must stop the adapter and its subordinate SAC(s) and PIFs on the adapter. Perform the following steps to stop an adapter: 1.
PAGE 217
Stopping and Starting an Adapter Managing the SLSA Subsystem 4. Use the SCF STOP LIF command to stop the LIFs identified in step 3. If you cannot stop a LIF because it has active clients, use the SCF ABORT LIF command. You can use the SCF STATUS LIF command to verify that the LIFs are STOPPED. STOP LIF $ZZLAN.L11021A STOP LIF $ZZLAN.L11021B STOP LIF $ZZLAN.L11021C STOP LIF $ZZLAN.L11021D STATUS LIF $ZZLAN.L11* SLSA Status LIF Name $ZZLAN.L11021A $ZZLAN.L11021B $ZZLAN.L11021C $ZZLAN.L11021D $ZZLAN.
PAGE 218
Stopping and Starting an Adapter Managing the SLSA Subsystem 7. Use the SCF STATUS PIF and SCF STATUS SAC commands to check the status of the PIFs and SACs. STATUS PIF $ZZLAN.G11021.* SLSA Status PIF Name $ZZLAN.G11021.0.A $ZZLAN.G11021.0.B $ZZLAN.G11021.0.C $ZZLAN.G11021.0.D State STOPPED STOPPED STOPPED STOPPED STATUS SAC $ZZLAN.G11021* SLSA Status SAC Name $ZZLAN.G11021.0 Owner 0 State STOPPED 8. Verify that the adapter is in the STOPPED state by using the SCF STATUS ADAPTER command.
PAGE 219
Renaming an Adapter Managing the SLSA Subsystem 3. Verify that the SACs and PIFs are in the STARTED state by using the SCF STATUS SAC and SCF STATUS PIF commands. STATUS SAC $ZZLAN.G11021* SLSA Status SAC Name $ZZLAN.G11021.0 Owner 0 State STARTED STATUS PIF $ZZLAN.G11021* SLSA Status PIF Name $ZZLAN.G11021.0.A $ZZLAN.G11021.0.B $ZZLAN.G11021.0.C $ZZLAN.G11021.0.D State STARTED STARTED STARTED STARTED 4. Start the LIFs associated with the PIFs on the adapter.
PAGE 220
Altering the Access List Managing the SLSA Subsystem 2. Stop the ADAPTER as described under Stopping and Starting an Adapter. STOP ADAPTER $ZZLAN.G11021, SUB ALL The system stops the adapter and its subordinate SACs and PIFs. 3. Delete the LIFs you just stopped or aborted. DELETE LIF ($ZZLAN.L11021A, $ZZLAN.L11021B, $ZZLAN.L11021C, $ZZLAN.L11021D) 4. Delete the name of the adapter with the SCF DELETE ADAPTER command. DELETE ADAPTER $ZZLAN.G11021 5.
PAGE 221
Altering the LANMAN Process Managing the SLSA Subsystem 2. Use the SCF INFO SAC command to check the current access list for the SAC you are planning to alter. INFO SAC $ZZLAN.G11021.0 SLSA Info SAC Name $ZZLAN.G11021.0 Owner 0 *Access List (0, 1, 2, 3) 3. Use the SCF ALTER SAC command to alter the access list. ALTER SAC $ZZLAN.G11021.0, ACCESSLIST (1, 0, 2, 3) The LANMAN process updates the access list for the specified SAC. 4.
PAGE 222
Managing the SLSA Subsystem Replacing a LANMON Without a Cold Load b. Use the SCF ALTER PROC command to set the stopmode attribute ALTER PROC $ZZKRN.#ZZLAN, stopmode sysmsg 2. Stop the persistence manager. ABORT PROC $ZPM 3. Restart the Kernel process. START PROC $ZZKRN.#ZZLAN 4. Use the SCF ABORT PROC command to abort the $ZZLAN process. ABORT PROC $ZZKRN.#ZZLAN Replacing a LANMON Without a Cold Load As of the G06.
PAGE 223
Replacing a LANMON Without a Cold Load Managing the SLSA Subsystem The following example stops and starts the LANMON in CPU 02 and verifies that the LANMON has started along with its associated SAC, PIF, and LIF objects: ABORT MON $ZZLAN.#ZLM02 Status MON #ZLM02 Name $ZZLAN.#ZLM02 State STOPPED PID Priority Trace Status OFF PID (3,302) Priority 200 Trace Status OFF START MON $ZZLAN.#ZLM02 STATUS MON #ZLM02 SLSA Status MON Name $ZZLAN.#ZLM02 State STARTED status sac G11021.0.
PAGE 224
Managing the SLSA Subsystem Replacing a LANMON Without a Cold Load 3. Determine if the primary LANMAN is in CPU 0 or CPU 01 by issuing the SCF STATUS PROCESS command: STATUS PROCESS $ZZKRN.#ZZLAN NONSTOP KERNEL - Status PROCESS \HELLO.$ZZKRN.#ZZLAN Symbolic Name Name State Sub Primary Backup Owner PID PID ID $ZZLAN $ZZLAN STARTED (0 ,15) (1 ,16) 255,255 NON STOP KERNEL SLSA Status PROCESS 4. Use the SCF ABORT MON command to ABORT the LANMON in the CPU associated with the backup LANMAN.
PAGE 225
Replacing a LANMON Without a Cold Load Managing the SLSA Subsystem 6. Verify that the LANMON in CPU 01 has started and that SAC, PIF, and LIF access is gained on that CPU: Status MON #ZLM01 Name $ZZLAN.#ZLM01 State STARTED PID (3,302) Priority 200 Trace Status OFF status sac G11021.0.A, detail SLSA Detailed Status SAC \SYS.$ZZLAN.G11021.0.A Current Access........... Last Download Time....... Last Error............... Owner CPU................ State.................... Trace Filename...........
PAGE 226
Replacing a LANMON Without a Cold Load Managing the SLSA Subsystem 8. Verify that the primary LANMAN has switched CPUs by issuing the SCF STATUS PROCESS command: STATUS PROCESS $ZZKRN.#ZZLAN NONSTOP KERNEL - Status PROCESS \HELLO.$ZZKRN.#ZZLAN Symbolic Name Name Sub Primary PID $ZZLAN STARTED 1 ,15 $ZZLAN State Backup PID 0 ,16 Owner ID 255,255 9. Use the SCF ABORT MON command to ABORT the LANMON in CPU 0 (if your backup LANMAN is in CPU 0).
PAGE 227
A Command Summary The appendix shows the syntax of the SCF commands for the ServerNet LAN Systems Access (SLSA) subsystem.
PAGE 228
Command Summary ADD [ /OUT file-spec/ ] ADAPTER adapter-name { { { [ [ [ [ [ [ , , , , , , , , , TYPE {E4SA|MIOE|TRSA|FESA|GESA|G4SA|ATM3SA|CCSA} LOCATION (group,module,slot) } ACCESSLIST ( n0 , n1,..., n15 ) } AUTODUMP { ON | OFF |EXTENDED}] AUTOFIRMUP { ON | OFF } ] AUTOSTART { ON | OFF } ] DLFILENAME file-spec ] DUMPFILENAME file-spec ] FIRMWAREFILENAME file-spec ] ADD [ /OUT file-spec/ ] LIF lif-name , PIF pif-name | ATMSAP atmsap.
PAGE 229
Command Summary ALTER [ /OUT file-spec/ ] PIF pif-name [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , [ , RESET ] ACTIVEMONITOR { ON | OFF } ] AUTONEGOTIATION { ON | OFF } ] INTERFACE { AUTODETECT | COPPER | FIBER } ] DATAFORWARDCOUNT df-count ] DATAFORWARDTIME df-time ] DUPLEX { HALF | FULL } ] EARLYTOKENRELEASE { ON | OFF } ] EMSVERBOSE { ON | OFF } ] JUMBOFRAME { ON | OFF } ] LINESPEED { 10 | 100 | 1000 } ] MAXSESSIONS max-sessions ] NODEMACADDRESS { addr | DEFAULT } ] NOOPTION ] RINGSPEED {
PAGE 230
Command Summary INFO [ /OUT file-spec/ ] LIF lif-name [ , DETAIL | OBEYFORM] INFO [ /OUT file-spec/ ] MON lanmon-name [ , DETAIL ] INFO [ /OUT file-spec/ ] PIF pif-name [ , DETAIL | OBEYFORM] INFO [ /OUT file-spec/ ] SAC sac-name [ , DETAIL | OBEYFORM] LISTOPENS LIF [/OUT file-spec / ] LIF [ lif-name ] NAMES [ /OUT file-spec / ][ object-name ] NAMES [ /out-file-spec / ] ATMSAP atmsap-name NAMES [ /OUT file-spec / ] ADAPTER adapter-name NAMES [ /OUT file-spec / ] LIF lif-name NAMES [ /OUT file-spec
PAGE 231
Command Summary NAMES [ /OUT file-spec / ] PROCESS $process-name NAMES [ /OUT file-spec / ] SAC sac-name RESET [ /OUT file-spec / ] ADAPTER adapter-name START [ /OUT file-spec/ ] ATMSAP atmsap-name START [ /OUT file-spec / ] ADAPTER adapter-name [ , SUB [ ONLY | ALL | NONE ] ] START [ /OUT file-spec / ] LIF lif-name START [ /OUT file-spec / ] MON lanmon-name START [/OUT file-spec/ ] PIF pif-name [ , SUB [ ONLY | ALL | NONE ] ] START [ /OUT file-spec/ ] SAC sac-name [ , SUB [ ONLY | ALL | NONE ] ]
PAGE 232
Command Summary STATS [ /OUT file-spec / ] PIF pif-name [ , RESET ] STATUS [ /OUT file-spec/ ] ATMSAP atmsap-name [ , DETAIL ] STATUS [ /OUT file-spec/ ] ADAPTER adapter-name [ , DETAIL ] STATUS [ /OUT file-spec/] LIF lif-name [ , DETAIL ] STATUS [ /OUT file-spec/ ] MON lanmon-name [ , DETAIL ] STATUS [ /OUT file-spec/ ] PIF pif-name [ , DETAIL ] STATUS [ /OUT file-spec/] PROCESS $ZZLAN [ , DETAIL ] STATUS [ /OUT file-spec/ ] SAC sac-name [ , DETAIL ] STOP [ /OUT file-spec/ ] ATMSAP atmsap-name ST
PAGE 233
Command Summary STOP [ /OUT file-spec/ ] PIF pif-name [ , SUB [ ONLY | ALL | NONE ] ] STOP [ /OUT file-spec/ ] SAC sac-name [ , SUB [ ONLY | ALL | NONE ] ] SWITCH [ /OUT file-spec/ ] PROCESS lanman-name TRACE [ /OUT file-spec/ ] MON lanmon-name { , [ [ [ [ [ [ [ [ [ STOP , BULKIO | NOBULKIO , COUNT count , LOCKSIZE locksize , NOCOLL , PAGES pages , RECSIZE size , SELECT select-spec , TO file-spec , WRAP } ] ] ] ] ] ] ] ] ]} TRACE [ /OUT file-spec/ ] PIF pif-name { { [ [ [ [ [ [ [ [ [ [ , , , , , , ,
PAGE 234
Command Summary TRACE [ /OUT file-spec/ ] PROCESS process-name { , STOP { , [ , BULKIO | NOBULKIO [ , COUNT count [ , LOCKSIZE locksize [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] ] ]} TRACE [ /OUT file-spec/ ] SAC sac-name { , STOP { [ , BULKIO | NOBULKIO [ , COUNT count [ , CPU cpu-number [ , LOCKSIZE locksize [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] ] ] ]} VERSION [/
PAGE 235
B SCF Error Messages This appendix lists the error messages that SCF can return for the SLSA subsystem and describes the cause, effect, and recovery for each error. SLSA 00001 SLSA E00001 Command not yet implemented. Cause. You entered a command that SCF does not recognize. Effect. SCF ignores the command. Recovery. Enter the appropriate command. SLSA 00002 SLSA E00002 SLSA SCF Product Module internal error - contact TNSC. Cause. SCF encountered an internal error. Effect. SCF ignores the command.
PAGE 236
SCF Error Messages SLSA 00005 SLSA E00005 Object object-name has been given an invalid access list. Cause. An invalid access list (such as, unacceptable processor, nonexistent processor, or incorrect number of processors) has been specified in the ALTER SAC command. Effect. SCF ignores the command, and the access list is not altered for the specified SAC. Recovery. Check the command, then reissue it. The access list must have from 2 to 16 valid processors specified for a SAC.
PAGE 237
SCF Error Messages level specifies whether this error is informative, warning, fatal, or unrecognized. object-name specifies the name of the object that generated the internal error. SLSA 00008 SLSA E00008 Configuration failure by origin due to cause (detail) on operation operation-type for object-name. Cause. The SCF command issued to the object specified by object-name requires LANMAN to manipulate the configuration database. The manipulation failed as specified by the cause and detail information.
PAGE 238
SCF Error Messages object-name specifies the name of the object that generated the error. SLSA 00009 SLSA E00009 Object object-name is busy with other operations. Cause. The object you issued the command to is busy performing actions and cannot process the SCF command. Effect. SCF ignores the command. Recovery. Wait, then try the command again. Contact your service provider if the problem persists for a long time. SLSA 00010 SLSA E00010 Cannot start object-name. Parent object is still in STOPPED state.
PAGE 239
SCF Error Messages SLSA 00012 SLSA E00012 Object object-name has registered client(s) and cannot stop. Cause. A LIF is preventing a LIF or a PIF from being stopped because the LIF and its associated PIF have active clients. object-name specifies the LIF or a PIF that has the registered clients. Effect. You cannot stop the object specified by object-name. Recovery. Identify the LIF involved (use the INFO LIF command), terminate all registered clients of the LIF, then reissue the STOP command.
PAGE 240
SCF Error Messages Effect. The LIF is not assigned to the specified PIF. Recovery. Assign a different PIF to the LIF you are attempting to add, or remove the current PIF from the LIF you specified in the ADD LIF command. Use the INFO LIF command to display the PIFs assigned to the LIFs in the SLSA subsystem. SLSA 00016 SLSA E00016 Subordinate PIF of object-name has link to existing LIF object. Cause.
PAGE 241
SCF Error Messages SLSA 00019 SLSA E00019 Firmware file for object-name does not contain an applicable download module. Cause. A LOAD command was issued for a SAC object, specified by object-name, whose previously specified firmware file does not contain a downloadable module that is appropriate for that particular SAC object. Effect. The firmware file is not downloaded to the SAC. Recovery.
PAGE 242
SCF Error Messages SLSA 00022 SLSA E00022 filename is an invalid filename Cause. The file name specified in an ADD ADAPTER or ALTER SAC command is not valid or does not contain enough information to construct a fully qualified file name. Effect. SCF ignores the command. Recovery. Check the file name, then reissue the command. SLSA 00023 SLSA E00023 filename is an invalid dump filename Cause. The dump file name in an ADD ADAPTER or ALTER SAC command is not valid because it does not end with 00. Effect.
PAGE 243
SCF Error Messages SLSA 00026 SLSA E00026 Adapter corresponding to object-name is configured but not detected at present Cause. The SLSA subsystem does not detect the adapter specified by object-name because the adapter is not plugged in, or it is the process of being reset. Effect. SCF ignores the command. Recovery. Retry the SCF command. If this message persists, make sure that adapter is correctly plugged in, then retry the command.
PAGE 244
SCF Error Messages SLSA 00030 SLSA E00030 Given MAC address is not valid as locally-administered MAC address Cause. You specified a MAC address that is not between %H400000000000 and %H7FFFFFFFFFFF. MAC addresses in this range are available as a locally-administered MAC address. Effect. The MAC address is not changed, and the command does not complete. Recovery. Reissue the command using a valid, locally-administered MAC address.
PAGE 245
SCF Error Messages Effect. SCF ignores the command. Recovery. Remove the DATAFORWARDCOUNT and DATAFORWARDTIME attributes from the ADD or ALTER command line. These two attributes are not required for a LIF that is associated with an ATMSAP object. SLSA 00051 SLSA E00051 Superior object not started for Cause. You issued a STATUS command, however the status information is not available for display. The object or its parent object is not in a started state. Effect. SCF ignores the command.
PAGE 246
SCF Error Messages Recovery. Specify the LINESPEED and DUPLEX attribute settings in the ALTER PIF Command. SLSA 00061 SLSA E00061 LINESPEED and DUPLEX not required when AUTONEGOTIATE is set to ON Cause. You issued an ALTER PIF command on a FESA or GESA adapter. You specified the AUTONEGOTIATE attribute to ON; however, you also specified the LINESPEED and DUPLEX attributes in the command line. Effect. SCF ignores the command. Recovery.
PAGE 247
SCF Error Messages SLSA 00064 SLSA E00064 Invalid TRACE command attribute combination Cause. The attribute in question conflicted with one or more of the other attributes on the command line. Effect. SCF ignores the command. Recovery. Refer to the TRACE Command on page 4-135 to determine the attributes that can be combined with a TRACE command string. SLSA 00065 SLSA E00065 LOCKSIZE must be less than or equal to PAGES Cause.
PAGE 248
SCF Error Messages Recovery. Issue the START MON command for the LANMAN’s backup CPU, then retry the SWITCH PROCESS command. SLSA 00068 SLSA E00068 The MON in the specified cpu to be traced is in the STOPPED state Cause. The user issued a TRACE command but there is no LANMON to handle that request in the specified CPU. Effect. SCF ignores the command. Recovery. Issue the START MON command, then retry the TRACE command. SLSA 00071 SLSA E00071 The objname does not support the FIBER INTERFACE type. Cause.
PAGE 249
SCF Error Messages SLSA 00073 SLSA E00073 SLSA E00073 DATAFORWARDTIME is beyond the valid range of 1-200000 MICROSECONDS Cause. The user attempted to specify a DATAFORWARDTIME value beyond the range of the current DATAFORWARDUNIT. Effect. SCF ignores the command. Recovery. Reissue the command with a DATAFORWARDTIME value that is between 1 and 200000 MICROSECONDS.
PAGE 250
SCF Error Messages LAN Configuration and Management Manual—520469-012 B-16
PAGE 251
Index A ABORT command ADAPTER 4-7 ATMSAP 4-9 LIF 4-10, 4-130, 5-7 MON 4-11 PIF 4-12, 4-132 SAC 4-133 Access list 4-16, 4-36, 4-37, 4-62, 4-111 altering 5-8 ADAPTER aborting 4-7 adding 4-15 deleting 4-39 INFO command 4-41 Naming 4-67 RESET command 4-76 starting 4-76 STATUS command 4-106 stopping 4-128 subordinate objects 4-18 Adapters configuring using WAN Wizard Pro 1-8, 5-1 display of names 4-74 installing 5-2 naming 5-1 naming convention for 3-2 ADD command ADAPTER 4-15, 5-2 ATMSAP 4-21 LIF 4-23 ALTER com
PAGE 252
D Index D I Data path 4-110, 4-115, 4-116, 4-117, 4-118, 4-120, 4-126, 4-133 DELETE command ADAPTER 4-39, 5-8 ATMSAP 4-39 LIF 4-40 Download file 4-17, 4-37 Download filename 4-18, 4-62 Dump file 4-17, 4-37, 4-62 Dump filename 4-18 E INFO command ADAPTER 4-41 ATMSAP 4-44 LIF 4-46 MON 4-49 PIF 4-50 SAC 4-60, 5-9 Installation 3-1 IOMF CRU naming convention for 3-2, 3-4 IPX/SPX See NonStop IPX/SPX End-of-file mark 4-137 Expand 2-15, 4-23 J F JUMBOFRAME 4-34 Fabric Status 4-127 Fault tolerance 2-16/2-
PAGE 253
M Index LANMON 4-74, 4-135 adapter ownership 3-1 See also MON LEC object 2-14 LENTRY object 2-14 LIF aborting 4-10 adding 4-23, 4-69 altering access list 4-29 assigning to PIFs 5-3 definition of 2-15 deleting 4-40 display of names 4-74 halting operation of 4-10 hierarchy 2-14 INFO command 4-46 initialization of 3-1 MAC address 4-48 name of 4-46, 4-49 naming convention for 3-4 naming convention for (H-Series) 3-6 PIF association 4-39, 4-79, 4-110, 4-120, 4-130 relationship to SLSA subsystem 2-10 SCF object
PAGE 254
O Index O PVC object 2-14 Object hierarchy 2-14 Objects 2-11/2-15 Q QIO subsystem 2-8 QOSSET object 2-14 P Parallel Library TCP/IP 2-5 PIF 2-14 aborting 4-12 altering 4-32 definition of 2-15 display of names 4-74 effect of ABORT LIF on 4-10 INFO command 4-50 initialization of 3-1 LIF association 4-79, 4-110, 4-120, 4-130 MAC address 4-52 names 3-9, 4-48, 4-50 assigning 5-2 SAC subordination 4-39 SCF object 2-11 starting 4-82 stats 4-85 stopping 4-131 TRACE command 4-138 PMF CRU configuration form 3-10
PAGE 255
T Index SAC (continued) TRACE command 4-145 SAC object 2-14 SAN 2-8 SCF generic processes 4-6 nonsensitive commands 4-3 object hierarchy 4-5 objects 2-11/2-15 operational states 4-6 persistence 2-11 sensitive commands 4-3 SCF objects 4-5 ServerNet addressable controllers See SAC ServerNet ID 4-61, 4-63 ServerNet WAN concentrator 2-9 Slot 3-3 SLSA subsystem components of 2-10, 4-5 START command ADAPTER 4-17, 4-76, 5-6 ATMSAP 4-77 LIF 4-79 affect on PIF 4-79 MON 4-79 PIF 4-13, 4-80 SAC 4-37, 5-2 Start-up se
PAGE 256
V Index Trace records 4-136, 4-139, 4-143, 4-146 V Versatile I/O (VIO) enclosure adapter type 4-16 ADD ADAPTER 4-15, 5-1 configuration file 3-12 overview 2-12 VERSION command MON 4-149 null 4-150 PROCESS 4-151 W WAN WAN Wizard Pro 1-8, 5-1 Wide area network (WAN) See WAN Special Characters * 4-41 LAN Configuration and Management Manual—520469-012 Index-6