This document is one of several that details major new or changed features in Enterprise Vault (EV) as of 9.0.3. This document covers the changes made to Enterprise Vault in order to support IPv6 networks.
Feature Description
Enterprise Vault has supported IPv6 networks since EV 9.0.3. The product code for Enterprise Vault core server modules, Accelerator and end-user interfaces has been updated to work seamlessly on IPv6 networks. Some limitations current apply; see section Licensing and support considerations later in this document.
Business Value
Enterprise Vault and associated Accelerator products usually work within a company’s internal network, and therefore are not constrained by the availability of IP addresses required when working on public networks. However the need for a larger IP address range is ever increasing and along with improvements in security and network management the IPv6 protocol is likely to become more common place. Today many federal agencies will only deploy software and hardware that supports IPv6 networks.
Underlying Principles
IPv6 uses a 128-bit network addressing scheme, compared to the 32-bit addressing scheme used by IPv4. In order to address this different range components within Enterprise Vault had to be updated to work with either a pure IPv6 network or a dual-stack IPv4/IPv6 hybrid network.
Along with code changes to API interfaces, several changes were made to the Graphical User Interface (GUI) to accommodate the 128-bit addressing range.
Test Drive
There are no special steps required to configure IPv6 after installing EV. If an IPv6 address is required then the address simply needs to be specified through the administration or configuration GUI. The following screenshot shows an example where the SQL server address is in IPv6 format.
Licensing and support considerations
For more information on current components of the product that support IPv6 please rerfer to the support matrix in the Related articles section.
Related Knowledge Base Articles
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.