BGP flap

We have p2p link between SanDeago and Mexico, configured with BGP.
in recent times the link is plapping continuously, plz check below bgp config on both routers.
NatPen_MX_3825#sh run | be bgp
router bgp 65001
no synchronization
bgp log-neighbor-changes
network 10.60.0.0 mask 255.255.0.0
redistribute static metric 20 route-map MXCAMMAP
neighbor 10.63.0.1 remote-as 1
neighbor 10.63.0.1 fall-over
no auto-summary
NatPen_MX_3825#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 10.63.0.1 to network 0.0.0.0
199.220.41.0/30 is subnetted, 1 subnets
B 199.220.41.176 [20/0] via 10.63.0.1, 00:00:13
1.0.0.0/24 is subnetted, 1 subnets
B 1.4.204.0 [20/0] via 10.63.0.1, 00:00:13
152.177.0.0/30 is subnetted, 1 subnets
B 152.177.74.24 [20/0] via 10.63.0.1, 00:00:13
152.181.0.0/30 is subnetted, 1 subnets
B 152.181.185.68 [20/0] via 10.63.0.1, 00:00:13
206.113.119.0/26 is subnetted, 2 subnets
B 206.113.119.128 [20/0] via 10.63.0.1, 00:00:13
B 206.113.119.0 [20/0] via 10.63.0.1, 00:00:13
199.220.194.0/30 is subnetted, 1 subnets
B 199.220.194.232 [20/0] via 10.63.0.1, 00:00:13
172.17.0.0/30 is subnetted, 1 subnets
B 172.17.29.0 [20/0] via 10.63.0.1, 00:00:13
172.16.0.0/24 is subnetted, 1 subnets
B 172.16.1.0 [20/0] via 10.63.0.1, 00:00:13
172.18.0.0/30 is subnetted, 2 subnets
B 172.18.30.0 [20/0] via 10.63.0.1, 00:00:13
B 172.18.29.0 [20/0] via 10.63.0.1, 00:00:13
172.21.0.0/30 is subnetted, 1 subnets
D 172.21.106.120 [220/63232] via 172.20.107.229, 5d03h, Serial2/0
172.20.0.0/30 is subnetted, 1 subnets
C 172.20.107.228 is directly connected, Serial2/0
172.23.0.0/30 is subnetted, 1 subnets
B 172.23.9.0 [20/0] via 10.63.0.1, 00:00:13
172.22.0.0/30 is subnetted, 2 subnets
B 172.22.0.144 [20/0] via 10.63.0.1, 00:00:13
D 172.22.157.84 [220/63232] via 172.20.107.229, 5d03h, Serial2/0
172.32.0.0/24 is subnetted, 1 subnets
B 172.32.7.0 [20/0] via 10.63.0.1, 00:00:13
10.0.0.0/8 is variably subnetted, 21 subnets, 5 masks
B 10.30.0.0/21 [20/0] via 10.63.0.1, 00:00:13
B 10.31.0.0/16 [20/0] via 10.63.0.1, 00:00:13
B 10.30.13.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.20.0.0/16 [20/0] via 10.63.0.1, 00:00:14
B 10.21.0.0/16 [20/0] via 10.63.0.1, 00:00:14
B 10.40.0.0/16 [20/0] via 10.63.0.1, 00:00:14
B 10.41.0.0/16 [20/0] via 10.63.0.1, 00:00:14
C 10.63.0.0/16 is directly connected, GigabitEthernet0/1
S 10.61.1.0/24 [1/0] via 10.60.0.2
C 10.60.0.0/16 is directly connected, GigabitEthernet0/0
B 10.100.0.44/30 [20/0] via 10.63.0.1, 00:00:14
B 10.133.201.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.100.0.32/30 [20/0] via 10.63.0.1, 00:00:14
B 10.90.0.0/16 [20/0] via 10.63.0.1, 00:00:14
B 10.172.16.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.4.204.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.4.205.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.3.202.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.4.202.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.4.201.0/24 [20/0] via 10.63.0.1, 00:00:14
B 10.254.254.240/32 [20/0] via 10.63.0.1, 00:00:14
147.225.0.0/30 is subnetted, 1 subnets
B 147.225.40.160 [20/0] via 10.63.0.1, 00:00:14
B 206.169.74.0/24 [20/0] via 10.63.0.1, 00:00:14
B 192.168.100.0/24 [20/0] via 10.63.0.1, 00:00:14
B* 0.0.0.0/0 [20/0] via 10.63.0.1, 00:00:14
NatPen_MX_3825#sh ip bg
NatPen_MX_3825#sh ip bgp
BGP table version is 32518, local router ID is 172.20.107.230
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 0.0.0.0 10.63.0.1 0 1 65000 65000 i
*> 1.4.204.0/24 10.63.0.1 0 1 ?
*> 10.3.202.0/24 10.63.0.1 0 1 ?
*> 10.4.201.0/24 10.63.0.1 0 1 ?
*> 10.4.202.0/24 10.63.0.1 0 1 ?
*> 10.4.204.0/24 10.63.0.1 0 1 ?
*> 10.4.205.0/24 10.63.0.1 0 1 ?
*> 10.20.0.0/16 10.63.0.1 0 1 65000 65000 ?
*> 10.21.0.0/16 10.63.0.1 0 1 65000 65000 i
*> 10.30.0.0/21 10.63.0.1 0 0 1 i
*> 10.30.13.0/24 10.63.0.1 0 0 1 i
*> 10.31.0.0/16 10.63.0.1 0 0 1 ?
*> 10.40.0.0/16 10.63.0.1 0 1 65000 65000 i
*> 10.41.0.0/16 10.63.0.1 0 1 65000 65000 ?
*> 10.60.0.0/16 0.0.0.0 0 32768 i
*> 10.61.1.0/24 10.60.0.2 20 32768 ?
r> 10.63.0.0/16 10.63.0.1 0 0 1 ?
*> 10.90.0.0/16 10.63.0.1 0 1 65000 10 i
*> 10.100.0.32/30 10.63.0.1 0 1 ?
*> 10.100.0.44/30 10.63.0.1 0 1 65000 65000 ?
*> 10.133.201.0/24 10.63.0.1 0 1 ?
*> 10.172.16.0/24 10.63.0.1 0 1 ?
*> 10.254.254.240/32
10.63.0.1 0 1 ?
*> 147.225.40.160/30
10.63.0.1 0 0 1 ?
*> 152.177.74.24/30 10.63.0.1 0 1 65000 ?
*> 152.181.185.68/30
10.63.0.1 0 1 65000 ?
*> 172.16.1.0/24 10.63.0.1 0 1 ?
*> 172.17.29.0/30 10.63.0.1 0 1 65000 65000 ?
*> 172.18.29.0/30 10.63.0.1 0 0 1 ?
*> 172.18.30.0/30 10.63.0.1 0 1 ?
*> 172.22.0.144/30 10.63.0.1 0 1 ?
*> 172.23.9.0/30 10.63.0.1 0 1 65000 65000 ?
*> 172.32.7.0/24 10.63.0.1 0 1 ?
*> 192.168.100.0 10.63.0.1 0 1 ?
*> 199.220.41.176/30
Network Next Hop Metric LocPrf Weight Path
10.63.0.1 0 1 ?
*> 199.220.194.232/30
10.63.0.1 0 1 65000 ?
*> 206.113.119.0/26 10.63.0.1 0 1 65000 65004 ?
*> 206.113.119.128/26
10.63.0.1 0 1 65000 65004 ?
*> 206.169.74.0 10.63.0.1 0 1 65000 65000 ?
NatPen_MX_3825#
NatPen_MX_3825#sh run | in ip rou
ip route 10.61.1.0 255.255.255.0 10.60.0.2
NatPen_MX_3825#
===============================================================================================================
router bgp 1
no synchronization
bgp log-neighbor-changes
network 10.30.0.0 mask 255.255.248.0
network 10.30.13.0 mask 255.255.255.0
redistribute connected
neighbor 10.63.0.2 remote-as 65001
neighbor 10.63.0.2 fall-over
neighbor 147.225.40.161 remote-as 65000
neighbor 147.225.40.161 distribute-list no-redist-CV-Routes out
neighbor 172.18.29.2 remote-as 1
no auto-summary
NatPen_SD2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 147.225.40.161 to network 0.0.0.0
199.220.41.0/30 is subnetted, 1 subnets
B 199.220.41.176 [200/0] via 10.100.0.34, 3w1d
1.0.0.0/24 is subnetted, 1 subnets
B 1.4.204.0 [200/0] via 10.133.201.254, 3w1d
152.177.0.0/30 is subnetted, 1 subnets
B 152.177.74.24 [20/0] via 147.225.40.161, 4w3d
152.181.0.0/30 is subnetted, 1 subnets
B 152.181.185.68 [20/0] via 147.225.40.161, 4w3d
206.113.119.0/26 is subnetted, 2 subnets
B 206.113.119.128 [20/0] via 147.225.40.161, 4w3d
B 206.113.119.0 [20/0] via 147.225.40.161, 4w3d
199.220.194.0/30 is subnetted, 1 subnets
B 199.220.194.232 [20/0] via 147.225.40.161, 4w0d
172.17.0.0/30 is subnetted, 1 subnets
B 172.17.29.0 [20/0] via 147.225.40.161, 3w0d
172.16.0.0/24 is subnetted, 1 subnets
B 172.16.1.0 [200/0] via 10.133.201.254, 3w1d
172.18.0.0/30 is subnetted, 2 subnets
B 172.18.30.0 [200/0] via 172.18.29.2, 3w1d
C 172.18.29.0 is directly connected, FastEthernet1/1
172.23.0.0/30 is subnetted, 1 subnets
B 172.23.9.0 [20/0] via 147.225.40.161, 1w2d
172.22.0.0/30 is subnetted, 1 subnets
B 172.22.0.144 [200/0] via 172.18.29.2, 3w1d
172.32.0.0/24 is subnetted, 1 subnets
B 172.32.7.0 [200/0] via 10.133.201.254, 3w1d
10.0.0.0/8 is variably subnetted, 21 subnets, 5 masks
C 10.30.0.0/21 is directly connected, GigabitEthernet0/0.1
C 10.31.0.0/16 is directly connected, GigabitEthernet0/0.2
C 10.30.13.0/24 is directly connected, GigabitEthernet0/0.2
B 10.20.0.0/16 [20/0] via 147.225.40.161, 4w0d
B 10.21.0.0/16 [20/0] via 147.225.40.161, 4w3d
B 10.40.0.0/16 [20/0] via 147.225.40.161, 1w2d
B 10.41.0.0/16 [20/0] via 147.225.40.161, 1w2d
C 10.63.0.0/16 is directly connected, GigabitEthernet0/1
B 10.61.1.0/24 [20/20] via 10.63.0.2, 00:01:44
B 10.60.0.0/16 [20/0] via 10.63.0.2, 00:01:44
B 10.100.0.44/30 [20/0] via 147.225.40.161, 4w3d
B 10.133.201.0/24 [200/0] via 172.18.29.2, 3w1d
B 10.100.0.32/30 [200/0] via 172.18.29.2, 3w1d
B 10.90.0.0/16 [20/0] via 147.225.40.161, 4w3d
B 10.172.16.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.4.204.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.4.205.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.3.202.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.4.202.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.4.201.0/24 [200/0] via 10.133.201.254, 3w1d
B 10.254.254.240/32 [200/0] via 10.133.201.254, 3w1d
147.225.0.0/30 is subnetted, 1 subnets
C 147.225.40.160 is directly connected, Serial3/0
B 206.169.74.0/24 [20/0] via 147.225.40.161, 2w1d
B 192.168.100.0/24 [200/0] via 10.133.201.254, 3w1d
B* 0.0.0.0/0 [20/0] via 147.225.40.161, 3w5d
NatPen_SD2#
NatPen_SD2#sh run | in ip route
ip route 0.0.0.0 0.0.0.0 10.133.201.254 210
ip route 1.4.205.147 255.255.255.255 10.100.0.29
ip route 170.146.36.16 255.255.255.255 10.100.0.29
ip route 170.146.234.48 255.255.255.255 10.100.0.29
NatPen_SD2#

