pingFinder.pingFilter database table

Edit online

The pingFinder.pingFilter table can be used to exclude particular devices or subnets from being pinged by the Ping finder.

Description

You may wish to exclude certain interfaces, such as ISDN and modem interfaces, because pinging these interfaces generates phone calls, which costs money. If you configure the Ping finder to use both the scope.zones table and the pingFinder.pingFilter table, the Ping finder pings those devices or subnets it has been seeded with if they are within either the discovery scope or the Ping finder scope.

Schema

The pingFinder.pingFilter database table schema is described in the following table:

Table 1. pingFinder.pingFilter database table schema 

Column name

Constraints

Data type

Description

 
m_Protocol
  • PRIMARY KEY
  • NOT NULL
  • Externally defined netProtocol data type

Integer
An integer representation of the IP protocol used by the presently-defined zone:
  • 1: IPv4
  • 2: IPv4 that has been through network address translation (NAT)
  • 3: IPv6
 
m_Action
  • NOT NULL
  • Externally defined netProtocol data type

Integer
Action to perform for current zone:
  • 0: Undefined
  • 1: Include
  • 2: Exclude
 
m_Zones

List of type zone

A list of varbinds (name=value) that define the present zone.

 
m_AddressSpace

Text

The name of the NAT address space to which the device belongs. This value is set in the translations.NATAddressSpaceIds table. If the discovery is not using NAT, or if the device is in the public domain, this value is NULL.