C H A P T E R 5 |
General Administration |
This chapter explains how to perform the following administrative and maintenance procedures:
To power off the system, you must halt the Solaris operating environment in each domain and power off each domain.
Before you begin this procedure, have the following books available:
Note - If you have a redundant system controller configuration, review Conditions That Affect Your SC Failover Configuration before you power cycle your system. |
When you power off the system, power off all of the active domains. Then power off the power grid or grids. The last step is to power off the hardware.
|
1. Connect to the appropriate domain shell.
See System Controller Navigation.
2. Type the following from the platform shell to display the status of all domains:
3. Complete the following substeps for each active domain.
These substeps include halting the Solaris operating environment in each domain, turning off the domain keyswitch, and disconnecting from the session.
a. Enter the domain console you want to power off.
See To Navigate Between The Platform Shell And a Domain.
b. If the Solaris operating environment is running, log in as superuser and halt the operating environment:
c. You will see the OpenBoot PROM ok prompt when the Solaris operating environment is shut down.
d. From the ok prompt, obtain the domain shell prompt.
i. Press and hold the CTRL key while pressing the ] key to get to the telnet> prompt.
ii. At the telnet> prompt, type send break:
The domain shell prompt is displayed.
e. Turn the domain keyswitch to the off position with the setkeyswitch off command:
f. Disconnect from the session by typing the disconnect command:
4. Access the platform shell (see To Select Destinations From the SC Main Menu) and power off the power grids to power off the power supplies.
5. Power off the hardware in your system.
Refer to the "Powering Off and On" chapter of the Sun Fire 6800/4810/4800/3800 Systems Service Manual or the Sun Fire E6900/E4900 Systems Service Manual.
|
Refer to the "Powering Off and On" chapter of the Sun Fire 6800/4810/4800/3800 Systems Service Manual or the Sun Fire E6900/E4900 Systems Service Manual.
2. Access the system controller platform shell.
See To Select Destinations From the SC Main Menu.
a. Access the domain shell for the domain you want to boot.
See To Navigate Between The Platform Shell And a Domain.
b. Boot the domain with the system controller setkeyswitch on command.
This command turns on the domain and boots the Solaris operating environment if the OpenBoot PROM auto-boot? parameter is set to true and the OpenBoot PROM boot-device parameter is set to the proper boot device.
Use the setupdomain command (OBP.auto-boot? parameter), which is run from a domain shell, or the OpenBoot PROM setenv auto-boot? true command to control whether the Solaris operating environment auto boots when you turn the keyswitch on. For more information on the OpenBoot PROM parameters, see the OpenBoot Command Reference Manual included with your Solaris operating environment release.
At the ok prompt, type the boot command to boot the Solaris operating environment:
After the Solaris operating environment is booted, the login: prompt is displayed.
5. To access and boot another domain, repeat Step 4.
Each domain has a virtual keyswitch with five positions: off, standby, on, diag, and secure. The setkeyswitch command in the domain shell changes the position of the virtual keyswitch to the specified value. The virtual keyswitch replaces the need for a physical keyswitch for each domain. This command is also available, with limited functionality, in the platform shell.
For command syntax, examples, descriptions of setkeyswitch parameters, and results when you change the keyswitch setting, see the setkeyswitch command in the Sun Fire Midrange System Controller Command Reference Manual.
![]() |
Caution - During the setkeyswitchoperation, heed the following precautions:
|
|
1. Access the domain you want to power on.
See System Controller Navigation.
2. Set the keyswitch to on, diag, or secure, using the system controller setkeyswitch command.
This section describes how to shut down a domain.
|
1. Connect to the domain console of the domain you want to shut down.
See System Controller Navigation.
From the domain console, if the Solaris operating environment is booted you will see the % , #, or login: prompt.
2. If the Solaris operating environment is running, halt the Solaris operating environment from the domain console as superuser.
3. Enter the domain shell from the domain console.
See To Go From a Domain Console To a Domain Shell.
5. If you need to completely power off the system, see Powering Off and On the System.
When you assign a board to a domain, the board must be listed in the access control list (ACL) for the domain. It cannot be already assigned to another domain. The ACL is checked only when you assign a board to a domain. If the board is assigned to a domain when the domain is active, the board is not automatically configured to be part of that domain.
|
Note - This procedure does not use dynamic reconfiguration (DR). |
1. Access the domain shell for the domain to which the board will be assigned.
See To Go From a Domain Console To a Domain Shell and To Go From a Domain Shell To a Domain Console.
2. Type the showboards command with the -a option to find available boards that can be used in the domain.
In the domain shell, the command output lists boards that are in the current domain. You can assign any board that is not yet assigned to a particular domain, but the board must be listed in the access control list (ACL).
3. Determine if the board is listed in the showboards -a output.
a. Make sure that the board has not been assigned to another domain by running the showboards command in the platform or domain shell.
A board cannot be assigned to the current domain if it belongs to another domain.
b. Verify that the board is listed in the ACL for the domain.
Use the showplatform -p acls command (platform shell) or the
showdomain -p acls command (domain shell).
c. If the board is not listed in the ACL for the desired domain, use the setupplatform -p acls command from the platform shell to add the board to the ACL for the domain.
See To Configure Platform Parameters.
4. Assign the proper board to the desired domain with the addboard command.
The board must be in the Available board state. For example, to assign
CPU/Memory board, sb2, to the current domain, type:
The new board assignment takes effect when you change the domain keyswitch from an inactive position (off or standby) to an active position (on, diag, or secure) using the system controller setkeyswitch command.
Assigning a board to a domain does not automatically make that board part of an active domain.
5. If the domain is active (the domain is running the Solaris operating environment, the OpenBoot PROM, or POST), complete this step.
See To Go From a Domain Console To a Domain Shell.
b. Shut down the domain by typing the following command:
By setting the domain keyswitch to standby instead of off, the boards in the domain do not need to be powered on and tested again. Setting the keyswitch to standby also decreases downtime.
c. Turn the domain on by typing the following command:
Note - Rebooting the Solaris operating environment without using the setkeyswitch command does not configure boards that are in the Assigned board state into the active domain. |
d. If your environment is not set to boot the Solaris operating environment automatically in the domain after you turned the keyswitch on, boot the operating environment by typing boot at the ok prompt.
|
Note - This procedure does not use dynamic reconfiguration (DR). |
Unassign a board from a domain with the deleteboard command. For a complete description of the deleteboard command, see the Sun Fire Midrange System Controller Command Reference Manual.
1. Halt the Solaris operating environment in the domain.
2. Enter the domain shell for the proper domain.
See System Controller Navigation.
3. Turn the domain keyswitch off with setkeyswitch off.
4. Type the showboards command to list the boards assigned to the current domain.
5. Unassign the proper board from the domain with the deleteboard command:
6. Turn on the domain by typing the following command:
7. If your environment is not set to automatically boot the Solaris operating environment in the domain, boot the operating environment.
This release of system firmware (5.19.0) supports the installation of both PCI and PCI-X cards in PCI-X I/O boards on Sun Fire midrange systems. By default, the firmware enables PCI-X mode on any I/O cards installed into a PCI-X I/O board.
Note - Earlier generation (non-PCI-X) PCI I/O boards are ignored by the PCI-X software, and require no additional user administration. |
|
Use the forcepci board_specification on Command
The command in this example, changeds the default operating mode of the card in PCI-X board slot IB7/P0/B0 to PCI mode. The mode change takes effect after the next power cycle of the IO assembly.
|
Use the forcepci board_specification info Command
This command used in this example displays the mode status of the card in the specified PCI-X board slot.
|
Use the forcepci board_specification off Command
The command in this example changes the default operating mode of the card in board slot IB7/P0/B0 to PCI-X mode (the default mode). The mode change takes effect after the next power cycle of the IO assembly.
The HostID/MAC Address Swap parameter of the setupplatform command enables you to swap the HostID/MAC address of one domain with that of another. This feature is useful when host-licensed software is tied to a particular domain HostID and MAC address, but you need to run that host-licensed software on another domain. You can swap the domain HostID/MAC address with that of an available domain and then run the host-licensed software on the available domain, without encountering license restrictions tied to the original domain HostID/MAC address.
|
Note - If you want to downgrade from release 5.16.0 (or greater) to an earlier firmware release, you must restore the original domain HostID/MAC address assignments before performing the downgrade. For details, see To Restore the HostID/MAC Address Swapped Between Domains. If you have a midrange system that contains boards with UltraSPARC IV CPUs, you cannot downgrade the firmware to a version before 5.16.0 because those processors are not supported by firmware releases earlier than 5.16.0. |
1. From the platform shell on the main SC, type:
The HostID/MAC Address Swap parameters are displayed.
2. Select the domain pair involved in the HostID/MAC address swap.
One of domains selected must be the domain on which the host-licensed software currently runs. The other domain selected must be an available domain on which the host-licensed software is to run. The domains selected must not be active.
HostID/MAC Address Swap ----------------------- Domain to swap HostID/MAC address [A,B,C,D]: b Domain to swap HostID/MAC address with [A,B,C,D]: d Commit swap? [no]: y |
The HostID/MAC addresses of the specified domains are swapped when you commit the swap.
3. Indicate whether you want to swap the HostID/MAC addresses between another pair of domains.
4. To verify the HostID/MAC address swap, type:
The HostID/MAC address mapping mode setting is manual, which indicates that the HostID/MAC addresses for a domain pair have been swapped.
Note - If you are using a boot server, be sure to configure the boot server to recognize the swapped domain HostID/MAC addresses. |
|
1. From the platform shell on the main SC, type:
2. Enter y (yes) to restore the HostID/MAC addresses that were swapped between domains:
HostID/MAC Address Swap ----------------------- Restore automatic HostID/MAC address assignment? [no]: y |
3. To verify that the HostID/MAC addresses were restored to the original domains, type:
The HostID/MAC address mapping mode setting is automatic, which indicates that the swapped HostID/MAC addresses have been restored to their original domains.
Note - If you are using a boot server, be sure to configure the boot server to recognize the restored HostID/MAC addresses. |
The flashupdate command updates the firmware in the system controller and the system boards (CPU/Memory boards and I/O assemblies). There is no firmware on the Repeater boards. This command is available in the platform shell only. The source flash image can be on a server or another board of the same type.
For a complete description of this command, including command syntax and examples, see the flashupdate command in the Sun Fire Midrange System Controller Command Reference Manual.
Note - Review the README and Install.info files before you upgrade the firmware. |
In order to upgrade the firmware from a URL, the firmware must be accessible from an FTP or HTTP URL. Before performing the flashupdate procedure, read the Install.info file and the information in the "Description" section of the flashupdate command in the Sun Fire Midrange System Controller Command Reference Manual. The "Description" section covers:
This section describes when to use the dumpconfig and restoreconfig commands.
Use the dumpconfig command to save platform and domain settings after you:
For an explanation of how to use this command, see Saving the Current Configuration to a Server. For complete command syntax and examples of this command, refer to the dumpconfig command in the Sun Fire Midrange System Controller Command Reference Manual.
Use the restoreconfig command to restore platform and domain settings.
For complete command syntax and examples of this command, refer to the restoreconfig command in the Sun Fire Midrange System Controller Command Reference Manual.
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.