There are some specific reasons where we are utilizing an IPv6 for external connectivity but we have to perform the task to map the internal IPv4s to external IPs across a variety of client networks we have in order to add HyperV hosts to VMan directly. VMware is mostly unaffected as we already did this where needed to access from VCenter.
I found a document on thwack that mentioned IPv6 on the roadmap for VMan, but that was back in 2012. SAM and NPM apparently already have IPv6 Support.
I contacted SolarWinds Support and after checking internally, they state this is not currently happening and that this request should be filed instead.
IPv6 is not only the way of the future, but a necessity now that IPv4 has been exhausted. Please consider IPv6 support for immediate inclusion into VMan so we may add HyperV hosts and the like using IPv6 instead of IPv4.