This article describes How to configure BGP to add new Autonomous system path and add any number of local Autonomous system


 

Prerequisites

  1. Versa Headend should be deployed and functional
  2. Versa FlexVNF is connected to a Router and eBGP is established between them


 

 

 

Topology

 

 

 

Configuration

  1. By default, routes (direct, static, etc) are not redistributed into BGP table. For example, 50.1.1.0/24 is connected subnet and it is present in routing table, but never was redistributed into BGP table

 

cid:image001.png@01D4B1F3.FB546B50

 

cid:image003.png@01D4B1F4.6BE25A80

 

cid:image004.png@01D4B1F6.5EA0BA90


 

  1. From the “Appliances” page, click on the router that needs to be configured. router1 will be configured for this illustration.

 

cid:image002.png@01D4B1F3.1FB8C8C0

 

  1. Click on the test , where various configuration can be done such as configuring “redistribution policy”, routing protocol (BGP, OSPF).

 

cid:image005.png@01D4B1F7.2F84D560

 

  1. To inject connected route into BGP table, click on Redistribution Policies tab and then on the + icon to add new redistribution policy.
  2. On the Add Redistribution Policy tab, click on the + icon which opens up another window called Add Term.
  3. From Add Term window, match and action items can be set. For this example, we will select Direct under Protocol 
  4. Then under Action, select Accept which means all connected routes in test vrf will be allowed to be redistributed into BGP table.

 

cid:image006.png@01D4B1F9.8F3CB340

 

cid:image008.png@01D4B1F9.BB65EFE0

 

  1. Once redistribution policy is added, the new redistribution policy name would appear under Redistribute to BGP section which needs to be selected and click OK.

 

cid:image007.png@01D4B1FA.BDFF1BE0

 

  1. After successfully adding redistribution policy into bgp, all connected subnets appear in bgp table and also the pfxSent values changed to 2 from 0 which means two prefixes were advertised to the bgp neighbor.

 

cid:image009.png@01D4B1FB.FD4DF7C0

 

cid:image010.png@01D4B1FC.74FE3A00

 

  1. As the prefixes are installed in the bgp table, we can change with BGP attributes.
  2. Configure Prefix list to match 50.1.1.0/24. Go to BGP tab on the left pane and click on Instance ID which is 100
  3. In BGP Instance window, click on Prefix List tab, Give a name allow-only-50 under Prefix List Name and then click on + icon.
  4. Configure Sequence Number to 10 , Action set to permit and IP Address/Mask configured to 50.1.1.0/24.

 

cid:image011.png@01D4B1FE.B29F2250

 

  1. Configure BGP policy. From Edit BGP Instance window, click on Peer/Group Policy and give a name of the policy ,click on + icon .
  2. Give a Term Name and define Match and Action items. Select the prefix list (allow-only-50) which was created earlier under NLRI. We are interested in match the prefix matched by prefix-list.
  3. Click on OK

 

cid:image012.png@01D4B200.B2529E10

 

  1. In the Action tab, Select Accept in Accept/Reject option.
  2. Set Local Autonomous system Prepend Count to 3.
  3. Specify the Autonomous system number that needs to be appended in Autonomous system Path Prepend.

 

cid:image014.png@01D4B203.23CA6620

 

  1. We need to add the bgp policy (bgp-policy1) to the neighbor (192.168.1.1) so that 50.1.1.0/24 is advertised with new Autonomous system set values ,Select bgp-policy1 under Export.

 

cid:image013.png@01D4B203.FE991BC0

 

  1. Now, you will see that three local Autonomous system number is added and new Autonomous system number is also prepended.