Configure Routing
From the Routing tab, you can configure static routing and the EBGP routing protocols. You can customize route redistribution for each routing protocol.
Configure Static IP Routes
You can manually configure static routes to specify the path that data packets take to reach a destination. Note that if you create static routes to use to leak routes between VRFs, you must also create a firewall rule that allows this traffic to pass through. You do this by selecting match criteria and the correct zone scope interface VRF names for both VRFs.
To configure a static IP route to a destination:
- Click Configure in the left menu bar to open the Configure dashboard.
- Hover over the device in the honeycomb, and then click Configure to open the site information window.
- Click the Routing tab, and then click the Static tab. Enter information for the following fields.
Field Description LAN Direct Redistribute Slide the toggle to enable redistribute to advertise the LAN Direct route to SD-WAN. Interface Select the interface on which to enable static routing. Redistribute Click Redistribute to advertise the static IP route added to WAN interface to redistribute to SD-WAN. If not selected, the static IP route is redistributed to LAN-VR. Destination (IPv4/Mask) Enter the destination IP address and subnet mask. Next Hop Select the next hop:
- Address—Click, and then enter the next-hop IP address. To configure a static route with the Discard or Reject option on a LAN virtual router, the next- hop IP address must be 0.0.0.0.
- Discard—For LAN virtual router, silently drop packets that match the route without sending an ICMP unreachable message. This is the default.
- Reject—For LAN virtual router, drop packets that match the route and send an ICMP unreachable message.
- IPsec—Click, and then select an IPsec tunnel. To configure IPsec in routing, you must add IPsec from the WAN network. To create an IPsec tunnel, see Configure IPsec VPN Settings (Tunnels).
- Routing Instance (VRF)—Click, and then select a routing instance to resolve the static route next hop to the same or to a different routing instance.
Name Enter the name of the static route for route redistribution. - Address—Click, and then enter the next-hop IP address. To configure a static route with the Discard or Reject option on a LAN virtual router, the next- hop IP address must be 0.0.0.0.
- Click Advance Configurations (Customized) to configure advanced static routing settings, and then enter information for the following fields.
Field Description Metric Enter the cost to reach the destination network. The metric is used to choose between multiple paths learned with the same routing protocol.
Range: 1 through 4294967295
Preference Enter the administrative distance (AD) or route preference value of the static route. You can assign a preference for each route. The preference is used to choose between multiple paths learned from different routing protocols.
Range: 1 through 255
Enable BFD (Bidirectional Forwarding Detection) (Group of Fields) Click to enable the use of BFD to monitor the next hop that is configured for the static route. If the BFD monitoring fails, the route is withdrawn from the routing table. Note that if you configure one or more of the Enable ICMP, Monitor, or Enable BFD fields simultaneously, and if any one of the monitors fails, the static route is withdrawn from the routing table. You cannot configure both BFD and monitor object for a static route. - Minimum Receive Interval (Required)
Enter the minimum time interval to receive routes, in milliseconds.
Range: 1 through 255000 milliseconds
- Multiplier
Enter the multiplier value to use to calculate the final minimum receive interval and minimum transmit interval.
Range: 1 through 255
- Minimum Transmit Interval (Required)
Enter the time after which routes can be retransmitted, in milliseconds.
Range: 1 through 255000 milliseconds
- Click Continue.
- Click the
icon. - Click Save and then Publish.
To delete the static route entry:
- Configure the static IP route with the IP address that you want to delete. See Configure Static IP Route.
- Click the
icon, and then click Publish.
Configure EBGP
External BGP (eBGP) is an exterior gateway protocol used for exchanging routing information between gateway hosts in a network. EBGP is the protocol commonly used between gateway hosts on the Internet.
You can configure an outbound routing policy that controls and filters prefixes that are advertised to BGP peers, and an inbound routing policy that controls and filters prefixes that are received from BGP peers.
- Outbound policy—Advertises all routes when there is no policy configured, by default. If a policy is configured, only matched routes are advertised or denied based on the set action. All other routes are denied.
- Inbound policy—Accepts all routes when there is no policy configured, by default. If a policy is configured, only matched routes will be accepted or denied based on the set action. All other routes are denied. After application of the policy, the routes are automatically advertised into the enterprise VPN network.
You use 0.0.0.0/0 as a wildcard to match all IP prefixes.
To configure eBGP:
- Click Configure in the left menu bar to open the Configure dashboard.
- Hover over the device in the honeycomb, and then click Configure to open the site information window.
- Click the Routing tab, and then click the EBGP tab. Enter information for the following fields.
Field Description Interface Select the interface to which to connect to the BGP neighbor (peer). BFD Click to enable BFD, to provide fast forwarding-path failure detection and decrease reconvergence time. Neighbor Enter the IP address of the BGP peer. Redistribute Click Redistribute to advertise the BGP IP prefixes learnt from WAN transport VRF to default LAN VRF and other SD-WAN branches. If not selected, the route is redistributed to LAN VRF. The other SD-WAN branches do not get the routes. Password Enter the password to authenticate the BGP instance. Local AS Enter the local AS number.
Range: 0 through 4294967295 or (0 through 65535).(0 through 65535)
AS Override Click to replace neighbor AS numbers with the local AS numbers from the AS path. Remote AS Enter the remote peer's AS number.
Range: 0 through 4294967295 or (0 through 65535).(0 through 65535)
Remove All Private AS# Click to remove all private AS numbers from a prefix's AS path before redistributing the same to BGP peers. - Click the
icon. - In the BGP profile section, you can monitor, edit, or delete a BGP profile.
- Click the
Edit icon to edit a profile. - Click the
Delete icon to delete a profile. - Click the
Monitor icon to go to the Monitor > Network screen and monitor a BGP routing instance. For more information, see Monitor BGP Routing Status.
- Click the
- Click Outbound Policy to configure a routing policy that controls and filters prefixes that are advertised to the BGP peer.
- If necessary, click Reorder Rules to enter rule reorder mode.
- To change a rule order, click the colored circle and drag the rule to a different spot in the rule set. The rule numbers are updated automatically.
- Click Save Reordered Rules to save the changes to the Titan cloud.
- Click the
icon to add a new outbound routing policy. Enter information for the following fields.
Field Description Rule Name Enter a name for the rule. Match Criteria Select one or more match criteria:
- Click the Prefix tab, and then enter the IP prefix to match.
- Click the Community tab, and then enter the BGP community string to match. Enter the string in one of the following formats:
- 2-byte or 4-byte decimal number
- 2-byte decimal number:2-byte decimal number
- Regular expression pattern
Action Select the action to apply to matched prefixes. - Allow
Click to allow the prefixes that match the match criteria.
If you add a BGP peer for a WAN interface, you can add the following additional criteria:
- Community Value—Enter the BGP community value to set. The value can be set in the format 2-byte decimal number:2-byte decimal number. For example, <0-65535>:<0-65535>.
- Local AS Path Prepend—Enter the number of times to prepend the local AS number to the AS path.
Range: 1 through 255
If you add a BGP peer for a LAN interface, you can add the following additional criteria:
- Community Value—Enter the BGP community value to set. The value can be set in the format 2-byte decimal number:2-byte decimal number. For example, <0-65535>:<0-65535>.
- Local AS Path Prepend—Enter the number of times to prepend the local AS number to the AS path.
Range: 1 through 255
- Deny
Click to deny the prefixes that match the match criteria. - Click the
icon. - Click Inbound Policy to configure a routing policy that controls and filters prefixes that are received from the BGP peer.
- If necessary, click Reorder Rules to enter rule reorder mode.
- To change a rule order, click the colored circle and drag the rule to a different spot in the rule set. The rule numbers are updated automatically.
- Click Save Reordered Rules to save the changes to the Titan cloud.
- Click the icon to add a new inbound routing policy. Enter information for the following fields.
Field Description Rule Name Enter a name for the rule. Match Criteria Select one or more match criteria:
- Click the Prefix tab and enter the IP prefix to match.
- Click the Community tab, and then enter the BGP community string to match. Enter the community string in one of the following formats:
- 2-byte or 4-byte decimal number
- 2-byte decimal number:2-byte decimal number
- Regular expression pattern
Action Select the action to apply to matched prefixes. - Allow
Click to allow the prefixes that match the match criteria:
- If you add BGP peer for a WAN interface, you can add the following additional criteria:
- Community Value—Enter the BGP community value to set. Community value can be set in the format 2-byte decimal number:2-byte decimal number. For example, <0-65535>:<0-65535>.
- If you add a BGP peer for a LAN interface, you can add the following additional criteria:
- Community Value—Enter the BGP community value to set. Community value can be set in the format 2-byte decimal number:2-byte decimal number. For example, <0-65535>:<0-65535>.
- Administrative Distance—Enter the administrative distance value. Administrative distance is a measure used by routers to determine the trustworthiness of a routing source. The low administrative distance indicates that eBGP routes are highly trusted compared to other routing protocols. The route with the lowest preference is the most likely to become the active route.
Range: 1 through 255
Default: For static route—1; For eBGP—20
- Deny
Click to deny the prefixes that match the match criteria. - Click the icon, and then click Save.