An L1 controller has limited knowledge of the system configuration. A Cx-brick only has information about its attached I/O brick and, if another Cx-brick is attached to it, information about that Cx-brick and its attached I/O brick. An I/O brick only has information about its attached Cx-brick. An R-brick only has information about itself.

You can view a brick's configuration information with the config command:

001c07-L1> config 
:0 - 001c07
:1 - 001i23
:2 - 001p11
001c07-L1>

This example is a system with one Cx-brick and two I/O-bricks. The <number> that follows the colon (0, 1, 2, and 3, from top to bottom in this example), refers to the L1 connection relative to the local brick. (The local brick is the brick that is processing the command.) For example, “:0” is the local brick. A number greater than 0 indicates that it is attached directly to or indirectly to the local brick.

All commands entered affect only the local brick. You can target a command to all bricks (including the local brick) by prefixing the command with an asterisk (*).

001c07-L1> * version 
001c07:
L1 0.7.37 (Image A), Built 11/24/2001 14:59:42 [2MB image]
001i23:
L1 0.7.37 (Image A), Built 11/24/2001 14:59:42 [2MB image]
001c11:
L1 0.7.37 (Image A), Built 11/24/2001 14:59:42 [2MB image]
001x15:
L1 0.7.37 (Image A), Built 11/24/2001 14:59:42 [2MB image]
001c07-L1>

You can target commands to a single brick by using its rack and slot number in the form `<rack>.<slot> <command>':

001c07-L1> 1.11 version 
001i23:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [2MB image]

You can also target commands to a single attached brick with either the nia, nib, iia, or iib command:

001c07-L1> iia version 
001i23:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [2MB image]

All information, warnings, and error messages generated by any of the system controllers are in the following form:

001c07 ERROR: invalid arguments for `ver' command, try “help ver”

The general format of the message includes a brick identification (this is not present if the command was sent to the local brick only), type of message, and the message. These messages can be the result of an invalid command (as shown in the example) or from tasks running on the L1 controller, such as the environmental monitor.

Each L1 controller has a log of local events. Use the L1 command log to view the event on any of the L1 controllers.

You can power on, power off, or reset a brick with L1 commands. The L1 command to power on a brick is power up or pwr u. The L1 command to power off a brick is power down or pwr d. The L1 command to reset a brick is reset.

When you prefix the power up, power down, or reset command with an asterisk (*), you can power on, power off, or reset the entire system.

001c07-L1> * power up 
001c07-L1>

---

Note: These commands can require from several seconds to several minutes to complete.

---

The brick with which the L1 controller 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 Cx-brick attempts to communicate with its local CPUs when console mode is entered. If the system has been powered on and one of the bricks receives a request to be the system console, then the Cx-brick attempts to communicate with that brick. The select command by itself shows the current console mode settings:

001c07-L1> select 
console input: 001c07 console0
console output: not filtered.

The following common subchannels are associated with console communications:

The output console input: 001c07 console0 shows that the L2 controller will send console input to brick 001c07 and the subchannel to be used is the console subchannel on node 0.

To change system console from one Cx-brick to another, use the select <rack> <slot> command:

001c07-L1> select r 2 s 7 
console input: 002c07 console0
console output: not filtered.
001c07-L1> 

To change the subchannel used on the selected brick, use the select command followed by the subchannel number or the word console followed by a node number:

001c07-L1> select sub 0A
console input: 001c07 CPU 0A
console output: not filtered.
001c07-L1>

---

Note: See the bulleted list in “Console Selection ” for valid subchannels.

---

During the boot process on a multi-rack system, there is a window of time in which all Cx-bricks are producing output. This output can produce a somewhat jumbled output at the L1 controller. However, you can filter the console output so that the L1 controller shows output from only the brick chosen to receive console input. You can turn filtering on and off with the select filter command.

If you attempt to communicate with a brick that is not responding, a time-out condition results:

001c07-L1> 

entering console mode 001c07 console, <CTRL-T> to escape to L1
no response from 001c07 junk bus console UART:UART_TIMEOUT

When this time-out condition occurs, either the brick is hung or the subchannel is incorrect.

The Power UP button powers on a single brick, multiple bricks, a partition, multiple partitions, or an entire system. The DEST: field indicates which bricks are powered on. See “Power Up Confirmation Window” for information on using the Power UP button.

The Power DOWN button powers off a single brick, multiple bricks, a partition, multiple partitions, or an entire system. The DEST: field indicates which bricks are powered off. See “Power Down Confirmation Window” for information on using the Power DOWN button.

The RESET button resets partitions. If you issue a reset command to a partition, the main memory is cleared and the registers are set to default values in all bricks within the targeted partition(s). For systems that contain multiple partitions, single or multiple partitions can be reset without affecting the entire system. If you issue a reset command to a single brick within a partition, the entire partition is reset. See “Reset Confirmation Window” for information on using the RESET button.

