C H A P T E R 2 - Initial Software Configuration

C H A P T E R 2

Initial Software Configuration

To set up your Sun Fire V20z or Sun Fire V40z server the first time, you should perform some initial configuration tasks. This chapter explains these initial steps:

Configuring the Service Processor

Defining SP Network Settings

Defining a Name for the Server (optional)

Creating the Initial Manager Account

Installing and Mounting the NSV Software

Setting up the Platform Operating System and Drivers

Note - An operating system can be installed on the server without configuring the service processor (SP) or the network share volume (NSV). However, if you choose to skip the SP and NSV setup, you will not be able to use the remote-management capabilities of the system or the diagnostics.

Configuring the Service Processor

Caution - The service processor (SP) must be secured with a user name and password when the server is first deployed. Failure to secure the SP can expose the server to security and availability risks through the SP network interface.

The Sun Fire V20z and Sun Fire V40z servers include a dedicated SP for complete server independence and maximum availability of server management. The SP is an embedded PowerPC that provides the following functions:

Environmental monitoring of the platform (such as temperatures, voltages, fan speeds and panel switches)

Alert messages when problems occur

Remote control of server operations (boot, shutdown and reboot of the server's operating system, turning the server's power on and off, stopping the server's boot process in BIOS, and upgrading BIOS)

After supplying AC power to the server, you are ready to begin configuring the SP by setting an IP address and associated network settings for the SP. You can configure the SP network settings by using DHCP or by using a static IP address.

Defining SP Network Settings

This section contains two alternate methods you can use to define SP network settings:

Assigning SP Network Settings Using DHCP

Assigning Static SP Network Settings

Assigning SP Network Settings Using DHCP

The following procedure describes how to set the SP network settings using DHCP from the Operator Panel. If your network does not use DHCP, or you want to assign a static IP address to the SP, follow the instructions in Assigning Static SP Network Settings.

1. Press any operator panel button on the server front panel (see FIGURE 2-1).

The LCD panel displays the first menu option:

Menu: Server Menu

FIGURE 2-1 Operator Panel Buttons

The three operator-panel buttons: from left to right, Back, Select and Cancel. Push Back and Select for Cancel; push Forward and Select for Enter.

2. Press the Forward button until you reach the SP menu:

Menu: SP menu

3. Press the Select button to display the SP menu options.

SP Menu: Set SP IP info?

4. Press the Select button.

The following prompt appears with the default response:

SP use DHCP? No

5. Press the Forward button to change to Yes, then press the Select button.

6. Press the Select button at the confirmation prompt.

SP use DHCP: Yes?

The server attempts to contact a DHCP server for an IP address. When the server receives a DHCP response, the LCD panel displays the DHCP-assigned SP IP addresses. The SP address is configured and the server is ready for use.

Note - Depending on your network conditions, it may take five to ten seconds for the new IP address allocated by the DHCP server to appear in the LCD panel.

7. Continue with Creating the Initial Manager Account for instructions on creating the initial manager account.

Note - A prompt appears that asks if you want to perform autoconfiguration. As an alternative to configuring an SP manually, you can run autoconfiguration, which replicates the configuration of one SP to another. Refer to the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide for instructions on autoconfiguration.

Assigning Static SP Network Settings

From the operator panel, follow these steps to set the SP network settings using a static IP address. You must specify a subnet mask and default gateway. This example uses the following sample settings:

IP Address: 10.10.30.5
Subnet Mask: 255.255.255.0
Default Gateway: 10.10.30.254

1. Press any operator panel button on the server front panel (see FIGURE 2-1).

The LCD panel displays the first menu option:

Menu: Server Menu

2. Press the Forward operator panel button until you reach the SP menu:

Menu: SP menu

3. Press the Select operator panel button to display the SP menu options.

SP Menu: Set SP IP info?

4. Press the Select operator panel button. The following prompt displays with the default response:

SP use DHCP? No

5. Press the Select operator panel button.

The LCD displays as follows:

SP IP Address: 0.0.0.0

6. With the cursor in the first field, increase or decrease the value using the Back or Forward operator panel button.

This field can hold a value between 0 and 255.

SP IP Address: 10.0.0.0

7. After reaching your desired value, press the Select operator panel button to advance the cursor to the next field.

SP IP Address: 10.0.0.0

8. Repeat Step 6 and Step 7 for each field until the desired IP address is displayed, then use the Enter button combination to save the IP Address.

The process continues to the next network setting, the Subnet Mask. The LCD displays as follows:

SP netmask: 255.255.255.0

9. Edit the subnet mask setting in the same manner as you did for the IP address. When finished, use the Enter button combination to save the subnet mask.

The process continues to the next network setting, the default gateway. The LCD displays as follows:

SP IP Gateway 10.10.30.1

10. Edit the default gateway setting in the same manner as you did for the IP address and the subnet mask. When finished, use the Enter button combination to save the default gateway.

The LCD displays the following confirmation prompt:

Use new IP data: Yes?

11. Press the Select operator panel button to use the new data, or use the Cancel button combination to disregard.

The SP address is now configured and the server is ready for use.

12. Continue with Creating the Initial Manager Account.

Creating the Initial Manager Account

After you install the server and configure the SP's network settings, you must create the initial manager account. You can then perform initial configuration of the server and create additional user accounts. Only the administrator who does the initial system configuration can create the initial manager account.

A setup account is included with each server. This setup account has no password. When you log in to the SP the first time using the setup account, you are prompted to define the initial manager account with a password and an optional public key.

Usernames and passwords are strings that consist of any alphanumeric character, underscore, hyphen, or period.

Usernames must be unique and must begin with an alphabetic character.

Passwords can contain any printable character and are case-sensitive.

A username or a password is limited to 32 characters and cannot be a null or an empty string.

There are two methods you can use to create the initial manager account:

From a command line: see Creating the Initial Account From a Command Line.

From the Systems Management (SM) console: see Creating the Initial Account From the SM Console.

Creating the Initial Account From a Command Line

1. Using an SSHv1 or SSHv2 client, connect to the IP address of the SP.

2. Authenticate as the user setup with no password required:

# ssh sp_ip_address -l setup

3. Follow the on-screen prompts to create the initial manager account.

After you create the initial manager account, the setup account is deleted and you are logged out of the server. You can then log in using the new initial manager account, from which you can create other user accounts.

Note - If you are prompted for a password, this indicates that the SP has already been secured with an account. If you do not know the management user name and password, you can reset the SP from the operator panel by navigating to the SP menu and selecting the Use defaults option. Note that all current settings for users and networks will be lost and the SP will reboot.

After you create the initial manager account, continue with Defining a Name for the Server or Server Management and Platform Software.

Creating the Initial Account From the SM Console

To create the initial manager account from the SM Console:

1. Enter the SP name or IP address as the URL or address in a browser, to enter the SM Console.

Note - When you create the initial manager account, you are prompted to accept a license agreement. After you create the initial manager account, this prompt no longer appears.

2. At the Create Initial Manager-Level User ID screen, enter a user ID for this account.

3. Enter a password for the account.

4. Re-enter the password to confirm.

5. Click the check mark button.

6. Use the SM Console to select initial configuration options.

After you create the initial manager-level user, the Initial Configuration Checklist screen displays in the SM Console. This enables you to determine the options you want for the initial setup of the SP.

The Initial Configuration Checklist is a table that lists the SM Console menu options and the commands you use to configure each option. It also includes links to the online help that provides instructions for each option.

Note - This table displays only after you create the initial manager user. Therefore, only the administrator who initially configures the account or who resets it via the operator panel can access it.

After you create the initial manager account, continue with Defining a Name for the Server or Server Management and Platform Software.

Defining a Name for the Server

If desired, you can define a name for the server that will be displayed in the operator-panel LCD when the SP is idle. After you define a name, the name and the IP address of the SP alternate every few seconds in the LCD.

Note - This is a descriptive name for the server, for your convenience only. It is not a DNS host name for the server on the network.

1. When the server is in background state, press any operator-panel button (see FIGURE 2-1).

After you press a button, the LCD panel displays the first menu option:

Menu: Server Menu

2. Press the Forward button until you reach the Panel menu:

Menu: Panel menu

3. Press the Select button to display the Panel menu options.

4. Press the Forward button until the Name for LCD menu option displays:

Panel Menu: Name for LCD?

5. Press the Select button to enable data entry.

6. Enter an alphanumeric string to display on the first line of the LCD.

You can enter letters A through Z, digits 0 through 9, hyphen and space.

a. Use the Forward and Back buttons to locate the character you wish to enter in each field.

b. Press the Select button when you locate the character you want.

c. Repeat this process until the entire name is complete.

7. Use the Enter button combination (Forward plus Select) to save your entry.

Server Management and Platform Software

This section includes descriptions of the network share volume (NSV) structure that is included with your server on CD, and a procedure for extracting and installing the software (see Installing and Mounting the NSV Software).

Although the SP functions normally without access to an external file system, a file system is required to enable several features, including event log files, software updates, diagnostics and the troubleshooting dump utility. You can configure the NSV to be shared among multiple SPs. Admin- and manager-level users can configure the external file system; however, monitor users can only view the current configuration with read-only access.

The following software components are included with your server:

Platform BIOS

SP Base Software

SP Value-Add Software

The update file for downloading Java Runtime Environment (JRE) packages

Network Share Volume, which includes diagnostics

Platform Software

Motherboard platform drivers

All of these software packages are packaged with the NSV and are installed on the file server when the external file system is installed and configured, as described in Installing and Mounting the NSV Software.

Network Share Volume Structure

TABLE 2-1 lists the the compressed packages that are included on the Sun Fire V20z and Sun Fire V40z Servers Network Share Volume CD-ROM:

TABLE 2-1 Compressed Packages on the Network Share Volume CD-ROM
File Name	File Contents
`nsv_V2_2_0_x.zip`	SP and platform diagnostics with some support for the SP software
`nsv-redhat_V2_2_0_x.zip`	Drivers for Red Hat Linux OS
`nsv-solaris_V2_2_0_x.zip`	Drivers for Solaris 9 OS and Solaris 10 OS
`nsv-suse_V2_2_0_x.zip`	Drivers for SUSE Linux OS

When extracted, the compressed packages in TABLE 2-1 populate the following directories on the NSV:

/mnt/nsv/ diags logs scripts snmp update_server sw_images (this folder appears after you extract one of the OS-specific .zip files)

TABLE 2-2 Directories on the Network Share Volume
Directory Name	Description
`diags`	Offline location of the server diagnostics.
`logs`	Offline location of the log files for the SP.
scripts	Sample scripts that can be used for scripting commands.
`snmp`	SNMP MIBS. Refer to Chapter 3 in the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide (817-5249) for details.
`update_server`	Application for updating the SP software and BIOS. Refer to to Chapter 1 in the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide (817-5249) for details.
`sw_images`	Contains a directory hierarchy of platform and SP components, including subdirectories for each version.

Installing and Mounting the NSV Software

Equipment Needed For This Procedure

Sun Fire V20z and Sun Fire V40z Servers Network Share Volume CD, which contains the NSV packages

An NFS server, to which you will copy the NSV packages from CD

Note - The NFS server can be any server that supports NFS and that is connected to the same network as the server's SP ports. The following procedure assumes that your NFS server is running Linux or UNIX. If you are using a different OS, consult the documentation for that OS for the exact commands to use.

To install and configure the NSV, follow these steps:

1. Connect the SP of the server to the same network as your NFS server.

See Cabling for the location of the SP connectors and guidelines for connecting servers to management LANs.

2. Insert the Sun Fire V20z and Sun Fire V40z Servers Network Share Volume CD into the NFS server and mount the CD.

3. Copy the folder that contains the NSV packages from the CD to the NFS server by typing the following command:

# cp -r /mnt/cdrom/<NSV_file_directory> /mnt/nsv/

4. Change to the directory on the server that now contains the compressed NSV packages and extract them by typing the following commands:

# cd /mnt/nsv/# unzip -a *.zip

Note - When unzipping a compressed file on a Linux platform, use the -a switch as shown to force text files to convert to the target operating system's appropriate end-of-line termination.

The extracted packages populate these directories:

/mnt/nsv/ diags logs snmp update_server sw_images

5. If you will be running the server diagnostics, run the following commands to create the appropriate permissions within the diags directories:

# chmod 777 /mnt/nsv/diags/NSV_version_number/scripts# chmod -R 755 /mnt/nsv/diags/NSV_version_number/mppc

6. Log in to the Sun Fire V20z or Sun Fire V40z server SP via SSH by typing the following command at the NFS server's command prompt:

# ssh -l admin_or_higher_login SSH_hostname

Note - Verify that NFS is enabled on the network before going to the next step. On systems running Linux, this must be done manually. Refer to the documentation for the version of Linux you are running for the instructions on enabling NFS.

7. Mount the NSV onto the Sun Fire V20z or Sun Fire V40z server SP by typing the following command:

# sp add mount -r NFS_server_hostname:/directory_with_NSV_files -l /mnt

Note - If you did not set up the SP on a DHCP network, you must use the
NFS_server_IP_address, rather than the NFS_server_hostname.

8. Continue with Setting up the Platform Operating System and Drivers.

Setting up the Platform Operating System and Drivers

Note - An operating system can be installed on the server without configuring the SP or the NSV. However, if you choose to skip the SP and NSV setup, you will not be able to use the remote-management capabilities of the system, or the diagnostics.

After setting up the SP and NSV software, you can install the platform operating system (OS) and drivers.

For details about installing a supported Linux OS and the required drivers, refer to the Sun Fire V20z and Sun Fire V40z Servers--Linux Operating System Installation Guide.

For Solaris OS installation, refer to the documentation that is provided with the Solaris OS software, or at the URL:

http://docs.sun.com/db/prod/solaris

For additional Solaris OS considerations specific to this server, also refer to the Sun Fire V20z and Sun Fire V40z Servers--Release Notes on the Documentation and Support Files CD, or one of the following URLs:

http://www.sun.com/products-n-solutions /hardware/docs/Servers/Workgroup_Servers/Sun_Fire_V20z/index.html