disco.NoVLANIndexing — Specifies certain nodes where VLAN Indexing should be skipped during discovery polling.
One of the methods NNMi uses to learn layer 2 connectivity between and among switch devices in a managed network
is to retrieve the dot1dTpFdbTable (FDB) from the switches. However, for Cisco switches, NNMi
must use a VLAN-indexing method to retrieve the entire FDB. Using this method, NNMi retrieves the FDB
once for each configured VLAN on the Cisco device. If there is a large number of VLANs configured on each device,
retrieving the FDB with VLAN-indexing might take a very long time, sometimes even hours, to complete.
Cisco switches are often configured to use the Cisco Discovery Protocol (CDP). CDP is considered to be a superior
method for learning layer 2 connectivity. Large switches located in the in the core of the network might contain many VLANs. These switches
typically do not have end nodes connected directly to them. If the switches you want to manage do not have end nodes connected directly to them,
you might want to suppress the collection of the FDB on these large switches. NNMi still completes the layer 2 discovery
using data collected from CDP. These large switches are prime candidates for suppression of VLAN-indexing. Do not suppress
VLAN-indexing on smaller switches located at the network's edge (often known as access switches) that have many end nodes attached to them.
You can configure NNMi to suppress VLAN indexing. To do this, the NNMi administrator needs to create
the disco.NoVLANIndexing file, where the name of the file is case-sensitive. The ovjboss service reads the disco.NoVLANIndexing file
when it starts. If the NNMi administrator makes changes to the disco.NoVLANIndexing file after the ovjboss service
starts, those changes will not take effect until the next time the ovjboss service starts. By default, the disco.NoVLANIndexing
file does not exist. If the disco.NoVLANIndexing does not exist, this feature is disabled and NNMi attempts to use VLAN-indexing
to collect the entire FDB table on all devices.
The disco.NoVLANIndexing file can contain IP addresses, IP address ranges, and comments.
A comment consists of the pound (or hash) sign (#) and all characters between
# and the end of the line. NNMi treats an empty line as a comment. IP addresses are specified in the standard
IP version 4 dotted-decimal notation or standard IP version 6 format (RFC 2373).
For details on the format of IP address ranges, see the Configure Address Ranges for Regions section of the NNMi help.
NNMi considers a node to match if one of the listed IP addresses matches a node's management address.
Other IP addresses hosted by the node are not considered. If a node matches one of the addresses in the disco.NoVLANIndexing file,
NNMi collects only the default FDB (the FDB which is accessible by using the community string with no @vlan-id suffix appended).
Disabling the collecting of the entire FDB might cause some inaccuracies in the layer 2 layout of the
managed network. HP is not responsible for these inaccuracies. Carefully consider which switches you include
in the disco.NoVLANIndexing file.
The following is an example of a disco.NoVLANIndexing file:
#This entry suppresses VLAN-indexing for the node whose management address is 10.2.37.149
10.2.37.149
192.168.100-101.1 #This entry causes the nodes 192.168.100.1 and 192.168.101.1 to be skipped, too
# Here are some examples of IPv6 addresses and ranges:
2136::8:800:200C:417a
fd01::a352:1245:fc4B
2001:D88:2:0:a07:ffff:0a01:3200-37ff
$NnmDataDir/shared/nnm/conf/disco/disco.NoVLANIndexing
%NnmDataDir%\shared\nnm\conf\disco\disco.NoVLANIndexing