Configure Dynamic Routing with OSPF or BGP

1. In the SD-WAN service of the Enterprise portal, select the Configure tab.
2. From the left menu, select Profiles to display the Profile page.
3. Select a Profile from the list of available Profiles or add a Profile if necessary.
4. Go to the Routing & NAT section and select the arrow next to BGP to expand.
5. In the BGP area, toggle the radio button from Off to On.

   

6. In the BGP area, enter the local Autonomous System Number (ASN) in the appropriate field.
7. Configure the BGP Settings.

   Table 4. BGP Settings - Options and Descriptions

   Option	Description
   Router ID	Enter the global BGP router ID. If users do not specify any value, the ID is automatically assigned. If users have configured a loopback Interface for the Edge, the IP address of the loopback Interface will be assigned as the router ID.
   Keep-Alive	Enter the keep-alive timer in seconds, which is the duration between the keep-alive messages sent to the peer. The range is from 0 to 65535 seconds. The default value is 60 seconds.
   Hold Timer	Enter the hold timer in seconds. If users don't receive the keep-alive message within the specified time, the peer is down. The range is from 0 to 65535 seconds. The default value is 180 seconds.
   Uplink Community	Enter the community string to treat as uplink routes. Uplink refers to link connected to the Provider Edge(PE). Inbound routes towards the Edge matching the specified community value is treated as Uplink routes. These routes are not owner of the Hub/Edge. Enter the value in number format ranging from 1 to 4294967295 or in AA:NN format.
   Enable Graceful Restart checkbox	Note when selecting this checkbox: The local router does not support forwarding during the routing plane restart. This feature supports preserving forwarding and routing in case of peer restart.

    

8. Select +Add in the Filter List area to create one or more filters. These filters are applied to the neighbor to deny or change the attributes of the route. Users can use the same filter for multiple neighbors.

   

   

   

