X460 and X450 Flapping Ports

  • 0
  • 2
  • Problem
  • Updated 3 years ago
  • Solved
I have installed 15 new X460 switch stacks, and upgraded the Firmware on some old X450s.
I notice that many of the Ethernet Ports are "Flapping". There is no stable connection, and devices constantly disconnect/reconnect at 10M/100M/1000M.  I note that the problem is worse with some Canon Printers, but other devices have problems. I can make the ports more stable by forcing the speed to 10M.

Here are some typical syslogs:

May  6 10:21:31 degp-s02 <vlan.msgs.portLinkStateDown> Port 5:2 link down
May  6 10:21:34 degp-s02 <vlan.msgs.portLinkStateUp> Port 5:2 link UP at speed 1 Gbps and full-duplex
May  6 10:22:25 degp-s02 <vlan.msgs.portLinkStateDown> Port 5:2 link down
May  6 10:22:27 degp-s02 <vlan.msgs.portLinkStateUp> Port 5:2 link UP at speed 10 Mbps and half-duplex
May  6 10:22:43 degp-s02 <vlan.msgs.portLinkStateDown> Port 4:24 link down
May  6 10:22:45 degp-s02 <vlan.msgs.portLinkStateUp> Port 4:24 link UP at speed 10 Mbps and half-duplex
May  6 10:22:47 degp-s02 <vlan.msgs.portLinkStateDown> Port 1:10 link down
May  6 10:22:50 degp-s02 <vlan.msgs.portLinkStateUp> Port 1:10 link UP at speed 1 Gbps and full-duplex
May  6 10:22:50 degp-s02 <vlan.msgs.portLinkStateDown> Port 5:2 link down
May  6 10:22:53 degp-s02 <vlan.msgs.portLinkStateUp> Port 5:2 link UP at speed 1 Gbps and full-duplex
May  6 10:23:14 degp-s02 <vlan.msgs.portLinkStateDown> Port 1:10 link down
May  6 10:23:16 degp-s02 <vlan.msgs.portLinkStateUp> Port 1:10 link UP at speed 1 Gbps and full-duplex
May  6 10:25:24 degp-s02 <vlan.msgs.portLinkStateDown> Port 5:2 link down
May  6 10:25:27 degp-s02 <vlan.msgs.portLinkStateUp> Port 5:2 link UP at speed 10 Mbps and half-duplex
May  6 10:25:39 degp-s02 <vlan.msgs.portLinkStateDown> Port 3:42 link down
May  6 10:25:41 degp-s02 <vlan.msgs.portLinkStateUp> Port 3:42 link UP at speed 10 Mbps and half-duplex
May  6 10:25:43 degp-s02 <vlan.msgs.portLinkStateDown> Port 3:42 link down
May  6 10:25:45 degp-s02 <vlan.msgs.portLinkStateUp> Port 3:42 link UP at speed 10 Mbps and half-duplex
May  6 10:26:29 degp-s02 <vlan.msgs.portLinkStateDown> Port 4:24 link down
May  6 10:26:32 degp-s02 <vlan.msgs.portLinkStateUp> Port 4:24 link UP at speed 10 Mbps and half-duplex
May  6 10:27:44 degp-s02 <vlan.msgs.portLinkStateDown> Port 3:38 link down
May  6 10:27:47 degp-s02 <vlan.msgs.portLinkStateUp> Port 3:38 link UP at speed 10 Mbps and half-duplex
May  6 10:27:51 degp-s02 <vlan.msgs.portLinkStateDown> Port 5:2 link down
May  6 10:27:53 degp-s02 <vlan.msgs.portLinkStateUp> Port 5:2 link UP at speed 1 Gbps and full-duplex
May  6 10:28:06 degp-s09 <vlan.msgs.portLinkStateDown> Port 1:16 link down
May  6 10:28:08 degp-s09 <vlan.msgs.portLinkStateUp> Port 1:16 link UP at speed 10 Mbps and half-duplex
May  6 10:30:05 degp-s03 <vlan.msgs.portLinkStateDown> Port 1:1 link down
May  6 10:30:06 degp-s09 <vlan.msgs.portLinkStateDown> Port 1:16 link down
May  6 10:30:08 degp-s03 <vlan.msgs.portLinkStateUp> Port 1:1 link UP at speed 10 Mbps and full-duplex
May  6 10:30:09 degp-s09 <vlan.msgs.portLinkStateUp> Port 1:16 link UP at speed 1 Gbps and full-duplex
May  6 10:30:20 degp-s03 <vlan.msgs.portLinkStateDown> Port 1:1 link down
May  6 10:30:23 degp-s03 <vlan.msgs.portLinkStateUp> Port 1:1 link UP at speed 10 Mbps and full-duplex
May  6 10:30:57 degp-s03 <vlan.msgs.portLinkStateDown> Port 1:19 link down
May  6 10:30:59 degp-s03 <vlan.msgs.portLinkStateUp> Port 1:19 link UP at speed 10 Mbps and full-duplex
May  6 10:31:12 degp-s03 <vlan.msgs.portLinkStateDown> Port 1:19 link down
May  6 10:31:14 degp-s03 <vlan.msgs.portLinkStateUp> Port 1:19 link UP at speed 10 Mbps and full-duplex


