Well after a lot of searching around the problem I managed to get the new
ASL to apply to the LUNs with a "vxconfigd -k -x syslog" This same
command run after 'tweaking' the /etc/vx/disk.info file also allowed me to
get the disks in the same order across my nodes. Hopefully it won't all
fall apart at some point down the line.
I tried to switch to OS based naming too but that didn't seem to make a
blind bit of difference - since I had what I wanted I didn't pursue this
any further though.
(Sathish - we are only at v5.0 but thanks for the response )
thanks,
Neil
From: "Sathish Nayak" <sathish_na...@symantec.com>
To: Neil Swallow/GBR/c...@csc, <veritas-vx@mailman.eng.auburn.edu>
Date: 02/09/2010 17:54
Subject: RE: [Veritas-vx] Discovered disk names
Which release you are using? Recent release 5.1 has capability to have
consistent names across cluster nodes.
- Sathish
-----Original Message-----
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Neil
Swallow
Sent: Thursday, September 02, 2010 12:12 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] Discovered disk names
Hello
I recently vxdctl enabled to see some new Hitachi LUN's (new array to
these
servers too) on two servers in a VCS cluster. The disks have been JBOD
named by the look of it (Disk_0 to Disk_28) rather than enclosure named.
I believe that this may be because I had an old version of the ASL
installed. I've now updated this ASL.
Additionally, whilst the Solaris device names seem to match on the two
cluster nodes, the Disk_x names do not. This doesn't technically
matter
but since this is a cluster I was hoping to get both nodes to look the
same
for easier management. and disk identification.
So....does anyone know the easiest way to wipe out the new VX disks (not
the OS devices) so I can re-vxdctl enable and hope that the new ASL
picks
the enclosure up correctly (OR can I just try and apply enclosure based
naming through vxddladm ??? and if so will this affect other,
pre-existing
disks?)
AND if I manage that (or even if not!) is there an easy way to get the
two
sides to match ? It seems I can edit /etc/vx/disk.info but is that the
only way?
thanks,
Neil
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