Dear Sathish,
Is the link flapping or the BGP is flapping?
If it is the link that is flapping then your BGP with the neighbour and the IGP with the neighbour must flap.
If it is only BGP which is flapping then we have to look in to different scenario , please share the log messages for the notification provided by the peer.
BR
Md Thanveer

Similar Messages

BGP flaps frequently

Hi,
I'm getting below logs in my router frequently and BGP flaps. could someone tell me what are the possible causes of this issue.
Oct 2 02:33:50: %BGP-3-NOTIFICATION: received from neighbor 192.168.181.217 4/0 (hold time expired) 0 bytes
Oct 2 02:33:50: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Down Peer closed the session
Oct 2 02:33:50: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.181.217 IPv4 Unicast topology base removed from session Peer closed the session
Oct 2 02:33:57: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Up
Oct 2 03:35:52: %BGP-3-NOTIFICATION: received from neighbor 192.168.181.217 4/0 (hold time expired) 0 bytes
Oct 2 03:35:52: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Down Peer closed the session
Oct 2 03:35:52: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.181.217 IPv4 Unicast topology base removed from session Peer closed the session
Oct 2 03:36:03: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Up

Hello,
- Many potential issue...
- Is it EBGP or IBGP?
- May be hold-time too short.
- May be overload CPU.
- May be inconsistent Keepalive/hold time.
- May be network flapping in the middle...
C.

