Hello all,
I have a situation where one system is taking a long time to scan for
disk groups. I have a VCS cluster in a 4+1 configuration. I have
recently added the last production node to the cluster. After the disks
were presented to the failover node, it took a long time for any Vx
commands
4.x keys will work with 5.0 binaries.
5.0 keys will not, as a rule, work with 4.x binaries.
Scott
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bonfoey,
Richard
Sent: Friday, October 03, 2008 10:29 AM
To: veritas-vx@mailman.eng.auburn.edu
Hi,
What is the storage vendor you are using and is it configured as A/P or
A/PF ?
Taking 5 minutes is probably the due to tress pass.
The reasons could be,
1. not have the proper ASL/APM for the storage on both the nodes
(including the failover node).
2. are both nodes are on a CVM
Maybe looking at the Veritas logs while the disk group commands run would
give you a hint...
In /var/adm/vx/
Jon
On Tue, Oct 7, 2008 at 1:59 PM, Kirubakaran Kaliannan
[EMAIL PROTECTED] wrote:
Hi,
What is the storage vendor you are using and is it configured as A/P or
A/PF ?
Taking 5
Thanks to all for the suggestions. I'm not sure if it's totally working
yet, but it definitely looks better.
Thanks Andrey - I didn't even think to check for trespassed luns. I
found about 1/2 the luns were trespassed. I fixed those. I re-ran a
vxdisk -o alldgs list. The Clariion SP went
