By default, the Cluster Edition is IPv6-unaware. You must start the Cluster Edition with trace flag 7841 to make it IPv6-aware. This causes the Cluster Edition to determine IPv6 availability and makes the Cluster Edition IPv6-aware.
See your etwork or IT specialist to configure your platforms and network infrastructure correctly for IPv6 support.
A second trace flag, 7815 can be set when you start the Cluster Edition which captures and logs address connection requests and host / name lookups.
The IPv6 Cluster Edition trace flags:
T7841 – enable the Cluster Edition IPv6-awareness.
T7815 – report all the Cluster Edition IPv4 & IPv6 Client address connect requests.
Before starting the Cluster Edition for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, you can configure and enable an IPv6 connection handler. Configuring and enabling the IPv6 connection handler requires adding an additional DCL entry. A single Cluster Edition configuration can typically carry up to 32 connection handler assignments within the DCL.
For example if you have a Site-local setup with two domains administrated under the nameserver setup:
sybase.com - being responsible for all IPv4 networking applications v6.sybase.com - being responsible for all IPv6 networking applications
The DCL entry for the Cluster Edition to start a cluster named “SYBASE” on the host “revival” for port 17100 looks similar to:
SYBASE master tcp ether revival.sybase.com 17100 query tcp ether revival.sybase.com 17100 master tcp ether revival.v6.sybase.com 17100 query tcp ether revival.v6.sybase.com 17100
In the above example, when the Cluster Edition is started as IPv6-aware, it creates two connection handlers. One listens on port 17100 for incoming IPv4 client connection requests, and the other listens on port 17100 for incoming IPv6 client connection requests.
