disco.SkipXdpProcessing — Contains a list of management IP addresses for nodes NNMi should not query for discovery protocol information.
One method NNMi uses to discover layer 2 connectivity between and among network devices in a managed network is to
collect information from the devices related to their discovery protocols. There are many defined discovery protocols. For example,
Link Layer Discovery Protocol (LLDP) is an industry standard protocol, while there are many vendor-specific protocols like Cisco
Discovery Protocol (CDP) for Cisco devices. These are all handled by NNMi discovery in the XdpAnalyzer.
You can configure NNMi to suppress discovery protocol collections for devices you specify.
This feature makes use of a configuration file, disco.SkipXdpProcessing, that the NNMi administrator creates.
The name of the file is case-sensitive.
The ovjboss service reads the disco.SkipXdpProcessing when
it starts up. If the NNMi administrator makes changes to this file after the ovjboss service starts up, those changes
will not take effect until the next time the ovjboss service starts. By default, the disco.SkipXdpProcessing file does not exist.
If the disco.SkipXdpProcessing does not exist, this feature is disabled and NNMi attempts to collect discovery protocol information from all managed nodes.
For more information about the known problems fixed by this feature, refer to the SEE ALSO section below.
The disco.SkipXdpProcessing file can contain IP addresses 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. Specify IP addresses in the standard
IP version 4 dotted-decimal notation or standard IP version 6 format (RFC 2373).
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.SkipXdpProcessing file,
NNMi skips the XdpAnalyzer service for that node and does not collect discovery protocol information.
Disabling the discovery protocol processing of a node or nodes might cause some inaccuracies in the layer 2 layout of the managed network. HP is not responsible for these inaccuracies.
The following is an example of a disco.SkipXdpProcessing file:
#This entry supresses the XdpAnalyzer processing for the node whose management address is 10.2.37.149
10.2.37.149
192.168.100.1 #This entry causes the node 192.168.100.1 to be skipped, too
# Here are some examples of IPv6 addresses:
2136::8:800:200C:417a
fd01::a352:1245:fc4B
$NnmDataDir/shared/nnm/conf/disco/disco.SkipXdpProcessing
%NnmDataDir%\shared\nnm\conf\disco\disco.SkipXdpProcessing