Lines Matching +full:board +full:- +full:2

7 .TH CFGADM_SBD 8 "August 2, 2023"
9 cfgadm_sbd \- \fBcfgadm\fR commands for system board administration
12 \fBcfgadm \fR \fB-l\fR [\fB-a\fR] [\fB-o\fR parsable] \fI ap_id\fR...
17 \fBcfgadm \fR \fB-c \fR \fIfunction\fR [\fB-f\fR] [\fB-y\fR | \fB-n\fR]
18      [\fB-o\fR nopoweroff] [\fB-v\fR] \fI ap_id\fR...
23 \fBcfgadm \fR \fB-t\fR [\fB-v\fR] \fI ap_id\fR...
28 \fBcfgadm \fR \fB-x \fR [\fB-f\fR] [\fB-v\fR] \fIfunction\fR \fI ap_id\fR...
34 system boards. It also enables you to connect or disconnect a system board from
42 Each board slot appears as a single attachment point in the device tree. Each
44 and condition of each component, and the states and condition of each board
45 slot by using the \fB-a\fR option.
89 The component is connected to the board slot.
114 .SS "Board Conditions"
115 The following are the names and descriptions of the board conditions.
122 The board failed testing.
131 The board is operational.
140 The board has not been tested.
149 The board slot is unusable.
152 .SS "Board States"
153 Inserting a board changes the receptacle state from empty to disconnected.
154 Removing a board changes the receptacle state from disconnected to empty.
157 \fBCaution:\fR Removing a board that is in the connected state or that is
170 The board is powered on and connected to the system bus. You can view the
171 components on a board only after it is in the connected state.
180 The board is disconnected from the system bus. A board can be in the
181 disconnected state without being powered off. However, a board must be powered
191 A board is not present.
196 The occupant state of a disconnected board is always unconfigured. The
205 At least one component on the board is configured.
214 All of the components on the board are unconfigured.
218 Functions that change the state of a board slot or a component on the board can
250 Functions that change the condition of a board slot or a component on the board
253 information string in the \fBcfgadm\fR \fB-l\fR output. A \fBY\fR in the Busy
282 In the following code examples, the permanent memory on board 0 must be moved
283 to another board. Thus, board 0 is the source, and board 1 is the
287 A status change operation cannot be initiated on a board while it is marked as
296 # \fBcfgadm -c unconfigure -y SB0::memory &\fR
303 First, the memory on board 1 in the same address range as the permanent memory
304 on board 0 must be deleted. During this phase, the source board, the target
305 board, and the memory attachment points are marked as busy. You can display the
310 # \fBcfgadm -a -s cols=ap_id:type:r_state:o_state:busy SB0 SB1\fR
324 After the memory has been deleted on board 1, it is marked as unconfigured. The
325 memory on board 0 remains configured, but it is still marked as busy, as in the
342 The memory from board 0 is then copied to board 1. After it has been copied,
343 the occupant state for the memory is switched. The memory on board 0 becomes
344 unconfigured, and the memory on board 1 becomes configured. At this point in
345 the process, only board 0 remains busy, as in the following example.
361 After the entire process has been completed, the memory on board 0 remains
379 The permanent memory has been moved, and the memory on board 0 has been
381 either board.
382 .SS "Platform-Specific Options"
383 You can specify platform-specific options that follow the options interpreted
384 by the system board plugin. All platform-specific options must be preceded by
386 of a command with platform-specific options:
389 \fB\fIcommand\fR -o \fIsbd_options\fR,platform=\fIplatform_options\fR\fR
391 This man page does not include the \fB-v\fR, \fB-a\fR, \fB-s\fR, or \fB-h\fR
398 \fB\fB-c \fR\fIfunction\fR\fR
409 board slots and to all of the components on the system board.
419 board before it deletes the memory from the board you want to unconfigure.
421 find enough memory on another board or if it cannot find an appropriate
427 to proceed with the operation. You can use the \fB-y\fR or \fB-n\fR options to
444 system board slots.
447 unconfigure the occupant. It then powers off the system board. At this point,
448 the board can be removed from the slot.
450 If you specify \fB-o nopoweroff\fR, the \fBdisconnect\fR function leaves the
451 board powered on.
460 Changes the occupant state to configured. This function applies to system board
461 slots and to any components on the system board.
466 function configures all of the components on the board, except those that have
486 board slots.
489 \fB-a\fR option to view the status of the components on the board. The
498 \fB\fB-f\fR\fR
503 The \fB-f\fR option never overrides fundamental safety and availability
510 \fB\fB-l\fR\fR
514 controlled by the \fB-s\fR, \fB-v\fR, and \fB-a\fR options as specified in
517 altered by the \fB\fR\fB-o\fR\fB parsable\fR option.
608 \fBinter-board-interleave\fR
611 The board is participating in interleaving with other boards.
684 \fBboard\fR
687 The \fBboard\fR type displays the following boolean name. If it are not
692 \fBpowered-on\fR
695 The board is powered on.
699 \fB-o\fR \fBparsable\fR option is not specified.
707 \fB\fB-o\fR parsable\fR
713 The \fB-o parsable\fR option can be used in conjunction with the \fB-s\fR
715 \fB-s\fR option.
721 \fB\fB-t\fR\fR
724 Tests the board.
726 Before a board can be connected, it must pass the appropriate level of testing.
728 Use of this option always attempts to test the board, even if it has already
730 \fB\fR\fB-c\fR\fB connect\fR state change function is issued, in which case the
731 test step can be skipped if the board already shows an appropriate level of
732 testing. Thus the \fB-t\fR option can be used to explicitly request that the
733 board be tested.
739 \fB\fB-x\fR\fI function\fR\fR
742 Performs an sbd-class function. You can use the following functions:
749 Powers the system board on.
760 Powers the system board off.
788 is a board-relative unit number.
791 memory attachment point affects all of the memory on the system board.
799 \fBExample 1 \fRListing All of the System Board
803 # \fBcfgadm -a -s "select=class(sbd)"\fR
827 The board in Slot 2 failed testing.
833 Slot 3 is unusable; thus, you cannot hot plug a board into that slot.
836 \fBExample 2 \fRListing All of the \fBCPU\fRs on the System Board
840 # \fBcfgadm -a -s "select=class(sbd):type(cpu)"\fR
856 # \fBcfgadm -l -s noheadings,cols=info SB0::cpu0\fR
868 # \fBcfgadm -l -s noheadings,cols=info -o parsable SB0::cpu0\fR
876 \fBExample 5 \fRDisplaying the Devices on an I/O Board
880 # \fBcfgadm -a -s noheadings,cols=ap_id:info -o parsable IO1\fR
882 IO1       powered-on assigned
898 # \fBcfgadm -c unconfigure -y SB0::memory &\fR
899 # \fBcfgadm -l -s noheadings,cols=info -o parsable SB0::memory SB1::memory\fR
944 # \fBcfgadm -c unconfigure -y SB0::memory &\fR
950 if [ -z "$1" ]; then
957 cfgadm_info='cfgadm -s noheadings,cols=info -o parsable'
961 if [ -z "$remaining" ]; then
972         if [ -n "$remaining" -a "$remaining" -ne 0 ]