Wired Intelligent Edge

 View Only
Back to discussions
Expand all | Collapse all

Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

This thread has been viewed 95 times

  • 1.  Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 04:45 PM

    Hi 

    I have two CX switches configured in VSX. From each switch, one port connects via a DAC cable to an HPE DL360Gen11 server. This server runs Windows Server 2022.

    I have configured a multi-chassis link aggregation from the switch side and from the server side, teaming has been configured with the two server ports in LACP mode and with dynamic load balancing.

    Switch Configuration:

    Ports Configuration:

    Server configuration: 

    The LAG goes up on ToR Switch 1 and remains in the ALFNCD state, but when I activate the lag from ToR Switch 2, negotiation begins and the state changes to ASFNCD and ALFNCDX. The port begins to go up and down. From the server side, Ethernet port 2 displays a "faulted lacp negotiation" message and connectivity to other servers starts to become intermittent. 

    For now, the solution has been to disable the Switch 2 port. I've also checked, and there's no problem with the cables or the ports on the server or the switches. I'd like to know if anyone has experienced this same problem and if it has been resolved. I think the switch configuration is fine, but I'd like your opinion and perhaps some configuration advice for the server side.

    Thanks.



  • 2.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 05:03 PM

    I will take the example on you configuring the LAG symmetrical using  interfaces 1/1/1

    interface lag 100
        description To_Server
        mode active
        no shutdown
        vsx-sync
            lag
        exit
     
    interface 1/1/1
        no shutdown
        lag 100
    On the Windows Server 2022 you need to do teaming mode LACP , Load balacning using Address Hash or Hyper-V Port, (do not use Dynamic). On Standby adapter leave it as None. 




    ------------------------------
    Shpat | ACEP | ACMP | ACCP | ACDP
    Just an Aruba enthusiast and contributor by cases
    If you find my comment helpful, KUDOS are appreciated.
    ------------------------------

    Original Message


  • 3.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 05:33 PM

    Hi Shpat 

    When you refer to configuring the LAG symmetrical, do you mean lag in multi-chassis? Both switches are 8100, so I'm using the lag in multi-chassis.


    Original Message


  • 4.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 05:39 PM

    Yes, correct. You need to have identical LAG Configuration on both switches for the ports where the servers are connected.



    ------------------------------
    Shpat | ACEP | ACMP | ACCP | ACDP
    Just an Aruba enthusiast and contributor by cases
    If you find my comment helpful, KUDOS are appreciated.
    ------------------------------

    Original Message


  • 5.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 06:49 PM

    Hi

    Yes, I have the configuration like this. I just noticed that the images I posted didn't paste. The configuration on both switches side is like this:

    interface lag 7 multi-chassis
        description Servidor AD
        no shutdown
        no routing
        vlan access 4
        lacp mode active
        lacp fallback
        loop-protect
        spanning-tree bpdu-guard
        spanning-tree tcn-guard
        spanning-tree port-type admin-edge
        exit

    I tried the LACP and Hash Address configuration, and it didn't work. I'll try LACP and Hyper-V Port, but I'm pretty sure it still didn't work this morning.


    Original Message


  • 6.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 23, 2025 08:38 PM

    Hi

    An update: I just tried putting on Windows Server the LACP and Hyper-V Port, but the LACP on Switch 2 port drops:

    The state on the port of Switch 1 is formed correctly, but on Switch 2 its state changes constantly.

    What could generate this behavior?

    I appreciate some help.


    Original Message


  • 7.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 01:37 AM
    Edited by r.grossmann Apr 24, 2025 01:44 AM

    Hi,

    From my point of view the LAG or LACP on the Servers side / virtual Switch is not configured properly.
    I do not see an "Aggr Key" (just a zero) at the partner details part on both switches.
    My LAG/LACP Neighbors (Switches and Fujitsu VMware ESX Hosts) do have a "Aggr Key" at partner details.

    With one exception:
    There is one Server which I hadn't configured with LAG/LACP yet, but the Switch Port is configured for MCLAG with LACP AND the MCLAG is configured with "lacp fallback". There is where I can't see a Partners "Aggr Key" diffferent from zero ("0").

    To investigate the switchside more further, please give us your actual VSX and physical and lag port configs.

    Kind regards

    Robert

    PS: The LACP timers should match on, too. Not a must, but a suggestion. The MTU on both physical switchport must match, and its a suggestion to take the same on the servers side.

    PS2: I share my Aruba switch (8325 VSX) config to an Distributed virtual Switch on an Fujitsu Server with VMware OS in a Vspehere Vcenter Environment:

    sdsw-rz-r08# sh run int 1/1/19