How can I fix this?  I have new(ish) f/w (X460 = v1541b3-patch1-1  and X450 = v1265b2-patch1-3)

Most of the cabling is brand new, could this be a problem?

Thanks,
Martin



Photo of Martin Harrow

Martin Harrow

  • 140 Points 100 badge 2x thumb

Posted 5 years ago

  • 0
  • 2
Photo of Sumit Tokle

Sumit Tokle, Alum

  • 5,738 Points 5k badge 2x thumb
What type of cable are you using to connect two switches?
Is there any L2 switch present in between the X460 and X450.
Does same type of log messages present on both the side of switch  port during the same time?
How frequently the ports are getting flapped?
Is there any loop in the network? 
Do you see any process going high in "top" command output?
Photo of Martin Harrow

Martin Harrow

  • 140 Points 100 badge 2x thumb
hi

Tha cables are described: MegaLine-Patch 6AEA-RJ45SL
I have a L3 core switch (x460-24x) connected to 10 edge switches (x460-48p) and some older X450-48P), in a star network.

The problems are between the edge switches and  the devices. Many Canon Printers iR-ADV C5235  (MAC 88:87:17:7e:82:2d) have the problem - see logs below.
Some PCs also have a problem.
The users are starting to complain about the new network.
The message occurs only on edge ports, not between switches.
There is no loop in the network ( I checked ELRP )
The messages appear every few minutes (see below)


