In BloxOne Service Edge, you can export connected or attached subnets, static routes and summary routes that you have configured to other Service Edge instances that are a part of the same Service Edge connectivity profile. You can also configure a summary route for an on-prem host and then filter route prefixes as per their status to export them to peer edges.
For example, assume that your Service Edge deployment contains five edge instances and two profiles. Profile 1 contains three edges (Edge1, Edge2, Edge3) and Profile 2 contains three edges (Edge1, Edge4, Edge5). When Edge1 exports a route, because Edge1 is part of Profile 1 and Profile 2, the route is distributed to all the members of both the profiles. When Edge2 exports a route, because Edge2 is part of only Profile 1, the route is distributed to the members of only Profile 1. At any point of time, there can be only one edge instance that can be a part of multiple profiles. A pair of edge instances cannot be a part of multiple profiles.
Route distribution is possible only if you have the Edge Services Router service and the Site-to-Site VPN service enabled on each Service Edge instance.
You can control the export of connected, learned, and static routes and specify the routes to be distributed to peer edges. You can also filter out and exclude networks that you do not automatically want to advertise to peer edges.
To specify and advertise the routes to be distributed to peer edges, do the following:
- In the Cloud Services Portal, click Manage > Service Edge > Edges.
- Click
-> Edit, or select the edge and click the Edit button.
- On the Edit <edge name> page, specify the following:
- Expand Routes Originated from the selected Edge.
- Click the Always Filter Connected check box to filter out all connected routes to peer edges. A connected route is a network configured on an attached interface. When you select the check box, all connected routes in the edge instance cannot be reached by other edge instances.
Click the Always Filter Learned check box to filter out all learned routes to peer edges. A learned route is a route recognized from peer edges through a routing protocol. When you select the check box, all learned routes in the edge instance cannot be reached by other edge instances.
- Click the Add button to configure summary routes. A summary route summarizes a given subset of routes. For a summary route you add, if you select ADVERTISED from the STATUS field, any matching connected, static, or learned routes are suppressed from advertising to peer edge instances and only the summary route is advertised. For example, if you have connected routes 195.177.1.0/24 and 195.177.2.0/24 and a summary route 195.177.0.0/16, then only 195.177.0.0/16 will be advertised to peer edges that belong to the same profile as the host edge.
- For a summary route you add, if you select FILTERED from the STATUS field, the summary route is never advertised and any matching connected, static, or learned routes are suppressed from advertising to peer edge instances. For example, if you have connected routes 195.177.1.0/24 and 195.177.2.0/24 and a summary route 195.177.0.0/16, then none of the routes will be advertised to peer edges.
If you configure summary routes, the summary route configuration precedes the configurations of the Always Filter Connected and Always Filter Learned check boxes. For example, if you select the Always Filter Connected check box and select ADVERTISED from the STATUS field for a summary route, then only the summary route is advertised and all connected and learned routes are suppressed. - Expand Static Routes to export only static routes. A static route is a user-configured route.
- Click Add New Static Route to add an
- Next Hop: Specify the IP address of the next closest router to which data packets will be routed.
- Click Save & Close.