Creating a BGP peer

Managing CPE devices > The BGP dynamic routing protocol > Creating a BGP peer

Creating a BGP peer

You can create a BGP peer on an individual CPE device or on all devices that use the CPE template. The maximum number of dynamic BGP peers is 512. If you plan to use route filtering, before creating a BGP peer, you must do the following:

To create a BGP peer, use the following instructions:

Creating a BGP peer on an individual CPE device.
To create a BGP peer on an individual CPE device:
1. In the menu, go to the SD-WAN section.
  By default, the CPE subsection is displayed with a table of CPE devices.
2. Click the CPE device.
  The settings area is displayed in the lower part of the page. You can expand the settings area to fill the entire page by clicking the expand button .
3. Select the BGP settings → Neighbors tab.
  A table of BGP peers is displayed.
4. Select the Override check box to ignore the applied CPE template and make the settings in the selected tab editable. This check box is cleared by default.
5. Click + BGP neighbor.
6. This opens a window; in that window, in the Name field, enter the name of the BGP peer. Maximum length: 50 characters.
7. If you do not want to establish a TCP session with the BGP peer after it is created, select the Disable BGP peer check box. This check box is cleared by default.
8. In the Neighbor IP field, enter the IPv4 address of the BGP peer.
9. In the Remote AS field, enter the autonomous system number of the BGP peer. Range of values: 1 to 4 294 967 295.
10. If necessary, enter a brief description of the BGP peer in the Description field.
11. In the Password field, enter the password for establishing a TCP session with the BGP peer. To see the entered password, you can click the show button . For a TCP session to be successfully established between two BGP peers, they must use the same password.
12. In the Loopback interface field, enter the IP address of the loopback interface that the CPE device must send to the BGP peer when establishing a TCP session.
13. In the eBGP hops field, enter the number of hops between the CPE device and the BGP peer if the TCP session is not established directly. Range of values: 1 to 255.
14. If necessary, configure BGP timers:
  1. Select the Custom BGP timers check box. This check box is cleared by default.
  2. In the Keepalive field, enter the time interval in seconds that the CPE device uses to send keepalive messages to BGP peers. Range of values: 0 to 65,535.
  3. In the Holdtime field, enter the time in seconds that the CPE device must wait to receive keepalive messages from BGP peers. If no keepalive messages are received from the BGP peer within the specified time, the device considers the peer unavailable. Range of values: 0 to 65,535.
15. To use the BFD protocol to detect loss of connectivity, select the BFD check box. This check box is cleared by default.
16. Select the Advanced settings to specify advanced BGP peer settings.
17. If necessary, select the following check boxes:
  - Select the Soft-reconfiguration inbound check box to store routes advertised by the BGP peer locally on the CPE device. This check box is cleared by default.
    Using this feature reduces the amount of memory available on the device.
  - Select the Attribute unchanged AS path check box to prevent modifying the 'AS path' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Allow AS in check box to allow the CPE device to receive from a BGP peer routes with the 'AS path' attribute, the value of which is the autonomous system number of this device.
  - Select the Attribute unchanged next-hop check box to prevent modifying the 'next hop' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Next-hop self check box to use the IP address of the CPE device as the 'next-hop' attribute when advertising routes to the BGP peer.
  - Select the Attribute unchanged MED check box to prevent modifying the 'MED' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Route reflector client check box to assign the Route Reflector role to the CPE device and the Route Reflector Client role to the BGP peer. You can only select this check box when configuring a BGP peer that is in the same autonomous system as the CPE device.
  By default, all check boxes are cleared.
18. In the Local AS field, enter the number of the local autonomous system that the CPE device must send to the BGP peer. Range of values: 1 to 4 294 967 295.
19. In the Weight field, enter the weight of the routes advertised by the BGP peer. The greater the weight of a route, the higher its priority. Range of values: 0 to 65,535.
20. In the Maximum prefix field, enter the maximum number of prefixes that the BGP peer can advertise to a CPE device. Range of values: 1 to 4,294,967,295.
21. If you want a CPE device to advertise routes with the 'community' attribute to its BGP peer, select the Send community check box and select the type of attribute to be sent in the drop-down list:
  - All to send all available types of the 'community' attribute to the BGP peer.
  - Standard and extended community to send 'standard community' and 'extended community' attributes to the BGP peer.
  - Extended community to send the 'extended community' attribute to the BGP peer.
  - Large community to send the 'large community' attribute to the BGP peer.
  - Standard community to send the 'standard community' attribute to the BGP peer.
  This check box is cleared by default.
22. Select the Default originate check box if you want the CPE device to forward the default route (0.0.0.0) to the BGP peer. This check box is cleared by default. You can also select the Set route map check box and select a previously created route map for the default route from the drop-down list that is displayed.
23. Select the Filtering tab to configure route filtering for the BGP peer.
24. Under Route map, select previously created route maps for route filtering:
  1. In the Inbound drop-down list, select the route map that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the route map that the CPE must use when advertising routes to the BGP peer.
25. Under Prefix list, select previously created prefix lists for route filtering:
  1. In the Inbound drop-down list, select the prefix list that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the prefix list that the CPE must use when advertising routes to the BGP peer.
26. Under Access control list, select previously created access control lists for route filtering:
  1. In the Inbound drop-down list, select the access control list that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the access control list that the CPE must use when advertising routes to the BGP peer.
