Please use this thread to share your IPv6 plans to help us prioritize our roadmap and ensure we're taking your specific use-cases into account - be sure to include answers to the following in any post:
I am a technical consultant working for an MSP in the UK. Have been running IPv6 in a test network for a few months and I am planning to push this to projects to roll out shortly.
* Planning to roll it out in phases, firstly enable all network infrastructure such as switches, routers and firewalls. Then the 2nd phase will be the servers both physical and virtual. 3rd phase will be client workstations.
* In the coming months, would be good to have it up and running by IPv6 day, but that is optimistic.
* There is still a lot of software which doesn't support it. For example Exchange 2003 doesn't support it at all, Exchange 2007 only supports it on Server 2008. And of course, Orion.
Really interested in getting some testing done of any IPv6 functionality that will be available in Orion.
Background: Our company runs Solarwinds as a to support our managed services for several customers. One of the hurdles with managing multiple customers has been dealing with RFC1918 IP conflicts. Many of our customers have already deployed elaborate IP addressing schemes, and unfortunately many of them conflict. (The 10.0.0.0/8 space is very popular, especially the subnet zero space). Our existing solution to managing these devices involves an elaborate NAT and manual translation tables that are incredibly hard to manage and difficult to scale... I won't get into those specifics here.
Since we own the management of our customers network devices one solution to managing (includes monitoring) their environment more effectively is to configure their network infrastructure to support IPv6 in a dual-stack architecture. Not one of our customers has encountered a need to deploy v6 so this would be very easy to implement and we could control the design and allocation as to avoid conflicts!
In preparation for this we have already deployed dual-stack 6/4 configurations internally and we are fully functional internal. We have a plan to stand up new customer environments with similar dual-stack configurations, and have set a schedule for a phased approach into existing customers networks.
Solarwinds ipv6 support is critical for us! It will greatly enhance our ability to scale our offering without the headache of managing NAT translations and the manual interpretation of them (i.e. 172.16.8.199 in solarwinds = 10.0.1.99 in Customer A's environment).
In short the answers to your questions are:
1. already rolling out, remaining elements (customers) will be phased.
3. Rolling out v6 dual-stack configurations to thousands of customer network devices and the eventual host configurations to support v6.
Thanks for your efforts and thanks for making IPv6 support a priority!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.