Dual Stack infrastructure implements both IPv4 and IPv6. This is the recommended infrastructure implementation for using the Cluster Edition as an IPv6-aware server.
Sybase applications are IPv6-aware. All code to turn the Cluster Edition and the Open Client/Server components IPv6-aware was done using the IETF designed primitives, see “Creating or converting for IPv6-aware applications.” The following matrix lists the platform run-time requirements and the specific product and its release version:
Platform |
the Cluster Edition IPv6 awareness |
Open Client/Server IPv6 awareness |
---|---|---|
Sun Solaris 8 32- and 64- bit |
12.5.3a and 15.0 |
12.5 and 15.0 |
HP-UX 11i(v1) 32- and 64-bit |
12.5.3a and 15.0 |
12.5 and 15.0 |
Microsoft Server 2003 |
12.5.3a and 15.0 |
12.5 and 15.0 |
Linux RHEL 3.0 |
15.0 |
12.5 and 15.0 |
Many Sybase products that are Open Client/Server based like XP Server, Backup Server, Replication Server and Open Switch became automatically IPv6-aware due to the layered Open Client Transport Control Layer (CTlib->NETlib) which is IPv6-aware for network-socket operations. An important note is that any DBlib based Open Client product is not IPv6-aware.
For the Cluster Edition, being IPv6-aware is a complex issue because some components within the server are 3rd party components and are not yet IPv6-aware. To understand how this impacts the Cluster Edition, the following list shows all functional mechanisms of the Cluster Edition that are IPv6-aware with respect to the platform / release matrix above:
Connection Handler
RPC mechanisms
Job Scheduler Task / Agent session connection
Network Host API
UDP Message support for sybsendmsg
Component Integration Services connectivity
Host / name resolving
XML URL connection handler
Auditing for client address data
The following functional mechanisms in the Cluster Edition do not support IPv6. These mechanisms in the Cluster Edition are IPv6-unaware:
Java support
License Management Server
LDAP driver
Private interconnect among various instances in cluster.