Wireless

 View Only
last person joined: 4 days ago 

Back to discussions
Expand all | Collapse all

L3 Cluster issue

This thread has been viewed 26 times

  • 1.  L3 Cluster issue

    Posted Apr 11, 2023 09:08 PM

    Hi 
    I have two virtual mobility controllers in a cluster
    It shows that it is in l3 connected state, even though probe status shows that there are no vlans failing
    Is there any other command I can use to narrow it down?

    #show lc-cluster group-membership

    Cluster Enabled, Profile Name = "itf-mc-cluster"
    Redundancy Mode On
    Active Client Rebalance Threshold = 50%
    Standby Client Rebalance Threshold = 75%
    Unbalance Threshold = 5%
    AP Load Balancing: Disabled
    Cluster Info Table
    ------------------
    Type IPv4 Address    Priority Connection-Type STATUS
    ---- --------------- -------- --------------- ------
    self   10.241.128.51      128             N/A CONNECTED (Member)
    peer   10.241.128.52      128    L3-Connected CONNECTED (Leader, last HBT_RSP 10ms ago, RTD = 1.281 ms)
    (eoc-mc-va-01) #show lc-cluster vlan-probe status

    Cluster VLAN Probe Status
    -------------------------
    Type IPv4 Address    REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
    ---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
    peer   10.241.128.52        0        0        0        0        0        0         0   L3 Conn     0/   0
    (eoc-mc-va-01) #show version

    Alcatel-Lucent Operating System-Wireless.
    AOS-W (MODEL: OAW-MC-VA), Version 8.2.2.4
    Website: http://enterprise.alcatel-lucent.com/
    All Rights Reserved (c) 2005-2019, Alcatel-Lucent.
    Compiled on 2019-02-01 at 14:21:11 UTC (build 68953) by p4build

    BIOS Version: Phoenix Technologies LTD, 6.00
    Built: 11/12/2020

    Switch uptime is 13 minutes 42 seconds
    Reboot Cause: User reboot.
    Supervisor Card
    Processor(s):
    Total CPUs :       4,    Sockets : 1,    Cores Per CPU :  4
            Socket 0: Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz
    5710M bytes of memory
    4096M bytes of Supervisor Card system flash.



  • 2.  RE: L3 Cluster issue

    EMPLOYEE
    Posted Apr 11, 2023 09:10 PM

    Do you have all of the VLANs excluded?



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------

    Original Message


  • 3.  RE: L3 Cluster issue

    Posted Apr 12, 2023 04:11 AM
    Yes all clans have been excluded



    Original Message


  • 4.  RE: L3 Cluster issue

    EMPLOYEE
    Posted Apr 12, 2023 06:02 AM

    If a controller cannot probe another controller on at least one shared VLAN, it will mark it as layer 3.  If both controllers are not sharing layer 2 VLANs in a way that they can probe each other, it cannot provide layer 2 failover to each other.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------

    Original Message


  • 5.  RE: L3 Cluster issue

    Posted Apr 12, 2023 07:07 PM
    Ah thanks
    That worked

    Regards



    Original Message