![]() ![]() If this is not something you would like to do I would try a different IOS version. If the error is only received when a host is not plugged in and the no keepalive prevents the alarms from being received, then I would disable keepalives when the interface is not in use, and enable them when it is in use. Hardware is Fast Ethernet, address is 981 (bia 981) See the output below:įastEthernet0/1 is up, line protocol is up (connected) You can however confirm that keepalives are configured for an interface with the show interface "interface type/mod/#" enable mode command. To me it sounds like an IOS bug or a port failure within the Ethernet Module. Since the port is not being used does the no keepalive interface config mode command stop the loopback alarms? If you plug a host PC in the port are these alarms still being received. I know with Serial interfaces you can issue a debug interface serial (#) and it will show keep alives sent and received. With Ethernet I don't believe there is a command to see keepalive statistics in real time or a record of keepalives over a period of time. If what you say is true and there is nothing connected to the interface why isn't it shut down? If nothing is connected and this is still happening you can try opening a TAC case. A temporary solution would be able to disable keepalives on the interface or prevent this condition from err-disabling an interface. So if it is a fiber interface it may have to do with Cisco bug ID CSCea46385. The suggested workaround is to disable keepalives and upgrade to Cisco IOS Software Release 12.2SE or later. For more information, refer to Cisco bug ID CSCea46385 ( registered customers only). In Cisco IOS Software Release 12.2SE-based software and later, keepalives are not sent by default on fiber and uplink interfaces. Keepalives are sent on all interfaces by default in Cisco IOS Software Release 12.1EA-based software. %PM-4-ERR_DISABLE: loopback error detected on Gi4/1, putting Gi4/1 in This message occurs because the keepalive packet is looped back to the port that sent the keepalive: ![]() The source interface receives the keepalive packet that it sent out, and the switch disables the interface (errdisable). A device can loop the packets back to the source interface, which usually occurs because there is a logical loop in the network that the spanning tree has not blocked. ![]() The switch sends keepalives out all the interfaces by default. ![]() Anyway I looked this up on and found the following:Ī loopback error occurs when the keepalive packet is looped back to the port that sent the keepalive. I couldn't check your link, because it keeps forwarding me to spam websites. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |