Hello all!

 

The traditional symmaskdb technology was replaced with  Auto-provisioning 
Groups  (see Solution Enabler Symmetrix  Controls CLI 7.2)

 

Just noticed an interesting bug  when configuring veritas disks on thin devices 
combined in storage groups.   When adding a symdev A (thin device

for sample)  to the symmetrix storage group a new lun id is presented to the 
symdev A. When removing this symdev A from the storage group this lun id can be 
used by another newly added symdev B. When  giving back the symdev A to the 
storage group it is presented with the new lun id.  As a result Veritas  gets 
two identical ebn disk names which can lead to some very bad things.   There 
can be two workarounds:

1)      Using reserve lun id option for symdev on symmetrix storage group  to 
exclude any confusion about lun ids;

2)      vxddladm set namingscheme=ebn persistence=no use_avid=yes

 

I think the best option is number 2. But no sure about potential problems 
because of changing default persistence (=yes) meaning

 

Any suggestions?

 

Regards, Pavel Tsvetkov

 

P.S. about this option from man pages:

 

 

 

persistence

                         Specifies whether the names of disk dev-

                         ices  that  are displayed by VxVM remain

                         unchanged after disk hardware  has  been

                         reconfigured and/or the system rebooted.

 

               If persistence is on, the DDL assigns device names

               from  the  persistent device name database, rather

               than generating new names according to the OSN  or

               EBN naming scheme.

 

               If the naming scheme is OSN, name  persistence  is

               off by default. The generated names are not likely

               to differ from the names in  the  persistent  name

               database,  unless a change causes the OS to assign

               a new path name for a device.

 

               If the naming scheme is EBN, name  persistence  is

               on  by  default.  Certain configuration changes on

               the array side could cause the generated  name  to

               be  different from the name in the persistent name

               database. When name persistence is  on,  the  name

               from  the  persistent names repository is used for

               the DMP meta-device, unless

                the user changes it. .

 

_______________________________________________
Veritas-vx maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to