This is an old revision of the document!
EAPS Troubleshooting
Switch Addresses
Address | Name |
02:04:96:83:48:AB | Server_Room |
00:04:96:83:9F:20 | ITV_CLoset |
00:04:96:83:9F:57 | Office |
00:04:96:83:9F:62 | Elementary_Ed |
00:04:96:83:9F:7E | Business_AD_RM |
00:04:96:83:9F:82 | Ag_Room |
00:04:96:83:9F:7B | Old_KSU_Closet |
00:04:96:83:9F:64 | 5th_Floor |
Ring Topology
Server_Room |
1:31 | Link_To_5th_Floor |
2:31 | Link_To_ITV_Closet |
ITV_CLoset |
1:53 | Link_To_Server_Room |
1:54 | Link_To_Office |
Office |
1:53 | Link_to_ITV_Room |
1:54 | Link_to_Elementary_Ed_closet |
Elementary_Ed |
1:53 | Link_To_Office |
1:54 | Link_To_Business_AD_Room |
Business_AD_RM |
1:53 | Link_To_Elementary_Ed_Closet |
1:54 | Link_To_Ag_Room |
Ag_Room |
1:53 | Link_To_Business_AD_RM |
1:54 | Link_To_Old_KSU_RM |
Old_KSU_Closet |
1:53 | Link_To_Ag_RM |
1:54 | Link_To_5TH_Floor |
5th_Floor |
1:53 | Link_To_Old_KSU |
1:54 | Link_TO_Server_RM |
Useful Commands
show ports 1:53-1:54 configuration no-refresh
configure ports 1:53 auto off speed 1000 duplex full
show ports 1:53-1:54 congestion
show log | include "Received Link-Down-Pdu"
show log | include <Info:vlan.msgs.portLinkStateDown>
show ports 1:53,1:54 rxerrors
show ports 1:31,2:31 rxerrors
EAPS Down Example
Slot-1 Office.1 # show eaps "seb-eaps"
Name: seb-eaps Priority: Normal
State: Links-Down Running: Yes
Enabled: Yes Mode: Transit
Primary port: 1:53 Port status: Up Tag status: Tagged
Secondary port: 1:54 Port status: Down Tag status: Tagged
Slot-1 Elementary_Ed.1 # show eaps "seb-eaps"
Name: seb-eaps Priority: Normal
State: Links-Down Running: Yes
Enabled: Yes Mode: Transit
Primary port: 1:53 Port status: Down Tag status: Tagged
Secondary port: 1:54 Port status: Up Tag status: Tagged
Packet Loss
--- 10.1.1.77 ping statistics ---
3365 packets transmitted, 3328 received, +11 errors, 1% packet loss, time 3443267ms
rtt min/avg/max/mdev = 0.185/0.722/1024.694/17.753 ms, pipe 4
--- 10.1.3.14 ping statistics ---
3368 packets transmitted, 3333 received, +11 errors, 1% packet loss, time 3445370ms
rtt min/avg/max/mdev = 0.207/1.040/1016.357/17.592 ms, pipe 4
CRC Errors
Any fiber run that is dropping seems to have some sort of CRC errors
run from Ag_Room to OLD_KSU giving CRC errors on OLD_KSU port 1:53 even after restarting both switches reconfigured both ports to 1G and CRC errors stopped
After reconfiguring both ports back to 10G the CRC errors seemed to have stopped
Run from server room to 5th floor stayed down after restarting both switches. Link did come up after reconfiguring both ports to 1G, both both 1:31 on server room switch and 1:54 on 5th floor switch had CRC errors
As of 8pm on Friday all other switches showing 0 CRC errors
Fibers in Ag_Room are transposed from the port descriptions.
Over the night of the 12th of Jan EAPS master reporting <Info:EAPS.RxPduLinkDown> on Office and OLD_KSU switches
reduced speed of Ag_room and OLD_KSU switch to 1G seeing if CRC errors are causing <Info:EAPS.RxPduLinkDown> on EAPS master
Office switch is having port 1:54 lose connection every hour or so, even after multiple restarts
Example Rx error report
show ports 1:53,1:54 rxerrors no-refresh
Port Rx Error Monitor
Port Link Rx Rx Rx Rx Rx Rx Rx
State Crc Over Under Frag Jabber Align Lost
================================================================================
1:53 A 0 0 0 0 0 0 0
1:54 A 0 0 0 0 0 0 0
================================================================================
Link State: A-Active, R-Ready, NP-Port Not Present L-Loopback