BGP Flapping and MTU

Hi everybody
I hope all my old pals ( no pun intended :) are doing fine. Today at work I encountered a strange issue, one of customer opened a ticket for BGP flapping.
It was only when I match the MTU of CE on PE router did bgp stabilize I asked of my senior co worker but he did not answer why. A lot of cisco documentation on google did not go into details why mismatched MTU could cause flapping.
I am reaching out to you guys may be someone knows and enlighten me.
Much appreciated
thanks

Hi Sarah,
You're welcome as always :)
Regarding the BGP flapping - can you be more specific? What exact kind of flapping was that? Were you getting any BGP notifications, or BGP hold intervals being exceeded? Any more technical information, such as logging messages, would be greatly helpful.
Speaking in an extremely general sense and most probably saying nothing new, MTU mismatches on a common link will cause the router with the smaller MTU to discard all incoming IP packets whose total size exceeds this smaller MTU. For unreliable protocols, this would cause irreparable packet losses. For TCP, the situation is more complex: each router opening a TCP session should advertise a TCP Maximum Segment Size (MSS) derived from its own MTU on the egress interface. The router with the smaller MTU would advertise its MSS equal to its smaller MTU minus 40, telling the other router to send TCP segments that would, after adding TCP and IP headers, be exactly MTU bytes long, so the other router would never send TCP segments that would be oversized. So here, despite the MTU mismatch on the same link, the TCP communication between the two routers should actually work.
Just wondering, what was the exact MTU value you had to configure? Was it significantly different from the default of 1500 bytes?
Best regards,
Peter

BGP continuosly flapping

Hi,
I'm getting below logs in my router frequently and BGP flaps. could someone tell me what are the possible causes of this issue.
Oct 2 02:33:50: %BGP-3-NOTIFICATION: received from neighbor 192.168.181.217 4/0 (hold time expired) 0 bytes
Oct 2 02:33:50: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Down Peer closed the session
Oct 2 02:33:50: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.181.217 IPv4 Unicast topology base removed from session Peer closed the session
Oct 2 02:33:57: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Up
Oct 2 03:35:52: %BGP-3-NOTIFICATION: received from neighbor 192.168.181.217 4/0 (hold time expired) 0 bytes
Oct 2 03:35:52: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Down Peer closed the session
Oct 2 03:35:52: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.181.217 IPv4 Unicast topology base removed from session Peer closed the session
Oct 2 03:36:03: %BGP-5-ADJCHANGE: neighbor 192.168.181.217 Up

Hi,
As Paul suggested check your connectivity, run an extended ping between BGP peers, might be as simple as layer 1 issue. Else check that you don't have recursive lookup for peer address where by you are peering with an address you you receive via BGP peering.
/Samir

EBGP PEER FLAP SNMP TRAP

Hi
Whenever there is a bgp neighbour flap, we are not getting snmp traps on the HP NNMI Server.. I believe during the neighbour flap, the device is unable to communicate with NNMI and drop the trap..
So I would like to write a custom EEM SCRIPT that can match a syslog pattern and generate a customised SNMP trap and send it to NNMI. May be I can delay the trap generation or sending so that the device restores the connectivity and then send an alert
Here are my questions:
Is this a good idea?
Can you give me a sample configuration with the MIB Values to be generated?
What MIB Should be loaded on the server?
I am curious how others are monitoring this kind of bgp flaps...
Sent from Cisco Technical Support iPad App

After i enabled snmp inform using following command
snmp-server host 100.190.19.33 informs version 2c XXXX
I see it is contineously incrementing snmp inform sent messages on the router..I am not sure what it is sending..I would like to be specific like sending only BGP snmp informs to the NMS..is it possible ?
DR1#show snmp
Chassis: FHK0850F0HL
4338622 SNMP packets input
    0 Bad SNMP version errors
    746076 Unknown community name
    0 Illegal operation for community name supplied
    0 Encoding errors
    35020739 Number of requested variables
    0 Number of altered variables
    3303916 Get-request PDUs
    97632 Get-next PDUs
    0 Set-request PDUs
    0 Input queue packet drops (Maximum queue size 1000)
6639622 SNMP packets output
    0 Too big errors (Maximum packet size 1500)
    546341 No such name errors
    0 Bad values errors
    0 General errors
    3592535 Response PDUs
    3047076 Trap PDUs
SNMP Dispatcher:
   queue 0/75 (current/max), 0 dropped
SNMP Engine:
   queue 0/1000 (current/max), 0 dropped
SNMP logging: enabled
    Logging to 10.45.224.19.162, 0/10, 761350 sent, 347 dropped.
    Logging to 10.48.176.1.162, 0/10, 759955 sent, 1886 dropped.
    Logging to 100.190.19.25.162, 0/10, 761329 sent, 368 dropped.
    Logging to 100.190.19.33.162, 0/10, 761367 sent, 474 dropped.
SNMP Manager-role output packets
    0 Get-request PDUs
    0 Get-next PDUs
    0 Get-bulk PDUs
    0 Set-request PDUs
    11 Inform-request PDUs
    0 Timeouts
    0 Drops
SNMP Manager-role input packets
    0 Inform request PDUs
    0 Trap PDUs
    11 Response PDUs
    0 Responses with errors
SNMP informs: enabled
    Informs in flight 0/25 (current/max)
    Logging to 100.190.19.33.162
        11 sent, 0 in-flight, 0 retries, 0 failed, 0 dropped

No memory available on a SUP720-3BXL with 1GB RAM

