Cisco recently launched two very interesting products: layer-3 routing for the Nexus 5000 switch and the Virtual Security Gateway (which is a fantastic solution that you’ll hear more about in my future posts). Sadly, both products support only IPv4.
I’m in this industry long enough to understand the need for “baby steps” and “focusing on what customers want” (and I know there are hundreds of great engineers within Cisco who know what needs to be done, but still have to read blog posts like this one), but launching critical products without IPv6 support after the IPv4 global address pool has already been depleted definitely doesn’t look futuristic (just for fun, you might want to watch John Chambers talking about Cisco’s IPv6 thought leadership).
Color-coded systems (like this one) seem to be popular, so here’s my current understanding of Cisco’s IPv6 Data Center readiness in (mostly rosy) vivid colors:
|Functionality||IPv6 readiness state|
|Routers||All WAN edge routers are IPv6 ready|
|Switches||Catalyst 6500, Nexus 7000|
|Nexus 5000 (no IPv6 routing), Nexus 1000V (no IPv6 PACL)|
|FWSM handles IPv6 on main CPU. No transparent mode.|
|Virtual Security Gateway filters IPv6 based on Ethertype|
|Email/Web security||IPv6 only supported by cloud-based Ironport solution (NAT64 anyone?)|
|Load balancers||Future IPv6 support promised on ACE30|
|NAT64||Stateless NAT64 on ASR1000 (pretty useless). No stateful NAT64 support.|
|WAN optimization||IPv6 not supported|
Have I missed something? Is the table incorrect? Please let me know!