Wireless Access

last person joined: 2 days ago 

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

VRRP between MM's on ESX

This thread has been viewed 5 times
  • 1.  VRRP between MM's on ESX

    EMPLOYEE
    Posted Jan 22, 2020 07:38 AM

    Hello trying to setup MM redundancy on a vmware station but I'm not getting the vrrp setup , any idea's?

     

    On MM1 (primary)
    ================

    (ArubaMM-VA_56_9C_3B) [mynode] #show switches

    All Switches
    ------------
    IP Address IPv6 Address Name Location Type Model Version Status Configuration State Config Sync Time (sec) Config ID
    ---------- ------------ ---- -------- ---- ----- ------- ------ ------------------- ---------------------- ---------
    192.168.1.250 None ArubaMM-VA_56_9C_3B Building1.floor1 master ArubaMM-VA 8.6.0.2_73853 up UPDATE SUCCESSFUL 0 2

    Total Switches:1
    (ArubaMM-VA_56_9C_3B) [mynode] #ping 192.168.1.251 (this is the MM peer)

    Press 'q' to abort.
    Sending 5, 92-byte ICMP Echos to 192.168.1.251, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 6.696/9.477/11.036 ms

    (ArubaMM-VA_56_9C_3B) [mynode] #show ip interface brief

    Interface IP Address / IP Netmask Admin Protocol VRRP-IP
    vlan 1 192.168.1.250 / 255.255.255.0 up up 192.168.1.253
    loopback unassigned / unassigned up up
    mgmt unassigned / unassigned down down

    (ArubaMM-VA_56_9C_3B) [mynode] #encrypt disable
    (ArubaMM-VA_56_9C_3B) [mynode] #show vrrp


    Virtual Router 10:
    Description Primary-master
    Admin State UP, VR State MASTER
    IP Address 192.168.1.253, MAC Address 00:00:5e:00:01:0a, vlan 1
    Priority 200, Advertisement 1 sec, Preemption Disable Delay 0
    Auth type PASSWORD, Auth data: aruba123
    tracking is not enabled
    (ArubaMM-VA_56_9C_3B) [mynode] #ping 192.168.1.253  (this is the configured VRRP adress)

    Press 'q' to abort.
    Sending 5, 92-byte ICMP Echos to 192.168.1.253, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0.066/0.1046/0.169 ms

     

    (ArubaMM-VA_56_9C_3B) [mynode] #show database synchronize

    Last L2 synchronization time: Wed Jan 22 14:38:41 2020
    Last L3 synchronization time: Secondary not synchronized since last reboot
    To Master Switch at 192.168.1.251: *** FAILED ***
    WMS Database backup file size: 0 bytes
    Upgrademgr Database backup file size: 0 bytes
    Cluster upgrademgr Database backup file size: 0 bytes
    Local User Database backup file size: 0 bytes
    Global AP Database backup file size: 0 bytes
    IAP Database backup file size: 0 bytes
    Airgroup Database backup file size: 0 bytes
    License Database backup file size: 0 bytes
    CPSec Database backup file size: 0 bytes
    Bocmgr Database backup file size: 0 bytes
    L2 Synchronization took less than one second
    L3 Synchronization took less than one second
    Last failure cause: Standby switch did not respond to the start request or is not ready

    10 L2 synchronization attempted
    10 L2 synchronization have failed

    0 L3 synchronization attempted
    0 L3 synchronization have failed

    L2 Periodic synchronization is enabled and runs every 20 minutes

    L3 Periodic synchronization is disabled

    Synchronization doesn't include Captive Portal Custom data
    Airmatch database gets synchronized periodically. Last synchronization time : 2020-01-22 14:51:55
    (ArubaMM-VA_56_9C_3B) [mynode] #

     

    On MM2 (standby)
    =================

    (ArubaMM-VA_B8_94_DF) [mynode] #show switches

    All Switches
    ------------
    IP Address IPv6 Address Name Location Type Model Version Status Configuration State Config Sync Time (sec) Config ID
    ---------- ------------ ---- -------- ---- ----- ------- ------ ------------------- ---------------------- ---------
    192.168.1.251 None ArubaMM-VA_B8_94_DF Building1.floor1 master ArubaMM-VA 8.6.0.2_73853 up UPDATE SUCCESSFUL 0 2

    Total Switches:1

    (ArubaMM-VA_B8_94_DF) [mynode] #ping 192.168.1.250 (this is the MM peer)

    Press 'q' to abort.
    Sending 5, 92-byte ICMP Echos to 192.168.1.250, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 3.635/14.8994/39.939 ms

    (ArubaMM-VA_B8_94_DF) [mynode] #encrypt disable
    (ArubaMM-VA_B8_94_DF) [mynode] #show vrrp


    Virtual Router 10:
    Description Secondary-master
    Admin State UP, VR State MASTER
    IP Address 192.168.1.253, MAC Address 00:00:5e:00:01:0a, vlan 1
    Priority 100, Advertisement 1 sec, Preemption Disable Delay 0
    Auth type PASSWORD, Auth data: aruba123
    tracking is not enabled
    (ArubaMM-VA_B8_94_DF) [mynode] #show ip interface brief

    Interface IP Address / IP Netmask Admin Protocol VRRP-IP
    vlan 1 192.168.1.251 / 255.255.255.0 up up 192.168.1.253
    loopback unassigned / unassigned up up
    mgmt unassigned / unassigned down down
    (ArubaMM-VA_B8_94_DF) [mynode] #ping 192.168.1.253 (this is the configured VRRP adress)

    Press 'q' to abort.
    Sending 5, 92-byte ICMP Echos to 192.168.1.253, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 0.054/0.0842/0.158 ms

    (ArubaMM-VA_B8_94_DF) [mynode] #



  • 2.  RE: VRRP between MM's on ESX
    Best Answer

    EMPLOYEE
    Posted Jan 22, 2020 07:48 AM

    If you haven't done so already:

     

    Screenshot 2020-01-22 at 06.46.32.png

    In case  you haven't, feel free to review the rest of the  Virtual Appliance Installation guide here:  https://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=37814



  • 3.  RE: VRRP between MM's on ESX

    MVP EXPERT
    Posted Jan 22, 2020 09:17 AM

    You  need to turn on promisious mode on your portgroup our vswitch to work with VRRP. Also dont use VRRP ID 220-255 that are reserved for internal purpose.

     



  • 4.  RE: VRRP between MM's on ESX

    Posted Jan 22, 2020 09:16 AM

    The VRRP settings are set at  /mm/mynode on each of the MMs, however the database synchronization needs to be set and enabled at /mm on your primary MM. Make sure you have done this at the proper group nodes.

    I hope this helps.