What’s new and exciting with EIGRP (Enhanced Interior Gateway Routing Protocol)? Actually, lots… First a bit a background on EIGRP.
EIGRP is an advanced distance vector routing protocol used extensively by enterprise customers. It is very popular because it is simple to deploy and support. Some major attributes are:
- EIGRP does not mandate many network design requirements and is therefore perceived as “forgiving” and “flexible”. For example, EIGRP does not require support for multiple routing sub-domains or Areas.
- While route summarization is a recommended best practice to minimize route table size, it is optional with EIGRP.
- EIGRP can scale to support thousands of routers in a Hub and Spoke configuration. The Hub and Spoke design is especially popular in WAN networks.
For additional information on EIGRP, please click here. There is also a great BLOG that compares EIGRP and OSPF that I think you will find informative and is posted here.
While EIGRP has a large customer following, some customers have hesitated because of concerns of EIGRP being “proprietary”, which would prevent them from multi-vendor network support. In some cases this has caused customers to design their networks to limit usage of EIGRP, even though they would like to deploy it ubiquitously. One result has been non-optimal network design and traffic flow, resulting from multiple IGP (Interior Gateway Protocol) redistribution points.
That brings me back to what is new and exciting with EIGRP. Read More »
Tags: EIGRP, Enhanced Interior Gateway Protocol, ietf, ietf working group, IGP, Interior Gateway Protocol, ipv4, IPv6, IPv6 deployment, OSPF, WAN, WAN networks
So, we wrapped up our day with the Networking Field Day crew last week with a free form discussion on where we go next with SDN. To be honest, the session did not go quite as I envisioned, but, in retrospect, I would not changed anything. As Ethan Banks (of PacketPushers fame) noted in Twitter, this session was more about shooting the unicorns than letting them run free. It seems that if we are going to convert our SDN unicorns into SDN plough horses, we are going to shed a little blood. At the end of the day, the market will be served by frank conversations—we need to move beyond painting SDN acolytes as starry-eyed and SDN detractors as being heretical and reactionary.
In the interest of keeping the conversation going, here are some of the things I walked away with after the conversation on Wednesday (in no particular order):
Is Hardware Innovation is Over?
This industry has always been one big pendulum and, currently, the pendulum is firmly in the software camp. Today, many of the truly interesting things in networking are going on with software. While most would agree we are at an inflection point with programmability, there are no clear directions for the evolution of SDN. Certainly there are pieces in place like OpenFlow and OpenStack, but OF 1.3 in unlikely to be the zenith of OF evolution let alone SDN evolution—current technologies will continue to mature and new ones will inevitably emerge. More importantly, the “how we do things” and “what do want to accomplish” of SDN will most certainly continue to evolve and as long as that is the case, software will rule because it’s simply easier and faster to experiment with software. But, once some clear directions begin to emerge, I guarantee you the action will swing back towards the hardware because doing things in hardware tends to be faster and more efficient. I could point to Cisco examples of this, but instead look at what Intel, the poster child for general purpose processors, has done with VT extensions to support virtualization or QuickSync for video transcoding.
Is OpenFlow Ready for PrimeTime?
One of the more contentious points yesterday is if OpenFlow is production ready. I think it’s a flawed “do these jeans make me e look fat” kind of question. There are certainly folks out there using OF to handle production traffic—for example, some of the cool things Brent Salisbury is doing. So, it’s not a binary question, but more a matter of assessing scope and scale. The better question to ask is what is the operational and performance envelope of OpenFlow and how does that match my needs, priorities, and capabilities. The risk with any emerging technology is that, often, the only way you find the edge of the envelope is once you’re on the other side, usually with colorful and memorable results. Regardless, I don’t see this question existing in another year or so.
Read More »
Tags: Cisco ONE, Cisco onePK, Network Field Day, OpenFlow, OpenStack, SDN
By Neelley Hicks, Guest Columnist
Near the epicenter of the 7.0 magnitude earthquake in Haiti, less than three months after it occurred, Clif Guy of Church of the Resurrection (COR) encountered a unique challenge: how to build a communications infrastructure so what was happening on the ground could be conveyed to incoming relief teams and others who had invested themselves in the Petit Goave community.
As director of IT at COR, Guy was used to technical challenges – but not of this scale. Spotty electricity and lack of Internet access in an area that had just suffered its worst natural disaster presented issues like never before. (Read how Clif used Google Earth to engineer a network to connect Haiti’s most needed areas.) Read More »
Tags: disaster response, education, Haiti, inveneo, ITC4D, UMC, vni, VNI-SA
Two weeks ago, we had the pleasure of hosting a TelePresence roundtable for 46 Public Sector CxO-level executives from 20 locations throughout Europe, Middle-East and Africa (see map below). The event was moderated by Jens Mortensen (Director Central Government & Healthcare, Cisco EMEAR) and the main objectives were:
- To present and debate on 3 perspectives of Government Cloud Governance: Policy, Insourcing Model, Outsourcing Model
- To share best practices and alternative governance models with peers in different countries
- To help shape, plan and implement a proven strategy for government cloud
The CTO of a central ICT agency in Europe reported: “I valued the pragmatic approach (presentations from people in the public sector who actually have a service running) and the possibility to ‘network’ with very relevant people for the cloud project [my organization] is working on).”
The CEO of an ICT Provider for Government agencies reported: “I enjoyed the discussion very much. Clearly there are very many different approaches to implementation of domain cloud solutions for both public and private sector needs based on local supply structures and government culture.”
Read More »
Tags: CIO, cloud, government, insourcing, outsourcing, policy, Roundtable
This week in London, our own Dr. Abe Peled accepted the prestigious Lifetime Achievement Award from Digital TV Europe, as part of its “Euro 50 Awards” at this week’s Cable Congress.
Anyone who knows Abe knows that he’s a quick-witted, highly intelligent, super-motivated gentleman, and we’re all sincerely glad he’s part of the Cisco team, following our acquisition of NDS in 2012.
Abe has 40 years of accomplishments in the digital TV industry. He started his television life in 1974 at IBM’s Research Division, working on advanced digital signal processing techniques, and advanced up and up and up until he was named VP/Systems and Software, overseeing all of IBM’s research labs, worldwide. His work there even landed his face on a cover story in the New York Times’ Business section, in August of ’91. Read More »
Tags: Abe Peled, cable congress, Service Provider