disco.scope database schema
The scope database is defined in $NCHOME /etc/precision/DiscoSchema.cfg
and $NCHOME /etc/precision/DiscoScope.cfg.
Its fully qualified database table names are: scope.zones; scope.detectionFilter;
scope.instantiateFilter; scope.special.
scope.detectionFilter table
If you specify a filter in the detectionFilter table, only devices matching it are discovered.
scope.inferMPLSPEs table
Use the scope.inferMPLSPEs table when enabling inference of inaccessible provider-edge (PE) devices by using the BGP data on the customer-edge (CE) devices. This table enables you to optionally specify which zones to process to determine which of the inferred PE devices are valid devices.
scope.instantiateFilter table
When you specify a filter in the instantiateFilter table, only devices that pass the criteria are instantiated, that is, sent to the DNCIM database. If no filter is specified, all discovered devices are instantiated.
scope.mplsTe table
The scope.mplsTe table defines the scope of MPLS Traffic Engineered (TE) tunnel discovery, and defines what information is retrieved.
scope.multicastGroup table
The scope.multicastGroup table defines which multicast groups to discover and which details to retrieve from these groups.
scope.multicastSource table
The scope.multicastSource table defines which IPM routes to discover. This is particularly useful if you have multiple IPM route sources, since you can scope multicast discovery by IPM route source to focus on the sources of interest.
scope.special table
The special table defines management IP addresses. A management address is an IP address on a device whose only role is to manage the device. Management addresses do not handle network traffic.
scope.zones table
Use the zones table to define areas of the network to be either included or excluded from the discovery process. A zone is typically defined as a list of varbinds. Varbinds are name = value pairs.