04-28-2011 09:06 AM - edited 03-06-2019 04:50 PM
We have OTV running between 2 data centers on the same campus. In the Layer 3 path between the data centers we have multiple ways to get from one side to the other (4 equal cost paths). One fiber link started to take errors and we didn't see it for a bit. I assume it caused every fourth packet to fail and be retransmitted... jobs that normally take 15 minutes took 4+ hours and were canceled...
Is there a way to configure a port to automatically shut down or err-disable because it is taking errors? UDLD Aggressive is enabled, it did not step in and shut the port.
05-02-2011 12:21 PM
Hi Jeff,
I'm not aware of a single command which would enable this, however you can write an EEM applet to monitor the interface counters and do an action based on it, such as shutdown the interface, send a log message or email.
Have a look at the Embedded Event Manager (EEM) on the Cisco Catalyst 6500 Series documentation which is written for 6k but still valid for Nexus.
One slightly sad thing is precisely the interface counters are not available on the Nexus, although you could use the SNMP Event in EEM applet to monitor the required counter and do necessary actions.
Have a look on the following documentation and also refer to "Configuration Examples for SNMP Notification" section for more details.
Best regards,
Andras
06-25-2012 08:15 AM
Hi Jeff -
Did you look at using EEM to shutdown the port that was accumulating CRC errors?
Or did you find another way?
Be interested to know as I have a similar issue.
Regards,
James
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide