The following restrictions apply for configuring a non-routed edge discovery policy:
NEs cannot be specified as aggregator nodes in more than one policy
NEs that are specified as aggregators cannot be specified as edge nodes in the same or another policy
NEs cannot be included in policies across admin domains
Note: A non-routed edge discovery policy does not automatically distinguish between routed and non-routed adjacencies, therefore operator intervention is required in order to prevent the inclusion of adjacencies that are already included in a routing protocol. You can use overrides to exclude specific routing interfaces from non-routed edge discovery policies in order to prevent routed adjacencies from being misrepresented on the topology maps. See
To override a non-routed edge discovery policy for a routing interface for more information.
Steps
1
Choose Tools→Route Analysis→Admin Domains / CPAAs from the NFM-P main menu. The Admin Domains / CPAAs form opens.
2
Choose Administrative Domain (CPAM: Topology) and click Search.
3
Choose an entry and click Properties. The IGP Administrative Domain (Edit) form opens.
4
Click on the Non-Routed Edge Discovery Policies tab.
5
Click Create. The Non-Routed Edge Discovery Policy (Create) form opens.
6
Configure the required parameters.
7
Specify aggregator routers and edge routers:
Click on the Aggregator Routers and Edge Routers tabs.
Click Add. A form opens.
Click Search.
Choose one or more entries and click OK. The form closes.