Professional Documents
Culture Documents
Adj-RIBs-In Raw NLRI / PA information received from peers Loc-RIB The best NLRIs after route policies have been applied Adj-RIBs-Out Routes BGP will advertise to other BGP peers
Redistribution Redistributed
YES NVRAM
up
up
R1#show ip route 1.1.1.1 Routing entry for 1.1.1.1/32 Known via "connected", distance 0, metric 0 (connected, via interface) R1#sh run | section bgp router bgp 65123 network 1.1.1.1 mask 255.255.255.255
Auto Summarization
auto-summary summarizes prefixes added to BGP at classful boundaries The behavior is different depending on if the prefixes were added with the network command or through redistribution The default is no auto-summary since IOS 12.3
Redistribution Redistribute only the classful network Network Command Inject more specific and summary
Well-known
mandatory discretionary
Optional
transitive nontransitive
Path Attributes
Attribute ORIGIN AS_PATH NEXT_HOP LOCAL_PREF ATOMIC_AGGREGATE AGGREGATOR COMMUNITY MULTI_EXIT_DISC ORIGINATOR_ID CLUSTER_LIST Class well-known mandatory well-known mandatory well-known mandatory well-known discretionary well-known discretionary optional transitive optional transitive optional nontransitive optional nontransitive optional nontransitive
IGP (i)
Prefix was learned internal to the AS Prefixes added to BGP with the network command
EGP (e)
Prefix was learned via EGP
Incomplete (?)
Prefix was learned through some other method Redistributed routes have an origin of incomplete
32768 i
R1#show ip bgp 1.1.1.1 | b Origin Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced, local, best R1#show ip bgp | i 10.0.45.0 *>i10.0.45.0/30 2.2.2.2 0 100 0 65004 ?
R1#show ip bgp 10.0.45.0 | b Origin Origin incomplete, metric 0, localpref 100, valid, internal, best
AS_SET
Unordered set of AS numbers enclosed in { } Used when prefixes have been aggregated
AS_CONFED_SEQUENCE
Similar to AS_SEQ but used in confederations
AS_CONFED_SET
Similar to AS_SET but used in confederations
0 0 0 0
Router#sh ip bgp 10.64.0.0 BGP routing table entry for 10.64.0.0/16, version 2698 Paths: (1 available, best #1, table default) Advertised to update-groups: 1 2 Refresh Epoch 1 13979 21326 4809 65103, (aggregated by 65103 192.168.101.3) 192.168.100.161 from 192.168.100.161 (12.123.71.116) Origin IGP, localpref 500, valid, external, atomic-aggregate, best Community: 13979:5000
Configuring LOCAL_PREF
ip prefix-list PREFER_ME_PLEASE permit 1.1.1.1/32 ! route-map SET_LOCAL_PREF permit 10 match ip address prefix-list PREFER_ME_PLEASE set local-preference 500 ! router bgp 65123 neighbor 10.0.45.1 route-map SET_LOCAL_PREF in ! R5#sh ip bgp 1.1.1.1 BGP routing table entry for 1.1.1.1/32, version 183 Paths: (2 available, best #2, table Default-IP-Routing-Table) Advertised to update-groups: 2 65004 65123 6.6.6.6 (metric 156160) from 6.6.6.6 (6.6.6.6) Origin IGP, metric 0, localpref 100, valid, internal 65004 65123 10.0.45.1 from 10.0.45.1 (172.16.46.193) Origin IGP, localpref 500, valid, external, best
Configuring MED
ip prefix-list PREFER_ME_PLEASE permit 1.1.1.1/32 ! route-map SET_MED permit 10 match ip address prefix-list PREFER_ME_PLEASE set metric 50 ! route-map SET_MED permit 20 set metric 100 ! router bgp 65123 neighbor 10.0.45.1 route-map SET_MED out ! R5#sh ip bgp 1.1.1.1 BGP routing table entry for 1.1.1.1/32, version 183 Paths: (2 available, best #2, table Default-IP-Routing-Table) Advertised to update-groups: 2 65004 65123 6.6.6.6 (metric 156160) from 6.6.6.6 (6.6.6.6) Origin IGP, metric 50, localpref 100, valid, internal 65004 65123 10.0.45.1 from 10.0.45.1 (172.16.46.193) Origin IGP, localpref 500, valid, external, best
Signals to receiving routers that AS_PATH information has been lost A router that receives a prefix with ATOMIC_AGGREGATE set cannot advertise a more specific prefix of the aggregate, and must keep ATOMIC_AGGREGATE set on updates
100 100
router bgp 65056 aggregate-address 172.16.56.0 255.255.255.0 summary-only R5#sh ip bgp | i 172.16.56 s> 172.16.56.0/26 0.0.0.0 *> 172.16.56.0/24 0.0.0.0 s> 172.16.56.64/26 0.0.0.0 s>i172.16.56.128/26 6.6.6.6 s>i172.16.56.192/26 6.6.6.6 0 0 0 0 100 100 32768 32768 32768 0 0 ? i ? ? ?
AS_SET
Due to AS_PATH information being lost during aggregation, routing loops are a possibility The AS_SET path attribute helps address this by placing an unordered list of all the AS from the more specific prefixes into AS_SET Additionally, AS_SEQ is still set to the aggregating routers AS No more need to set ATOMIC_AGGREGATE AS_SET is dynamic If more specific routes downstream fail, AS_SET can be updated on the fly, and those changes are advertised
Configuring AS_SET
RouterD# show ip bgp | b Network Network *> 160.0.0.0/8 Next Hop 4.4.4.1 Metric LocPrf Weight Path 0 300 {200,100} i
network 0.0.0.0
0.0.0.0/0 must already exist in the routing table
default-information originate
0.0.0.0/0 must already exist in the routing table Requires redistribution of 0.0.0.0/0 to work
neighbor default-originate
Unconditionally advertises 0.0.0.0/0 to a specific neighbor
Option 2: advertise-map
ip prefix-list MUST_EXIST permit 10.1.1.1/32 ip prefix-list DEFAULT_ROUTE permit 0.0.0.0/0 ! route-map MUST_EXIST permit 10 match ip address prefix-list MUST_EXIST ! route-map DEFAULT_ROUTE match ip address prefix-list DEFAULT_ROUTE ! router bgp 65123 neighbor 10.0.123.2 advertise-map DEFAULT_ROUTE exist-map MUST_EXIST