07-22-2011 09:56 AM
First, do you need to have the "Standby" master redundant controller setup as a master? I currently have a spare local that I want to use as the redundant master. It appears that a local controller does not support the master-redundancy stanza. If so, not a big deal - I'll just have to blow that controller away and let it re-sync with the existing master controller.
The second question is about what happens when you enable master redundancy. Last night I enabled this feature on our existing master controller and, in short order, I began to lose connectivity to all of my local controllers. Does the VRRP IP address of the master redundancy configuration become the only IP address that local controllers use to contact the master controller? I currently have our existing master IP address on another interface.
Thanks for any help that you can offer!
Thanks for your help!
07-22-2011 10:01 AM
The second answer is yes, the VRRP VIP needs to be the IP address that the local controllers point to in their master-ip statements. That is what creates the redundancy. If the primary fails, the backup takes control of the IP address and the local controllers continue to function.
07-25-2011 09:41 AM
One more question. I have the following interfaces:
172.16.9.134 - VRRP / future master redundancy IP
172.16.191.253 - existing loopback, source for syslog and RADIUS, and master controller IP
Currently, the source of the controller traffic comes from our .253 address. If I understand you correctly, the new VRRP IP will now handle all local to master controller traffic. Will the VRRP address also become the new source for our syslog and RADIUS traffic? Or, is that something that I can keep with the existing interface, for the time being?
Thanks for your help, it really helps!
07-25-2011 09:53 AM