[c-nsp] SPLIT ETHERNET

[Chris Burwell]

This sounds like port channel/Etherchannel. HP calls this trunking on
their procurve line.

When you are talking about switching equipment, this is usually used
when you want to incorporate redundant network links. For example, if
you want to have to uplink ports from an edge switch back to your core
you could put the two ports in an Etherchannel. When you do this, the
switch treats the two ports as one.

A major advantage of doing this is convergence. If you had a similar
setup to what I described above, but instead used STP to block one of
the ports and prevent loops, it would take a longer amount (a few
seconds with rstp) of time for the switch to fail over to the other
port if one should fail (That time is called convergence). With
Etherchannel, convergence is really not an issue since the switch
treats both ports as one.

I hope this helps.

- Chris

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Rocker Feller
> Sent: 06 January 2009 12:37
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] SPLIT ETHERNET
>
> Hi,
>
> I am looking to understand the term split ethernet and how it works.
>
> Anybody having an idea on what it refers to and how it can be implemented?
>
> So far the documentation I have seen is
>
> ?"It presents a single IP address on multiple Ethernet Interfaces. The split Ethernet function supports the usage of several Ethernet interfaces in different general processor boards"
>
> This is the best i can get and would appreciate anybody with a pointer to the right direction.
>
> I am fairly new in this cisco field and would appreciate assistance
>
> Rock.
> _______________________________________________
> 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/