Pass-Through NEMs not Visible in CMM due to Incorrect Fruid Data

Asset ID:	1-73-1156243.1
Update Date:	2011-05-20
Keywords:

Solution Type FAB (standard) Sure

Solution 1156243.1 : Pass-Through NEMs not Visible in CMM due to Incorrect Fruid Data

Applies to:

Sun Netra 6000 System - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Sun Blade 6000 System - Version: Not Applicable to Not Applicable [Release: N/A to N/A]
Information in this document applies to any platform.

_________

Affected Parts: (FRU/CRU Part Number / Description)

371-1451 - 10-Port Gigabit Ethernet Network Express Module (X4250A)

Symptoms

You will not see NEM type and fruid information in the CMM BUI component screens if you attempt to view fruid data from CMM CLI commands. For example:

    show / -l all:

    /CH/NEM1
    Targets:
    PRSNT
    STATE

    Properties:
    type = Network Express Module
    ipmi_name = NEM1

Example of what a programmed NEM looks like:

    /CH/NEM0
    Targets:
    PRSNT

    Properties:
    type = Network Express Module
    ipmi_name = NEM0
    fru_name = ASSY,BD,NEM,6000
    fru_part_number = 371-1451-04
    fru_serial_number = 0000000-0828YF1287.

Power monitoring on the CMM may show 0 Watts as a value because CMM doesn't know what kind of NEM is installed without fruid data:

    /CMM/powermgmt/advanced/22

    Targets:

    Properties:
    name = NEM1 Allocated Power
    unit = Watts
    value = 0

Impact

The missing fruid data does not cause any operating issues as far as blades having network connectivity through the Pass-Through NEMs. What this issue does cause is difficulty identifying what NEMs are installed in a given Sun Blade 6000 chassis and NEM fru monitoring issues.

Changes

Contributing Factors

Any Pass-Through NEM 371-1451-04 shipped between May 6th 2009 and Jan 4th 2010 could have missing fruid data. There are 895 affected NEMs between this time period.

How to identify affected parts:

If you have 371-1451-04 Pass-Through NEMs that are not showing up in CMM BUI and or ipmitool fru outputs then you are affected with this issue.

    ipmitool -H <ipaddressofCMM> -U root fru

Cause

Root Cause

The cause of the described issue was due to the elimination of the testing step in the FRU area which also eliminated the FRU programming step.

This issue has been corrected in manufacturing since Jan 4th 2010.

Solution

Workaround

No workaround available - see Resolution section.

Resolution

The final resolution to this issue is to program the fruid with a generic all zeros serial number fruid, then program the specific serial number of the NEM label into the fruid.

Login with sunservice, which depending on ILOM version will need to be enabled.
Copy the generic .bin file to the CMM using scp.
Once copied, program the generic fruid into the NEM.
Once programmed with the generic fruid, proceed with programming the specific serial number off of the NEM from the label above the handle.
Once completed reboot the CMM.

Attached is a .pdf doc with the detailed directions. The generic .bin file needed to program the fruid is available at the following URL (the files are attached to issue #19):

http://panacea.uk.oracle.com/twiki/bin/view/Products/ProdIssuesC10Chassis

References

For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

* http://tns.central/fab

In addition to the above you may email:

* [email protected]

Contacts

Contributor: [email protected]
Responsible Engineer: [email protected]
Responsible Manager: [email protected]
Business Unit Group: Systems Group-x64

Attachments

This solution has no attachment