Wired Intelligent Edge

last person joined: 19 hours ago 

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

LACP problems in the VSX - JL479A-8320

This thread has been viewed 24 times

  • 1.  LACP problems in the VSX - JL479A-8320

    Posted May 21, 2019 07:55 AM

    Hi all , 

    We have two switches in the our core layer .

    Switches model are Aruba 8320 and running the VSX .

    The switches connected to 7210 Aruba Controller with two links and LACP . 

    We getting log from VSX Primary switch.

     

    We checked into the Layer1 and Layer2 .

     

    SFP's and Fiber cables are 

     

     

    Logs from the VSX Secondary switch ; 

     

    2019-05-21:13:58:48.126162|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:13:58:53.077433|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:13:59:12.393323|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:13:59:18.321296|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:13:59:18.409931|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:13:59:23.419356|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:13:59:25.496070|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:13:59:30.421256|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:00:01.845229|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:14:00:06.790304|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:00:31.124868|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:14:00:36.148915|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:00:49.312462|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:14:00:56.279733|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:01:10.502713|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:14:01:15.506838|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:01:33.731669|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down
    2019-05-21:14:01:38.769395|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:01:53.909236|hpe-vsxd|7011|LOG_INFO|AMM|-|VSX 13 state local up, remote down

     

    MCLAG Configuration on switch ;

     

    interface 1/1/35
    no shutdown
    lag 13
    exit
    KS-BB-AD-253# sh run interface lag13
    interface lag 13 multi-chassis
    description Aruba_MD1
    no shutdown
    no routing
    vlan trunk native 111
    vlan trunk allowed all
    lacp mode active
    exit

     

     

    KS-BB-AD-253# show lacp interfaces vsx-peer

    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 Aggr Port Port State System-ID System Aggr Forwarding
    Name Id Pri Pri Key State
    ------------------------------------------------------------------------------
    1/1/52 lag1 53 1 ALFNCD d0:67:26:4a:5b:10 65534 1 up
    1/1/53 lag1 54 1 ALFNCD d0:67:26:4a:5b:10 65534 1 up
    1/1/38 lag2(mc) 1038 1 ALFNCD d0:67:26:4a:49:1c 65534 2 up
    1/1/39 lag3(mc) 1039 1 ALFNCD d0:67:26:4a:49:1c 65534 3 up
    1/1/40 lag4(mc) 1040 1 ALFNCD d0:67:26:4a:49:1c 65534 4 up
    1/1/41 lag5(mc) 1041 1 ALFNCD d0:67:26:4a:49:1c 65534 5 up
    1/1/42 lag6(mc) 1042 1 ALFNCD d0:67:26:4a:49:1c 65534 6 up
    1/1/48 lag7(mc) 1048 1 ALFNCD d0:67:26:4a:49:1c 65534 7 up
    1/1/46 lag8(mc) 1046 1 ALFNCD d0:67:26:4a:49:1c 65534 8 up
    1/1/47 lag9(mc) 1047 1 ALFNCD d0:67:26:4a:49:1c 65534 9 up
    1/1/45 lag10(mc) 1045 1 ALFNCD d0:67:26:4a:49:1c 65534 10 up
    1/1/44 lag11(mc) 1044 1 ALFNCD d0:67:26:4a:49:1c 65534 11 up
    1/1/43 lag12(mc) 1043 1 ALFNCD d0:67:26:4a:49:1c 65534 12 up
    1/1/35 lag13(mc) 1035 1 ALFNCD d0:67:26:4a:49:1c 65534 13 up
    1/1/36 lag14(mc) 1036 1 ALFNCD d0:67:26:4a:49:1c 65534 14 up


    Partner details of all interfaces:
    ------------------------------------------------------------------------------
    Intf Aggr Port Port State System-ID System Aggr
    Name Id Pri Pri Key
    ------------------------------------------------------------------------------
    1/1/52 lag1 53 1 ALFNCD d0:67:26:4a:49:1c 65534 1
    1/1/53 lag1 54 1 ALFNCD d0:67:26:4a:49:1c 65534 1
    1/1/38 lag2(mc) 112 0 ALFNCD 08:97:34:fb:10:e5 4325 975
    1/1/39 lag3(mc) 16 0 ALFNCD 08:97:34:fa:4c:65 19557 969
    1/1/40 lag4(mc) 112 0 ALFNCD 08:97:34:fb:11:65 4453 968
    1/1/41 lag5(mc) 16 0 ALFNCD 08:97:34:fa:cd:e5 52709 969
    1/1/42 lag6(mc) 112 0 ALFNCD 08:97:34:fa:ad:e5 44517 970
    1/1/48 lag7(mc) 16 0 ALFNCD 08:97:34:fa:18:65 6245 970
    1/1/46 lag8(mc) 111 0 ALFNCD 08:97:34:fa:06:65 1637 963
    1/1/47 lag9(mc) 26 0 ALFNCD 08:97:34:ff:b7:65 46949 977
    1/1/45 lag10(mc) 112 0 ALFNCD 04:09:73:71:65:e5 26085 969
    1/1/44 lag11(mc) 16 0 ALFNCD 08:97:34:fb:72:e5 29413 970
    1/1/43 lag12(mc) 16 0 ALFNCD 08:97:34:fa:08:e5 2277 962
    1/1/35 lag13(mc) 6 255 ALFNCD 00:1a:1e:04:bc:78 32768 1
    1/1/36 lag14(mc) 6 255 ALFNCD 00:1a:1e:04:c8:40 32768 1
    KS-BB-AD-253#

     

     

    LACP flags are continuous changes in a minute .

    1/1/35 lag13(mc) 6 255 ALFNCD 00:1a:1e:04:bc:78 32768 1

    1/1/35 lag13(mc) 6 255 ALFN 00:1a:1e:04:bc:78 32768 1

    1/1/35 lag13(mc) 6 255 ALFNCDX 00:1a:1e:04:bc:78 32768 1 etc.

     

    Can you help us ?

    Thanks in advance .

     



  • 2.  RE: LACP problems in the VSX - JL479A-8320

    Posted May 21, 2019 08:08 AM

    More logs from VSX primary switch.

     

    2019-05-21:14:59:19.743683|hpe-vsxd|7012|LOG_INFO|AMM|-|VSX 13 state local down, remote up
    2019-05-21:14:59:19.763044|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFN
    2019-05-21:14:59:22.694834|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFOEX
    2019-05-21:14:59:22.707192|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFN, Partner state ALFOEX
    2019-05-21:14:59:24.697940|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFN, Partner state ALFN
    2019-05-21:14:59:24.709344|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFN
    2019-05-21:14:59:24.709785|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFNCD
    2019-05-21:14:59:24.718671|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNCD, Partner state ALFNCD
    2019-05-21:14:59:24.730136|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:59:24.743526|hpe-vsxd|7013|LOG_INFO|AMM|-|VSX 13 state local up, remote up
    2019-05-21:14:59:42.946539|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNCD, Partner state ALFN
    2019-05-21:14:59:42.971749|hpe-vsxd|7012|LOG_INFO|AMM|-|VSX 13 state local down, remote up
    2019-05-21:14:59:42.979189|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFN
    2019-05-21:14:59:45.933265|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFOEX
    2019-05-21:14:59:45.944042|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFN, Partner state ALFOEX
    2019-05-21:14:59:47.936289|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFN, Partner state ALFN
    2019-05-21:14:59:47.946342|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFN
    2019-05-21:14:59:47.946727|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNC, Partner state ALFNCD
    2019-05-21:14:59:47.986923|lacpd|1321|LOG_INFO|AMM|-|LAG 13 State change for interface 1/1/35: Actor state: ALFNCD, Partner state



  • 3.  RE: LACP problems in the VSX - JL479A-8320

    MVP GURU
    Posted May 21, 2019 06:50 PM

    Hi, there is something strange going on...having the whole picture would really help (not just part of the picture taken from a specific position).

     

    Aruba 8320 VSX:

     

    Could you be so kind to show us sanitized output of these CLI Commands:

     

    • show lacp interfaces multi-chassis (details of lag13 only)
    • show lacp interfaces multi-chassis vsx-peer (details of lag13 only)
    • show interface lag13
    • show interface lag13 vsx-peer
    • show lacp interface 1/1/35
    • show lacp interface 1/1/35 vsx-peer

    executed on VSX Primary?

     

    Eventually the output of:

     

    • show vsx lacp aggregates lag13
    • show run vsx-sync peer-diff (details of lag13 only)
    • show vsx config-consistency lacp lag13
    • show vsx config-consistency lacp lag13 vsx-peer

    would be of help too.

     

    Aruba 7210:

     

    I suppose your Aruba 7210 controller is physically connected with two links to your Aruba 8320 VSX...one link is going from an Aruba 7210 port to VSX Primary interface 1/1/35 and the other link is going from another Aruba 7210 port to VSX Secondary interface 1/1/35...both 1/1/35 interfaces on VSX side are part of the same VSX LAG Id 13 (Multi-Chassis LAG with Id 13) which is defined on both VSX Members and that very VSX LAG is configured as per known VSX Best Practices (including, but not limited by, references to loop-protection and permitted VLANs features).

     

    On Aruba 7210 side you should just create a Port Channel (which is a LAG) using LACP by following known configuration methods for your ArubaOS running version (as example like the one described here which should be possibly quite relevant...or here if you prefer something very short to read).



  • 4.  RE: LACP problems in the VSX - JL479A-8320

    Posted Jun 12, 2023 10:02 AM

    Hi There, 

    i'm having the same issue right know , when i assign the vsx peer the same lag the connected switch depug these messages

    2023-06-09T22:29:23.147194+0000 lacpd[2306] <WARN> Event|1310|LOG_WARN|AMM|1/1|Partner is out of sync for interface 1/1/50 LAG sport: 1. Actor state: ALFOX, partner state PSFO
    2023-06-09T22:29:23.224118+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALIO, Partner state PLIO
    2023-06-09T22:29:23.321913+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFO, Partner state PLIO
    2023-06-09T22:29:23.399792+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFO, Partner state PLFO
    2023-06-09T22:29:23.444210+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFOE, Partner state PLFO
    2023-06-09T22:29:23.488112+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFOE, Partner state PSFO
    2023-06-09T22:29:23.521715+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFOX, Partner state PSFO
    2023-06-09T22:29:24.261194+0000 lacpd[2306] <INFO> Event|1309|LOG_INFO|AMM|1/1|Partner is detected for interface 1/1/50 LAG 27 : 65534,00:00:00:01:01:01. Actor state: ALFOX, partner state ALFOE
    2023-06-09T22:29:24.266074+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFOX, Partner state ALFOE
    2023-06-09T22:29:24.301110+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFO, Partner state ALFOE
    2023-06-09T22:29:24.329445+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFO, Partner state ALFOX
    2023-06-09T22:29:25.981095+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFO, Partner state ALFN
    2023-06-09T22:29:26.049168+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFNC, Partner state ALFN
    2023-06-09T22:29:26.093308+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFNC, Partner state ALFNC
    2023-06-09T22:29:26.152068+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFNCD, Partner state ALFNC
    2023-06-09T22:29:26.253023+0000 lacpd[2306] <INFO> Event|1321|LOG_INFO|AMM|1/1|LAG 27 State change for interface 1/1/50: Actor state: ALFNCD, Partner state ALFNCD

    what have you done to solve this problem 


    Original Message


  • 5.  RE: LACP problems in the VSX - JL479A-8320
    Best Answer

    Posted May 29, 2019 03:38 AM

    Hi all , 

     

    Problem has been resolved .

    We replaced the fiber optic cable and it's running .