Command targets

You can set a persistent command target for the CMM CLI or send individual CLI commands to a specific target.

You can use the command-line interface to target commands to the Flex System Enterprise Chassis, the CMM, or to other devices installed in the chassis. The command-line prompt indicates the persistent command environment: the target where commands are directed unless another target is specified. You can specify a command target by using the full target name or by using a target name that is relative to the persistent command environment.

When a command-line interface session is started, the persistent command environment is system ; this indicates that commands are being directed to the Flex System Enterprise Chassis.

The following table lists Flex System components that are supported as command targets. Target names have been selected to maintain scripting compatibility with other Lenovo and IBM systems.

To direct commands to a specific command target, its path name must be specified, either as a full path name or as a path name based on the current persistent command environment. To view path names for targets in your Flex System Enterprise Chassis, use the list command.

Table 1. Valid command targets
Component Target path
Flex System Enterprise Chassis system
CMM (by bay number) mm[x]
CMM (primary) mm[p] or mm[P]
CMM (standby) mm[s] or mm[S]
Compute node blade[x]
Logical node grouping bladegroup[x]
System-management processor sp
Expansion adapter exp[x]
Compute node management card mgmtcrd[x]
Compute node microprocessor cpu[x]
Expansion node be[x]
Compute node high-speed expansion card hsec[x]
Compute node memory memory[x]
Compute node flash DIMM (Lenovo eXFlash Storage DIMM) flashdimm[x]
Storage expansion enclosure bladeenclosure[x]
Storage disk disk[x]
Alarm panel tap[x]
Storage backplane stgbkplane[x]
Add-in card addin[x]
Add-in card PCI-Express module pciexpress[x]
I/O (switch) module switch[x]
Power supply power[x]
Fan logic module fanmux[x]
Fan module blower[x]
Rear LED card mt[x]

You can change the persistent command environment for the remainder of a command-line interface session by using the env command (see env command). When you list the target as a command attribute by using the -T option, you change the target environment for the command that you are entering, temporarily overriding the persistent command environment. You can specify target environments by using the full path name or by using a partial (relative) path name that is based on the persistent command environment. Full path names always begin with "system". The levels in a path name are divided using a colon ( : ).

For example:

Most CMM commands must be directed to the primary CMM. If only one CMM is installed in the Flex System Enterprise Chassis, it always acts as the primary CMM. Either CMM can function as the primary CMM; however, only one CMM can be primary at one time. You can determine which CMM is acting as the primary CMM by using the list command (see list command).

Commands can be directed to the primary CMM, regardless of its bay location, using the -T system:mm[p] or -T system:mm[P] option. Commands can be directed to the standby CMM, regardless of its bay location, using the -T system:mm[s] or -T system:mm[S] option.

Example: To display a hierarchical list of all command targets in the Flex System Enterprise Chassis, while the Flex System Enterprise Chassis is set as the persistent command environment, at the system> prompt, type
list -l a

The following example shows the information that might be returned when the command is run:

system> list -l a
        blade[1]  Server1
        mm[1]     standby
        mm[2]     primary

The following table shows each target with its full path. This is the path that would be used if the persistent command environment was set to the Flex System Enterprise Chassis.

Table 2. Example system components and command paths
Component Target path
Flex System Enterprise Chassis system
Compute node, bay 1 (named ’Server1’) system:blade[1]
Node system-management processor, compute node bay 1 system:blade[1]:sp
Microprocessor, compute node bay 1 system:blade[1]:cpu[1]
Alarm panel, compute node bay 1 system:blade[1]:tap[1]
Storage backplane, compute node bay 1 system:blade[1]:stgbkplane[1]
Expansion node 1, compute node bay 1 system:blade[1]:be[1]
Add-in card 1, expansion node 1, compute node bay 1 system:blade[1]:be[1]:addin[1]
High-speed expansion card 2, add-in card 1, expansion node 1, compute node bay 1 system:blade[1]:be[1]:addin[1]hsec[2]
Add-in card 2, expansion node 1, compute node bay 1 system:blade[1]:be[1]:addin[2]
Memory module 1, compute node bay 1 system:blade[1]:memory[1]
Memory module 4, compute node bay 1 system:blade[1]:memory[4]
Add-in card 1, compute node bay 1 system:blade[1]addin[1]
Fan module 1 system:blower[1]
Fan module 2 system:blower[2]
Fan module 5 system:blower[5]
Fan module 6 system:blower[6]
Fan module 7 system:blower[7]
Fan module 10 system:blower[10]
Power supply 1 system:power[1]
Fan module, power supply 1 system:power[2]:blower[1]
Power supply 2 system:power[2]
Fan module, power supply 2 system:power[2]:blower[1]
Standby CMM, CMM bay 1 system:mm[s] or system:mm[S] or system:mm[1]
Primary CMM, CMM bay 2 system:mm[p] or system:mm[P] or system:mm[2]
I/O (switch) module, bay 1 system:switch[1]
Rear LED card system:mt[1]
Fan logic module 1 system:fanmux[1]
Fan logic module 2 system:fanmux[2]

The complete command target hierarchy for the example is shown in the following illustration.

Graphic illustrating an example Flex System command target hierarchy.