Term
|
Definition
1. OPEN - Starts the BGP session 2. KEEPALIVE - Maintains the BGP session 3. UPDATE: Network Reachability Exchanges 4. NOTIFICATION: A failure occured; close BGP session with Peer |
|
|
Term
|
Definition
1. NEIGHBOR TABLE: The connected BGP Peer sessions. 2. BGP TABLE: List of ALL BGP routes 3. ROUTING TABLE: List of the BEST routes injected from the BGP TABLE |
|
|
Term
|
Definition
TCP is used to create BGP Neighbor relationships. Specifically TCP port 179. |
|
|
Term
|
Definition
A collection of routers under one Authority. |
|
|
Term
Configure BGP Process in ASN 5500 |
|
Definition
|
|
Term
Configure BGP neighbor with a destination IP address of 10.1.45.1 and an AS of 5500 |
|
Definition
R1(conf)#router bgp 6500 R1(conf)#neighbor 10.1.45.1 remote-as 5500 |
|
|
Term
|
Definition
|
|
Term
Configure BGP Process to utilize loopback 0 interface for Neighbor relationship. |
|
Definition
R1(conf)#router bgp 6500 R1(conf)#neighbor 10.1.45.1 update-source loopback 0 |
|
|
Term
Configure BGP neighbors that are NOT directly connected |
|
Definition
R1(conf)#router bgp 6500 R1(conf)#neighbor 10.1.45.1 ebgp-multihop |
|
|
Term
What two ways get networks into the BGP Table? |
|
Definition
1. network configuration command 2. redistribution |
|
|
Term
|
Definition
* Valid network > Best route (which is installed in IP route table i Internal network h History network d Damped network s Surpressed network |
|
|
Term
|
Definition
|
|
Term
|
Definition
Do not use or advertise a route that has been learned via iBGP until the same route has been learned via the IGP |
|
|
Term
BGP Next-hop default processing |
|
Definition
1. eBGP Peers: change the next hop address on advertised routes. 2. iBGP Peers: DO NOT change next hop address on advertised routes |
|
|
Term
Configure iBGP Process to modify the next-hop address to it's own IP address for the next-hop for BGP routes advertised. ** Workaround for BGP Synchronization ** |
|
Definition
R1(conf)#router bgp 6500 R1(conf)#neighbor 10.1.45.1 next-hop-self |
|
|
Term
|
Definition
1. Well-Known - Every vendor supports 2. Optional - 3. Mandatory - MUST be in the UPDATE 4. Descretionary - 5. Transitive - Travel from AS to AS. 6. Non-Transitive - Stay within the Authorities AS |
|
|
Term
Well Known, Mandatory BGP Attributes |
|
Definition
1. Autonomous System Path 2. Next Hop Address 3. Origin |
|
|
Term
Well Known, Discretionary BGP Attirbutes |
|
Definition
1. Local Preference 2. Atomic Aggregate |
|
|
Term
|
Definition
0. Ignore routes with inaccessible next hop address 1. Prefer the path with the highest WEIGHT. 2. Prefer the path with the highest LOCAL_PREF 3. Prefer the path that was locally originated via a network command 4. Prefer the path with the shortest AS_PATH 5. Prefer the path with the lowest origin type. 6. Prefer the path with the lowest MED 7. Prefer eBGP paths over iBGP paths 8. Prefer the path with the lowest IGP metric to the BGP next hop. 9. Determine if multiple paths require installation in the routing table for BGP Multipath. 10. When both paths are external, prefer the one that was received first (oldest one) 11. Prefer the route that comes from the BGP router with the lowest Router ID 12. If the originator or router ID is the same for multiple paths, prefer the path with the minimum cluster list length. 13. Prefer the path that comes from the lowest neighbor address. |
|
|