Abbreviated migration scenarios
This section gives some abbreviated scenarios for when you are thinking of installing clusters on IBM® MQ
Abbreviated scenarios: Effects of CONNAME and LOCLADDR settings
The following table provides an overview of what will occur for the different TCP/IP stacks (IPv4 only, IPv6 only and dual IPv4 and IPv6 stacks) and given the settings for CONNAME and LOCLADDR the expected connection result.
Note: Using mapped addresses can require protocol translators in the IP network.
| Stack Type | CONNAME setting | LOCLADDR setting | Connection result |
|---|---|---|---|
| IPv4 only stack | IPv4 address | Channel binds to IPv4 stack | |
| IPv6 address | Channel fails to resolve CONNAME | ||
| Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv4 stack | ||
| IPv4 address | IPv4 address | Channel binds to IPv4 stack | |
| IPv6 address | IPv4 address | Channel fails to resolve CONNAME | |
| Host name resolves to both IPv4 and IPv6 addresses | IPv4 address | Channel binds to IPv4 stack | |
| Any address | IPv6 address | Channel fails to resolve LOCLADDR | |
| IPv4 address | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv4 stack | |
| IPv6 address | Host name resolves to both IPv4 and IPv6 addresses | Channel fails to resolve CONNAME | |
| Host name resolves to both IPv4 and IPv6 addresses | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv4 stack | |
| Dual IPv4 and IPv6 stack | IPv4 address | Channel binds to IPv4 stack | |
| IPv6 address | Channel binds to IPv6 stack | ||
| Host name resolves to both IPv4 and IPv6 addresses | Channel binds to stack determined by IPADDRV | ||
| IPv4 address | IPv4 address | Channel binds to IPv4 stack | |
| IPv6 address | IPv4 address | Channel fails to resolve CONNAME | |
| Host name resolves to both IPv4 and IPv6 addresses | IPv4 address | Channel binds to IPv4 stack | |
| IPv4 address | IPv6 address | Maps an IPv4 CONNAME to an IPv4 mapped IPv6 address. IPv6 implementations that do not support IPv4 mapped IPv6 addressing fail to resolve CONNAME | |
| IPv6 address | IPv6 address | Channel binds to IPv6 stack | |
| Host name resolves to both IPv4 and IPv6 addresses | IPv6 address | Channel binds to IPv6 stack | |
| IPv4 address | Host name resolves to both IPv4 and IPv6 addresses | Maps an IPv4 CONNAME to an IPv4 mapped IPv6 address. IPv6 implementations that do not support IPv4 mapped IPv6 addressing fail to resolve CONNAME | |
| IPv6 address | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv6 stack | |
| Host name resolves to both IPv4 and IPv6 addresses | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv6 stack | |
| IPv6 only stack | IPv4 address | Maps an IPv4 CONNAME to an IPv4 mapped IPv6 address. IPv6 implementations that do not support IPv4 mapped IPv6 addressing fail to resolve CONNAME | |
| IPv6 address | Channel binds to IPv6 stack | ||
| Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv6 stack | ||
| Any address | IPv4 address | Channel fails to resolve LOCLADDR | |
| IPv4 address | IPv6 address | Maps an IPv4 CONNAME to an IPv4 mapped IPv6 address. IPv6 implementations that do not support IPv4 mapped IPv6 addressing fail to resolve CONNAME | |
| IPv6 address | IPv6 address | Channel binds to IPv6 stack | |
| Host name resolves to both IPv4 and IPv6 addresses | IPv6 address | Channel binds to IPv6 stack | |
| IPv4 address | Host name resolves to both IPv4 and IPv6 addresses | Maps an IPv4 CONNAME to an IPv4 mapped IPv6 address. IPv6 implementations that do not support IPv4 mapped IPv6 addressing fail to resolve CONNAME | |
| IPv6 address | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv6 stack | |
| Host name resolves to both IPv4 and IPv6 addresses | Host name resolves to both IPv4 and IPv6 addresses | Channel binds to IPv6 stack |
Abbreviated scenarios: System configurations
Table 3 gives a number of abbreviated scenarios based on the configuration of the installed queue managers and the IP configuration they are running on. The list is not intended to be exhaustive, but to give a number of examples of what to expect based on the configurations shown.
The abbreviations are combined in Table 3 to give the configuration of the systems involved in trying to establish communication. For example:
- v71 + IPv6: Represents a queue manager from an earlier version of the product on a system with a TCP/IP 6 stack
- v8 + Dual: Represents a queue manager from the latest version of the product on system with a dual TCP/IP 4 and 6 stack
| Abbreviation | Meaning |
|---|---|
| v71 | queue manager from an earlier version of the product |
| v8 | queue manager from the latest version of the product |
| IPv4 | a system using an IPv4 only stack |
| IPv6 | a system using an IPv6 only stack |
| Dual | a system using both an IPv4 and an IPv6 stack |
| IPv4DNS | DNS returns an IPv4 address only for host name of system holding the responding queue manager |
| IPv6DNS | DNS returns an IPv6 address only for host name of system holding the responding queue manager |
| DualDNS | DNS returns an IPv4 and IPv6 address for host name of system holding the responding queue manager |
| LOCLADDR4 | The LOCLADDR parameter is set to IPv4 addressing |
| LOCLADDR6 | The LOCLADDR parameter is set to IPv6 addressing |
| IPADDR4 | IPADDRV is set to IPv4 addressing |
| IPADDR6 | IPADDRV is set to IPv6 addressing |
| Originating queue manager | Responding queue manager | Result | |||
|---|---|---|---|---|---|
| Queue manager and Stack | LOCLADDR | IPADDRV | Queue Manager and Stack | DNS Return | |
|
v71 + IPv6
|
Any
|
Not applicable
|
IP Error
|
||
|
v71 + IPv4 or
v71 + Dual |
Both
LOCLADDR4 & LOCLADDR6 |
Not applicable
|
v71 + IPv4 or
v71 + Dual |
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v71 + IPv4 or
v71 + Dual |
Blank or
LOCLADDR4 |
Not applicable
|
v71 + IPv4 or
v71 + Dual |
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v71 + IPv4 or
v71 + Dual |
Blank or
LOCLADDR4 |
Not applicable
|
v71 + Dual
|
IPv6DNS
|
Unable to resolve
CONNAME |
|
v71 + IPv4 or
v71 + Dual |
Blank or
LOCLADDR4 |
Not applicable
|
v71 + Dual or
v8 + Dual v8 + IPv4 |
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v71 + IPv4 or
v71 + Dual |
LOCLADDR6
|
Not applicable
|
IP Error
|
||
|
v71 + IPv4 or
v71 + Dual |
Blank or
LOCLADDR4 or both LOCLADDR4 & LOCLADDR6 |
Not applicable
|
v8 + IPv6
|
IPv6DNS
|
Unable to resolve
CONNAME |
|
v8 + IPv4
|
Blank or
LOCLADDR4 |
Not specified
|
v71 + IPv4 or
v71 + Dual or v8 + IPv4 |
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v8 + IPv4
|
LOCADD6
|
Not specified
|
Unable to resolve
LOCLADDR |
||
|
v8 + IPv4
|
Blank or
LOCLADDR4 |
Not specified
|
v8 + IPv6
|
IPv6DNS
|
Unable to resolve
CONNAME |
|
v8 + IPv6
|
Blank or
LOCLADDR6 |
Not specified
|
v71 + Dual
|
DualDNS
|
Attempts to start IPv6
channel and fails as there will be no IPv6 listener available |
|
v8 + IPv6
|
Blank or
LOCLADDR6 |
Not specified
|
v71 + IPv4
|
IPv4DNS
|
Attempts to start IPv6
channel and fails as there will be no IPv6 listener available |
|
v8 + IPv6 or
v8 + Dual |
LOCLADDR6
|
Blank or
IPADDR6 |
v8 + IPv6 or
v8 + Dual |
IPv6DNS or
DualDNS |
IPv6 connection can be
established |
|
v8 + Dual
|
LOCLADDR6
|
IPADDR4
|
v8 + Dual
|
IPv4DNS or
DualDNS |
IPv6 connection can be
established where mapped addressing can be used |
|
v8 + Dual
|
Blank or
LOCLADDR4 |
IPADDR4
|
v71 + Dual
|
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v8 + Dual
|
Both
LOCLADDR4 & LOCLADDR6 |
Blank or
IPADDR4 |
v71 + Dual
|
IPv4DNS or
DualDNS |
IPv4 connection can be
established |
|
v8 + Dual
|
LOCLADDR4
|
IPADDR4
|
Unable to resolve
LOCLADDR |
||
|
v8 + Dual
|
LOCLADDR6
or both LOCLADDR4 & LOCLADDR6 |
Blank or
IPADDR6 |
v8 + IPv6 or
v8 + Dual |
IPv6DNS or
DualDNS |
IPv6 connection can be
established |