Re: Cisco router logs

Pratikslv38 · ‎12-10-2021

Can anybody help me to understand why BGP flapped if there is no issue in ISP media.

==================================

BFL_BURHANPUR_TCL#sh ver
Cisco IOS Software, C800 Software (C800-UNIVERSALK9-M), Version 15.5(3)M4a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Thu 06-Oct-16 14:23 by prod_rel_team

ROM: System Bootstrap, Version 15.4(1r)T1, RELEASE SOFTWARE (fc1)

BFL_BURHANPUR_TCL uptime is 4 days, 3 hours, 56 minutes
System returned to ROM by power-on
System restarted at 13:32:37 IST Mon Dec 6 2021
System image file is "flash:c800-universalk9-mz.SPA.155-3.M4a.bin"
Last reload type: Normal Reload
Last reload reason: power-on

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco C881-K9 (revision 1.0) with 488524K/35763K bytes of memory.
Processor board ID FGL213194R8
5 FastEthernet interfaces
1 Virtual Private Network (VPN) Module
DRAM configuration is 32 bits wide
255K bytes of non-volatile configuration memory.
250880K bytes of ATA System CompactFlash (Read/Write)

License Info:

License UDI:

-------------------------------------------------
Device# PID SN
-------------------------------------------------
*1 C881-K9 FGL213194R8

License Information for 'c800'
License Level: advipservices Type: Permanent
Next reboot license Level: advipservices

Configuration register is 0x2102

BFL_BURHANPUR_TCL#sh ip int brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up up
FastEthernet1 unassigned YES unset down down
FastEthernet2 unassigned YES unset down down
FastEthernet3 unassigned YES unset down down
FastEthernet4 unassigned YES NVRAM up up
FastEthernet4.3757 10.77.50.166 YES NVRAM up up
Loopback0 10.72.158.194 YES NVRAM up up
Loopback200 10.143.4.53 YES NVRAM up up
Vlan1 10.194.188.3 YES NVRAM up up
BFL_BURHANPUR_TCL#sh run int FastEthernet4
Building configuration...

Current configuration : 70 bytes
!
interface FastEthernet4
no ip address
duplex full
speed 100
end

