Configuration of the scope.zones table

Creating two inclusion zones

This example configuration of the scope.zones table creates two inclusion zones for the current discovery. Both zones are defined using a single insert.

insert into scope.zones
(
        m_Protocol,
        m_Action,
        m_Zones
)
values
(
        1,
        1,
        [
            {
                m_Subnet="172.16.1.0",
                m_NetMask=24
            },
            {
                m_Subnet="172.16.2.*"
            }
        ]
);

The previous OQL insert specifies the following conditions:

• The network uses the Internet Protocol (m_Protocol=1).
• Any devices that fall into the present zone are to be included in the discovery (m_Action=1).
• The discovery includes:
  • Any device that falls within the 172.16.1.0 subnet (with a subnet mask of 24, that is, 24 bits turned on and 8 bits turned off, which implies a netmask of 255.255.255.0).
  • Any device with an IP address starting with 172.16.2, that is, in the 172.16.2.0 subnet with a mask of 255.255.255.0.

Creating a zone within a zone

Zones can be specified within zones: within a given inclusion zone, you can specify devices or subnets that are not to be detected. These devices are not pinged by the Ping finder or interrogated by the discovery agents. For example, you can define an include scope zone consisting of the Class B subnet 172.20.0.0/16, and completely contained within that zone you can specify an exclude scope zone consisting of the subnet 172.20.32.0/19. Finally, completely contained within the exclude scope zone you could specify an include scope zone 172.20.33.0/24.

// Include all IP addresses in this range
insert into scope.zones
(
        m_Protocol,
        m_Action,
        m_Zones
)
values
(
        1,
        1,
       [{m_Subnet = '172.20.0.0', m_NetMask = 16 }]
);

// Apart from the IP addresses in this range
insert into scope.zones
(
        m_Protocol,
        m_Action,
        m_Zones
)
values
(
        1,
        2,
        [{m_Subnet = '172.20.32.0' , m_NetMask = 19 }]
);
// Except for these IP addresses which we do want to include
insert into scope.zones
(
        m_Protocol,
        m_Action,
        m_Zones
)
values
(
        1,
        1,
        [{m_Subnet = '172.20.33.0' , m_NetMask = 24 }]
);

The previous OQL insert specifies three scope zones:

• All zones specify that the network uses the Internet Protocol (m_Protocol=1).
• Include and exclude zones are defined as follows:
  • Any devices that fall into the first zone, 172.20.0.0/16, are to be included in the discovery (m_Action=1).
  • Any devices that fall into the second zone, 172.20.32.0/19, which is completely contained within the first zone, are to be excluded from the discovery (m_Action=2).
  • Any devices that fall into the third zone, 172.20.33.0/24, which is completely contained within the second zone, are to be included in the discovery (m_Action=1).