Wireless Access

last person joined: 17 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

L3 redundancy - LMS/Backup LMS

This thread has been viewed 6 times
  • 1.  L3 redundancy - LMS/Backup LMS

    Posted Feb 01, 2012 05:57 PM

    I've got two sites where I need to implement L3 redundancy.  My question is do the VLANs or the subnets need to be the same on the two controllers? I know the SSIDs need to be the same but if the SSIDs on the two controllers don't correspond to the same VLANs or subnet, would the clients do DHCP again in the new VLAN or expect the same VLAN/subnet?



  • 2.  RE: L3 redundancy - LMS/Backup LMS

    EMPLOYEE
    Posted Feb 01, 2012 08:51 PM

     

     

    The handover can be  very quick and if it is quick enough, the radio does not go down long enough for the client to notice and it will not re-DHCP.



  • 3.  RE: L3 redundancy - LMS/Backup LMS

    Posted Feb 01, 2012 10:32 PM

    Thanks as always cjoseph. So the VLANs/subnets don't need to be the same, correct? Is there anything else I would need to do other than configuring the Backup LMS address on each controller in the AP System profile?



  • 4.  RE: L3 redundancy - LMS/Backup LMS
    Best Answer

    EMPLOYEE
    Posted Feb 01, 2012 10:33 PM
    Do not need to be the same. Backup lms is all you need.


  • 5.  RE: L3 redundancy - LMS/Backup LMS

    Posted Nov 07, 2012 07:43 AM

    I have a question on the above: If the VLANs/subnet are not the same on the backup LMS and the clients do not re-DHCP will they not be in the 'wrong subnet' during failover?



  • 6.  RE: L3 redundancy - LMS/Backup LMS

    Posted Nov 07, 2012 08:11 AM

    Yes, the clients that fail won't work until they release/renew, reboot or disconnect/reconnect.



  • 7.  RE: L3 redundancy - LMS/Backup LMS

    Posted Nov 07, 2012 09:41 AM

    Thanks olino for the quick reply.

     

    Follow-up:

    Could this be then avoided in any way making use of L3 Redundancy?

     

    I'm currently looking at a setup where 2 Mobility Controllers are in 2 different routing domains but both advertise the same subnets. I see this working if all the APs are on controller #1 that VLAN will be active and if that controller fails the AP would all move to the 2nd controller which would then advertise the same subnet since it will activitate the VLAN (which is triggered on the APs joining). However if the AP during fallback are active on both controllers we have a routing issue ...

     

     



  • 8.  RE: L3 redundancy - LMS/Backup LMS

    Posted Nov 07, 2012 09:54 AM

    There is really not a "good" way to do make the clients recover automatically (at least not one that I know of).  You MIGHT be able to get the routing to work properly, but as you say, it might break when not all APs move at the same time.  The best bet is to have L2 redundancy for your controllers and only use L3 to protect against some large outage, such as power in the whole datacenter.



  • 9.  RE: L3 redundancy - LMS/Backup LMS

    Posted Nov 07, 2012 10:00 AM

    I was thinking along these lines as well. Thanks for confirming this :)