topic Re: Ports blocked when moving LACP connection to new switches in ExtremeSwitching (EXOS/Switch Engine)

Ports blocked when moving LACP connection to new switches

Stephen_Stormon — Wed, 10 Jan 2024 20:40:50 GMT

We currently both connections from our ISP connected to one X460-48t switch (16.2.5.4 16.2.5.4-patch1-30)

Ports are set to auto-negotiate.

enable sharing 51 grouping 51-52 algorithm address-based L2 lacp

We are attempting to move the connections to two Extreme Networks x695 switches (31.7.1.4-patch1-36).

We can’t set the ports to auto-negotiate ("01/06/2024 07:35:24.10 <Warn:HAL.Port.OpticCfgCflct> The configuration for the LX optic module is not correct - please configure port 36 for auto-negotiation Off and speed 1000”), so they have to be manually configured.

Switch #1 configure ports 36 auto off speed 1000 duplex full enable sharing 36 grouping 36 algorithm address-based L2 lacp enable mlag port 36 peer x695-02 id 36 Switch #2 configure ports 36 auto off speed 1000 duplex full enable sharing 36 grouping 36 algorithm address-based L2 lacp enable mlag port 36 peer x695-01 id 36

However, when we move the cables to the new switches, XOS is disabling the ports. We don't have spanning tree enabled, so that isn't the issue. I opened a case and the best guess is because the ISP portal is set to auto-negotiation on the ports whereas we have them set to manual. We won't be able to test changing the ISP portal settings to auto-negotiation off until 2/3, but has anyone run into an issue where a mismatch of auto-negotiation blocks ports?

Re: Ports blocked when moving LACP connection to new switches

Stefan_K_ — Wed, 10 Jan 2024 21:03:00 GMT

Hi Stephen,

1 Gig Fiber-Lines and X695... Always a mess. 🙂 I never got it running if the remote side has Auto-Neg enabled, because it's a chipset limitation. (see Q A: Does the x695 support auto negotiation at 1gb or 10gb? | Extreme Portal (site.com)) Afaik other newer switches (5520, 5420...) are also affected.

What wonders me is that you said the port is getting disabled. I only observed that in such cases one side of the line got a "link up" and the other side remained down.

I think there is no other way than "correcting" the Auto-Nego Settings on the ISP-Router.

Best regards
Stefan

Re: Ports blocked when moving LACP connection to new switches

Stephen_Stormon — Thu, 11 Jan 2024 14:52:52 GMT

Thanks for the reply. Yes, the port on both switches was showing a link but blocked (below). We will try hard setting the speed.

Untag: *36(Cyxtera-02)bgG Tag: *49(x695-02<->01)g,*1(5520-01_58)gG,*2(5520-02_58)gG,*3(5520-03_58)gG,*56(ST-Core_Uplink-40)gG,*51(x695-02<->03+04)gG Flags: (*) Active, (!) Disabled, (g) Load Sharing port (b) Port blocked on the vlan, (m) Mac-Based port (M) Mac-Based port with ingress filtering on (i) Port inactivated on the vlan due to VXLAN configuration (a) Egress traffic allowed for NetLogin (u) Egress traffic unallowed for NetLogin (t) Translate VLAN tag for Private-VLAN (s) Private-VLAN System Port, (L) Loopback port (x) VMAN Tag Translated port (A) Dynamically added by Auto-peering (F) Dynamically added by Fabric Attach (G) Multi-switch LAG Group port

Re: Ports blocked when moving LACP connection to new switches

Rey_Juan_Carlos — Tue, 16 Jan 2024 08:09:51 GMT

What is showing the log for ports 36 when they are blocked?

Can you show us your config for the ISC link and mlag peers?

Re: Ports blocked when moving LACP connection to new switches

markus_of — Mon, 29 Jan 2024 10:25:50 GMT

If the ports are blocked, it sounds to me like a loop has been detected.

Can you reach both switches via the ISC?

Do you have ELRP active?

For the new models (5520, 5420...) we also had to buy new GBICs and turn off auto-negation.

Re: Ports blocked when moving LACP connection to new switches

Stephen_Stormon — Sun, 04 Feb 2024 05:59:18 GMT

Tried this again today, and the reason for the ports being blocked really was the fact that they were set to auto-negotiate on in the ISP control panel and auto-negotiate off on the ports. Switching the ISP to auto off resolved the blocking.