| Asset ID: |
1-71-1401598.1 |
| Update Date: | 2012-09-13 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1401598.1
:
How to replace a Virtualized Multi-Fabric 10GbE NEM (Network Express Module):ATR:1401598.1:3
| Related Items |
- Sun Blade 6000 System
- Sun Blade 6048 System
- Sun Netra 6000 System
|
| Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
|
In this Document
Applies to:
Sun Blade 6000 System - Version Not Applicable and later
Sun Blade 6048 System - Version Not Applicable and later
Sun Netra 6000 System - Version Not Applicable and later
Information in this document applies to any platform.
Goal
How to replace a Virtualized Multi-Fabric 10GbE NEM (Network Express Module)
Fix
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE ENGINEER NEED:(IS A SITE ENGINEER AVAILABLE?):
Blade 6000 Chassis, NEM
TIME ESTIMATE: 45 minutes
TASK COMPLEXITY: 3
FIELD ENGINEER INSTRUCTIONS
PROBLEM OVERVIEW: How to replace an Virtualized Multi-Fabric 10GbE Network Express Module Card
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? : Schedule maintenance window to power off the Blade 6000 chassis with customer's agreement
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
-----------------------------------------------
This procedure is NOT for Virtualized Multi-Fabric 10GbE M2 NEMs. The procedure for Virtualized Multi-Fabric 10GbE M2 NEMs is available in the document:
How to replace a Virtualized Multi-Fabric 10GbE M2 NEM (Network Express Module):ATR:1408733.1:3 (Doc ID 1408733.1)
This procedure only describes a NEM replacement, if you plan to remove it from the chassis refer to the section "Removing a NEM" from the Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module Documentation
1. Identify the NEM model
Hydra = Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module
Hydra2 = Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module
Verify the NEM model using the CMM ILOM Web Interface
- In a web browser, enter the IP address of the CMM
- Select CMM from the CMM ILOM left side menu
- Select Components -> /CH/NEM0
- Select Components -> /CH/NEM1
Verify the NEM model using the CMM ILOM CLI
- Connect to the ILOM using using a terminal emulator from a terminal or PC running directly to the CMM serial port on your chassis
- or connect to the chassis Ethernet network management port using a secure shell (SSH)
- Execute one the following commands depending on which NEM requires maintenance:
-> show /CH/NEM0
-> show /CH/NEM1
Example:
-> show /CH/NEM0
Targets:
SEEPROM
SP
Properties:
type = Network Express Module
fru_name = SUN BLADE 6000 10GBE Hydra NEM
fru_part_number = 501-7935-02
fru_serial_number = 0000000-7001C003K
Commands:
cd
show
Refer to the Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module User's Guide for using Integrated Lights Out Manager (ILOM) with the Virtualized NEM:
http://docs.oracle.com/cd/E19677-01/
2. CAUTION
- You must power off the chassis before replacing an Hydra NEM.
- The server modules must be informed if you are replacing a non-redundant NEM.
- If you are replacing a functional SAS-NEM (for example replacing a Multi-Fabric NEM with a 10GbE Virtualized Multi-Fabric NEM), make sure that multipathing at the OS level is enabled on all active server blades in the chassis before you remove the existing NEM. This ensures that the primary path to disks is not lost, which can cause an OS panic. For servers running Windows 2003, which does not support multipathing, shut down IO to all disks on the disk module that are not in hardware RAID volumes.
3. Replacement procedure
1. Power off the chassis.
2. In the rear of the chassis, locate the NEM that you want to remove.
3. Label the cables so that you can install them in the same location, then remove all cables from the NEM.
4. Press together and hold the buttons on both the right and left ejector levers.
5. To unlatch the NEM from the chassis, open the ejector levers by extending them outward.
6. Holding the open ejector levers, pull the NEM toward you until you can pull the rest of the module out by hand.
Support the weight of the NEM with one hand at the bottom of the NEM.
7. Determine if the following are present in the chassis:
A server blade that is running CAM or a CAM agent.
A server blade that uses an LSI host bus adapter.
If both of the above conditions are true, continue with Step 10.
If either one of the above conditions is not true, continue to Step 13.
8. Power on the chassis.
9. Follow the procedure below to clear the LSI host bus adapter's non-present persistence mappings
on all server blades in the chassis that meet both of these requirements listed in Step 7.
- Log in to your server as root.
- Change to the directory that contains the appropriate version of lsiutil for your application. For example:
# cd LSIUtilKit1.60/Linux
- Enter the application name in the appropriate context. For example:
# ./lsiutil
- Type 1 and press Enter to display the main menu.
- Type 15 and press Enter to display the Persistence menu.
- Type 11 (Clear all non-present persistence mappings) and press Enter.
- Type and enter 0 three times to exit the lsiutil application.
10. Power off the chassis.
11. Insert the new NEM into the chassis.
12. Reconnect all the cables in their original locations.
13. Power on the chassis.
14. Execute the procedure below to save a Snapshot of the Host Bus Adapter Persistence Mappings
on all server blades in the chassis that meet all three of these requirements:
o The server blade is running CAM or a CAM agent.
o The server blade uses an LSI host bus adapter.
o The server blade is running the Solaris OS.
- Log in to your server as root.
- Change to the directory that contains the appropriate version of lsiutil for your OS. For example:
# cd LSIUtilKit1.60/Linux
- Enter the application name in the appropriate context. For example:
# ./lsiutil
- Type 1 and press Enter to display the main menu.
- Type 15 and press Enter to display the Persistence menu.
- Type 7 and press Enter.
- Enter a file name. For example, HBA33_persistence_file. The file is saved to the current directory. You get confirmation of this with a statement of the number of persistent entries saved.
- Type and Enter 0 three times to exit the lsiutil application.
Caution - Note that you must save the persistence mappings snapshot to external media as you will not be able to reinstall it from a local disk.
For more information refer to the Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module Documentation
-----------------------------------------------
4. REFERENCE INFORMATION
References
@<NOTE:1408733.1> - How to replace a Virtualized Multi-Fabric 10GbE Network Express Module M2 NEM (Network Express Module):ATR:1408733.1:3
<NOTE:1397771.1> - Virtualized Multi-Fabric 10GbE Network Express Module Product Page
Attachments
This solution has no attachment