Hi,
any advices what to do if all RAM of the RP is consumed?
r1-core#show log
Sep 17 03:38:13.999 CET: %OSPF-5-ADJCHG: Process 8877, Nbr 10.100.205.246 on Vlan60 from FULL to DOWN, Neighbor Down: Dead timer expired
Sep 17 03:38:20.715 CET: %OSPF-5-ADJCHG: Process 8877, Nbr 10.100.205.246 on Vlan60 from LOADING to FULL, Loading Done
Sep 17 03:38:48.451 CET: %SYS-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from 0x434488CC, alignment 0
Pool: Processor Free: 1107328 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
-Process= "BGP Task", ipl= 0, pid= 626
-Traceback= 4340F154z 43428FE4z 4343FDD4z 41C77F70z 41CCB3C4z 41CCD7C0z 41CD0604z 41D3C380z 41D3CB48z 41D24B20z 433FAAC0z 433FAAACz
Sep 17 03:38:54.683 CET: %SYS-2-CFORKMEM: Process creation of BGP Open failed (no memory). -Process= "BGP Router", ipl= 0, pid= 558
-Traceback= 43444E34z 43444FDCz 41C8E09Cz 433F52D4z 433F5408z 41C903D0z 41CA22F8z
r1-core#show version
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(1)SY1, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 01-May-13 13:16 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
BOOTLDR: Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(1)SY1, RELEASE SOFTWARE (fc5)
r1-core-inn uptime is 16 weeks, 4 days, 4 hours, 16 minutes
Uptime for this control processor is 16 weeks, 4 days, 4 hours, 6 minutes
System returned to ROM by reload at 04:14:47 CET Wed Jan 12 2000 (SP by reload)
System restarted at 18:34:19 CET Sun May 25 2014
System image file is "disk0:s72033-adventerprisek9-mz.151-1.SY1.bin"
Last reload reason: Reload Command
cisco WS-C6509-E (R7000) processor (revision 1.3) with 983008K/65536K bytes of memory.
Processor board ID SMC11140074
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
16 Virtual Ethernet interfaces
122 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
r1-core#show module
Mod Ports Card Type Model Serial No.
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1301F7T8
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1108HB7S
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD08340D87
8 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL1338Z0SV
Mod MAC addresses Hw Fw Sw Status
1 0024.1469.ccb0 to 0024.1469.ccdf 3.0 12.2(18r)S1 15.1(1)SY1 Ok
3 001a.e27a.3840 to 001a.e27a.386f 2.5 12.2(18r)S1 15.1(1)SY1 Ok
5 0011.21b9.9928 to 0011.21b9.992b 3.2 8.5(4) 15.1(1)SY1 Ok
8 0027.0d34.ed50 to 0027.0d34.ed67 4.1 12.2(18r)S1 15.1(1)SY1 Ok
Mod Sub-Module Model Serial Hw Status
1 Distributed Forwarding Card WS-F6700-DFC3BXL SAL11370Q8C 5.3 Ok
3 Distributed Forwarding Card WS-F6700-DFC3BXL SAL1333W4V1 5.6 Ok
5 Policy Feature Card 3 WS-F6K-PFC3BXL SAL1040X3AU 1.8 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL1040Z0JL 2.2 Ok
8 Distributed Forwarding Card WS-F6700-DFC3BXL SAL1439UQVP 5.6 Ok
Mod Online Diag Status
1 Pass
3 Pass
5 Pass
8 Pass
r1-core#show memory summary
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 4732E520 885824224 873473292 12350932 1107328 556184
I/O 8000000 67108864 21641732 45467132 45467132 45465404
Critical 537DCDE0 475940 44 475896 475896 475896
Critical 949A940 36084 44 36040 36040 36040
Processor memory
Address Bytes Prev Next Ref PrevF NextF Alloc PC what
4732E520 0016853976 00000000 48341124 001 -------- -------- 433EB834 *Init*
48341124 0000012800 4732E520 48344350 001 -------- -------- 43FAE89C *Init*
48344350 0000005000 48341124 48345704 001 -------- -------- 433F9578 List Headers
48345704 0000000160 48344350 483457D0 001 -------- -------- 43FAAFA0 *Init*
483457D0 0000000160 48345704 4834589C 001 -------- -------- 43FAAFA0 *Init*
4834589C 0000000160 483457D0 48345968 001 -------- -------- 43FAAFA0 *Init*
48345968 0000000160 4834589C 48345A34 001 -------- -------- 43FAAFA0 *Init*
48345A34 0000000160 48345968 48345B00 001 -------- -------- 43FAAFA0 *Init*
48345B00 0000001500 48345A34 48346108 001 -------- -------- 43452288 messages
48346108 0000010000 48345B00 48348844 001 -------- -------- 434522E4 Watched Queue
48348844 0000010000 48346108 4834AF80 001 -------- -------- 4345233C Watched Bitfield
4834AF80 0000005000 48348844 4834C334 001 -------- -------- 43452394 Watcher Info
4834C334 0000001500 4834AF80 4834C93C 001 -------- -------- 434523EC Watcher Message Queue
4834C93C 0000004288 4834C334 4834DA28 001 -------- -------- 4073CD0C TTY data
4834DA28 0000000512 4834C93C 4834DC54 001 -------- -------- 4073E668 TTY Output Buf
4834DC54 0000000160 4834DA28 4834DD20 001 -------- -------- 43FAAFA0 *Init*
4834DD20 0000026000 4834DC54 483542DC 001 -------- -------- 41481DFC Process Stack
483542DC 0000000184 4834DD20 483543C0 001 -------- -------- 4344FDC8 Process Events
483543C0 0000000160 483542DC 4835448C 001 -------- -------- 43FAAFA0 *Init*
4835448C 0000000648 483543C0 48354740 001 -------- -------- 4344D754 Process
48354740 0000000124 4835448C 483547E8 001 -------- -------- 41485478 *Init*
483547E8 0000010000 48354740 48356F24 001 -------- -------- 433F82E0 List Elements
48356F24 0000010000 483547E8 48359660 001 -------- -------- 433F82E0 List Elements
48359660 0000010000 48356F24 4835BD9C 001 -------- -------- 433F82E0 List Elements
4835BD9C 0000010000 48359660 4835E4D8 001 -------- -------- 433F82E0 List Elements
4835E4D8 0000010000 4835BD9C 48360C14 001 -------- -------- 433F82E0 List Elements
48360C14 0000000220 4835E4D8 48360D1C 001 -------- -------- 408658C8 Env action
48360D1C 0000000184 48360C14 48360E00 001 -------- -------- 408658C8 Env action
48360E00 0000000184 48360D1C 48360EE4 001 -------- -------- 408658C8 Env action
48360EE4 0000000148 48360E00 48360FA4 001 -------- -------- 43782A4C Crypto CA
48360FA4 0000000184 48360EE4 48361088 001 -------- -------- 408657C4 Env action
48361088 0000000184 48360FA4 4836116C 001 -------- -------- 408658C8 Env action
4836116C 0000000184 48361088 48361250 001 -------- -------- 408657C4 Env action
48361250 0000000184 4836116C 48361334 001 -------- -------- 408658C8 Env action
48361334 0000000832 48361250 483616A0 001 -------- -------- 40D9BF10 FM_HA_RDT_INDEX_LIST
483616A0 0000000832 48361334 48361A0C 001 -------- -------- 40D9BF10 FM_HA_RDT_INDEX_LIST
48361A0C 0000000128 483616A0 48361AB8 001 -------- -------- 40D29F90 FM core
48361AB8 0000000240 48361A0C 48361BD4 001 -------- -------- 437BAABC Crypto CA
48361BD4 0000000028 48361AB8 48361C1C 001 -------- -------- 437A3F88 Crypto CA
48361C1C 0000000184 48361BD4 48361D00 001 -------- -------- 408657C4 Env action
48361D00 0000000184 48361C1C 48361DE4 001 -------- -------- 408657C4 Env action
48361DE4 0000000184 48361D00 48361EC8 001 -------- -------- 408658C8 Env action
48361EC8 0000000032 48361DE4 48361F14 001 -------- -------- 40C106E8 draco-oir-process:slot 1
48361F14 0000000032 48361EC8 48361F60 001 -------- -------- 42269CFC Entity MIB C6k Private Process
48361F60 0000000032 48361F14 48361FAC 001 -------- -------- 420D4CB4 Bitfield pool
48361FAC 0000000512 48361F60 483621D8 001 -------- -------- 425779B4 IPC Rx Win Table
483621D8 0000000512 48361FAC 48362404 001 -------- -------- 425779B4 IPC Rx Win Table
48362404 0000000648 483621D8 483626B8 001 -------- -------- 407B4094 XDR: Peer cblk
483626B8 0000000320 48362404 48362824 001 -------- -------- 407BA6C8 XDR: stats array
48362824 0000000300 483626B8 4836297C 001 -------- -------- 407BA6C8 XDR: stats array
4836297C 0000000280 48362824 48362AC0 001 -------- -------- 407BA6C8 XDR: stats array
48362AC0 0000002420 4836297C 48363460 001 -------- -------- 407BA6C8 XDR: stats array
48363460 0000000460 48362AC0 48363658 001 -------- -------- 407BA6C8 XDR: stats array
48363658 0000000560 48363460 483638B4 001 -------- -------- 407BA6C8 XDR: stats array
483638B4 0000000320 48363658 48363A20 001 -------- -------- 407BA6C8 XDR: stats array
48363A20 0000000280 483638B4 48363B64 001 -------- -------- 407BA6C8 XDR: stats array
48363B64 0000000120 48363A20 48363C08 001 -------- -------- 407BA6C8 XDR: stats array
48363C08 0000000156 48363B64 48363CD0 001 -------- -------- 407BA6C8 XDR: stats array
48363CD0 0000001500 48363C08 483642D8 001 -------- -------- 434040C4 Reg Function Seq List
483642D8 0000001500 48363CD0 483648E0 001 -------- -------- 4340411C Reg Function iList
483648E0 0000001500 483642D8 48364EE8 001 -------- -------- 43404174 Reg Function Caselist
48364EE8 0000000032 483648E0 48364F34 001 -------- -------- 42075A40 Init
48364F34 0000000184 48364EE8 48365018 001 -------- -------- 408658C8 Env action
48365018 0000000184 48364F34 483650FC 001 -------- -------- 4124C56C QM-SB
483650FC 0000000060 48365018 48365164 001 -------- -------- 40B237E0 IPC Seat Manager
48365164 0000000088 483650FC 483651E8 001 -------- -------- 4133A234 SIP10GQM-SB
483651E8 0000000032 48365164 48365234 001 -------- -------- 41D08250 BGP Router
48365234 0000000048 483651E8 48365290 001 -------- -------- 43222694 Entity MIB API
48365290 0000000112 48365234 4836532C 001 -------- -------- 4227D18C *Init*
4836532C 0000000032 48365290 48365378 001 -------- -------- 4203E7F0 Parser Linkage
48365378 0000000032 4836532C 483653C4 001 -------- -------- 4203E7F0 Parser Linkage
483653C4 0000000032 48365378 48365410 001 -------- -------- 4203E7F0 Parser Linkage
48365410 0000000032 483653C4 4836545C 001 -------- -------- 42075A40 Init
4836545C 0000000072 48365410 483654D0 001 -------- -------- 43404C54 *Init*
483654D0 0000000072 4836545C 48365544 001 -------- -------- 43404C54 *Init*
48365544 0000000052 483654D0 483655A4 001 -------- -------- 43404C54 *Init*
483655A4 0000000204 48365544 4836569C 001 -------- -------- 43404C54 *Init*
4836569C 0000000112 483655A4 48365738 001 -------- -------- 43404C54 *Init*
48365738 0000000024 4836569C 4836577C 001 -------- -------- 43404C54 *Init*
4836577C 0000001552 48365738 48365DB8 001 -------- -------- 404F4FB0 *Init*
48365DB8 0000003000 4836577C 4836699C 001 -------- -------- 40500E7C Transport ERP id cb chunk
4836699C 0000000032 48365DB8 483669E8 001 -------- -------- 42075A40 Init
483669E8 0000000032 4836699C 48366A34 001 -------- -------- 4203E7F0 Parser Linkage
48366A34 0000000032 483669E8 48366A80 001 -------- -------- 4203E7F0 Parser Linkage
48366A80 0000000032 48366A34 48366ACC 001 -------- -------- 42075A40 Init
48366ACC 0000000024 48366A80 48366B10 001 -------- -------- 43F76708 *Init*
48366B10 0000000024 48366ACC 48366B54 001 -------- -------- 43F766F4 *Init*
48366B54 0000000024 48366B10 48366B98 001 -------- -------- 43F76728 *Init*
48366B98 0000000024 48366B54 48366BDC 001 -------- -------- 43F76708 *Init*
48366BDC 0000000024 48366B98 48366C20 001 -------- -------- 43F766F4 *Init*
48366C20 0000000024 48366BDC 48366C64 001 -------- -------- 43F76728 *Init*
48366C64 0000000024 48366C20 48366CA8 001 -------- -------- 43F76708 *Init*
48366CA8 0000000024 48366C64 48366CEC 001 -------- -------- 43F766F4 *Init*
48366CEC 0000000024 48366CA8 48366D30 001 -------- -------- 43F76728 *Init*
48366D30 0000000024 48366CEC 48366D74 001 -------- -------- 43F76708 *Init*
48366D74 0000000024 48366D30 48366DB8 001 -------- -------- 43F766F4 *Init*
48366DB8 0000000024 48366D74 48366DFC 001 -------- -------- 43F76728 *Init*
48366DFC 0000000024 48366DB8 48366E40 001 -------- -------- 43F76708 *Init*
48366E40 0000000024 48366DFC 48366E84 001 -------- -------- 43F766F4 *Init*
48366E84 0000000024 48366E40 48366EC8 001 -------- -------- 43F76728 *Init*
48366EC8 0000000024 48366E84 48366F0C 001 -------- -------- 43F76708 *Init*
48366F0C 0000000024 48366EC8 48366F50 001 -------- -------- 43F766F4 *Init*
48366F50 0000000024 48366F0C 48366F94 001 -------- -------- 43F76728 *Init*
48366F94 0000000024 48366F50 48366FD8 001 -------- -------- 43F76708 *Init*
48366FD8 0000000024 48366F94 4836701C 001 -------- -------- 43F766F4 *Init*
4836701C 0000000024 48366FD8 48367060 001 -------- -------- 43F76728 *Init*
48367060 0000000024 4836701C 483670A4 001 -------- -------- 43F76708 *Init*
483670A4 0000000024 48367060 483670E8 001 -------- -------- 43F766F4 *Init*
483670E8 0000000024 483670A4 4836712C 001 -------- -------- 43F76728 *Init*
4836712C 0000000024 483670E8 48367170 001 -------- -------- 43F76708 *Init*
48367170 0000000024 4836712C 483671B4 001 -------- -------- 43F766F4 *Init*
483671B4 0000000024 48367170 483671F8 001 -------- -------- 43F76728 *Init*
483671F8 0000000024 483671B4 4836723C 001 -------- -------- 43F76708 *Init*
4836723C 0000000024 483671F8 48367280 001 -------- -------- 43F766F4 *Init*
48367280 0000000024 4836723C 483672C4 001 -------- -------- 43F76728 *Init*
483672C4 0000000024 48367280 48367308 001 -------- -------- 43F76708 *Init*
48367308 0000000024 483672C4 4836734C 001 -------- -------- 43F766F4 *Init*
4836734C 0000000024 48367308 48367390 001 -------- -------- 43F76728 *Init*
48367390 0000000024 4836734C 483673D4 001 -------- -------- 43F76708 *Init*
483673D4 0000000024 48367390 48367418 001 -------- -------- 43F766F4 *Init*
48367418 0000000024 483673D4 4836745C 001 -------- -------- 43F76728 *Init*
4836745C 0000000024 48367418 483674A0 001 -------- -------- 43F76708 *Init*
483674A0 0000000024 4836745C 483674E4 001 -------- -------- 43F766F4 *Init*
483674E4 0000000024 483674A0 48367528 001 -------- -------- 43F76728 *Init*
48367528 0000000024 483674E4 4836756C 001 -------- -------- 43F76708 *Init*
4836756C 0000000024 48367528 483675B0 001 -------- -------- 43F766F4 *Init*
483675B0 0000000024 4836756C 483675F4 001 -------- -------- 43F76728 *Init*
483675F4 0000000024 483675B0 48367638 001 -------- -------- 43F76708 *Init*
48367638 0000000024 483675F4 4836767C 001 -------- -------- 43F766F4 *Init*
4836767C 0000000024 48367638 483676C0 001 -------- -------- 43F76728 *Init*
483676C0 0000000024 4836767C 48367704 001 -------- -------- 43F76708 *Init*
48367704 0000000024 483676C0 48367748 001 -------- -------- 43F766F4 *Init*
48367748 0000000024 48367704 4836778C 001 -------- -------- 43F76728 *Init*
4836778C 0000000024 48367748 483677D0 001 -------- -------- 43F76708 *Init*
483677D0 0000000024 4836778C 48367814 001 -------- -------- 43F766F4 *Init*
48367814 0000000024 483677D0 48367858 001 -------- -------- 43F76728 *Init*
48367858 0000000024 48367814 4836789C 001 -------- -------- 43F76708 *Init*
4836789C 0000000024 48367858 483678E0 001 -------- -------- 43F766F4 *Init*
483678E0 0000000024 4836789C 48367924 001 -------- -------- 43F76728 *Init*
48367924 0000000024 483678E0 48367968 001 -------- -------- 43F76708 *Init*
48367968 0000000024 48367924 483679AC 001 -------- -------- 43F766F4 *Init*
483679AC 0000000024 48367968 483679F0 001 -------- -------- 43F76728 *Init*
483679F0 0000000024 483679AC 48367A34 001 -------- -------- 43F76708 *Init*
48367A34 0000000024 483679F0 48367A78 001 -------- -------- 43F766F4 *Init*
48367A78 0000000024 48367A34 48367ABC 001 -------- -------- 43F76728 *Init*
48367ABC 0000000024 48367A78 48367B00 001 -------- -------- 43F76708 *Init*
48367B00 0000000024 48367ABC 48367B44 001 -------- -------- 43F766F4 *Init*
48367B44 0000000024 48367B00 48367B88 001 -------- -------- 43F76728 *Init*
48367B88 0000000024 48367B44 48367BCC 001 -------- -------- 43F76708 *Init*
48367BCC 0000000024 48367B88 48367C10 001 -------- -------- 43F766F4 *Init*
48367C10 0000000024 48367BCC 48367C54 001 -------- -------- 43F76728 *Init*
48367C54 0000000024 48367C10 48367C98 001 -------- -------- 43F76708 *Init*
48367C98 0000000024 48367C54 48367CDC 001 -------- -------- 43F766F4 *Init*
48367CDC 0000000024 48367C98 48367D20 001 -------- -------- 43F76728 *Init*
48367D20 0000000024 48367CDC 48367D64 001 -------- -------- 43F76708 *Init*
48367D64 0000000024 48367D20 48367DA8 001 -------- -------- 43F766F4 *Init*
48367DA8 0000000024 48367D64 48367DEC 001 -------- -------- 43F76728 *Init*
48367DEC 0000000024 48367DA8 48367E30 001 -------- -------- 43F76708 *Init*
48367E30 0000000024 48367DEC 48367E74 001 -------- -------- 43F766F4 *Init*
48367E74 0000000024 48367E30 48367EB8 001 -------- -------- 43F76728 *Init*
48367EB8 0000000024 48367E74 48367EFC 001 -------- -------- 43F76708 *Init*
48367EFC 0000000024 48367EB8 48367F40 001 -------- -------- 43F766F4 *Init*
48367F40 0000000024 48367EFC 48367F84 001 -------- -------- 43F76728 *Init*
48367F84 0000000024 48367F40 48367FC8 001 -------- -------- 43F76708 *Init*
48367FC8 0000000024 48367F84 4836800C 001 -------- -------- 43F766F4 *Init*
4836800C 0000000024 48367FC8 48368050 001 -------- -------- 43F76728 *Init*
48368050 0000000024 4836800C 48368094 001 -------- -------- 43F76708 *Init*
48368094 0000000024 48368050 483680D8 001 -------- -------- 43F766F4 *Init*
483680D8 0000000024 48368094 4836811C 001 -------- -------- 43F76728 *Init*
4836811C 0000000024 483680D8 48368160 001 -------- -------- 43F76708 *Init*
48368160 0000000024 4836811C 483681A4 001 -------- -------- 43F766F4 *Init*
483681A4 0000000024 48368160 483681E8 001 -------- -------- 43F76728 *Init*
Bug in IOS Version? More RAM is not possible in SUP720-3BXL.
Thanks,
Thomas

