Netra SPARC T3-1BA Blade Server Product Notes |
This document contains important and late-breaking information about Oracle’s Netra SPARC T3-1BA blade server. This document includes information about upgrading to ATCA R3U3 software and firmware.
This document contains the following:
The most recent versions of the Netra SPARC T3-1BA blade server and Sun Netra CT900 server documentation are available at:
http://www.oracle.com/pls/topic/lookup?ctx=nst31ba&id=homepage http://www.oracle.com/pls/topic/lookup?ctx=ct900&id=homepage
The commands for board reset and FRU control cold reset have known issues with host power on. The host might not come up after board reset command is executed. Perform a deactivate and activate of the blade server instead of using the board reset command.
When a Netra SPARC T3-1BA blade server is booted using the CF device, hot plugging of devices into the front USB ports might not be automatically detected. (CR 7009182).
If this issue is encountered after attempting to hot plug a USB device, use either of the following workarounds:
Prior to hot plugging a USB device, use either of the following workarounds to enable USB device hot plugging:
Device name will look like /pci@___/pci@___/pci...
http://download.oracle.com/docs/cd/E19253-01/index.html
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:
When the blade is powered off to M1 state, the blade’s serial port might output extraneous characters on the console. There is no functional impact to the blade, and the characters can be ignored. The problem occurs only on some models of serial concentrator.
This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.
The following documents ship with the Netra SPARC T3-1BA blade server:
Refer to the Netra SPARC T3-1BA Blade Server Start Here for information on obtaining the rest of the Netra SPARC T3-1BA blade server documentation or go to the following web sites.
http://www.oracle.com/pls/topic/lookup?ctx=nst31ba&id=homepage http://www.oracle.com/pls/topic/lookup?ctx=ct900&id=homepage
The R3U3 release and patches provide the following enhancements:
The latest release of bcfutool and upgradefw tool introduced support for the deferred firmware activation feature on the blade server. Refer to the README file in the firmware release bundle for detailed information.
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.
This enhancement retains any custom values you configured for the following variables.
If you want to reset these variables to their default, use the Reset IPMC configuration variables command.
For detailed command information, refer to the Sun Netra CT900 Server Administration and Reference Manual.
The R3U3 release and patches provide the following new features.
Two new commands for use only with the Netra SPARC T3-1BA blade server allow users to override thermal thresholds and display current settings. The thermal trip setting determines if a blade server shuts down because maximum temperature is reached.
In extreme situations such as operating in a war zone, there may be a requirement by the user to override the maximum temperature thresholds to prevent shutdown of blade servers. Referred to as “war-zone mode,” users can override thermal trip to keep blade servers, and consequently, their systems, running, even if they reach maximum temperature thresholds.
For more information and instructions, refer to the Sun Netra CT900 Software Developer’s Guide.
Two new commands are available to set and get the management port configuration to access either the rear or front panel:
For command syntax and descriptions, refer to the Sun Netra CT900 Server Administration and Reference Manual.
Three new commands are available to set and query the management port routing configuration:
For command syntax and descriptions, refer to the Sun Netra CT900 Server Administration and Reference Manual.
The Netra SPARC T3-1BA blade server supports a low power FB-DIMM @1.55 volts, in addition to the 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 CT900 Software Developer’s Guide.
A multiplexer (MUX) controller and ShMM configuration is available for use on Netra SPARC T3-1BA 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 CT900 chassis, a complete end-to-end solution is provided. This 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 Netra SPARC T3-1BA blade server in a third-party chassis, which does not have the Sun Netra CT900 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 Blade Centric Firmware Update Tool (bcfutool) consolidates the functionality from existing utilities and provides an easy-to-use interface for upgrading the IPMC, MMC, and system firmware from the Netra SPARC T3-1BA blade server payload running Oracle Solaris OS.
This version of bcfutool introduces support for deferred firmware activation and firmware bank switching (for system firmware).
For more information, refer to the README file included in the R3U3 release package and the instructions in these Product Notes.
With the R3U3 release, a new systems firmware progress sensor (SFPS) is available. 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 CT900 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://www.oracle.com/pls/topic/lookup?ctx=nst31ba&id=homepage
http://www.oracle.com/pls/topic/lookup?ctx=ct900&id=homepage
The Netra SPARC T3-1BA blade server supports the Oracle Solaris 10 (9/10) OS and subsequent compatible versions, with supported Netra patches. The Oracle Solaris OS software can be downloaded from Oracle at:
For information on these versions of the Oracle Solaris OS, including installation, see the appropriate Oracle Solaris documentation collection at the Sun Documentation web site at:
http://www.oracle.com/technetwork/server-storage/solaris/documentation/index.html
After you download the Oracle Solaris OS, check the downloaded file to ensure that it downloaded correctly, for example:
To display current version information, preview required upgrades, and to perform an upgrade of the Sun Netra CT900 system and installed blade servers, invoke the autofwupgrade command from the ShMM. The command syntax is as follows.
autofwupgrade [-h] [ [-vp] [-q <release>] [-a <release>] -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. |
Note - The autofwupgrade tool does not support system firmware version query/upgrade of the Netra SPARC T3-1BA blade server. |
Use the following command at the cli prompt.
or use the autofwupgrade command.
Note - The showhost command works for systems and many blades; however, it does not work for the Netra SPARC T3-1BA blade server. See next section. |
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 Netra SPARC T3-1BA blade server firmware should be at the versions listed in the README.
The command syntax is as follows.
Use the bcfutool command at the Oracle 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 - R3U3 includes changes from previous releases. |
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. |
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 Netra SPARC T3-1BA blade server and Sun Netra CT900 servers, refer to the Netra SPARC T3-1BA blade server README files and Sun Netra CT900 Server Product Notes.
Be sure to follow the upgrade sequence documented in the README files.
The autofwupgrade tool upgrades the following automatically from the ShMM:
Note - To access and use the automated firmware upgrade tool, you must upgrade the ShMM firmware to the newest release 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.)
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 Netra SPARC T3-1BA blade server, refer to the README files and following instructions in this section.
Be sure to follow the upgrade sequence documented in the README files.
To Download Firmware |
1. Log in to https://support.oracle.com.
If this is your first time logging in to Oracle Support, register as a new user, following the links and instructions on the site.
3. In the Patch Search area, click on the Advanced Search link.
4. For Product select Netra SPARC T3-1BA from the pull-down menu.
5. For Release, select the newest release, unless you require an earlier release.
6. For Platform, enter or select the platform that matches your system.
7. Click on the Search button.
8. From the Patch Search Results, find the package that you want to download.
9. Select each package you want, then download it and the associated README.
You can download both the firmware package and the patches from the same search results screen.
10. 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.
11. Perform the procedures for upgrading system firmware, IPMC firmware, and MMC firmware, as applicable.
12. Apply the patches as described in Applying Patches.
To Upgrade System Firmware |
1. Update the system firmware by entering the bcfutool command as follows:
where <x_x_x_x> 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.
To Upgrade IPMC Firmware |
1. Update the IPMC firmware by entering the bcfutool command as follows:
bcfutool -c ipmc -f Netra_T3-1BA_ipmc-boot-<x.x.x>.hpm bcfutool -c ipmc -f Netra-T3-1BA_ipmc_main_<x.x.x>.hpm |
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 Oracle 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.
To Upgrade MMC Firmware |
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 Oracle 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 Oracle Support web site for the Netra SPARC T3-1BA blade server and instructions on how to apply these patches. If the Oracle 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 Oracle Solaris OS that you are using for more information on managing and applying patches. |
There are two types of patches to download: regular patches and point patches. If you specify the base Patch ID number (the first six digits) in the Search field, you see the most recent version of the patch.
Always install point patches after you have installed the regular patches.
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 Netra SPARC T3-1BA blade server.
Following are the instructions for downloading and installing the patches on a boot device.
1. If you already downloaded the patches, skip to Step 12.
2. If you need to download the patches, log in to https://support.oracle.com.
If this is your first time logging in to Oracle Support, register as a new user, following the links and instructions on the site.
4. In the Patch Search area, click on the Advanced Search link.
5. For Product select Netra SPARC T1-1BA from the pull-down menu.
6. For Release, select the newest release, unless you require an earlier release.
7. For Platform, enter or select the platform that matches your system.
8. Click on the Search button.
A list of patches with their IDs is displayed.
9. Review the Patch Search Results to find the patches that you want to download.
The mandatory Oracle Solaris 10 OS patches are listed in the following table.
10. Click on the patch ID you want to download.
Each patch ID is shown in blue text, which is a link to the download page.
11. Download each patch and associated README.
12. 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.
13. Review the patch README files for specific Install Instructions and follow those instructions.
14. To install a patch, become superuser and type the patchadd and the full path to the patch.
15. Perform a patchadd for each of the patches in the order listed in Step .
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 Netra SPARC T3-1BA Blade Server User’s Guide.
Note - Refer to the Oracle 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 Netra patches that you will apply to a Oracle Solaris 10 OS diskless service.
1. Log in to https://support.oracle.com.
If this is your first time logging in to Oracle Support, register as a new user, following the links and instructions on the site.
2. Select "Patches & Updates."
3. Locate and download the mandatory Oracle Solaris 10 OS patches listed in the following table.
4. In the "Patch Search" area, enter the patch ID, omitting the revision number (last two numbers).
If a newer revision is listed for a patch, select and download it.
6. Move the patch zip files into the patch-download-dir directory.
Where patch-download-dir is the path to the directory where the Oracle Solaris 10 OS patches are stored. The patch-download-dir directory might already contain patches that were copied during the OS installation.
7. 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.
8. Change directories to the /usr/sadm/bin directory.
9. 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 Oracle Solaris 10 OS patches are stored.
Note - Note that you must add an additional -U option when you install the last patch. |
10. Refer to the instructions in the Netra SPARC T3-1BA Blade Server User’s Guide 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 upgrade 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 Oracle Solaris from the Oracle Solaris prompt. For detailed instructions, refer to the Oracle Solaris Operating System documentation and the Netra SPARC T3-1BA Blade Server User’s Guide.
When the shutdown is completed, the ok prompt is displayed.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.