[c-nsp] L3 to access layer

[Tim Durack]

Not if you're doing L3 at the access switch though...

We do L2 for the desktop access layer, but every switch has it's own
set of dedicated VLANs, so it's the closest thing to L3 without
running L3 on the switch (if that makes any sense.)

For the Data Center we span VLANs across "server" switches. Servers
run with NIC teaming, transmit load balancing means both MACs are
active out-bound, only one inbound.

Fail-over time is deterministic and does not involve any
STP/etherchannel configuration for the server ports.

Works well for us.

Tim:>

On Fri, Mar 21, 2008 at 11:40 AM, Paul Stewart <paul at paulstewart.org> wrote:
> We do it all the time here.. in the sense of primary/secondary NIC cards
>  sharing same MAC and same IP etc.... to two different distribution
>  switches.... NIC bonding would be the more proper term though I guess...;)
>
>
>  -----Original Message-----
>  From: cisco-nsp-bounces at puck.nether.net
>
>
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Adrian Chadd
>  Sent: Friday, March 21, 2008 11:51 AM
>  To: James Slepicka
>  Cc: cisco-nsp
>  Subject: Re: [c-nsp] L3 to access layer
>
>  On Fri, Mar 21, 2008, James Slepicka wrote:
>  > Maybe only a consideration in the data center, but you can't do NIC
>  > teaming across multiple switches for fault tolerance.
>
>  Sure you can.
>
>  (Oh, you want me to tell you how?)
>
>
>
>
>
>  Adrian
>
>  _______________________________________________
>  cisco-nsp mailing list  cisco-nsp at puck.nether.net
>  https://puck.nether.net/mailman/listinfo/cisco-nsp
>  archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>  --
>  No virus found in this incoming message.
>  Checked by AVG.
>  Version: 7.5.519 / Virus Database: 269.21.8/1337 - Release Date: 3/20/2008
>  8:10 PM
>
>
>
>
>  _______________________________________________
>  cisco-nsp mailing list  cisco-nsp at puck.nether.net
>  https://puck.nether.net/mailman/listinfo/cisco-nsp
>  archive at http://puck.nether.net/pipermail/cisco-nsp/
>