* Slot-1 DEGP-S09.11 # show cpu-monitoring
(sorted output)
Card   Process      5    10   30   1    5    30   1    Max           Total
Slot-1    fdb    0.7    0.9    1.0    1.0    0.9    0.8    0.8    3.4    16,772.9    16,121.2
Slot-1    exsshd    2.4    2.0    1.6    1.5    1.6    1.1    0.9    6.8    3,707.4    20,690.4
Slot-1    snmpSubagent    0.0    0.0    0.0    0.0    0.0    0.1    0.0    21.9    2,935.9    1,951.0
Slot-1    nodemgr    0.2    0.1    0.1    0.1    0.1    0.1    0.1    0.5    2,509.3    2,651.9
Slot-1    snmpMaster    0.0    0.0    0.0    0.0    0.0    0.1    0.0    22.1    2,451.3    1,914.6
Slot-1    hal    0.8    0.5    0.5    0.4    0.4    0.4    0.4    66.6    2,365.6    14,125.2
Slot-1    epm    0.1    0.0    0.0    0.1    0.1    0.1    0.1    7.1    1,594.7    684.4
Slot-1    acl    0.2    0.2    0.1    0.1    0.1    0.1    0.1    0.8    1,493.1    4,160.6
Slot-1    cfgmgr    0.0    0.0    0.0    0.0    0.0    0.1    0.0    9.6    992.0    546.5
Slot-1    etmon    0.0    0.0    0.0    0.1    0.1    0.1    0.1    7.8    950.2    964.9
Slot-1    bfd    0.1    0.0    0.0    0.1    0.1    0.1    0.1    0.6    677.3    813.0
Slot-1    rip    0.1    0.0    0.0    0.1    0.1    0.1    0.1    0.8    599.5    1,227.9
Slot-1    ripng    0.0    0.0    0.0    0.1    0.1    0.1    0.1    0.6    578.6    679.5
Slot-1    thttpd    0.0    0.0    0.0    0.0    0.0    0.1    0.1    14.2    509.7    71.1
Slot-1    esrp    0.0    0.0    0.0    0.2    0.1    0.1    0.1    6.5    441.9    542.1
Slot-1    msdp    0.0    0.0    0.0    0.1    0.1    0.1    0.1    0.6    382.7    464.2
Slot-1    eaps    0.0    0.0    0.0    0.0    0.0    0.0    0.0    5.8    241.0    76.3
Slot-1    vlan    0.0    0.0    0.0    0.0    0.0    0.0    0.0    7.2    214.0    58.4
Slot-1    System    8.3    7.4    8.4    7.6    8.0    7.8    7.8    15.6    196.6    278,076.4

* Slot-1 DEGP-S09.13 # top
Mem: 402768K used, 107736K free, 0K shrd, 144268K buff, 91192K cached
CPU:  1.6% usr 12.7% sys  0.0% nic 81.3% idle  0.0% io  3.7% irq  0.4% sirq
Load average: 7.26 7.33 7.34 4/185 13639
  PID  PPID USER     STAT   RSS %MEM CPU %CPU COMMAND
 1217     2 root     RW<      0  0.0   0  4.2 [bcmLINK.0]
 1219     2 root     SW<      0  0.0   1  3.7 [bcmLINK.1]
13626  1695 root     S     1324  0.2   1  2.1 ./exsshd
 1439     1 root     S     3212  0.6   1  0.9 ./fdb
13639 13638 root     R      820  0.1   0  0.9 top -d 3


I also see on some switches (below is the core switch):
05/06/2014 14:40:44.09 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 13:40:33.31 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 12:40:32.72 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 11:40:29.57 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 10:40:20.42 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 09:40:00.96 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 08:39:54.83 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 07:39:47.14 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 06:39:43.40 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 05:39:41.97 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 04:39:40.86 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 03:39:39.95 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 02:39:39.16 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 01:39:37.87 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/06/2014 00:39:36.93 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 23:39:35.91 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 22:39:35.10 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 21:39:33.98 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 20:39:32.66 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 19:39:31.67 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 18:39:18.65 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 17:39:09.66 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 16:39:08.45 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 15:38:55.07 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 14:38:53.81 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 13:38:53.23 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 12:38:49.74 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 11:38:41.42 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 10:38:33.90 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 09:38:32.96 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 08:38:30.29 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.
05/05/2014 07:38:21.25 <Erro:HAL.IPv4Mc.L3TblFull> Slot-2: IPv4 multicast entry not added. Hardware L3 Table full.



