Sun Netra CP3260 Blade Server Product Notes |
The Sun Netra CP3260 Blade Server Product Notes contain important and late-breaking information about the Sun Netra CP3260 blade server. This document includes information about upgrading to ATCA R3U2.
This document contains the following:
The most recent versions of the Sun Netra CP3260 blade server and Sun Netra CT 900 server documentation are available at:
http://docs.sun.com/app/docs/prod/cp3260.brd#hic http://docs.sun.com/app/docs/prod/n900.srvr#hic
If the SB flash disk appears as “drive type unknown” with format, perform the following:
Turn off Volume Management before starting sunvts test.
Disktest/CF will be in the test menu under USB-device:
Software and firmware on the servers must be at least version ATCA R3 or newer.
Use the VTS6.4ps2 SPARC (or newer) Toolkit and Documentation.
Download and install SunVTS. For instructions, refer to the Sun Netra CP3260 User’s Guide (820-0457).
The following documents ship with the Netra CP3260 blade server:
Refer to the Sun Netra CP3260 Blade Server Getting Started Guide for information on obtaining the rest of the Netra CP3260 blade server documentation or go to the following web sites.
http://docs.sun.com/app/docs/prod/cp3260.brd#hic http://docs.sun.com/app/docs/prod/n900.srvr#hic
The R3U3 release provides the following enhancements:
IPMC configuration variables are now retained across firmware upgrades and downgrades, as long as the version being downgraded to supports this feature.
IPMC has a group of parameters that are stored in SEEPROM (NV Storage). All variables are part of one data structure. Each of these variables performs a function and can be set or read via commands. These variables are stored across IPMC resets. However, previously, these variables were reset to default values when new or upgraded firmware was installed.
This enhancement retains any custom values you configured for the following variables.
If you want to reset these variables to their default, use the new Reset IPMC configuration variables command.
For detailed command information, refer to the Sun Netra CT 900 Server Administration and Reference Manual (819-1177).
Support was added for the Linux BIOS Update Utility. This utility is a stand-alone application for Linux that incorporates the BIOS payload and application required to perform a BIOS update. The utility uses the /dev/mem interface to access the BIOS.
For this application to work on a Linux system:
The CP32x0 BIOS consists of three regions:
1. Boot BIOS Region, which contains the lowest level system initialization.
2. NVRAM Region, which stores system specific configuration data.
3. Main BIOS Region, which includes system configuration code.
The utility can be used to update any or all of these regions. Typically, only the main BIOS region needs to be updated, but in some cases it might be necessary to update the Boot BIOS region
For detailed instructions, refer to the README file.
This release provides the following new features.
The Sun Netra CP3260 blade server now supports a low power FB-DIMM @1.55 volts, in addition to the currently supported FB-DIMM@1.8 volts.
The FB-DIMM sensor accommodates the new voltage range with the following thresholds:
Note - These critical and non recoverable voltage ranges are threshold ranges. |
For information about sensors, refer to the Sun Netra CT 900 Software Developer’s Guide (819-1175).
A new multiplexer (MUX) controller and ShMM configuration is available for use on Sun Netra CP3260 blade server to multiplex 10GbE network interface unit (NIU) ports to Zone 2 (backplane) and/or to Zone 3 (ARTM). You can configure both ports independently.
Note - The host must be configured to match the MUX configuration. |
For customers using the blade servers in a Sun Netra CT 900 chassis, a complete end-to-end solution is provided. This new feature is implemented through the ShMM firmware and new IPMI commands on the IPMC. These commands extend MUX configuration access to the management software so that during blade server hot-swaps, the MUX configuration is persistent across blade server activations and deactivations.
Customers who use Sun Netra CP3260 blade server in a third-party chassis, which does not have the Sun Netra CT 900 chassis ShMM management software implemented, can save MUX configurations in a configuration file or in a persistent storage managed by system management software. When a system management software detects blade server activation, it sends the command to set MUX to the programmed state. Because management software sends the command during every blade server activation, the configuration is persistent across blade server deactivation and activation.
Refer to the following documentation:
The R3U2 release introduces the Blade Centric Firmware Update Tool (bcfutool), which provides support for customers who use Sun Netra CP3260 blade servers in a third party ATCA chassis, instead of a Sun Netra CT 900 chassis.
This tool consolidates the functionality from existing utilities and provides an easy-to-use interface for upgrading the IPMC, MMC, and system firmware from the Sun Netra CP3260 blade server payload running Solaris OS.
For more information, refer to the README file included in the R3U2 release package and the instructions in these Product Notes.
A new systems firmware progress sensor (SFPS) is available on the Sun Netra CP3260 blade server. The purpose of the sensor is to model the firmware running on the payload and provide various states to the external management software (ShMM on Sun Netra CT 900 servers). This occurs via a standard IPMI event mechanism.
The firmware states are Progress, Hang, and Error, with various substates. The sensor generates an IPMI event message for each state. You can verify the messages by using clia sel command on the ShMM, through HPI event and SNMP traps for each state of a sensor event.
Refer to the following documentation:
http://docs.sun.com/app/docs/prod/cp3260.brd
http://docs.sun.com/app/docs/prod/n900.srvr#hic
The Sun Netra CP3260 blade server supports the Solaris 10 (8/07) OS and subsequent compatible versions, with supported Sun Netra patches. The Solaris OS software can be downloaded from the Sun download center at:
For information on these versions of the Solaris OS, including installation, see the appropriate Solaris Documentation Collection at the Sun Documentation web site at:
http://docs.sun.com/app/docs/prod/solaris
After you download the Solaris OS, check the downloaded file to ensure that it downloaded correctly.
To display current version information, preview required upgrades, and to perform an upgrade of the Sun Netra CT 900 system and installed blade servers, invoke the autofwupgrade command from the ShMM. The command syntax is as follows.
autofwupgrade [-h] [ [-vp] -f <FTP-server-IP-address>:<release-archive-root-dir>[:<user-name>:<password>] [-s <board-slot-number>] [-t board-type] ] |
Tip - We recommend that you use the -p option to preview the required updates before performing the upgrade. |
|
Use the following command at the cli prompt.
or use the autofwupgrade command.
For users who do not have access to the ShMM or who want manual control of the FW upgrade process, use the bcfutool upgrade tool instead of the ShMM autofwupgrade. Refer to the README and these Product Notes for information and instructions.
The Sun Netra CP3260 blade server firmware should be at the versions listed in the README.
The command syntax is as follows.
|
Use the bcfutool command at the Solaris prompt.
This release contains the most up-to-date features, enhancements, and bug fixes. Using an earlier release could limit your use of features and enhancements, and could affect your blade servers and systems with known issues.
Note - R3U2 includes changes from previous releases. |
A single bundled software and firmware package is available to apply the applicable portions to your chassis and blade servers. To download the release package and upgrade your Sun Netra CP3260 blade server and Sun Netra CT 900 servers, refer to the Sun Netra CP3260 blade server README files and Sun Netra CT 900 Server Product Notes.
Be sure to follow the upgrade sequence documented in the README files.
This tool upgrades the following automatically from the ShMM:
You can use this tool to upgrade firmware from R3 and R3HW1 releases.
Note - To access and use the automated firmware upgrade tool, you must upgrade the ShMM firmware to R3U2 before running the automated upgrade tool. |
The following firmware are not upgraded by the autofwupgrade tool and must be upgraded manually. (For upgrade instructions, refer to README files included in the release download package.)
Although this tool does not currently support downgrading automatically to back out of an upgrade, future releases might support downgrading back to R3U2.
For detailed instructions on how to use the firmware upgrade tool and how to roll back an upgrade, refer to the README included with the R3U2 package.
A single bundled software and firmware package is available to apply the applicable portions to your blade servers. To download the release package and upgrade your Sun Netra CP3260 blade servers, refer to the Sun Netra CP3260 blade server README files and these Product Notes.
This tool upgrades the following automatically:
A typical firmware update takes about seven minutes, and during this time the service processor will be fully operational because it is running an earlier image.
The following firmware are not upgraded by the bcfutool tool and must be upgraded manually. (For upgrade instructions, refer to README files included in the release download package.)
Although this tool does not currently support downgrading automatically to back out of an upgrade, future releases might support downgrading back to R3U2. For detailed instructions on how to roll back an upgrade, refer to the README included with the R3U2 package.
Be sure to follow the upgrade sequence documented in the README file.
![]() |
Caution - Asynchronous events such as power outage, latch opening, or blade extraction during a firmware upgrade might corrupt the blade server firmware such that the blade will not be able to boot, and you will not be able to retry the upgrade. Be careful not to cause any these events during upgrades. For more information, see Troubleshooting Upgrades. |
|
1. Download the most recent package listed at the SDLC site:
Find the package for the release you want to download.
2. After the compressed package is downloaded, expand the files by entering the following commands.
where Rx_Ux_ is the release’s version and update number.
3. Check the current firmware versions on your blade server, using the bcfutool -g command.
All firmware versions are listed in the results from this command. Individual commands for checking system, IPMC, and MMC firmware are also available.
4. Perform the procedures for upgrading system firmware, IPMC firmware, and MMC firmware, as applicable.
|
1. Update the system firmware by entering the bcfutool command as follows:
where <x_x_x_g> is the newest system firmware version that you are replacing the earlier version with.
2. Enter yes or y to continue.
Entering yes will continue the process of upgrading the firmware.
3. When the upgrade is complete, check the system firmware version.
If the upgrade was successful, the newest version will be returned after you enter the command.
If you encountered problems during the upgrade, see Troubleshooting Upgrades.
|
1. Update the IPMC firmware by entering the bcfutool command as follows:
where <x.x.x> is the newest IPMC boot and main firmware versions that you are replacing the earlier versions with.
2. Enter yes or y to continue.
Entering yes will continue the process of upgrading the firmware.
When the service processor has been successfully updated, the user will be presented with the Solaris login prompt.
3. When the upgrade is complete, check the IPMC firmware version.
If the upgrade was successful, the newest versions will be returned after you enter the command.
If you encountered problems during the upgrade, see Troubleshooting Upgrades.
|
1. Update the MMC firmware by entering the bcfutool command as follows:
where <x.x.x> is the newest MMC firmware version that you are replacing the earlier version with.
2. Enter yes or y to continue.
Entering yes will continue the process of upgrading the firmware.
When the service processor has been successfully updated, the user will be presented with the Solaris login prompt.
3. When the upgrade is complete, check the MMC firmware version.
If the upgrade was successful, the newest versions will be returned after you enter the command.
If you encountered problems during the upgrade, see Troubleshooting Upgrades.
This section provides information on the Sun Netra patches that you must download from the SunSolveSM web site for the Sun Netra CP3260 blade server and instructions on how to apply these patches. If the Solaris OS was pre-installed on your system, these patches might already be installed; verify that they are present.
Note - Refer to the System Administration Guide: Basic Administration documentation for the Solaris OS that you are using for more information on managing and applying patches. |
There are two types of patches to download:
Before you start downloading, identify or create a directory on your system for receiving the downloaded patches. This directory will be referred to as the patch-download-dir in the following procedures.
There are two procedures for downloading and installing patches for the Sun Netra CP3260 blade server.
Following are the instructions for downloading and installing the patches on a boot device.
1. Go to SunSolve web site and accept the onscreen agreement.
2. Locate and download the mandatory Solaris 10 (08/07) OS patches listed in TABLE 1.
3. Use the unzip command on the patches that you downloaded to extract the contents of the downloaded zip files.
Refer to the unzip(1) man page for additional information.
4. Review the patch README files for specific Install Instructions and follow those instructions.
5. To install a patch, become superuser and type the patchadd and the full path to the patch.
6. Perform a patchadd for each of the patches in the order listed in Step 2.
Refer to the patchadd(1M) man page for instructions on using the command.
These patches are required for the diskless client boot server installation process documented in the Sun Netra CP3260 Blade Server User’s Guide (820-0457).
Note - Refer to the Solaris 10 OS System Administration Guide: Basic Administration documentation for more information on managing diskless services. |
Following are the instructions for downloading and installing the Sun Netra patches that are being applied to a Solaris 10 OS diskless service.
1. If you have not already done so, go to SunSolve web site and download the following mandatory patches listed in TABLE 2.
2. Move the patch zip files into the patch-download-dir directory.
Where patch-download-dir is the path to the directory where the Solaris 10 OS patches are stored. The patch-download-dir directory might already contain patches that were copied during the OS installation.
3. Use the unzip command on all of the patches that you downloaded to extract the contents of the downloaded zip files.
Refer to the unzip(1) man page for instructions on using the command.
4. Change directories to the /usr/sadm/bin directory.
5. Install the required patches to the diskless service.
Use the smosservice patch command to install the patches to the installation image.
Install the software patches on the server in the order shown, where root-password is the root password of the server and patch-download-dir is the path to the directory where the Solaris 10 OS patches are stored.
Note - Note that you must add an additional -U option when you install the last patch. |
6. Refer to the instructions in the Sun Netra CP3260 Blade Server User’s Guide (820-0457) to complete the installation procedures for diskless clients.
To prevent issues during bcfutool command upgrades, review the following information.
To avoid firmware corruption, prevent the following events from occurring while the firmware is being upgraded:
A recommendation for avoiding failures during ugrade vulnerability periods is to monitor the upgrade manually or by using a script.
If you encounter any issues during an upgrade when using the bcfutool command, see the following tables for information helpful when troubleshooting the issue.
To remove and replace a blade server safely, manually shut down Solaris from the Solaris prompt. For detailed instructions, refer to the Solaris Operating System documentation and the Sun Netra CP3260 Blade Server User’s Guide (820-0457).
When the shutdown is completed, the ok prompt is displayed.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.