Much of the time I can see errors on an interface incrementing and proactively fix the issue before it becomes a bigger problem. Personally, I use Cacti to monitor my device interfaces for utilization and errors and have Cacti e-mail me when a threshold is reached. And even better tool is NeDi (network discovery) Or you could just write some scripts or develop program to do the same thing, if you have the time. A comparable configuration management tool for 'Nix is RANCID. Cat Tools can do much more, check it out. " show interfaces", is easy to configure and schedule. Cat Tools will also run commands, so gathering interface statistics, e.g. It can be configured to send you an e-mail with an attachment of any changes that have occurred with configurations. I have used it to automate firewall, router, and switch configuration backups for a variety of vendor devices.
Cisco nexus show interface errors windows#
Another good tool is the Windows program Kiwi Cat Tools. Splunk or ManageEngine Eventlog Analyzer, Linux syslog, etc. It's situations like this where a syslog server comes in handy, e.g. LOL, we all have the "Facebook" users, often times at the C-level. %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 2065 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 2765 N/A %ISDN-6-DISCONNECT: Interface Serial0/0/0:2 disconnected from 515, call lasted 492 seconds %ISDN-6-DISCONNECT: Interface Serial0/0/0:11 disconnected from 17038490960, call lasted 50 seconds %ISDN-6-DISCONNECT: Interface Serial0/0/0:10 disconnected from 7035277500, call lasted 1010 seconds %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 1960 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 170960 N/A %ISDN-6-DISCONNECT: Interface Serial0/0/0:11 disconnected from 17038522843, call lasted 3 seconds %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 122843 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:11 is now connected to 1843 N/A %ISDN-6-DISCONNECT: Interface Serial0/0/0:0 disconnected from 4805, call lasted 255 seconds %ISDN-6-DISCONNECT: Interface Serial0/0/0:1 disconnected from 4005, call lasted 234 seconds %ISDN-6-CONNECT: Interface Serial0/0/0:2 is now connected to 515 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:1 is now connected to 408805 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 408805 N/A %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 405 N/A
![cisco nexus show interface errors cisco nexus show interface errors](http://blog.uninets.com/wp-content/uploads/2020/07/nexus-9k-port-channel-configuration.png)
DISCONNECT: Interface Serial0/0/0:0 disconnected from 20032, call lasted 74 seconds Logging to 170.XX.XX.252 (udp port 514, audit disabled,Īuthentication disabled, encryption disabled, link up),
![cisco nexus show interface errors cisco nexus show interface errors](https://slideplayer.com/slide/6224191/20/images/51/Store+and+forward+mode+Incoming+jumbo+frames+are+discarded+rather+than+being+truncated+and+stomped+with+CRC..jpg)
Trap logging: level notifications, 61 message lines logged Monitor logging: level debugging, 0 messages logged, xml disabled,īuffer logging: level debugging, 3491 messages logged, xml disabled,Ĭount and timestamp logging messages: disabled Cisco Nexus Show Commands for High CPU Usage. Syslog logging: enabled (0 messages dropped, 66 messages rate-limited,Ġ flushes, 0 overruns, xml disabled, filtering disabled)Ĭonsole logging: level debugging, 3491 messages logged, xml disabled,