7 Enabling IPv6
This topic includes the following sections:
7.1 Overview
IPv6 is the next generation internet protocol. It fixes a number of problems in IPv4, such as the limited number of available IPv4 addresses. It also adds many improvements to IPv4 in areas such as routing and network autoconfiguration. IPv6 has strong mobile device support, and has attractive features for ISPs or Telecom companies, such as QoS and security. IPv6 is expected to gradually replace IPv4, with the two coexisting for a number of years during a transition period.
Note:
Oracle Tuxedo 11g Release 1 (11.1.1.0) only supports IPv6 basic functionality in this release. Advanced IPv6 features (for example, QoS and flow control) are not supported.Parent topic: Enabling IPv6
7.2 Enabling IPv6
A Tuxedo process can only supports one IP version at the same time. In order to switch between IPv4 and IPv6, you must use the TMUSEIPV6
environment variable. For more information, see tuxenv(5)
in the File Formats, Data Descriptions, MIBs, and System Processes Reference in the Tuxedo 11g Release 1 (11.1.1.0) Reference Guide.
The default value is n|N
(IPv4). If
TMUSEIPV6
is set to y|Y
IPv6 is used as
the network protocol.
TMUSEIPV6
can be set in the*MACHINES
,
*GROUPS
, *SERVERS
sections in the
UBBCONFIG file, or you can set it before booting Tuxedo.
Parent topic: Enabling IPv6
7.2.1 IPv6 Address Format
The following are valid IPv6 formats:
-
fe80:0:0:0:202:55ff:fecf:50b
-
fe80::202:55ff:fecf:50b
Tuxedo support two formats of V6 address:
//[IPv6 address]:port
//hostname:port
The IPv6 address in the URL is enclosed by square brackets. For hostname, it does not need to
be enclosed by square brackets. For example: //[fe80::202:55ff:fecf:50b]:9010
or//bjaix5:9010
You can use[::]
or [0:0:0:0:0:0:0:0]
as IPv6 wildcard
addresses. For example:
For a server booted on bjaix5 (a dual stack machine), the wildcard address can be
//[::]:60120
or //[0:0:0:0:0:0:0:0]:60120
The server listens on 60120
on all bjaix5 interfaces
(172.22.34.45
and fe80::202:55ff:fecf:50b
). It can accept
IPv6 and IPv4 protocol.
Parent topic: Enabling IPv6
7.2.2 Tuxedo Component IPv6 Support
Following Tuxedo components support IPv6:
- BRIDGE & BSBRIDGE
-
tlisten
- GWTDOMAIN
- WSL/WSH
- WS
- CERT-C
- Jolt
- ISL/ISH
- CORBA client
- SNMP
- SALT
- CORBA & ATMI SSL LDAP
Note:
Tuxedo invokes database XA call back to operate with database. For XA IPv6 depends on the database vendor support.WEBGUI is unsupported IPv6
Parent topic: Enabling IPv6
7.3 IPv4 and IPv6 Interoperability
Tuxedo supports the following TCP/IP address formats:
- IPv4 only
- IPv6 only
- IPv4 and IPv6 mixed environment
Note:
Windows 2000, 20003, and XP platforms do not support dual stack.
The following table summarizes IPv4 and IPv6 interoperability.
Table 7-1 IPv4 and IPv6 interoperability
IPv4 Server IPv4 Host Only | IPv6 Server IPv6 Host Only | IPv4 Server Dual Host Stack | IPv6 Server Dual Host Stack | |
---|---|---|---|---|
IPv4 client, IPv4-only host | IPv4 | No | IPv4 | IPv4(1) |
IPv6 client, IPv6-only host | No | IPv6 | No | IPv6 |
IPv4 client, dual-stack host | IPv4 | No | IPv4 | IPv4(1) |
IPv6 client, dual-stack host | IPv4 | IPv6 | IPv4(2) | IPv6 |
- On Linux and UNIX platforms, the server must listen using the IPv6 wildcard address (::).
- IPv6 client can connect to an IPv4 server on Dual-stack host with textual V4 IP address only (for example, //10.130.5.144:10002).
Parent topic: Enabling IPv6
7.4 Oracle Tuxedo MP Mode Interoperability
If a master uses IPv6 and NADDR & NLSADDR are configured as
//[IPv6 address]:port
, all slave nodes
must
use IPv6 as well. Slave nodes using IPv4
cannot start.
If master is using IPv4, all slave nodes must use IPv4 as well. Slave nodes using IPv6 cannot start.
Note:
Oracle Tuxedo MP mode cannot be configured using a wildcard address ([::]
) in UBBCONFIG. If you use a wildcard address in MP mode, tmloadcf
fails and an ERROR message is sent to ULOG.
Parent topic: Enabling IPv6