02-01-2017 03:31 AM - edited 03-05-2019 07:57 AM
Hi guys,
My BGP went down suddenly and won't establish any longer, constantly getting the message saying "%BGP-3-NOTIFICATION: received from neighbor 10.254.241.1 2/8 (open: unknown subcode) 3 bytes 000101". BGP state is sitting in idle and sometimes goes to Active but never in Established state. This was working fine until I decided to redistribute EIGRP into BGP and vice-versa. As soon as I configured the redistribution, I started getting these message. Now I tried ip prefix filters, removing re-distribution, removing EIGRP altogether but success yet. I know my ISP has a prefix limit of 50 but here I am not even advertising 50 prefixes. My ISP tried resetting the peer but it didn't help.
Here's the BGP state:
BGP neighbor is 10.254.241.1, remote AS 2856, external link
Description: Peer to BT PE
BGP version 4, remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:26, last write 00:00:26, hold time is 180, keepalive interval is 60 seconds
Message statistics:
InQ depth is 0
OutQ depth is 0
Sent Rcvd
Opens: 46919 5
Notifications: 0 46919
Updates: 35 122
Keepalives: 10 10
Route Refresh: 0 0
Total: 46964 47056
Default minimum time between advertisement runs is 30 seconds
For address family: IPv4 Unicast
BGP table version 2894, neighbor version 0/0
Output queue size : 0
Index 1, Offset 0, Mask 0x2
1 update-group member
Inbound soft reconfiguration allowed
Sent Rcvd
Prefix activity: ---- ----
Prefixes Current: 0 0
Prefixes Total: 0 0
Implicit Withdraw: 0 0
Explicit Withdraw: 0 0
Used as bestpath: n/a 0
Used as multipath: n/a 0
Outbound Inbound
Local Policy Denied Prefixes: -------- -------
Total: 0 0
Number of NLRIs in the update sent: max 28, min 1
Address tracking is enabled, the RIB does have a route to 10.254.241.1
Connections established 5; dropped 5
Last reset 18:57:36, due to BGP Notification received, open: unknown subcode
Transport(tcp) path-mtu-discovery is enabled
BGP configuration:
router bgp 64710
no synchronization
bgp log-neighbor-changes
network 10.220.255.24 mask 255.255.255.248
network 10.254.241.0 mask 255.255.255.252
redistribute eigrp 9000 route-map EIGRP-TO-BGP
neighbor 10.254.241.1 remote-as 2856
neighbor 10.254.241.1 description Peer to BT PE
neighbor 10.254.241.1 soft-reconfiguration inbound
no auto-summary
route-map EIGRP-TO-BGP permit 10
match ip address prefix-list EIGRP-TO-BGP
ip prefix-list EIGRP-TO-BGP seq 100 permit 10.160.0.0/16 le 24
ip prefix-list EIGRP-TO-BGP seq 120 permit 10.129.0.0/16 le 24
ip prefix-list EIGRP-TO-BGP seq 140 permit 10.220.0.0/16 le 24
Any idea why the BGP is not establishing?
Thanks,
Kiran
02-01-2017 03:44 AM
GB-LDC-MPLS01#sh ver
Cisco IOS Software, 7301 Software (C7301-ADVIPSERVICESK9-M), Version 12.4(24)T8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Sun 09-Sep-12 07:23 by prod_rel_team
ROM: System Bootstrap, Version 12.3(4r)T4, RELEASE SOFTWARE (fc1)
BOOTLDR: Cisco IOS Software, 7301 Software (C7301-BOOT-M), Version 12.4(24)T8, RELEASE SOFTWARE (fc1)
GB-LDC-MPLS01 uptime is 4 days, 16 hours, 37 minutes
System returned to ROM by reload at 19:03:57 UTC Fri Jan 27 2017
System restarted at 19:06:04 UTC Fri Jan 27 2017
System image file is "disk0:c7301-advipservicesk9-mz.124-24.T8.bin"
Last reload reason: Reload Command
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 7301 (NPE) processor (revision F) with 491520K/32768K bytes of memory.
Processor board ID 74858976
SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache
1 slot midplane, Version 2.0
02-01-2017 04:59 AM
I have now upgraded the router to ADV-ENT-15.2(4)S7 and I get a slightly different message now.
Cisco IOS Software, 7301 Software (C7301-ADVENTERPRISEK9-M), Version 15.2(4)S7
Feb 1 12:42:10.254 UTC: %BGP-3-NOTIFICATION: received from neighbor 10.254.241.1 active 2/8 (no supported AFI/SAFI) 3 bytes 000101 (timer expired)
12-14-2018 07:28 PM
12-14-2018 08:00 PM
Hello
Can you try turning off the capabilities check
Neighbour y.y.y.y dont-capability-negotiate
12-14-2018 09:25 PM
12-15-2018 05:12 AM
Hello
possible bug? -here
12-15-2018 08:06 AM
Has this BGP worked before and then stopped working? Or is this a new install of BGP?
I wonder about this part of the notification
received from neighbor y.y.y.y active 2/2 (peer in wrong AS) 0 bytes
Perhaps the poster can run debug for bop and post the debug output?
HTH
Rick
12-15-2018 08:52 AM
12-15-2018 12:30 PM
Your cisco received the notification from juniper. So juniper is complaining about something. Can you check the logs on juniper and see if there are any messages that relate to this?
I still believe that running debug for bgp and posting the output might shed light on this. It might also be helpful if you would post the configuration on cisco.
HTH
Rick
12-15-2018 12:50 PM
12-15-2018 12:56 PM
It is unfortunate that running debug is not a possibility. So we will need to find other ways to investigate this. As a starting point could you post the config of the cisco?
It might also be helpful if you would post from the cisco the output of these commands
show ip bgp
show ip bop neighbor
and the output of similar commands on the juniper.
HTH
Rick
12-15-2018 08:50 PM
12-17-2018 06:11 AM
In the first post from the current poster the cisco was receiving notifications sent from Juniper. In the recent post the cisco is generating notifications. So sometimes the notifications are generated from Juniper and sometimes generated from cisco. This makes me wonder if it is a question of which device initiates the request. And it certainly suggests that there is a significant mismatch between the devices. We have seen the config from the cisco. Perhaps we could see the config from Juniper?
HTH
Rick
12-15-2018 01:02 PM
Hello
RIB does have a route to 10.254.241.1
Connections established 5; dropped 5
Do you have reachability to this peer?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide