Riverbed SteelHead 3070-SD, Руководство пользователя

Страница: 30 / 124

30 | Configuring Local Subnet Discovery on SteelHead SD
Defining local subnet discovery
Defining local subnet discovery
After you have defined subnet discovery at the organization level, you can drill down to particular sites
to define inclusion and exclusion lists. For OSPF routes, make sure that your branch has the LAN zone
and WAN uplink attached to it before you begin. For BGP routes, make sure that your branch has the
iBGP neighbor defined for the LAN router and the eBGP neighbor defined for the WAN router.
You can also configure community list and tags for subnet autodiscovery. This feature enables the
discovery of subnets based on the community or tag present in the route. You can specify the
community list and tag for both inclusion and exclusion network lists.
To define local subnet discovery
1. Choose Network Design to display the sites for the organization.
2. Select the site for which you want to define local subnet discovery.
3. Select the Local Subnet Discovery tab.
4. Select the zone to discover all of the LAN-side subnets routed through the zone’s peers. The list
includes automatically populated and manually added zones. Preexisting zones that are directly
connected to a site are added to the list automatically. You can manually add other zones. Zones
deleted from a site are automatically removed from the list.
5. Select the uplink from the Uplinks inclusion list.
6. Under Inherit global, click On to globally include subnets and next hops. Whatever subnets were
configured for inclusion or exclusion at the organization level can be inherited at the site level.
Figure 4-5. Defining site level subnet discovery
7. Optionally, specify a community list 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 separated by a comma.