- Unless it is a major new launch or a brand new product line I tend not to really focus on the spec bump launches from Cisco. However the Cisco Datacenter Blog has an interesting post on the new Nexus 3100 series. The highlight of the post is the platform architecture white paper, those tend to be very useful. The super unfortunate part is that you cannot download it without handing over your details, bummer.
- Another post from Cisco, the security blog this time, about onePK. onePK is an API framework for managing Cisco devices. This is part of the whole “SDN” universe which you could dedicate hundreds of blogs to appropriately cover. The Cisco Security blog has a series on onePK and a demo application (or is it just app now days?) on how to use it. Part 1 and Part 2.
- Of course Cisco isn’t the only one with a horse in the SDN race, VMware are out touting the GA of NSX. I’ll be looking at getting that going in my lab at some point but I feel I’ll need a deeper understanding of the hardware requirements in case I’m missing something. With that in mind VMware are showing off their visibility tools for networking and I have to admit, I’m pretty impressed. I think if you were a pure virtualisation shop (NSX is multi-hypervisor) then you’d be hard pressed to want another networking monitoring tool. Just look at the pretty pictures!
- It appears Hyper-V 2012 has a bug with the port mirroring feature, it might miss some packets. Aidan Finn has all the details, suffice to say, install KB2885541. I can only imagine the fun the engineer who discovered this bug had, a lot of head scratching went on I think!
- IPv6 seems to be one of those perpetually coming technologies, we ran out of IPv4 addresses long ago but people still seem to be resisting it at every turn for some reason. But learning IPv6 is still important (lets face it, if it does become big you will become one of the few to know anything about it) and Ed Horley at How Funky has a post on Unique Local Addresses (ULA). While I think it is a great primer I would agree with Andrew von Nagy in the comments, ULA seems best suited as an internal number scheme to provide stable addressing for internal resources. That seems the most logical to me.
That wraps up this edition but I’d like to leave you with a bonus link, the DevOps Reactions Tumblr. As this post will be out on a Friday I think everyone needs a good laugh. I’ve linked straight to one of my favourite ones, what to do when someone breaks the naming convention. I’d caution you though, you can easily get stuck on that site laughing and nodding your head as the time passes by. Almost as bad as TVTropes.org!