One of the fun things for me about helping with the new CCDP Bootcamp is learning about technologies you do not get exposure to in the “traditional” Routing and Switching curriculum that are based on mid-level and low-level Cisco hardware. One of those technologies that our new course will cover is Bidirectional Forwarding Detection (BFD). This technology is found on Cisco 6500/7600 series routers, as well as 12000 series and Carrier Routing System (CRS-1 Routers).
Like many of the features covered in the Routing Protocol Design section of the course, Bidirectional Forwarding Detection seeks to speed up routing protocol convergence. The key factor in this goal addressed by BFD is the fast detection of node or link failure in the routing design.
Many approaches to the fast detection of the failure of a link or neighbor deal with some type of accelerated hello packet (fast hellos at Layer 3). BFD operates along a similar line,except the fast link hellos are accomplished at Layer 2. The CPU impact of the BFD process ends up being much less compared to other fast hello approaches. Cisco has tested systems running 100 concurrent BFD sessions between routers and noticed an increase in CPU utilization of a mere 2%. And remember, that was with 100 concurrent sessions running.
In order to take advantage of Cisco’s BFD, we not only require the correct software and hardware version, but we need the cooperation of the routing protocol. Fortunately, BFD functionality has been engineered into OSPF, EIGRP, IS-IS, and BGP, as well as such important “support” protocols like HSRP.
If you would like to learn more about BFD right now, visit the Cisco DOC-CD.
Like many of the features covered in the Routing Protocol Design section of the course, Bidirectional Forwarding Detection seeks to speed up routing protocol convergence. The key factor in this goal addressed by BFD is the fast detection of node or link failure in the routing design.
Many approaches to the fast detection of the failure of a link or neighbor deal with some type of accelerated hello packet (fast hellos at Layer 3). BFD operates along a similar line,except the fast link hellos are accomplished at Layer 2. The CPU impact of the BFD process ends up being much less compared to other fast hello approaches. Cisco has tested systems running 100 concurrent BFD sessions between routers and noticed an increase in CPU utilization of a mere 2%. And remember, that was with 100 concurrent sessions running.
In order to take advantage of Cisco’s BFD, we not only require the correct software and hardware version, but we need the cooperation of the routing protocol. Fortunately, BFD functionality has been engineered into OSPF, EIGRP, IS-IS, and BGP, as well as such important “support” protocols like HSRP.
If you would like to learn more about BFD right now, visit the Cisco DOC-CD.
