Support for IPv6 in the source and destination address of flows

FormerIdeaCreator

Other requests on thwack for IPv6 support:

http://thwack.solarwinds.com/message/162351#162351

http://thwack.solarwinds.com/message/107547#107547

Find more posts tagged with

prodfr

Status: None

Comments

jbboatright

IPv6 support is mandatory for the U.S. Federal Agencies and the first major deadline for supporting public facing services is 9/30/2012 and FULL LAN IPv6 support is in 2014. It doesn't even sound like IPv6 support is "On the roadmap for future support" yet (as of the blog entry on 67/2012) . If SolarWinds can't fully support IPv6 with NTA , the customers have no choice to look to other vendors (who have rightfully come to the conclusion that this IPv6 "thing" might actually be around for a few years) and their respective products for their future network management needs. The longer that Solar WInds continues to be "gauging demand to determine prioritization for IPv6 support", the shorter the customers will be "gauging the potential role of the SolarWinds products in their future network management architectures". The US Government Agencies already technically can't procure any products that aren't on the NIST USGv6 registry for compliant products without an involved waiver process.

wwwrspecht

I am already struggling from lack of IPv6 with NTA, it's not at a critical level yet but it will be steadily getting worse over time. I agree with jbboatright's point that SolarWinds should not gauge this just on input from current users, they should consider the fact that they may be losing potential customers because of lack of support for IPv6. That restricts our community and is not good in the long term.

CaptainOrion

As an employee at a U.S. Federal agency IPv6 support is important to us. Current and future purchases must be IPv6 compatible.

gonnason

This shouldn't even require a vote. Get on with it already.

tkellar

I am throwing in my positive vote. Our corporation has been running IPv6 for some time. It is horrible that we do not have a means for identifying this given the true benefits of Netflow. Without it...we are running blind. I have decided that until Solarwinds supports it...to evaluate other products that perform IPv6 netflow analysis and run in there. I understand Solarwind's position...not that many in the IPv6 market. However, that will change...especially for ISPs and the U.S. government.

FormerMember

Almost all other SolarWinds products support IPv6, how come there is no support on NTA? We are fully IPv6 enabled and are looking forward to have this feature added as soon as possible.

foonly

Bump!

I also work at a federal agency. We need IPv6 support especially in NTA for troubleshooting.

Also see https://thwack.solarwinds.com/ideas/3938 IPAM Neighbor Cache (Can't scan a /64!)

and https://thwack.solarwinds.com/ideas/3939 IPAM DHCPv6

classclownfish

Our environment is almost exclusively IPv6 and this is a major gap in NTA's capabilities. Until IPv6 is supported, NTA is just about useless for us. I just wish I'd thought to confirm that v6 was supported (I mistakenly assumed it was, because even our old NetFlow tools from tiny companies support it) before I pushed to purchase this product

jordandalley

A bit of a drawback that NTA doesn't support IPv6....

analogfire

With both IPv4 and IPv6 peering upstream to internet this lack of support really limits visibility. Any updates on committing to a roadmap?

rrawdon

+1 here too - we are on track to switch to a competing flow analysis tool due to this and other shortcomings.

cresveld

Since IPv6 is becoming more and more normal, why isn't this still in Solarwinds?

This really is a must have nowadays

ndubois

We really need this feature ! It is useless to have a tool that don't show us a big part of the flows.

ferrashoo

Crossing my fingers. Hope this gets and update.

mitchell.clouatre

Not being able to view ipv6 flows limits us from pushing this out to customers. Is there any kind of roadmap as to when we should expect to see this update?