Creating a BGP peer

You can create a BGP peer in a network template or on a device. A BGP peer created in a network template is automatically created on all devices that use this template. The maximum number of dynamic BGP peers is 512.

To create a BGP peer:

  1. In the main menu of the Open Single Management Platform Console, go to the Application & Services → NGFW section.
  2. Create a BGP peer in one of the following ways:
    • If you want to create a BGP peer in a network template, in the menu, select the Network templates tab, click the network template, and select the Routing → BGP section.
    • If you want to create a BGP peer on a device, select the Devices tab, click the device, select the Routing → BGP section, and enable the Override toggle switch.
  3. Open an existing BGP instance by selecting it in the table and clicking the Edit button in the upper part of the table, or create a BGP instance.
  4. In the settings area of the BGP instance, select the Neighbors tab.

    A table of BGP peers is displayed.

  5. Click + Create.
  6. This opens a window; in that window, in the Name field, enter the name of the BGP peer. The maximum length of the name is 50 characters.
  7. If necessary, enter a brief description of the BGP peer in the Description field.
  8. If you want to disable a BGP peer and prevent establishing a TCP session with it, enable the Shutdown toggle switch. This toggle switch is disabled by default.
  9. In the Neighbor IP address field, enter the IPv4 address of the BGP peer.
  10. In the Remote AS field, enter the autonomous system number of the BGP peer. Range of values: 1 to 4 294 967 295.
  11. If you want the device to use a password when establishing a TCP session with the BGP peer, in the Password field, enter the password. For a TCP session to be established between two BGP peers, they must use the same password. To see the entered password, you can click the show icon .
  12. If necessary, in the Update source field, enter the IPv4 address of the loopback interface that the device sends to the BGP peer when establishing a TCP session.
  13. If the TCP session is not established directly between the device and the BGP peer, in the eBGP hops field, enter the number of hops between the device and the BGP peer. Range of values: 1 to 255.
  14. If you want to use the BFD protocol to detect loss of connectivity, enable the BFD toggle switch. When this toggle switch is enabled, the changes you make to the route map are immediately applied to a BGP peer if the BGP peer uses this route map. You can select a route map for the BGP peer at step 17 of these instructions.
  15. If you want to configure BGP timers:
    1. Enable the Custom BGP timers toggle switch. This toggle switch is disabled by default.
    2. In the Keepalive field, enter the time interval in seconds that the device uses to send control packets to a BGP peer. Range of values: 0 to 65 535.
    3. In the Holdtime field, enter the time interval in seconds that the CPE device uses when receiving control packets from the BGP peer. If no control packets are received from the BGP peer within the specified time, the device considers this BGP peer unavailable. Range of values: 0 to 65 535.
  16. If you want to specify advanced settings for the BGP peer:
    1. Select the Advanced tab.

      Advanced settings of the BGP peer are displayed.

    2. Manage the following settings as needed:
      • Enable the Soft-reconfiguration inbound toggle switch to store the routes advertised by a BGP peer group locally on the device. This feature takes up disk space on the device. When this toggle switch is enabled, the changes you make to the route map are immediately applied to a BGP peer if the BGP peer uses this route map. You can select a route map for the BGP peer at step 17 of these instructions.
      • Enable the Allow AS in toggle switch to let BGP peers advertise routes to the device with the 'AS path' attribute, whose value is the autonomous system number of the device.
      • Enable the Next hop self toggle switch to use the IPv4 address of the device as the value of the next-hop attribute when advertising routes to a BGP peer.
      • Enable the Route reflector client toggle switch to assign the Route Reflector role to the device, and the Route Reflector client role to the BGP peer. You can enable this toggle switch only for a BGP peer that is in the same autonomous system as the device itself.
      • Enable the Attribute unchanged AS path toggle switch to keep the AS path attribute unchanged for routes that the device advertises to the BGP peer.
      • Enable the Attribute unchanged next hop toggle switch to keep the next hop attribute unchanged for routes that the device advertises to the BGP peer.
      • Enable the Attribute unchanged MED toggle switch to keep the MED attribute unchanged for routes that the device advertises to the BGP peer.

      By default, these toggle switches are disabled.

    3. In the Local AS field, enter the number of the local autonomous system that the device sends to the BGP peer group. Range of values: 1 to 4 294 967 295.
    4. 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.
    5. In the Maximum prefix field, enter the maximum number of routes that the BGP peer can advertise to the device. Range of values: 1 to 4 294 967 295.
    6. If you want the device to advertise routes with the community attribute to the BGP peer, enable the Send community toggle switch, and in the Type drop-down list that appears, select an attribute type:
      • All for all available types of the community attribute.
      • Both for the standard and extended community attribute.
      • Extended for the extended community attribute.
      • Large for the large community attribute.
      • Standard for the standard community attribute.

      This toggle switch is disabled by default.

    7. If you want the device to advertise the default 0.0.0.0/0 route to the BGP peer, enable the Default originate toggle switch. This toggle switch is disabled by default.
  17. If you want to use a previously created route map, select the Set route map toggle switch and select a route map from the drop-down list that appears.
  18. If you want to configure route filtering for the BGP peer:
    1. Select the Filtering tab.

      The route filtering settings are displayed.

    2. Under Access control list, select the created access control lists:
      1. In the Inbound drop-down list, select an access control list for the routes that the BGP peer advertises to the device.
      2. In the Outbound drop-down list, select an access control list for the routes that the device advertises to the BGP peer.
    3. Under Prefix list, select the created prefix lists:
      1. In the Inbound drop-down list, select a prefix list for the routes that the BGP peer advertises to the device.
      2. In the Outbound drop-down list, select a prefix list for the routes that the device advertises to the BGP peer.
    4. Under Route map, select the created route maps:
      1. In the Inbound drop-down list, select a route map for the routes that the BGP peer advertises to the device.
      2. In the Outbound drop-down list, select a route map for the routes that the device advertises to the BGP peer.
  19. Click Create.

    The BGP peer is created and displayed in the table.

  20. Save the settings of the network template or device.
Page top