> Tracebacks and BGP flapping are not necessarily related.
BGP flapps because there was no more RAM available. (according to the log "ip cef was disabled" because of low memory) After reactivating "ip cef distributed" the BGP sessions becomes stable.
> After the IOS upgrade, did you see any more Tracebacks?
I did not see any tracebacks in the log. Because of having much lower memory available with the new image (only 10-15MB RAM after booting) I decide to downgrade and boot with the previous version.

Ciscoworks RME Syslog Automation Actions

I set up RME several years ago on our Ciscoworks several running LMS 3.2 to notify us on any BGP flaps via email notification.
I noticed the last couple maintenance period where we had perform Circuit work with our ISP's. We haven't received any emails....I verified those
routers are configured to send notifications in the Device Selector and even checked the router logs.
004161: Nov 20 05:04:52 EST: %BGP-5-ADJCHANGE: neighbor X.X.X.X Down BGP Notification sent
004162: Nov 20 05:04:52 EST: %BGP-3-NOTIFICATION: sent to neighbor X.X.X.X 4/0 (hold time expired) 0 bytes
The syslog collector status appears to be normal.....is there anything I need to do the fix this?

Hi,
Are you receiving any emails from your LMS server? If not, navigate to Common Services > Server > Admin > System Preferences to enter your SMTP settings.
Identifying the syslog message is one step but there are more.
AUTOMATED ACTIONS
Set Up
By default, Automated Actions are used to notify via email, using the `sampleEmailScript.pl` as the script to run. If you do not want to use this, you could write or use your own scripts to perform the action that you really want. In this case please note that we do not provide support for any custom scripts if the problem seems to be related to the script that you are using.
You still need the following settings:
1. Select Devices
In *RME > Tools > Syslog > Automated Actions* and click on create and select the devices that you wish to use.
2. Define Message Type
Please give a name to the Automated Action and then click on add to define a message type. In here, please specify the following values:
    Facility: BGP
    Sub-facility: *
    Severity: 5
    Mnemonic: ADJCHANGE
    Description: *
