Dell Networking OS10 BGP Passive Peering - How to form BGP Neighborship when the peer has Port 179 Blocked or Can only Be the Active BGP Peer
Summary:This article explains how to configure DELL OS10 switch as a Passive BGP Peer
Please select a product to check article relevancy
This article applies to This article does not apply toThis article is not tied to any specific product.Not all product versions are identified in this article.
Initially BGP Peer-1 is in Idle state, it sends a TCP SYN to configured Peer-1 with source port is a random port and destination port 179. Peer-2 respond to peer with a TCP SYN, ACK with source port is 179 and Destination port is the random port used by Peer-1. Peer-1 responds with a TCP SYN ACK.
After TCP session is formed BGP moves to OPENSENT state.
In the above scenario
,
Peer-1 is the Active or connecting side as it is sending the TCP SYN.
Peer-2 is the Passive or listening side as it is listening to TCP Port 179 and responds with an ACK.
When a BGP speaker is configured as active, it may end up on either the active or passive side of the connection that eventually gets established. Once the TCP connection is completed, it does not matter which end was active and which was passive. The only difference is in which side of the TCP connection has port number 179.
Initially If OS10 receives a TCP SYN packet with a destination port 179 from a neighbor to form BGP Neighborship, it responds with a TCP ACK
If it does not receive any TCP SYN, OS10 tries to actively form BGP Neighborship by sending a TCP SYN with destination port 179
Note
If the peer cannot accept TCP packet with destination Port 179 i.e can only act as Active or connecting side, then we must enable passive peering in OS10.
If you enable passive peering for the peer template, the system does not send an OPEN message but responds to an OPEN message.
BGP Passive Peering (IPv4/IPv6) do not support password until 10.5.4.4. Check the release notes/User guide of newer firmware to check if support has been added later.
You can restrict the number of passive sessions the neighbor accepts using the limit command.
Optional: Enter maximum passive peers (Dynamic Peer*) count, which can dynamically be learned by peer listening. After the specified limit is reached, the next neighbor in the subnet will be treated as normal BGP peer.
Consider the DELLOS10 switch is connected forming a BGP peering to Router and Server. Router has no restriction.
The Server has an incoming Firewall rule to block TCP destination port 179.
We can also specify an IP range to listen rather than a specific host and limit number of connection. In Below sample configuration, we have 10.0.0.0/24subnet configured as listen to 5 Neighbor. After this limit is reached, the next neighbor in the subnet will be treated as normal BGP peer.