Stacking Ports Flapping X460-G2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-20-2019 03:22 PM
We have 9 X460-G2 stacks running version 22.5.1.7 and we have noticed that the stacking ports are flapping on a regular basis.
The link goes down on Stacking ports 1:2 and 2:1 then comes back up.
Has anyone else experienced this problem? What was the resolution?
Thank you
The link goes down on Stacking ports 1:2 and 2:1 then comes back up.
Has anyone else experienced this problem? What was the resolution?
Thank you
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-25-2019 09:29 AM
Thanks @ChrisH
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-25-2019 09:00 AM
Hello,
The 10Gb/stacking ports flapping in 22.5 on the x460G2 is a known issue that will be fixed under xos0073360.
In the meantime i suggest, like already mentioned before, to configure 150ms debounce timers on the stacking-ports as explained in the following article: https://gtacknowledge.extremenetworks.com/articles/Solution/Link-flaps-continuously-on-X460-G2
The implications of setting this 150ms debounce timer are that in case of a valid link down event of these ports, the switch will wait 150ms before it declares the link to really be down, so this could cause additional latency/delay in case of a real failover.
best regards,
Chris
The 10Gb/stacking ports flapping in 22.5 on the x460G2 is a known issue that will be fixed under xos0073360.
In the meantime i suggest, like already mentioned before, to configure 150ms debounce timers on the stacking-ports as explained in the following article: https://gtacknowledge.extremenetworks.com/articles/Solution/Link-flaps-continuously-on-X460-G2
The implications of setting this 150ms debounce timer are that in case of a valid link down event of these ports, the switch will wait 150ms before it declares the link to really be down, so this could cause additional latency/delay in case of a real failover.
best regards,
Chris
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-22-2019 12:55 PM
We had the same problem, changing debounce time on stacking ports fixed it. I wonder what are the implications of this and if there is none or if is necesary why its not the default value....
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-20-2019 04:34 PM
We had some issues with slots randomly rebooting and TAC recommended that we
configure stack-ports debounce time 150.
We just did that recently and are currently monitoring. Difference with us we have 460-48p Generation 1s, running a 16 code (with v.80 stacking - extreme branded)
then you can show stack-ports debounce to confirm the time (ms) took place.
configure stack-ports debounce time 150.
We just did that recently and are currently monitoring. Difference with us we have 460-48p Generation 1s, running a 16 code (with v.80 stacking - extreme branded)
then you can show stack-ports debounce to confirm the time (ms) took place.