Dave.... I know this. ;) If you check the log.. it shows this for only specific ports.. and it happens constantly (many times within a few seconds).. and this is spanning across all my access-layer switches. One thing I'm figuring could be NIC incompatibility.. but I'm not sure.. any suggestions?
If this is caused by NIC incompatibility, you should see input errors and CRC errors on the switch ports. Just clear the counters before checking if there are errors or CRCs and verify if they are increasing.
"Windows 2000 and Windows ME employ a power management capability that can disable the NIC. When the NIC is disabled for power management, the NIC will drop link to the switch. If there is a concern of link going up/down on NICs using operating systems Windows 2000 or Windows ME, disable the power management feature as a first means of troubleshooting link up/down situations."
If you don't want to get this messages in your logfiles because they're only caused by "client" pc's , than put a
"no logging event link-status"
"no snmp trap link-status"
on each interface, which belongs to a client pc. Usually, those interfaces need not to be monitored, but it depends on you. If you say, hey, maybe there's a problem with the client (if it occurs very frequent, but this doesn't seem to be in your case) you'll better leave it on OR you would say it's just a normal power off/power on of the user pc....than you better turn off these messages with the above commands.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...