service command

This command resets a compute node, compute node system-management processor, I/O module, or the primary or standby CMM.

If command syntax is not correctly entered, or if a command fails to run, an error message is returned. See Common errors for a list of error messages that apply to all commands or service command errors for a list of error messages that are specific to the service command.

Attention: If you are managing your Flex System chassis using the optional Flex System Manager software, you must unmanage and remanage the chassis when performing virtual reseat (service-level reset) of the primary CMM using the service -vr command. See Flex System Manager management node information center page for more information.
Table 1. service command.

The command table is a multi-row, four-column table where each row describes a CMM CLI command option: column one lists command function, column two provides a detailed command description, column three shows command-option syntax, and column four lists valid command targets.
Function What it does Command Target (see paths in Command targets)
Virtual reseat Performs a virtual reseat (service-level reset) of the specified command target.

A virtual reseat simulates physical removal and insertion of the command target. The virtual reseat removes standby power from the command target and then restores it. Each command target type has unique behavior when virtually reseated:

  • A CMM or I/O module is automatically powered on after the virtual reseat.
  • A compute node or storage node remains off after a virtual reseat and the user will need to power it back on. The command forcibly shuts down the compute node operating system.
  • If the -vr command option is run on the primary CMM without specifying the -o command option, warnings about the standby CMM state are displayed.
Attention:
  • Performing a virtual reseat on Flex System components might result in the loss of data. Do not perform a virtual reseat unless you are instructed by Lenovo Support. Prior to executing a virtual reseat, perform any needed operations to protect user data.
  • Performing a virtual reseat on an Flex System V7000 storage node (or storage cluster) might result in the loss of data. Do not perform a virtual reseat on an Flex System V7000 storage node (or storage cluster) unless you are instructed by Lenovo Support. Prior to executing a virtual reseat, perform any needed operations to protect user data.
Important:
  • Instead of performing a virtual reseat on an Flex System V7000 storage node, use the "Powering on and powering off the clustered system" procedure to power off an Flex System V7000 storage node, if needed (see Powering on and powering off the clustered system).

(continued on next page)

 service -vr
This command can only be run by users who have one or more of the following command authorities:
  • For the CMM target:
    • Supervisor
    • Chassis Administration
    • Chassis Configuration
  • For the compute node or storage node target:
    • Supervisor
    • Blade Administration
    • Blade Configuration
  • For the I/O Module target:
    • Supervisor
    • I/O Module Administration
See Commands and user authority for additional information.
Primary or standby CMM:
  • mm[p]
  • mm[P]
  • mm[s]
  • mm[S]
  • mm[x]
  • where x is the primary or standby CMM bay number.
Compute node or storage node:
  • blade[x]
  • where x is the node bay number.
I/O module:
  • switch[x]
  • where x is the I/O-bay number.
Virtual reseat

(continued)
  • If you do perform a virtual reseat on an Flex System V7000 storage node, one or more nodes might cause a node error 578 and be unavailable. Use the Flex System V7000 storage node troubleshooting information to troubleshoot issues caused by the virtual reseat option (see Flex System V7000 Troubleshooting).

    For more information on Flex System V7000 storage node error 578, see Flex System V7000 error 578.

  • During a virtual reseat, the component will experience a temporary loss of communication and its power state will change.
  • If you are managing your Flex System chassis using the optional Flex System Manager software, you must unmanage and remanage the chassis when performing virtual reseat (service-level reset) of the primary CMM. See Flex System Manager management node information center page for information.
Note: Do not perform a virtual reseat on a compute node that indicates it is in maintenance mode. Indications of maintenance mode are shown in the CMM or IMM event logs and by management applications such as the optional Flex System Manager software.
    
Virtual reseat of primary CMM (suppress warnings for standby CMM) Performs a virtual reseat (service-level reset) of the specified command target.

A virtual reseat simulates physical removal and insertion of the command target. The virtual reseat removes standby power from the command target and then restores it.

  • A CMM is automatically powered on after the virtual reseat.
  • The -o command option suppresses warnings about the standby CMM state.
Attention:
  • During a virtual reseat, you will temporarily lose communication with the command target and its power state will change. Before performing a virtual reseat, make sure that you perform any actions necessary to protect user data.
  • If you are managing your Flex System chassis using the optional Flex System Manager software, you must unmanage and remanage the chassis when performing virtual reseat (service-level reset) of the primary CMM. See Unmanaging a chassis and Remanaging a chassis after unmanaging for information.
 service -vr -o
This command can only be run by users who have one or more of the following command authorities:
  • Supervisor
  • Chassis Administration
  • Chassis Configuration
See Commands and user authority for additional information.
Primary or standby CMM:
  • mm[p]
  • mm[P]
  • mm[s]
  • mm[S]
  • mm[x]
  • where x is the primary or standby CMM bay number.
Hard restart Performs a hardware reset of the system-management processor of the specified command target. A hard restart directly resets the system-management processor on the command target. The power state of the command target is not affected by this reset.
Note:
  • During a hard restart, you will temporarily lose communication with the command target. Communication between the compute node and its management network should automatically restore after the system-management processor reset is complete.
  • Not all compute nodes support the hard restart function.
  • A system-management processor does not need to be responsive in order to reset it.
 service -hard
This command can only be run by users who have one or more of the following command authorities:
  • Supervisor
  • Blade Administration
  • Blade Configuration
See Commands and user authority for additional information.
Compute node system-management processor:
  • sp

Example:

To perform a virtual reseat (service-level reset) of the I/O module in bay 1, while the Flex System Enterprise Chassis is set as the persistent command environment, at the system> prompt, type 
service -T switch[1] -vr
To perform a hardware reset of the compute node (service processor) in bay 1, while the Flex System Enterprise Chassis is set as the persistent command environment, at the system> prompt, type 
service -T blade[1]:sp -hard

The following example shows the information that is returned from these commands:

system> service -T switch[1] -vr
OK
system> service -T blade[1]:sp -hard
OK
system>
Parent topic: Command reference