Enclosure names can potentially differ across multiple servers depending on the order they were presented

book

Article ID: 100004781

calendar_today

Updated On:

Cause

DDL sorts the enclosure serial numbers before starting by assigning the integer identifiers (0, 1, 2, …). One exception is that it tries to keep the name persistent as well.

 

So it can happen that if the host is already seeing one enclosure (enclrx) with serial number x, then the enclosure will get 0 as an enclosure name. Later if new enclosure (enclry) is connected with serial number y and even if ‘y’ is less than ‘x’, as zero is already reserved for the old enclosure (enclrx), the new enclosure enclry gets ID as 1.

 To refresh the names, customers can simply remove the /etc/vx/disk.info file where the persistent names are stored and then enclosure name ordering should be followed.

 

Resolution

The CLI(command line interface) command "vxddladm assign names" was introduced in 5.0 MP3 to dynamically refresh the contents of the /etc/vx/disk.info file.

The "vxddladm assign names" command was enhanced further in 5.1 SP1 to dynamically refresh the contents of the /etc/vx/array.info file.

 

 

Issue/Introduction

Enclosure name ordering. Server A # vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT ======================================================================================= emc0 EMC 000290300822 CONNECTED A/A 10 emc1 EMC 000290301414 CONNECTED A/A 5 disk Disk DISKS CONNECTED Disk 3 Server B # vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT ======================================================================================= emc0 EMC 000290301414 CONNECTED A/A 5 emc1 EMC 000290300822 CONNECTED A/A 10 disk Disk DISKS CONNECTED Disk 3 Potentially, the two enclosures are inconsistent across the two servers.