Discovery and postprocessing customization

You can customize the discovery process by using the discovery hook script files in the BASEDIR/smarts/rules/discovery/custom directory of the
IP Manager
installation area. Each discovery hook script is configured in such a way that it is invoked during a specific phase of the discovery:
  • custom-start-fulldscv.asl
    This script is run by the
    IP Manager
    before a full discovery.
  • custom-start-system.asl
    This script is run by the
    IP Manager
    before a system is discovered.
  • custom-end-system.asl
    This script is run by the
    IP Manager
    after a system is discovered and before postprocessing.
  • custom-start-post.asl
    This script is run by the
    IP Manager
    at the beginning of postprocessing.
  • custom-end-post.asl
    This script is run by the
    IP Manager
    at the end of postprocessing.
    You can customize discovery postprocessing by editing the ASL rule set in the custom-start-post.asl or custom-end-post.asl file. Here are two applications:
  • Edit the custom-start-post.asl file to rename devices after the devices are discovered and named by the
    IP Manager
    .
  • Edit the custom-end-post.asl file to unmanage devices in IP address ranges or with specific name patterns.
    If there are groups of IP addresses that are not normally reachable by using ICMP polling, specify the IP ranges or matching criteria in the custom-end-post.asl file to ensure that the
    IP Manager
    will set the management state of these IP addresses to be unmanaged. The
    IP Manager
    will not ping IP addresses that are unmanaged.
    IPs, devices, interfaces, ports, and other objects can also be unmanaged or managed through the
    Global Console
    by attaching the
    Global Console
    to the
    IP Manager
    and selecting the Unmanage or Manage menu option.
    All methods for controlling the management state of objects are described in the
    .