Upgrading the X6220 Server Module to SW1.1 Causes Device Paths to be Reenumerated

Asset ID:	1-77-1001129.1
Update Date:	2011-03-22
Keywords:

Solution Type Sun Alert Sure

Solution 1001129.1 : Upgrading the X6220 Server Module to SW1.1 Causes Device Paths to be Reenumerated

Related Items


Sun Blade X6220 Server Module

Related Categories


GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
 GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved

PreviouslyPublishedAs
201512

Product
Sun Blade X6220 Server Module

Bug Id
<SUNBUG: 6648545>

Date of Preliminary Release
15-Jan-2008

Date of Resolved Release
20-Mar-2008

Upgrading the X6220 Server Module to SW1.1 Causes Device Paths to be Reenumerated

1. Impact

Upon upgrading the Sun Blade X6220 Server module with SW1.1 or later, device paths may be reenumerated, causing NIC ports to not work correctly, thereby affecting the applications which use those ports (iSCSI, SANs, etc.)

2. Contributing Factors

This issue can occur on the following platform:

Sun Blade X6220 Server Module with ILOM/BIOS upgrade SW1.1

The ILOM/BIOS version on a system can be determined by logging in to the SP of the server blade and running the 'version' command as in the following example:

    SP-> version
    SP firmware 2.0.3.1
    SP firmware build number: 23240
    SP firmware date: Fri Oct 12 18:13:55 PDT 2007
    SP filesystem version 0.1.14

The ILOM/BIOS versions are linked, so if you running a certain ILOM version you have a certain BIOS level as well. The version above indicates this system has SW1.1 installed with ILOM 2.0.3.1/BIOS 30.

3. Symptoms

After upgrading the ILOM/BIOS, NIC ports can no longer be accessed and a new NIC device shows up within the device files.

Checking the device files indicates the paths have changed:

Old path:

    /pci@7b,0/pci10de,cb84@a

New path:

    /pci@7c,0/pci10de,cb84@a

4. Workaround

If the server module is upgraded to SW1.1, new ports will need to be configured as well as the associated software which uses those ports.

5. Resolution

There is no final fix to this issue, as the changes incorporated in the ILOM/BIOS upgrade SW1.1 are permanent to support future platform releases. Please see the Workaround section above as the final resolution for this isssue.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Modification History
20-Mar-2008: Updated Resolution section; RESOLVED

Previously Published As
103202
Internal Comments
Please send technical questions to the following email:
[email protected]
and CC the following persons:
Internal Contributor/Submitter
Internal Eng Responsible Engineer
Internal Services Knowledge Engineer

Availability ==> Regression
The root cause is that BIOS30 disabled the PCI Express controller XVR0 and XVR1 for CR6611333 (Gemini does not boot off a CF). BIOS29 added slot 0xE to support IB NEM (CR6605201).

This issue will not be experienced on new systems shipped as new
systems, per WO_38122, all ship with the latest SW1.1a version
installed since 12/10/07. Therefore, the device paths are set for these
new systems. The concern here is the customer base already in the field
that will be affected when they are upgraded.

Internal Contributor/submitter
[email protected]

Internal Eng Responsible Engineer
[email protected]

Internal Services Knowledge Engineer
[email protected]

Internal Eng Business Unit Group
SSG WGS (Workgroup Systems)

Internal Escalation ID
70809248, 1-395465305

Internal Sun Alert Kasp Legacy ID
103202

Product_uuid
4d0e7d47-d285-11db-9135-080020a9ed93|Sun Blade X6220 Server Module
Internal Sun Alert & FAB Admin Info
WF 20-Mar-2008, david m: no fix, use Workaround, publish as resolved
WF 30-Jan-2008 karen doing catchup
Critical Category: Availability ==> Regression
Significant Change Date:
Avoidance: None
Responsible Manager: [email protected]
Original Admin Info: [WF 11-Jan-2008, dave m: draft created, waiting on addtl info from submitter]

Attachments

This solution has no attachment