User`s guide

Operating the L1 Controller
007-3938-003 19
• “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. 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, as follows:
003c01-L1> config
:0 - 003c01
:1 - 004i01
:2 - 002c01
:3 - 001x01
003c01-L1>
Bricks are referenced by their racks and slot or bay locations. These values are stored in
nonvolatile memory on the L1. Virtually all system controller communications require
that each brick has a valid and unique rack and slot.
If a brick is not set with its rack and slot number, it appears in the output of an L2 config
command, as shown in the following example:
L2> config
137.38.88.82.1.0 ---c-- (no rack/slot set)
L2>
To set the rack and slot for a brick, address it by its IP address, USB port, and L1 controller
index. Note the following example:
L2> 137.38.88.82:1:0 brick rack 1
L2> 137.38.88.82:1:0 brick slot 8
L2> 137.38.88.82:1:0 reboot_l1
INFO: closed USB /dev/sgil1_0
INFO: opened USB /dev/sgil1_0
L2>config