BGP

Question 1

Configuration > Networking > Routing > BGP

Answer 1

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.

Question 2

EdgeConnect has the following behaviors relative to communities:

Answer 2

l Although EdgeConnect does not configure BGP communities, it propagates existing communities.
l Appliances can display up to ten communities per route.
l Appliances subnet-share communities with their EdgeConnect peers.
l Appliances advertise communities to remote peers, if learned from EdgeConnect peers.
l Appliances advertise communities to BGP neighbors.
l 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.
l 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.
l 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
l A maximum of 64 BGP peers and 64 OSPF peers is supported per appliance, with 200 next-hops supported per interface.

Question 3

Prefix Match Criteria

Answer 3

The default for prefix match criteria is exact-match + greater-than.

Both the specified prefix and any subnets of that prefix will be matched, up to a length of 32 for IPv4 or 128 for IPv6 (subnet sharing route maps only).

Question 4

Routes Tab
Configuration > Networking > Routing > Routes

Answer 4

Each appliance builds a route table with entries that are added automatically by the system, added manually by a user, or learned from a routing protocol (SD-WAN Fabric Subnet Sharing, BGP, or OSPF)

Question 5

Route Maps

Answer 5

Route Maps are policies applied to IP routes during redistribution between routing protocols.
They have Match Criteria and Set Actions that allow for filtering routes or modifying metrics and attributes for routes that meet the criteria defined in the match statement.
Route-map rules follow a top-down order based on the sequence number defined for each entry.
EdgeConnect Enterprise supports applying Route Maps inbound from and outbound to BGP peers and outbound to OSPF neighbors and the SD-WAN Fabric.
It is best practice to use Orchestrator to apply Route
Maps using templates.

Question 6

Route mapping is supported for the following protocols and the direction of those protocols:

Answer 6

l Local, static to SD-WAN fabric
l BGP, OSPF to SD-WAN fabric
l SD-WAN fabric to BGP Outbound peers
l Local, BGP, OSPF to BGP outbound peers
l Local BGP Peers to EdgeConnect BGP sessions