05/06/2014 15:08:40.90 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 1 Gbps and full-duplex
05/06/2014 15:08:38.38 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 15:08:34.09 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 10 Mbps and half-duplex
05/06/2014 15:08:31.36 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 15:01:02.33 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:15 link UP at speed 100 Mbps and full-duplex
05/06/2014 15:00:59.91 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:15 link down
05/06/2014 14:58:23.57 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 1 Gbps and full-duplex
05/06/2014 14:58:21.19 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 14:56:56.98 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:8 link UP at speed 100 Mbps and full-duplex
05/06/2014 14:56:55.25 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:8 link down
05/06/2014 14:53:49.54 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 10 Mbps and half-duplex
05/06/2014 14:53:47.21 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 14:51:26.24 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 1 Gbps and full-duplex
05/06/2014 14:51:23.67 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 14:48:55.47 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 10 Mbps and half-duplex
05/06/2014 14:48:52.90 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 14:38:36.24 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 1 Gbps and full-duplex
05/06/2014 14:38:33.79 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:16 link down
05/06/2014 14:38:31.71 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:16 link UP at speed 10 Mbps and half-duplex



I need to find a solution for this, it cannot be normal.

I think the flapping is blocking the CPU, because sometimes the Ridgeline cannot get an SNMP response - I suspect CPU overload.


Thx, Martin





Photo of MUNIR ENG

MUNIR ENG

  • 1,256 Points 1k badge 2x thumb
what is mean
switch#top .?
for what it using ?
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 48,648 Points 20k badge 2x thumb
please refer to the "ExtremeXOS Command Reference Guide" to get information about the different commands...

# top

Description:
Displays real-time CPU utilization information by process.
Photo of Sumit Tokle

Sumit Tokle, Alum

  • 5,738 Points 5k badge 2x thumb
How long you have seen this issue? Have you done any changes which could trigger this issue?

Does auto negotiation is on,on all the port which are connected to the end devices? if yes, then you might need to open case with TAC for further investigation.
Photo of Martin Harrow

Martin Harrow

  • 140 Points 100 badge 2x thumb
I was using AUTO on all ports. for the flapping ports, I have set the connection to fixed 10M/half.
I think I must open a case.
What are the best commands to check the switch?
You suggested TOP? any others?

Photo of Sumit Tokle

Sumit Tokle, Alum

  • 5,738 Points 5k badge 2x thumb
Yes, 

You can share the below information to TAC when you open case. It would help to get resolution as soon as possible.

Network topology diagram
show forwarding configuration
debug hal show forwarding distributions
debug hal show ipv4Mc
show iproute reserved-entries statistics
show tech
show port <port #> information detail
show port <port #> configuration   
debug hal show optic-info
 debug hal show cpu-queue


Thanks.

Photo of MUNIR ENG

MUNIR ENG

  • 1,256 Points 1k badge 2x thumb
thank for this information , but when i doing this commands i got on many values ! how can i know which the better value?
Photo of Edson Yuji

Edson Yuji

  • 212 Points 100 badge 2x thumb
I had this same problem in Extreme switches. This happened when I fixed the port speed to 100Mbps Full duplex for example, workstation and IP station and printers were auto-negotiation happened flapping port.
Photo of Martin Harrow

Martin Harrow

  • 140 Points 100 badge 2x thumb
Hi Edson, Thanks for the input. Most of my problems occur with Canon printers, so as a work around I have been setting the speed to 10M fixed. I'm just annoyed that we have "upgraded" from 10 year old Cisco switches (which had no problems) to brand new Extreme switches that have these problems.
Photo of rbrt_weiler

rbrt_weiler

  • 834 Points 500 badge 2x thumb
Hi Martin,

I suspect that your old switches were Fast Ethernet switches? In this case you should check your passive infrastructure. I've seen issues with Gigabit in one of our offices as well, turned out that the - very old - cabling wasn't able to handle Gigabit Ethernet. If cabling turns out to be the issue you've basically got two options:

* Replace the cabling.
* configure ports <range> auto on speed 100 duplex full

The first option can be quite budget intense, but is the better solution.

-Robert
Photo of Martin Harrow

Martin Harrow

  • 140 Points 100 badge 2x thumb
Robert, thanks for the feedback. I have tried this, it helps a bit.  ;-)
Photo of Boon Nyian Jap

Boon Nyian Jap

  • 110 Points 100 badge 2x thumb
