SGI® L1 and L2 Controller Software User’s Guide 007-3938-003
CONTRIBUTORS Written by Linda Rae Sande Revised by Francisco Razo and Terry Schultz Illustrated by Dan Young Production by Karen Jacobson Engineering contributions by Don Adams, Michael T. Brown, Dick Brownell, Jason Chang, Steve Hein, Jill Heitpas, Nancy Heller, Matt Hoy, Hao Pham, Craig Schultz, and Lisa Steinmetz. COPYRIGHT © 2002, 2003, 2004 Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein.
New Features in This Guide This manual has been updated with information to support the SGI Altix 350 system. Major Documentation Changes The following sections were revised for this release: 007-3938-003 • Added information about SGI Altix 350 system hardware manuals to “Related Publications” on page xix. • Added information about viewing release notes on Linux systems to “Obtaining Publications” on page xx. • Added Altix 350 systems to the list of systems supported in Chapter 1.
Record of Revision Version Description 001 May 2002 Initial revision. 007-3938-003 002 February 2003 Updated to support the SGI Origin 3900 and SGI Altix 3000 series of servers. 003 May 2004 Updated to support the SGI Altix 350 systems.
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . xi Tables . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Examples . . . . Related Publications . Obtaining Publications Conventions . . . Reader Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3. viii Operating the L1 Controller . . . . . . . . . . L1 Mode . . . . . . . . . . . . . . Viewing System Configuration . . . . . . . Command Targeting . . . . . . . . . . Viewing Information, Warnings, and Error Messages Powering On, Powering Off, and Resetting the Brick Console Mode from L1 . . . . . . . . . . Console Selection . . . . . . . . . . . Upgrading L1 and L2 Firmware . . . . . . . . . Upgrading L1 Firmware . . . . . . . . . . Upgrading L2 Firmware . . . . . . . . . .
Contents fan . . . . . flash . . . . help . . . . . history . . . . iia, iib, iic, and iid . ioport . . . . istat . . . . . junkbus. . . . l1 . . . . . l1dbg . . . . leds . . . . . link . . . . . log . . . . . margin . . . . network . . . fuel . . . . . nia and nib . . . nmi . . . . . nvram reset . . partdb . . . . pbay . . . . pci . . . . . pimm . . . . port . . . . power . . . . reboot_l1 . . . reset . . . . router . . . . scan . . . . security verify . . select . . . . serial . . . . softreset . . .
Contents uart . . . . . usb . . . . . verbose . . . . version . . . . L2 Controller Commands autopower . . . config . . . . date . . . . . destination . . . dhcpserver . . . env . . . . . help . . . . . ip. . . . . . l1 . . . . . . l2 . . . . . . l2find . . . . l2display . . . log . . . . . multisys . . . . nvram reset . . . pbay . . . . . ping . . . . . power . . . . quit . . . . . rackid . . . . reboot_l2 . . . reset . . . . . select . . . . serial. . . . . shell . . . . . smp . . . . . sysname. . . .
Figures Figure 3-1 Rack Numbering . . . . . . . . Example of nmi Front Panel Display Output . . . . . . . . . . . . . 8 . 73 Figure 3-2 Example of softreset Command Output. . . . . . . .
Tables Table 2-1 Table 3-1 Table 3-2 Table 3-3 007-3938-003 L1 Controller Messages Valid Brick Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 . 45 l1dbg Commands . Valid Brick Types . . . . . . . . . . . . . . . . . . . . . . . . . . 64 . 95 . .
Examples Example 3-1 Example 3-2 Example 3-3 Example 3-4 Example 3-5 Example 3-6 Example 3-7 Example 3-8 Example 3-9 Example 3-10 Example 3-11 Example 3-12 Example 3-13 Example 3-14 Example 3-15 Example 3-16 Example 3-17 Example 3-18 Example 3-19 Example 3-20 Example 3-21 Example 3-22 Example 3-23 Example 3-24 Example 3-25 Example 3-26 Example 3-27 007-3938-003 * version Command Output . autopower Command Output . . . . . . . . . . . . . . . . . . . . 41 . 41 brick Command Output . . . . . . .
Examples Example 3-28 Example 3-29 Example 3-30 Example 3-31 Example 3-32 Example 3-33 Example 3-34 Example 3-35 Example 3-36 Example 3-37 Example 3-38 Example 3-39 Example 3-40 Example 3-41 Example 3-42 Example 3-43 Example 3-44 Example 3-45 Example 3-46 Example 3-47 Example 3-48 Example 3-49 Example 3-50 Example 3-51 Example 3-52 Example 3-53 Example 3-54 Example 3-55 Example 3-56 Example 3-57 Example 3-58 Example 3-59 Example 3-60 xvi ioport clksrc a Command Output . . . .
Examples Example 3-61 Example 3-62 Example 3-63 Example 3-64 Example 3-65 Example 3-66 Example 3-67 Example 3-68 Example 3-69 Example 3-70 Example 3-71 Example 3-72 Example 3-73 Example 3-74 Example 3-75 Example 3-76 Example 3-77 Example 3-78 Example 3-79 Example 3-80 Example 3-81 Example 3-82 Example 3-83 Example 3-84 Example 3-85 Example 3-86 Example 3-87 Example 3-88 Example 3-89 Example 3-90 Example 3-91 Example 3-92 Example 3-93 007-3938-003 reset Command Output . . . . . . . . . . . .
Examples Example 3-94 Example 3-95 Example 3-96 Example 3-97 Example 3-98 xviii shell Command Output . . . smp Command Output . . . . sysname Command Output . . sysname Command Output version Command Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Guide This guide describes how to use the L1 and L2 controller commands at your system console to monitor and manage the following systems: • SGI Origin 3000 series of servers • SGI Origin 300 series of servers • SGI Origin 300 systems with NUMAlink • SGI Onyx 3000 series of graphics systems • SGI Onyx 300 series of graphics systems • SGI Altix 350 systems • SGI Altix 3000 family of servers and superclusters The following topics are covered in this guide: • Chapter 1, “Introducing
About This Guide Note: The L1 and L2 controller command information contained in this user’s guide supersedes the L1 and L2 controller command information in SGI Origin 3000 Series Owner’s Guide and other owner’s and user’s guides. • SGI Origin 300 User’s Guide introduces the Origin 300 server and describes how to set up and operate the server. • SGI Origin 300 System with NUMAlink Module User’s Guide introduces the server and describes how to set up and operate the server.
About This Guide Note: InfoSearch is not available on Linux systems. • On IRIX systems, you can view release notes by entering either grelnotes or relnotes at a command line. • On Linux systems, you can view release notes on your system by accessing the README.txt file for the product. This is usually located in the /usr/share/doc/productname directory, although file locations may vary. • You can view man pages by typing man title at a command line.
About This Guide Reader Comments If you have comments about the technical accuracy, content, or organization of this document, contact SGI. Be sure to include the title and document number of the manual with your comments. (Online, the document number is located in the front matter of the manual. In printed manuals, the document number is located at the bottom of each page.) You can contact SGI in any of the following ways: • Send e-mail to the following address: techpubs@sgi.
Chapter 1 1.
1: Introducing the L1 and L2 Controllers You monitor the system with the L1 controller either at the L1 controller’s liquid crystal display (LCD) or at a system console. See Chapter 2, “Using the L1 and L2 Controllers,” for details on using the L1 controller, and see Chapter 3, “L1 and L2 Controller Commands,” for a list of L1 controller commands. The following are some of the functions performed by the L1 controller.
L2 Controller • Provides a high-speed serial channel to communicate between the system controller network and the hub ASIC. • Provides a high-speed serial channel to communicate with the L1 controller as a second brick or server. This is implemented as an RS-485 ICMB interface in the NUMAflex cable. • Controls Joint Test Action Group (JTAG) boundary scan. • Logs information in Non-Volatile Random Access Memory (NVRAM). • Provides a USB slave port to communicate with upstream system controllers.
1: Introducing the L1 and L2 Controllers The following are functions performed by the L2 controller. (For a list of functions specific to a product or component, see your server or graphics system user’s guide.) • Controls resource sharing. • Controls the L1 controllers on the server or graphics system. • Maintains controller configuration and topology information between the L1 and hardware L2 controllers. • Routes data between upstream devices and downstream devices.
Chapter 2 2.
2: Using the L1 and L2 Controllers Monitoring Feedback and Entering Commands You can monitor the L1 controller status and error messages on the L1 controller’s liquid crystal display (LCD) located on the front panel of the individual bricks. The L1 controller and L2 controller status and error messages can also be monitored at your system console. The L2 controller hardware includes L2 controller firmware.
Operating the L2 Controller L2 Mode After a connection to the L2 controller, the following prompt appears, indicating that the L2 is ready to accept commands: L2> Common operations are discussed in the following sections: • “Viewing System Configuration” on page 7 • “Setting Command Targeting” on page 8 • “Viewing Information, Warnings, and Error Messages” on page 11 • “Powering On, Powering Off, and Resetting the System” on page 11 Viewing System Configuration You can use the L2 config command t
2: Using the L1 and L2 Controllers 0 - local brick (the brick to which the USB cable is attached). Other than 0, the meaning of other values are system/device specific. rrr is the rack number t is the type of brick (C-brick, I-brick, and so on) ss is the slot number p is the partition (not present if the system is not partitioned). A brick is identified by its rack and slot. In the example shown above, 003c01 is a C-brick in rack 3 and unit position 1.
Operating the L2 Controller The slot is optional; if not given, then all slots in the specified rack(s) are implied. You should avoid specifying a rack list and slot list that include multiple racks and slots, such as rack 2-4,7 slot 1-8,11,13. Generally, a rack and slot together are used to specify an individual brick. You can use the aliases r and s to specify rack and slot, respectively.
2: Using the L1 and L2 Controllers The following example shows what bricks are found in the default destination. If you type a command not understood by the L2, the command is sent to these bricks. Note: In the current implementation, adding a brick to either rack 2 or 3 would not automatically include it in the default destination. You would need to reset the default destination. L2> destination 002c01 (127.0.0.1:0:2) 003c01 (127.0.0.
Operating the L2 Controller Viewing Information, Warnings, and Error Messages All information, warnings, and error messages generated by any of the system controllers are in the following form: 002c01 ERROR: invalid arguments for ‘ver’ command, try “help ver” The general format includes a brick identification and the type of message, followed by the message.
2: Using the L1 and L2 Controllers To enter console mode from L2 mode, press Ctrl+D at the L2 prompt and observe the response, as follows: L2> Ctrl+D entering console mode 002c01 console, to escape to L2 . . To return to L2 mode from console mode, press Ctrl+T, as follows: Ctrl+T escaping to L2 system controller L2> At this point, you can enter any L2 or L1 command.
Operating the L2 Controller Enter the select command alone to show the current console mode settings as follows: L2> select known system consoles (non-partitioned) 007c11 - L2 detected current system console console input: 007c11 console console output: not filtered On a partitioned system, enter the select command alone to show the current console mode settings as follows: L2>select known system consoles (partitioned) partition partition partition partition partition partition 1: 2: 3: 4: 5: 6: 007c11
2: Using the L1 and L2 Controllers The following are common subchannels associated with console communications on an SGI Altix system: • Subchannel 0A specifies Node 0, CPU A. • Subchannel 0C specifies Node 0, CPU B. • Subchannel 1A specifies Node 1, CPU A. • Subchannel 1C specifies Node 1, CPU B. • Subchannel 2A specifies Node 2, CPU A. • Subchannel 2C specifies Node 2, CPU B. • Subchannel 3A specifies Node 3, CPU A. • Subchannel 3C specifies Node 3, CPU B. • Node 0 console subchannel.
Operating the L2 Controller • Subchannel 3A specifies Node 3, CPU A. • Subchannel 3B specifies Node 3, CPU B. • Subchannel 3C specifies Node 3, CPU C. • Subchannel 3D specifies Node 3, CPU D. • Node 0 console subchannel. • Node 1 console subchannel. • Node 2 console subchannel. • Node 3 console subchannel. The following common subchannels are associated with console communications on all other MIPS/IRIX systems: • Subchannel 0 specifies CPU A. • Subchannel 1 specifies CPU B.
2: Using the L1 and L2 Controllers For console subchannels, perform the following: L2> select sub console0 or L2> select sub console1 and so on. The output console input: 001c05 console0 shows that the L2 will send console input to brick 001c05 and the subchannel to be used is the console0 subchannel. To change system console status from one brick to the attached C-brick, use the select command: 001c05-L2> select r 2 s 1 console input: 001c05 console console output: not filtered.
Operating the L2 Controller 002c01-L1> To return to L2 mode, press Ctrl+T, as follows: 002c01-L1> Ctrl+T escaping to L2 system controller, to send escape to L1 L2> At this point, you can enter any L2 command.
2: Using the L1 and L2 Controllers 003c01> Ctrl+D entering console mode 002c01 console, to escape to L1 Ctrl+T escaping to L2 system controller, to send escape to L1 L2> Ctrl+T escaping to L1 system controller 003c01-L1> l1 L1 command processor engaged, to exit. 003c01-L1> Operating the L1 Controller The L1 controller operates in one of the following two modes, each of which is discussed in the sections that follow: • L1 mode.
Operating the L1 Controller • “Viewing System Configuration” on page 19 • “Command Targeting” on page 21 • “Viewing Information, Warnings, and Error Messages” on page 22 • “Powering On, Powering Off, and Resetting the Brick” on page 22 Viewing System Configuration An L1 has limited knowledge of the system configuration. A C-brick only has information about its attached I/O brick and, if another C-brick is attached to it, information about that C-brick and its attached I/O brick.
2: Using the L1 and L2 Controllers 137.38.88.82:1:0 001c08 L2. The following example shows how to set rack 1, slot 8, for the C-brick with an IP address of 127.0.0.1: L2> config 127.0.0.1: 127.0.0.1:0:0 - ---c-127.0.0.1:0:1 - 001i01 127.0.0.1:0:5 - 001c05 L2> :0:0 brick rack 1 brick rack set to 001. L2> :0:0 brick slot 8 brick slot set to 08. L2> :0:0 reboot_l1 INFO: closed USB /dev/sgil1_0 INFO: opened USB /dev/sgil1_0 L2> L2> config 127.0.0.1: 127.0.0.1:0:0 - 001c05 127.0.0.1:0:1 - 001i01 127.0.0.
Operating the L1 Controller 001c05-L1> config :0 - 001c05 :1 - ---i-:5 - 001c08 :6 - 001p01 001c05-L1> iia brick rack 4 ---i--: brick rack set to 004.
2: Using the L1 and L2 Controllers 004i01: L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support] 002c01: L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support] 001x01: L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support] 003c01-L1> The L1 also supports a L1> . target. For example, 003c01-L1> 4.1 version 004i01: L1 0.7.
Operating the L1 Controller If an L2 is not present, you need to power on, power off, and reset the system from one of the C-bricks. You do so by targeting all bricks, as follows: 003c01-L1> * power up 003c01-L1> This command can require from several seconds to several minutes to complete. You can enter the power off and reset commands in similar ways. Console Mode from L1 In console mode, output from the system is visible and all input is directed to the system.
2: Using the L1 and L2 Controllers Console Selection The brick with which the L1 communicates in console mode is the system console or global master, and you can view and set it with the select command. By default, the C-brick attempts to communicate with its local CPUs when it enters console mode. If the system has been powered on and either one of the bricks has a request to be the system console, then the C-brick attempts to communicate with that brick.
Operating the L1 Controller The following are common subchannels associated with console communications on an SGI Altix system: • Subchannel 0A specifies Node 0, CPU A. • Subchannel 0C specifies Node 0, CPU B. • Subchannel 1A specifies Node 1, CPU A. • Subchannel 1C specifies Node 1, CPU B. • Subchannel 2A specifies Node 2, CPU A. • Subchannel 2C specifies Node 2, CPU B. • Subchannel 3A specifies Node 3, CPU A. • Subchannel 3C specifies Node 3, CPU B. • Node 0 console subchannel.
2: Using the L1 and L2 Controllers • Subchannel 3A specifies Node 3, CPU A. • Subchannel 3B specifies Node 3, CPU B. • Subchannel 3C specifies Node 3, CPU C. • Subchannel 3D specifies Node 3, CPU D. • Node 0 console subchannel. • Node 1 console subchannel. • Node 2 console subchannel. • Node 3 console subchannel. The following five common subchannels are associated with console communications on all other MIPS/IRIX systems: • Subchannel 0 specifies CPU A. • Subchannel 1 specifies CPU B.
Operating the L1 Controller For console subchannels, perform the following: L1> select sub console0 or L1> select sub console1 and so on. The output console input: 003c01 console shows that the L1 will send console input to brick 003c01 and the console subchannel will be used.
2: Using the L1 and L2 Controllers Upgrading L1 and L2 Firmware L1 and L2 firmware is currently distributed as part of your software package. This collection of software packages contains L1 and L2 firmware. The L1 and L2 firmware binary, and the utilities used to update it, are stored in /usr/cpu/firmware/sysco. The System Controller Software CD is not shipped by default. You can download the System Controller Software 1.x package from http://support.sgi.com/ or order it on CD-ROM (P/N 812-1138-007).
Identifying Bricks Upgrading L2 Firmware The L2 firmware consists of the following two parts: • Boot image • Kernel image Typically, you will upgrade the firmware through the network connection from the SGIconsole to the L2, as follows: $> /usr/cpu/firmware/sysco/flashsc --12 10.1.1.1 /usr/cpu/firmware/sysco/l2.bin local Once this command has executed, You must power-cycle the L2 to run the new image. To do this, you can use the L2 command reboot_l2.
2: Using the L1 and L2 Controllers To set the rack and slot for a brick, address it by its IP address, USB port, and L1 controller index. The following is an example: L2> 137.38.88.82:1:0 brick rack 3 L2> 137.38.88.82:1:0 brick slot 10 L2> 137.38.88.82:1:0 reboot_l1 L2> config 137.38.88.82:1:0 003c10 L2> The following example shows how to set rack 3, slot 1, for the C-brick with the IP address 127.0.0.1: L2> config 127.0.0.1: 127.0.0.1:0:0 - ---c-127.0.0.1:0:1 - 004i01 127.0.0.1:0:5 - 002c01 127.0.0.
Status and Error Messages To set the rack and slot from the L1 prompt, simply use the brick rack and brick slot commands. To set the rack and slot on one of the attached bricks (an attached I/O brick, C-brick, or a C-brick’s I/O brick), use the L1 targeting commands iia, iib, or nia, nib. See the following example. 003c01-L1> config verbose :0 - 003c01 (local) :1 - ---i-- (IIA) :5 - 002c01 (NIA) :6 - 001x01 (IIA NIA) 003c01-L1> iia brick rack 4 ---i--: brick rack set to 004.
2: Using the L1 and L2 Controllers Note: Besides the L1 control display, if you have an L2 controller, you can see the L1 controller messages on the L2 controller touch display located on the front door of the leftmost compute rack (position 001). If you have a system console, you can also see the L1 controller messages on your system console. Table 2-1 lists the L1 controller messages.
Status and Error Messages Table 2-1 L1 Controller Messages L1 System Controller Message Message Meaning and Action Needed Internal voltage messages: ATTN: x.xV high fault limit reached @ x.xxV 30-second power off sequence for the brick (or system, if no backup is available), server, or module. ATTN: x.xV low fault limit reached @ x.xxV 30-second power off sequence for the brick (or system, if no backup is available), server, or module. ATTN: x.xV high warning limit reached @ x.
2: Using the L1 and L2 Controllers Table 2-1 L1 Controller Messages (continued) L1 System Controller Message Message Meaning and Action Needed Temperature messages: high alt. ATTN: TEMP # advisory temperature reached The ambient temperature at the brick’s, server’s, @ xxC xxF or module’s air inlet has exceeded 27 ˚C. ATTN: TEMP # critical temperature reached @ The ambient temperature at the brick’s, server’s, xxC xxF or module’s air inlet has exceeded 31 ˚C.
Status and Error Messages Upstream devices (for example, rack display, console, and modem) provide control for the system, initiate commands for the downstream devices, and act on the messages that they receive from downstream devices.
Chapter 3 3. L1 and L2 Controller Commands You can use L1 and L2 controller commands to monitor and manage the SGI Origin 3000 series servers, SGI Origin 300 servers, SGI Origin 300 servers with a NUMAlink module, SGI Altix 350 systems, SGI Altix 3000 family of servers and superclusters, SGI Onyx 3000 graphics systems, and SGI Onyx 300 graphics systems.
3: L1 and L2 Controller Commands L2 Commands You can use all of the L2 controller commands to monitor and manage all of the devices (Origin 3000 series servers, SGI Altix 3000 series servers, Onyx 3000 graphics systems, Origin 300 servers, and Onyx 300 graphics systems) that include a hardware L2 controller. (You cannot use L2 controller commands with systems that do not include a hardware L2 controller.
Sending Commands to Specific Devices Sending Commands to Specific Devices You can use the variable to send a specific command to particular devices. (Use the help command to get the list of the many commands that you can enter with .) The following are some of the commands in which you can use as a variable: • • : : • .
3: L1 and L2 Controller Commands • If no target is specified and is an L2 controller command, it is executed on the local L2 controller only. If the L2 controller does not understand the command, it passes it on to all the L1 controllers in the default destination. (The destination command shows the default destinations.) • If the target is specified and is an L2 controller command, it is executed on the targeted L2 controllers.
L1 Controller Commands * (asterisk character) Use * to broadcast the command specified. For systems with a C-brick, a command that is broadcasted is sent to all of the bricks that are attached to the C-brick that issued the command. For systems that do not have a C-brick, a command that is broadcasted is sent to all systems connected to the system that issued the command. Example 3-1 shows sample output from the * version command.
3: L1 and L2 Controller Commands brick The following brick command set provides the status of the brick and sets the brick location and type. • brick • brick type • brick rack • brick slot • brick rackslot • brick partition none • brick partition Note: For this command set, you can use bay or upos instead of slot, rs instead of rackslot, and part or p in the place of partition.
L1 Controller Commands Example 3-5 brick slot Command Output 001c07-L1>brick slot 07 brick slot set to 07. Use brick rackslot to set the brick rack and slot number. Example 3-6 shows sample output. Example 3-6 brick rackslot Command Output 001c07-L1>brick rackslot 01 07 brick rack set to 01 brick slot set to 07 Use brick partition none to clear the brick partition number. Example 3-7 shows sample output.
3: L1 and L2 Controller Commands Note: For this command set, you can use cfg instead of config and v instead of verbose, Use the config command to view the L1 controller configuration information. Example 3-9 shows sample output from the config command for an Origin 300 server, Origin 300 server with NUMAlink, or Onyx 300 graphics system.
L1 Controller Commands Valid Brick Types Table 3-1 Type Description c C-brick i I-brick p P-brick r R-brick x X-brick n N-brick g G-brick ? Unknown brick type Use the other commands in this set as follows: • Use config verbose to view an expanded view of the L1 controller configuration information. • Use config reset to reset the L1 controller configuration. • Use config ring to check for network interface (NI) ring configuration. Used on all bricks.
3: L1 and L2 Controller Commands Use the cpu command to view the status of all cpus. Example 3-11 shows a sample output from the cpu command on a C-brick: Example 3-11 cpu Command Output T1-038c01-L1>cpu CPU Present Enabled --- ------- ------0 1 1 1 1 1 2 1 1 3 1 1 Use the other commands in this set as follows: • Use cpu e to enable all cpus, and use the cpu d command to disable all cpus. • Use cpu e to enable the number of the cpu entered.
L1 Controller Commands cti Use cti to send a command to an I/O interface (II) port (port A) found in I/O bricks (such as I-brick, P-brick, and so on) cabled to a C-brick. Example 3-13 shows sample output from the cti version command. Example 3-13 cti version Command Output 003c01-L1>cti version 002c01: L1 0.7.37 (Image A), Built 05/24/2000 14:59:42 [P1 support] Used on a C-brick or on server bricks performing the compute function.
3: L1 and L2 Controller Commands maximum of +12 (for 12 hours ahead of GMT) and a minimum of -12 (for 12 hours behind GMT). Used on all bricks. debug The following debug command set provides the status of and sets the virtual debug switches. (In systems that include C-bricks, these commands are valid only for C-bricks.) • debug • debug Use the debug command to determine the current settings for the virtual debug switches. Example 3-15 shows sample output.
L1 Controller Commands • display failure on • display power off • display attention off • display failure off Note: For this command, you can use dsp instead of display, pwr instead of power, attn instead of attention, and fail for failure. Use the display command to view the front panel display status. Example 3-17 shows sample output.
3: L1 and L2 Controller Commands eeprom Use the following eeprom command set to view the eeprom data and to write eeprom data. • eeprom • eeprom • eeprom fuel write default Use the commands in this set as follows: • Use eeprom to view brick eeprom data. Example 3-18 shows sample output. • Use eeprom to show brick eeprom data for specified eeprom, specified offset, and specified length.
L1 Controller Commands DIMM 6 DIMM 1 80 08 07 0e 04 04 b0 b0 60 00 00 00 ce 00 00 4c 33 33 19 02 09 ff ff ff DIMM 3 DIMM 5 DIMM 7 - no hardware (SPD) 0c 0a 02 48 00 01 02 26 00 00 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 33 42 20 54 ff ff ff ff ff ff ff ff ff ff - no hardware - no hardware - no hardware detected 04 a0 80 00 00 00 00 00 00 00 00 00 01 4b 4d 2d 47 30 ff ff ff ff ff ff detected detected detected 02 50 00 00 4d 20 ff ff 80 3c 00 00 33 42 ff ff 08 50 00 00 20 05 ff ff 08 30 00 00 3
3: L1 and L2 Controller Commands Use the commands in this set as follows: • Use env to view the status of the voltage, fan speed, and internal temperature of a brick. The output of the env command is divided into four areas: environmental monitoring and auto start status, voltage status, fan status, and temperature status (see Example 3-19). • Use env check to get a brief environmental status. • Use env on|off to enable or disable environmental monitoring.
L1 Controller Commands PIMM0 1.5V PIMM0 3.3V aux PIMM0 5V aux PIMM0 12V bias PIMM1 SRAM PIMM1 CPU PIMM1 1.5V PIMM1 3.3V aux PIMM1 5V aux PIMM1 12V bias Enabled Enabled Enabled Enabled Disabled Disabled Disabled Disabled Disabled Disabled 10% 10% 10% 10% 10% 10% 10% 10% 10% 10% 1.350/ 1.650 2.970/ 3.630 4.500/ 5.500 10.800/ 13.200 2.970/ 3.630 1.710/ 2.090 1.350/ 1.650 2.970/ 3.630 4.500/ 5.500 10.800/ 13.200 20% 20% 20% 20% 20% 20% 20% 20% 20% 20% 1.200/ 1.800 2.640/ 3.960 4.000/ 6.000 9.600/ 14.
3: L1 and L2 Controller Commands The voltage status contains five columns as follows: • The Description column provides the name of the supply voltage (2.5 V, 3.3 V, 5 V, etc.). • The State column provides the current state of the supply voltage (Enabled, Fault, Warning, Waiting, or Disabled). • The Warning Limits column provides the range of voltages that, when exceeded, causes a supply voltage to be in a Warning state.
L1 Controller Commands Example 3-20 env altitude high Command Output 001c07-L1>env altitude high 001c07-L1> Example 3-21 env reset Command Output 001c07-L1>env reset 001c07-L1> Used on all bricks. fan Use the fan command to determine whether the fans are on or off and to read the fan speeds. In the fan command output, the number in parentheses is the counter reading for the fan. The counter reading is a value provided by the fan tachometer.
3: L1 and L2 Controller Commands flash The following flash command set provides the status of and updates of the firmware images stored in flash memory. • flash status • flash status verbose • flash default • flash default current • flash default new • flash default old • flash default reset Use flash status to view the status of the two firmware images stored in flash memory. Example 3-23 shows sample output. Each image has a checksum value that indicates whether an image is valid.
L1 Controller Commands • Use flash default reset to set the firmware image with the latest time-stamp as the default image that the system controller uses when booting. If the selected firmware image is not valid, the flash default commands will return the following message: “cannot set default--image A (or B) is invalid!” Used on all bricks. help The following help command set provides helpful information on the system controller commands.
3: L1 and L2 Controller Commands Example 3-24 history Command Output 001c07-L1>history History length: 3/20 2: fan speed 4 1: fan 0: env Used on all bricks. iia, iib, iic, and iid Use the iia and iib targeting commands on a system with a C-brick with IP41 processors to send a command to the brick attached on the local II A port or local II B port, respectively.
L1 Controller Commands Example 3-25 ioport Command Output for a C-Brick 001c07-L1>ioport Junkbus I/O port speed: 600 MHz - current, attached I/O is detected 400 MHz - default, when no attached I/O detected Example 3-26 ioport Command Output for an X-Brick 001i21-L1>ioport XBridge port A speed: 400 MHz - current, no attached C detected XBridge port B speed: 600 MHz - current, from attached C 400 MHz - default, when no attached C detected XBridge UST clock source: port A Use ioport 400|600 to set the sp
3: L1 and L2 Controller Commands istat Use the following istat command set to view the status of the memory, queues, tasks, and memory allocation. • istat memory • istat queues • istat tasks • istat pmalloc Use istat memory to view the status of the L1 controller memory. Example 3-29 shows sample output.
L1 Controller Commands Example 3-31 001c07-L1>istat tasks MAIN_TSK [0x300019f8] USB_CNTL [0x30007f38] CMD_ITSK [0x300096e4] SMP_RTSK [0x3000e1c8] SMP_ITSK [0x3000e318] SMP_WTSK [0x3000e270] ENV_PITK [0x3000a9ec] ENV_FITK [0x3000aa94] ENV_TITK [0x3000ab3c] ENV_PMTK [0x3000abe4] ENV_FMTK [0x3000ac8c] ENV_TMTK [0x3000ad34] BDR_RTSK [0x30009f30] BDR_WTSK [0x3000a020] CTI_RTSK [0x3000f23c] CTI_WTSK [0x3000f2e4] USB_RTSK [0x3000edd4] USB_WTSK [0x3000eeec] SCAN_TSK [0x30002398] I2C_HIGH [0x30007154] I2C_LOW [0x30
3: L1 and L2 Controller Commands prealloc calls: 3 history: Used on all bricks. junkbus The following junkbus command set provides the status of and sets the L1 controller-to-junkbus protocol setting. (For systems that include a C-brick, these commands are valid only for the C-brick.) • junkbus • junkbus dump output Note: For the junkbus command set, you can use jbus instead of junkbus, d instead of dump, o for output, i for input, and rst for reset.
L1 Controller Commands l1 Use the l1 command to engage the L1 controller command processor. Press Ctrl+D to disengage the command processor. Example 3-34 shows sample output. Example 3-34 l1 Command Output 001c003-L1>l1 L1 command processor engaged, to exit. Used on all bricks. l1dbg The following l1dbg command set displays and sets the state of communication debugging features.
3: L1 and L2 Controller Commands Example 3-35 l1dbg Command Output 001c07-L1>l1dbg L1 irouter debugging is off L1 junkbus communication debugging is off L1 environmental debugging is off L1 port interrupt debugging is off L1 i2c interrupt debugging is off L1 voltage margin debugging is off Use l1dbg junkbus to turn on communication debugging for the L1 controller-to-junkbus-ASIC communication. Example 3-36 shows sample output from the l1dbg junkbus on command.
L1 Controller Commands Table 3-2 l1dbg Commands (continued) Command Description l1dbg pppdump Controls data dump on junkbus ppp errors. l1dbg promreq Controls PROM request debugging. l1dbg qsusp Sets queue suspend time req/rsp and evt. Used on all bricks. leds Use the leds command to read the value of the group 0 and group 1 status LEDs. In systems that include a C-brick, this command is only valid for the C-brick.
3: L1 and L2 Controller Commands Used on C-bricks or server bricks performing the compute function. Note that, if a C-brick is present, this command is only valid on the C-brick. link Use the link command to show the error status for the network interface (NI) and I/O interface (II) connector links. Use the link verbose command to show the complete status for the NI and II connector links. Note: For this command, you can use v in the place of verbose. Used on all bricks.
L1 Controller Commands USB: registered as remote SMP-R: UART:UART_NO_CONNECTION L1 booting... [L1-0] ALERT: eeprom.c line 367 ; eeprom 0 checksum error. USB: registered as remote L1 booting... [L1-0] ALERT: eeprom.c line 367 ; eeprom 0 checksum error. USB: registered as remote CTI-R: UART:UART_BREAK_RECEIVED CTI-R: IRouter:read failed - read error USB-R: USB:device was reset Use log clear or log reset to empty the log. Example 3-39 shows sample output.
3: L1 and L2 Controller Commands • margin|mgn 1.2 default|low|norm|high Set 1.2V to ROM default voltage • margin|mgn 1.2 Set 1.2V margin, exp 0..255 • margin|mgn 1.5 default|low|norm|high Set 1.5V to ROM default voltage • margin|mgn 1.5 Set 1.5V margin, 0..255 • margin|mgn 1.8 default|low|norm|high Set 1.8V to ROM default voltage • margin|mgn 1.8 Set 1.8V margin, 0..255 • margin|mgn 2.5 default|low|norm|high Set 2.5V to ROM default voltage • margin|mgn 2.
L1 Controller Commands • margin|mgn vid 1.5 default|low|norm|high Set 1.5V to ROM default voltage • margin|mgn vid 1.5 Set 1.5V margin, 0..31 • margin|mgn vid 2.5 default|low|norm|high Set 2.5V to ROM default voltage • margin|mgn VCPU default|low|norm|high Set VCPU to ROM default voltage • margin|mgn VCPU Set VCPU margin, 0..
3: L1 and L2 Controller Commands • margin|mgn p0sram Set PIMM0 SRAM margin, 0..255 • margin|mgn p1sram default|low|norm|high Set PIMM1 SRAM to ROM default voltage • margin|mgn p1sram Set PIMM1 SRAM margin, 0..255 • margin|mgn p0cpu default|low|norm|high Set PIMM0 CPU to ROM default voltage • margin|mgn p0cpu Set PIMM0 CPU margin, 0..
L1 Controller Commands • margin|mgn 2.5xio default|low|norm|high Set Fuel XIO voltage Used on all bricks. network The following network command set displays and sets the mode of the network communication interface. (For systems that include a C-brick, this command is valid only for C-bricks.) • network • network usb • network 422 • network autodetect|auto on • network autodetect|auto off Use network to view the current mode of the network communication interface.
3: L1 and L2 Controller Commands Used on C-brick or on server bricks performing the compute function and I/O bricks. Note that, if a C-brick is present, this command is valid only for the C-brick. fuel Use the fuel command to enable or disable the Silicon Graphics Fuel visual workstation LEDs for debugging purposes.
L1 Controller Commands nia and nib Use the nia and nib targeting commands to send a command to the brick attached on the local NI A port or NI B port, respectively. For more information, see “select” on page 87. Used on C-bricks with IP41 processors and on SGI Origin 3900 systems. nmi Use the nmi command to issue a non-maskable interrupt (NMI). For systems that include a C-brick, the nmi command is valid only for the C-brick. After the L1 system controller receives an nmi command, it displays “NMI...
3: L1 and L2 Controller Commands nvram reset The nvram reset command returns the NVRAM settings of the L1 controller to the factory default settings. Used on all bricks. partdb The following partdb command set displays, enables, and disables partitioning. • • • Note: For this command set, you can use e or on instead of enable and d or off instead of disable. Use partdb to display partition information from the database.
L1 Controller Commands • pbay dcport • pbay fru • pbay fru <0 for power bay, 1 - 6 for DPS> • pbay reset • pbay env • pbay env on|off • pbay init • pbay serial Use the pbay command to view the status of the power bay (see Example 3-44). Example 3-44 pbay Command Output 001r28-L1>pbay Total current: 16.5 Amps (+/-11%) Use pbay version to view the firmware version of the power bay (see Example 3-45).
3: L1 and L2 Controller Commands • Use pbay reset to reset the power bay and the power supplies. • Use pbay env to view the status of environmental monitoring. • Use pbay env on|off to enable or disable environmental monitoring. • Use pbay init to initialize communication with the power bay. • Use pbay serial to display the power bay ICMB card serial number. Used on C-bricks, I/O-bricks, R-bricks, and graphic bricks.
L1 Controller Commands • The Power column lists the value (error & off, error & on, okay & off, or okay & on) of the power OK and power on bits. • The Attn LED column lists the value (off or on) of the attention LED for the PCI card. • The Enable column lists the value (off or on) of the bus enable bit for the PCI card. • The Reset column lists the value (off or on) of the reset bit for the PCI card. Example 3-46 shows sample output from the pci command.
3: L1 and L2 Controller Commands Example 3-49 pci 1 2 u Command Output 001i21-L1>pci 1 2 u 001i21-L1> Use pci reset to reset all of the PCI cards in an I/O brick, Origin 300 server, or PCI expansion module. Example 3-50 shows sample output. Example 3-50 pci reset Command Output 001i21-L1>pci reset 001i21-L1> Use pci reset to reset all of the PCI cards on a bus in an I/O brick, Origin 300 server, or PCI expansion module. The variable is the bus number.
L1 Controller Commands Note: For the pimm command set, you can use the mnemonics int and ext instead of the words internal and external. Use pimm to determine the PIMM clock source (internal or external) and the clock mode (synchronous or asynchronous). Example 3-53 shows sample output. Example 3-53 pimm Command Output 001c07-L1>pimm PIMM clock source is external PIMM mode is asynchronous Use pimm clksrc to set the PIMM clock source to external or internal.
3: L1 and L2 Controller Commands • The Local Pwr column lists the value, “okay” or “none,” of the local power OK bit (bit 1) for each port. • The Link LED column lists the value, “on” or “off,” of the link LED bit (bit 2) for each port. • The SW LED column lists the value, “on” or “off,” of the software LED bit (bit 3) for each port. Note: For this command, the mnemonic prt may replace the word port.
L1 Controller Commands • power vrm • power • power up hold Note: For the power command set, the mnemonics pwr, u, and d may replace the words power, up, and down. Use power to view the detailed current state of the power and margin values for the power supplies in a brick or system. Example 3-58 shows sample output. Example 3-58 power Command Output 001c07-L1>power Supply State Voltage -------------- ----- --------48V on N/A DIMM on 2.509V 2.5V on 2.522V 1.5V on 1.509V 3.3V aux NC 3.
3: L1 and L2 Controller Commands power check Command Output Example 3-59 001c07-L1>power check power appears on Use power to power up or power down all of the power supplies in a brick or system. Example 3-60 shows sample output. power up Command Output Example 3-60 001c07-L1>power up 001c07-L1> Used on all bricks. reboot_l1 The following reboot_l1 command set reboots the L1 controller.
L1 Controller Commands • Use reboot_l1 raw to boot the L1 controller flash image at the flash image address listed for . Used on all bricks. reset Use the reset command to perform a reset of the system. After the system controller receives a reset command, it sets various control and status signals back to their default values, and reboots the operating system. Example 3-61 shows sample output. Example 3-61 reset Command Output 001c07-L1>reset 001c07-L1> Used on all bricks.
3: L1 and L2 Controller Commands Note: For the router command set, you can use rtr instead of router, rep instead of repeater, and ord instead of ordinary. Use router to view the current router type. Example 3-62 shows sample output. Example 3-62 router Command Output 001r19-L1>router router type is ordinary Use the other commands in this set as follows: • Use router meta to set the router type to meta. • Use router repeater to set the router type to repeater.
L1 Controller Commands • scan reset hard Perform hard JTAG reset (via TRSTN) • scan reset soft Perform soft JTAG reset (via TMS) • scan reset both Perform hard and soft JTAG reset • scan sel Select SIC: • scan sel Select SIC: • scan sel Select SIC: • scan ids Read and display IDCODE registers • scan set trst 0 Direct control of JTAG TRST signal • scan set trst 1 Direct control
3: L1 and L2 Controller Commands Direct control of JTAG TDI signal • scan set tdi 1 Direct control of JTAG TDI signal • scan set psi 0 Direct control of JTAG PSI signal • scan set psi 1 Direct control of JTAG PSI signal • scan get Display state of JTAG TAP signals • scan debug Set scan debug message level • scan debug Display scan debug message level • scan info Display scan information • scan count Count length of IR and BYPASS registers • scan count Count length of IR and BYP
L1 Controller Commands select The following select command set displays and sets the device to serve as console I/O. (These commands are valid only for C-bricks, or other devices with CPUs.) • select • select • select subchannel console • select subchannel • select subchannel • select subchannel • select filter Note: For this command set, you can use sel in the place of select, sub or s in the place of subchannel, and con in the place of console.
3: L1 and L2 Controller Commands • Use select subchannel console to set the current console subchannel as console I/O. • Use select subchannel to set the mode of console I/O to the subchannel specified for (possible values for are 0, 1, 2, 3, or 4). • Use select subchannel to set the mode of console I/O to a CPU subchannel (possible CPU subchannel values are a, b, c or d).
L1 Controller Commands • Use serial dimm to show the dual-inline memory module (DIMM) part and serial number. • Use serial clear to clear the SSN. • Use serial to erase and reassign the device’s SSN. The variable is the value of a security key that is provided only to SGI employees. • Use serial security on to enable the SSN security. Used on all bricks. softreset Use the softreset command to issue a software reset.
3: L1 and L2 Controller Commands Figure 3-2 Example of softreset Command Output Used on C-brick or on server bricks performing the compute function. Note that, if a C-brick is present, this command is valid only for the C-brick. test Use the following test command set to test various components in the L1 controller.
L1 Controller Commands • Use test i2c to test the I2C bus as many passes as you enter for the variable. • Use test ioexp set to set a value for an I/O expander. The variable is an I2C bus address and the variable is the value for the I/O expander. • Use test ioexp get to read a value from an I/O expander. The variable is an I2C bus address. • Use test ioexp get all to read the values from all of the I/O expanders.
3: L1 and L2 Controller Commands • uart • uart junkbus reset (You can use r in place of reset for this command) Example 3-66 shows sample output from the uart command.
L2 Controller Commands verbose Use the verbose command to get a system maintenance port (SMP) prompt and get into character-echo mode. Used on all bricks. version Use the version command to view the version of the firmware that is currently running in the system controller. Example 3-68 shows sample output. version Command Output Example 3-68 001r19-L1>version L1 0.7.27 (Image A), Built 04/28/2002 13:06:43 [P1 support] Used on all bricks.
3: L1 and L2 Controller Commands Use the autopower command to view the current auto power-up setting. Example 3-69 shows the sample output. autopower Command Output Example 3-69 L2>autopower auto power up appears disabled L2> Use autopower on to enable the auto power on. Use autopower off to disable the auto power on. Use autopower abort to abort the auto power on. config The following config command set displays configuration information.
L2 Controller Commands config Command output Example 3-70 L2>config 127.0.0.1: 127.0.0.1:0:0 127.0.0.1:1:0 127.0.0.1:1:1 127.0.0.1:2:0 - 001r19 001c07 001i21 001c10 The number that follows the USB port number, after the second colon, is the L1 index. Bricks are referenced by their racks and slot or bay locations. These values are stored in non-volatile memory on the L1.
3: L1 and L2 Controller Commands • Use config l2 to see configuration information for all the L1 controllers connected to the local L2 controller. • Use config l2 verbose to see more detailed L2 controller configuration information. • Use config rescan to force an L1 controller configuration update. • Use config auto to enable automatic L1 controller configuration updates. • Use config manual to disable automatic L1 controller configuration updates.
L2 Controller Commands destination The following destination command set displays the brick identification numbers of bricks that are the destinations of L2 commands, and sets the bricks that are the destinations for L2 commands. • destination • rack slot destination • destination reset Note: For these commands, the mnemonic dest may replace the word destination. Also, the mnemonics r and s may replace the words rack and slot.
3: L1 and L2 Controller Commands Use destination reset to reset the destination of L2 commands to all bricks in all racks and all slots. Example 3-74 shows sample output. Note: For this command, the mnemonic rst may replace the word reset.
L2 Controller Commands Use env summary to generate an environmental summary of an entire system. Example 3-76 shows sample output. Example 3-76 env summary Command Output L2>env summary all environmental conditions appear normal L2> Use rack slot env summary to display an environmental summary for specified rack number(s) and slot number(s).
3: L1 and L2 Controller Commands Use the ip command to display the L2 controller static IP address settings. Example 3-77 shows sample output. Example 3-77 ip Command Output essc1-001-L2>ip addr: 137.38.88.197 netmask: 255.255.255.0 broadcast addr: 137.38.88.255 essc1-001-L2> Use the other commands in this set as follows: • Use ip to set the address and netmask L2 static IP configuration parameters.
L2 Controller Commands Use rack slot l1 to engage the L1 command processor of a brick in a specified rack and slot. The variable following rack is one or more rack numbers, and the variable following slot is one or more slot numbers. Example 3-78 shows sample output. Note: For the variable, you can enter a single number, or two numbers separated by a hyphen to indicate a range, or numbers separated by commas to indicate separate items.
3: L1 and L2 Controller Commands Use :: l1 to send a command to a destination brick that does not yet have a brick identification number assigned to it. The variable is an IP address, the variable is the port number, the variable is the L1 controller index number, and the variable is an L1 controller command. Use :: l1 to send a command to a destination brick that does not yet have a brick identification number assigned to it.
L2 Controller Commands Use rack slot l2 to engage a specified L2 controller. The variable specifies the rack number(s) and slot number(s). Note: For the variable, you can enter a single number, or two numbers separated by a hyphen to indicate a range, or numbers separated by commas to indicate separate items. For , you can also enter an asterisk or the word “all” to select all the items available.
3: L1 and L2 Controller Commands l2display Use the following l2display command set to set the functioning of your L2 controller touch display. • l2display debug • l2display debug • l2display enable • l2display disable • l2display Note: For these commands, l2dsp can replace l2display in your entries. Use the commands in this set as follows: • Use l2display debug to set the L2 controller touch display to display the debug flags specified in .
L2 Controller Commands Use log clear|reset to empty the log. Use log insert to write a line in the log. The variable is text to enter in the log. Example 3-82 shows sample output where the text for is “Start the Test.” Example 3-82 log insert Start the Test Command Output L2>log insert Start the Test log entry made. multisys Use the following multisys command set to enable, disable, and show the settings for multiple system network sharing.
3: L1 and L2 Controller Commands nvram reset The nvram reset command returns the NVRAM settings of the L2 controller to the factory default settings. pbay Use pbay config to report the bricks connected to each power bay. Use pbay to send a specified command to one L1 controller connected to each power bay. ping Use the following ping command set to set the ping function between L2 controller and L2 controllers or L2 controller and L1 controllers.
L2 Controller Commands • Use ping sender <1 or 0> to enable (1) or disable (0) sender ping as a valid response. • Use ping l1 to set L2 controller to L1 controller ping frequency in seconds. • Use ping reset to reset L2 controller to L2 controller and L2 controller to L1 controller ping configuration to default. power The following power command set displays the power status of the bricks and powers up and powers down the bricks.
3: L1 and L2 Controller Commands Example 3-84 L2>power 001i21: power appears 001r19: power appears 001c07: power appears 001c10: power appears power Command Output on on on on Use rack slot power to view the power status of a specified brick. Use rack slot power up or rack slot power down to power up or power down specified bricks. The variable following rack is one or more rack numbers and the variable following slot is one or more slot numbers.
L2 Controller Commands quit Use the quit command to exit the L2 command processor. rackid Use the following rackid command set to display or set the L2 controller rack ID. • rackid • rackid Use the rackid command to display the rack ID of an L2 controller. Example 3-87 shows sample output.
3: L1 and L2 Controller Commands Note: For the reset command set, you can use rst in the place reset, r in the place of rack, and s in the place of slot. Use reset to reset the individual default brick or bricks. Caution: If you enter a reset command at the L2 prompt, it will reset all the bricks in your server system, which can create problems for your operating system if the operating system is running when you enter the reset command.
L2 Controller Commands • select partition • select filter on • select filter off Note: For this command set, the mnemonic sel, t, sub (or s), con, part (or p), res may replace the words select, terse, subchannel, console, partition, and reset. Use the select command to view the brick ID number and subchannel that receives console input. Example 3-88 shows sample output. In this example, the brick ID is a C-brick in rack 2, slot 1 (002c01) and the subchannel is the console channel.
3: L1 and L2 Controller Commands Example 3-89 select subchannel Command Output L2>select subchannel c console input: 003c01 CPUc console output: not filtered console detection: L2 detected Use select . to select the brick (brick ID) that receives console input. The variable is a rack number and the variable is a slot number. In Example 3-90, the brick ID is a C-brick in rack 3, slot 1 (003c01). Example 3-90 select . Command Output L2>select 3.
L2 Controller Commands serial Use the following serial command set to view and set the L2 controller system serial number. • serial • serial set Use the serial command to view the L2 controller system serial number. Example 3-92 shows sample output. Example 3-92 serial Command Output L2>serial L2 system serial number: not set. Use serial set to set the L2 controller system serial number. The variable is the L2 system serial number. Example 3-93 shows sample output.
3: L1 and L2 Controller Commands smp The following smp command set displays the status of the system maintenance port (SMP) network connection. These commands are also used to join a specified SMP group or leave a current SMP group. • smp • smp verbose • smp join • smp leave Note: For this command set, the mnemonic v may replace the word verbose. Use the smp command to view the status of the SMP network connection. Example 3-95 shows a sample output.
L2 Controller Commands sysname Use the following sysname command set to display or set the system name (name of the L2 controller). • sysname • sysname Use the sysname command to display the name of the system. Example 3-96 shows a sample output. Example 3-96 sysname Command Output essc1-001-L2>sysname L2 system name : essc1. essc1-001-L2> Use sysname to set a system name where the variable is the system name. Example 3-97 shows sample output.
3: L1 and L2 Controller Commands Note: For this command, ver may replace the word version, v may replace verbose, s may replace summary, c may replace check, r may replace rack, and s may replace slot. The version command displays the L2 controller firmware version currently running in the system controller, as shown in Example 3-98. Example 3-98 version Command Output L2>version L2 version 0.4.
Index Symbols *(asterisk character) command, 41 A autopower command, 41, 93 B brick command, 42 brick identification, 29 C command * (asterisk character), 41 autopower, 41, 93 brick, 42 config, 43, 94 cpu, 45 date, 47, 96 debug, 48 destination, 97 dhcpserver, 98 display, 48 eeprom, 50 env, 51, 98 fan, 55 flash, 56 007-3938-003 help, 57, 99 history, 57 iia, 47, 58 iib, 58 iic, 58 iid, 58 ioport, 58 ip, 99 istat, 60 junkbus, 62 l1, 63, 100 L1 controller commands, 40 l1dbg, 63 l2, 102 L2 controller comma
Index port, 79 power, 80, 107 quit, 109 rackid, 109 reboot_l1, 82 reboot_l2, 109 reset, 83, 109 router, 83 scan, 84 select, 87, 110 serial, 88, 113 shell, 113 smp, 114 softreset, 89 sysname, 115 test, 90 uart, 91 usb, 92 verbose, 93 version, 93, 115 command targeting L1 mode, 21 L2 mode, 8 commands sending to specific devices, 39 config command, 43, 94 console mode from L1 mode, 23 from L2 mode, 11 console selection, 12, 24 cpu command, 45 D date command, 47, 96 debug command, 48 destination command, 97 dh
Index L l1 command, 63, 100 L1 controller commands, 40 commands, devices supported, 38 messages, 31 online list, 37 L1 controller command *(asterisk character), 41 autopower, 41 brick, 42 config, 43 cpu, 45 date, 47 debug, 48 display, 48 eeprom, 50 env, 51 fan, 55 flash, 56 help, 57 history, 57 iia, 47, 58 iib, 58 iic, 58 iid, 58 ioport, 58 istat, 60 junkbus, 62 l1, 63 l1dbg, 63 leds, 65 link, 66 log, 66 margin, 67 network, 71 nextgen, 72 nia, 46, 73 nib, 73 nmi, 73 007-3938-003 nvram reset, 74 partdb, 7
Index L2 controller command autopower, 93 config, 94 date, 96 destination, 97 dhcpserver, 98 env, 98 help, 99 ip, 99 l1, 100 l2, 102 l2display, 104 l2find, 103 log, 104 multisys, 105 nvram reset, 106 pbay, 106 ping, 106 power, 107 quit, 109 rackid, 109 reboot_l2, 109 reset, 109 select, 110 serial, 113 shell, 113 smp, 114 sysname, 115 version, 115 L2 firmware upgrading, 28, 29 L2 mode powering off, 11 powering on, 11 resetting system, 11 setting command targeting, 8 to console mode, 11 to L1 mode, 16 viewin
Index powering on L1 mode, 22 L2 mode, 11 T Q U quit command, 109 uart command, 91 upgrading L1 and L2 firmware, 28 L1 firmware, 28 L2 firmware, 29 usb command, 92 R rackid command, 109 reboot_l1 command, 82 reboot_l2 command, 109 reset command, 83, 109 resetting L1 mode, 22 resetting system L2 mode, 11 router command, 83 test command, 90 V verbose command, 93 version command, 93, 115 viewing system configuration L1 mode, 19 S W scan command, 84 select command, 87, 110 serial command, 88, 113 sh
