5.3, the story is the same.
Thanks,
-kiru
From: Fred [mailto:mamatec...@mamatec.com]
Sent: Wednesday, June 24, 2009 10:33 AM
To: Kirubakaran Kaliannan
Cc: Mamatec Team; veritas...@mailman.eng.auburn.edu;
veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] SCSI-3 reservation over VIO
Hi,
To exclude paths from dmp or from vxvm, Try
# vxdmpadm exclude vxvm path=
# vxdmpadm exclude vxdmp path=
Run the above command for all the paths you want to exclude. If just
from DMP, run the second command only.
Also 'vxdiskadm' can be used to suppress the path from DMP and or from
vxvm.
Hi,
The another way to change the names in the diskgroup in one go is
1. vxprint -mpvsh -g DISKGROUP >DISKGROUP.out
2. destroy the diskgroup
3. create the diskgroup with the same disk names
4. edit DISKGROUP.out and change the names manually
5
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 configurati
Hi,
Try the following command to enable config on all the disks,
# vxedit -g dg_mig_test set nconfig=all dg_mig_test
Thanks
-kiru
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 9:17 AM
To: veritas-vx@mailman.eng.
VIO client. All disks will
be seen directly instead of through VIO.
Thanks,
-kiru
From: Mamatec Team [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 10, 2008 2:12 AM
To: Kirubakaran Kaliannan
Cc: [EMAIL PROTECTED]; veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] SCSI-3 r
will be updated as "By default SF can support all VIO supported storage
arrays."
Thanks,
-kiru
From: Mamatec Team [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2008 2:11 PM
To: Kirubakaran Kaliannan
Cc: [EMAIL PROTECTED]; veritas-vx@mailman.eng.auburn.edu
Subject: Re: [
Hi,
The VIO client don't support SCSI-3 PR on VSCSI devices as of last SF
release. I hear IBM has plans to support this soon on VSCSI devices.
Once they support SCSI-3 PR on vscsi devices, it is straight forward for
SF to support fencing (just matter of testing and certifying the
support).
James,
Detach and reattach the plex. As this is in DISABLED state, it may not
be recovering.
-kiru
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James
Williams
Sent: Monday, January 08, 2007 6:26 AM
To: veritas-vx@mailman.eng.auburn.edu
Subjec
Hi Peter,
What kind of Jbod is it ?
DDL do consider serial number for multipathing. For JBOD category, The
seriel number is looked at the default location, if it don't find one,
then thi skind of problem araise.
So, we have an option in "vxddladm addjbod" CLI, to specify the inquiry
page detai
Jon,
This is not possible. Unless you explicitly run "vxdmpadm enable
ctlr=c0", the controller will not get ENABLED. No VxVM specific daemon
or scripts will issue this command.
Please look at the file /etc/vx/log/cmdlog to see whether the following
command
"vxdmpadm enable ctlr=c0"
is issue
Removing rm /etc/vx/disk.info would help.
This keeps the name persistent across reboot.
Thanks
-kiru
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robinson, Greg
Sent: Thursday, November 30, 2006 7:57 PM
To: Veritas-vx@mailman.eng.auburn.edu
Subject
12 matches
Mail list logo
