Sun Storage 2540 Array
 

GCS>Sun Microsystems>Sun FAB>Standard>Reactive
 

With controller firmware 06.17.52.10 there is a possibility of duplicate World Wide Port Names (WWPN) being assigned to controllers in separate subsystems.

This issue can manifest itself when configuring more than one StorageTek 2540 array in a SAN or DAS configuration. When there are two or more controllers with same WWPN, they cannot be uniquely identified.

• Sun StorageTek 2540 array with controller firmware 06.17.52.10

To verify the firmware release use the CAM - Troubleshooting-> FRU's-> Controller-> Revision.

1. In a SAN, When more than one controller with the same WWPN is connected to a switch, the switch will see two or more unique devices with the same WWPN.

2. Array may experience loss of array management capabilities as described in CR 6501426 where the 2540 array could not be registered with CAM.

This issue occurs when the MAC addresses (which are used by the controller to generate the WWPN) of controllers in different 2540 arrays are sequential. When these values are sequential, the controller will generate duplicate WWPN's.

Prior to configuring more than one 2540 in a customers data path environment:

1. Attempt to register the new 2540 array with CAM. If the 2540 registers successfully, navigate to the Physical Devices -> Ports page and compare the WWPNs of the new 2540 array being configured to any other 2540 arrays already configured in the customers data path environment.

2. If the 2540 does not register successfully in CAM or during the comparison of WWPNs it is determined that the new 2540 array controller port WWPNs are duplicates of ones already configured in the customers data path environment,refer to the workaround for the procedure to generate a new unique WWPN for the new 2540 array being configured.

To perform this workaround you will need access to the 2540 controller serial shell.

The procedure to connect to the serial port and get the "Service Interface Main Menu" is documented in: http://download.oracle.com/docs/cd/E19508-01/820-0015-14/820-0015-14.pdf.

1. Login to the A controller serial shell and verify the current WWPNs by issuingthe "fcall 110" command. In this example the WWPN for Controller A is: "200500a0-b835ebcd":

-> fcall 110
(Tick 0041550045) ==> 09/20/07-12:46:44 (GMT)
Role  Chip  PortId       PortWwn            NodeWwn      DstNPort
Dflt     2  fffffe  00000000-00000000  00000000-00000000 05402780
Dflt     3  fffffe  00000000-00000000  00000000-00000000 053b6660
Host     2  000001  10000000-c94c0d71  20000000-c94c0d71 0555f020
This     2  0000e4  200500a0-b835ebcd  200400a0-b835ebcc 01fffe00

2. Perform the same verification of the WWPNs from the B controller shell.

3. To generate new WWPNs issue the following command in the A controllerserial shell:

-> wwnSetWwn 0,0
value = 0 = 0x0
-> 09/21/07-17:31:23 (GMT) (tShell):

NOTE: If the system has dual controllers, same action should be performed on each controller. Please reboot controllers after done.

This will set the WWPN to 0 on the A controller.

4. Issue the following command in the B controller serial shell:

-> wwnSetWwn -1,-1
value = 0 = 0x0
-> 09/21/07-17:31:44 (GMT) (tShell):

NOTE: If the system has dual controllers, same action should be performed on each controller. Please reboot controllers after done.

This will set the WWPN to ffffffff-ffffffff on the B controller.

5. Power cycle the array.

6. Perform steps 1 & 2 of the workaround again to verify the new WWPNs of the 2540 array being configured. Then re-compare the new WWPNs with those that already exist in the customer data path environment.

If no duplicate WWPNs are found, the workaround is complete.

If there is still duplication, perform steps 3-6 again until no duplication is observed.

At the time of publication of this FAB the final resolution is pending completion. Please use CR 6581772 for tracking purposes.

The next firmware release is planned to address this issue via the following patches:

• 127486-01 -Solaris
• 127487-01 -Windows
• 127488-01 -Linux

And CAM 6.01 (or later) is planned to include the new version from download site in late October/Nov 2007.

Note: the above patches are planned to be available in October when 500gb SATA drives release. However, CR 6581772 will not be listed in the README file.

This solution has no attachment