Unsolved
This post is more than 5 years old
5 Posts
0
4514
January 15th, 2017 19:00
8204F port errors
We are getting FCS and Internal MAC Rx errors on a single port. I have replaced the SFP and fibre cable as well as moving the cable to an alternate port, none of which has stopped the errors which occur randomly every hour or so (currently up to approximately 1200 errors).
I am not seeing any errors on the other end (the connection is a trunk between an 8024F switch and 5548 switch). The issue started around a month ago and has increased in severity to the point where the port is going down for short periods.
Could issues from the 5548 switch cause errors to only show up on the 8024F switch?
events found
No Events found!
Will8384
5 Posts
0
January 16th, 2017 19:00
Logging only shows the interface going down and up, and consequently STP status changes:
<189> JAN 17 11:31:17 10.0.200.64-1 TRAPMGR[245162672]: traputil.c(637) 661417 %% Te1/0/2 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> JAN 17 11:31:17 10.0.200.64-1 TRAPMGR[245162672]: traputil.c(637) 661416 %% Link Up: Te1/0/2
<189> JAN 17 11:31:17 10.0.200.64-1 TRAPMGR[245162672]: traputil.c(637) 661415 %% Te1/0/2 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> JAN 17 11:31:17 10.0.200.64-1 TRAPMGR[245162672]: traputil.c(637) 661414 %% Link on Te1/0/2 is failed
<189> JAN 17 11:31:17 10.0.200.64-1 TRAPMGR[245162672]: traputil.c(637) 661413 %% Link Down: Te1/0/2
5548 FW version: 4.1.0.10
8024F FW version: 5.0.1.3
I have only changed ports on the 8024F as any changes to the 5548 could cause downtime on a production environment.
There have not been any changes made to the effected ports configuration for over a year.
Will8384
5 Posts
0
January 17th, 2017 14:00
There have been STP changes on the 5548 te1/0/2 port that connects to the 8024F, though there have been very few errors and no operation status changes on that port compared to the 8024F port. I have been concentrating on the 8024F as it's where I have seen all the errors and the port actually going down.
The 8024F is being used as a core switch that has all the trunk connections to the switch stacks in other cabinets. None of the other ports/connections are having any issues.
The current network layout and STP configuration has been in placed for years now with no issue. Could the errors on the 8024F port be caused by issues with the 5548? If so I can organise some maintenance periods to replace the SFP on the switch.
switch064#show spanning-tree tengigabitethernet 1/0/2
Port Te1/0/2 Enabled
State: Discarding Role: Designated
Port id: 128.2 Port Cost: 2000
Port Fast: No Root Protection: No
Designated bridge Priority: 16384 Address: D067.E599.4DC4
Designated port id: 128.2 Designated path cost: 2000
CST Regional Root: 40:00:D0:67:E5:99:4D:C4
Root Guard..................................... FALSE
Loop Guard..................................... FALSE
TCN Guard...................................... FALSE
Auto Portfast.................................. TRUE
Port Up Time Since Counters Last Cleared....... 0 day 0 hr 0 min 0 sec
BPDU: sent 18350187, received 8328871
switch064#show spanning-tree summary
Spanning Tree Adminmode........... Enabled
Spanning Tree Version............. IEEE 802.1w
BPDU Guard Mode................... Disabled
BPDU Flood Mode................... Disabled
BPDU Filter Mode.................. Disabled
Configuration Name................ D0-67-E5-99-4D-C4
Configuration Revision Level...... 0
Configuration Digest Key.......... 0xac36177f50283cd4b83821d8ab26de62
Configuration Format Selector..... 0