Sun Storage 3510 FC Array
 
Sun Storage 3310 Array
 
Sun Storage 3511 SATA Array
 
Sun Storage 3320 SCSI Array
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
 

Applies to:

Symptoms

1. Multiple arrays will exhibit the same Ethernet or MAC address.
2. The unique worldwide names may change resulting in change of DIDs (device
ids) which are used for Sun[TM] Cluster configurations.

This document will explain why this problem happens, and includes steps to resolve the above.

Changes

The CUI is by default generated from the chassis serial number. On a working array, if this CUI is changed, 

both the MAC address as well as the worldwide names will change thereby causing problems from the host end.

We must ensure that the CUI always remains the same after any maintenance activity for smooth operation of the array.

Cause

Explanation for the above two issues:

1. Multiple arrays will exhibit the same Ethernet or MAC address.

This problem may happen when we use the cloning feature of these type of arrays where we can duplicate

the NVRAM settings from one array to another. We can save the NVRAM or the configuration details

from one array and use the same to create the same configuration on the other array.

By doing this, we also duplicate the CUI and the MAC address. Hence we could have more than one array with same MAC address.

2. The unique worldwide names may change resulting in change of DID's (device ids) which are used for Sun Cluster configurations.

All the controller FRUs that come from logistics have their controller unique identifier field set to "0" .

When this controller is used as a replacement FRU, it inherits the "unique identifier" from the primary controller,

in the case of a dual controller configuration, or the chassis serial number becomes the controller unique identifier,

in the case of a single controller or scenarios where the primary controller is also having problems.

The bottom line is that during a controller replacement or cloning, we must ensure that the CUI

is set to the same value as the array chassis serial number. Failing to do so will result in either multiple arrays

having the same ethernet address, or the worldwide names of the logical drives will change.

Solution

Resolution

If one of these problems occurs, perform the following steps to resolve this issue :

1. Telnet to the SE3310/SE3320/SE3510/SE3511 array
2. At the Main Menu, select "View and Edit configuration parameters
3. On the resulting menu, select "Controller Parameters"
4. From the "Controller Parameters" menu, select
   "Controller Unique Identifier "
5. Enter the value 0 to automatically read the chassis serial number from the midplane or type the hex value for the original serial number of the chassis (use this method when the midplane has been replaced)
6. Reset the array

NOTE 1: If the midplane is replaced, then the controller unique identifier will change and in this case, if we are running Sun Cluster,

then we would have to manually recreate the DID's for Sun Cluster to work normally.

NOTE 2: A non-zero value should be specified only if the chassis has been replaced but the original CUI

has to be retained: for example, in a Sun Cluster configuration to maintain the same DID's.

This practice is not recommended as it can lead to problems and confusion in the future.

On the next available outage, the DID's must be manually fixed for the cluster to work normally.

This solution has no attachment