Considerations when implementing IPv6 in a network

 

This section lists some things that you should consider when you are thinking of installing WebSphere MQ V6.0 on an IPv6 network.

• To ensure consistency across the network, you should plan the introduction of IPv6 for the whole network, especially where clusters are involved. For example, although a queue manager is now IPv6 capable, this doesn't imply that the queue managers it can communicate with are also IPv6 capable.

• When setting the domain name server (DNS) or equivalent, consider whether the system on which the target queue manager is running can resolve to an IPv4 address, an IPv6 address or a dual IPv4 and IPv6 address.

• If the system that you are installing WebSphere MQ V6.0 on does not support IPv6, WebSphere MQ V6.0 will only be able to connect using IPv4.

• For a queue manager running on an IPv6 enabled system to be able to communicate with a queue manager running on an IPv4 enabled system, the IPv4 enabled system must have a hostname that resolves to an IPv4 address only.

• If there are multiple domain name servers in a WebSphere MQ network, each hostname used in a channel definition must resolve to the same address (or addresses), regardless of which DNS is used.

• If the hostname used in a channel definition resolves to a system which hosts a queue manager from WebSphere MQ V5.3 or earlier, the hostname must resolve to an IPv4 address only.

 

Parent topic:

Internet Protocol V6 (IPv6) migration

mi10200_