<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Bundle - Tag - Fryguy's Blog</title><link>https://hugo.fryguy.net/tags/bundle/</link><description>Bundle - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 27 Apr 2012 12:06:59 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/tags/bundle/" rel="self" type="application/rss+xml"/><item><title>Cisco IOS XR Interface Bundles ( aka Etherchannel or 802.3ad)</title><link>https://hugo.fryguy.net/2012/04/27/cisco-ios-xr-interface-bundles-aka-etherchannel-or-802-3ad/</link><pubDate>Fri, 27 Apr 2012 12:06:59 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/04/27/cisco-ios-xr-interface-bundles-aka-etherchannel-or-802-3ad/</guid><description><![CDATA[<p align="center">
  
</p>
<p>Well, time for another IOS XR post, this time on Interface Bundles, particularly Ethernet. With IOS XR a bundle can be considered a group of one or more ports that are aggregated together and treated as one link. The different links within a single bundle can have different speeds, where the fastest link can be up to four times faster than the slowest link. Each bundle has a single MAC, and a single IP address.<br>
As with some other devices, you can have interfaces in a bundle across multiple line cards, thus protecting yourself from a single point of failure. If a line card fails,  the bundle interface will stay up as you configured it to span more then 1 card. A bundle also provides you with more bandwidth then might normally be available if using a single interface. Cisco IOS XR supports 802.3ad (LACP) as well as Cisco proprietary EtherChannel. In all honesty, if you use anything other then LACP you are asking for trouble – LACP has prevent many problems when GBICs have gone bad, but the interfaces are still UP/UP.<br>
Ok, time for the meat and potatoes:</p>]]></description></item></channel></rss>