hi martin, did you managed to resolve the issue? I having the same issue with x460 now
Photo of PARTHIBAN CHINNAYA

PARTHIBAN CHINNAYA, Alum

  • 4,382 Points 4k badge 2x thumb
Hi Boon,
Are you seeing this problem in X460 XGM module 10g ports?

could you copy paste the link flap logs from x460 and its peer device?
Photo of Boon Nyian Jap

Boon Nyian Jap

  • 110 Points 100 badge 2x thumb
Hi there,

after we upgraded the switch firmware and applied debounce time 150 to stack ports, the stack ports flapping issue was resolved. However, I did observed some flapping for data ports. No sure if anyone noticed this issue.
Photo of PARTHIBAN CHINNAYA

PARTHIBAN CHINNAYA, Alum

  • 4,382 Points 4k badge 2x thumb
It applies to data ports as well
Please apply denounce timer settings
Summit , bd8k and bdx8 10 g ports are impacted
Photo of Boon Nyian Jap

Boon Nyian Jap

  • 110 Points 100 badge 2x thumb
should we applied debounce 150 to all data ports too? Extreme support advise that it should be applied to port that are flapping only. is that right?
Photo of PARTHIBAN CHINNAYA

PARTHIBAN CHINNAYA, Alum

  • 4,382 Points 4k badge 2x thumb
If the switch is connected to another 10 g port
(Switch) then yes. '
All 10g switch to switch connectivity ports must have debounce timer to 150 .

Note: 3rd party vendors have default debounce
Timer as 150
(Edited)
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,676 Points 10k badge 2x thumb
The latest release of EXOS (15.5.3) should have a fix that remove the debounce timer. Please check the RN.
Photo of Boon Nyian Jap

Boon Nyian Jap

  • 110 Points 100 badge 2x thumb

it is not 10G port, but the 1G data ports that are flapping. I have upgraded to 15.5.3 patch 1-2.
#configured stack-port debounce time 150

#debug hal configure stack-ports pre-emphasis 7 driver-current 9

anyone faced similar issue?

I have a 2 slot stack with 460 runing xos 15.4.2 , I tried to configure the command "configure stack-ports 2:2 debounce time 150"  but it is not  accepted by the sw

How can i configure the debounce timer?
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,088 Points 10k badge 2x thumb
You need 15.5.3 I think for this command. Upgrade to the latest patch of this release.
Photo of PARTHIBAN CHINNAYA

PARTHIBAN CHINNAYA, Alum

  • 4,382 Points 4k badge 2x thumb
we just need to upgrade x460 to the right EXOS version.
I believe in x460 by default the debounce timer is 150.
For other chassis based and summit switches it has to be manually set with exos versions.
Photo of PARTHIBAN CHINNAYA

PARTHIBAN CHINNAYA, Alum

  • 4,382 Points 4k badge 2x thumb
It looks like in exos 15.5.x  we dont need these settings.[x460]
Photo of Boon Nyian Jap

Boon Nyian Jap

  • 110 Points 100 badge 2x thumb
no sure, it is requested by extreme support to put in these commands after upgrade to 15.5.3 patch 1-2
Photo of Grosjean, Stephane

Grosjean, Stephane, Employee

  • 13,676 Points 10k badge 2x thumb
Just for clarification.

There was an issue with 10G uplinks on x460. This is documented in the FN404. This is resolved with some EXOS version, as documented.

Stacking flapping is addressed via a specific command, that is accessible and persistent since 15.5.3. Defining the right value, if you have that issue, should be done with the help of TAC.

Other summits, BD, ports, are not impacted.

For 1G flapping, that could be due to cabling (is the cable old? what category? PoE on it as well?) or due to the end-device.

Using debounce timer on a data port will certainly prevent flapping. Question is, is that for a good thing? If the flapping is due to some issues with the links, hiding it will not resolve loss of packet, poor performances, etc. I am not aware of problem of that sort, so I'd encourage you to validate the infra, check if reducing speed helps...