Table of Contents
This chapter describes IPv6 provided by Tmax.
This section describes the basic concept and features of IPv6 and dual stack, which is an IP conversion technology.
IPv6, a network-level protocol, is a next generation Internet protocol established as the Internet Protocol version 6. Due to the limitation of using IPv4 protocol for the Internet, which was used in the past, IETF established IPv6 protocol as the new protocol.
IPv4, expressed in 32 bits, can create 4,294,967,296 addresses. As the number of computers connected to the Internet has grown dramatically, IPv4 addresses have almost been exhausted. IPv6 has been suggested to resolve this issue.
IPv6, expressed in 128 bits, can create 3.4x10^38 addresses (2^128), which is close to infinity. With this many addresses, one IPv6/48 network can be provided per 10㎡ of surface area on the earth.
A big difference between IPv4 and IPv6 is how an address is expressed. An IPv6 address can be represented with a hexadecimal number that includes a colon(:) between every 16 bits (four digits).
2001:0db8:85a3:08d3:1319:8a2e:0370:7334
Until the conversion to IPv6 is complete, IPv4 and IPv6 networks will be used concurrently. To support both IPv4 and IPv6, the following technologies are provided by the basic platform vendors for OS, router, switch, etc.
IPv4/IPv6 dual stack is the easiest way to maintain compatibility between an IPv6 node and a IPv4 dedicated node. Since an IPv6/IPv4 dual stack node can send or receive both IPv4 and IPv6 packets, it is compatible with both IPv4 node and IPv6 node.
Tunneling is used for IPv6/IPv4 host and router to encapsulate IPv6 datagrams in an IPv4 packet, and transmit it through the IPv4 routing topology. Through tunneling, IPv6 packets can be transmitted through the existing IPv4 routing infrastructure.
IPv6 can be used in Tmax by configuring the necessary settings. IPv4 is the default protocol.
The settings can be applied to the environment variables and Tmax configuration files as needed. (Since configuration files cannot not be used for a client, environment variables must be configured for a client.)
In Tmax, client, multi-node, multi-domain, and tcp gateways are implemented using sockets. Each module can choose to use IPv4 or IPv6.
Each module can select to use IPv6 based on the following situations.
Accepting a connection
The following describes Tmax components and configuration depending on how a connection is accepted.
| Components | Description |
|---|---|
| cll | Receives a connection from a client.
|
| tmm, clh | Receives an inter-node connection in a multi-node environment.
Receives a connection from an extern server.
|
| racd | Receives a utility connection in a multi-node environment.
|
| webagent(twagent) | Receives a WebAdmin connection.
|
| gateway([non]tx, [async] tuxedo, [async] java, wsgw, xagw) | Receives a connection.
|
| hms | Receives a connection from hms cluster.
|
| tcp g/w | Receives a connection.
|
| tmsnmpd | Receives an SNMP-requested connection.
|
| Java components | Receives a connection from jtmax or webtasync. The java components must be set through environment variables when executing java. (To run them on WAS, they must be set to environment variables at startup.)
|
Requesting a connection
The following describes Tmax components and configuration according to how the connection is requested.
| Components | Description |
|---|---|
| c client | Requests a connection to Tmax.
|
| tmm | Connects to another node(tmm) in a multi-node environment.
|
| clh | Connects to another node(clh) in a multi-node environment.
|
| tdl | Connects to another node in a multi-node environment when executing the tdl utility.
|
| hms | Connects to HMS of another node in a clustered HMS environment.
|
| xa client | Connects to the xa gateway.
|
| tcp g/w | Connects to an external server.
|
| gateway([non]tx, [async] tuxedo, [async] java) | Connects to another gateway.
|
| gateway(wsgw) | Connects to the Web Service server.
|
| Java components | Requests a connection to jtmax, webtasync, or twadmin. The java components must be set through environment variables when executing java. (To run them on WAS, they must be set to environment variables at startup.)
|
If IPv6 support is configured, Tmax creates a socket for IPv6. If a platform where Tmax is installed provides a conversion technology like dual stack, Tmax can receive a connection request through both IPv4 and IPv6. If IPv6 is not configured for Tmax even though the platform supports both IPv6 and IPv4, Tmax can receive only IPv4 connections.
Tmax supports other IPv6 related features, in addition to the aforementioned connection and transmission related features, for inputting and searching for information, such as ci information, in ACL or tmadmin.
The following are additional features for IPv6.
ACL
Limits client connection IP.
Supports IPv6 addresses in a separate configuration file.
Specified as [2011::xxx].
tmadmin
| Command | Description |
|---|---|
| ci | Outputs the IP of a connected client. |
| txgwi, ntxgwi, jgwi, ajgwi | Outputs the IP of a connected gateway. |
| sqi | Outputs the client IP of Session Q. |
client and server API
| API | Description |
|---|---|
| tpgetsockname | Retrieves the socket address, which is used internally by Tmax, from the server or client. Refer to Tmax. "3.1.54. tpgetsockname" for detailed information. |
| tpgetpeername | Retrieves the socket address of the peer to which a socket is connected from the server or client. Returns the peer socket address (node) after connecting to Tmax. Refer to Tmax. "3.1.52. tpgetpeername" for detailed information. |
| tpgetpeer_ipaddr | Retrieves the socket address of the peer node from the server. Refer to Tmax. "3.2.34. tpgetpeer_ipaddr" for detailed information. |
| tpgetcliaddr_ipv6 | Retrieves the port number and IP of the client that corresponds to the clid among the clients connected to Tmax. Refer to Tmax. "3.1.47. tpgetcliaddr_ipv6" for detailed information. |
| tpbroadcast | Sends an unrequested message to all clients registered on Tmax. Refer to Tmax. "3.1.29. tpbroadcast" for detailed information. |
| tmadmin | Outputs statistical information that can be queried in tmadmin, a Tmax management tool. Refer to Tmax. "3.2.4. tmadmin" for detailed information. |