The NMI button issues a non-maskable interrupt command to a brick, multiple bricks, a partition, or multiple partitions. When the system hangs, you can send the affected brick or partition an NMI interrupt via the L2 console. The interrupt goes to PROM and causes the CPU state to be captured for each targeted Cx-brick. This information is saved in flash PROM and the system log. This information assists SGI technicians in debugging system hangs and customer problems. See “NMI Confirmation Window” for information on using the NMI button.

The DEST: button sets the target destinations for the power up, power down, reset, and nmi commands. The text to the right of the DEST: button shows the current target destination. The target destination in Figure 8-6 is all racks and all slots (r * s *). Therefore, a power up, power down, reset, or nmi command is sent to all bricks in the system. The text ([57 Bricks]) indicates the number of bricks that will be affected by the command. See “Destination Selection Window” for information on using the DEST: button.

Figure 8-6. Home Window

To select all racks and all slots, press the ALL button. To scroll the rack list and brick list (not shown in Figure 8-12), press the arrow buttons below the Partition button on the display. The scroll buttons are active only when the number of racks exceeds the available space to display them.

Figure 8-12. Targeting All Bricks in System

Once you have selected the bricks, press the Apply button to set the new destinations. The home window will then reappear. The new destinations are reflected in the destination field across the bottom of the home window display. See Figure 8-6.

Before pressing the Apply button to set the new destinations, you can reset the destination window to the last applied state by pressing the Reset DEST button. The destination selection window will then revert back to the last applied status.

To select a single brick within a rack, see Figure 8-13 and follow these steps:

The new destination is reflected in the destination field near the bottom of the display window. For example, Figure 8-13 shows rack 001, slot 031 (r1 s31) as the destination.

Once you have selected the bricks, press the Apply button to set the new destinations. The home window will then reappear. The new destinations are reflected in the destination field across the bottom of the home window display.

To select multiple bricks within a rack, see Figure 8-14 and follow these steps:

The new destination is reflected in the destination field near the bottom of the display window. For example, Figure 8-14 shows rack 001, slots 015, 019, and 031 (r1 s15, 19, 31) as the destination.

Once you have selected the bricks, press the Apply button to set the new destinations. The home window will then reappear. The new destinations are reflected in the destination field across the bottom of the home window display.

To select all bricks within a rack, see Figure 8-15 and follow these steps:

The new destination is reflected in the destination field near the bottom of the display window. For example, Figure 8-15 shows all slots in rack 001 (r1 s *) as the destination.

Once you have selected the rack, press the Apply button to set the new destinations. The home window will then reappear. The new destinations are reflected in the destination field across the bottom of the home window display.

To select all bricks within a partition, see Figure 8-16 and follow these steps:

The new partition target is reflected in the destination field near the bottom of the display window. For example, Figure 8-16 shows partition 001 (p1) as the destination.

Once you have selected the partition, press the Apply button to set the new partition target. The home window will then reappear. The new partition target is reflected in the destination field across the bottom of the home window display.

Use the same procedure to select multiple partitions. Press ALL to select all partitions. If you select the Partition button, the command is sent to all bricks within the selected partition(s).

You can use the L2 config command to view the current system configuration from a brick level:

L2> config
L2 127.0.0.1: - 001 (LOCAL)
L1 127.0.0.1:0:5 	- 001c19
L1 127.0.0.1:0:0 	- 001c15
L1 127.0.0.1:1:5 	- 001c11
L1 127.0.0.1:1:0 	- 001c07
L1 127.0.0.1:1:1 	- 001i23
L2>

As shown above, config produces a list of bricks and their locations in the system and the system controller address of each brick. This is similar to the output from using the config command on the L1 controller with the addition of the IP address of the L2 controller and USB port number. The structure of the brick's address is as follows:

a.b.c.d:x:y

where:

A brick is identified by its rack, type, and slot (001c07). The structure of the brick location is as follows:

rrrbss.p

where:

In the example shown above, 001c07 is a Cx-brick in rack 001 and slot position 07.

If a command is not understood by the L2 controller, it is passed to the L1 controllers. The destination determines which L1 controllers receive the command. A destination, specified by the following, is a range of racks and slots:

rack <rack list> slot <slot list> 

The <rack list> specifies a list of racks. This can be a list delimited by commas, such that 2,4,7 specifies racks 2, 4, and 7. You can use a dash to specify a range of racks, such that 2-4 specifies racks 2, 3, and 4. Both nomenclatures can be combined, such that 2-4,7 specifies racks 2, 3, 4, and 7.

You can specify the <slot list> using the same nomenclature. The slot number is the lowest unit number that the brick occupies. This number is located on the rack rail slightly above where the bottom of the brick sits. For example, in Figure 8-17, the slot number of the brick is 11.

Figure 8-17. Rack Numbering