3. Select Automated Action
Select the default script or the script that you wish to use. Please note that this script must be located in the *CSCOpx/files/scripts/syslog* file and needs to have only write/execute permissions for casuser/Administrator in Windows.
This way when a message matching the above is generated, the Automated Action is triggered and this will run the script that you choose and do the commands that it has specified.
Here is an example:
If you verify that your setup is correctly configured then take a look at the smtp.log found under ../CSCOpx/log.
Thanks.

Prefix-list; clear bgp peer-group Test soft in; no file prompt quiet

Hello everyone,
I have a few simple questions. Hope someone will help me Thank you in advance.
1) We are using prefix-set into route-maps, but how I can use a prefix-list?
2) In classic IOS we have the command: clear bgp peer-group Test soft in
I don't see it in IOS-XR (Cisco IOS XR Software, Version 4.0.1):
RP/0/RSP0/CPU0:STH02#clear bgp ipv4 unicast ?
*                  Clear all peers and all routes from the BGP table
A.B.C.D or X:X::X BGP neighbor address to clear
as                 Clear peers in a specific AS
dampening          Clear route flap dampening information
external           Clear all external peers
flap-statistics    Clear flap statistics
nexthop            Clear nexthop
self-originated    Clear redistributed, network and aggregate routes originated here
shutdown           Clear all peers which were shut down due to low memory
3) In classic IOS we have the command: no file prompt quiet
I don't see it in IOS-XR. What is the command for IOS-XR?
I need it for the operation like this:
copy ftp://**:***@216.*.*.*/CUST_AS-TEST-in.prefixlist compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist
Wed Apr 18 12:02:00.936 UTC
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]? !!!!   I don't need this question
Copy : Destination exists, overwrite ?[confirm]                                                   !!!!   I don't need this question
Accessing ftp://*:*@216.*.*.*/CUST_AS-TEST-in.prefixlist
C
584 bytes copied in      0 sec
Have a nice day,
Dimitry