BFL_BURHANPUR_TCL#sh int FastEthernet4
FastEthernet4 is up, line protocol is up
Hardware is PQII_PRO_UEC, address is a023.9f9d.9f6c (bia a023.9f9d.9f6c)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 129000 bits/sec, 26 packets/sec
5 minute output rate 16000 bits/sec, 9 packets/sec
8271454 packets input, 5876678238 bytes
Received 296771 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
6173224 packets output, 1873423725 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
71495 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
BFL_BURHANPUR_TCL#sh log
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 203 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 206 messages logged, xml disabled,
filtering disabled
Exception Logging: size (8192 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level debugging, 210 message lines logged
Logging to 10.70.0.201 (udp port 514, audit disabled,
link up),
209 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 10.209.19.200 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 121.240.6.13 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 121.240.5.113 (udp port 514, audit disabled,
link up),
210 message lines logged,
Logging to 121.240.6.13 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 121.240.5.113 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 121.240.118.90 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 115.114.170.78 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 202.54.29.110 (udp port 514, audit disabled,
link up),
210 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging Source-Interface: VRF Name:
FastEthernet4.3757

Log Buffer (8192 bytes):
cessful
Dec 9 12:26:56.383: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 13:07:27.920: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 13:07:27.920: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 13:07:28.292: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 13:07:57.925: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 13:23:28.522: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 13:23:28.522: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 13:23:29.702: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 13:23:58.527: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 13:29:28.756: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 13:29:28.760: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 13:29:29.128: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 13:29:58.761: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 13:50:59.554: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 13:50:59.554: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 13:51:16.937: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 13:51:29.587: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 13:53:29.663: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 13:53:29.663: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 13:53:47.037: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 13:53:59.667: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 15:41:28.744: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 15:41:28.748: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 15:41:29.116: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 15:41:58.749: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 16:09:29.802: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 16:09:29.802: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 16:09:30.874: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 16:09:59.807: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 16:20:00.183: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 16:20:00.183: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 16:20:00.555: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 16:20:30.212: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 9 17:25:02.660: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 9 17:25:02.664: %HA_EM-6-LOG: Failover: Failover Started
Dec 9 17:25:16.042: %HA_EM-6-LOG: Failover: Failover Successful
Dec 9 17:25:32.693: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 09:45:39.743: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 09:45:39.743: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 09:45:40.215: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 09:46:09.776: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 10:49:12.142: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 10:49:12.146: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 10:49:12.614: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 10:49:42.147: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 11:34:13.844: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 11:34:13.848: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 11:34:14.216: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 11:34:43.848: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 11:35:13.881: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 11:35:13.885: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 11:35:14.253: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 11:35:43.886: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 11:57:14.710: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 11:57:14.714: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 11:57:15.082: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 11:57:44.715: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 12:44:11.492: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 12:44:11.492: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 12:44:12.669: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 12:44:41.497: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 12:47:11.605: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 12:47:11.605: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 12:47:13.178: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 12:47:41.610: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 15:12:47.119: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 15:12:47.119: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 15:12:47.792: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 15:13:12.152: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 15:28:42.721: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 15:28:42.725: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 15:29:00.496: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 15:30:12.792: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 15:30:42.797: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 15:30:42.801: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 15:30:52.870: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 15:47:46.385: %BGP-3-NOTIFICATION: sent to neighbor 10.77.50.165 4/0 (hold time expired) 0 bytes
Dec 10 15:47:46.385: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 reset (BGP Notification sent)
Dec 10 15:47:46.417: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Down BGP Notification sent
Dec 10 15:47:46.417: %BGP_SESSION-5-ADJCHANGE: neighbor 10.77.50.165 IPv4 Unicast topology base removed from session BGP Notification sent
Dec 10 15:48:13.282: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 active reset (Peer closed the session)
Dec 10 15:48:13.282: %BGP_SESSION-5-ADJCHANGE: neighbor 10.77.50.165 IPv4 Unicast topology base removed from session Peer closed the session
Dec 10 15:48:24.824: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Up
Dec 10 16:01:22.913: %BGP-3-NOTIFICATION: sent to neighbor 10.77.50.165 4/0 (hold time expired) 0 bytes
Dec 10 16:01:22.913: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 reset (BGP Notification sent)
Dec 10 16:01:22.945: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Down BGP Notification sent
Dec 10 16:01:22.945: %BGP_SESSION-5-ADJCHANGE: neighbor 10.77.50.165 IPv4 Unicast topology base removed from session BGP Notification sent
Dec 10 16:01:52.029: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Up
Dec 10 16:07:14.185: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 16:09:14.260: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 16:09:14.264: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 16:09:16.633: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 16:26:06.463: %BGP-3-NOTIFICATION: sent to neighbor 10.77.50.165 4/0 (hold time expired) 0 bytes
Dec 10 16:26:06.463: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 reset (BGP Notification sent)
Dec 10 16:26:06.495: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Down BGP Notification sent
Dec 10 16:26:06.495: %BGP_SESSION-5-ADJCHANGE: neighbor 10.77.50.165 IPv4 Unicast topology base removed from session BGP Notification sent
Dec 10 16:26:24.830: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 active reset (Peer closed the session)
Dec 10 16:26:24.834: %BGP_SESSION-5-ADJCHANGE: neighbor 10.77.50.165 IPv4 Unicast topology base removed from session Peer closed the session
Dec 10 16:26:25.078: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 passive reset (Peer closed the session)
Dec 10 16:26:25.078: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 passive Down AFI/SAFI not supported
Dec 10 16:26:44.377: %BGP-5-ADJCHANGE: neighbor 10.77.50.165 Up
Dec 10 16:26:47.606: %BGP-5-NBR_RESET: Neighbor 10.77.50.165 passive reset (Peer closed the session)
Dec 10 16:35:15.239: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
Dec 10 17:14:46.727: %TRACK-6-STATE: 123 ip sla 123 reachability Up -> Down
Dec 10 17:14:46.727: %HA_EM-6-LOG: Failover: Failover Started
Dec 10 17:14:47.099: %HA_EM-6-LOG: Failover: Failover Successful
Dec 10 17:15:16.743: %TRACK-6-STATE: 123 ip sla 123 reachability Down -> Up
BFL_BURHANPUR_TCL# sh cloc
17:30:56.178 IST Fri Dec 10 2021
BFL_BURHANPUR_TCL#

=====================

A:mu-ind-t2-hrt02# show router 500020 bgp summary | match context all 10.77.50.166
10.77.50.166
65192 142 0 01h02m38s 2/2/3021 (IPv4)
1952 0
*A:mu-ind-t2-hrt02# show time
Fri Dec 10 17:29:23 IST 2021

Richard Burts · ‎12-11-2021

We have very little detailed information to work with, especially very limited information about configuration and that makes it difficult to offer good advice. I do have a couple of comments. If you want this discussion to go forward you need to provide us with more information.

- you obviously are running IP tracking. We do not know what you are tracking and do not know what impact the results of tracking might have on BGP. Certainly need more information about this.

- tracking is showing lots of ups and downs. So it appears the network environment is not stable. It is possible that this is impacting BGP.

- messages like this indicate that you are not receiving information (or not receiving some information) from the peer. So why is the peer not able to send you information?

HTH

Rick