>>(eww html mail?) grow up. >>"teaming" which lets you set active/standby port selection which requires that both ports be in the same L2 domain.
Adrian Chadd wrote: > (eww html mail?) > > Stuff like the intel cards are shipped with "teaming" which lets you set > active/standby port selection (as well as classical etherchannel and > STP type protocols.) > > This means the standby port won't be used for any outgoing traffic, thus > the switch won't learn the shared MAC on that card. It'll "see" unicast > flood, broadcast and perhaps multicast crap on the standby NIC but the > card will be throwing it all away. > > Its not "true" redundancy by any classical stretch of the imagination but > it works fine in situations where your redundancy requirement is dead > chassis detection. > > > > > Adrian > > On Fri, Mar 21, 2008, James Slepicka wrote: > >> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> >> <html> >> <head> >> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> >> </head> >> <body bgcolor="#ffffff" text="#000000"> >> enlighten me<br> >> <br> >> Adrian Chadd wrote: >> <blockquote cite="mid:[EMAIL PROTECTED]" >> type="cite"> >> <pre wrap="">On Fri, Mar 21, 2008, James Slepicka wrote: >> </pre> >> <blockquote type="cite"> >> <pre wrap="">Maybe only a consideration in the data center, but you >> can't do NIC >> teaming across multiple switches for fault tolerance. >> </pre> >> </blockquote> >> <pre wrap=""><!----> >> Sure you can. >> >> (Oh, you want me to tell you how?) >> >> >> >> >> >> Adrian >> >> </pre> >> </blockquote> >> </body> >> </html> >> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
