Re: NIC Team

From: Venkataramanaiah.R (vramanaiah@gmail.com)
Date: Sun May 13 2007 - 17:06:49 ART


this is exactly where i am getting to.. I am designing a Data center network
with a few access switches..

When i refer uplink, i am referring to all the links out of the
access-switch ... I am looking at the entire module failing; which
eventually cuts down all the uplinks and the inter-access switch links..

Planning for module redundancy; just for this failure situation is not
justifiable in my opinion

thanks

On 5/13/07, Andy LaPorte <andy@cloud9.net> wrote:
>
> I think you would need to use tracking in some way to provide network
> redundancy. I have never seen a server perform some sort of tracking
> unless
> both NIC are active/active with some routing function on the server side.
>
> I would be interested to learn if there is another way of doing this also
> based just on the server tracking connectivity to an end destination.
>
> Another though is both access switches should be cross linked with
> spanning
> tree blocking that port. If the uplink goes down then the spanning tree
> would re-converge and the cross link would become active.
>
> Andy
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Venkataramanaiah.R
> Sent: Sunday, May 13, 2007 2:52 PM
> To: ccielab@groupstudy.com
> Subject: OT : NIC Team
>
> Question on NIC Teaming...
>
> In fault tolerant mode; we generally connect the two NICs to two different
> access switches..
>
> It just stuck me; that this might be providing Fault tolerance when one of
> the NIC goes down; but what happens when there is a indirect failure like
> the uplink between the Acesss switch and distribution switch fails..?
>
> How does the server come to know of this failure condition? (For its
> outgoing traffic)
>
> Rgds
> -Venkat
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:20 ART