C H A P T E R 2

Powering On or Off and Resetting Components

This chapter contains the following sections:

Section 2.1, Powering On All Components at Once

Section 2.2, Powering Off All Components Except the Active System Controller

Section 2.3, Powering Off All Components Including the Active System Controller

Section 2.4, Powering on the Switch and System Controllers

Section 2.5, Powering Off a Switch and System Controller

Section 2.6, Powering on Server Blades

Section 2.7, Powering Off Server Blades

Section 2.8, Resetting System Controllers, Switches, and Server Blades

2.1 Powering On All Components at Once

Note - To use the poweron and poweroff commands, you must have r-level user permission on the System Controller. (For information about the levels of user permission available for the System Controller, see Chapter 3.)

To power on all components at once (to recover them from a powered down, ready-to-remove, or standby power state), type:

sc> poweron ch

2.2 Powering Off All Components Except the Active System Controller

You can power off (or power down to a ready-to-remove or standby) state all components (except the active System Controller) at once. The blade system chassis is designed so that you cannot power off or down the active System Controller in a single command. For the correct procedure to follow to power off all components including the active System Controller, see Section 2.3, Powering Off All Components Including the Active System Controller.

Caution - Before running any of the commands described in this section, make sure you have saved any switch settings that have changed since the last time each switch booted (if you want to preserve the changes). For instructions about saving your switch settings, refer to the Sun Fire B1600 Blade System Chassis Software Setup Guide.

Note - To use the poweron and poweroff commands, you must have r-level user permission on the System Controller. (For information about the levels of user permission available for the System Controller, see Chapter 3.)

TABLE 2-1 lists the different commands for powering off or powering down all components in the chassis except the active System Controller.

Where a command has options associated with it, you can specify more than one option on the command line. However, the -s and -r options for the poweroff command are logically incompatible. Therefore you cannot include them together on the same command line.


Command and Option (if any)	Effect of the Command
`sc> poweroff ch`	Powers off all components on the chassis except the active System Controller.
`sc> poweroff -f ch`	Powers off all components (except the active System Controller) even if an orderly shutdown of the operating system on a component has failed.
`sc> poweroff -F s`n	Powers off the blade in slot n even if the active System Controller has not finished executing commands (from another user) involving the specified blade.
`sc> poweroff -y ch`	Powers off all compononents (except the active System Controller) without displaying the confirmation prompt.
`sc> poweroff -s ch`	Powers down all components (except the active System Controller) to standby mode (equivalent of `standbyfru ch` command).
`sc> poweroff -r ch`	Powers down all components (except the active System Controller) to a state in which it is safe for them to be removed. The `-r` option also turns on the "ok to remove" LED for each component (equivalent of the `removefru ch` command).
`sc> standbyfru ch`	Powers down all components (except the active System Controller) to standby mode (equivalent of the `poweroff -s ch` command).
`sc> standbyfru -f ch`	Powers down all components (except the active System Controller) to standby mode even if an orderly shutdown of the operating system on a component has failed.
`sc> standbyfru -y ch`	Powers down all components (except the active System Controller) to standby mode without displaying the confirmation prompt.
`sc> removefru ch`	Powers down all components (except the active System Controller) to a state in which it is safe for them to be removed; this command also turns on the "ok to remove" LED for each component (equivalent of the `poweroff -r ch` command).
`sc> removefru -f ch`	Powers down all components (except the active System Controller) to a state in which it is safe for them to be removed even if an orderly shutdown of the System Controller's operating system has failed. This command also turns on the "ok to remove" LED for each component.

2.3 Powering Off All Components Including the Active System Controller

You cannot power off or down the active System Controller in a single command. To power it down to a ready-to-remove state, do the following:

1. Power off all components except the active System Controller.

Type:

sc> poweroff ch

2. Make sure all components (except the active System Controller) are in a ready-to-remove state.

Type:

sc> removefru ch

3. Put the active System Controller into a ready-to-remove state.

Type:

sc> removefru sscn

where n is either 0 or 1 depending on whether the active System Controller is the one in SSC0 or SSC1.

Note - You can only use the removefru command on the active System Controller when all other components are in a ready-to-remove state.

4. Remove the power supply cords from the SSC modules.

The SSC modules are not physically powered down until the power supply cords have been removed.

2.4 Powering on the Switch and System Controllers

The SSCs are powered on as soon as you apply power to the chassis. However, if you have powered one of them off or down for any reason, you need to use the poweron command to restart it. This section tells you how to do this.

Note - To power on the Switch and System Controller(SSC), you must have r-level user permission on the System Controller. For information about the levels of user permission available, see Chapter 3.

To power on a single Switch and System Controller, type:

sc> poweron sscn

where n is either 0 or 1 depending on whether you want to power on the System Controller in SSC0 or SSC1.

2.5 Powering Off a Switch and System Controller

Note - To power off a Switch and System Controller, you must have r-level user permission on the System Controller. For information about the levels of user permission available, see Chapter 3.

TABLE 2-2 lists the different commands for powering off or powering down the Switch and System Controller (SSC).

Note - You can only power off or down the standby System Controller. For information about powering down the active System Controller, see Section 2.3, Powering Off All Components Including the Active System Controller.


Command and Option (if any)	Effect of the Command
`sc> poweroff ssc`n	Powers off SSC n (where n is 0 or 1 depending on whether the standby System Controller is in SSC0 or SSC1).
`sc> poweroff -f ssc`n	Powers off the standby System Controller (SSC0 or SSC1) even if an orderly shutdown of the System Controller's operating system has failed.
`sc> poweroff -F ssc`n	Powers off the standby System Controller (SSC0 or SSC1) even if the active System Controller has not finished executing commands (from another user) involving the standby System Controller.
`sc> poweroff -y ssc`n	Powers off the standby System Controller (SSC0 or SSC1) without displaying the confirmation prompt.
`sc> poweroff -s ssc`n	Powers the standby System Controller (SSC0 or SSC1) down to standby-power mode (equivalent of `standbyfru` command).
`sc> poweroff -r ssc`n	Powers the standby System Controller down to a state in which it is safe for it to be removed; the `-r` option also turns on the "ok to remove" LED (equivalent of the `removefru` command).
`sc> standbyfru ssc`n	Powers the standby System Controller down to standby-power mode (equivalent of the `poweroff -s` command).
`sc> standbyfru -f ssc`n	Powers the standby System Controller down to standby-power mode even if an orderly shutdown of its operating system has failed.
`sc> standbyfru -F ssc`n	Powers the standby System Controller down to standby-power mode even if the active System Controller has not finished executing commands (from another user) involving the standby System Controller.
`sc> standbyfru -y ssc`n	Powers the standby System Controller down to standby-power mode without displaying the confirmation prompt.
`sc> removefru ssc`n	Powers the standby System Controller down to a state in which it is safe for it to be removed; this command also turns on the "ok to remove" LED on the SSC's rear panel (equivalent of the `poweroff -r` command).
`sc> removefru -f ssc`n	Powers the standby System Controller down to a state in which it is safe for it to be removed even if an orderly shutdown of the System Controller's operating system has failed. This command also turns on the "ok to remove" LED on the SSC's rear panel.
`sc> removefru -F ssc`n	Powers the standby System Controller down to a state in which it is safe for it to be removed even if the active System Controller has not finished executing commands (from another user) involving the standby System Controller.
`sc> removefru -y ssc`n	Powers the standby System Controller down to a state in which it is safe for it to be removed but does not display the confirmation prompt before doing so. This command also turns on the "ok to remove" LED on the SSC's rear panel.

2.6 Powering on Server Blades

Note - To power on any server blades, you must have r-level user permission. For information about the levels of user permission available, see Chapter 3.

To power on a single server blade, type:

sc> poweron sn

where n is the number of the slot containing the blade you want to power on.

To power on more than one server blade, specify each blade in a space-separated list as in the following example:

sc> poweron s1 s6 s11

2.7 Powering Off Server Blades

Note - To power off any server blades, you must have r-level user permission. (For information about the levels of user permission available on the System Controller, see Chapter 3.)

TABLE 2-3 lists the commands for powering off or powering down a server blade. To apply any of the commands to more than one server blade, use a space-separated list. For example, to power off the blades in slots 1, 3, and 15, you would type:

sc> poweroff s1 s3 s15

You can specify more than one option on the command line. However, the -s and -r options available for the poweroff command are logically incompatible. Therefore you cannot include them together on the same command line.

Note - The commands listed in TABLE 2-3 all attempt to shut down the operating system on the blade before powering off or powering down the blade itself.


