I have a situation that I have 4 controllers divided into 2 clusters and both clusters are in the same VLAN. I configured the cluster as shown below.
Cluster 1
lc-cluster group-profile "lc-cluster1"
controller 10.60.10.136 priority 128 mcast-vlan 0 vrrp-ip 10.60.10.138 vrrp-vlan 3010 group 0 rap-public-ip 0.0.0.0
controller 10.60.10.137 priority 128 mcast-vlan 0 vrrp-ip 10.60.10.139 vrrp-vlan 3010 group 0 rap-public-ip 0.0.0.0
Cluster2
lc-cluster group-profile "lc-cluster2"
controller 10.60.11.136 priority 128 mcast-vlan 0 vrrp-ip 10.60.11.138 vrrp-vlan 3010 group 10 rap-public-ip 0.0.0.0
controller 10.60.11.137 priority 128 mcast-vlan 0 vrrp-ip 10.60.11.139 vrrp-vlan 3010 group 10 rap-public-ip 0.0.0.0
As you can see, both clusters are in the same VLAN (ID 3010) which has subnet 10.60.10.0/23. I changed the group ID in the second cluster, but now the following problem arises.
The VRRP configuration uses the same VRRP ID and generates the same MAC address.
VRRP ID 220 on cluster 1
Virtual Router 220:
Description
Admin State UP, VR State MASTER
IP Address 10.60.10.138, MAC Address 00:00:5e:00:01:dc, vlan 3010
Priority 255, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled
VRRP ID 220 on cluster 2
Virtual Router 220:
Description
Admin State UP, VR State MASTER
IP Address 10.60.11.138, MAC Address 00:00:5e:00:01:dc, vlan 3010
Priority 255, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled
Different virtual IP, but both the same MAC address, which leads to some nasty connectivity problems, like VIP's not reachable and authentication issues.
I wonder whats the best way to solve this. Manually changing the VRRP ID on the controllers from cluster 2 or can something be done in the lc-cluster group-profile configuration (it seems that changing group-id doesn't help).