If you select Rack/Slot and a rack number (001 in our example) from the destination selection window, the Slots selection section appears as shown in Figure 3-13. This section provides the following options:

ALL		Select ALL to select all the slots for the rack selected.
CLR		Select CLR to deselect all the slots you have selected for the rack.
Numbered selections		Select these numbers to pick the slots that you want as destination for the command you want to execute. Figure 3-13. Slot Selection Section

If you select Partition and ALL (to select all partitions in a server system) from the destination selection window, the partition selection window appears as shown in Figure 3-14.

Figure 3-14. All Partitions Selected Window

If you select Partition and a particular partition (001 in our example), the partition selection window appears as shown in Figure 3-15.

Figure 3-15. Individual Partition Selected Window

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

L2> config
127.0.0.1:
127.0.0.1:0:0 - 003c01
127.0.0.1:0:1 - 004c01
127.0.0.1:0:2 - 002c01
127.0.0.1:0:3 - 001x01
L2>

As shown above, config produces a list of bricks 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 with the addition of the L2 IP address and USB port number. The structure of the brick's address is as follows:

a.b.c.d:x:y - rrrtss.p

where:

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.

If a command is not understood by the L2 system controller, in general it is passed on to the L1 system controllers. The destination determines which L1s 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, sometimes referred to as a bay number, is the unit position number located on the rack, slightly above where the bottom of the brick sits. Each rack unit position number is located toward the top of the two lines that mark the unit position that the number represents. For example, the rack numbering for a brick located in slot 10 would appear on the left front side of the rack, as shown in Figure 3-20:

Figure 3-20. 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, 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. 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, type the following:

partition <partition> <cmd>

Default Destination 

When the L2 starts, the default destination is set to all racks and all slots. You can determine the default destination by using the destination command, as follows:

L2> destination 
all racks, all slots
L2>

The following command sets the destinations to rack 2 and 3, all slots:

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 type a command not understood by the L2, the command would be 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.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>

Current Destination 

The current destination is a range of racks and slots for a given 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.

Command Interpretation

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

When L1 and L2 commands are similar, you can assure that an L1 command is entered for the bricks in the current destination by preceding the <L1 command> with the L1 command (this is a one-time destination):

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

See “L2 Controller Command Set” in Appendix B for details on the L2 commands.

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

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

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

L2> power up 
L2>

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 in “Viewing Information, Warnings, and Error Messages”.

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

L2> r 2 s 5 power up 
L2>

You can enter the power down and reset commands in a similar way. See Appendix B, “System Controller Commands” for details on the L2 commands.

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

When in console mode, the L2 can communicate with a brick set with the select command to be the system console or global master that receives the console input. This system console can be set and viewed with the select command.

The L2 chooses the C–brick as the default console in the following order of priority:

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

L2> select 
console input: 002c01 console
console output: not filtered
console detection: L2 detected

There are five common subchannels associated with console communications:

The output console input: 002c01 console shows that the L2 will send console input to brick 002c01 and the console 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, as follows:

L2> select 3.1 
console input: 003c01 console
console output: no filtered
console detection: L2 detected

To change the subchannel used by the brick to be the system console, use select subchannel <a|b|c|d> command. (Use select subchannel console to select the console as the subchannel of the brick to be the system console.) For example, to select subchannel b, type the following:

L2> select subchannel b 
console input: 003c01 console CPU
console output: no filtered
console detection: L2 detected

During the boot process on a multibrick system, there is a window of time during which the C–bricks are all producing output. This can result in a somewhat jumbled output at the L2. Console output can be filtered, though, which means that the L2 will show output only from the brick chosen to receive console input. You can turn on filtering with select filter on and turn it off with select filter off.

If you try to communicate with a brick chosen to receive console input, but the brick is not responding, a time-out condition results, as follows:

L2> Ctrl+D 
entering console mode 003c01 CPU2, <CTRL_T> to escape to L2

no response from 003c01 bedrock CPU2 system not responding
no response from 003c01 bedrock CPU2 system not responding

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

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. An I/O brick only has information about its attached C–brick. An R–brick only has information about itself.

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

003c01-L1> config 
:0 - 003c01
:1 - 004i01
:2 - 002c01
:3 - 001x01
003c01-L1>

This example is a two C–brick, two I/O-brick system. The :<number> that follows the colon (0, 1, 2, and 3 from top to bottom in our example) refers to the L1 connection relative to the local brick. (The local brick is the brick that is processing the command.)

From a C–brick's perspective:

:0 is the local brick
:1 is the attached I/O brick
:2 is the attached C–brick
:3 is the attached C–brick's attached I/O brick

From an I/O brick's perspective:

:0 is the local brick
:1 is the attached C–brick on port A
:2 is the attached C–brick on port B

From an R–brick's perspective:

0: is 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 (*).

003c01-L1> * version 
003c01:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support]
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>

You can also target commands to a single attached brick with either the cti, ctc, or ctci command:

003c01-L1> cti version 
004i01:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support]
003c01-L1> ctc version
002c01:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support]
003c01-L1> ctci version 
001x01:
L1 0.7.37 (Image A), Built 05/24/2001 14:59:42 [P1 support]
003c01-L1>

See “L1 Controller Command Set” in Appendix B for details on the L1 commands.

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 of the message includes a brick identification (this is not present if the command was 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, such as the environmental monitor.

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

You can power on and power off the brick with the power command, as follows:

003c01-L1> power up 
003c01-L1>

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 a similar fashion. See “L1 Controller Command Set” in Appendix B for details on the L1 commands.

The brick with which the L1 communicates in console mode is the system console or global master, and it can be viewed and set with the select command. By default, the C–brick attempts to communicate with its local CPUs when console mode is entered. 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. The select command by itself shows the current console mode settings:

003c01-L1> select 
console input: 003c01 console
console output: not filtered.

There are five common subchannels associated with console communications.

The output console input: 003c01 console shows that the L1 will send console input to brick 003c01 and the console subchannel will be used.

To change system console status from one brick to the attached C–brick, use the select command, followed by ctc or the rack and slot number of the attached C–brick:

003c01-L1> select ctc 
console input: 002c01 console
console output: not filtered.
003c01-L1> select r 2 s 1 
console input: 002c01 console
console output: not filtered.
003c01-L1> 

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

003c01-L1> select 2 
console input: 002c01 CPU C
console output: not filtered.
003c01-L1>

During the boot process on a multi-rack system, there is a window of time during which both C–bricks are producing output. This resulting output may be a somewhat jumbled at the L1. Console output can be filtered, though, meaning that the L1 shows output only from the brick chosen to receive console input. You can turn filtering on and off with the select filter command.

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

003c01-L1> 

entering console mode 002c01 console, <CTRL-T> to escape to L1
no response from 002c01 bedrock console UART:UART_TIMEOUT

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