[prev in list] [next in list] [prev in thread] [next in thread] 

List:       veritas-ha
Subject:    RE: [Veritas-ha] VCS turning off a network card?
From:       "Tom Stephens" <Tom.Stephens () veritas ! com>
Date:       2005-04-01 22:20:01
Message-ID: 39310EC65ADF75458980739A2810901EA18C9B () svlxchcln2 ! enterprise ! veritas ! com
[Download RAW message or body]

Andrey,

Isn't that what you have specified for it to do?

...
Device @v880 = { hme0 = "147.208.14.91", qfe2 = "147.208.14.91" }
...

	Tom


-----Original Message-----
From: veritas-ha-admin@mailman.eng.auburn.edu
[mailto:veritas-ha-admin@mailman.eng.auburn.edu] On Behalf Of Andrey
Dmitriev
Sent: Friday, April 01, 2005 12:52 PM
To: veritas-ha@mailman.eng.auburn.edu
Subject: RE: [Veritas-ha] VCS turning off a network card?

BTW,

I've changed the config..

However, .91 IP now came up on qfe2 card.

I am now suspecting a bad hme0 card/connection?


        MultiNICA mnic (
                Device @rock = { hme0 = "147.208.14.116",
                         qfe3 = "147.208.14.116" }
                Device @dragon = { hme0 = "147.208.14.114",
                         qfe3 = "147.208.14.114" }
                Device @smaug = { hme0 = "147.208.14.120",
                         hme1 = "147.208.14.120" }
                Device @v880 = { hme0 = "147.208.14.91", qfe2 =
"147.208.14.91" }
                NetMask = "255.255.255.128"
                ArpDelay = 5
                Options = trailers
                RouteOptions @rock = "default 147.208.14.116 0"
                RouteOptions @dragon = "default 147.208.14.114 0"
                RouteOptions @smaug = "default 147.208.14.120 0"
                RouteOptions @v880 = "default 147.208.14.91"



On Fri, 1 Apr 2005, Tom Stephens wrote:

> Andrey,
> 
> 	Your right.  Only one should be up at a time, and VCS will
> manage that.
> 	Though I am curious why you chose to use MultiNICA instead of
> MultiNICB...?  (Not that there is anything wrong with it, just
> wondering...)
> 
> 	Tom
> 
> 
> 
> -----Original Message-----
> From: veritas-ha-admin@mailman.eng.auburn.edu
> [mailto:veritas-ha-admin@mailman.eng.auburn.edu] On Behalf Of Andrey
> Dmitriev
> Sent: Friday, April 01, 2005 11:58 AM
> To: veritas-ha@mailman.eng.auburn.edu
> Subject: [Veritas-ha] VCS turning off a network card?
> 
> We've been trying to figure out a mystery on why a network card
> sometimes
> comes up and sometimes doesn't. Since I saw it come up and then come
> down,
> immediate I thought that it's vcs (and probably just misconfigured vcs
> or
> OS)
> 
> what i saw..
> 
> [lroot@v880]-> ifconfig -a
> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
1
>         inet 127.0.0.1 netmask ff000000
> hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index
> 2
>         inet 147.208.14.91 netmask ffffff80 broadcast 147.208.14.127
>         ether 8:0:20:e1:4:d9
> qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index
> 3
>         inet 147.208.14.93 netmask ffffff80 broadcast 147.208.14.127
>         ether 8:0:20:cd:1a:9e
> [lroot@v880]-> df -k
> Filesystem            kbytes    used   avail capacity  Mounted on
> /dev/dsk/c5t0d0s0    1949551  247434 1643631    14%    /
> /dev/dsk/c5t0d0s6    4038702  918459 3079856    23%    /usr
> /proc                      0       0       0     0%    /proc
> fd                         0       0       0     0%    /dev/fd
> mnttab                     0       0       0     0%    /etc/mnttab
> /dev/dsk/c5t0d0s1    4133838  105850 3986650     3%    /var
> swap                 47480336      24 47480312     1%    /var/run
> swap                 47480376      64 47480312     1%    /tmp
> /dev/dsk/c5t0d0s5    6053358   51817 5941008     1%    /opt
> 
> Few secs later...
> 
> [lroot@v880]-> ifconfig -a
> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
1
>         inet 127.0.0.1 netmask ff000000
> qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index
> 3
>         inet 147.208.14.93 netmask ffffff80 broadcast 147.208.14.127
>         ether 8:0:20:cd:1a:9e
> [lroot@v880]-> ifconfig -a
> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
1
>         inet 127.0.0.1 netmask ff000000
> qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index
> 3
>         inet 147.208.14.93 netmask ffffff80 broadcast 147.208.14.127
>         ether 8:0:20:cd:1a:9e
> [lroot@v880]->
> 
> 
> Relavant cluster config...
> 
> Wait.. I did something wrong here.. vcs should use either
> device(hme0/qfe2) for v880.. but the IP should be the same? And I
> shouldn't be bringing up the second card, VCS should take care of me
if
> it
> has to..?
> 
> 
>         MultiNICA mnic (
>                 Device @rock = { hme0 = "147.208.14.116",
>                          qfe3 = "147.208.14.116" }
>                 Device @dragon = { hme0 = "147.208.14.114",
>                          qfe3 = "147.208.14.114" }
>                 Device @smaug = { hme0 = "147.208.14.120",
>                          hme1 = "147.208.14.120" }
>                 Device @v880 = { hme0 = "147.208.14.91", qfe2 =
> "147.208.14.93" }
>                 NetMask = "255.255.255.128"
>                 ArpDelay = 5
>                 Options = trailers
>                 RouteOptions @rock = "default 147.208.14.116 0"
>                 RouteOptions @dragon = "default 147.208.14.114 0"
>                 RouteOptions @smaug = "default 147.208.14.120 0"
>                 RouteOptions @v880 = "default 147.208.14.91"
>                 )
> 
> _______________________________________________
> Veritas-ha maillist  -  Veritas-ha@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
> 

_______________________________________________
Veritas-ha maillist  -  Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha

_______________________________________________
Veritas-ha maillist  -  Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic