This topic includes the following sections:
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 10g Release 3 (10.3) only supports IPv6 basic functionality in this release. Advanced IPv6 features (for example, QoS and flow control) are not supported. |
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 10g Release 3 (10.3) 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.
The following are valid IPv6 formats:
Tuxedo support two formats of V6 address:
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
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.
Following Tuxedo components support IPv6:
Notes: | Tuxedo invokes database XA call back to operate with database. For XA IPv6 depends on the database vendor support. |
Note: | WEBGUI does not support IPv6 |
Tuxedo supports the following TCP/IP address formats:
Note: | Windows 2000, 20003, and XP platforms do not support dual stack. |
Table 7-1 summarizes IPv4 and IPv6 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. |