Wireless Access

Reply
Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Correct, that's exactly what I'm setting up.

Re: Clustering MD in 8.x. The need for VRRP IP?

When in the cluster config settings on the MM, when you assign a VRRP IP and VLAN for each MD being added to the cluster, the cluster manager will automatically create a VRRP ID across all cluster members, making that specific MD the Master (priority 255) and all others lower (235, 215, etc). For example, I have three controllers in my lab cluster that runs my network. They are:

 

VMC1 (ipaddr 192.168.200.13 - cluster VIP 192.168.200.23)

VMC2 (ipaddr 192.168.200.14 - cluster VIP 192.168.200.24)

VMC3 (ipaddr 192.168.200.15 - cluster VIP 192.168.200.25)

 

Below is the output from their 'show vrrp' output, but note that I only entered in the cluster cofig for each MD the cluster IP, the cluster VIP and VRRP vlan.

 

Note I also created a cluster-wide VIP for AP discovery as well (VRRP ID 200)

 

###################
(HH-VMC1) #show vrrp

Virtual Router 200:
Description AP_Discovery_200
Admin State UP, VR State MASTER
IP Address 192.168.200.20, MAC Address 00:00:5e:00:01:c8, vlan 200
Priority 255, Advertisement 1 sec, Preemption Disable Delay 0
Auth type PASSWORD, Auth data: ********
tracking is not enabled

Virtual Router 220:
Description
Admin State UP, VR State MASTER
IP Address 192.168.200.23, MAC Address 00:00:5e:00:01:dc, vlan 200
Priority 255, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 221:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.24, MAC Address 00:00:5e:00:01:dd, vlan 200
Priority 235, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 222:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.25, MAC Address 00:00:5e:00:01:de, vlan 200
Priority 215, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled
(HH-VMC1) #
###################
(HH-VMC2) #show vrrp

Virtual Router 200:
Description AP_Discovery_200
Admin State UP, VR State BACKUP
IP Address 192.168.200.20, MAC Address 00:00:5e:00:01:c8, vlan 200
Priority 245, Advertisement 1 sec, Preemption Disable Delay 0
Auth type PASSWORD, Auth data: ********
tracking is not enabled

Virtual Router 220:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.23, MAC Address 00:00:5e:00:01:dc, vlan 200
Priority 215, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 221:
Description
Admin State UP, VR State MASTER
IP Address 192.168.200.24, MAC Address 00:00:5e:00:01:dd, vlan 200
Priority 255, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 222:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.25, MAC Address 00:00:5e:00:01:de, vlan 200
Priority 235, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled
(HH-VMC2) #
###################
(HH-VMC3) #show vrrp

Virtual Router 200:
Description AP_Discovery_200
Admin State UP, VR State BACKUP
IP Address 192.168.200.20, MAC Address 00:00:5e:00:01:c8, vlan 200
Priority 235, Advertisement 1 sec, Preemption Disable Delay 0
Auth type PASSWORD, Auth data: ********
tracking is not enabled

Virtual Router 220:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.23, MAC Address 00:00:5e:00:01:dc, vlan 200
Priority 235, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 221:
Description
Admin State UP, VR State BACKUP
IP Address 192.168.200.24, MAC Address 00:00:5e:00:01:dd, vlan 200
Priority 215, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled

Virtual Router 222:
Description
Admin State UP, VR State MASTER
IP Address 192.168.200.25, MAC Address 00:00:5e:00:01:de, vlan 200
Priority 255, Advertisement 1 sec, Preemption Enable Delay 0
Auth type NONE ********
tracking is not enabled
(HH-VMC3) #
###################

Jerrod Howard
Sr. Technical Marketing Engineer
Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Is there any reason I couldn't re-use one of the cluster created VIPs for AP provisioning?  I only have a pair of MDs in my network, and that's not likely to change any time soon.

Highlighted

Re: Clustering MD in 8.x. The need for VRRP IP?

Nope that will work fine, I just did both to test.

Jerrod Howard
Sr. Technical Marketing Engineer
Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Awesome!  Thanks very much for the quick confirmation.

Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Just to follow up, I have one MD brought up. It looks like it's started up the cluster, as it shows itself as isolated in show lc-cluster, but VRRP is completely inactive on it, and neither of the MD VIPs are pingable. My best guess is that they won't come online until the second MD has come online at least once (which I can't do until I've migrated my APs over), but I have an ATAC case open to verify.

Re: Clustering MD in 8.x. The need for VRRP IP?

Clustering, as a function of clustering, doesn't require VRRP. You would have had to have configured it as part of the VRRP component of the cluster config on the MM. Mine looks like this:

 

controller 192.168.200.13 priority 200 mcast-vlan 0 vrrp-ip 192.168.200.23 vrrp-vlan 200

    controller 192.168.200.14 priority 200 mcast-vlan 0 vrrp-ip 192.168.200.24 vrrp-vlan 200

    controller 192.168.200.15 priority 200 mcast-vlan 0 vrrp-ip 192.168.200.25 vrrp-vlan 200

 

But the VRRP component is NOT required. 

Jerrod Howard
Sr. Technical Marketing Engineer
Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Yup, that matches my cluster config in my /md tree:

 

lc-cluster group-profile "campus-primary-cluster"
controller 130.215.39.54 priority 128 mcast-vlan 0 vrrp-ip 130.215.39.55 vrrp-vlan 1039
controller 130.215.39.56 priority 128 mcast-vlan 0 vrrp-ip 130.215.39.57 vrrp-vlan 1039
active-ap-lb
!

 

"show lc-cluster" on 130.215.39.54 shows it as the isolated leader of campus-primary-cluster as expected, but "show vrrp" returns no output at all.

Frequent Contributor I

Re: Clustering MD in 8.x. The need for VRRP IP?

Success! I was able to bring my second MD online, and as soon as I did the lc-cluster configured VRRP instances showed up and started working. Apparently they don't work until both (all?) of the MDs have actually checked in with the MMs at least once. Until then, the VRRP addresses do not come up.

Hopefully knowing this will save someone else this particular headache :)

Re: Clustering MD in 8.x. The need for VRRP IP?

That's actually good to know! Thanks for following up!

Jerrod Howard
Sr. Technical Marketing Engineer
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: