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.

You can define multiple zones, and you can combine inclusion and exclusion zones. However, if you define a combination of inclusion and exclusion zones, the exclusion zones must be within the scope of the inclusion zones.

Table 1. scope.zones 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 filtAction 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 discovery 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.