Building network automation solutions

9 module online course

Start now!

Another Nexus 1000V IPv6 FAIL

The keynote speeches during this week’s Cisco Live Europe were full of data centers, virtualization and cloudy promises. Mysteriously absent was IPv6; looks like a 15 year old protocol is no longer sexy enough to be mentioned.

Cisco’s execution obviously follows its vision – new version of Nexus 1000V software was released at the same time. Limitations and Restrictions section is very clear: IPv6 ACLs are still not supported. Is this a sign of a deliberate IPv6-less Data Center strategy or is it something different?

In totally unrelated news, the last two blocks of IPv4 address space have been allocated to APNIC this week, triggering the allocation of the remaining five blocks to regional RIRs; the event lovingly known as IPocalypse. So far, I haven’t seen a reasonable alternative to IPv6, so I guess we’re stuck with it for good.

But maybe it’s all part of a grand vision: lack of IPv6 in data centers might trigger faster embracement of cloud services. Or maybe not ... in the next totally unrelated bit of (missing) news, Amazon EC2 still lacks native IPv6 connectivity.

Fortunately for the enterprise networking engineers, some companies did manage to combine two seemingly unrelated visions: if you need to offer your legacy IPv4 data center applications to the brave new world of IPv6 clients, F5 will be more than happy to sell you a few (field-tested) BIG IP boxes. After all, if they’re good enough for Facebook, they just might survive your traffic load as well.

And the last totally unrelated item (this time a shameless plug): if you need to understand how IPv6 will impact your enterprise network, register for my new Enteprise IPv6 – the First Steps webinar.


  1. It's just marketing, now buy new datacenter equipment and the we will sell you new with IPv6 support. Easy as that.
  2. Fail for sure especially because there are a number of enterprises/governments that have been putting IPv6 support as a mandatory requirement. But also, like you mentioned, we have multiple vendors in the market so I'm sure we can skip Cisco if we want so it's not the end of the road.

    But what I think it's happening is that even VSphere IPv6 support is not at the same level as IPv4 (but getting there) so Cisco might be thinking: - the market is not going to migrate from IPv4 to IPv6 tomorrow, maybe not even during next 12 months... slowly they'll introduce it but the biggest market share will still cover IPv4 scenarios so we have one, maybe two, years in front of us to come up with a new Nexus xxxxV product line.

    Or maybe I'm wrong and they just don't care!
  3. IPv6 was perhaps not mentioned in the keynotes.
    However, in almost all sessions (atleast the ones I went to), weather they were related to IPv6 in some way or not, IPv6 was mentioned. And in general the audience was very aware of this, because for products that do not have IPv6 capability there were always some people asking "ok, but what about IPv6", in every session that I attended.
    (And it seems that the ace team is going to do something about this as well... even though they are "a bit" behind...)
    And wireless network at Live was ipv4/ipv6, so we had native ipv6 internet connectivity.
Add comment