Dead Simple Routers-On-A-Stick Configuration |
As a follow-up to my previous article on Port Channels titled “4 Types of Port Channels and When They're Used” I wanted to talk a bit about the long-standing rule that says you should always create your Etherchannel (EC) bundles with a number of links that works out to a power of two (ie, 2,4 or 8 links). That rule is less applicable today than it used to be.
The other day I was catching up on recorded content from Cisco Live! and I saw mention of yet another implementation of port channels (this time called Enhanced Virtual Port Channels). I thought it would make a good blog entry to describe the differences of each, where they are used, and what platforms each is supported on.
"The separation of location and identity is a step which has recently been identified by the IRTF as a critically necessary evolutionary architectural step for the Internet."
- N. Chiappa in draft-chiappa-lisp-introduction-00An example would be that my IPv6 prefix 2001:67c:208c:10::/64 (the 'who') currently is located behind the following WAN IP addresses: 62.194.155.106, 217.8.107.2 and 2001:67C:21B4:1::2 (the 'where'). In this example my prefix is multi-homed behind 3 connections, and I'm doing IPv6 over IPv4 next to IPv6 over IPv6. This is possible because this single IPv6 prefix can have multiple Routing Locators (the 'where') and LISP is address-family agnostic.
Many real time applications such as VOIP, gaming, teleconferencing, and performing music together, require low latency. These are increasingly unusable in today’s internet, and not because there is insufficient bandwidth, but that we’ve failed to look at the Internet as a end to end system. The edge of the Internet now often runs congested. When it does, bufferbloat causes performance to fall off a cliff.
Where once a home user’s Internet connection consisted of a single computer, it now consists of a dozen or more devices – smart phones, TV’s, Apple TV’s/Roku devices, tablet devices, home security equipment, and one or more computer per household member. More Internet connected devices are arriving every year, which often perform background activities without user’s intervention, inducing transients on the network. These devices need to effectively share the edge connection, in order to make each user happy. All can induce congestion and bufferbloat that baffle most Internet users.
The CoDel (“coddle”) AQM algorithm provides the “missing link” necessary for good TCP behavior and solving bufferbloat. But CoDel by itself is insufficient to solve provide reliable, predictable low latency performance in today’s Internet.
Bottlenecks are most common at the “edge” of the Internet and there you must Continue reading
That was it! My work life has an absolute peak every year and that’s when I’m again fortunate enough to visit Cisco Live in the US. This year it was held in San Diego, California.
I flew in on Saturday with 2 colleagues on LA and drove to San Diego after a quick tour around Sunset Boulevard ;)
We stayed at the Manchester Grand Hyatt, which is a hotel I can truly recommend when visiting San Diego. Services were good and staff was helpful!
My focus this year was to combine both Datacenter and Service Provider sessions as those are the fields I’m active in. I found that the SP related sessions had a quite smaller crowd attending them. I guess this is related as the SP customers are considered important customers and get a lot more attention from Cisco people, so they already know what to expect in terms of roadmap and technologies. Still I had quite some very good sessions where I learnt about the features (and limitations) about some cool new things :-)
Sunday
On Sunday it’s a special day as you need to purchase additional sessions called Techtorials. This was the first year I took a Continue reading