® Sametime deployment can support IPv4 addressing, IPv6 addressing, or both protocols. The option you choose will determine how you configure the servers in your deployment.
Existing Sametime deployments use IPv4 addressing only. Rather than completely switch over to IPv6 addressing, you will probably want to phase it in and support both protocols for some time until you are satisfied with your IPv6 support. There are some requirements and limitations for each type of addressing, so review the sections below before implementing any changes.
IPv4 and IPv6 protocols
(Internet Protocol version 4) and IPv6
(Internet Protocol version 6) are names of protocols that define how you address computers on the Internet. The IPv6 protocol was introduced to provide not only a larger number of addresses for the increasing number of computers on the Internet, but also to enhance the security of Internet communications.
When entering an IPv4 address, you format it using four sets of digits, separated with dots like this:
IPv6 addresses use eight sets of hexadecimal digits separated with colons like this:
You may see IPv6 addresses abbreviated, for example:
- 2001:db8:85a3:0:0:8a2e:370:7334 where the leading zeros in each group are omitted
- 2001:db8:85a3::8a2e:370:7334 where two consecutive groups containing only zeros are represented by a double colon
- [2001:db8::]/64 where the suffix (/64) indicates the portion of the address that represents the network (the remainder of the address represents computers within that network)
If the URL includes a port, add the :port
value outside of the brackets like this:
Supporting IPv4–only addressing
Prior to release 8.0.2, Sametime products supported only IPv4 addresses, listening only for connections from clients using the IPv4 protocol and ignoring connections using the IPv6 protocol. An IPv4–only deployment requires no special configuration and can combine Sametime components from release 8.0.2 and later with those from prior releases.
Supporting both IPv4 and IPv6 addressing
Sametime release 8.0.2 introduced support for IPv6 addressing, but additionally continued support for IPv4 addressing. This allows you to update your Sametime deployment gradually by combining servers that support both protocols.
Even if a particular Sametime component is enabled only for IPv4 addressing, it can still communicate with IPv6–enabled servers within the deployment provided those servers also support IPv4 addressing (known as dual-support).
Enabling support for IPv6 addressing requires some additional configuration in your deployment. If you upgrade from an IPv6-enabled server in your Sametime deployment, you should verify that your IPv6 settings are still in place and modify them if needed.
When installing the Sametime
® System Console on a system that supports both IPv4 and IPv6 addressing, the IPv4 and IPv6 addresses associated with the Sametime
System Console must be mapped to the same host name. Additional host names cause problems in the Sametime
System Console because SSL certificates can be generated using either the IPV4 or IPV6 host name, which might not match during authentication.
Supporting IPv6–only addressing
If you choose to support only IPv6 addressing in your Sametime deployment, use the instructions in this section to enable IPv6. You will additionally need to disable support for IPv4 addressing by ensuring that your settings use values recommended for "IPv6 only" wherever that option is offered.
Enabling support for IPv6 addressing requires some additional configuration in your deployment. If you upgrade from an IPv6-enabled server in your Sametime deployment, you should verify that you IPv6 settings are still in place and modify them if needed.
Parent topic: Supporting IPv6 addressing in a Sametime deployment