9. In the appropriate text fields, set the rules for the filter, as described in the table below.

   Table 5. Add Filter - Options and Descriptions

   Option	Description
   Filter Name	Enter a descriptive name for the BGP filter.
   Match Type	Choose the type of the routes to match with the filter: Prefix for IPv4 or IPv6- Choose to match with a prefix for IPv4 or IPv6 address and enter the corresponding prefix IP address in the Value field. Community- Choose to match with a community and enter the community string in the Value field. AS Path - Match routes using the user-provided AS path regular expression. Metric- Match routes using the user-provided MED value. Local preference-Match routes using the user-provided local preference value.
   Match Value	Enter the subnet value.
   Exact Match	It performs the filter action only when the Prosecutes match exactly with the specified prefix or community string. By default, this option is enabled.
   Action Type	Select the action to perform when the routes match with the specified prefix or the community string. Users can either permit or deny the traffic.
   Action Set	When the BGP routes match the specified criteria, users can set to route the traffic to a network based on the attributes of the path. Select one of the following options from the drop-down list: None- The attributes of the matching routes remain the same. Local Preference- It routes the matching traffic to the path with the specified local preference. Community- It filters the matching routes by the specified community string. Users can also select Community Additive to enable the additive option, which appends the community value to existing communities. Metric - It routes the matching traffic to the path with the specified metric value. As-Path-Prepend- Allows pre-pending multiple entries of Autonomous System (AS) to a BGP As-Path-Exclude - AS path exclude is a new set option, using which users can remove specific Autonomous System (AS) numbers from a route’s AS path. When users exclude ASNs, the system deletes all occurrences of the specified numbers, regardless of where they appear in the sequence.

   AS path Regex match option

   By using the AS Path Regex match type, administrators can filter BGP routes based on the autonomous systems they have traversed, applying a Permit or Deny action whenever a route's AS path matches the defined pattern. This approach enables the creation of sophisticated policies based on a route’s origin or transit history rather than just its prefix, allowing the system to accept routes from specific providers, block untrusted transit networks, or match defined ranges of ASNs.

   Table 6. Supported AS Path Regex Characters

   Character	Meaning / Use	Example	Matches Example AS Paths
   0–9	Digits used in AS numbers	^65001$	65001
   ^	Start of AS path	^65001	65001 65002 65003
   $	End of AS path	65001$	65003 65002 65001
   _	AS boundary (start, end, space, comma, brace, or parentheses)	_65001_	65000 65001 65002
   			65001
   |	Logical OR (alternation)	^(65001|65002)$	65001
   			65002
   []	Character class (any one character in set)	^6500[12]$	65001
   			65002
   {}	Repeat count	[0-9]{5}	65000
   ()	Grouping (for OR or repetition)	(65001|65002) 65003	65002 65003 65004
   (space)	AS separator	^65001 65002	65001 65002 65003
   *	Zero or more repetitions	[0-9]*	65001
   			123
   +	One or more repetitions	[0-9]+	65001
   .	Any single character	6500.	65000–65009
   ?	Zero or one occurrence	6500[1-2]?	6500
   			65001
   			64002
   -	Range indicator (inside [])	^65[0-9][0-9]$	6500–6599
   \	Escape special characters (treat literally) Usually matches confederations and AS_SET	_\{65200_	65100 {65200 65300}
   		_\(64512\)	65001 (64512) 65001

   AS Path Exclude

   AS path exclude is a new set option,using which users can remove specific Autonomous System (AS) numbers from a route’s AS path. When users exclude ASNs, the system deletes all occurrences of the specified numbers, regardless of where they appear in the sequence.

   Example:

   For instance, if a user provides input as "100 300" and a route's AS path is "100 200 300 400", the resulting AS path after filtering will be "200 400"

10. Select the + icon to add more matching rules for the filter. Repeat the procedure to create more BGP filters. The Filter List area displays the configured filters.
    Note:

    • The maximum number of supported BGPv4 Match/Set rules is 512 (256 inbound, 256 outbound). Exceeding 512 total Match/Set rules may cause performance issues, resulting in disruptions to the enterprise network.
    • Older versions of Edge and their profiles show the new enhanced BGP filter options AS Path, AS-Path -Exclude, Metric and Local preference in the user interface, but these settings are not applied until upgraded to Edge version 7.0 or above.
11. Scroll down to Neighbors and select +Add.

    

12. Configure the following settings for the IPv4 addressing type:

    Table 7. Neighbours - Options and Descriptions

    Option	Description
    Neighbor IP	Enter the IPv4 address of the BGP neighbor
    ASN	Enter the ASN of the neighbor
    Inbound Filter	Select an Inbound filer from the drop-down list
    Outbound Filter	Select an Outbound filer from the drop-down list

    Note: When overriding and configuring BGP neighbors at the Edge level, any Profile-level filters associated with the neighbors is removed when users switch the Edge from one profile to another. So at the Edge level, users must make sure to re-associate the filters with the BGP neighbors after switching the Edge profile.

    Additional Options – Select the View all to configure the following additional settings:

    Table 8. Additional Options and Descriptions

    Option	Description
    Max-hop	Enter the number of maximum hops to enable multi-hop for the BGP peers. The range is from 1 to 255 and the default value is 1. Note: This field is available only for eBGP neighbors, when the local ASN and the neighboring ASN are different. With iBGP, when both ASNs are the same, multi-hop is inherent by default and this field is not configurable.
    Local IP	Local IP address is the equivalent of a loopback IP address. Enter an IP address that the BGP neighborships can use as the source IP address forth outgoing packets. If users do not enter any value, it uses the IP address of the physical Interface as the source IP address. Note: For eBGP, this field is available only when Max- hop count is more than 1. For iBGP, it is always available as iBGP is inherently multi-hop.
    Uplink	Flag the neighbor type to Uplink. Select this option if users use the neighbor as the WAN overlay toward MPLS. The system uses this flag to determine if the site becomes a transit site (such as an SD-WAN Hub) by propagating routes learned over an SD-WAN overlay to a WAN link toward MPLS. If users want to establish the site as a transit site, users must also select the Overlay Prefix Over Uplink check box in the Advanced Settings area.
    Allow AS	Select the checkbox to allow the BGP routes to receive and process even if the Edge detects its own ASN in the AS-Path.
    Default Route	The Default Route adds a network statement in the BGP configuration to advertise the default route to the neighbor.
    Enable BFD	Enables subscription to existing BFD session for the BGP neighbor.
    Keep-Alive	Enter the keep-alive timer in seconds, which is the duration between the keep-alive messages sent to the peer. The range is from 0 to 65535 seconds. The default value is 60 seconds.
    Hold Timer	Enter the hold timer in seconds. If users don't receive the keep-alive message within the specified time, the peer is down. The range is from 0 to 65535 seconds. The default value is 180 seconds.
    Connect	Enter the time interval to try a new TCP connection with the peer if it detects the TCP session is not passive. The default value is 120 seconds.
    MD5 Auth	Select the checkbox to enable BGP MD5 authentication. Administrators typically use this option in legacy or federal networks, where they commonly implement BGP MD5 as a security measure for BGP peering.
    MD5 Password	Enter a password for MD5 authentication. Note: Starting from the 4.5 release, the use of the special character < in the password is no longer supported. In cases where users have already used < in their passwords in previous releases, they must remove it to save any changes on the page.

     

13. Select the + to add more BGP neighbors. Over Multi-hop BGP, the system might learn routes that require recursive lookup. These routes have a next-hop IP which is not in a connected subnet, and do not have a valid exit Interface. In this case, the routes must have the next-hop IP resolved using another route in the routing table that has an exit Interface. When there is traffic for destination that needs these routes to look up, routes requiring recursive lookup resolves to a connected Next Hop IP address and Interface. Until the recursive resolution happens, the recursive routes point to an intermediate Interface.
    For additional information about Multi-hop BGP Routes, see the Remote Diagnostic Tests on Edges section in the VeloCloud SD-WAN Troubleshooting Guide.
14. Navigate to Advanced Settings and select the down arrow to open the Advanced Settings section.

    

15. Configure the following advanced settings and globally apply them to all the BGP neighbors with IPv4 addresses.

    Table 9. Advanced Settings - Options and Descriptions

    Option	Description
    Overlay Prefix	Select the check box to redistribute the prefixes learned from the overlay.
    Turn off AS-Path carry over	The user should leave this option unchecked by default. Select the check box to turn off AS-PATH Carry Over. In certain topologies, turning off AS-PATH Carry Over will influence the outbound AS-PATH to make the L3 routers prefer a path towards an Edge or a Hub. Warning: When users turn off AS-PATH Carry Over, users must tune their network carefully to avoid routing loops.
    Connected Routes	Select to redistribute all the connected Interface subnets.
    OSPF	Select the checkbox to enable OSPF redistribute into BGP.
    Set Metric	When users enable OSPF, enter the BGP metric for the redistributed OSPF routes. The default value is 20.
    Default Route	Select to redistribute the default route only when Edge learns the BGP routes through overlay or underlay. When users select the Default Route option, the Advertise option is available as Conditional.
    Overlay Prefixes over Uplink	Select the checkbox to propagate routes learned from overlay to the neighbor with uplink flag.
    Networks	Enter the network address in IPv6 format that BGP advertises to the peers. Select (+) to add more network addresses.

    When users enable the Default Route option, the BGP routes are advertised based on the Default Route selection globally and per BGP neighbor.

    Table 10. Default Route Advertising Options

    Default Route Selection		Advertising Options
    Global	Per BGP Neighbor
    Yes	Yes	The per BGP neighbor configuration overrides the global configuration and hence the system always advertises the default route to the BGP peer.
    Yes	No	BGP redistributes the default route to its neighbor only when the Edge learns an explicit default route through the overlay or underlay network.
    No	Yes	The system advertises the default route to the BGP peer.
    No	No	The system does not advertise the default route to the BGP peer.

     

16. Select the IPv6 tab to configure the BGP settings for IPv6 addresses. Enter a valid IPv6 address of the BGP neighbor in the Neighbor IP field.
    The BGP peer for IPv6 supports the following address format:

    • Global unicast address (2001:CAFE:0:2::1)
    • Unique Local address (FD00::1234:BEFF:ACE:E0A4)
17. Configure the other settings as required.
    Note: The Local IP address configuration is not available for IPv6 address type.
18. Select Advanced to configure the following advanced settings, which globally apply to all the BGP neighbors with IPv6 addresses.

    Table 11. Advanced Options and Descriptions

    Option	Description
    Connected Routes	Select the checkbox to redistribute all the connected Interface subnets.
    Default Route	Select the checkbox to redistribute the default route only when Edge learns the BGP routes through overlay or underlay. When users select the Default Route option, the Advertise option is available as Conditional.
    Networks	Enter the network address in IPv6 format that BGP will be advertising to the peers. Select the Plus (+) Icon to add more network addresses.

    The Route Summarization feature is available in the 5.2 release, for an overview and use case of this functionality, see Route Summarization. For configuration details, follow the Steps 19 to 24.
19. Select +Add in the Route Summarization area. It adds a new row to the Route Summarization area.

    

20. Under the Subnet column, enter the network range that users want to summarize in the A.B.C.D/M format and the IP subnet.
21. Under the AS Set column, select Yes if applicable.
22. Under the Summary Only column, select the Yes checkbox to allow only the summarized route to be sent.
23. Add additional routes, if necessary, by selecting +Add. To Clone or Delete a Route Summarization, use the appropriate buttons, located next to +Add. The BGP Settings section displays the BGP configuration settings.
24. Select Save Changes when complete to save the configuration.
    Note: When users configure BGP settings for a profile, the configuration settings are automatically applied to the SD-WAN Edges associated with the profile.

Users can override the inherited Profile settings at the Edge level when configuring BGP from the Edge to Underlay Neighbors.

1. In the SD-WAN service of the Enterprise portal, select Configure > Edges . The Edges page displays the configured Edges.
2. Select on an Edge or select View in the Device column of the Edge.
3. Go to the Routing & NAT section and select the arrow next to BGP to expand.
4. The BGP settings configured for the associated Profile are displayed. If required, users can select Override and modify the BGP Settings.
   Note: Overriding and configuring BGP neighbors at the Edge level removes any Profile-level filters associated with the neighbors when users switch the Edge from one profile to another. At the Edge level, users must re-associate the filters with the BGP neighbors after switching the Edge profile.
5. In addition to the BGP Settings configured for a Profile, users can select an Edge Interface configured in the segment as the source Interface for BGP. For the IPv4 address type, users can select only the Loopback Interface as Source Interfacee, and for the IPv6 address type, users can select any Edge Interface as the Source Interface. This field becomes available:
   • Only when users choose to override the BGP Settings at the Edge level.
   • For eBGP, only when Max-Hop count is greater than 1. For iBGP, it is always available as iBGP is inherently multi-hop.

   Important:

   • Users cannot select an Edge Interface if users have already configured a local IP address in the Local IP field.
   • Users cannot configure a local IP address if users have selected an Edge Interface in the Source Interface list.
6. Select Save Changes to save the modified configuration.

The system supports only eBGP when configuring BGP over IPsec..

1. Go to Configure > Network Services and then under Non SD-WAN Destinations, expand Non SD-WAN Destinations via Gateway.
   Note: The New NSD via Gateway option appears only when there are no items in the table. Follow Step 2 and Step 3 to create a new Non SD-WAN Destination.

   

2. Select +New to create a new Non SD-WAN Destination.

   

3. In Non SD-WAN Destinations via Gateway, configure the following fields:

   Table 17. Non SD-WAN Destinations via Gateway - Options and Descriptions

   Option	Description
   Name	Enter a name for the Non SD-WAN Destination in the text box.
   Type	Select an IPsec tunnel type from the menu.
   Tunnel Mode	Active/ Hot-Standby mode supports to set up a maximum of 2 tunnel endpoints or Gateways.
   	Active/Active mode supports to set up a maximum of 4 tunnel endpoints or Gateways. All Active tunnels can send and receive traffic through ECMP.
   VPN Gateway 1	Enter a valid IP address.
   VPN Gateway 2	Enter an optional valid IP address.

4. Select Create to add the new destination.

   

5. In the Non SD-WAN Destinations via Gateway area, slide the grey bar to the far right to the BGP column.

   Select the Edit link under the BGP column.

   If the Edit link does not display under the BGP column, see the section Configure a Tunnel Between a Branch and a Non SD-WAN Destinations via Edge to enable an Edge to Non SD-WAN via Gateway.

   After selecting the Edit link under the BGP column, the Edit BGP dialog displays.

6. Toggle the BGP Activated radio button to the right to turn it green.
7. Select +Add to create one or more filters. These filters are applied to the neighbor to deny or change the attributes of the route. The same filter can be used for multiple neighbors.
8. Configure the options in the Filter List area:

   

   

   Table 18. Filter Rules - Options and Descriptions

   Option	Description
   Filter Name	Enter a descriptive name for the BGP filter.
   Match Type	Choose the type of the routes to match with the filter: Prefix for IPv4 or IPv6- Choose to match with a prefix for IPv4 or IPv6 address and enter the corresponding prefix IP address in the Value field. Community- Select to match with a community and enter the community string in the Value field. AS Path - Match routes using the user-provided AS path regular expression. Metric- Match routes using the user-provided MED value. Local preference- Match routes using the user-provided local preference value.
   Match Value	Enter the subnet value.
   Exact Match	It performs filter action only when the BGP routes match exactly with the specified prefix or community string. By default, this option is enabled.
   Action Type	Choose the action to perform when the BGP routes match with the specified prefix or the community string. Users can either permit or deny the traffic.
   Action Set	When the BGP routes match the specified criteria, users can set to route the traffic to a network based on the attributes of the path. Select one of the following options from the drop-down list: None- The attributes of the matching routes remain the same. Local Preference- It routes matching traffic to the path associated with the specified local preference. Community- It filters the matching routes by the specified community string. Users can also select Community Additive to enable the additive option, which appends the community value to existing communities. Metric- It routes matching traffic to the path associated with the specified metric value. AS-Path-Prepend- Allows pre-pending multiple entries of Autonomous System (AS) to a BGP route. As-Path-Exclude - AS path exclude is a new set option, using which users can remove specific Autonomous System (AS) numbers from a route’s AS path. When users exclude ASNs, the system deletes all occurrences of the specified numbers, regardless of where they appear in the sequence.

   AS path Regex match option

   By using the AS Path Regex match type, administrators can filter BGP routes based on the autonomous systems they have traversed, applying a Permit or Deny action whenever a route's AS path matches the defined pattern. This approach enables the creation of sophisticated policies based on a route’s origin or transit history rather than just its prefix, allowing the system to accept routes from specific providers, block untrusted transit networks, or match defined ranges of ASNs.

   Table 19. Supported AS Path Regex Characters:

   Character	Meaning / Use	Example	Matches Example AS Paths
   0–9	Digits used in AS numbers	^65001$	65001
   ^	Start of AS path	^65001	65001 65002 65003
   $	End of AS path	65001$	65003 65002 65001
   _	AS boundary (start, end, space, comma, brace, or parentheses)	_65001_	65000 65001 65002
   			65001
   |	Logical OR (alternation)	^(65001|65002)$	65001
   			65002
   []	Character class (any one character in set)	^6500[12]$	65001
   			65002
   {}	Repeat count	[0-9]{5}	65000
   ()	Grouping (for OR or repetition)	(65001|65002) 65003	65002 65003 65004
   (space)	AS separator	^65001 65002	65001 65002 65003
   *	Zero or more repetitions	[0-9]*	65001
   			123
   +	One or more repetitions	[0-9]+	65001
   .	Any single character	6500.	65000–65009
   ?	Zero or one occurrence	6500[1-2]?	6500
   			65001
   			64002
   -	Range indicator (inside [])	^65[0-9][0-9]$	6500–6599
   \	Escape special characters (treat literally) Usually matches confederations and AS_SET	_\{65200_	65100 {65200 65300}
   		_\(64512\)	65001 (64512) 65001

   AS Path Exclude

   AS path exclude is a new set option, using which users can remove specific Autonomous System (AS) numbers from a route’s AS path. When users exclude ASNs, the system deletes all occurrences of the specified numbers, regardless of where they appear in the sequence.

   Example:

   For instance, if a user provides input as "100 300" and a route's AS path is "100 200 300 400", the resulting AS path after filtering will be "200 400"

9. Select (+) to add more matching rules for the filter. Repeat the procedure to create more filters.

   

    

   

   Note: The system assigns these BGP neighbors to their respective tunnels exclusively to establish neighborship and facilitate subsequent control exchanges. This configuration ensures that all such communication occurs solely over the designated tunnels.
10. In the BGP Editor window, configure the BGP settings for the Primary and Secondary Gateways.
    Note: The Secondary Gateway option is available only if users have configured a secondary Gateway for the corresponding Non SD-WAN Destination.

    Note: In a customer deployment where users configure a Non VeloCloud SD-WAN Destination (NSD) via Gateway with redundant tunnels, the system may exhibit specific path preferences. If the Primary and Secondary Gateways advertise a prefix with an equal AS path to the Primary and Secondary NSD tunnels, the Primary NSD tunnel prefers the redundant Gateway path over the Primary Gateway.
11. In the Primary Cloud Gateway section, enter the local ASN and the Router ID.
12. Scroll down to the Neighbors area and select +Add.
13. Configure the following settings in the Neighbors area:

    

     

    Table 20. Neighbors - Options and Descriptions

    Option	Description
    Local ASN	Enter the local Autonomous System Number (ASN)
    Router ID	Enter the BGP Router ID.
    Neighbor IP	Enter the IP address of the NSD neighbor.
    ASN	Enter the ASN for the NSD neighbor.
    Inbound Filter	Select an Inbound filter from the list.
    Outbound Filter	Select an Outbound filter from the list.
    Additional Options – Select View All to configure the following additional settings:
    Local IP	Local IP is mandatory for configuring Non SD-WAN Neighbors. Local IP address is the equivalent of a loopback IP address. Enter an IP address that the BGP neighborships can use as the source IP address for the outgoing packets.
    Max-hop	Enter the number of maximum hops to enable multi-hop for the BGP peers. For the 5.1 release and later, the range is from 2 to 255 and the default value is 2. Note: When upgrading to the 5.1 release, any max-hop value of 1 automatically updates to a max-hop value of 2. Note: This field is available only for eBGP neighbors, when the local ASN and the neighboring ASN are different. With iBGP, when both ASNs are the same, it deactivates the multi-hop by default and this field is not configurable.
    Allow AS	Select the check box to allow the Edge to receive and process BGP routes even if it detects its own ASN in the AS-Path.
    Default Route	The Default Route adds a network statement in the BGP configuration to advertise the default route to the neighbor.
    Enable BFD	Enables subscription to existing BFD session for the BGP neighbor. Note: The system does not support single-hop BFD sessions for BGP over IPsec with NSD Neighbors; however, the Edge supports multi-hop BFD for these configurations. When setting up NSD-BGP sessions, users must provide a Local IP. The SD-WAN Edge treats only the directly connected Interface IPs as single-hop BFD sessions.
    Keep Alive	Enter the keep alive timer in seconds, which is the duration between the keep alive messages that are sent to the peer. The range is from 0 to 65535 seconds. The default value is 60 seconds.
    Hold Timer	Enter the hold timer in seconds. If the Edge does not receive a Keep Alive message within the specified time, the system considers the peer to be down. The range is from 0 to 65535 seconds. The default value is 180 seconds.
    Connect	Enter the time interval to try a new TCP connection with the peer if it detects the TCP session is not passive. The default value is 120 seconds.
    MD5 Auth	Select the check box to enable BGP MD5 authentication. Users typically use this option in legacy or federal networks to secure BGP peering.
    MD5 Password	Enter a password for MD5 authentication. Note: Starting from the 4.5 release, it does not support special character < in the password. In cases where users have already used < in their passwords in previous releases, they must remove it to save any changes on the page.

    The Neighbors area displays the configured Neighbors

    

    Note: In multi-hop BGP, the system might learn routes that require recursive lookups. These routes have a next-hop IP address that is not in a connected subnet and do not have a valid exit Interface. In this case, the routes must have the next-hop IP resolved using another route in the routing table that has an exit Interface. When there is traffic for a destination that needs these routes to be looked up, routes requiring recursive lookup will get resolved to a connected Next Hop IP address and Interface. Until the recursive resolution happens, the recursive routes point to an intermediate Interface. For additional information about Multi-hop BGP Routes, see the Remote Diagnostic Tests on Edges section in the VeloCloud SD-WAN Troubleshooting Guide.
14. Select Save Changes.

    Route Summarization

    The Route Summarization feature is available in the 5.2 release, for an overview and use case of this functionality, see Route Summarization. For configuration details, follow the steps below.

15. Scroll down to the Route Summarization area.
16. Select +Add in the Route Summarization to add a new row to the Route Summarization table. Configure route summarization, as described in the table below.

    

    Table 21. Route Summarization - Options and Descriptions

    Option	Description
    Filter Name	Enter a descriptive name for the BGP filter.
    Subnet	Enter the IP subnet.
    AS Set	Generate AS set path information from the summarized routes (while advertising the summary route to the peer). Under the AS Set column, select Yes if applicable.
    Summary Only	Select Yes to allow only the summarized route to be sent.

17. Add additional routes, if necessary, by selecting +Add. To Clone or Delete a route summarization, use the appropriate buttons, located next to +Add.
    The BGP Settings section displays the BGP configuration settings.
18. Select Save Changes when complete to save the configuration.
    Note:

    • Only Gateways running version 6.0 or later have an option to configure up to 4 tunnels per VPN type. In addition, those tunnels intended to be a Non SD-WAN gateway can operate in either AA or A-HS mode to achieve the user's load-sharing/balancing preferences.
    • For gateways running a version earlier than 6.0, the system interprets all active-active configurations as active-hotstandby. In this scenario, the system designates Tunnel 1 as active and Tunnel 2 as hot-standby.

Users can run Remote Diagnostics tests to view the logs of the BGP sessions and use the log information for troubleshooting purposes.

1. In the SD-WAN service of the Enterprise portal, select Diagnostics > Remote Diagnostics .
2. The Remote Diagnostics page displays all the active Edges.
3. Select the Edge that users want to troubleshoot. The Edge enters live mode and displays all the possible Remote Diagnostics tests than users can run on the Edge.
4. For troubleshooting BGP sessions, scroll to the following sections and run the tests:
   • Troubleshoot BGP- List BGP Redistributed Routes – Run this test to view routes redistributed to BGP neighbors.
   • Troubleshoot BGP- List BGP Routes – Run this test to view the BGP routes from neighbors. Users can enter IPv4 or IPv6 prefix to view specific BGP routes or leave the prefix empty to view all the BGP routes.
   • Troubleshoot BGP- List Routes per Prefix – Run this test to view all the Overlay and Underlay routes for a specific IPv4 or IPv6 prefix and the related details
   • Troubleshoot BGP- Show BGP Neighbor Advertised Routes – Run this test to view the BGP routes advertised to a neighbor.
   • Troubleshoot BGP- Show BGP Neighbor Learned Routes – Run this test to view all the accepted BGP routes learned from a neighbor after filters.
   • Troubleshoot BGP- Show BGP Neighbor Received Routes – Run this test to view all the BGP routes learned from a neighbor before filters.
   • Troubleshoot BGP- Show BGP Neighbor Details – Run this test to view the details of BGP neighbor.
   • Troubleshoot BGP- Show BGP Routes per Prefix – Run this test to view all the BGP routes and their attributes for the specified prefix.
   • Troubleshoot BGP- Show BGP Summary – Run this test to view the existing BGP neighbor and received routes.
   • Troubleshoot BGP- Show BGP Table – Run this test to view the BGP table.
   • Troubleshoot BGPv6- Show BGPv6 Neighbor Advertised Routes – Run this test to view the BGPv6 routes advertised to a neighbor.
   • Troubleshoot BGPv6- Show BGPv6 Neighbor Learned Routes – Run this test to view all the accepted BGPv6 routes learned from a neighbor after filters.
   • Troubleshoot BGPv6- Show BGPv6 Neighbor Received Routes – Run this test to view all the BGPv6 routes received from a neighbor before filters.
   • Troubleshoot BGPv6- Show BGPv6 Neighbor Details – Run this test to view the details of BGPv6 neighbor.
   • Troubleshoot BGPv6- Show BGPv6 Routes per Prefix – Run this test to view all the BGPv6 routes for the prefix and their attributes.
   • Troubleshoot BGPv6- Show BGPv6 Summary – Run this test to view the existing BGPv6 neighbor and received routes.
   • Troubleshoot BGPv6- Show BGPv6 Table – Run this test to view the details of BGPv6 table.

   For additional information about all the supported BGP related Remote Diagnostics tests, see the Remote Diagnostic Tests on Edges section in the VeloCloud SD-WAN Troubleshooting Guide.

VeloCloud SD-WAN enables the configuration of Bidirectional Forwarding Detection (BFD) sessions to detect route failures between two connected entities.

1. In the SD-WAN service of the Enterprise portal, select Configure > Profiles .
2. Select the Device icon for a profile, or select a profile, then select the Device tab.
3. On the Device tab, navigate to the Routing and NAT section and select the arrow next to the BFD area to open it.
4. Turn the BFD slider to the ON position.
5. Configure the following settings:

   Table 22. Routing and NAT - Options and Descriptions

   Option	Description
   Peer Address	Enter the IPv4 address of the remote peer to initiate a BFD session. Enter a locally configured IPv4 address for the peer listener. This address sends the packets. Note: Select the IPv6 tab to configure IPv6 addresses for the remote peer and the peer listener.
   Local Address	For IPv6, the local and peer addresses support only the following format: IPv6 global unicast address (2001:CAFE:0:2::1) IPv6 unique local address (FD00::1234:BEFF:ACE:E0A4)
   Multihop	Select the checkbox to enable multihop for the BFD session. While BFD on Edge and Gateway supports directly connected BFD Sessions, users need to configure BFD peers in conjunction with multihop BGP neighbors. The multihop BFD option supports this requirement. The administrator must enable multihop for the BFD sessions associated with NSD-BGP neighbors.
   Detect Multiplier	Enter the detection time multiplier. The system multiplies the remote transmission interval by this value to determine the detection timer for connection loss. The range spans from 3 to 50, with a default value of 3.
   Receive Interval	Enter the minimum time interval, in milliseconds, at which the system can receive the control packets from the BFD peer. The range is from 300 to 60000 milliseconds, and the default value is 300 milliseconds.
   Transmit Interval	Enter the minimum time interval, in milliseconds, at which the local system can send the BFD control packets. The range is from 300 to 60000 milliseconds, and the default value is 300 milliseconds.

    

6. Select the (+) icon to add details of more peers.
7. Select Save Changes.

   

   Configuring BFD rules for a profile automatically applies those rules to all associated Edges. If required, users can override the configuration for a specific Edge. See Configure BFD for Edges for additional information.

   VeloCloud SD-WAN supports configuring BFD for BGP and OSPF.

   • To enable BFD for BGP, see Configure BFD for BGP for Profiles.
   • To enable BFD for OSPF, see Configure BFD for OSPF.
   • To view the BFD sessions, see Monitor BFD Sessions.
   • To view the BFD events, see Monitor BFD Events.
   • For troubleshooting and debugging BFD, see Troubleshooting BFD.

1. In the SD-WAN service of the Enterprise portal, select Configure > Edges .
2. Select the Device icon next to an Edge, or select an Edge and select the Device tab.
3. On the Device tab, scroll down to BFD Rules.
4. Select Override to modify the BFD configuration settings for the selected Edge.

   

5. Select Save Changes.
   VeloCloud SD-WAN supports configuring BFD for BGP and OSPF.

   • To enable BFD for BGP, see Configure BFD for BGP for Profiles.
   • To enable BFD for OSPF, see Configure BFD for OSPF.
   • To view the BFD sessions, see Monitor BFD Sessions.
   • To view the BFD events, see Monitor BFD Events.
   • For troubleshooting and debugging BFD, see Troubleshooting BFD.

Configure Bidirectional Forwarding Detection (BFD) for Border Gateway Protocol (BGP) on SD-WAN Profiles.

1. In the SD-WAN service of the Enterprise portal, select Configure > Profiles .
2. Select the Device icon for a profile, or select a profile then select the Device tab.
3. On the Device tab, navigate to the Routing & NAT section and select the arrow next to the BGP area to open it.
4. Turn the BDF slider to the ON position.
5. In the BGP Editor window, select View All in the Additional Options column for a BGP neighbor then select Enable BFD. Users can enable a BFD subscription for multiple BGP neighbors, including NSD Neighbors in the 4.3 release.
   Note: Ensure to configure Multihop as Multihop BFD for NSD BGP Neighbors in the 4.3 release. For additional information about NSD Neighbors, see Configure BGP Over IPsec from Edge to Non SD-WAN Neighbors.

   

   Note: BGP over Internet Protocol Security (IPsec) from the SD-WAN Edge does not support a single-hop BFD session.
6. Configure the other settings as required then select OK.

   When users enable BFD for BGP settings in a profile, the setting automatically applies to the Edges associated with the profile. If required, users can override the configuration for a specific Edge. See Configure BFD for BGP for Edges for additional information.

   When a BGP neighbor receives a "BFD session down" update, the BGP session terminates immediately. The system then flushes all routes learned through that peer without waiting for the keepalive timer to expire.

Enterprise users can override the inherited settings at the Edge level for Bidirectional Forwarding Detection (BFD) for Border Gateway Protocol (BGP).

1. In the SD-WAN service of the Enterprise portal, select Configure > Edges .
2. Select the Device icon next to an Edge, or select an Edge then select the Device tab.
3. On the Device tab, navigate to the Routing & NAT section then select the arrow next to the BGP area to open it.
4. Select Override and move the slider to the ON position to modify the BGP settings for the selected Edge.

   

1. In the SD-WAN service of the Enterprise portal, select Configure > Profiles .
2. Select a profile then select View from the Device column of the profile. The Device page for the selected profile appears.
3. Navigate to Connectivity then select Interfaces to display the Edge models available for the selected Profile.
4. In the Interfaces section, select an Edge model to view the interfaces available in the Edge and select an interface to edit the settings.
5. In the Interface edit window, users can configure OSPF settings under IPv4/IPv6 Settings. Select OSPF, and then select the OSPF Area from the list.

   

6. Expand Advanced Settings then in Custom Settings, select Enable BFD.
7. Configure the other settings as required then select Save.

   Enabling BFD for an OSPF area in a profile automatically applies the setting to all associated Edges. If required, users can override the configuration for a specific Edge. See Configure BFD for OSPF for Edges for additional information.

   When an OSPF neighbor receives a "BFD session down" update, the OSPF session terminates immediately. The neighbor then flushes all routes without waiting for the keepalive timer to expire.

Enterprise users can modify the inherited Profile settings at the Edge level for Bidirectional Forwarding Detection (BFD) for Open Shortest Path First (OSPF).

1. In the SD-WAN service of the Enterprise portal, select Configure > Edges .
2. Select the Edge users want to configure BFD for OSPF settings then select the View link in the Device column of the Edge. The Device page for the selected Edge appears.
3. Navigate to Connectivity then select Interfaces.
4. In the Interfaces section, select an interface to edit the settings.
5. In the Interface edit window, users can configure OSPF settings under IPv4/IPv6 Settings. Select OSPF then select the OSPF Area from the list.

   

6. Expand Advanced Settings then on the Custom Settings tab, select Enable BFD.
7. Configure the required settings for the Edge as required then select Save.

1. In the SD-WAN service of the Enterprise portal, select Configure > Network Services .
2. In the Non SD-WAN Destinations via Gateway area, select Edit in the BFD column that corresponds to the Non SD-WAN Destination.

   

3. In the BFD Editor window, move the BFD Activated slider to the right to turn it on to configure the BFD settings for the Primary and Secondary Gateways.
4. Configure the BFD settings:
   Note: The Secondary Gateway option is available only if users have configured a secondary Gateway for the corresponding Non SD-WAN Destination.

   

    

   Table 23. BFD Settings - Options and Descriptions

   Field	Description
   Peer Address	Enter the IP address of the remote peer to initiate a BFD session.
   Local Address	Enter a locally configured IP address for the peer listener. The system uses this address to send the packets.
   Multihop	The VeloCloud SD-WAN does not support this option for Gateways.
   Detect Multiplier	Enter the detection time multiplier. The system multiplies the remote transmission interval by this value to determine the detection timer for connection loss. The range spans from 3 to 50, with a default value of 3.
   Receive Interval	Enter the minimum time interval, in milliseconds, at which the system can receive the control packets from the BFD peer. The range is from 300 to 60000 milliseconds, and the default value is 300 milliseconds.
   Transmit Interval	Enter the minimum time interval, in milliseconds, at which the local system can send the BFD control packets. The range is from 300 to 60000 milliseconds, and the default value is 300 milliseconds.

   Note: BFD is supported only on VLAN Trunking Protocol (VTP) tunnels.

1. In the SD-WAN service of the Enterprise portal, select Monitor > Routing .
2. In the Routing screen, select the BFD tab.
3. Select Filter next to Search and opt to filter the details by different categories.

   The Edge BFD Sessions table displays the BFD Sessions of the Edge and the Gateway.

   

   The BFD Sessions include the following details for Edges and Gateways:

   • Name of the Edge or Gateway
   • Segment name
   • Peer IPv4 or IPv6 address
   • Local IPv4 or IPv6 address
   • State of the BFD session
   • Remote and Local timers
   • Number of Events
   • Duration of the BFD session

   Select an Event number to view the details of the event.

Run Remote Diagnostics tests to view the logs of the Bidirectional Forwarding Detection (BFD) sessions and utilize the log information for troubleshooting purposes.

1. In the SD-WAN service of the Enterprise Portal, select Diagnostics > Remote Diagnostics .
2. The Remote Diagnostics page displays all the active Edges.
3. Select the Edge that users want to troubleshoot. The Edge enters live mode and displays all the possible Remote Diagnostics tests that users can run on the Edge.
4. For troubleshooting BFD sessions, move through to the following sections and run the tests:
   • Troubleshoot BFD- Show BFD Peer Status - Choose the Segment from the drop-down list. Enter the Peer and Local IP addresses of an already configured BFD session. Select Run to view the details of the BFD peers.
   • Troubleshoot BFD- Show BFD Peer counters - Choose the Segment from the drop-down list. Enter the Peer and Local IP addresses of an already configured BFD session. Select Run to view the details of the counters of the BFD peers.
   • Troubleshoot BFD- Show BFD Setting - Select Run to view the details of BFDv4 settings and the status of neighbors.
   • Troubleshoot BFD6- Show BFD6 Setting - Select Run to view the details of BFDv6 settings and the status of neighbors.

   For additional information about all the supported BFD-related Remote Diagnostics tests, see the Remote Diagnostic Tests on Edges section in the VeloCloud SD-WAN Troubleshooting Guide.