glide.discovery.discoverable.network.max.netmask.bits
ServiceNow property description:
Maximum netmask size for discoverable networks (bits): The maximum number of bits in a regular netmask for networks that will be discovered by Network Discovery. By "regular netmask" we mean a netmask that can be expressed in binary as a string of ones followed by a string of zeroes (255.255.255.0 is regular, 255.255.255.64 is irregular). Regular networks are commonly expressed like this: 10.0.0.0/24, which means a network address of 10.0.0.0 with a netmask of 255.255.255.0. Larger bit numbers mean networks with smaller numbers of addresses in them. For example, the network 10.128.0.128/30 has four addresses in it: one network address (10.128.0.128), one broadcast address (10.128.0.131), and two usable addresses (10.128.0.129 and 10.128.0.130). Small networks like this are commonly configured in netowrk gear to provide loopback addresses or networks used strictly by point-to-point connections. Since these sorts of networks generally don't need to be discovered by Network Discovery, it would be useful to filter them out. By setting this property to a value of 1 through 32, you can limit the sizes of regular networks that are discovered. Setting it to any other value will cause all networks to be discovered. Irregular networks are always discovered. The default value is 28, which means that regular networks with 8 or fewer addresses will not be discovered.
Attributes
- Sys ID: de1758510a0a0b02002e836ce6d1702d
- Type: integer
- Application: Global
- Default value: 28

AI generated property description:
The ServiceNow property `glide.discovery.discoverable.network.max.netmask.bits` is used to define the maximum subnet size that the Discovery process will consider when scanning a network. According to the documentation, this property sets a limit on the netmask bits, which effectively controls the scope of the network segments that Discovery will attempt to explore. By adjusting this property, administrators can prevent the Discovery process from attempting to scan excessively large subnets, which could lead to performance issues or incomplete discoveries. The default value for this property is typically set to ensure a balance between thorough network scanning and system performance. Adjusting this value can be particularly useful in large or complex network environments where certain subnets need to be excluded from the Discovery process.
Source