topic Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected in ExtremeSwitching (EXOS/Switch Engine)

Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

Andrei1989 — Thu, 29 Oct 2020 20:23:22 GMT

I am using a project stack of 4 extreme switches (2-x670 vim 4-40G4X module, 2-x460 v80 module).

Updated switch version to 16.2.5.4 patch1-20

The port indication is on when the down command is forced, and when the physical cable is disconnected

This occurs on all ports on the switch and on stack ports.

cable removed

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

Miguel-Angel_RO — Thu, 29 Oct 2020 20:29:59 GMT

Andrei,

What’s the question?

Mig

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

Andrei1989 — Thu, 29 Oct 2020 20:36:08 GMT

Hi, mig.

Why on the ports the indication is on when it is off?

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

davidj_cogliane — Thu, 29 Oct 2020 20:45:42 GMT

Lights being on if there is no link sounds like a bug and I recommend opening a TAC case to report and try to resolve that.

If you look at the port in the CLI does it show disabled and ready?

The thing that really caught my attention though is the mixed stack. Are you aware that you are limited by the table sizes of the least powerful switch?

The stacking tool can show you what you are working with in your case.

https://stackingtool.extremenetworks.com/StackingTool/

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

Andrei1989 — Fri, 30 Oct 2020 13:39:34 GMT

Hi, David

Ports are disabled, but the LEDs on the switch are blinking. Problem with indication on stack ports and ethernet ports from 1 to 25, after 25 ethernet port and optical port indication works correctly.

The table sizes are not oversized

How do I open a support ticket?

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

davidj_cogliane — Fri, 30 Oct 2020 19:24:46 GMT

Andre,

You can open a support ticket online at https://extremeportal.force.com/extrsupporthome

Or you can call 1 800 872 8440 if your in the US or Canada, I don’t know the other number.

You misunderstood my table comment. I was trying to explain that the 670s are dumbed down because you stacked them with the 460s. From the image you shared that might not matter in your deployment, but I wanted to make sure you were aware.

Right in your screen shot you can see the theoretical maximum IPv4 routes on a 670 is 16,352 but because you stacked it with a 460 it is limited to 12,256.

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

Andrei1989 — Fri, 30 Oct 2020 19:39:11 GMT

Thank you David.On the 3rd and 4th switch in the stack (x460), I get multicast (1 Gbit in total), but already on the 1st and 2nd switches, it is delivered broken to me passing through the stack ports. The first 3 years, this problem was not observed, however, after 3 years of work, such problems began to arise.We also changed the cable, the module, updated the switch, the tables are not full. We do not understand the cause of the problem.

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

davidj_cogliane — Fri, 30 Oct 2020 19:50:21 GMT

A TAC case is definitely your best option at this point. They have access to the most information and I am sure they will be able to get you squared away.

Please post what the resolution is so the next person knows.

Re: Extreme x670 . The port indication is on when the down command is forced, and when the physical cable is disconnected

FredrikB — Fri, 06 Nov 2020 08:32:53 GMT

Some years ago we had a problem with stacking ports in the X460 and saw a lot of RX errors on those. TAC advised us to change some hidden timer values I think. You can check with this command:

show port stack-ports rxerrors no-refresh

==============================================================================
Port      Link     Rx      Rx      Rx        Rx      Rx         Rx         Rx
          State    Crc    Over    Under     Frag    Jabber      Align      Lost
================================================================================
1:1       A      244       0        0        0        0          0          0
1:2       A      792       0        0        0        0          0          0
3:1       A        5       0        0        0        0          0          0
4:2       A    46251       0        0        0        0          0          0
================================================================================

We never saw any improvement and now most stacks are broken up and converted into single switches with LAG to the dists that run MLAG towards the access switches. Problem solved...