Munish,
If, after you brought up SysA,
SGA failed back over to it you would incur an outage. It’s the position of
VCS to try and maintain the highest availability of your application. As a
result, it will not fail back to a server automatically like this. If SysB
faults f
have done this manually).
Hope
this explains it a bit more.
Tom
From: Munish Dhawan
[mailto:[EMAIL PROTECTED]
Sent: Sunday, September 03, 2006
7:00 PM
To: Tom Stephens;
Veritas-ha@mailman.eng.auburn.edu
Subject: RE: [Veritas-ha] SG
Failover&Failback Q
Dharmesh,
This may sound a bit repetitive from what support has told you,
but here's what I'd try:
First, this appears to be a NFS problem. Even so, what I would do is
first isolate it completely from VCS. To do this, I would stop VCS
(hastop -all) and make sure that all the resources w
Laszlo,
The short answer is this
isn’t something that you should be concerned about.
For a bit longer answer, there
is a attribute called ConfidenceInterval. This attribute reflects the amount
of time that a resource must be in a particular state (online,
Holger,
You should make the exit values for your monitor script equal
100 for offline and 110 for online, given the version of VCS you are
using.
I don't suppose the line:
{ if ($4 == "Alive") {exit 1} else {exit 0}
Is causing you issues?
But a easy way to troub
You should be able to use vxlicrep to report on all your licenses on a
system.
Tom
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Damodharan K
Sent: Tuesday, March 27, 2007 2:52 AM
To: [EMAIL PROTECTED]
Cc: veritas-ha@mailman.eng.auburn.edu
Subject:
Ceri,
No, it's not a bug. It's trying to match the entire line
(including the -a).
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ceri
Davies
Sent: Thursday, April 26, 2007 3:11 AM
To: veritas-ha@mailman.eng.auburn.edu
Subject: [Ve
Is vxconfigd running on each of the systems?
Tom
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Hunter
Sent: Monday, May 28, 2007 7:03 AM
To: veritas-ha@mailman.eng.auburn.edu
Subject: [Veritas-ha] State Unknown
Can'
You might also want to try to set the Options attribute for your Share
resource to "-o rw"
Tom
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Munish
Dhawan
Sent: Monday, May 28, 2007 3:43 AM
To: Zhisong Jason Jin; veritas-ha@m
If the monitor test is not valid (regarding you exit with 110) then the monitor
should exit with 100 (offline).
Tom
Sent by Good Messaging (www.good.com)
-Original Message-
From: Charles Bueche [mailto:[EMAIL PROTECTED]
Sent: Monday, August 27, 2007 07:48 AM US Mountain Stand
can reach the person managing the list at
> [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Veritas-ha digest..."
>
>
> Today's Topics:
>
>1. vcs 4.1mp2 + RH linux and nfs ques
I would suggest that you use the NetApp agents instead of the bundled
Mount agent.
Tom
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arjun
koneru
Sent: Thursday, September 20, 2007 6:31 AM
To: veritas-ha
Subject: [Veritas-ha]
Some comments inline with TS>:
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Rongsheng Fang
Sent: Friday, September 28, 2007 6:53 AM
To: veritas-ha@mailman.eng.auburn.edu
Cc: [EMAIL PROTECTED]
Subject: [Veritas-ha] Highly available Symantec
When the resource fails a monitor, and RestartLimit is >0, then it will
attempt to restart the resource. It will not, however, mark the
resource as faulted unless the resource fails to start after the restart
(or until the number of restarts has been exceeded). So in order for
the resfault trigge
You shouldn't need to restart GAB/LLT, as it should automatically heal
it's self when the links are re-established. You may want to recheck
the cabling again.
Tom
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karthik
Sent: Friday, February 08, 2008 3:53
Karthik,
This could be due to a couple of possible problems.
One, you may not have downloaded the complete package. Under the
directory where you extracted the files to, make sure you can find the
CPI/common/CPI.pm file. If it is there, and your still getting the
error, try ad
Jorgen,
Consider the situation where it did fail over the disk group to
another system (sysb). At this point, sysb would have the ability to read and
write to the diskgroup and is functioning as expected. Sysa (the system where
you pulled the fiber from) is still running to
Ceri,
You would be correct that there is not a way for you to monitor
the amount of time left in the ConfInterval.
Depending on how your application is configured, you may be able
to craft the monitor EP for it in such a way to utilize the
ConfidenceLevel in conjunction with the o
Not according to the release notes for the product. These can be found
at:
ftp://exftpp.symantec.com/pub/support/products/ClusterServer_UNIX/283850
.pdf (For Linux 5.0)
ftp://exftpp.symantec.com/pub/support/products/ClusterServer_UNIX/287175
.pdf (For Linux 5.0 MP1)
ftp://exftpp.symantec.co
Did the value for your Pfile attribute definition get cut off?
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pablo
Calvo
Sent: Thursday, June 05, 2008 9:21 AM
To: veritas-ha@mailman.eng.auburn.edu
Subject: [Veritas-ha] missing or illegal da
Is your exit code for success 110 and for failure of the monitor 100?
Tom
From: veritas-ha-boun...@mailman.eng.auburn.edu
[mailto:veritas-ha-boun...@mailman.eng.auburn.edu] On Behalf Of
Jeff_Jones
Sent: Friday, January 09, 2009 11:52 AM
To: veritas-ha@mailman.eng.auburn.e
Just to add a bit to Jim's response...
Once you deleted the SG from the VCS configuration using the Cluster
GUI, you would then need to remove the VxVM disk group. I'm assuming
that before you removed the service group, you brought it offline. This
should have deported the disk group for you. A
Ganesh,
I'd suggest you open a support case with Symantec, as there are
several reason why this could be happening. Make sure that you tell
them if you are using VVR or not when you open the case.
Tom
-Original Message-
From: veritas-ha-boun...@mailman.eng.auburn.edu
[m
Charles,
There is not a online training/tutorial that I know of,
however there are several examples in the User's Guide.
(http://www.symantec.com/business/support/knowledge_base_sli.jsp?pid=150
66)
Though the foundation of knowledge that you have with
3.5 shoul
Charles,
I'd still recommend using a proxy setup like your
familiar with. The proxy resources don't have to point to a resource in
the ClusterService group, but could refer to any NIC resource that you
have in a different SG. If you have several SG's that are all using the
same
ther people's mistakes and the rest of us have
to be other people." -- Zig Ziglar, Author
From: Tom Stephens [mailto:tom_steph...@symantec.com]
Sent: Wednesday, July 08, 2009 11:49 PM
To: Baker, Charles H.; veritas-ha@mailman.eng.auburn.edu
Subject: RE: [Veritas-ha] NICs and Prox
Gak,
The way that the LVMVolumeGroup agent determines the
state of the resource (VG in your case) is by execution of the monitor
script under /opt/VRTSvcs/bin/LVMVolumeGroup. If memory serves, this is
a Perl based script that you should be able to cat out and view easily.
I bel
27 matches
Mail list logo
