Sun Server X4-8
 
Oracle Server X5-8
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
 

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: This is a FRU

Applies to:

Goal

How to Replace a Sun Server X4-8, Oracle Server X5-8 Front Indicator Module.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?:
Sun Server X4-8, Oracle Server X5-8 Training

TIME ESTIMATE: 30 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: A Sun Server X4-8, Oracle Server X5-8 Front Indicator Module needs replacement

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

This is a cold-service component. Disconnect the AC power cables from the server before performing this procedure.

WHAT ACTIONS ARE REQUIRED?:

Reference Doc:
Sun Server X4-8 Service Manual
http://docs.oracle.com/cd/E40591_01/html/E40317/index.html

Oracle Server X5-8 Service Manual
http://docs.oracle.com/cd/E56301_01/html/E56311/index.html

Sun Server X4-8 component designations and locations
http://docs.oracle.com/cd/E40591_01/html/E40317/gnsak.html#scrolltoc


How to Remove the Front Indicator Module (FIM)

1.Prepare the server for cold service.  Shutdown OS and power off server.

1.1. Log into the ILOM and check the TLI container values and sync them if needed.  The server supports Top Level Identifier (TLI) and stores the TLI records in the midplane (MIDPLANE) FRUID container, called Primary, the Front Indicator Module (FIM), called Backup1, and the SMOD (SMOD/MB) board, called Backup2.

1. To avoid mismatched TLI values causing a failure after a FIM replacement the fruid data should be confirmed to have matching data in at least the Primary (MIDPLANE) and the Backup2 (SMOD) containers so that the FIM will have it's container updated automatically after replacement. Go into restricted mode and use the showpsnc command to check this.  
   -> set SESSION mode=restricted
   
   WARNING: The "Restricted Shell" account is provided solely
   to allow Services to perform diagnostic tasks.
   
   [(restricted_shell) x4-8-example-sp:~]# showpsnc
   Primary: fruid:///SYS/MIDPLANE
   Backup 1: fruid:///SYS/FIM
   Backup 2: fruid:///SYS/SMOD/MB
   
   Element           | Primary           | Backup1           | Backup2
   ------------------+-------------------+-------------------+-------------------
   PPN                 X4-8P1.L+NPAP1+1    X4-8P1.L+NPAP1+1    X4-8P1.L+NPAP1+1
   PSN                 1421NM8004          1421NM8004          1421NM8004
   Product Name        SUN SERVER X4-8     SUN SERVER X4-8     SUN SERVER X4-8 
   [(restricted_shell) x4-8-example-sp:~]# exit
    
2. The above example shows a system with all three containers properly in sync. If the output from the system does not show all of the containers with matching values then you should reset the SP and then re-check the values again. An ILOM reset will attempt to auto-populate the matching values if one container is out of sync.  
   -> reset /SP
   Are you sure you want to reset /SP (y/n)? y
   Performing reset on /SP
    
3. After an ILOM reset if the Primary and Backup2 containers match then proceed with the following steps to replace the FIM. If these two containers do not match then DO NOT proceed with the replacement yet.
4. If the containers do not match you will need to use the copypsnc command from service or escalation mode to copy the data from the good container so that the Primary and Backup2 containers match (Backup1 is the FIM and we are about to replace this so it is not as important at this step). If you are unfamiliar with this process and require assistance please reference the steps for using copypsnc to fix the serial number detailed in the "How to update product serial number on systems which implement TLI functionality (Doc ID 1280913.1)" and contact the TSC if needed.
5. How to access service mode and escalation mode on ILOM 3.x and later platforms (Doc ID 1019946.1)
6. After the TLI data in the Primary and Backup2 containers have been confirmed to match proceed with the following steps.

2.Disconnect the AC power cables from the power supplies.
3.Remove the topmost power supply (PSU3) and place it on an anti-static mat.
4.To unlock the FIM, reach into the vacant power supply slot, locate the release latch on the underside of the FIM, and push the latch upward.
5.To remove the FIM, press and hold the release latch and slide the FIM completely out of it's slot.

6.Place the removed FIM on an anti-static mat.


How to Install the Front Indicator Module (FIM)

1.Position the connector end of the FIM at the opening of the slot.  Ensure that the open side (internal ribbon cable visible) of the FIM is facing upward.
2.To install the FIM, slide it into the slot until it locks and is flush with the front of the server.  This locking action is accompanied by a click sound.
3.Install the power supply (PSU3).
4.Verify that the Power OK indicator on the PSU indicator panel turns on steady after power is restored to the server and the server is in full power mode.

5. After adding or replacing a component in your server, you can initiate a backup of the latest TLI record information in the MIDPLANE FRUID Primary container to Backup1/Backup2 on the FIM or SMOD containers using this procedure.

    A. Enter Service mode.
How to access service mode and escalation mode on ILOM 3.x and later platforms (Doc ID 1019946.1)

    B. To backup the Primary container to the Backup1 container, enter the following command:

    C. Verify the TLI fruid data is updated on the new FIM, as the FIM is the Backup1 device.  The TLI fruid data should update automatically if the Primary and Backup1 devices and data are valid.  If it doesn't use (Doc ID 1280913.1) to update the TLI fruid data manually. 

WHAT ACTIONS ARE REQUIRED TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?:

Power on & boot up system and verify full functionality

How to verify the FIM is working properly.

When the server is powered on the LEDs will flash and show status of the server as it goes through POST/BIOS boot process, and finally boots the OS.  The LED status should be correct if the FIM is working properly.

This solution has no attachment