BGP Dynamic Peering

-

 As we know, configuring the BGP neighbor is not too difficult, but when we are going to configure 100 Number of neighbors, then it cloud be tedious.

So to minimize this configuration we have BGP peer Group, in which we can group the BGP Neighbors who are sharing the same outbound polices, either the BGP Neighborship is iBGP or eBGP. But the first we need to manually configure 100 Peer and then add to the peer group. So the problem is still not resolved.

Let’s verify BGP peer Group configuration

1 Example: Configuration step of iBGP Peer Group.



2 Example: Configuration step of eBGP peer Group.



With the Dynamic BGP peering feature, BGP router dynamically establish peering with group of remote neighbor that are configured using a range of IP addresses and BGP peer group.

In the Dynamic BGP peering, BGP peer tries to establish a BGP neighborship, if the neighbor router initiate TCP session because Dynamic BGP peer configuration router work as passive listen mode and it initiates a TCP session if the IP and AS number match with any of the configured IP subnets.

 

So in this scenario, we will discuss on how to configure Dynamic BGP peer.



As per diagram R1 wants dynamic peering with R2 and R3, so let verify the configuration steps;

Step 1. Define BGP peer group name

R1(config-router)# neighbor  Dynamic-peer peer-group

 

Step 2. Create a global limit of BGP dynamic subnet range neighbors. The value ranges from 1 to 5000. R1(config-router)# bgp listen limit 100

 

Step 3. Define the IP Subnet Range and associate it with a peer group. Multiple subnets can be added to the same peer group.

 R1(config-router)# bgp listen range 172.16.0.0/16 peer-group Dynamic-peer

Step 4. Define the remote-as for the peer group. Optionally, define the list of AS numbers that can be accepted to form neighborship with. The max limit of alternate-as numbers is 5.

R1(config-router)# neighbor Dynamic-peer  remote-as   65002 alternate-as 65003 65004

 

Step 5. Activate the peer group under ipv4 address-family

R1(config-router)#address-family ipv4

R1(config-router-af)# neighbor Dynamic-peer  activate.

 

Router1#show run | section router bgp

router bgp 65001

 bgp log-neighbor-changes

 bgp listen range 172.16.0.0/16 peer-group Dynamic-peer

 neighbor Dynamic-peer peer-group

 neighbor Dynamic-peer remote-as 65002 alternate-as 65003 65004

 !

 address-family ipv4

  neighbor Dynamic-peer activate

 exit-address-family

 

Router2#show run | section bgp

router bgp 65002

 bgp log-neighbor-changes

 neighbor 172.16.1.1 remote-as 65001

 

Router3#show run | section router bgp

router bgp 65003

bgp log-neighbor-changes

neighbor 172.16.2.1 remote-as 65001

 

 

Router1#show ip bgp summary

BGP router identifier 10.10.10.1, local AS number 65001

BGP table version is 1, main routing table version 1

 

Neighbor        V           AS    MsgRcvd    MsgSent   TblVer     InQ OutQ    Up/Down    State/PfxRcd

*172.16.1.2     4        65002       4                 4             1              0    0         00:00:38        0

*172.16.2.2     4        65003       4                 2             1              0    0         00:00:29        0

* Dynamically created based on a listen range command

 Dynamically created neighbors: 2, Subnet ranges: 1

 

BGP peergroup Dynamic-peer listen range group members:

  172.16.0.0/16

 

Total dynamically created neighbors: 2/(100 max), Subnet ranges: 1

 

Router1#show tcp brief all

TCB                    Local Address                 Foreign Address                   (state)

A2B61B90         172.16.1.1.179              172.16.1.2.64321                    ESTAB

A2B62F48         172.16.2.1.179               172.16.2.2.17764                   ESTAB

A2B19B20          0.0.0.0.179                            *.*                                   LISTEN

 

As per output illustrates that the router is listening on port 179 but with foreign address of *.*.

Comments

Post a Comment

Popular posts from this blog

BGP Neighbor States

-
Image
  BGP is designed for handle large amount of routing information and Complex Networks, BGP enable routers create TCP connection with neighbor that is called BGP Peers. BGP neighbors are manually configured, when we configure BGP neighbor, it goes through different stages before it reaches the desired state (Established State).   BGP Session goes through following stages: 1)      Idle state : In this state, BGP enable router detects start event (start event occur when we configure new neighbor or reset already established neighbor peering), and tries to initiates a TCP connection to the BGP peer, and also listening new BGP peer router, who tries to establish new connection. If successful, BGP state changes to connect state, if any error cause in this state, BGP router again back to the idle state, the ConnectRetryTime is set to 60 secs, and re-initiate connection when decrement to zero. Further failure results doubling ConnectRetryTime in the length from previous...
Read more

MBGP vs BGP

-
  MBGP vs BGP Currently BGP is running in version 4, which has been published in 2006 (RFC 4271). By default, BGPv4 only supports IPv4 unicast prefixes, But BGP can do much more than carrying IPv4 prefixes only. RFC 4760 Multiprotocol extensions for BGPv4 was written in order to enhance the capacity of carrying routing related information other than carrying ipv4 only.     Multiprotocol Extensions for BGPv4 added some new attributes. ·          Multiprotocol Reachable NLRI (MP_REACH_NLRI): It carry set of reachable destination with next-hop information. ·          Multiprotocol Unreachable NLRI (MP_UNREACH_NLRI): It carry set of unreachable destinations.   Note: - “MP_REACH_NLRI” and “MP_UNREACH_NLRI” are optional and Non-transitive attribute, because of this if neighbor doesn’t support the multiprotocol capabilities, it will just ignore information carried in these attributes and will...
Read more