Wireless Access

 View Only
Expand all | Collapse all

Join VMC to another VMC

This thread has been viewed 8 times
  • 1.  Join VMC to another VMC

    Posted Mar 05, 2019 09:43 AM

    How do I convert two standalone controllers (8.4) to a pair - A master and Local in the old 6.x terminology.

    FYI there is no MM invloved.

     

    Regards,

    MF



  • 2.  RE: Join VMC to another VMC

    Posted Mar 05, 2019 10:12 AM

    Hi MD-RF,

     

    The master local construct does not work in 8.x anymore. You can either use an MM to run them as part of the MM architecture or both as standalone. 

     

    You can run them in a limited master-standby construct as I described here:

    https://www.flomain.de/2017/11/master-standby-arubaos-8/

     

    But I really recommend using a Mobility Master. 

     

    BR

    Florian



  • 3.  RE: Join VMC to another VMC

    Posted Mar 06, 2019 03:38 AM

    That would just about do , however can I assume that the Standby master cannot terminate APs while the master is up, even with HA?



  • 4.  RE: Join VMC to another VMC
    Best Answer

    Posted Mar 06, 2019 07:18 AM

    yes, that's true. The standby cannot terminate AP's. Only in the case of a failure of the master, will the standby terminate AP's. That's no active:active solution. 

     

    That's why I would recommend a Mobility Master and a cluster setup. 



  • 5.  RE: Join VMC to another VMC

    Posted Mar 08, 2019 11:26 AM

    I've setup the master redundancy but the standby doesn't seem to be syncing. On the master there is only one switch in the "show switches" output and when I run the "show running-config" command on the standby it says "modul SAPM is busy. Please try later".

    It also has "Last Snapshot (master unreachable)" under the "show switches" command.



  • 6.  RE: Join VMC to another VMC

    Posted Mar 11, 2019 09:03 AM

    can you ping the master, from the standby? 



  • 7.  RE: Join VMC to another VMC

    Posted Mar 11, 2019 09:05 AM

    Yes the master can be pinged from the local. The VRRP redundancy is up and working correctly with the master contorller as master in the VRRP and the standby running as "Backup".



  • 8.  RE: Join VMC to another VMC

    Posted Mar 11, 2019 09:18 AM

    what does a 

    #show database synchronize  

     tell you? Do you see errors in the syslog? 



  • 9.  RE: Join VMC to another VMC

    Posted Mar 12, 2019 04:53 AM

    On the local it shows -

    Last L2 synchronization time: standby not synchronized since last reboot

    L2 periodic synchronization is enabled and runs every 5 minutes

     

    On the master -

    to master switch at <standbyipaddress>: ***  FAILED  ***

    -output omitted-

    L2 synchronization took 30 second

    L3 Synchronization took less than one second

     

    251 L2 synchronization attempted

    251 L2 synchronization have failed

     

    0 L3 synchronization attempted

    0 L3 synchronization have failed

     

    L2 periodic synchronization is enabled and runs every 5 minutes

    L3 periodic synchronization is disabled



  • 10.  RE: Join VMC to another VMC

    Posted Mar 12, 2019 06:11 AM

    I have raised a case with TAC ad it seems that the master redundancy VRRP needs to run on the management VLAN. In effect it is dependent on the command "controller-ip vlan".



  • 11.  RE: Join VMC to another VMC

    Posted Mar 13, 2019 12:50 AM

    Hi MD-RF,

     

    Oh yes, that is true. You need to run it on the controller IP. Did you changed this it and does it work now? 

     

    I've learned that the hard way too, at a customer :) 



  • 12.  RE: Join VMC to another VMC

    Posted Mar 13, 2019 05:40 AM

    Yes I have changed this and it now works. Its worth noting that I had already done the configuration of all of the profiles which did not get pushed to the Standby controller. If you need to sync the profiles they need to be configured at the Mobility Controller level (/mm not /mynode). /mynode is the default area you are placed into when logging into the controller.