Scan Ranges in Infinite Device Management - Best Practices

Before discussing the best practices, there are a few things to be aware of when building your custom scan ranges:

  1. Default scan ranges will use the ip address and subnet mask of the computer running ICE to determine what addresses to scan, and what the broadcast and network addresses are.
  2. However when you input a custom scan range, the subnet mask will only be used to calculate the broadcast/network addresses so ICE will not scan these addresses. Limiting the range of addresses must be done with the start and end ranges, not the netmask.
  3. ICE will accept a scan range of a single address.

Best practices:

  1. Remember ICE will be running on your customers network, so try to limit the amount of needless scanning. Work with your customer to enable you to:
  2. Limit scanning to those subnets where printers will be found. IE: If the customer has a large network composed of many subnets, scan only those subnets where printers will be found.
  3. Limit scanning within subnets wherever possible to the address range where printers will be found. IE if the customer always installs printers with ip addresses above 200 on a class C subnet, don't scan all 254 addresses, instead configure it to scan just the 54 addresses where printers will be found.
  4. Always remember ICE accepts scan ranges of a single address.
  5. Use reasonable scan intervals. Improving the accuracy and performance of FM is dependent on what you do with the data obtained, not on how much data you obtain.

The importance of item 1 cannot be understated. While it is much easier to setup a single class B subnet and scan everything than it is to setup a number of partial class C scans, that method will also create a lot of useless traffic on your customer's network.
How did we do with this article?