28 | Configuring Local Subnet Discovery on SteelHead SD
Defining global subnet discovery at the organization level
•
Zone inclusion list
- You select one or more of the configured LAN zones. Routes whose next-hop
interface matches one of the selected zones are qualified as local subnets. Preexisting zones that
are directly connected to a site are added to the list automatically. You can also manually add other
zones. Zones deleted from a site are automatically removed from the list.
•
Uplink inclusion list
- You select one or more of the configured WAN uplinks. Routes whose next-
hop interface matches one of the selected WAN uplinks are qualified as local subnets. For example,
you might want to attract traffic towards a site for transit purposes. If Site A wants to connect to Site
C through Site B. Site B can learn Site C networks via the underlay and make Site A traffic bound for
Site C to be forwarded to Site C.
•
Community inclusion list
- You specify a community to include all the routes that carry that
community string. The routes matching the community in the community list are reported as local
subnets. You can specify multiple communities.
•
Tag
inclusion list
- You specify a tag to include all the routes that include the tag. All the routes
matching the tag are reported as local subnets from the configured site. You can specify multiple
tags.
•
Network prefix inclusion list
- You configure a list of prefixes. If a route for one of the prefixes in the
list is received, it is qualified as a local subnet.
•
Next-hop inclusion list
- You configure a list of next-hop prefixes. All routes whose next-hop
matches one of the entries in the list are qualified as a local subnet.
•
Community exclusion list
- You specify a tag to exclude all the routes that include the tag. All the
routes matching the tag are reported as local subnets from the configured site. You can specify
multiple tags.
•
Tag
exclusion list
- You specify a tag list to include. You can specify multiple tags. The routes
matching the tag list are reported as local subnets. You can list more than one community.
•
Network prefix exclusion list
- You configure a list of prefixes. If a route for one of the prefixes in
the list is received, it’s not qualified as a local subnet.
Note:
SteelConnect SDI-2030 and SDI-5030 gateways don’t allow you to define routing criteria based on zones and
uplinks.
For SteelHead SD, you can create inclusion and exclusion lists at the organization, zone, and site level.
For example, you could create an umbrella subnet 10.0.0.0/8 inclusion list at the organization level and
then drill down to a particular site to exclude 10.0.0.0/16.
Inclusion lists are applied first, and then exclusions lists will be applied.
Defining global subnet discovery at the organization level
Users can add an organization level subnet discovery rule under the Global Subnet Discovery tab. This
rule will be applied to all sites, unless they are specifically overridden by the site-level subnet discovery
rule.
To define global subnet discovery for an organization
1. Choose Organizations.
Summary of Contents for SteelHead 3070-SD
Page 14: ...14 Introducing SteelHead SD Next steps...
Page 36: ...36 Configuring AutoVPN on SteelHead SD Configuring AutoVPN on SteelHead SD...
Page 90: ...90 Configuring LAN Side Internet Breakout on SteelHead SD Troubleshooting...
Page 104: ...104 Configuring High Availability on SteelHead SD Troubleshooting...
Page 116: ...116 Health Check and Reporting on SteelHead SD Exporting Netflow data...
Page 124: ...124 TOS DSCP QoS Traffic Class Table TOS DSCP and QoS Traffic Classes Table...
