Sessions and Peers
When two routers communicate using the BGP protocol, a BGP session is started. The two end-points of that
session are Peers. A Peer is also called a Neighbor.
Establish a Session
Information exchange between peers is driven by events and timers. The focus in BGP is on the traffic routing
policies.
In order to make decisions in its operations with other BGP peers, a BGP process uses a simple finite state
machine that consists of six states: Idle, Connect, Active, OpenSent, OpenConfirm, and Established. For each
peer-to-peer session, a BGP implementation tracks which of these six states the session is in. The BGP
protocol defines the messages that each peer should exchange in order to change the session from one state
to another.
State
Description
Idle
BGP initializes all resources, refuses all inbound BGP connection attempts, and initiates
a TCP connection to the peer.
Connect
In this state the router waits for the TCP connection to complete, transitioning to the
OpenSent state if successful.
If that transition is not successful, BGP resets the ConnectRetry timer and transitions to
the Active state when the timer expires.
Active
The router resets the ConnectRetry timer to zero and returns to the Connect state.
OpenSent
After successful OpenSent transition, the router sends an Open message and waits for
one in return.
OpenConfirm
After the Open message parameters are agreed between peers, the neighbor relation is
established and is in the OpenConfirm state. This is when the router receives and
checks for agreement on the parameters of open messages to establish a session.
Established
Keepalive messages are exchanged next, and after successful receipt, the router is
placed in the Established state. Keepalive messages continue to be sent at regular
periods (established by the Keepalive timer) to verify connections.
After the connection is established, the router can now send/receive Keepalive, Update, and Notification
messages to/from its peer.
Peer Groups
Peer groups are neighbors grouped according to common routing policies. They enable easier system
configuration and management by allowing groups of routers to share and inherit policies.
Peer groups also aid in convergence speed. When a BGP process needs to send the same information to a
large number of peers, the BGP process needs to set up a long output queue to get that information to all the
Border Gateway Protocol IPv4 (BGPv4)
210
Summary of Contents for S4048T
Page 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Page 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Page 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Page 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Page 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Page 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Page 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Page 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Page 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Page 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...