cancel
Showing results for 
Search instead for 
Did you mean: 
itagsupport
Level 9

MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hi all

We have a running MWG 7.1.0.x cluster (Proxy HA with 2 nodes WW5500) with no problems for production (PROD).

Now we would like to build another Proxy HA cluster (2 nodes WW1100) for testing (TEST) on the same IP subnet (same broadcast domain).

  • Is this possible on the same subnet? (Normally each node of TEST cluster propagates itself as a scanner using broadcasts, also to the PROD cluster what disturbes operation of prod traffic, shown with "mfend-lb -s")
  • If Yes, how are the settings under Central Mgmt Config and Proxies (HTTP) ?
  • Do we need to use different "Group runtime", "Group update" and "Group network" values for PROD and TEST clusters?

Thanks for any answers.

Tom

0 Kudos
1 Solution

Accepted Solutions
itagsupport
Level 9

Re: MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hi Andre

Today we took the PROD and the TEST clusters online.

All works fine now with different MFEND_LBID='61' für PROD nodes and MFEND_LBID='62' for TEST nodes defined in file /etc/sysconfig/mfend .

Btw, we also changed the VRRP Router ID from the default 51 to 61 for PROD and 62 for TEST just to be on the safe side for operation.

Thanks for your support

Regards,

Tom

0 Kudos
4 Replies
asabban
Level 17

Re: MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hello,

you should use a different VRRP ID. Additionally MFEND should use a different ID for both clusters, otherwise all nodes will have the same ID which will cause all nodes to become one cluster when they are in the same broadcast domain.


Try to add "MFEND_LBID" to /etc/sysconfig/mfend (outside of the "AUTOGENERATED" block). You can simply add (for your new cluster) something like:

MFEND_LBID='1234'

This has to be done on all nodes. If you reboot your test cluster, it should no longer interefere with the existing cluster.

There should be no need for different Groups, unless you use a central management configuration for both clusters.

I hope this helps.

Best,

Andre

0 Kudos
itagsupport
Level 9

Re: MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hi Andre

Thanks for coming back on this.

I will now change the mfend config files on each node of the PROD cluster as follows:

[root@proxy-prod1 mfend]# cat /etc/sysconfig/mfend

### BEGIN AUTOGENERATED CONFIG

MFEND_MANAGEMENT='192.168.14.202'

MFEND_MODE='haproxy'

MFEND_ROLE='director'

MFEND_REDIRECT[0]='http 8080 vlan:none 8080'

### END AUTOGENERATED CONFIG

MFEND_LBID='51'

  and

[root@proxy-prod2 ~]# cat /etc/sysconfig/mfend

### BEGIN AUTOGENERATED CONFIG

MFEND_MANAGEMENT='192.168.14.203'

MFEND_MODE='haproxy'

MFEND_ROLE='director'

MFEND_REDIRECT[0]='http 8080 vlan:none 8080'

### END AUTOGENERATED CONFIG

MFEND_LBID='51'

and the mfend config files on each node of the TEST cluster as follows:

[root@proxy-test1 ~]# cat /etc/sysconfig/mfend

### BEGIN AUTOGENERATED CONFIG

MFEND_MANAGEMENT='192.168.14.196'

MFEND_MODE='haproxy'

MFEND_ROLE='director'

MFEND_REDIRECT[0]='http 8080 vlan:none 8080'

### END AUTOGENERATED CONFIG

MFEND_LBID='52'

  and

[root@proxy-test2 ~]# cat /etc/sysconfig/mfend

### BEGIN AUTOGENERATED CONFIG

MFEND_MANAGEMENT='192.168.14.197'

MFEND_MODE='haproxy'

MFEND_ROLE='director'

### END AUTOGENERATED CONFIG

MFEND_LBID='52'

Do you agree on that?

I will try at the next chance when we get a change window.

Thanks and regards,

Tom

Nachricht geändert durch itagsupport on 20.01.12 13:59:42 MEZ
0 Kudos
asabban
Level 17

Re: MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hi Tom,

I would expect this to work. After the reboot you should be able to run cat /proc/wsnat/status and look for the ID to verify the change worked.

Let me know how it goes.

Best,

Andre

0 Kudos
itagsupport
Level 9

Re: MWG 7 clustering with 2 independant Proxy HA clusters

Jump to solution

Hi Andre

Today we took the PROD and the TEST clusters online.

All works fine now with different MFEND_LBID='61' für PROD nodes and MFEND_LBID='62' for TEST nodes defined in file /etc/sysconfig/mfend .

Btw, we also changed the VRRP Router ID from the default 51 to 61 for PROD and 62 for TEST just to be on the safe side for operation.

Thanks for your support

Regards,

Tom

0 Kudos