Wired Intelligent Edge

 View Only
Back to discussions
Expand all | Collapse all

Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

This thread has been viewed 89 times

  • 1.  Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 03, 2022 09:23 PM
    Hello everyone,

    I would like to count on your support to try to figure out the root of the following issue.

    The company has bought two Aruba 8300 and I am trying to configure the chassis to be able to be connected to the current two Aruba cx 6300 switches, but for some reason I am getting the following error, LACP-BLOCK. I have reconfigured the switches several time and the issue persist. 


    The vsx is syncronized and everything looks good, I am sharing with you the current config for the CX8320 primary and secondary and also the CX6300.

    PRIMARY_SW

    Current configuration:
    !
    !Version ArubaOS-CX TL.10.05.0010
    !export-password: default
    hostname SW-8320-PRI
    clock timezone america/Arizona
    debug lag all
    vrf KA
    ntp server 172.21.16.112
    ntp enable
    !
    !
    !
    ssh server vrf mgmt
    vlan 1
    vlan 10
    name ESXi Management
    vsx-sync
    vlan 11
    name vSAN Network
    vsx-sync
    vlan 12
    name vMotion Network
    vsx-sync
    vlan 13
    name Switches
    vsx-sync
    vlan 14
    name Switch Management
    vsx-sync
    vlan 15
    name iLO_Management
    vsx-sync
    vlan 999
    name L3-OSPF
    vsx-sync
    interface mgmt
    no shutdown
    ip dhcp
    interface lag 5 multi-chassis
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 6 multi-chassis
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 7 multi-chassis
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 8 multi-chassis
    no shutdown no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 100
    no shutdown
    description ISL
    no routing
    vlan trunk native 1 tag
    vlan trunk allowed all
    lacp mode active
    interface lag 250 multi-chassis
    no shutdown
    description MC_10Gbps
    no routing
    vlan trunk native 13 tag
    vlan trunk allowed 10-15
    lacp mode active
    qos trust dscp
    spanning-tree bpdu-guard
    spanning-tree tcn-guard
    spanning-tree port-type admin-edge interface 1/1/5
    no shutdown
    lag 5
    interface 1/1/6
    no shutdown
    lag 6
    interface 1/1/7
    no shutdown
    lag 7
    interface 1/1/8
    no shutdown
    lag 8
    interface 1/1/17
    no shutdown
    no routing
    vlan access 313
    interface 1/1/19
    no shutdown
    no routing
    vlan access 313
    interface 1/1/47
    no shutdown
    mtu 9100 lag 250
    interface 1/1/48
    no shutdown
    vrf attach KA
    description KEEPALIVE
    ip address 192.168.0.1/30
    interface 1/1/49
    no shutdown
    mtu 9198
    description ISL
    lag 100
    interface 1/1/50
    no shutdown
    mtu 9198
    description ISL
    lag 100
    interface loopback 1
    description R-ID
    ip address 1.1.1.1/32
    ip ospf 1 area 0.0.0.0
    interface vlan 13
    description Switches+iLO ip address 192.168.131.120/27
    active-gateway ip mac 00:00:00:00:83:20
    active-gateway ip 192.168.131.222
    ip ospf 1 area 0.0.0.0
    interface vlan 999
    description L3-OSPF
    ip address 172.16.0.1/30
    ip ospf 1 area 0.0.0.0
    no ip ospf passive
    ip ospf network point-to-point
    vsx
    inter-switch-link lag 100
    role primary
    keepalive peer 192.168.0.2 source 192.168.0.1 vrf KA
    vsx-sync time
    !
    !
    !
    !
    !
    router ospf 1 vrf 313
    area 0.0.0.0
    router ospf 1 router-id 1.1.1.1
    passive-interface default
    redistribute connected
    area 0.0.0.0
    https-server vrf mgmt

    #################%%%%%%%%%%%%%%%##################

    Secondary

    Current configuration:
    !
    !Version ArubaOS-CX TL.10.05.0010
    !export-password: default
    clock timezone america/Arizona
    debug vsx all
    debug mstp all
    debug lag all
    vrf KA
    ntp server 172.21.16.112
    ntp enable
    !
    !
    !
    ssh server vrf mgmt
    vlan 1 vlan 10
    name ESXi Management
    vsx-sync
    vlan 11
    name vSAN Network
    vsx-sync
    vlan 12
    name vMotion Network
    vsx-sync
    vlan 13
    name Switches+iLO
    vsx-sync
    vlan 14
    name Switch Management
    vsx-sync
    vlan 15
    name iLO_Management
    vsx-sync
    vlan 999
    name L3-OSPF
    vsx-sync
    interface mgmt
    no shutdown
    ip dhcp
    interface lag 5 multi-chassis no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 6 multi-chassis
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 7 multi-chassis
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 8 multi-chassis
    no shutdown
    no routing vlan trunk native 1
    vlan trunk allowed 10-13
    lacp mode active
    hash l2-src-dst
    interface lag 100
    no shutdown
    description ISL
    no routing
    vlan trunk native 1 tag
    vlan trunk allowed all
    lacp mode active
    interface lag 250 multi-chassis
    no shutdown
    description MC
    no routing
    vlan trunk native 13 tag
    vlan trunk allowed 10-15
    lacp mode active
    qos trust dscp
    spanning-tree bpdu-guard
    spanning-tree tcn-guard
    spanning-tree port-type admin-edge
    interface 1/1/5 no shutdown
    lag 5
    interface 1/1/6
    no shutdown
    lag 6
    interface 1/1/7
    no shutdown
    lag 7
    interface 1/1/8
    no shutdown
    lag 8
    interface 1/1/17
    no shutdown
    no routing
    vlan access 313
    interface 1/1/19
    no shutdown
    no routing
    vlan access 313
    interface 1/1/21
    no shutdown
    no routing interface 1/1/47
    no shutdown
    mtu 9100
    lag 250
    interface 1/1/48
    no shutdown
    vrf attach KA
    description KEEPALIVE
    ip address 192.168.0.2/30
    interface 1/1/49
    no shutdown
    mtu 9198
    description ISL
    lag 100
    interface 1/1/50
    no shutdown
    mtu 9198
    description ISL
    lag 100
    interface loopback 1
    description R-ID
    ip address 2.2.2.2/32
    ip ospf 1 area 0.0.0.0 interface vlan 313
    description Switches+iLO
    ip address 192.168.131.120/27
    active-gateway ip mac 00:00:00:00:83:20
    active-gateway ip 192.168.131.222
    ip ospf 1 area 0.0.0.0
    interface vlan 999
    description L3-OSPF
    ip address 172.16.0.2/30
    ip ospf 1 area 0.0.0.0
    no ip ospf passive
    ip ospf network point-to-point
    vsx
    inter-switch-link lag 100
    role secondary
    keepalive peer 192.168.0.1 source 192.168.0.2 vrf KA
    vsx-sync time
    !
    !
    !
    !
    !
    router ospf 1 router-id 2.2.2.2
    passive-interface default
    redistribute connected
    area 0.0.0.0
    https-server vrf mgmt


    #################%%%%%%%%%%%%%%%##################

    CX 6300_Switches 

    interface lag 250
    no shutdown
    description Link_to_Branch
    no routing
    vlan trunk native 313
    vlan trunk allowed 1,310-315
    lacp mode active
    !
    !
    interface 1/1/15
    no shutdown
    mtu 9100
    description Link_to_Branch
    lag 250
    !
    interface 2/1/15
    no shutdown
    mtu 9100
    description Link_to_Branch
    lag 250
    !

    Show vsx status config-sync

    Thanks in advance.

    Regards
    ​

    ------------------------------
    Scott James
    ------------------------------


  • 2.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 04, 2022 02:43 AM
    Hi Scott, to me there is something weird about VLANs' membership on involved LAG logical interfaces (the VSX LAG - which is a Multi-Chassis on the Aruba 8320 VSX side - and a standard LAG on the Aruba CX 6300 VSF Stack side). To be honest I'm not seeing a match.

    LAGs (VSX and Standard) should, first of all, have matching VLANs membership.

    Where is the LAG 200 (as per your screenshot)?

    Aruba 8320 VSX side, based on the running configurations you shared, I see a Multi-Chassis LAG (VSX LAG) lag250 made of interface 1/1/47 of the VSX Primary and interface 1/1/47 of the VSX Secondary, this VSX LAG lag250 is tagged on these VLAN IDs: VLAN 13 (native tagged), 10-14. The MTU is 9100.

    Aruba CX 6300 side, based on the running configuration you shared, I see the LAG lag250 made of interface 1/1/15 of the 1st VSF Member and interface 2/1/15 of 2nd VSF Member, this lag250 logical interface has: VLAN 313 (Native untagged), VLAN 1 and 310-315 tagged.

    Pretty strange. Isn'it?



    Original Message


  • 3.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 04, 2022 06:31 AM
    Please share output of: 

    show lacp interface multi-chassis

    ------------------------------
    Vincent Giles
    ------------------------------

    Original Message


  • 4.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 04, 2022 11:20 AM

    Hello, 

    This is the new running-config,

    vrf KA 
    vlan 310
    name ESXi Management
    vsx-sync
    vlan 311
    name vSAN Network
    vsx-sync
    vlan 312
    name vMotion Network
    vsx-sync
    vlan 313
    name Switches+iLO
    vsx-sync
    vlan 314
    interface mgmt
    no shutdown
    ip dhcp
    interface lag 100
    no shutdown
    description ISL
    no routing
    vlan trunk native 1 tag
    vlan trunk allowed all
    lacp mode active
    interface lag 200 multi-chassis
    no shutdown
    description MC_A_IDC
    no routing
    vlan trunk native 313
    vlan trunk allowed 1,310-313
    lacp mode active
    interface 1/1/25
    no shutdown
    no routing
    vlan access 310
    interface 1/1/27
    no shutdown
    no routing
    vlan access 310
    interface 1/1/47
    no shutdown
    mtu 9100
    description MC_A_IDC
    lag 200
    interface 1/1/48
    no shutdown
    vrf attach KA
    description KEEPALIVE
    ip address 192.168.0.1/30
    interface 1/1/49
    no shutdown
    mtu 9198
    lag 100
    interface 1/1/50
    no shutdown
    mtu 9198
    lag 100
    interface vlan 313
    vsx-sync active-gateways
    description Switches+iLO
    ip address 10.91.31.220/27
    active-gateway ip mac 00:00:00:00:83:20
    active-gateway ip 10.91.31.222
    vsx
    system-mac 02:01:00:00:01:00
    inter-switch-link lag 100
    role primary
    keepalive peer 192.168.0.2 source 192.168.0.1 vrf KA
    vsx-sync aaa bfd-global bgp dhcp-relay mclag-interfaces ospf qos-global route-map vsx-global



    Secondary

    vrf KA
    vlan 310
    name ESXi Management
    vsx-sync
    vlan 311
    name vSAN Network
    vsx-sync
    vlan 312
    name vMotion Network
    vsx-sync
    vlan 313
    name Switches+iLO
    vsx-sync
    interface mgmt
    no shutdown
    ip dhcp
    interface lag 100
    no shutdown
    description ISL
    no routing
    vlan trunk native 1 tag
    vlan trunk allowed all
    lacp mode active
    interface lag 200 multi-chassis
    no shutdown
    description MC_A_IDC
    no routing
    vlan trunk native 313
    vlan trunk allowed 1,310-313
    lacp mode active
    interface 1/1/47
    no shutdown
    mtu 9100
    description MC_A_IDC
    lag 200
    interface 1/1/48
    no shutdown
    vrf attach KA
    description KEEPALIVE
    ip address 192.168.0.2/30
    interface 1/1/49
    no shutdown
    mtu 9198
    lag 100
    interface 1/1/50
    no shutdown
    mtu 9198
    lag 100
    interface vlan 313
    vsx-sync active-gateways
    description Switches+iLO
    ip address 10.91.31.221/27
    active-gateway ip mac 00:00:00:00:83:20
    active-gateway ip 10.91.31.222
    vsx
    system-mac 02:01:00:00:01:00
    inter-switch-link lag 100
    role secondary
    keepalive peer 192.168.0.1 source 192.168.0.2 vrf KA
    vsx-sync aaa bfd-global bgp dhcp-relay mclag-interfaces ospf qos-global route-map vsx-global
    !
    !
    !
    !
    !
    https-server vrf mgmt


    ##########
    Switches 6300

    interface lag 200
    no shutdown
    no routing
    vlan trunk native 313
    vlan trunk allowed 1,310-315
    lacp mode active
    ​!
    !

    interface 1/1/15
    lag 200
    mtu 9100
    no shutdown
    !
    interface 2/1/15
    lag 200
    mtu 9100
    no shutdown


    SW-8320-SEC# show lacp interface 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/47 lag200(mc) 1047 1 ALFOE 02:01:00:00:01:00 65534 200


    Partner details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Partner Port State System-ID System Aggr
    name Port-id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 0 65534 PLFOEX 00:00:00:00:00:00 65534 0


    Remote Actor details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Port Port State System-ID System Aggr
    name id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 47 1 ALFNCD 02:01:00:00:01:00 65534 200


    Remote Partner details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Partner Port State System-ID System Aggr
    name Port-id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 80 1 ALFNCD b8:d4:e7:0b:32:c0 65534 200

    **************************

    SW-8320-PRI# show lacp interface 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/47 lag200(mc) 47 1 ALFNCD 02:01:00:00:01:00 65534 200


    Partner details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Partner Port State System-ID System Aggr
    name Port-id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 80 1 ALFNCD b8:d4:e7:0b:32:c0 65534 200


    Remote Actor details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Port Port State System-ID System Aggr
    name id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 1047 1 ALFOE 02:01:00:00:01:00 65534 200


    Remote Partner details of all interfaces:
    ----------------------------------------------------------------------------------
    Intf Aggregate Partner Port State System-ID System Aggr
    name Port-id Priority Priority Key
    ----------------------------------------------------------------------------------
    1/1/47 lag200(mc) 0 65534 PLFOXE 00:00:00:00:00:00 65534 0






    ------------------------------
    Scott James
    ------------------------------

    Original Message


  • 5.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 04, 2022 12:46 PM
    Are the 2x 6300 in VSF ?
    Is the regular LAG properly set-up on VSF to the 8320 LAG200 ?

    ------------------------------
    Vincent Giles
    ------------------------------

    Original Message


  • 6.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 04, 2022 01:48 PM
    1. Hello,
    Yes the 6300 are configured with VSF, however I have configured lag multichassis from the 8300 to 6300 switches

    ------------------------------
    Scott James
    ------------------------------

    Original Message


  • 7.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 05, 2022 05:29 AM
    Hello Scott,

    we're all implying that you're linking physical interfaces with same speed and media type.

    VSF side:

    A standard LAG (with LACP) made of 2 interfaces (1/1/15 and 2/1/15), one interface on a VSF member (1/1/15) and the other interface on another VSF member (2/1/15).

    interface lag 200
       no shutdown
       no routing
       vlan trunk native 313
       vlan trunk allowed 1,310-315
       lacp mode active
    ​exit

    interface 1/1/15
       lag 200
       mtu 9100
       no shutdown
    exit

    interface 2/1/15
       lag 200
       mtu 9100
       no shutdown
    exit

    to

    VSX side

    A Multi-Chassis LAG (with LACP) - also called VSX LAG - made of a total of 2 interfaces (say 10G): one physical interface on VSX Primary member and the other interface on the VSX Secondary member. VSX LAG lag200 (1/1/47 on VSX Primary and 1/1/47 on VSX Secondary) looks:

    VSX LAG lag200 (defined on each VSX member):

    interface lag 200 multi-chassis
       no shutdown
       description MC_A_IDC
       no routing
       vlan trunk native 313
       vlan trunk allowed 1,310-313
       lacp mode active
    exit

    VSX LAG lag200's physical interface member (defined on each VSX member):

    interface 1/1/47
       no shutdown
       mtu 9100
       description MC_A_IDC
       lag 200
    exit

    Is this correct?

    ------------------------------
    Davide Poletto
    ------------------------------

    Original Message


  • 8.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 06, 2022 02:39 PM
    Hi Parnassus et all,

    Thank you so much for your time,

    I have configured the switches like the configuration that you described,, but the issue perssits, I don't know why but I tried to configure a "normal" LACP on the primary switches and also I get the same LACP-block

    I was checking the logs and got this events with LAG-Multi-chassis,

    2022-02-04T15:30:13.535055+00:00 SW-8320-PRI lacpd[1666]: Event|1310|LOG_WARN|AMM|1/1|Partner is out of sync for interface 1/1/47 LAG sport: 2. Actor state:
    2022-02-04T15:30:13.529979+00:00 SW-8320-PRI lacpd[1666]: Event|1321|LOG_INFO|AMM|1/1|LAG 200 State change for interface 1/1/47: Actor state: ALFOX, PartnerO
    2022-02-04T15:30:13.526476+00:00 SW-8320-PRI lacpd[1666]: Event|1321|LOG_INFO|AMM|1/1|LAG 200 State change for interface 1/1/47: Actor state: ALFOE, PartnerO
    2022-02-04T15:30:13.522871+00:00 SW-8320-PRI lacpd[1666]: Event|1321|LOG_INFO|AMM|1/1|LAG 200 State change for interface 1/1/47: Actor state: ALFOE, PartnerO
    2022-02-04T15:30:13.522101+00:00 SW-8320-PRI lacpd[1666]: Event|1309|LOG_INFO|AMM|1/1|Partner is detected for interface 1/1/47 LAG 200 : 65534,00:00:00:00:0
    2022-02-04T15:30:13.518525+00:00 SW-8320-PRI lacpd[1666]: Event|1321|LOG_INFO|AMM|1/1|LAG 200 State change for interface 1/1/47: Actor state: ALFO, Partner O




    BTW, what's mean ALFO?

    I hope this can help.

    Regards!!!!

    ------------------------------
    Scott James
    ------------------------------

    Original Message


  • 9.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 07, 2022 04:53 AM
    Hello Scott, would you be so kind to post the output of these two commands executed on the VSX side?

    show lacp interfaces multi-chassis (to see local Actor/Partner and remote Actor/Partner connectivity)
    show lacp interfaces multi-chassis 1/1/47
    show lacp interfaces multi-chassis 1/1/47 vsx-peer

    FYI: "ALFO" status means A=Active + L=Long-timeout + F=Aggregable + O=Out-of-sync <- your LACP driven VSX LAG lag200 is out-of-sync on a particular member interface, normally one would expect to see "ALFNCD" on all VSX LAG member interfaces.

    ------------------------------
    Davide Poletto
    ------------------------------

    Original Message


  • 10.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 14, 2022 03:40 PM
    do you have check no physical issue ? (wrong cabling port) with show lldp ?

    ------------------------------
    PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...

    PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)

    PowerArubaCL: Powershell Module to use Aruba Central

    PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..

    ACEP / ACMX #107 / ACDX #1281
    ------------------------------

    Original Message


  • 11.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 15, 2022 03:41 PM
    Dear All,

    I have updated the switches to the version ArubaOS-CX_8320_10_07_0040.swi but the issue persist. =s =(

    Any other recommendation?

    Regards

    ------------------------------
    Scott James
    ------------------------------

    Original Message


  • 12.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 15, 2022 06:00 PM
    Hello Scott,

    I saw you followed the suggestion made by Stanislav but why just updating your Aruba 8320 VSX from ArubaOS-CX 10.05.0010 to ArubaOS-CX 10.07.0040 (November 2021) when the ArubaOS-CX 10.07.0061 (February 2022) is readily available for both the Aruba 8320 and the Aruba 6300 switch series?

    Is there a particular reason for not moving directly to latest available AOS-CX 10.07 software build?

    Don't know if your setup is still the same (as per configuration you posted above), anyway...would you be so kind to post the outputs of these three commands executed on the VSX side?

    show lacp interfaces multi-chassis (to see local Actor/Partner and remote Actor/Partner connectivity)
    show lacp interfaces multi-chassis 1/1/47
    show lacp interfaces multi-chassis 1/1/47 vsx-peer

    This is becoming curious.

    ------------------------------
    Davide Poletto
    ------------------------------

    Original Message


  • 13.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 08, 2022 05:57 AM
    Hi Scot,

    Did you try to disable/enable the VSX LAG (should be performed on both VSX nodes), or even reboot the whole VSX cluster with the VSX Lag configured and enabled? 
    I saw you're using a bit older SW version with your 8320 switches. I am asking the above question because there are some known issues with the LAGs (you can check this out in the Release Notes of the other branches - 10.06 and 10.07 for example). A good first step will be upgrade of the SW of the 8320 switches, before diving more in troubleshooting - upgrade will be needed for sure in the near future.

    ------------------------------
    Stanislav Naydenov
    ------------------------------

    Original Message


  • 14.  RE: Multi-Chassis on CX 8320 with Cx6300 LACP-BLOCKED

    Posted Feb 15, 2022 03:42 PM
    Hi, 

    I have updated the switches to the version ArubaOS-CX_8320_10_07_0040.swi but the issue persist.

    Any other recommendation?

    ------------------------------
    Scott James
    ------------------------------

    Original Message


Related Content