Wired

last person joined: 21 hours ago 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

ArubaOS-CX: VSX LAG's interface state (In-sync/Out-of-Sync) inconsistency?

  • 1.  ArubaOS-CX: VSX LAG's interface state (In-sync/Out-of-Sync) inconsistency?

    Posted Mar 28, 2019 11:59 AM

    I noticed that one of our interface (1/1/7 member of lag4 on both VSX nodes) shows a different state (Out-of-Sync versus In-Sync) respectively if the show lacp interfaces multi-chassis is committed on Primary or Secondary node (approximately during the same time):

     

    Primary reports (truncated output, reported only lag4(mc)):

     

    Aruba-8320-1# show lacp interfaces multi-chassis 
    
    State abbreviations :
    A - Active        P - Passive      F - Aggregable I - Individual
    S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
    C - Collecting    D - Distributing 
    X - State m/c expired              E - Default neighbor state
    
    Actor details of all interfaces:
    ------------------------------------------------------------------------------
    Intf    Aggregate  Port    Port     State   System-ID         System   Aggr    
            name       id      Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7   lag4(mc)   7       1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    1/1/8   lag4(mc)   8       1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    
    
    Partner details of all interfaces:
    ------------------------------------------------------------------------------
    Intf    Aggregate  Partner Port     State   System-ID         System   Aggr    
            name       Port-id Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7   lag4(mc)   2       128      ALFNCD  98:be:94:66:18:30 32768    48879   
    1/1/8   lag4(mc)   6       128      ALFNCD  98:be:94:66:18:30 32768    48879   
    
    
    Remote Actor details of all interfaces:
    ------------------------------------------------------------------------------
    Intf   Aggregate  Port    Port     State   System-ID         System   Aggr    
           name       id      Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7  lag4(mc)   1007    1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    1/1/8  lag4(mc)   1008    1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    
    
    Remote Partner details of all interfaces:
    ------------------------------------------------------------------------------
    Intf   Aggregate  Partner Port     State   System-ID         System   Aggr    
           name       Port-id Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7  lag4(mc)   1       128      ALFNC   98:be:94:66:18:30 32768    48879   
    1/1/8  lag4(mc)   5       128      ALFNC   98:be:94:66:18:30 32768    48879   

    Secondary reports (truncated output, reported only lag4(mc)):

     

    Aruba-8320-2# show lacp interfaces multi-chassis
    
    State abbreviations :
    A - Active        P - Passive      F - Aggregable I - Individual
    S - Short-timeout L - Long-timeout N - InSync     O - OutofSync
    C - Collecting    D - Distributing 
    X - State m/c expired              E - Default neighbor state
    
    Actor details of all interfaces:
    ------------------------------------------------------------------------------
    Intf    Aggregate  Port    Port     State   System-ID         System   Aggr    
            name       id      Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7   lag4(mc)   1007    1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    1/1/8   lag4(mc)   1008    1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    
    
    Partner details of all interfaces:
    ------------------------------------------------------------------------------
    Intf    Aggregate  Partner Port     State   System-ID         System   Aggr    
            name       Port-id Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7   lag4(mc)   1       128      ALFNCD  98:be:94:66:18:30 32768    48879   
    1/1/8   lag4(mc)   5       128      ALFNCD  98:be:94:66:18:30 32768    48879   
    
    
    Remote Actor details of all interfaces:
    ------------------------------------------------------------------------------
    Intf   Aggregate  Port    Port     State   System-ID         System   Aggr    
           name       id      Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7  lag4(mc)   7       1        ALFOCD  d0:67:26:49:b8:9e 65534    4       
    1/1/8  lag4(mc)   8       1        ALFNCD  d0:67:26:49:b8:9e 65534    4       
    
    
    Remote Partner details of all interfaces:
    ------------------------------------------------------------------------------
    Intf   Aggregate  Partner Port     State   System-ID         System   Aggr    
           name       Port-id Priority                           Priority Key     
    ------------------------------------------------------------------------------
    1/1/7  lag4(mc)   2       128      ALFNC   98:be:94:66:18:30 32768    48879   
    1/1/8  lag4(mc)   6       128      ALFNC   98:be:94:66:18:30 32768    48879   

    Notice how lag4(mc) 1/1/7 Interface's state (N versus O) is reported as Remote Actor from the VSX Secondary:

    lag4_comparison_28032019.png

    Isn't that a little bit strange?

     

    How is it possible that the very same Interface 1/1/7 is concurrently seen In-Sync (N) and Out-of-Sync (O)?

     

    Logs of VSX Primary: NO logs related to 1/1/7.

     

    Logs of VSX Secondary:

     

    2019-03-28:13:49:20.447160|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFO, Partner state ALFNCD
    2019-03-28:13:49:20.815111|lacpd|1313|LOG_INFO|AMM|-|LAG 4 set as VSX 
    2019-03-28:13:49:20.816062|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALIO, Partner state PLIO
    2019-03-28:13:49:20.818323|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFO, Partner state PLIO
    2019-03-28:13:49:20.826889|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFO, Partner state PLFO
    2019-03-28:13:49:20.830274|lacpd|1309|LOG_INFO|AMM|-|Partner is detected for interface 1/1/7 LAG 4 : 65534,00:00:00:00:00:00. Actor state: ALFOE, partner state PLFO 
    2019-03-28:13:49:20.830413|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFOE, Partner state PLFO
    2019-03-28:13:49:20.833512|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFOE, Partner state PSFO
    2019-03-28:13:49:20.836760|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFOX, Partner state PSFO
    2019-03-28:13:49:20.840133|lacpd|1310|LOG_WARN|AMM|-|Partner is out of sync for interface 1/1/7 LAG sport: 15. Actor state: ALFOX, partner state PSFO 
    2019-03-28:13:49:21.349742|lacpd|1309|LOG_INFO|AMM|-|Partner is detected for interface 1/1/7 LAG 4 : 32768,98:be:94:66:18:30. Actor state: ALFOX, partner state ALFNC 
    2019-03-28:13:49:21.349819|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFOX, Partner state ALFNC
    2019-03-28:13:49:21.353090|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFO, Partner state ALFNC
    2019-03-28:13:49:23.034047|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFNCD, Partner state ALFNC
    2019-03-28:13:49:23.347832|lacpd|1321|LOG_INFO|AMM|-|LAG 4 State change for interface 1/1/7: Actor state: ALFNCD, Partner state ALFNCD

     Any idea? Am I misunderstanding commands' outputs?



  • 2.  RE: ArubaOS-CX: VSX LAG's interface state (In-sync/Out-of-Sync) inconsistency?

    Posted Apr 29, 2019 07:43 AM

    It seems a bug. Did you open a case ?



  • 3.  RE: ArubaOS-CX: VSX LAG's interface state (In-sync/Out-of-Sync) inconsistency?

    Posted Apr 29, 2019 08:03 AM

    Not yet. I'm going to open it just now on the Aruba Case Management Portal on ASP. Thanks.

     

    Edit: opened Case number 5338235074.