Академический Документы
Профессиональный Документы
Культура Документы
Silver Peak
Subnet Sharing Metric for
OSPF and BGP Learned
Routes
Tech Note
201417-001 Rev A
Silver Peak Subnet Sharing Metric for OSPF and BGP Learned Routes Tech Note
Table of Contents
Table of Contents 3
Copyright and Trademarks 4
Support 5
Related Documentation 6
Subnet Sharing 7
Typical SD-WAN Deployment 8
Subnet Sharing Metric 9
Static Route Metric 10
Subnet Sharing Metric for OSPF Learned Routes 11
Subnet Sharing Metric for BGP Learned Routes 12
Copyright and Trademarks
Silver Peak Subnet Sharing Metric for OSPF and BGP Learned Routes Tech Note
Date: August 2018
Copyright © 2018 Silver Peak Systems, Inc. All rights reserved. Information in this document is subject to change at any time. Use
of this documentation is restricted as specified in the End User License Agreement. No part of this documentation can be
reproduced, except as noted in the End User License Agreement, in whole or in part, without the written consent of Silver Peak
Systems, Inc.
Trademark Notification
TM TM
The following are trademarks of Silver Peak Systems, Inc.: Silver Peak Systems , the Silver Peak logo, Network Memory , Silver
TM TM TM TM
Peak NX-Series , Silver Peak VX-Series , Silver Peak VRX-Series , Silver PeakSilver Peak Unity EdgeConnect , and Silver
TM
Peak Orchestrator . All trademark rights reserved. All other brand or product names are trademarks or registered trademarks of
their respective companies or organizations.
Warranties and Disclaimers
THIS DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. SILVER PEAK SYSTEMS, INC. ASSUMES NO RESPONSIBILITY FOR ERRORS OR
OMISSIONS IN THIS DOCUMENTATION OR OTHER DOCUMENTS WHICH ARE REFERENCED BY OR LINKED TO THIS
DOCUMENTATION. REFERENCES TO CORPORATIONS, THEIR SERVICES AND PRODUCTS, ARE PROVIDED “AS IS”
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IN NO EVENT SHALL SILVER PEAK SYSTEMS,
INC. BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY
DAMAGES WHATSOEVER, INCLUDING, WITHOUT LIMITATION, THOSE RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY,
ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS DOCUMENTATION. THIS DOCUMENTATION MAY
INCLUDE TECHNICAL OR OTHER INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY
ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE
DOCUMENTATION. SILVER PEAK SYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENTATION AT ANY TIME.
Silver Peak Systems, Inc.
2860 De La Cruz Boulevard
Santa Clara, CA 95050
1.877.210.7325 (toll-free in USA)
+1.408.935.1850
http://www.silver-peak.com/support
Support
For product and technical support, contact Silver Peak Systems at either of the following:
1.877.210.7325 (toll-free in USA)
+1.408.935.1850
www.silver-peak.com/support
We’re dedicated to continually improving the usability of our products and documentation.
If you have suggestions or feedback for our documentation, send an e-mail to
techpubs@silver-peak.com.
If you have comments or feedback about the interface, send an e-mail to usability@silver-
peak.com.
Related Documentation
Release Notes provide information on new software features, system bugs, and software
compatibility.
All user documentation is available at http://www.silver-peak.com.
Subnet Sharing
Subnet Sharing is Silver Peak’s internal routing protocols that shares local, static and dynamically
learned LAN routes at each site across the SD-WAN fabric. Subnet Sharing is enabled in the product
by default, requiring no additional configuration. Since site-to-site traffic flows over SD-WAN overlays
(i.e. overlay/underlay tunnels), the route look-up for the destination involves selecting egress SD-
WAN overlay based on learned Subnet Sharing information at the sender site. If there are multiple
paths to the destination, then the path with the lower Subnet Share metric is selected. If there are
multiple paths with the same metric, then Peer Priority configuration is used to determine the egress
SD-WAN overlay. If no Peer Priority is configured and there are multiple paths with the same metric,
then traffic is sent over all the SD-WAN overlays with the same metric.
Typical SD-WAN Deployment
A sample SD-WAN deployment with three sites is shown in the Figure 1. Each site has one or more
WAN transports e.g. MPLS, Internet, LTE etc. The EdgeConnects deployed at the sites form SD-
WAN overlays (i.e. secured overlay/underlay tunnels) on the different transports available at each
site.
Figure 1. SD-WAN Deployment with Three Sites
Subnet Sharing Metric
When an SD-WAN site shares LAN side local, static, OSPF and BGP learned subnets to the rest of
the sites in SD-WAN fabric, it uses the default metric 50 for all the subnets. This default metric value of
50 can be modified by selecting an appliance from the Orchestrator UI. For example, in Figure 2, at
spro2-ecve site, the value of 50 can be modified to the desired metric (e.g. 100) for all the routes at
spro2-ecve site that will be subnet-shared with the rest of the SD-WAN fabric.
Figure 2. Subnet Sharing Metric
Static Route Metric
Metric for each configured static route can be set to the desired value. When a static route is
configured at the selected site, default metric value is 50. Modify this value to desired metric value so
that the route gets shared with modified metric value across the SD-WAN fabric.
Figure 3. SD-WAN Deployment with Three Sites
Subnet Sharing Metric for OSPF Learned
Routes
When OSPF is enabled on LAN side, OSPF routes are learned by EdgeConnect from its OSPF
neighbors. All learned OSPF routes are shared with the rest of the sites in the SD-WAN fabric with
the learned route’s OSPF metric value. EdgeConnect allows user to change OSPF learned metric to
a desired value by changing the metric on the following screen. When set, all the OSPF routes
redistributed to the Subnet-Sharing will be shared with the new metric value ignoring route’s OSPF
learned metric.
Figure 4. Subnet Sharing OSPF Learned Routes
Subnet Sharing Metric for BGP Learned
Routes
When EdgeConnect has BGP peers configured, not all BGP learned routes are shared with the rest
of the sites in the SD-WAN fabric. It depends upon the type of the BGP peer (Branch, PE and
Branch-transit type). BGP routes learned from Branch and Branch-transit type peers are shared
across SD-WAN fabric while to avoid the routing loops, BGP routes learned from BGP-PE type peer
are not shared with the SD-WAN fabric.
When BGP routes are received from the BGP peers, EdgeConnect performs standard BGP route
selection process to select the best BGP route to be shared on the SD-WAN fabric. BGP MED value
received in the best BGP route is used to set Subnet-Sharing metric value. If the MED attribute is
absent in the best BGP received route then the default metric value is used that depends upon the
type of BGP peer. If the best BGP route is learned from iBGP peer then the Subnet-Shared metric is
set to 250 (50+200) and if the best BGP route learned from eBGP peer then the Subnet-Shared
metric set to 70 (50+20).
EdgeConnect allows to set desired metric value to substitute BGP MED before the route is Subnet-
Shared with the rest of the SD-WAN fabric. As shown in the picture below, if user configures “Input
Metric” parameter then it is used as the Subnet-Shared metric and BGP MED value is ignored. If the
“Input Metric” parameter is not configured then as mentioned above, either MED value of the BGP
route is used or if MED attribute is not present then metric values of 70 and 250 are used for eBGP
and iBGP peers respectively.
NOTE Input Metric is a per peer setting. Unless there are specific reason, it is recommended to set to same
“Input Metric” value for all the BGP peers. Since routes learned from BGP-PE peer type are not shared across
the SD-WAN fabric, setting “Input Metric” for BGP-Peer has no impact.
Figure 5. Subnet Sharing Metric for BGP Learned Routes