I've tried both with "/sbin/gabconfig -c -n4" and "/sbin/gabconfig -c -n3" (By the way, does the absence of white space between the -n argument and the number matters?)
 

----- Original Message-----
From: Jim Senicka <james_seni...@symantec.com>
Date: Tuesday, March 17, 2009 16:22
Subject: RE: [Veritas-ha] SFCFSRAC - node with the highest nodeid panics afternode with the lowest nodeid rejoins
To: Imri Zvik <im...@inter.net.il>
Cc: veritas-ha@mailman.eng.auburn.edu

> What is your gabtab settings?
>
> You seem to have two independent cluster generations.
>
> You should have /sbin/gabconfig -c -n4 in gabtab
>
>
>
>
> -----Original Message-----
> From: Imri Zvik [mailto:im...@inter.net.il]
> Sent: Tuesday, March 17, 2009 10:16 AM
> To: Jim Senicka
> Cc: veritas-ha@mailman.eng.auburn.edu
> Subject: Re: [Veritas-ha] SFCFSRAC - node with the highest
> nodeid panics
> afternode with the lowest nodeid rejoins
>
> On Tuesday 17 March 2009 15:32:55 Jim Senicka wrote:
> > A few questions
> >
> > 1. Do you have a support case open?
>
> Yes, for over two weeks.
>
> > 2. Do you reconnect the FC before the node boots?
>
> Yes, FC is reconnected immediately after the panic.
>
> > 3. Is the network available during boot time?
>
> Yes.
>
> >
> > "GAB: port b is halting the system due to network failure"
> essentially> means that VXFEN is connecting between two clusters
> with different
> > generation numbers, which should only happen if the clusters booted
> > independent of each other, then were joined at the network level
>
> This is weird. As you can see from the logs I've attached
> before, the
> cluster
> nodes 1, 2 and 3 were members, and node 0 rejoined them....
>
>
‭‮
_______________________________________________
Veritas-ha maillist  -  Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha

Reply via email to