The following section is a summary of the major points you should be aware of in this chapter.
Border Gateway Protocol Overview
- Border Gateway Protocol is a Path Vector protocol
- BGP is primarily used to exchange NLRI between routing domains or autonomous systems
- There are 4 (four) BGP processes that run when BGP is enabled in Cisco IOS-based devices:
- The BGP Open process
- The BGP I/O process
- The BGP Scanner process
- The BGP Router process
- The BGP Open process is used for peer establishment
- The BGP I/O process handles the reading, writing, and execution of BGP messages
- The BGP Scanner process periodically scans the BGP RIB
- The BGP Router process sends/receives routes, establishes peers, and interacts with the RIB
- There are three major components of the BGP Router process. These components are:
- The BGP Routing Information Base (RIB)
- The IP RIB for BGP-learned Prefixes
- The IP Switching Component for BGP-learned Prefixes
- In Cisco IOS software, BGP information is stored in one of two data structures or tables
- These two data structures or tables are the Neighbor Table and the BGP Table
- The Neighbor Table contains a list of all the configured neighbors of the local BGP speaker
- The BGP Table or BGP Routing Information Base (RIB) contains all BGP routes
- All Border Gateway Protocol messages all share a common header which is 19-bytes long
- There are only four BGP messages available. These four messages are:
- The OPEN Message
- The UPDATE Message
- The NOTIFICATION Message
- The KEEPALIVE Message
- The different states BGP will go through before a neighbor relationship is established are:
- The Idle State
- The Connect State
- The Active State
- The OpenSent State
- The OpenConfirm State
- The Established State
- Border Gateway Protocol path attributes fall into four separate categories, which are:
- Well-known mandatory
- Well-known discretionary
- Optional transitive
- Optional non-transitive
- There are BGP two attributes that are used to influence the inbound path:
- The MULTI_EXIT_DISC attribute
- The AS_PATH attribute
- There are BGP two attributes that are used to influence the outbound path:
- The LOCAL_PREF Attribute
- The WEIGHT Attribute
Troubleshooting Neighbor Relationships
- The most common reason for failing to establish peer relationships are misconfigurations
- Common misconfigurations include:
- Using the Incorrect Autonomous System Number for the Peer
- Using the Incorrect IP Address for the Peer
- Incorrect Authentication Parameters
- No IP Connectivity between Indirectly Connected Peers
- In addition to misconfigurations, the following can prevent adjacencies from establishing:
- Access Control Lists Filtering BGP Packets
- Layer 1 and Layer 2 Issues
- Device Resource Consumption
Troubleshooting Route Advertisement
- Route advertisement issues with BGP are commonly due to device misconfigurations
- The network command must match the exact route BGP is to advertise
- The aggregate-address command requires a specific route for aggregate advertisement
- By default, the aggregate-address command does not suppress specific prefix
- The BGP Scanner process checks the BGP Table for updates every 60 seconds
- Following policy modification, clear the BGP session for changes to apply immediately
Troubleshooting Route Redistribution Issues
- By default, BGP will use the IGP metric when routes are redistributed into BGP
- When redistributing OSPF into BGP, only internal and Type 1 externals are redistributed
- By default, only external BGP routes are redistributed into IGPs
- The bgp redistribute-internal command is required to redistributed iBGP routes