Thank you Alexander for your reply. It is the good RPL description and I've got the idea of REFRESH capable peer.
BUT, I still don't find the answer on my 3-d question:
In classic IOS we have the command: no file prompt quiet
I don't see it in IOS-XR. What is the command for IOS-XR?
I need it for the operation like this:
copy ftp://**:***@216.*.*.*/CUST_AS-TEST-in.prefixlist compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist
Wed Apr 18 12:02:00.936 UTC
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]? !!!!   I don't need this question
Copy : Destination exists, overwrite ?[confirm]                                                   !!!!   I don't need this question
Accessing ftp://*:*@216.*.*.*/CUST_AS-TEST-in.prefixlist
C
584 bytes copied in      0 sec
How can I suppress confirmations like this?
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]?
Copy : Destination exists, overwrite ?[confirm]
Dimitry

BGP peering via default route

I read http://blog.ipexpert.com/2010/11/08/bgp-peering-and-default-routes/ and understood that BGP speaker will not initiate BGP connection with the other BGP router if it can reach it via default route only...And BGP peering will not come up at all if both the BGP speakers know each other via default routes only....I could not understand the reason behind this though...Could any expert help me in understanding the underlying reasoning?

I can't think of a reason why you would want to peer with a router you don't have a route for. If you're relying on a default route for a multi-hop bgp peer session, it could cause the session to be unreliable due to changes in the network down the line from you. An unreliable bgp session would be bad on the router's cpu/memory if the session were to flap.

BGP Notification received, configuration change

Hi,
We are monitoring a BGP peering flap for a fraction of seconds approximately every three days for a particular neighbor. We are seeing this behavior consistently for a Month.
Jun 10 08:55:15.566 NST: bgp[1041]: %ROUTING-BGP-5-ADJCHANGE : neighbor x.x.x.x Down - BGP Notification received, configuration change (VRF: default)
Jun 10 08:55:15.565 NST: bgp[1041]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor x.x.x.x on standby due to BGP Notification received (VRF: default)
Would like to know what does the error messge indicates "BGP Notification received, configuration change"

There might be a clue in the bgp trace on the device that experienced this condition:
show bgp trace and look around the time of the notification down.
Depending on what is on the other side, I think that hte investigation is better done on that node as that was the originator of the change hence bringing the peer down.
This can be as simple as an address family add or remove, things like that. When capabilities of a peer change, they have to bring down the peering since they are only sent in the OPEN message.
IF it is very periodic, I would also verify and check what might be happening during those time windows, especially on the peer. Maybe there is a config script that could induce things.
If that peer is an XR device, the bgp trace will be very helpful in that regard.
If itis an IOS device, then maybe you need to keep running some debug bgp event for around the time that you expect this flap, and a syslog analysis (sh log) around that time for clues.
xander

BGP Router high process

What do we need to do if BGP Router contribute high process in CPU?
CPU utilization for five seconds: 97%/43%; one minute: 99%; five minutes: 92%
PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
44    36270732 35464661       1022 25.03% 15.21% 14.43%   0 BGP Router
325   7703860203228294256          0 10.47% 5.58% 5.24%   0 IP Input
455     7596596 28244228        268 5.59% 1.60% 0.82%   0 BGP I/O
543    13576608   8569950       1584 3.83% 18.94% 9.57%   0 BGP Task
   9   152474380 15201602      10030 2.07% 0.27% 0.57%   0 Check heaps
