What type of physical layer events could potentially lead to an interface going to an errdisabled state…within the context of ‘show interface phy details’ counters? We are seeing three of these messages within the switch logs : 3981: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4 followed by this: Ebra: 3984: %ETH-4-ERRDISABLE: link-interrupt-storm error detected on Ethernet4
Thanks for posting the questions.
For checking the reason of errdisable, you can use the following CLI:
Link flapping is one possible reason interfaces are disabled. You can use “show mac detail” CLI to get a summary of the states of the interface, phy, “local fault” and “remote fault”. “show phy detail” gives more details but relatively more difficult to interpret.
show mac detail
show phy detail
If you have more questions, you can provide the output of the above CLI, we can have a look.
There can be couple of reasons for interface to go into errdisable state
1.For example if the number of flaps are more because of low light level/inconsistency in incoming Rx optical signal arista default behavior is to put the interface state in errdisable state as this alleviates the port going into Bad state because of excessive heating.
2.The same can be verified by
3. Coming to Phy details, when you do
4.Now to recover from errdisable state, it depends on what is the reason you obtained 2a.
5.Before concluding if its a optic,cable or port issue there are a series of L1 T-shooting steps I can share it with you
I would be more than happy to discuss this over a call if you would like to.
Otherwise, Feel free to send a email to firstname.lastname@example.org and my colleagues are more than happy to dive deep into the issue if required
Hope this helps!
Missed one more point in your case the reason is
Ethernet4 followed by this: Ebra: 3984: %ETH-4-ERRDISABLE: link-interrupt-storm error detected on Ethernet4
Can you share eth4 configurations? and show version from the switch
Post your Answer
You must be logged in to post an answer.