BGP Tab
Configuration > Networking > Routing > BGP
On this tab, you can configure BGP (Border Gateway Protocol) for appliances and add their BGP peers (also known as BGP “neighbors”). You can also add and modify peer-based advertisement and redistribution rules. EdgeConnect has the following behaviors relative to communities:
Although EdgeConnect does not configure BGP communities, it propagates existing communities.
Appliances can display up to ten communities per route.
Appliances subnet-share communities with their EdgeConnect peers.
Appliances advertise communities to remote peers, if learned from EdgeConnect peers.
Appliances advertise communities to BGP neighbors.
All BGP-learned subnets also appear in the appliance Routes table, displayed on the Routes configuration page. In addition, any AS Path or BGP Community information learned with a particular subnet will also be displayed with that subnet entry in the table.
BGP route updates are not refreshed unless the peer specifically asks for it. To update the BGP routes, go to the Peers table and select Soft Reset in the desired row.
BGP Equal-cost multi-path (ECMP) is supported for eBGP and iBGP. Multiple next-hops will be installed for the same prefix if all BGP path attributes are the same, enabling BGP to load balance egress traffic across multiple peers. A maximum of 20 BGP peers is supported per appliance, with 16 next-hops supported per interface.
Click the Summary button on the BGP tab to display configuration details associated with the local appliance, such as its local AS number and router ID. Click the icon in the BGP State Details column to display a summary, including the number of routes learned and advertised via BGP by this appliance.
Click the Peers button on the BGP tab to display information about all configured peers for the appliances selected in the appliance tree. Click the icon in the Peer Details column to display the connection status of each peer that is configured for the appliance.
The table below describes the fields displayed for the BGP configuration.
| Field | Description |
|---|---|
| Appliance Name | Name of the appliance. |
| Segment | Name of the segment being used, if enabled. |
| Peer IP | IP address of the EdgeConnect peer. |
| Local Interface | A list of the interfaces that can be chosen: Any, lan0, wan0, or wan1. |
| Peer ASN | Peer’s Autonomous System Number. |
| Peer State | State of the peer. A peer state of Established indicates that full adjacency has been established and routes can be advertised to and learned from that peer. |
| Soft Reset | Allows new changes to be incorporated without taking the entire BGP session down. |
| Established Time | Final peer state that indicates neighbor connection as complete. |
| Type | Governs what kinds of routes the appliance is allowed to advertise to this BGP peer. These routes are itemized as Route Export Policies. |
| Inbound Route Map | Route map being used for the inbound traffic. |
| Outbound Route Map | Route map being used for the outbound traffic. |
| Local Preference | Local preference is the first attribute an EdgeConnect appliance looks at to determine which route towards a certain destination is the “best” one. This value is not exchanged between external BGP routers. Local preference is a discretionary BGP attribute. Default value is 100. The path with the highest local preference is preferred. |
| MED | Multi Exit Discriminator. When BGP chooses the best route to reach a certain destination, it first looks at the local preference and AS path attributes. When the local preference and AS path length are the same for two or more routes towards a certain prefix, the Multi Exit Discriminator (MED) attribute is chosen. With MED, the lowest value is preferred. NOTE: If you configured the Metric Delta parameter in an earlier version of our software, this value has been translated into a MED value. |
| Input Metric | Metric that is advertised with the route when shared. |
| Enable Imports | Allows the learning of routes from this specific BGP peer. |
| AS Prepend Count | Learned path from an external prepend between a remote BGP site to local BGP peers. |
| Next-Hop-Self | Advertised route connected to a CE router that an EdgeConnect appliance learns from the eBGP with a PE router. |
| Keep Alive Timer | Interval, in seconds, between keep alive signals to a peer. |
| Hold Timer | When availability to a peer is lost, this specifies how long to wait before dropping the session. |
| Peer Details | Any additional details about a peer or its state. |
To edit the BGP configuration for one of the listed appliances, click the edit icon in the left column of the table.
BGP Information
Use this window to enable BGP for your appliances and to configure BGP peers. Complete the following steps to start BGP configuration.
Move the toggle to Enable BGP.
Complete the following fields.
Field Description Autonomous System Number (ASN) Configure this number as needed for your network. Router ID This router identifier is the IPv4 address by which the remote peer can identify this appliance for purposes of BGP. Graceful Restart Enable receiver-side graceful restart capability. EdgeConnect retains routes learned from the peer and continues to use it for forwarding (if possible) if/when a BGP peer goes down. The retained routes are considered stale routes. They will be deleted and replaced with newly received routes.
Max Restart Time – Specifies the maximum time (in seconds) to wait for a Graceful Restart capable peer to come back after a peer restart or peer session failure.
Stale Path Time – Specifies maximum time (in seconds) following a peer restart that EdgeConnect waits before removing stale routes associated with that peer.AS Path Propagate Select this check box to enable this appliance to send the full AS path, associated with a prefix to other routers and appliances, avoiding routing loops. This will provide the learned path from an external prepend between a remote BGP site to local BGP peers.
To add a BGP peer, select Add. The Add Peer dialog box opens.
Add Peer
Complete the following fields to add a BGP peer.
| Field | Description |
|---|---|
| Peer IP | IP address of the EdgeConnect peer. |
| Local Interface | You can specify the source address or interface for a specific BGP peer. Select the interface from the drop-down list: any, lan0, wan0, or wan1. |
| Peer ASN | Peer’s Autonomous System Number. |
| Peer Type | Select the type of peer from the drop-down list: Branch or PE-router. |
| Admin Status | Select whether you want the Admin Status UP or DOWN. |
| Next-Hop-Self | Select this check box to enable the next-hop-self. |
| Inbound route map | Route map for inbound traffic. Select the edit icon to load or configure inbound route maps. |
| Outbound route map | Route map for outbound traffic. Select the edit icon to load or configure outbound route maps. |
| Keep Alive Timer | Interval, in seconds, between keep alive signals to a peer. |
| Hold Timer | Specified time to wait before dropping the session when the reachability to a peer is lost. |
| Enable MD5 Password | Select this check box to add a password to authenticate the TCP session with the peer. |
BGP Inbound and Outbound Route Redistribution Maps
Route Maps are policies that can be applied to static, OSPF, BGP, and SD-WAN fabric learned routes. These policies have match and set criteria. A route map is applied to routes during route redistribution between routing protocols and allows for filtering routes or modifying route attributes.
Maximum allowed amounts for BGP route maps and rules per route map:
Specify up to 20 BGP route maps (inbound and outbound).
Apply up to 128 rules per route map.
You can add, delete, rename, or clone route maps using this window. You can add rules to your route map to further specify routing protocols by clicking Add Rule. Use rules to allow or deny routes based on numerous matching criteria.
NOTE: Prefix match criteria is ‘exact match + less than’. Both the prefix specified and any subnets of that prefix will be matched. This behavior will be updated in a future release to allow for selection of ‘exact,’ ‘greater than,’ or ‘less than’ criteria.
To permit a default-route, deny 0.0.0.0/1, deny 128.0.0.0/1, and then permit any.
You can specify the following fields in each rule for the selected route map.
Priority (Inbound and Outbound)
| Field | Description |
|---|---|
| Priority | If you are using Orchestrator templates to add rules, Orchestrator will delete all entries from 1000 – 9999 before applying its policies.You can create rules with higher priority than Orchestrator rules (1 – 999) and rules with lower priority (10000 – 19999 and 25000 – 65534). NOTE: The priority range from 20000 to 24999 is reserved for Orchestrator.When adding a rule, the priority is incremented by 10 from the previous rule. The priority can be changed, but this default behavior helps to ensure you can insert new rules without having to change subsequent priorities. |
Select Match Criteria (Inbound)
| Source Protocol | Complete the Following Fields (based on protocol selected) |
|---|---|
| BGP | Enter the prefix (list of subnets separated by commas) and your BGP communities. Prefix BGP Communities |
Select Match Criteria (Outbound)
| Source Protocol | Complete the Following Fields (based on protocol selected) |
|---|---|
| Local/Static | Enter the prefix (list of subnets separated by commas) and your BGP communities. Prefix |
| SD-WAN (Local/Static) | Prefix BGP Communities |
| BGP | Prefix BGP Communities |
| OSPF | Prefix OSPF Tag |
| SD-WAN (BGP) | Prefix BGP Communities |
| SD-WAN (OSPF) | Prefix OSPF Tag |
Set Actions (Inbound and Outbound)
| Field | Description |
|---|---|
| Permit | Enable or disable. This setting allows or denies the route map. |
| BGP Local Preference | Best BGP destination. The default value is 100. |
| Metric | Metric for the route. |
| BGP Communities | Label of extra information that is added to one or more prefixes advertised to BGP neighbors. |
| Nexthop | Advertised route connected to a CE router that an EdgeConnect appliance learns from the eBGP with a PE router. |
| ASN Prepend Count | Original route path that was used. NOTE: This field is displayed only for the Outbound redistribution map. |
| Comment | Comment you want to include. |
The following table describes the redistribution commands supported in the BGP routing protocol.
| Command | Redistribution Support |
|---|---|
| Match prefix | Yes |
| Set metric | Yes |
| Set tag | Yes |