The slot <slot list> is optional; if not given, then all slots in the specified rack(s) are implied. You should avoid specifying a rack list and a slot list that includes multiple racks and slots, such as rack 2-4,7 slot 1-8,11,13. Generally, you specify a rack and slot together to specify an individual brick.

You can use the aliases r and s to specify rack and slot, respectively. You can use the alias all or * in both the <rack list> and the <slot list>, or by themselves, to specify all racks and all slots.

To send a command to all bricks in a partition, enter the following:

partition <partition> <cmd>

The default destination of a command when the L2 controller is first initiated is all racks and all slots. You can change the default destination by using the destination command:

L2> destination 
all racks, all slots
L2>

The following command sets the destination as all slots in racks 2 and 3:

L2> r 2,3 destination 
2 default destination(s) set
L2>

The following example shows what bricks are found in the default destination. If you enter a command not understood by the L2 controller, the command is sent to these bricks.

---

Note: In the current implementation, if you add a brick to either rack 2 or 3, it would not be automatically included in the default destination. You would need to reset the default destination.

---

L2> destination 
002c07 (127.0.0.1:0:2)
003c07 (127.0.0.1:0:0)
L2>

The following command resets the default destination to all racks and all slots:

L2> destination reset 
default destination reset to all racks and slots
L2>

The current destination of a command is a range of racks and slots included with the command. For example, the following command sends the command <L1 command> to all bricks in racks 2, 3, 4, and 7:

L2> r 2-4,7 <L1 command> 

This is a one-time destination.

Some L2 commands are the same as the L1 commands. In many cases, this is intentional because the L2 controller provides sequencing that is necessary for a command to function correctly.

When L1 and L2 commands are similar, you can ensure that an L1 command is entered for the bricks in the current destination by preceding the command <L1 command> with the l1 command:

L2> r 2-4,7 l1 <L1 command> 

This is a one-time destination.

All information, warnings, and error messages generated by any of the system controllers are in the following form:

001c07 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. A message may be the result of an invalid command, as shown in the example, or the result of tasks running on the L1 controller, such as the environmental monitor.

Each L1 controller has a log of local events. Use the L1 command log to view events on any of the L1 controllers.

You can power on and power off the system with the power command. This command is interpreted by the L2 controller, because the bricks must be powered on in a specific order.

L2> power up 
L2>

Depending on the size of the system, the power command may require several seconds to several minutes to complete. In the example above, all racks and slots in the default destination are affected. Any errors or warnings are reported as described above in “Viewing Information, Warnings, and Error Messages”.

To power on or power off a specific brick, specify a current destination:

L2> r 2 s 7 power up 
L2>

To power on or power off all bricks in a partition, enter the following:

L2> partition <partition number> <power up or power down>

To reset the system, enter the following:

L2> reset
L2>

This command restarts the system by resetting all registers to their default settings and rebooting the system controllers. Resetting a running system will cause the operating system to reboot and all memory will be lost.

When in console mode, the L2 communicates with the Cx-brick that is the system console or global master. All input from the console is directed to the Cx-brick. You can set and view the system console with the select command.

The L2 controller chooses the Cx-brick as the default console in the following priority order:

The select command by itself shows the current console mode settings:

L2> select 
known system consoles (non-partitioned)

	001c07-L2 detected

current system console

console input: 001c07 CPU 0A
console output: not filtered

The following common subchannels are associated with console communications:

The output console input: 001c07 console0 shows that the L2 controller will send console input to brick 001c07 and the console0 subchannel will be used.

To change the brick that will be the system console, use the select <rack>.<slot> command, where <rack> is the rack and <slot> is the slot where the brick is located:

L2> select 3.7 
console input: 003c07 console
console output: no filtered
console detection: L2 detected

To change the subchannel used on the selected brick to be the system console, use the select subchannel <0A|0B|0C|0D|1A|1B|1C|1D|2A|2B|2C|2D|
3A|3B|3C|3D> command. (Use the select subchannel console to select the current console as the subchannel of the brick to be the system console.) For example, to select the subchannel that corresponds to CPU A of node 1, enter the following:

L2> select subchannel 1A
console input: 003c07 console CPU1A
console output: no filtered

---

Note: See the bulleted list in “Console Selection ” for valid subchannels.

---

During the boot process on a multibrick system, there is a window of time in which all Cx-bricks are producing output. This can result in a somewhat jumbled output at the L2 controller. However, you can filter console output so that the L2 controller shows output from only the brick chosen to receive console input. You can turn on and off filtering with the select filter on and select filter off commands.

If you attempt to communicate with a brick chosen to receive console input but that is not responding, a time-out condition results:

L2> Ctrl+D 
entering console mode 001c07 CPU1A, <CTRL_T> to escape to L2

no response from 001c07 Junk bus CPU1A system not responding
no response from 001c07 Junk bus CPU1A system not responding

When this time-out condition occurs, either the brick is hung or the subchannel is not correct.