Link Search Menu Expand Document


A complete guide to EdgeConnect routing is beyond the scope of this document. Before troubleshooting, you should have an understanding of subnet sharing, peer priority, and route redistribution.

Routing Decisions

Routing decisions are made based on a well-known evaluation process:

  1. Longest Prefix Match
  2. Lowest Administrative Distance
  3. Lowest Metric
  4. Lowest Peer Priority

NOTE Peer Priority is a concept specific to EdgeConnect. If the first three values are equal, Peer Priority breaks the tie. If all values are equal and Peer Priority is not configured, traffic is load balanced over all peers involved in the tie.


To show routes learned by appliances in the fabric, click Configuration, and then click Routes. Use this information to confirm configuration for route presence, AD, metric, and more.

Find Preferred Route

Use this tool to determine traffic-forwarding decisions for traffic coming from the WAN or LAN, or for traffic self-generated by the appliance. To access the tool, click Configuration, and then click Routes. To edit one of the table entries, click the Pencil icon. The appliance-specific route page appears with a button displayed to load the tool.

NOTE If segmentation is enabled, make sure the entry selected is part of the segment under investigation.

The following example shows that self-generated traffic from this appliance, destined for, will be sent to the EAST2-AWS appliance, and that the route was learned over the SD-WAN fabric.

Finding the Preferred Route

Common Issues

Issue Resolution
Route not present on appliance from another appliance. Confirm there is a tunnel up between the two appliances, or between the appliance and its hubs if using regional routing.
Routes not being advertised to other appliances. Confirm there is a tunnel up between the two appliances, or between the appliance and its hubs if using regional routing.
Not enough or too many routes being seen from non-EdgeConnect devices. Check inbound/outbound route maps for the routing protocol being used.
Routes not being advertised to other network equipment. Confirm the routing protocol is in the appropriate state. Confirm the route maps are configured properly.

Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.

Open Source Code:

Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America