|C H A P T E R 1|
Overview and Preparation
This chapter provides an overview of the ELOM-to-ILOM migration process and details the preparatory steps that you need to perform for a successful upgrade of your Sun Fire X4150 and X4450 servers and Sun Blade X6250 and X6450 server modules. While the migration procedures are similar for all four servers, some differences exist, particularly between the Sun Fire and Sun Blade server groups. The differences are noted, and when necessary, the procedures are separated.
The information and procedures in this chapter pertain to both Sun Fire X4150 and X4450 servers and Sun Blade X6250 and X6450 server modules.
The following is a list of questions about the ELOM-to-ILOM migration.
Why should I migrate my servers to ILOM?
Sun has consolidated and focused its resources on supplying a single server and server module management utility that best meets the needs of our customers. Sun is committed to supporting and developing ILOM as the server management utility of choice.
Does this mean Sun no longer supports ELOM?
Sun continues to support ELOM. However, Sun no longer provides updates to ELOM. Additionally, future updates to your server or server module hardware might depend on ILOM compatibility for functionality.
Does upgrading to ILOM involve changing my server’s hardware?
Upgrading to ILOM is a firmware-only update and does not require changing or modifying your server’s hardware.
When should I migrate my system?
Sun recommends that you migrate your servers to ILOM as soon as possible.
Can I upgrade multiple systems using scripts?
Yes. See Migrating to ILOM Using the Command-Line Interface (CLI) and Upgrade Scripts.
What is the minimum version of ELOM that I should have installed before beginning the migration process?
It is recommended that you upgrade your server or server module to the latest available version of ELOM before beginning this process.
To which version of ILOM will I migrate my servers?
You need to upgrade your servers to a temporary (transitional) version of ELOM first and then migrate to ILOM. When the migration process is finished, your server or server module will have ILOM version 184.108.40.206.
Can I use the transitional version of ELOM without migrating to ILOM?
No. The transitional ELOM version is not supported for normal use. It should only be used when migrating to ILOM.
How to do I migrate my servers from ELOM to ILOM?
See The Migration Process.
What if I do not want to migrate to ILOM right now?
See Choosing Not to Migrate From ELOM to ILOM.
ILOM includes the following features that ELOM does not:
For more information about ILOM features and capabilities, go to:
Sun recommends that you migrate your servers to ILOM as soon as possible. However, you might find it more convenient to downgrade your ILOM-based servers to ELOM and perform the ELOM-to-ILOM migration at a later date. For information about downgrading a server or server module from ILOM to ELOM, see Chapter 6.
This section provides an overview of the ELOM-to-ILOM migration process and details the steps that you need to perform for a successful upgrade of your server.
Upgrading from ELOM to ILOM is very similar to upgrading to a newer version of firmware. You can use the same interfaces, and the process is functionally the same. For example, you can use the web GUI or the CLI to upgrade your servers using a combined firmware image file that upgrades both the BIOS and service processor (SP) at the same time. Additionally, if you would like to upgrade multiple servers, you can use the CLI with scripting languages to create scripts that will perform the upgrade.
When upgrading from ELOM to ILOM, you can use the following methods:
The migration process requires that you perform at least two upgrades. First, you must upgrade your server from the latest version (recommended) of ELOM to a temporary or transitional version of ELOM. Then you must upgrade from the transitional version of ELOM to the final version of ILOM. FIGURE 1 shows the basic migration process.
FIGURE 1 The Basic Migration Process
|Note - The transitional version of ELOM is not supported for normal system management. The transitional version of ELOM should only be used in the process of migrating to ILOM.|
You need to perform several preparatory steps before you upgrade your servers to the transitional version of ELOM, including reviewing the Product Notes, accessing the BIOS Setup Utility to record custom settings, and downloading the necessary firmware files. The Migration Task Table lists all the steps, tasks, and relevant sections.
|Caution - The procedures in this document require multiple power cycles, resulting in SP reboots. TheSP might lose its Gateway address after a power cycle. Before starting the migration process power cycle the server or server module and verify that your SP’s Gateway address is retained. If the address is not retained, you must set the Gateway address using the CLI after each power cycle. For more information, see the Product Notesfor your server.|
The following table lists the steps and relevant sections and procedures:
This section describes how to access your server’s documentation collection so that you can review the Product Notes and obtain the latest version of ELOM and ILOM documents. The Product Notes document contains the most up-to-date information about your server, including Tools and Drivers CD version information and issues related to hardware, software, the BIOS, and the SP.
Additionally, ELOM and ILOM documentation is available with your server’s document collection. Because of the differences between the versions of ELOM, it is recommended that you use your server’s Embedded Lights Out Manager Administration Guide as a reference when performing the steps in the upcoming procedures.
Use the following procedure to access the Product Notes and determine:
1. Open your browser and go to one of the following:
2. Click to expand the documentation collection for your server or server module.
3. Choose to view or download the Product Notes.
4. Review the document for Tools and Drivers CD version information, ELOM-to-ILOM migration-related information, and ILOM-specific information and issues.
5. Download the ELOM and ILOM documentation for your server.
The web GUI screens and CLI commands and namespaces differ between versions of ELOM. Therefore, the commands and references in the procedures in this document might not be the same for your server. Use the Embedded Lights Out Manager Administration Guide for your server or server module as a reference when performing the steps in the upcoming procedures.
The migration process does not preserve the BIOS settings. If you customized (changed) the BIOS settings from the default value, you might need to access the BIOS Setup Utility, review the settings, and, if necessary, record these values so that you can enter them again at the end of the migration process.
You need the following:
1. Set up your server or server module to respond to POST and boot messages.
Use the serial terminal or computer running terminal-emulation software. For information about how to set up your server or server module to respond to POST and boot messages, using a keyboard, video, and mouse, see the Installation Guide or the Embedded Lights Out Manager Administration Guide for your server.
2. Reboot the server and watch the screen for the BIOS prompt.
A prompt appears requesting you to press F2 to enter the BIOS Setup Utility.
3. When prompted, press F2 to enter the BIOS Setup Utility.
The BIOS Setup Utility main screen appears.
4. Use the arrow keys to navigate the BIOS Setup Utility menus and view the BIOS settings.
For a description of the BIOS screens, see the Service Manual.
5. Step through each menu and record the customized (non-default) server or site-specific settings.
6. To exit the BIOS Setup Utility press the Esc key (or the F10 key).
The server boots.
The procedures in this section require SP reboots. After a reboot, the SP might lose its Gateway address. Before starting the migration process record the Gateway address, and power cycle the server or server module and verify that your SP Gateway address is retained. If the address is not retained, you need set the Gateway address using the CLI after each power cycle.
1. Start your browser, and type the IP address of the server’s SP:
where xxx.xxx.xxx.xxx is the IP address of the SP.
The ELOM web GUI login screen appears.
2. Log in as root or as an account with administrator privileges.
The ELOM web GUI main screen appears.
3. Click the Configuration tab.
The Configuration submenu screen appears.
4. Click the Network tab and record the Gateway IP address in the table below:
5. To exit the ELOM web GUI, click log out.
1. Log in to the CLI.
For CLI access options and login instructions, see the Embedded Lights Out Manager Administration Guide for your server.
The CLI prompt appears:
|Note - The CLI commands, syntax, and namespaces in this section might be different from the commands, syntax, and namespaces used for your server; see the Embedded Lights Out Manager Administration Guide for your server or server module for the appropriate commands, syntax, and namespaces.|
2. Navigate to the network directory, and enter the show command. For example:
-> cd /SP/network
The network settings appear.
3. Record the Gateway IP address in the table below.
4. To exit the CLI, use the exit command:
To migrate your servers to ILOM, you need to download and copy the necessary firmware files. The files are available online at the product’s Sun download site. You can download the appropriate Tools and Drivers CD ISO image, or you can download the files as a .zip file.
|Note - The instructions in this manual assume that you are working from either the mounted ISO image file or a physical CD.|
1. Start your browser and go to the Sun product page for your server:
2. Do one of the following to navigate to the Download link for your server or server module:
a. From the product page, click the Support tab and scroll down to the ELOM-to-ILOM transitional update section.
b. Under the Downloads heading, click Latest Drivers and Firmware.
The download page for your server or server module appears.
c. To access the relevant files for your server, locate the version listed below and click Download.
d. Agree to terms and login to the download page.
e. At the download page, do one of the following:
|Note - The procedures in this manual assume that you are working from a CD or mounted ISO image.|
f. Proceed to Step 3.
a. From the downloads list, locate the latest version of the Tools and Drivers CD for your server.
|Note - Sun recommends that you always update your server to the latest version of firmware.|
b. Click Download.
c. Agree to terms and login to the download page.
d. Download the latest Tools and Drivers CD ISO image file.
e. Burn a CD of the file.
f. Proceed to Step 3.
3. Copy the transitional ELOM firmware file from the Tools and Drivers CD (or copy the extracted file) to a device that is accessible to your server:
|Tip - If you are using the CLI to perform the upgrade, copy the files to your TFTP server.|
The directory structure and file naming convention varies according to the server:
4. Copy the combined ILOM firmware image file from the Tools and Drivers CD (or copy the extracted file) to a device that is accessible to your server:
The combined ILOM firmware image file is a .bin file. The directory structure and file naming convention varies according to the server:
You can choose to preserve ELOM configuration settings for the ELOM-to-ILOM migration process. If you want to preserve ELOM configuration settings when migrating from ELOM to ILOM, then you must select to preserve the settings when upgrading to the transitional version of ELOM, and again when upgrading to ILOM. Otherwise, all ELOM configuration settings are lost. However, because of differences between ELOM and ILOM, some ELOM features are not supported by ILOM, and therefore, not retained.
The following is a list of the unsupported configuration settings that are not retained during the migration process:
The following is a list of the configuration settings that are retained during the migration process:
When migrating to ILOM, ELOM user accounts with user and callback privilege settings are not retained. If you would like to retain these user accounts, you can change the privilege settings in ELOM to either operator or administrator before you perform the upgrade. However, changing privilege settings for user accounts might present a security risk.
For more information about how to manage user accounts and upgrade (change) user account privileges, see the Embedded Lights Out Manager Administration Guide for your server.
You can use upgrade scripts to perform the migration process. Using scripts enables you to upgrade multiple servers to ILOM consecutively. Upgrade scripts are located on the Tools and Drivers CD:
The Sun Fire X4150 and X4450 example script is a working script that you can use as a template for performing multiple server upgrades. The script was developed from information in this document. For more information about the example script, see the readme.txt file in the same directory.