BGP Routes After Policy Application

The following example shows the routes in the BGP (Border Gateway Protocol) routing table at Router A after applying the custFilter inbound policy:

* Switch.127 # show bgp routes address-family ipv6-unicast all
Routes:
Destination                                 LPref Weight MED
Peer                                     Next-Hop
AS-Path
-------------------------------------------------------------------------
*>i  2001:db8:4001::/48                          100   1      100
2001:db8:2000::2                         2001:db8:2000::2
1100 5623
*>i  2001:db8:4002::/48                          100   1      100
2001:db8:2000::2                         2001:db8:2000::2
1100 5623
*>i  2001:db8:4003::/48                          100   1      100
2001:db8:2000::2                         2001:db8:2000::2
1100 5623
*>i  2001:db8:5030::/48                          100   1      100
2001:db8:2000::2                         2001:db8:2000::2
1100 4977
*>i  2001:db8:5031::/48                          100   1      100
2001:db8:2000::2                         2001:db8:2000::2
1100 4977
Flags: (*) Preferred BGP route, (>) Active, (d) Suppressed, (h) History
(s) Stale, (m) Multipath, (u) Unfeasible
Origin: (?) Incomplete, (e) EGP, (i) IGP
BGP Route Statistics
Total Rxed Routes : 6
Feasible Routes   : 5
Active Routes     : 5
Rejected Routes   : 1
Unfeasible Routes : 0
Route Statistics on Session Type
Routes from Int Peer: 0
Routes from Ext Peer: 5

Route 2001:db8:a004::/48 is not present in the BGP routing table shown above.

The routes were updated because soft-reset is configured for this neighbor.

The following command examples show that the denied routes are not transmitted to the neighbors:

* Switch.130 # show bgp neighbor 2001:db8:3000::2 address-family ipv6-unicast transmitted-routes all
Advertised Routes:
Destination                                 LPref Weight MED
Peer                                     Next-Hop
AS-Path
-------------------------------------------------------------------------
>i  2001:db8:4001::/48                          0            100
2001:db8:3000::1
2100 1100 5623
>i  2001:db8:4002::/48                          0            100
2001:db8:3000::1
2100 1100 5623
>i  2001:db8:4003::/48                          0            100
2001:db8:3000::1
2100 1100 5623
>i  2001:db8:5030::/48                          0            100
2001:db8:3000::1
2100 1100 4977
>i  2001:db8:5031::/48                          0            100
2001:db8:3000::1
2100 1100 4977
Flags: (*) Preferred BGP route, (>) Active, (d) Suppressed, (h) History
(s) Stale, (m) Multipath, (u) Unfeasible
Origin: (?) Incomplete, (e) EGP, (i) IGP
BGP Route Statistics
Advertised Routes : 5

The next example shows another way to see that the MED values are set as defined in the policy.

* Switch.131 # show bgp neighbor 2001:db8:3000::2 address-family ipv6-unicast transmitted-routes detail all
Advertised Routes:
Route: 2001:db8:4001::/48, Active
Origin IGP, Next-Hop 2001:db8:3000::1, MED 100
As-PATH: 2100 1100 5623
Route: 2001:db8:4002::/48, Active
Origin IGP, Next-Hop 2001:db8:3000::1, MED 100
As-PATH: 2100 1100 5623
Route: 2001:db8:4003::/48, Active
Origin IGP, Next-Hop 2001:db8:3000::1, MED 100
As-PATH: 2100 1100 5623
Route: 2001:db8:5030::/48, Active
Origin IGP, Next-Hop 2001:db8:3000::1, MED 100
As-PATH: 2100 1100 4977
Route: 2001:db8:5031::/48, Active
Origin IGP, Next-Hop 2001:db8:3000::1, MED 100
As-PATH: 2100 1100 4977
BGP Route Statistics
Advertised Routes : 5