DiscoPingFinderSeeds.cfg configuration file
The DiscoPingFinderSeeds.cfg configuration file is used for seeding the Ping finder and restricting device detection.
Database tables used
The DiscoPingFinderSeeds.cfg configuration file can be used to configure inserts into the following database tables:
- pingFinder.pingRules
- pingFinder.scope
Note that there is another configuration file associated with
the pingFinder database, the DiscoPingFinderSchema.cfg file, but you
should not need to alter this file.
Note: If you are seeding
an IPv6 discovery, bear in mind that there are potentially billions
of devices to be pinged within a single IPv6 subnet. To ensure that
discovery completes, you must specify a sufficiently large netmask
if you specify an IPv6 subnet as a ping seed.
Sample: seeding the Ping finder with a single device address
The following example insert defines a single seed with IP address of 10.10.2.224. This example
does not specify values for m_NumRetries and m_TimeOut because they automatically take the default
values from the configuration table.
Restriction: Network Manager does not support the
IPv4–mapped IPv6 format and expects all IPv6 addresses to be in standard colon-separated IPv6
format. For example, Network Manager
does not support an IPv4–mapped IPv6 address such as
::ffff:192.0.2.128. Instead
enter this address as ::ffff:c000:280 (standard colon-separated IPv6
format).insert into pingFinder.pingRules
( m_Address, m_RequestType )
values
( "10.10.2.224", 1 );Sample: seeding the Ping finder with a class B subnet address
The following example insert defines a single class B subnet as a seed.
insert into pingFinder.pingRules
( m_Address, m_RequestType, m_NetMask )
values
( "10.10.0.0", 2, "255.255.0.0" );Sample: seeding the Ping finder with class C subnet addresses
The following example insert defines two Class 2 subnets as seeds.
insert into pingFinder.pingRules
( m_Address, m_RequestType, m_NetMask )
values
( "10.10.2.0", 2, "255.255.255.0" );
insert into pingFinder.pingRules
( m_Address, m_RequestType, m_NetMask )
values
( "10.10.47.0", 2, "255.255.255.0" );Sample: restricting device detection
The following example insert configures the Ping finder to use the scope.zones table and use the discovery scope.
insert into pingFinder.scope
( m_UseScope, m_UsePingEntries )
values
( 1, 1 );Important: Other combinations
of m_UseScope and m_UsePingEntries filters are not recommended. Specifying
values (0,0) results in an unbounded discovery, while specifying values
(0,1) results in devices that you do not want to discover being needlessly
pinged.