When troubleshooting Border Gateway Protocol (BGP) relationships on Cisco hardware, network engineers frequently need to determine whether a remote peer is advertising a specific prefix. While a route may not appear in the active BGP table or the local routing information base (RIB), it might still be arriving at the interface and getting filtered out by an inbound route-map, prefix-list, or AS-path filter.
To isolate filtering issues and verify raw inbound routing updates, Cisco provides commands to inspect incoming BGP announcements. This guide covers how to inspect received BGP routes across Cisco IOS, IOS-XE, NX-OS, and IOS-XR platforms, clarifies the distinction between pre-policy and post-policy tables, addresses common CLI errors, and provides ready-to-use configuration templates.
Table of Contents
BGP Route Inspection: received-routes vs. routes
Before issuing verification commands, it is essential to distinguish between pre-policy and post-policy BGP tables. Cisco routers process incoming network advertisements through an ingress policy pipeline, sorting entries across distinct stages of the Routing Information Base (Adj-RIB-In and Loc-RIB).
The following comparison outlines the operational differences between the received-routes and routes keywords:
| Feature / Criterion | show ip bgp neighbors <IP> received-routes | show ip bgp neighbors <IP> routes |
|---|---|---|
| Routing Phase | Pre-policy (raw inbound updates) | Post-policy (filtered updates) |
| BGP Table Location | Stored in the unedited Adj-RIB-In table. | Processed into the local BGP table (Loc-RIB). |
| Policy Impact | Displays routes before inbound route-maps, prefix-lists, or distribute-lists are applied. | Displays only routes that have passed all inbound policy filters. |
| Filtered Routes | Visible (including denied and discarded prefixes). | Hidden (denied routes are suppressed). |
| Memory Overhead | Requires local storage of unmodified paths via soft reconfiguration. | No additional memory overhead required. |
| Primary Use Case | Diagnosing whether a peer is sending a route that is being dropped by local policy. | Verifying which routes from a peer were accepted and are candidates for the routing table. |
Understanding this distinction clarifies why a prefix might appear under received-routes but remain absent from routes: inbound policy rejected the prefix.
How to Check Received Routes in Cisco IOS and IOS-XE
In standard Cisco IOS and IOS-XE deployments, inspecting pre-policy prefixes requires querying the specific neighbor’s inbound table. Follow this step-by-step workflow to verify received advertisements.
Step 1: Identify the Target BGP Neighbor
Determine the operational state and IP address of your BGP neighbor:
Router# show ip bgp summary
Verify that the neighbor relationship shows an established state and displays a numeric prefix counter under the State/PfxRcd column.
Step 2: Query Pre-Policy Advertisements
To view all raw prefixes advertised by the neighbor before inbound filters are applied, run:
Router# show ip bgp neighbors 192.0.2.1 received-routes
Step 3: Interpret the Command Output
The output displays the BGP table entries received directly from the peer:
BGP table version is 482, local router ID is 198.51.100.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
* 10.10.0.0/16 192.0.2.1 0 0 65001 65100 i
* 172.16.0.0/12 192.0.2.1 0 0 65001 ?
- Valid marker (
*): Confirms the router received a well-formed BGP update. - Next Hop: Indicates the gateway advertised by the peer.
- Path: Displays the autonomous system path traversed before reaching your router.
Step 4: Filter Output for Specific Prefixes
When peering with an upstream transit provider sending full internet routing tables, narrow the output to a specific prefix:
Router# show ip bgp neighbors 192.0.2.1 received-routes 10.10.0.0/16
Alternatively, use regular expressions or pipe filters to find specific AS paths or subnets:
Router# show ip bgp neighbors 192.0.2.1 received-routes | include 10.10.
Troubleshooting: “Inbound Soft Reconfiguration Not Enabled”
When running show ip bgp neighbors <IP> received-routes, Cisco IOS and IOS-XE routers often return the following error message:
% Inbound soft reconfiguration not enabled on neighbor 192.0.2.1
Below are common operational questions and solutions associated with this error.
Why does this error occur?
By default, Cisco IOS and IOS-XE do not retain raw, pre-policy routing updates in memory. When a BGP update arrives, the router applies inbound policies (such as route-maps), places accepted routes into the BGP table, and discards the original advertisement to conserve RAM. Because the unmodified Adj-RIB-In is discarded, the router has no raw data to show when prompted for received-routes.
Does BGP Route Refresh eliminate the need for this command?
Not entirely. The BGP Route Refresh capability (RFC 2918) allows routers to request fresh routing updates dynamically from a peer using the command clear ip bgp <IP> in. While Route Refresh enables non-disruptive policy changes without dropping BGP sessions, it still applies filters on the fly and discards the raw input. If you need to view raw pre-policy updates at any time, inbound soft reconfiguration must be explicitly enabled.
What are the memory implications of enabling soft reconfiguration?
Enabling inbound soft reconfiguration instructs the router to store two copies of every prefix advertised by that neighbor: the pre-policy update and the accepted post-policy update. For small-to-medium peering sessions, the memory footprint is negligible. However, on edge routers receiving full internet routing tables (over 900,000 routes per peer), enabling this command can consume hundreds of megabytes of additional control-plane RAM per neighbor.
Configuration Templates: Enabling Inbound Soft Reconfiguration
To enable inspection of pre-policy routes, configure the soft-reconfiguration inbound parameter under the BGP process. Below are production-ready configuration snippets.
Classic Cisco IOS (Global BGP Process)
Use this configuration for legacy Cisco IOS deployments running traditional IPv4 unicast routing:
router bgp 65000
neighbor 192.0.2.1 remote-as 65001
neighbor 192.0.2.1 soft-reconfiguration inbound
end
Cisco IOS-XE (Address-Family Configuration)
Modern IOS-XE configurations isolate neighbors within specific address families (IPv4, IPv6, or VRF instances):
router bgp 65000
neighbor 192.0.2.1 remote-as 65001
!
address-family ipv4 unicast
neighbor 192.0.2.1 activate
neighbor 192.0.2.1 soft-reconfiguration inbound
exit-address-family
!
address-family ipv6 unicast
neighbor 2001:db8::1 remote-as 65001
neighbor 2001:db8::1 activate
neighbor 2001:db8::1 soft-reconfiguration inbound
exit-address-family
end
VRF-Aware BGP Template
For enterprise WAN and MPLS deployments utilizing Virtual Routing and Forwarding (VRF):
router bgp 65000
address-family ipv4 vrf CUSTOMER_A
neighbor 10.255.1.2 remote-as 65100
neighbor 10.255.1.2 activate
neighbor 10.255.1.2 soft-reconfiguration inbound
exit-address-family
end
Note: After applying these commands, the router will store all future inbound updates from the specified neighbor. To populate the table immediately without resetting the peering session, run clear ip bgp <neighbor-ip> in.
Checking Received Routes in Cisco NX-OS and IOS-XR
Data center and carrier-grade operating systems handle BGP updates with different command syntax and default behaviors compared to standard IOS.
Cisco NX-OS (Nexus Switches)
Cisco NX-OS requires explicit Address Family Identifier (AFI) keywords in its verification commands.
Verify Neighbor Status:
text
switch# show bgp ipv4 unicast summaryCheck Received Routes (Pre-Policy):
text
switch# show bgp ipv4 unicast neighbors 192.0.2.1 received-routesCheck Accepted Routes (Post-Policy):
text
switch# show bgp ipv4 unicast neighbors 192.0.2.1 routes
NX-OS Behavior Note: Similar to IOS, if soft reconfiguration is not enabled, NX-OS will reject the command unless soft-reconfiguration inbound always is configured globally or on the neighbor under the BGP address family.
Cisco IOS-XR (Carrier Routing Platforms)
Cisco IOS-XR features a modular control-plane architecture. By default, IOS-XR can store pre-policy route information when configured, but its command syntax conforms to a strict hierarchical structure:
Check Received Routes (Pre-Policy):
text
RP/0/RSP0/CPU0:Router# show bgp ipv4 unicast neighbors 192.0.2.1 received-routesInspect Received Routes for IPv6:
text
RP/0/RSP0/CPU0:Router# show bgp ipv6 unicast neighbors 2001:db8::1 received-routesInspect Routes with Detail:
To view extended path attributes, communities, and MED for unedited received routes:
text
RP/0/RSP0/CPU0:Router# show bgp ipv4 unicast neighbors 192.0.2.1 received-routes detail
Cisco Command Reference: show ip bgp neighbors Suite
The following reference table documents the syntax, operational modes, and parameters for the BGP verification command suite across Cisco IOS and IOS-XE platforms.
Command Syntax
show ip bgp neighbors [ip-address] [received-routes | routes | advertised-routes]
Parameter Reference
ip-address: Specifies the IPv4 or IPv6 address of the target BGP neighbor.received-routes: Displays all received BGP routes (pre-policy) from the specified neighbor. Requiressoft-reconfiguration inbound.routes: Displays all accepted BGP routes (post-policy) received from the specified neighbor that survived ingress filtering.advertised-routes: Displays all BGP routes currently sent to the specified neighbor after outbound policies have been evaluated.
Command Specifications
- Command Mode: User EXEC (
>), Privileged EXEC (#) - Privilege Level: Level 1 (Read-Only)
- Hardware Scope: Cisco ISR, ASR, Catalyst 8000/9000, and legacy routing platforms.
- Standard Dependencies: Peer must be in the
Establishedstate. Prefixes will only be listed underreceived-routesif the session was refreshed or established afterneighbor soft-reconfiguration inboundwas applied.
Conclusion
Checking received BGP routes on Cisco devices is a fundamental troubleshooting technique for resolving routing discrepancies and validating filter configurations. By using received-routes, engineers can verify the raw, pre-policy advertisements sent by an external peer, whereas routes displays what successfully passed local filtering. When working on memory-constrained devices or handling full internet routing tables, consider the RAM requirements of inbound soft reconfiguration before enabling it permanently across all peers.











Comments