| Sun Fire V210 and V240 Servers Installation Guide |     |
| Sun Fire V210 and V240 Servers Installation Guide | |
| C H A P T E R 3 |
|
Powering On and Configuring the Server |
This chapter tells you how to power on and configure the server to suit your application. It contains the sections:
Before you power on the server, you should become familiar with the LED indicators associated with the server itself and with various components. The server status indicators are located on the bezel and repeated on the back panel. The components with LED indicators to convey status are power supply units, Ethernet ports and hard disk drives. TABLE 3-1 contains explanations of the indicators.
|
Either power is not present, or the Solaris OS is not running. |
|||
|
The server has detected a problem and requires the attention of service personnel. |
|||
|
The network link is established and running at its maximum supported speed. |
||
To power on the server, you can use either the On/Standby button, located behind the front bezel, or you can use the keyboard. Powering on from the keyboard enables you to see system output as the server powers on.
Before you begin the procedures in this section, make sure that the keyswitch is in the normal position. This position allows the On/Standby button to control the power state of the server. For more information on the operation of the keyswitch, see the Sun Fire V210 and V240 Servers Administration Guide.
The Sun Fire V210 server does not have a keyswitch.
|
1. Connect the server to the power supply.
The server automatically goes into Standby power mode when it is connected to a power source.
2. Set up a connection to the SERIAL MGT port.
For details, refer to the Sun Fire V210 and V240 Servers Administration Guide.
When you switch to the ALOM prompt after initial power on, you will be logged in as the admin user and prompted to set a password. You must set this password in order to execute certain commands.
3. If you are prompted to do so, set a password for the admin user.
Once the password is set, the admin user has full permissions and can execute all ALOM command-line interface (CLI) commands.
4. Turn on power to any peripherals and external storage devices you have connected to the server.
Read the documentation supplied with the device for specific instructions.
5. At the console prompt, type the following command to power on the server:
6. At the console prompt, type the following to access the server:
|
|
Caution - Never move the system when the system power is on. Movement can cause catastrophic hard drive failure. Always power off the system before moving it. |
1. Connect the server to the power supply.
The server automatically goes into Standby power mode when it is connected to a power source.
2. Turn on power to any peripherals and external storage devices you have connected to the server.
Read the documentation supplied with the device for specific instructions.
4. (Sun Fire V240 only) Insert the system key into the keyswitch and set it to the Normal or Diagnostics position.
5. Press the On/Standby button.
a. Turn the keyswitch to the Locked position.
This prevents anyone from accidentally powering off the system.
b. Remove the system key from the keyswitch and store it in a secure place.
|
|
Note - Applications running on the Solaris OS can be adversely affected by a poorly executed system shutdown. Make sure you have gracefully shut down any applications before powering off the system. |
1. Notify users that the system will be powered down.
2. Back up the system files and data, if necessary.
3. (Sun Fire V240 only) Ensure that the keyswitch is in the Normal or Diagnostics position.
4. Press and release the On/Standby button behind the front bezel.
The system begins an orderly software system shutdown.
5. Wait for the front panel green LED to go out.
6. (Sun Fire V240 only) Remove the system key from the keyswitch and store it in a secure place.
7. Set up a console session to the server.
Refer to the Sun Fire V210 and V240 Servers Administration Guide for instructions on how to set up a console session.
The Sun Fire server ships with the Solaris 10 OS and the Java Enterprise System preinstalled on the hard drive. When you power on the server for the first time, a series of questions lead you through the configuration procedure. This procedure consists of a number of questions. The answers you give determine how the server is configured.
With the release of OpenBoot PROM 4.16.2, diagnostics are enabled by default. This ensures complete diagnostic test coverage on the initial boot and after error or reset events. This change results in increased boot time. To change the diagnostic settings after the initial boot and after you configure the server for the first time, refer to the OpenBoot PROM Enhancements for Diagnostic Operation in the shipping kit.
Choose the configuration that best suits your requirements from the list below and follow the instructions in the appropriate section to power on and configure your server.
|
During booting you will be prompted for certain information. The information you provide determines the configuration of the server.
1. Specify the type of terminal with which you are communicating with the server.
2. Specify whether you need IPv6 enabled, and then follow the instructions on the screen.
3. Specify whether you want to enable the Kerberos Security mechanism, and then follow the instructions on the screen.
4. When prompted, give a password (if any) for users logging in as root.
|
Follow the instructions in this section if you do not have a Name Server configured on your network.
|
Tip - Read these instructions through before you follow them, to see what information the system will prompt you for when you start it for the first time. |
During booting you will be prompted for certain information. The information you provide determines the configuration of the server.
1. Specify the type of terminal you are using to communicate with the server.
2. When asked if you want the server to be networked, answer Yes.
You must manually specify an IP address when prompted.
3. Specify whether the IP address is to be configured by DHCP.
4. Specify which of the Ethernet ports you intend to use as the primary Ethernet connection.
5. Specify a host name for the server.
6. If prompted, specify the IP address for the system.
The system prompts you for this address if you declined to use DHCP in Step 3. It also asks you whether the server is to be part of a subnet, and if you answer Yes it prompts you to provide the netmask of the subnet.
7. Specify whether you need IPv6 enabled, and then follow the instructions on the screen.
8. Specify whether you want to enable the Kerberos Security mechanism, and then follow the instructions on the screen.
9. Specify the name service you want the server to use.
10. Specify the name of the domain of which the server will be a part.
11. Specify whether you want the system to search the network for a name server or whether you want it to use a particular name server.
12. If you chose to use a particular name server, specify the host name and IP address of the name server.
13. At the name server, create entries in the network administration files for the system you are setting up.
14. At the system you are setting up, follow the prompts to provide time and date information.
15. When prompted, give a password (if any) for users logging in as superuser.
|
1. Specify the type of terminal you are using to communicate with the server.
2. When prompted to indicate whether you want the server to be networked, specify No.
3. Specify a Host Name for the server.
4. Confirm the information you have given.
5. Specify the date and time information.
6. When prompted, give a password (if any) for users logging in as root.
If you want to start the power on process again, as if from a previously unused server, you must clear the configuration of the server.
|
1. At the Solaris OS prompt, type:
2. When prompted to confirm that you want to create a "blank" server, type y.
3. When the OpenBoot PROM prompt appears, type:
4. Follow the instructions in one of the following sections:
This section contains a brief introduction to the Sun Advanced Lights Out Manager (ALOM) software. For detailed ALOM instructions and configuration information, refer to the Sun Advanced Lights Out Manager User's Guide.
The ALOM software is preinstalled on the server and is ready to run as soon as power is applied to the server. However, you need to perform some basic configuration steps to customize the ALOM software to suit your application.
|
1. Type the default keystroke sequence:
2. If you are prompted to do so, set a password for the admin user.
After you set the password, the admin user has full permissions and can execute all ALOM CLI commands.
|
More than one ALOM user can be connected to the server console stream at a time, but only one user is permitted to type input characters to the console.
If another user is logged on and has write capability, you will see the message below after issuing the console command:
| Sun Fire V210 and V240 Servers Installation Guide | 819-4209-10 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Power On From the Keyboard
