MQ Appliance DR between HA Pairs

The use of the 100Gb eth40 interface (available on the M2003 appliance) is not required. By default, HA replication uses the 10Gb eth21 interface and DR replication uses the 10Gb eth20 interface. There are several Ethernet interfaces available on the MQ Appliance and you can configure different interfaces to be used instead if you prefer. The example in our documentation illustrates that messaging applications and HA/DR replication will usually use different network interfaces. In the example, eth40 has been selected to be used by the messaging applications, but this is just an example. Your configuration can, and probably will, be different.

Thanks Jamie! one more q on same context

Let's say we have a scenario where we are not using preferred appliance on both the DR sites(primary & secondary). When going for manual DR scenario or natural DR where the QM can be started in DR remote site?

Will it be on the appliance where secondary DR QM command was run while doing the DR setup?

crtdrsecondary -m terentia1 -sx -s 1024 -l Hugin,Mugin -i 10.1.20.1,10.1.20.2 -p 2015 -t a -v 10.2.20.1,10.2.20.2

Or it can be started on any of the two appliances?

Or it can be started only on the Hugin appliance , as it is given first in the above command?

Thanks Jamie! one more q on same context

Let's say we have a scenario where we are not using preferred appliance on both the DR sites(primary & secondary). When going for manual DR secario or natural DR where the QM can be started in DR remote site?

Will it be on the appliance where secondary DR QM command was run while doing the DR setup?

crtdrsecondary -m terentia1 -sx -s 1024 -l Hugin,Mugin -i 10.1.20.1,10.1.20.2 -p 2015 -t a -v 10.2.20.1,10.2.20.2

Or it can be started on any of the two appliances?

Or it can be started only on the Hugin appliance , as it is given first in the above command?

Based off the doc: https://www.ibm.com/docs/en/mq-appliance/9.3?topic=cdrfoahag-example-network-set-up-hadr-configuration-two-ha-groups

is eth40 a new setup required?

Thanks Jamie for the confirmation. One last q on same context

So let's say we have a scenario we have not set preferred appliance on both the DR sites (primary & secondary) and when the DR managed failover or DR natural calamity happens?

Can the QM be started on any of the two appliances in DR remote side?

Or it depends on which DR remote appliance we have ran the below command ?

crtdrsecondary -m terentia1 -sx -s 1024 -l Hugin,Mugin -i 10.1.20.1,10.1.20.2 -p 2015 -t a -v 10.2.20.1,10.2.20.2

Or it depends whether Hugin, Mugin has been given in first in above command?

Thanks Jamie for confirmation. One more Q on same context -

So, let say if we don't set preferred appliance on both the DR sites(Primary & Secondary) HA group, And in a scenario when DR happens both managed or natural. Can the QM be started on any of the appliances DR remote site?

Or it can be only started on the appliance where below command we will run while setting up the DR

crtdrsecondary -m terentia1 -sx -s 1024 -l Hugin,Mugin -i 10.1.20.1,10.1.20.2 -p 2015 -t a -v 10.2.20.1,10.2.20.2

Or it depends in command we have put Hugin first or Mugin?

The same HA configuration options can be used irrespective of whether DR has also been configured. This means that you can set a preferred appliance for a queue manager in each of the HA groups, but it is optional and you can alternatively use the clearhapreferred command to specify that a HA queue manager has no preferred appliance. The configuration for each HA group is independent, so setting or clearing the preferred appliance in one of the HA groups has no effect on the other HA group.

To use this HA group feature at both the sites for a queue manager, do we need to set the qm as a preferred qm on an appliance or it can run as clearhapreferred qm on any appliance?

Support for configuring disaster recovery (DR) between high availability (HA) groups is available from version 9.3.2 of the MQ Appliance firmware. For more information see https://www.ibm.com/docs/en/mq-appliance/9.3?topic=cha-configuring-disaster-recovery-fail-over-another-high-availability-group.

This is a valid requirement, and something we hope to do in a future update to the appliance.