Command and Option (if any)	Effect of the Command
`sc> poweroff s`n	Powers off the blade in slot n.
`sc> poweroff -f s`n	Powers off the blade in slot n even if an orderly shut down of its operating system has failed.
`sc> poweroff -F s`n	Powers off the blade in slot n even if the active System Controller has not finished executing commands (from another user) involving the specified blade.
`sc> poweroff -y s`n	Powers off the blade in slot n without displaying the confirmation prompt.
`sc> poweroff -s s`n	Powers the blade in slot n down to standby mode (equivalent of `standbyfru` command).
`sc> poweroff -r s`n	Powers the blade in slot n down to a state in which it is safe for it to be removed; the `-r` option also turns on the blue "ok to remove" LED on the front of the blade (equivalent of the `removefru` command).
`sc> standbyfru s`n	Powers the blade in slot n down to standby mode (equivalent of the `poweroff -s` command).
`sc> standbyfru -f s`n	Powers the blade in slot n down to standby mode even if an orderly shut down of the blade's operating system has failed.
`sc> standbyfru -F s`n	Powers the blade in slot n down to standby mode even if the active System Controller has not finished executing commands (from another user) involving the specified blade.
`sc> standbyfru -y s`n	Powers the blade in slot n down to standby mode without displaying the confirmation prompt.
`sc> removefru s`n	Powers the blade in slot n down to a state in which it is safe for it to be removed; this command also turns on the blue "ok to remove" LED on the front of the blade (equivalent of the `poweroff -r` command).
`sc> removefru -f s`n	Powers the blade in slot n down to a state in which it is safe for it to be removed. This command performs power down even if an orderly shutdown of the blade's operating system has failed. Thecommand also turns on the blue "ok to remove" LED on the front of the blade.
`sc> removefru -F s`n	Powers the blade in slot n down to a state in which it is safe for it to be removed. This command performs power down even if the active System Controller has not finished executing commands (from another user) involving the specified blade.
`sc> removefru -y s`n	Powers the blade in slot n down to a state in which it is safe for it to be removed but does not display the confirmation prompt before doing so. This command also turns on the blue "ok to remove" LED on the front of the blade.

2.7.1 Turning on the Blue "ok to remove" LED Manually

If you have a server blade powered down and you want to remove it, you can apply the removefru command to it anyway. This causes the blue "ok to remove" LED come on, enabling you to identify the blade easily when you go to the chassis to remove it. For example, if the blade in slot 3 were powered down but you wanted to turn the LED on, you would type:

sc> removefru s3

Are you sure you want to power off FRU S3 (y/n)?: y

FRU S3 is already powered off

Sep 17 13:14:49: bem: MINOR: S3: OK to Remove LED state changed to ON on FRU S3

2.8 Resetting System Controllers, Switches, and Server Blades

TABLE 2-4 lists the commands for resetting components of the blade system chassis.

If you install new firmware onto a System Controller (see Chapter 10), you will need to reset that System Controller afterwards.

Note - To reset any of the components of the blade system chassis, you must have r-level user permission on the System Controller. (For information about the levels of user permission available, see Chapter 3.)


Command and Option (if any)	Effect of the Command
`sc> reset s`n	Resets the server blade in slot n.
`sc> reset s`n sy	Resets the server blades in slots n and y. (Specify the blades you want to reset in a space-separated list.)
`sc> reset -y s`n	Resets the blade in slot n without displaying the confirmation prompt.
`sc> reset -F s`n	Forces the specified blade to reset even if the active System Controller has not finished executing commands (for another user) involving that blade.
`sc> reset -x s`n	Performs an externally-initiated reset on the blade in slot n.
`sc> reset ssc`n/`swt`	Resets the switch in SSCn (where n is 0 or 1).
`sc> reset -y ssc`n/`swt`	Resets the switch in SSCn without displaying the confirmation prompt.
`sc> reset -F ssc`n/`swt`	Resets the switch in SSCn even if the active System Controller has not finished executing commands (for another user) involving that switch.
`sc> reset -x ssc`n/`swt`	Performs an externally-initiated reset on the switch in SSCn.
`sc> resetsc`	Resets the System Controllers. Neither of the switches is affected by this reset. You will lose your user session when you reset the System Controller using this command.
`sc> resetsc -y`	Resets the System Controllers without displaying the confirmation prompt.
`sc> resetsc -F`	Resets the active System Controller without waiting for any outstanding `flashupdate` or `setupsc` commands (from another user) to finish executing. By default, the System Controller will not initiate the reset of itself until it has finished executing these commands for another user.
`sc> reset ssc`n/`sc`	Resets the standby System Controller (where n is 0 or 1 depending whether the standby System Controller is in SSC0 or SSC1).
`sc> reset -f ssc`n/`sc`	Forces the standby System Controller to reset even if it is not possible to shut down its operating system gracefully (where n is 0 or 1 depending whether the standby System Controller is in SSC0 or SSC1). When you execute this command you will also cause the switch in the same SSC unit to reset.
sc> break sn	If Solaris is running (and it is configured to handle breaks in this way), the `break` command causes a Solaris blade to drop from Solaris into either kadb or OBP, depending on the mode in which Solaris was booted. The break command disables the hardware watchdog on a Solaris blade and issues the following error: "Debugging requested; hardware watchdog disabled; reboot to re-enable."
sc> break -y sn	As above, but the -y option means that you are not prompted to confirm the `break` command that you have initiated.
sc> break sn sy sx	As above, but this command applies the break to blades n, y, and x.