In Border Gateway Protocol (BGP) routing, verifying route propagation is one of the most critical operational tasks for network engineers. Whether you are provisioning an Internet transit link, peering over an Internet Exchange Point (IXP), or deploying an internal MPLS/EVPN fabric, ensuring that your router announces only the intended prefixes—and strictly suppresses internal or unauthorized subnets—is essential for network stability and leak prevention.
On Cisco hardware, examining what is transmitted out of an interface requires inspecting the local BGP database after all outbound policies have been applied. This guide covers how to inspect advertised routes across Cisco IOS, IOS-XE, NX-OS, and IOS-XR platforms, explores the architectural difference between BGP route tables, troubleshoots why prefixes fail to advertise, and provides a quick-reference CLI cheat sheet.
Table of Contents
Verifying Advertised Routes in Cisco IOS and IOS-XE
In traditional Cisco IOS and modern IOS-XE environments, inspecting the prefixes advertised to a remote peer follows a clear, three-step operational workflow.
Step 1: Verify the BGP Neighbor State
Before checking outbound routing updates, verify that the TCP peering session with the target neighbor is up and in the Established state.
Router# show ip bgp summary
Look at the State/PfxRcd column for your neighbor’s IP address. If it shows a number (even 0), the session is Established. If it displays states like Active, Idle, or Connect, BGP is down, and no routes are being actively exchanged.
Step 2: Execute the Outbound Route Command
To display all prefixes sent to a specific neighbor within the standard IPv4 Unicast address family, issue the primary operational command:
Router# show ip bgp neighbors 192.0.2.2 advertised-routes
For environments utilizing modern BGP address-family configurations, the protocol-agnostic syntax is preferred:
Router# show bgp ipv4 unicast neighbors 192.0.2.2 advertised-routes
For an IPv6 peer, adjust the address family accordingly:
Router# show bgp ipv6 unicast neighbors 2001:db8:1::2 advertised-routes
Step 3: Interpret the Command Output
The output reveals the exact prefix list being pushed out to the neighbor interface:
Router# show ip bgp neighbors 192.0.2.2 advertised-routes
BGP table version is 24, 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 0.0.0.0 0 32768 i
*> 172.16.1.0/24 0.0.0.0 0 32768 i
*> 192.0.2.128/25 192.168.1.1 0 32768 64512 i
Total number of prefixes 3
Key output indicators include:
* *> (Valid and Best): Only routes flagged as valid (*) and selected as the best path (>) are eligible for transmission to BGP peers.
* Next Hop: For locally injected routes (e.g., via a network statement), the next hop generally appears as 0.0.0.0 locally, but BGP rewrites this to the router’s local peering IP when sending out to an external peer (eBGP).
* Path: Displays the AS_PATH string prepended before sending. If announcing local prefixes, only the origin code (i) appears.
BGP RIB Architecture: Advertised Routes vs. Received Routes vs. BGP Table
To properly interpret what you see on the CLI, it helps to understand where the output originates within the BGP Routing Information Base (RIB) processing pipeline. BGP maintains distinct logical databases for processing inbound, local, and outbound paths.
Peer Updates ---> [ Adj-RIB-In (Pre-Policy) ]
|
(Inbound Policy)
v
[ Adj-RIB-In (Post-Policy) ]
|
(Path Selection)
v
[ Loc-RIB ] ---> (Exported to IP Routing Table / FIB)
|
(Outbound Policy)
v
[ Adj-RIB-Out (Post-Policy) ] ---> Advertised to Peer
The table below contrasts the four primary BGP table verification commands and their architectural roles:
| Criterion | show ip bgp neighbors <ip> advertised-routes | show ip bgp neighbors <ip> received-routes | show ip bgp neighbors <ip> routes | show ip bgp |
|---|---|---|---|---|
| BGP RIB Stage | Adj-RIB-Out | Adj-RIB-In (Pre-Policy) | Adj-RIB-In (Post-Policy) | Loc-RIB |
| Direction | Outbound | Inbound | Inbound | Local Routing Database |
| Policy State | After outbound route-maps, prefix-lists, and AS-path prepending are evaluated. | Raw prefixes delivered by peer prior to applying any inbound filtering. | Filtered prefixes accepted from the peer after inbound policy evaluation. | Global BGP table containing all known paths from all neighbors and local injection. |
| Prerequisites | Peering session in Established state. | Requires neighbor <ip> soft-reconfiguration inbound enabled in BGP config. | Peering session in Established state. | Active BGP routing process. |
| Memory Impact | Negligible (calculated dynamically from Loc-RIB via outbound filter). | Significant (stores duplicate pre-policy copy of peer table in RAM). | Standard BGP path storage in main BGP table. | Standard BGP path storage. |
| Primary Operational Purpose | Confirm which routes are leaving the router toward a specific neighbor. | Audit what a peer is sending before your local policies discard or modify paths. | Verify which routes from a specific peer survived inbound filtering. | Evaluate overall path selection, tie-breakers, and internal next-hop validity. |
Cisco Command Reference: show ip bgp neighbors advertised-routes
Syntax Description
show ip bgp [address-family] neighbors {ip-address | peer-group-name} advertised-routes
show bgp [ipv4 | ipv6] [unicast | multicast] neighbors {ip-address} advertised-routes
Command Modes
- Privileged EXEC (
Router#)
Parameter Definitions
address-family: (Optional) Designates the specific routing table instance to inspect (e.g.,ipv4 unicast,ipv6 unicast,vpnv4). Defaults to IPv4 Unicast if omitted on traditional IOS.ip-address: The IPv4 or IPv6 address of the target BGP neighbor.peer-group-name: The configured name of a BGP peer-group. Displays combined outbound advertisements applied to all group members.advertised-routes: Instructs the BGP process to run the Loc-RIB against the neighbor’s configured outbound policy and output the resulting prefix set.
Behavioral and Compatibility Notes
- Soft Reconfiguration: Unlike
show ip bgp neighbors received-routes, this command does not requireneighbor soft-reconfiguration inboundor any outbound caching commands. It processes the Loc-RIB dynamically against the active outbound policy chain. - Outbound Policy Processing: Prefixes denied by an outbound route-map, prefix-list, distribute-list, or community-filter are excluded from this output.
- Platform Support: Available in Cisco IOS Software Release 11.1 and later; all releases of Cisco IOS-XE (16.x, 17.x); Cisco NX-OS Release 4.0 and later; Cisco IOS-XR Release 3.0 and later.
Verifying Advertised Routes in Cisco NX-OS and IOS-XR
Modern data center and service provider platforms depart from traditional IOS conventions by enforcing strict address-family hierarchies and modular routing architectures.
Cisco NX-OS (Nexus Platforms)
Nexus switches running NX-OS require explicit specification of address families and Virtual Routing and Forwarding (VRF) instances.
Step 1: Check Global Table Advertisements
switch# show bgp ipv4 unicast neighbors 10.1.1.2 advertised-routes
Step 2: Check VRF-Specific Advertisements
If your BGP session resides inside a non-default VRF (such as an EVPN tenant or customer VRF):
switch# show bgp ipv4 unicast neighbors 10.1.1.2 advertised-routes vrf PROD_A
Step 3: Interpret NX-OS Output
switch# show bgp ipv4 unicast neighbors 10.1.1.2 advertised-routes vrf PROD_A
Peer: 10.1.1.2, Address Family: IPv4 Unicast
BGP table version is 112, local router ID is 10.255.255.1
Status: s-suppressed, x-deleted, S-stale, d-damped, h-history, *-valid, >-best
Network Next Hop Metric LocPrf Weight Path
*> 10.200.1.0/24 10.1.1.1 0 100 0 i
*> 10.200.2.0/24 10.1.1.1 0 100 0 i
Total number of prefixes: 2
Cisco IOS-XR (ASR 9000, NCS Platforms)
Cisco IOS-XR utilizes a microkernel architecture where all BGP routing policies are implemented via Routing Policy Language (RPL). Under IOS-XR, BGP enforces a default-deny model: unless an explicit inbound and outbound route-policy is configured, no prefixes are accepted or advertised.
Step 1: Execute the Address-Family Command
RP/0/RSP0/CPU0:Router# show bgp ipv4 unicast neighbors 192.168.10.1 advertised-routes
Step 2: Inspect Multi-VRF Environments
RP/0/RSP0/CPU0:Router# show bgp vrf TENANT-1 ipv4 unicast neighbors 192.168.10.1 advertised-routes
Step 3: Verify Policy Attachment
If the command output is blank on IOS-XR, verify that an outbound policy permitting prefixes exists on the neighbor configuration:
RP/0/RSP0/CPU0:Router# show running-config router bgp 65000 neighbor 192.168.10.1
Ensure the block contains a valid route-policy <NAME> out statement.
Troubleshooting Empty or Missing BGP Advertised Routes
When show ip bgp neighbors <ip> advertised-routes returns empty or omits expected prefixes, use this checklist to diagnose the underlying cause.
Why is the advertised routes output completely blank?
An empty output typically points to one of three baseline issues:
1. Peering Down: The neighbor session is not in the Established state. Verify with show ip bgp summary.
2. No Best Path Available: BGP only advertises valid, best paths (*>). If the prefix in your BGP table has an unreachable next hop or a RIB failure flag (r), it will not be advertised.
3. Default Deny (IOS-XR): On Cisco IOS-XR, omitting an outbound route-policy prevents any routes from being advertised.
Why is a locally configured prefix not being announced?
If you have configured a network statement under router bgp (e.g., network 10.10.0.0 mask 255.255.0.0), but it does not appear in your advertised routes:
* Exact Match in RIB Required: BGP will not generate a route via the network command unless the exact prefix and subnet mask already exist in the router’s main routing table (show ip route). If your IGP only has individual /24 subnets, a /16 network statement will fail silently. Add a matching static route to Null0 or inject the specific /24 subnets.
How do outbound route-maps or prefix-lists filter advertisements?
BGP evaluates outbound policies sequentially. If an outbound route-map or prefix-list is applied to the neighbor:
* Verify policy assignment: show running-config | section router bgp
* Locate: neighbor <ip> route-map <MAP_NAME> out
* Inspect the map: show route-map <MAP_NAME>
* Remember that route-maps and prefix-lists contain an implicit deny at the end. Any prefix not explicitly matched by a permit statement is dropped.
Why are iBGP-learned routes not being advertised to other iBGP peers?
Under the standard BGP Split-Horizon Rule, a BGP router will never advertise a prefix learned from an internal BGP (iBGP) peer to another iBGP peer. This rule prevents loops in the absence of AS_PATH changes.
* Solution: To propagate iBGP routes to internal peers, configure a Route Reflector (neighbor <ip> route-reflector-client) or establish a full mesh of iBGP peerings.
Does BGP route dampening or conditional advertisement suppress routes?
- Flapping / Dampening: If a route flaps frequently, BGP route flap dampening marks it with
d(damped) orh(history), suppressing advertisement until the reuse threshold expires. Check withshow ip bgp dampened-paths. - Conditional Injection: If using
neighbor <ip> advertise-map <MAP> non-exist-map <MAP>, the route will only be advertised if the monitored prefix vanishes from the BGP table.
Cisco BGP Route Verification Command Cheat Sheet
Use the templates below as a quick operational reference across platforms.
================================================================================
CISCO IOS / IOS-XE BGP VERIFICATION TEMPLATE
================================================================================
! 1. Check Peering Health & Session State
show ip bgp summary
show bgp all summary
! 2. Check Outbound Advertised Routes (Adj-RIB-Out)
show ip bgp neighbors <NEIGHBOR_IP> advertised-routes
show bgp ipv4 unicast neighbors <NEIGHBOR_IP> advertised-routes
show bgp ipv6 unicast neighbors <NEIGHBOR_IPV6> advertised-routes
! 3. Check Inbound Accepted Routes (Adj-RIB-In, Post-Policy)
show ip bgp neighbors <NEIGHBOR_IP> routes
! 4. Check Raw Inbound Received Routes (Adj-RIB-In, Pre-Policy)
! Note: Requires 'neighbor <NEIGHBOR_IP> soft-reconfiguration inbound'
show ip bgp neighbors <NEIGHBOR_IP> received-routes
! 5. Inspect Policy Filtering
show ip bgp <PREFIX> <MASK>
show route-map <ROUTE_MAP_NAME>
show ip prefix-list <PREFIX_LIST_NAME>
================================================================================
CISCO NX-OS (NEXUS) VERIFICATION TEMPLATE
================================================================================
! Check Neighbor State (Global & VRF)
show bgp sessions [vrf <VRF_NAME>]
! Check Advertised Routes
show bgp ipv4 unicast neighbors <NEIGHBOR_IP> advertised-routes [vrf <VRF_NAME>]
show bgp ipv6 unicast neighbors <NEIGHBOR_IPV6> advertised-routes [vrf <VRF_NAME>]
! Check Filtered Inbound Paths
show bgp ipv4 unicast neighbors <NEIGHBOR_IP> routes [vrf <VRF_NAME>]
================================================================================
CISCO IOS-XR VERIFICATION TEMPLATE
================================================================================
! Check Neighbor State
show bgp summary [vrf <VRF_NAME>]
! Check Advertised Routes
show bgp ipv4 unicast neighbors <NEIGHBOR_IP> advertised-routes
show bgp vrf <VRF_NAME> ipv4 unicast neighbors <NEIGHBOR_IP> advertised-routes
! Verify Outbound RPL Configuration
show rpl route-policy <POLICY_NAME>
Summary
Checking advertised BGP routes on Cisco devices is centered on the show ip bgp neighbors <neighbor-ip> advertised-routes command (and its modern address-family equivalents). Because this command evaluates the outbound policy against your active Loc-RIB, it gives you an exact view of the Adj-RIB-Out table. When prefixes fail to appear, systematically verify session states, ensure exact prefix matches exist in the local IP routing table, validate iBGP split-horizon behavior, and audit outbound route-maps for implicit deny statements. Incorporating these verification steps into your maintenance and deployment workflows helps maintain clean routing tables and avoids accidental route leaks.











Comments