{"id":316,"date":"2021-02-18T15:05:57","date_gmt":"2021-02-18T15:05:57","guid":{"rendered":"https:\/\/bluemap.co\/blog\/?p=316"},"modified":"2022-01-09T07:27:25","modified_gmt":"2022-01-09T07:27:25","slug":"how-to-configure-bgp-on-juniper-router","status":"publish","type":"post","link":"https:\/\/bluemap.co\/blog\/2021\/02\/how-to-configure-bgp-on-juniper-router\/","title":{"rendered":"How to configure BGP on Juniper router?"},"content":{"rendered":"\n

BGP<\/strong> is a path vector routing protocol used to exchange routing information among routers in different Autonomous Systems [ASs]<\/strong>. BGP operates over TCP port 179. It is a reliable but slow routing protocol and it is also the routing protocol which runs the internet. JUNOS supports<\/a> BGP version 4 [v4]. This version of BGP adds support for Classless Inter-domain Routing (CIDR), which eliminates the concept of network classes.\u00a0BGP supports two types of neighbor relationship- ibgp [internal BGP peers- within same AS] and ebgp [external BGP peers – within different AS].\u00a0<\/p>\n\n\n\n

In this blog I will explain step by step configuration of BGP peers in Juniper vMX routers<\/strong>. To begin with, let us have a look at the topology:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this topology we have two Autonomous Systems – AS 100 and AS 200. In AS 100 we have vMX-1 and vMX-2 and in AS 200 we have vMX-3. Cisco routers 3725<\/strong> acts as end host which we will be using to check connectivity at the end of the configuration. <\/p>\n\n\n\n

Let us look at the steps involved to configure BGP in the above topology:<\/p>\n\n\n\n

  1. IP Configuration on the interface<\/strong>: Assign IP addresses as displayed in the topology. You can copy paste the commands below in your router if you trying to create the same lab<\/li><\/ol>\n\n\n\n

    vMX-1<\/p>\n\n\n\n

    set interfaces ge-0\/0\/2 unit 0 family inet address 10.1.1.1\/24<\/p>\n\n\n\n

    set interfaces ge-0\/0\/3 unit 0 family inet address 192.168.4.1\/30<\/p>\n\n\n\n

    set interfaces lo0 unit 0 family inet address 1.1.1.1\/32<\/p>\n\n\n\n

    vMX-2<\/p>\n\n\n\n

    set interfaces ge-0\/0\/2 unit 0 family inet address 192.168.7.1\/30<\/p>\n\n\n\n

    set interfaces ge-0\/0\/3 unit 0 family inet address 192.168.4.2\/30<\/p>\n\n\n\n

    set interfaces lo0 unit 0 family inet address 4.4.4.4\/32<\/p>\n\n\n\n

    vMX-3<\/p>\n\n\n\n

    set interfaces ge-0\/0\/0 unit 0 family inet address 10.1.3.1\/24<\/p>\n\n\n\n

    set interfaces ge-0\/0\/2 unit 0 family inet address 192.168.7.2\/30<\/p>\n\n\n\n

    set interfaces lo0 unit 0 family inet address 6.6.6.6\/32<\/p>\n\n\n\n

    2. Autonomous System and Router-ID configuration<\/strong>: As shown in the topology the Autonomous System will be assigned as AS-100 for vMX-1 and vMX-2 and AS-200 for vMX-3. Router-ID is a logical parameter, you can either use the ones I have chosen or choose your own values<\/p>\n\n\n\n

    vMX-1<\/p>\n\n\n\n

    set routing-options router-id 1.1.1.1<\/p>\n\n\n\n

    set routing-options autonomous-system 100<\/p>\n\n\n\n

    vMX-2<\/p>\n\n\n\n

    set routing-options router-id 4.4.4.4<\/p>\n\n\n\n

    set routing-options autonomous-system 100<\/p>\n\n\n\n

    vMX-3        <\/p>\n\n\n\n

    set routing-options router-id 6.6.6.6<\/p>\n\n\n\n

    set routing-options autonomous-system 200<\/p>\n\n\n\n

    3. eBGP peer configuration<\/strong>: eBGP peers are formed between routers which belong to two different Autonomous Systems. In our case eBGP peering will be done between vMX-2 of AS-100 with vMX-3 of AS-200. Follow the commands below to create eBGP peering. The address chosen for peering is the interface address for the routers.<\/p>\n\n\n\n

    vMX-2<\/p>\n\n\n\n

    set protocols bgp group BGP-Ext type external<\/p>\n\n\n\n

    set protocols bgp group BGP-Ext local-address 192.168.7.1<\/p>\n\n\n\n

    set protocols bgp group BGP-Ext peer-as 200<\/p>\n\n\n\n

    vMX-3<\/p>\n\n\n\n

    set protocols bgp group BGP-ext type external<\/p>\n\n\n\n

    set protocols bgp group BGP-ext local-address 192.168.7.2<\/p>\n\n\n\n

    set protocols bgp group BGP-ext peer-as 100<\/p>\n\n\n\n

    4. iBGP peer configuration<\/strong>: iBGP peers are formed between routers which belong to the same Autonomous System. In our case iBGP peering will be done between vMX-1 and vMX-2 in AS-100. In this case we choose the loopback IP addresses to establish iBGP peering, hence static routing is done on vMX routers to have connectivity with each other\u2019s loopback interfaces<\/p>\n\n\n\n

    vMX-1<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal type internal<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal local-address 1.1.1.1<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal peer-as 100<\/p>\n\n\n\n

    set routing-options static route 4.4.4.4\/32 next-hop 192.168.4.2<\/p>\n\n\n\n

    vMX-2<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal type internal<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal local-address 4.4.4.4<\/p>\n\n\n\n

    set routing-options static route 1.1.1.1\/32 next-hop 192.168.4.1<\/p>\n\n\n\n

    5. Routing Policy configuration<\/strong>: Till the above commands we have successfully established BGP connectivity between the routers. Now the next step is to advertise networks in BGP and to do the Next-Hop configuration for our iBGP peers. Speaking about routing policies the default policy for BGP is JUNOS says that import all routes and export nothing. To change this behavior and export our directly connected network into BGP we have to design an export route policy for BGP. Policy will be applied on the following routers for following purposes:<\/p>\n\n\n\n

    vMX-1: to advertise the connected the networks on vMX-1<\/p>\n\n\n\n

    set policy-options policy-statement Conn from protocol direct<\/p>\n\n\n\n

    set policy-options policy-statement Conn then accept<\/p>\n\n\n\n

    vMX-2: to configure Next-Hop-Self for vMX-1 and advertise networks in BGP. [Remember the next-hop-rule in BGP!!]<\/p>\n\n\n\n

    set policy-options policy-statement My-route from protocol direct<\/p>\n\n\n\n

    set policy-options policy-statement My-route from protocol static<\/p>\n\n\n\n

    set policy-options policy-statement My-route then accept<\/p>\n\n\n\n

    set policy-options policy-statement NHP term 1 from route-filter 1.1.1.1\/32 exact<\/p>\n\n\n\n

    set policy-options policy-statement NHP term 1 then next-hop self<\/p>\n\n\n\n

    set policy-options policy-statement NHP term 2 from protocol bgp<\/p>\n\n\n\n

    set policy-options policy-statement NHP term 2 from protocol direct<\/p>\n\n\n\n

    set policy-options policy-statement NHP term 2 then accept<\/p>\n\n\n\n

    vMX-3: to advertise the connected the networks on vMX-3<\/p>\n\n\n\n

    set policy-options policy-statement My-Route from protocol direct<\/p>\n\n\n\n

    set policy-options policy-statement My-Route then accept<\/p>\n\n\n\n

    6. Applying routing policy in BGP<\/strong>: Once the policies have been designed it is time to apply the policy in the BGP configuration:<\/p>\n\n\n\n

    vMX-1<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal neighbor 4.4.4.4 export Conn<\/p>\n\n\n\n

    vMX-2<\/p>\n\n\n\n

    set protocols bgp group BGP-Ext neighbor 192.168.7.2 export My-route<\/p>\n\n\n\n

    set protocols bgp group BGP-Internal neighbor 1.1.1.1 export NHP<\/p>\n\n\n\n

    vMX-3<\/p>\n\n\n\n

    set protocols bgp group BGP-ext neighbor 192.168.7.1 export My-Route<\/p>\n\n\n\n

    7. Verification<\/strong>: The result of the above configuration is shown below:<\/p>\n\n\n\n