interface 1/1/19
    description VMs-Srv7-25G-0027-vmnic2
    no shutdown
    mtu 9100
    lag 31
    exit

sdsw-rz-r08# sh run int 1/1/19 vsx
interface 1/1/19
    description VMs-Srv7-25G-0027-vmnic10
    no shutdown
    mtu 9100
    lag 31
    exit

sdsw-rz-r08# sh ru int lag 31
interface lag 31 multi-chassis
    description VMs-Srv7-0027
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed all
    lacp mode active
    lacp fallback
    spanning-tree root-guard
    spanning-tree tcn-guard
    spanning-tree port-type admin-edge
    exit

sdsw-rz-r08# sh ru int lag 31 vsx
interface lag 31 multi-chassis
    description VMs-Srv7-0027
    no shutdown
    no routing
    vlan trunk native 1
    vlan trunk allowed all
    lacp mode active
    lacp fallback
    spanning-tree root-guard
    spanning-tree tcn-guard
    spanning-tree port-type admin-edge
    exit

sdsw-rz-r08# sh lacp interfaces 1/1/19
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
Aggregate-name : lag31(multi-chassis)
-------------------------------------------------
                       Actor             Partner
-------------------------------------------------
Port-id            | 19                 | 5
Port-priority      | 1                  | 255
Key                | 31                 | 19
State              | ALFNCD             | ALFNCD
System-ID          | 0a:00:0c:02:01:00  | ec:e7:a7:04:e4:94
System-priority    | 65534              | 1

sdsw-rz-r08# sh lacp interfaces 1/1/19 vsx
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
Aggregate-name : lag31(multi-chassis)
-------------------------------------------------
                       Actor             Partner
-------------------------------------------------
Port-id            | 1019               | 4
Port-priority      | 1                  | 255
Key                | 31                 | 19
State              | ALFNCD             | ALFNCD
System-ID          | 0a:00:0c:02:01:00  | ec:e7:a7:04:e4:94
System-priority    | 65534              | 1

sdsw-rz-r08# sh lacp aggregates lag31
Aggregate name   : lag31 (multi-chassis)
Interfaces       : 1/1/31 1/1/19
Peer interfaces  : 1/1/31 1/1/19
Heartbeat rate   : Slow
Hash             : l3-src-dst
Aggregate mode   : Active

sdsw-rz-r08# sh lacp aggregates lag31 vsx
Aggregate name   : lag31 (multi-chassis)
Interfaces       : 1/1/31 1/1/19
Peer interfaces  : 1/1/31 1/1/19
Heartbeat rate   : Slow
Hash             : l3-src-dst
Aggregate mode   : Active

