show run | begin bgp
show ip bgpShows BGP table
sho ip bgp summary
sho ip bgp all sum | i <IP ADDRESS>
show bgp ipv4 unicast summary
show bgp vpnv4 unicast all summary
show bgp vpnv4 unicast all
show bgp vpnv4 unicast rd <route distinguisher/prefix>
show bgp ipv6 unicast <ipv6 address>
clear ip bgp * To reset bgp sessions – for lab sims…i.e. don't do this in production environment!
show ip bgp vpnv4 vrf <VRF NAME> summary
show ip bgp neighbors <NEIGHBOR IP>
show ip bgp vpnv4 vrf <VRF NAME> neighbors <NEIGHBOR IP> routes
show ip bgp vpnv4 vrf <VRF NAME> neighbors <NEIGHBOR IP> received-routes
show ip bgp vpnv4 vrf <VRF NAME> neighbors <NEIGHBOR IP> advertised-routes

IOS XR

show bgp vrf <VRF NAME> summary
show bgp vrf <VRF NAME> neighbor <NEIGHBOR IP> routes
show bgp vrf <VRF NAME> neighbor <NEIGHBOR IP> advertised-routes

BGP Local-AS

Let’s assume a member would like to use BGP as number 65111 which is already in use by a different member. In this case Deutsche Boerse will assign a free AS number to that member (in our example 65200) If the member is not willing to use the free AS number he has to use bgp local-as, no-prepend and replace-as.

BGP “local-as” only

The configuration will look like this:

TF-RMIL0115 (AP POP router)

router bgp 12625

!

address-family ipv4 vrf M_65200

neighbor 10.20.100.38 remote-as 65200

neighbor 10.20.100.38 activate

neighbor 10.20.100.38 prefix-list trading_networks_A out

neighbor 10.20.100.38 route-map trading_member_in in

neighbor 10.20.100.38 maximum-prefix 20

!

R004446 (member router)

router bgp 65111

address-family ipv4 vrf M_65111

neighbor 10.20.100.37 remote-as 12625

neighbor 10.20.100.37 local-as 65200

The “Local-as” and “real” as numbers are visible within the AS PATH. The BGP tables will look like this:

TF-R004446#sh ip bgp vpnv4 vrf M_65111

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 0.0.0.0 0 32768 i
* 193.29.91.64/27 10.20.100.37 0 65200 12625 i

TF-RMIL0115#sh ip bgp vpnv4 vrf M_65200

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 10.20.100.38 0 0 65200 65111 i
*>i193.29.91.64/27 10.79.1.15 0 100 0 i

BGP “local-as” + “no-prepend”

The configuration on the POP router will not change. The configuration on the member router will look like this:

TF-R004446#

router bgp 65111

address-family ipv4 vrf M_65111

neighbor 10.20.100.37 remote-as 12625

neighbor 10.20.100.37 local-as 65200 no-prepend

The local as number on member end will disappear from the AS PATH. The BGP table will look like this:

TF-R004446#sh ip bgp vpnv4 vrf M_65111

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 0.0.0.0 0 32768 i
* 193.29.91.64/27 10.20.100.37 0 12625 i

TF-RMIL0115#sh ip bgp vpnv4 vrf M_65200

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 10.20.100.38 0 0 65200 65111 i
*> i 193.29.91.64/27 10.79.1.15 0 100 0 i

BGP “local-as” + “no-prepend” + “replace-as”

The configuration on the POP router will not change. The configuration on the member router will look like this:

TF-R004446#

router bgp 65111

address-family ipv4 vrf M_65111

neighbor 10.20.100.37 remote-as 12625

neighbor 10.20.100.37 local-as 65200 no-prepend replace-as

The members “real” as number on the POP router will disappear. The BGP tables will look like this:

TF-R004446#sh ip bgp vpnv4 vrf M_65111

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 0.0.0.0 0 32768 i
* 193.29.91.64/27 10.20.100.37 0 12625 i

TF-RMIL0115#sh ip bgp vpnv4 vrf M_65200

Network Next Hop Metric LocPrf Weight Path
*> 90.203.102.0/24 10.20.100.38 0 0 65200 i
*> i 193.29.91.64/27 10.79.1.15 0 100 0 i