•
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.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.TMUSEIPV6 can be set in the *MACHINES, *GROUPS, *SERVERS sections in the UBBCONFIG file, or you can set it before booting Tuxedo.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:9010or //[0:0:0:0:0:0:0:0]:60120The 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.
•
•
•
•
•
•
•
• Table 7‑1 summarizes IPv4 and IPv6 interoperability.
Table 7‑1 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.