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.aslThis script is run by theIP Managerbefore a full discovery.
- custom-start-system.aslThis script is run by theIP Managerbefore a system is discovered.
- custom-end-system.aslThis script is run by theIP Managerafter a system is discovered and before postprocessing.
- custom-start-post.aslThis script is run by theIP Managerat the beginning of postprocessing.
- custom-end-post.aslThis script is run by theIP Managerat 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 theIP 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 theIP Managerwill set the management state of these IP addresses to be unmanaged. TheIP Managerwill not ping IP addresses that are unmanaged.IPs, devices, interfaces, ports, and other objects can also be unmanaged or managed through theGlobal Consoleby attaching theGlobal Consoleto theIP Managerand selecting the Unmanage or Manage menu option.All methods for controlling the management state of objects are described in the .