376    16372652   7777145       2105 1.83% 13.93% 13.76%   0 IP RIB Update
358    56785192 14452691       3929 0.95% 0.44% 0.52%   0 CEF: IPv4 proces
23    55656604 116191071        479 0.71% 0.51% 0.50%   0 ARP Input
348     5736736   7812055        734 0.63% 4.19% 5.03%   0 XDR mcast
546    36531108 132425650        275 0.63% 0.37% 0.28%   0 Port manager per
35    56337684 306101724        184 0.23% 0.42% 0.30%   0 IPC Seat Manager
330   287962916 871459868        330 0.23% 0.39% 1.61%   0 SNMP ENGINE
286      7682841067821917          0 0.15% 0.07% 0.07%   0 Ethernet Msec Ti
626      354112    825565        428 0.15% 0.11% 0.09%   0 IPv6 Input
   3      754316 523105917          1 0.15% 0.10% 0.09%   0 HSRP Common
385     2182508 14151135        154 0.15% 0.10% 0.14%   0 L3 Manager
317    44655884 658073408         67 0.07% 0.04% 0.21%   0 PDU DISPATCHER
395     4363480   4661440        936 0.07% 0.04% 0.05%   0 HIDDEN VLAN Proc
323     1161648 134374319          8 0.07% 0.04% 0.05%   0 VRRS Main thread
56     2269676   9230664        245 0.07% 0.08% 0.07%   0 Per-Second Jobs
240     1449416   1870109        775 0.07% 0.04% 0.05%   0 Compute load avg
243   1488814081309230003        113 0.07% 0.13% 0.76%   0 IP SNMP
CPU utilization for five seconds: 97%/43%; one minute: 99%; five minutes: 92%
PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
44    36270732 35464661       1022 25.03% 15.21% 14.43%   0 BGP Router
325   7703860203228294256          0 10.47% 5.58% 5.24%   0 IP Input
455     7596596 28244228        268 5.59% 1.60% 0.82%   0 BGP I/O
543    13576608   8569950       1584 3.83% 18.94% 9.57%   0 BGP Task
   9   152474380 15201602      10030 2.07% 0.27% 0.57%   0 Check heaps
376    16372652   7777145       2105 1.83% 13.93% 13.76%   0 IP RIB Update
358    56785192 14452691       3929 0.95% 0.44% 0.52%   0 CEF: IPv4 proces
23    55656604 116191071        479 0.71% 0.51% 0.50%   0 ARP Input
348     5736736   7812055        734 0.63% 4.19% 5.03%   0 XDR mcast
546    36531108 132425650        275 0.63% 0.37% 0.28%   0 Port manager per
35    56337684 306101724        184 0.23% 0.42% 0.30%   0 IPC Seat Manager
330   287962916 871459868        330 0.23% 0.39% 1.61%   0 SNMP ENGINE
286      7682841067821917          0 0.15% 0.07% 0.07%   0 Ethernet Msec Ti
626      354112    825565        428 0.15% 0.11% 0.09%   0 IPv6 Input
   3      754316 523105917          1 0.15% 0.10% 0.09%   0 HSRP Common
385     2182508 14151135        154 0.15% 0.10% 0.14%   0 L3 Manager
317    44655884 658073408         67 0.07% 0.04% 0.21%   0 PDU DISPATCHER
395     4363480   4661440        936 0.07% 0.04% 0.05%   0 HIDDEN VLAN Proc
323     1161648 134374319          8 0.07% 0.04% 0.05%   0 VRRS Main thread
56     2269676   9230664        245 0.07% 0.08% 0.07%   0 Per-Second Jobs
240     1449416   1870109        775 0.07% 0.04% 0.05%   0 Compute load avg
243   1488814081309230003        113 0.07% 0.13% 0.76%   0 IP SNMP

Hi,
BGP Router process is in charge to determine the best path and processes any route "churn". It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
(http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html)
So I suggest to check what make this process working hard. Depending on that you can choose what to do: bgp dampening (if you have many changes in advertisement received form a neighbor), tuning timer (if neighbor is flapping), using peer-group / update-groups to reduce the amount of job your BGP process has to do to process updates etc...
Have a look here: https://supportforums.cisco.com/discussion/11604471/high-cpu-usage-bgp-router-process
Bye,
enrico
PS please rate if useful

EIGRP and BGP

when EIGRP and BGP is flapping.
which portion should I check to find out
if it is flapping because of high traffic or low quality access lines?
which should config should I check?
thanks a lot

Following links may help you
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094613.shtml
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009478a.shtml

Why internal EIGRP flapping when a WAN link is flapping?

I have router A and B running EIGRP in between. Router B has a WAN connection into the carrier.
Recently the EIGRP neighboring between A and B was flapping. In the mean time the WAN link was flapping too.
Router B was running BGP over the WAN link and redistributing BGP into EIGRP.
Why the WAN link issue caused the EIGRP neighboring up and down?
Thanks
Gary

When we attempted to ping the ISP's router will a full size MTU packet, the packet gets dropped. Any packets greater than 400 bytes gets dropped.

BGP dampening

Hi,
I have to check if in Cisco 7200 router there are bgp session flapping without charging the cpu and I had an idea using the bgp dampening command.
Now, if someone used it, if this command introduces cpu load.
Thank you.
Regards.
Paolo

bgp route dampening is not so cpu intensive.
once the route is dampened, it depends on a simple property, the ReuseLimit, in conjunction with the HalfLife of the suppression, to begin advertising the route again.
this is not too cpu intensive to worry about, unless you had thousands of routes to dampen.

How to reduce BGP scanner in C7200?

Hi,
I have a Cisco 7206VXR with NPE-300 and 256 MB of RAM.
I have the problem issue that the BGP scanner process is about 9.6% on 32% of total CPU load.Randomly there are picks up to 99% of BGP scanner.
I thought that it caused by route flapping but after enabling bgp dampening it happened anything.
Does anyone know how to create route inbound filtering from two peers?
Thank you very much.
Regrds.
Paolo

The BGP scanner by default runs every 60seconds. It goes through and updates the BGP tables (remove or add routes based on current information).
For filtering on the inbound direction, you can filter based on prefix or ASN. The following example is a bit of an overkill, but it only allows the /23 prefix listed, routes in this /23 originated in the AS listed, and a max of 50 routes to be advertised to this device:
neighbor 1.1.1.1 remote-as 65001
neighbor 1.1.1.1 description [Customer-A]
neighbor 1.1.1.1 prefix-list Customer in
neighbor 1.1.1.1 maximum-prefix 50
neighbor 1.1.1.1 filter-list 32 in
ip prefix-list Customer-In description [Customer-A]
ip prefix-list Customer-In seq 5 permit 10.0.0.0/23
ip as-path access-list 32 permit _65001$
You could always talk to your ISP and take partial routes instead of a full table if you wanted. Hope this helps.

BGP flap

Similar Messages

Maybe you are looking for