27. Click Create.
  The BGP peer is created and displayed in the table.
28. In the upper part of the settings area, click Save to save the configuration of the CPE device.
Creating a BGP peer on all devices that use the CPE template.
To create a BGP peer on all devices that use the CPE template:
1. In the menu, go to the SD-WAN → CPE templates subsection.
  A table of CPE templates is displayed.
2. Click the CPE template.
  The settings area is displayed in the lower part of the page. You can expand the settings area to fill the entire page by clicking the expand button .
3. Select the BGP settings → Neighbors tab.
  A table of BGP peers is displayed.
4. Click + BGP neighbor.
5. This opens a window; in that window, in the Name field, enter the name of the BGP peer. Maximum length: 50 characters.
6. If you do not want to establish a TCP session with the BGP peer after it is created, select the Disable BGP peer check box. This check box is cleared by default.
7. In the Neighbor IP field, enter the IPv4 address of the BGP peer.
8. In the Remote AS field, enter the autonomous system number of the BGP peer. Range of values: 1 to 4 294 967 295.
9. If necessary, enter a brief description of the BGP peer in the Description field.
10. In the Password field, enter the password for establishing a TCP session with the BGP peer. To see the entered password, you can click the show button . For a TCP session to be successfully established between two BGP peers, they must use the same password.
11. In the Loopback interface field, enter the IP address of the loopback interface that the CPE device must send to the BGP peer when establishing a TCP session.
12. In the eBGP hops field, enter the number of hops between the CPE device and the BGP peer if the TCP session is not established directly. Range of values: 1 to 255.
13. If necessary, configure BGP timers:
  1. Select the Custom BGP timers check box. This check box is cleared by default.
  2. In the Keepalive field, enter the time interval in seconds that the CPE device uses to send keepalive messages to BGP peers. Range of values: 0 to 65,535.
  3. In the Holdtime field, enter the time in seconds that the CPE device must wait to receive keepalive messages from BGP peers. If no keepalive messages are received from the BGP peer within the specified time, the device considers the peer unavailable. Range of values: 0 to 65,535.
14. To use the BFD protocol to detect loss of connectivity, select the BFD check box. This check box is cleared by default.
15. Select the Advanced settings to specify advanced BGP peer settings.
16. If necessary, select the following check boxes:
  - Select the Soft-reconfiguration inbound check box to store routes advertised by the BGP peer locally on the CPE device. This check box is cleared by default.
    Using this feature reduces the amount of memory available on the device.
  - Select the Attribute unchanged AS path check box to prevent modifying the 'AS path' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Allow AS in check box to allow the CPE device to receive from a BGP peer routes with the 'AS path' attribute, the value of which is the autonomous system number of this device.
  - Select the Attribute unchanged next-hop check box to prevent modifying the 'next hop' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Next-hop self check box to use the IP address of the CPE device as the 'next-hop' attribute when advertising routes to the BGP peer.
  - Select the Attribute unchanged MED check box to prevent modifying the 'MED' attribute of routes that the CPE device advertises to the BGP peer.
  - Select the Route reflector client check box to assign the Route Reflector role to the CPE device and the Route Reflector Client role to the BGP peer. You can only select this check box when configuring a BGP peer that is in the same autonomous system as the CPE device.
  By default, all check boxes are cleared.
17. In the Local AS field, enter the number of the local autonomous system that the CPE device must send to the BGP peer. Range of values: 1 to 4 294 967 295.
18. In the Weight field, enter the weight of the routes advertised by the BGP peer. The greater the weight of a route, the higher its priority. Range of values: 0 to 65,535.
19. In the Maximum prefix field, enter the maximum number of prefixes that the BGP peer can advertise to a CPE device. Range of values: 1 to 4,294,967,295.
20. If you want a CPE device to advertise routes with the 'community' attribute to its BGP peer, select the Send community check box and select the type of attribute to be sent in the drop-down list:
  - All to send all available types of the 'community' attribute to the BGP peer.
  - Standard and extended community to send 'standard community' and 'extended community' attributes to the BGP peer.
  - Extended community to send the 'extended community' attribute to the BGP peer.
  - Large community to send the 'large community' attribute to the BGP peer.
  - Standard community to send the 'standard community' attribute to the BGP peer.
  This check box is cleared by default.
21. Select the Default originate check box if you want the CPE device to forward the default route (0.0.0.0) to the BGP peer. This check box is cleared by default. You can also select the Set route map check box and select a previously created route map for the default route from the drop-down list that is displayed.
22. Select the Filtering tab to configure route filtering for the BGP peer.
23. Under Route map, select previously created route maps for route filtering:
  1. In the Inbound drop-down list, select the route map that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the route map that the CPE must use when advertising routes to the BGP peer.
24. Under Prefix list, select previously created prefix lists for route filtering:
  1. In the Inbound drop-down list, select the prefix list that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the prefix list that the CPE must use when advertising routes to the BGP peer.
25. Under Access control list, select previously created access control lists for route filtering:
  1. In the Inbound drop-down list, select the access control list that the BGP peer must use when advertising routes to the CPE device.
  2. In the Outbound drop-down list, select the access control list that the CPE must use when advertising routes to the BGP peer.
26. Click Create.
  The BGP peer is created and displayed in the table.
27. In the upper part of the settings area, click Save to save the configuration of the CPE template.

Article ID: 244857, Last review: Aug 21, 2024

Page top