Abbreviated migration scenarios

 

This section gives some abbreviated scenarios for when you are thinking of installing WebSphere MQ V6.0.

 

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.

Using mapped addresses can require protocol translators in the IP network.

Effects of CONNAME and LOCLADDR settings
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 following table lists the abbreviations used in Table 3. The abbreviations in this table are combined in Table 3 to give the configuration of the systems involved in trying to establish communication. For example:

Abbreviations used in system configurations
Abbreviation Meaning
v53 a WebSphere MQ V5.3 or earlier queue manager
v6 WebSphere MQ V6.0 queue manager
   
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 hostname of system holding the responding queue manager
IPv6DNS DNS returns an IPv6 address only for hostname of system holding the responding queue manager
DualDNS DNS returns an IPv4 and IPv6 address for hostname 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

System configurations
Originating queue manager Responding queue manager Result
Queue manager and Stack LOCLADDR IPADDRV Queue Manager and Stack DNS Return  

v53 + IPv6

Any

Not applicable

   

IP Error

v53 + IPv4 or
v53 + Dual

Both
LOCLADDR4
&
LOCLADDR6

Not applicable

v53 + IPv4 or
v53 + Dual

IPv4DNS or
DualDNS

IPv4 connection can be
established

v53 + IPv4 or
v53 + Dual

Blank or
LOCLADDR4

Not applicable

v53 + IPv4 or
v53 + Dual

IPv4DNS or
DualDNS

IPv4 connection can be
established

v53 + IPv4 or
v53 + Dual

Blank or
LOCLADDR4

Not applicable

v53 + Dual

IPv6DNS

Unable to resolve
CONNAME

v53 + IPv4 or
v53 + Dual

Blank or
LOCLADDR4

Not applicable

v53 + Dual or
v6 + Dual
v6 + IPv4

IPv4DNS or
DualDNS

IPv4 connection can be
established

v53 + IPv4 or
v53 + Dual

LOCLADDR6

Not applicable

   

IP Error

v53 + IPv4 or
v53 + Dual

Blank or
LOCLADDR4
or both
LOCLADDR4
&
LOCLADDR6

Not applicable

v6 + IPv6

IPv6DNS

Unable to resolve
CONNAME

           

v6 + IPv4

Blank or
LOCLADDR4

Not specified

v53 + IPv4 or
v53 + Dual or
v6 + IPv4

IPv4DNS or
DualDNS

IPv4 connection can be
established

v6 + IPv4

LOCADD6

Not specified

   

Unable to resolve
LOCLADDR

v6 + IPv4

Blank or
LOCLADDR4

Not specified

v6 + IPv6

IPv6DNS

Unable to resolve
CONNAME

v6 + IPv6

Blank or
LOCLADDR6

Not specified

v53 + Dual

DualDNS

Attempts to start IPv6
channel and fails as there
will be no IPv6 listener
available

v6 + IPv6

Blank or
LOCLADDR6

Not specified

v53 + IPv4

IPv4DNS

Attempts to start IPv6
channel and fails as there
will be no IPv6 listener
available

v6 + IPv6 or
v6 + Dual

LOCLADDR6

Blank or
IPADDR6

v6 + IPv6 or
v6 + Dual

IPv6DNS or
DualDNS

IPv6 connection can be
established

v6 + Dual

LOCLADDR6

IPADDR4

v6 + Dual

IPv4DNS or
DualDNS

IPv6 connection can be
established where
mapped addressing can
be used

v6 + Dual

Blank or
LOCLADDR4

IPADDR4

v53 + Dual

IPv4DNS or
DualDNS

IPv4 connection can be
established

v6 + Dual

Both
LOCLADDR4
&
LOCLADDR6

Blank or
IPADDR4

v53 + Dual

IPv4DNS or
DualDNS

IPv4 connection can be
established

v6 + Dual

LOCLADDR4

IPADDR4

   

Unable to resolve
LOCLADDR

v6 + Dual

LOCLADDR6
or both
LOCLADDR4
&
LOCLADDR6

Blank or
IPADDR6

v6 + IPv6 or
v6 + Dual

IPv6DNS or
DualDNS

IPv6 connection can be
established

 

Parent topic:

Internet Protocol V6 (IPv6) migration


mi10230_