12-19-2013 05:52 AM
I am currently running RAP2's and RAP3's with two 3600's in a master/local setup both located in the same data center. I am tasked with designing a DR solution in the event this data center was not available. I could simply relocate the local to another Data Center and use that for the backup LMS. The challenge is I cannot extend L2 between the DC's so the VLAN must change for the phones. This is fine but I have noticed the phones do not reboot and obtain a new IP if they are simply placed on another vlan. In the event of a disaster having users reboot the phones tp obtain an IP on the other subnet would not be a big deal, however I am sure RAP's will find their way to the local at some point. Any ideas would be appreciated.
12-19-2013 08:55 AM
12-19-2013 09:12 AM
That's a real worry that the phones don't reboot. I assume they are something different to Cisco which reboots if it loses comms to the call manager?
Well, ideal number 1 from me...
Nail up a static GRE between the controllers, and align it with a specific VLAN (where your phones will live). This means regardless of where the phones terminate, they live in a routed "cloud" VLAN shared between controllers and resilience will be fine.
Then, make sure the layer 3 egress point from both controllers suits the routed infrastructure, maybe using OSPF to make it optimised and resilient? I haven't thought this through in detail, and it might not suit your layer 3 topology, but it's an idea at least?
Also have a sensible think about where the DHCP is going to come from resiliently of course.