IPv6 infrastructure

Dual Stack infrastructure implements both IPv4 and IPv6. This is the recommended infrastructure implementation for using Adaptive Server Enterprise as an IPv6-aware server.

Sybase applications are IPv6-aware. All code to turn Sybase™ Adaptive Server and the Open Client/Server components IPv6-aware was done using the IETF designed primitives.

The following matrix lists the platform run-time requirements and the specific product and its release version:

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 Adaptive Server Enterprise being IPv6-aware is a complex issue because some components within the ASE are 3rd party components and are not yet IPv6-aware. To understand how this impacts Adaptive Server Enterprise the following list shows all functional mechanisms of Adaptive Server Enterprise 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 Adaptive Server Enterprise do not support IPv6. These mechanisms in Adaptive Server Enterprise are IPv6-unaware. They will gradually (over time) be become IPv6-aware in follow-on releases:

• Java support

• License Management Server

• LDAP driver

Before starting Adaptive Server for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, an IPv6 connection handler can be configured and enabled. Configuring and enabling the IPv6 connection handler requires adding an additional DCL entry. A single Adaptive Server 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 name server setup:

sybase.com - being responsible for all IPv4 networking applications
v6.sybase.com - being responsible for all IPv6 networking applications

The DCL entry for Adaptive Server to start named “SYBASE” on the host “revival” for port 17100 would typically look like:

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 Adaptive Server is started with IPv6-awareness it creates two connection handlers. One listens on port 17100 for incoming IPv4 Clients connection requests, and the other listens on port 17100 for incoming IPv6 Clients connection requests.