Collection of useful, relevant or inane places on the the Internets for 7 Oct 2011:
- The Reason Enterprises Aren’t Deploying IPv6 – Ethan Banks at Packet Pushers –
What’s the kick in my pants to deploy IPv6 at my enterprise? Does my company need IPv6 to do business with other companies? No. Are there mission-critical resources available to my business only through IPv6? Nope. Will my company reach a new market upon deploying IPv6? No again.
- Big Switch Network, OpenFlow, and Virtual-Networking – Simply great post from Derick Winkworth after spending some time BigSwitch learning about OpenFlow
With these two points in mind, I have decided that OpenFlow has what it needs to support real separation for SP-like L2VPN/L3VPN virtualization. With the introduction of support in v1.1 for stacked MPLS and VLAN tags, OpenFlow can also provide for differentiation on the wire and integration with existing M(T/SZ) networks. It will be up to the vendors of the controllers to ensure that the controller meets the IETF (and other standards bodies’) security standards for M(T/SZ) networks.
- Show 66 – VXLAN and NVGRE with Ken Duda –
I wanted to know more about VXLAN and NVGRE so who better than [Ken Duda](http://aristanetworks.com) from Arista Networks, the only author listed on both IETF RFCS and [Ivan Pepelnjak](http://blog.ioshints.info) on a call to go fast and loose on the topics.
- Of Network Innovation, Unicorns, and Nirvana | Ethernet Fabric – Disagree. Automation is already here, and orchestration is the unknown.
Of course, in the modern data center the various infrastructure domains don’t get to exist as their own discrete little coils: they’re all twisted together in at least a triple helix, which means that significant change in one domain will forcibly pull along the others at a faster rate. The big change, of course, is mass adoption of server virtualization. The medium follow-on change is the importation of fabric principles into the Ethernet world. Some parts of that will have longer-range impact on network evolution than others.
- Not All Servers Are Alike (With DNA) – Software switching has a problem – hardware architecture. Here are the numbers:
Today thanks to Donald Skidmore of Intel we have found a way to measure whether a certain server is adequate (from the hardware point of view) for the wire rate in particular with small packets. The problem is apparently due to the memory bandwidth that on some systems is surprisingly limited. It is worth to remark that memory type/speed is important but it is also important how this memory is connected to the rest of the system.
- The Network is a Blinky Light: VMWare is terrible at actual virtual-networking –
More generally speaking, while VMWare has most certainly helped spur the current virtualization and cloud movement, they have failed to really embrace virtual networking in a meaningful or coherent way in-line with existing network virtualization technologies (such as MPLS or Q-in-Q). In the meantime many enterprises have adopted these technologies.
Where have we heard this before ?
- Marked: MultiMarkdown preview, everywhere – One of my favourite MAC apps for munging Markdown formatted text.
Introducing Marked. Marked opens MultiMarkdown, Markdown, Text or HTML files and previews them as HTML documents. It watches the file for changes, updating the preview any time the file is saved. With a full set of preview styles, Marked adds an ideal “live” Markdown preview to any text editor. Plus… copy HTML with a keystroke, save to PDF or Print, or export to HTML in seconds.
- Cisco Blog » Blog Archive » Digging Deeper into VXLAN, Part 1 – First in a series of Blog Posts from Omar Sultan at Cisco ( You can the man out of CCIE, but can’t take the CCIE out of the man)
Yes, I am still talking about VXLAN, rather you folks are still talking about VXLAN, so I thought its worthwhile digging deeper into the topic since there is so much interest out there. There also still seem to be a fair number of misconceptions around VXLAN, so let’s see what we can do to clear things up.
- Coding Relic: VXLAN Part Deux –
This is the second of several articles about VXLAN. I have not been briefed by any of the companies involved, nor received any NDA information. These articles are written based on public statements and discussions available on the web.I strongly recommend reading the first article before this one, to provide background.
- HP Blogs – Intelligent Resilient Framework rocks: boosting vM… – The HP Blog Hub– I have several problems with this article. But mostly its trying way to hard to point that HP IRF is a performance boost. This is true of any MLAG technology using Big Brother fabric ideas.Of course IRF is faster, it uses all available bandwidth where STP would block redundant paths. It also refers to a data sheet for failover time instead of testing it too
The HP IRF datasheet touts a 50ms failover time. Consistently we were able to show failover times of less than 10ms and in some cases less than 1ms! Incredible! This is as good as, if not better than, much higher-end, much more expensive technologies like SONET and MPLS TE!!
IRF is cool technology in that it will, one day, scale up to eight chassis. This is overegging the pudding. HP needs to make to most of what is has and not try to outrun itself. There are great features in their products but this isn’t bringing them out.