sdsw-rz-r08#


    Original Message


  • 8.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 11:40 AM

    Hi Robert

    This is my VSX configuration: 

    • Ports 1/1/25 and 1/1/26 on both switches are ISL Links
    • Port 1/1/24 on both switches is keepalive link
    ToR-PERS-1# sh vsx status
    VSX Operational State
    ---------------------
      ISL channel             : In-Sync
      ISL mgmt channel        : operational
      Config Sync Status      : In-Sync
      NAE                     : peer_reachable
      HTTPS Server            : peer_reachable
     
    Attribute           Local               Peer
    ------------        --------            --------
    ISL link            lag256              lag256
    ISL version         2                   2
    System MAC          02:00:00:00:01:00   02:00:00:00:01:00
    Platform            8100                8100
    Software Version    LL.10.13.1080       LL.10.13.1080
    Device Role         primary             secondary
    ToR-PERS-1# sh lag 256
    System-ID       : 34:c5:15:00:b3:c0
    System-priority : 65534
     
    Aggregate lag256 is up
     Admin state is up
     Description : ISL Link
     Type                        : normal
     Lacp Fallback               : Disabled
     MAC Address                 : 34:c5:15:00:b3:c0
     Aggregated-interfaces       : 1/1/25 1/1/26
     Aggregation-key             : 256
     Aggregate mode              : active
     Hash                        : l3-src-dst
     LACP rate                   : slow
     Speed                       : 80000 Mb/s
     Mode                        : trunk

    ToR-PERS-1# sh lag 256 vsx-peer
    System-ID       : 34:c5:15:00:6c:80
    System-priority : 65534
     
    Aggregate lag256 is up
     Admin state is up
     Description : ISL Link
     Type                        : normal
     Lacp Fallback               : Disabled
     MAC Address                 : 34:c5:15:00:6c:80
     Aggregated-interfaces       : 1/1/25 1/1/26
     Aggregation-key             : 256
     Aggregate mode              : active
     Hash                        : l3-src-dst
     LACP rate                   : slow
     Speed                       : 80000 Mb/s
     Mode                        : trunk
    ToR-PERS-1# sh running-config interface lag256
    interface lag 256
        description ISL Link
        no shutdown
        no routing
        vlan trunk native 1
        vlan trunk allowed all
        lacp mode active
        exit
    ToR-PERS-1# sh running-config interface lag256 vsx-peer
    interface lag 256
        description ISL Link
        no shutdown
        no routing
        vlan trunk native 1
        vlan trunk allowed all
        lacp mode active
        exit
    ToR-PERS-1# sh running-config interface 1/1/25-1/1/26
    interface 1/1/25
        description ISL port 1
        no shutdown
        mtu 9198
        lag 256
        exit
    interface 1/1/26
        description ISL port 2
        no shutdown
        mtu 9198
        lag 256
        exit
    ToR-PERS-1# sh running-config interface 1/1/25-1/1/26 vsx-peer
    interface 1/1/25
        description ISL port 1
        no shutdown
        mtu 9198
        lag 256
        exit
    interface 1/1/26
        description ISL port 2
        no shutdown
        mtu 9198
        lag 256
        exit
    The config for LACP Multi-Chassis to Server: 
    ToR-PERS-1# sh running-config interface lag 7
    interface lag 7 multi-chassis
        description Servidor AD
        no shutdown
        no routing
        vlan access 4
        lacp mode active
        lacp fallback
        loop-protect
        spanning-tree bpdu-guard
        spanning-tree tcn-guard
        spanning-tree port-type admin-edge
        exit
    ToR-PERS-1# sh running-config interface lag 7 vsx-peer
    interface lag 7 multi-chassis
        description Servidor AD
        no shutdown
        no routing
        vlan access 4
        lacp mode active
        lacp fallback
        loop-protect
        spanning-tree bpdu-guard
        spanning-tree tcn-guard
        spanning-tree port-type admin-edge
        exit
    ToR-PERS-1# sh running-config interface 1/1/17
    interface 1/1/17
        description Servidor_AD
        no shutdown
        mtu 9000
        lag 7
        exit
    ToR-PERS-1# sh running-config interface 1/1/17 vsx-peer
    interface 1/1/17
        description Servidor_AD
        no shutdown
        mtu 9000
        lag 7
        exit
    How can I configure the timers? The MTUs are set to 9000 on both the switch and server sides.

    Original Message


  • 9.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 02:44 AM

    Maybe you could check those two videos and compare configs:

    HPE Aruba Networks AOS-CX Basics 6 - LACP

    04- Configure NIC teaming and LACP Protocol server 2022 step by step.

    Maybe there is a step you might be missing during the configuration of the LACP within the Windows Server.



    ------------------------------
    Shpat | ACEP | ACMP | ACCP | ACDP
    Just an Aruba enthusiast and contributor by cases
    If you find my comment helpful, KUDOS are appreciated.
    ------------------------------

    Original Message


  • 10.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 11:58 AM

    Hi shpat

    Thanks, We're reviewing this, but the NIC Teaming configuration video doesn't make it clear to me. At minute 6:56, the configuration is seen as Switch Independent and Address Hash. Then, in Standby Adapter, it tries to configure it with LACP. Then, an error message appears indicating that only Switch Independent is supported.

    We continue reviewing and testing.


    Original Message


  • 11.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 12:53 AM

    That error shown on 6:56 is normal for what they tried to do. Also, just checking, on both physical NIC cards, did you remove the IP Addressing and leave the IP Address only on the NIC Teaming ?



    ------------------------------
    Shpat | ACEP | ACMP | ACCP | ACDP
    Just an Aruba enthusiast and contributor by cases
    If you find my comment helpful, KUDOS are appreciated.
    ------------------------------

    Original Message


  • 12.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 10:38 AM

    Hi shpat

    We'll review it and I'll keep you updated, along with any other tests we'll be performing. Thanks!


    Original Message


  • 13.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 09:02 AM
    Edited by parnassus Apr 24, 2025 09:23 AM

    Hello Diego, as others already wrote you it could be an issue on the bare metal server's OS side (is it an Microsoft Hyper-v or a Microsoft Windows Server 2022 the OS installed on the bare metal HPE ProLiant DL360 G11 server then?).

    In any case I add below one of our VSX LAG configuration used to connect to a bare metal IBM server running IBM PowerVM (similar to the one other posted).

    VSX LAG definition (VSX LAG definition is identical and VSX synchronized on VSX Primary and VSX Secondary, as you already know):

    interface lag 10 multi-chassis
        description IBM-VIOS-1-xxxxxxx-ent4
        no shutdown
        no routing
        vlan trunk native 2005
        vlan trunk allowed 2000,2005,2096,2100,2102-2103,2105-2109
        lacp mode active
        loop-protect
        loop-protect vlan 2000,2005,2096,2100,2102-2103,2105-2109

    The Spanning Tree related commands were omitted since the above is a LAG to a bare metal server not to a peer Switch (probably the loop protect options could be avoided too considering we are not going to cause a loop once we connect that physical server).

    Below the VSX LAG member interfaces 1/1/10 on VSX Primary and VSX Secondary (the only difference is the interface description):

    interface 1/1/10
        description IBM-VIOS-1-xxxxxxx-C8-T0-ent0-ent4
        no shutdown
        mtu 9198
        flow-control rx
        lag 10

    interface 1/1/10
        description IBM-VIOS-1-xxxxxxx-C6-T0-ent2-ent4
        no shutdown
        mtu 9198
        flow-control rx
        lag 10

    As you can see it's nothing special (VLAN memberships apart <- YMMV about that).


    Original Message


  • 14.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 24, 2025 11:52 AM

    Hi parnassus

    Is a HPE ProLiant DL360 G11 and the Windows Server 2022 OS was installed as baremetal. I checked your configuration and don't see many differences from mine. I'm still checking from the server side. I've put the details of my setup in another answer in case you want to validate anything.

    Thanks.


    Original Message


  • 15.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 06:30 AM

    Hello Diego, let's focus into the Server's NIC ports then.

    IMHO you should get rid of the vEthernet we see and restart by checking via PowerShell the available physical Ethernet adapters:

    Get-NetAdapter -Name * -Physical

    Then check their teaming capabilities:

    Get-NetAdapterAdvancedProperty -Name "*TeamingMode*" | Select-Object -Property DisplayName, DisplayValue

    Let me now to suppose you can (re)start from your two defaulted NICs (say "Ethernet 1" and "Ethernet 2") without anything else (no "TeamNIC" and no "vEthernet (Virtual-Switch-Externo)") - it should be possible to create the logical NIC Team (say "Team") working with the "LACP" Teaming Mode and "Dynamic" Load Balancing Algorithm and "Slow" LACP Timer:

    New-NetLbfoTeam -Name "Team" -TeamMembers "Ethernet 1","Ethernet 2" -TeamingMode LACP -LoadBalancingAlgorithm Dynamic -LacpTimer Slow

    Check the result:

    Get-NetLbfoTeam

    Can you post the outcome of the above procedure?

    Notes:

    LACP = Uses the IEEE 802.1ax Link Aggregation Control Protocol (LACP) to dynamically identify links that are connected between the host and a given switch (This protocol was formerly known as IEEE 802.3ad draft).

    Dynamic = Uses the source and destination TCP ports and the IP addresses to create a hash for outbound traffic. Moves outbound streams from team member to team member as needed to balance team member utilization.

    LACP Timer = it shouldn't necessarily it matches the one set on the peer device (Anyway I suggest you to set "slow" on both ends, in any case each end controls how often inter-connected devices exchange LACP Protocol Data Units PDUs or Control Messages from its stanpoint).


    Original Message


  • 16.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 10:37 AM

    Hi Parnassus

    Let's check it out and I'll let you know the results. Thanks!


    Original Message


  • 17.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 06:34 AM

    Hi Diego,
    The Switch configs seems to be fine.
    The LACP Rate Mode is configured with slow per default.
    On Switch side it could be changed in the lag interface via: lacp rate slow/fast
    You can chek it with: sh lacp aggregates lag7
    I don't know what the default setting is for Windows Server Teaming or how to adjust it, nor an aruba cli command to check it out for the neighbors port. But I guess it should not be a problem.

    So I really guess it must rely on the servers side :-(


    Original Message


  • 18.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 06, 2025 08:05 PM

    Hi Robert

    After configuring both the server side and the lag on the switch from scratch, I noticed that port 1/1/17 on Switch #2 wasn't working properly. I switched to port 1/1/19 and LACP started working better. However, and according to what you told me in a previous answer, I still see an "Aggr Key" at zero.

    ToR-PERS-1(config)# sh lacp interfaces 1/1/19
     
    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
     
     
    Aggregate-name : lag9(multi-chassis)
    -------------------------------------------------
                           Actor             Partner
    -------------------------------------------------
    Port-id            | 19                 | 1
    Port-priority      | 1                  | 1
    Key                | 9                  | 0
    State              | ALFNCD             | ASFNCD
    System-ID          | 02:00:00:00:01:00  | 6c:92:cf:cb:ae:6e
    System-priority    | 65534              | 0

    ToR-PERS-1(config)# sh lacp interfaces 1/1/19 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
     
     
    Aggregate-name : lag9(multi-chassis)
    -------------------------------------------------
                           Actor             Partner
    -------------------------------------------------
    Port-id            | 1019               | 2
    Port-priority      | 1                  | 1
    Key                | 9                  | 0
    State              | ALFNCD             | ASFNCD
    System-ID          | 02:00:00:00:01:00  | 6c:92:cf:cb:ae:6e
    System-priority    | 65534              | 0
     
    ToR-PERS-1(config)#
    It's strange, I no longer see any alerts or status changes on the interfaces. I even tested by disconnecting one of the ports, and the connection to the machines remains. I would expect the link status to be ALFNCD, but I see one link in ASFNCD status.
    On the server side, the configuration is basic: two interfaces in LACP and in Dynamic mode, I also tried with Address Hash and the behavior is the same.
    Could this be wrong?
    Thanks.

    Original Message


  • 19.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 07, 2025 05:42 AM

    Hi Diego,

    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
    So if you want to have actor and partner as same, you should change the server to slow timers or the switch to fast timers.

    For the switch side you can do it as told: lacp rate fast (default is slow).

    Afterwards both sidies should be on ASFNCD.

    Maybe the "Zero" will be gone then, too. But if not, perhaps it doesen't matter.  You can try with a simple ping test and plugging out and in both switchports (one after one), to see if you're loosing connection or if the MCLAG is working properly and a "failover" to the remaining active link is working.

    Kind regards
    Robert

    PS: unbeliveable that a single Switchport (or SFP?) has been broken

    Original Message


  • 20.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 07, 2025 10:35 AM

    Hi Robert

    Thanks for your response. As you indicated, I just tested it by changing the timer to fast on the switch side, and the lacp status is the same in both cases (ASFNCD).

    ToR-PERS-1(config)# sh lacp interfaces 1/1/19
     
    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
     
     
    Aggregate-name : lag9(multi-chassis)
    -------------------------------------------------
                           Actor             Partner
    -------------------------------------------------
    Port-id            | 19                 | 1
    Port-priority      | 1                  | 1
    Key                | 9                  | 0
    State              | ASFNCD             | ASFNCD
    System-ID          | 02:00:00:00:01:00  | 6c:92:cf:cb:ae:6e
    System-priority    | 65534              | 0

    As you can see, the "zero" hasn't disappeared, but the MC-LAG is working fine. Failover is working fine, and the ping remains active regardless of whether either port is powered on.

    PS: It seems the port isn't working logically; it was connected with an Aruba DAC cable. The port appears to be fine, the LED flashes on and off when disconnected, but when I plugged the same DAC cable into another port, LACP started working. I even tried the port as access only, without LACP, and the ping started to be intermittent. Very strange; I've never seen anything like this before.

    Kind regards.


    Original Message


  • 21.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 07, 2025 02:29 PM
    Have you done my advice? 




    Original Message


  • 22.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 07:24 AM

    Hi, there,

    Are you absolutely sure you have the 2 switches config exactly the same ?

    (I don't see cli output in your posting)

    If so; start removing line by line from the bottom up, switch by switch

    lacp mode active
        lacp fallback
        loop-protect
        spanning-tree bpdu-guard
        spanning-tree tcn-guard
        spanning-tree port-type admin-edge

    And see if anything changes.

    If same, start troubleshot hardware.

    Xross over cabes

    Xross over transceiver

    And see if faulty port switch to Ethernet (away from Ethernet 2)

    If fault messages move, replace hardware

    Please post result, step by step

    Steinar


    Original Message


  • 23.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 10:18 AM
    Diego could check and report back by executing:

    show vsx config-consistency
    show vsx config-consistency vsx-peer

    and:

    show vsx config-consistency lacp lag 7
    show vsx config-consistency lacp lag 7 vsx-peer

    just to be sure all is regular on VSX and lag 7.



    Original Message


  • 24.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 10:35 AM

    Hi parnassus

    This is the result of the requested commands, although they do not work with the vsx-peer, so I entered Switch 2 and executed them:

    ToR-PERS-1# show vsx config-consistency
    Configurations                          Local                                   Peer
    ------------------                      ------                                  ------
    Software Version                        LL.10.13.1080                           LL.10.13.1080
    System MAC                              02:00:00:00:01:00                       02:00:00:00:01:00
    System Profile                          Basic                                   Basic
    ISL hello interval                      1                                       1
    ISL dead interval                       20                                      20
    ISL hold interval                       0                                       0
    Keepalive hello interval                1                                       1
    Keepalive dead interval                 3                                       3
    Keepalive UDP port                      7678                                    7678

    VSX VLAN List
    -------------
    Local ISL VLANs : 1 4 40-42
    Peer ISL VLANs : 1 4 40-42

    VSX Active Forwarding
    ---------------------
    Interface VLANs      : None
    Peer Interface VLANs : None

    STP Configurations                      Local                                   Peer
    ------------------                      ------                                  ------
    STP Enabled                             Yes                                     Yes
    STP Mode                                mstp                                    mstp
    MST hello time(in seconds)              2                                       2
    MST maximum age(in seconds)             20                                      20
    MST maximum hops                        20                                      20
    MST Config Name                         02:00:00:00:01:00                       02:00:00:00:01:00
    MST Config Revision                     -                                       -
    MST Config Digest                       AC36177F50283CD4B83821D8AB26DE62        AC36177F50283CD4B83821D8AB26DE62
    MST number of instances                 0                                       0

    RPVST VLAN List:
    ----------------
    Local:
    Peer :

    Local Port Configurations
    =========================
    Port      Port-Type
    ---------------------

    Local VLAN Configurations
    =========================
    VLAN                PVLAN-Type          PVLAN-Association
    ---------------------------------------------------------

    Peer Port Configurations
    =========================
    Port      Port-Type
    ---------------------

    Peer VLAN Configurations
    =========================
    VLAN                PVLAN-Type          PVLAN-Association
    ---------------------------------------------------------

    ToR-PERS-1#

    ToR-PERS-2# show vsx config-consistency
    Configurations                          Local                                   Peer
    ------------------                      ------                                  ------
    Software Version                        LL.10.13.1080                           LL.10.13.1080
    System MAC                              02:00:00:00:01:00                       02:00:00:00:01:00
    System Profile                          Basic                                   Basic
    ISL hello interval                      1                                       1
    ISL dead interval                       20                                      20
    ISL hold interval                       0                                       0
    Keepalive hello interval                1                                       1
    Keepalive dead interval                 3                                       3
    Keepalive UDP port                      7678                                    7678

    VSX VLAN List
    -------------
    Local ISL VLANs : 1 4 40-42
    Peer ISL VLANs : 1 4 40-42

    VSX Active Forwarding
    ---------------------
    Interface VLANs      : None
    Peer Interface VLANs : None

    STP Configurations                      Local                                   Peer
    ------------------                      ------                                  ------
    STP Enabled                             Yes                                     Yes
    STP Mode                                mstp                                    mstp
    MST hello time(in seconds)              2                                       2
    MST maximum age(in seconds)             20                                      20
    MST maximum hops                        20                                      20
    MST Config Name                         02:00:00:00:01:00                       02:00:00:00:01:00
    MST Config Revision                     -                                       -
    MST Config Digest                       AC36177F50283CD4B83821D8AB26DE62        AC36177F50283CD4B83821D8AB26DE62
    MST number of instances                 0                                       0

    RPVST VLAN List:
    ----------------
    Local:
    Peer :

    Local Port Configurations
    =========================
    Port      Port-Type
    ---------------------

    Local VLAN Configurations
    =========================
    VLAN                PVLAN-Type          PVLAN-Association
    ---------------------------------------------------------

    Peer Port Configurations
    =========================
    Port      Port-Type
    ---------------------

    Peer VLAN Configurations
    =========================
    VLAN                PVLAN-Type          PVLAN-Association
    ---------------------------------------------------------

    ToR-PERS-2#

    ToR-PERS-1# show vsx config-consistency lacp lag7
    Configurations                          Local               Peer
    ------------------                      ------              ------
    Name                                    lag7                lag7
    Loop protect enabled                    true                true
    Hash scheme                             l3-src-dst          l3-src-dst
    Qos dscp
    Qos cos
    Qos trust

    VSX VLAN list
    4
    Peer VSX VLAN list
    4

    STP link-type                           point_to_point      point_to_point
    STP port-type                           admin-edge          admin-edge
    STP bpdu-filter                         Disabled            Disabled
    STP bpdu-guard                          Enabled             Enabled
    STP loop-guard                          Disabled            Disabled
    STP root-guard                          Disabled            Disabled
    STP rpvst-filter                        Disabled            Disabled
    STP rpvst-guard                         Disabled            Disabled
    STP tcn-guard                           Enabled             Enabled
    ToR-PERS-1#

    ToR-PERS-2# show vsx config-consistency lacp lag7
    Configurations                          Local               Peer
    ------------------                      ------              ------
    Name                                    lag7                lag7
    Loop protect enabled                    true                true
    Hash scheme                             l3-src-dst          l3-src-dst
    Qos dscp
    Qos cos
    Qos trust

    VSX VLAN list
    4
    Peer VSX VLAN list
    4

    STP link-type                           point_to_point      point_to_point
    STP port-type                           admin-edge          admin-edge
    STP bpdu-filter                         Disabled            Disabled
    STP bpdu-guard                          Enabled             Enabled
    STP loop-guard                          Disabled            Disabled
    STP root-guard                          Disabled            Disabled
    STP rpvst-filter                        Disabled            Disabled
    STP rpvst-guard                         Disabled            Disabled
    STP tcn-guard                           Enabled             Enabled


    Original Message


  • 25.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 06, 2025 08:10 PM

    Hi Parnassus

    After configuring both the server side and the lag on the switch from scratch, I noticed that port 1/1/17 on Switch #2 wasn't working properly. When I plugged it in, its status would start to change, and pings to other machines would become intermittent. To rule this out, we changed ports, taking ports 1/1/19 and creating a lag of 9 (all to maintain order). I switched to port 1/1/19 and LACP started working better. However, I still see an "Aggr Key" at zero when I see the partner details:

    ToR-PERS-1(config)# sh lacp interfaces 1/1/19
     
    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
     
     
    Aggregate-name : lag9(multi-chassis)
    -------------------------------------------------
                           Actor             Partner
    -------------------------------------------------
    Port-id            | 19                 | 1
    Port-priority      | 1                  | 1
    Key                | 9                  | 0
    State              | ALFNCD             | ASFNCD
    System-ID          | 02:00:00:00:01:00  | 6c:92:cf:cb:ae:6e
    System-priority    | 65534              | 0

    ToR-PERS-1(config)# sh lacp interfaces 1/1/19 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
     
     
    Aggregate-name : lag9(multi-chassis)
    -------------------------------------------------
                           Actor             Partner
    -------------------------------------------------
    Port-id            | 1019               | 2
    Port-priority      | 1                  | 1
    Key                | 9                  | 0
    State              | ALFNCD             | ASFNCD
    System-ID          | 02:00:00:00:01:00  | 6c:92:cf:cb:ae:6e
    System-priority    | 65534              | 0
     
    ToR-PERS-1(config)#
    It's strange, I no longer see any alerts or status changes on the interfaces. I even tested by disconnecting one of the ports, and the connection to the machines remains. I would expect the link status to be ALFNCD, but I see one link in ASFNCD status.
    On the server side, the configuration is basic: two interfaces in LACP and in Dynamic mode, I also tried with Address Hash and the behavior is the same.
    Could this be wrong?
    Thanks.

    Original Message


  • 26.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted Apr 25, 2025 10:42 AM

    Hi Steinar

    Yes, I'm sure the config between two switches is exactly the same.

    I posted my configuration in a previous post. I also ran hardware tests for the ports and cables. The problem seems to be in the server-side LACP configuration. I'll also run the tests you mentioned and will let you know the results. Thanks!


    Original Message


  • 27.  RE: Question about configuring a Link Aggregation beetwen CX Switches and a Windows Server

    Posted May 07, 2025 08:20 PM

    Hi Steinar

    Yes, I have followed your advice. For some strange reason, port 1/1/17 on Switch 2 was causing connectivity issues. I changed it to port 1/1/19, and when I saw that it worked better, I ran the LACP configuration again on this port, also from the server side. LACP is now working correctly. Although it seems a bit odd to me that a port would be failing, considering it's a new 8100 Switch.

    Thanks for your answers. Kind regards.


    Original Message


Related Content