C H A P T E R 3 |
Powering On the System |
This chapter includes instructions for booting the Sun Fire V215 and V245 servers and for enabling the system controller network management port.
The following topics are discussed:
The system controller runs on the 3.3V standby voltage. As soon as AC power is connected to the system, the system controller powers on, runs diagnostics, and initializes the ALOM firmware.
Note - If you are not logged in, ALOM times out after 60 seconds and reverts to the system console. For more information, refer to the Advanced Lights Out Management (ALOM) User's Guide. |
To Power On the System Controller |
1. Connect a terminal or a terminal emulator to the SC serial management port.
2. Configure the terminal or terminal emulator with these settings:
3. Turn on the terminal or terminal emulator.
4. Connect the AC power cable(s).
5. Watch the terminal for system messages.
After the system controller boots, the system controller login prompt is displayed on the serial console. The following example shows a partial output from the system controller boot sequence leading to the login prompt.
The system controller network management port is not operational until you configure the network settings for the system controller. Configure the system controller in this order:
1. After the system controller boots, access the ALOM command-line interface through the serial management port. See To Log Into the System Controller.
2. Configure the system controller. See To Configure the System Controller Network Management Port.
3. Enable the new values by resetting the system controller. See To Reset the System Controller.
When you power on the system for the first time, you use the system controller serial port to power on the server and run POST.
To Log Into the System Controller |
After the system controller boots, the sc> prompt is displayed. The default configuration provides an ALOM user account called admin. There is no default password, so you must create a password using the system controller password command.
1. Use the password command to set the admin password.
sc> password password: Changing password for admin Setting password for admin. New password: new-password Re-enter new password: new-password sc> |
2. Enter admin for the login name followed by your password.
To Configure the System Controller Network Management Port |
To access the system controller using the network for the first time, you must first configure the SC network management port through the SC serial management port.
Set these network parameters according to the specific details of your network configuration:
To configure these parameters you must use the setsc command. The usage is:
1. Set the netmask for the system controller.
This example uses 255.255.255.0 to set the netmask. Your network environment subnet might require a different netmask. Use a netmask number most appropriate to your environment.
2. Set the IP address for the system controller.
3. Set the IP address for the system controller gateway.
4. Set the if_network parameter to true.
5. Use the showsc command to verify that the parameters were set correctly.
The showsc command displays all the configuration parameters and their values, as listed in TABLE 3-1.
if_network[1] |
|
To Reset the System Controller |
After all of the configuration parameters are set, you must reset the system controller for the new values to take affect.
2. Reply y when you are prompted to confirm that you want to reset the system controller.
Note - You can specify the -y flag to the resetsc command and bypass the confirmation message. |
The system controller resets, runs diagnostics, and returns to the login prompt.
To Log Into the System Controller Using the Network Management Port |
Note - You must configure the system controller parameters shown in To Configure the System Controller Network Management Port before you can use the network management port. |
1. Open a Telnet session and connect to the system controller by specifying its network address.
2. Login as admin using the password you previously set.
After you have enabled the network management port on the system controller, power on the server and connect to the system console by following the procedures in this section.
To Power On the System |
Powering on the system requires you to use the poweron command at the SC console.
To initiate the power-on sequence, issue the poweron command.
You see an sc> alert message on the system console. This indicates that the system has reset.
To Connect to the System Console |
Output from POST, OpenBoot, and the Solaris OS is displayed in the system console using the network console on the system controller.
Execute the console command, and use the -f option to force the console to be attached to your session.
Multiple users can be connected to the console, but only one can be attached.
After you have connected to the system console, you are ready to boot the Solaris OS. The Solaris OS is preinstalled on Sun Fire V215 and V245 servers on the disk in slot 0. The Solaris OS is not configured (that is, the sys-unconfig command was run in the factory). If you boot the system from this disk, you will be prompted to configure the Solaris OS for your environment.
To Boot the Solaris Operating System |
1. At the ok prompt, boot from the disk that contains the Solaris OS.
2. Type the boot command at the ok prompt.
Use the value from Step 1 to construct the boot command. You must append the target to the disk path. In the following example, the system is being booted from disk 0 (zero), so @0,0 is appended to the disk path.
The Solaris OS should boot at this point.
3. Use the configuration information you gathered during preparing for the installation, and follow the instructions on the preinstalled software site.
4. Install the necessary patches and updates, if needed.
5. Install any optional software at this time.
If you have purchased any optional software, you should install it now by following the instructions provided with the software. Otherwise, at this point, you should be done with the installation of the server.
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.