If during the initial polling phase a system is assigned an ICMPSNMP access mode, the discovery process calls the custom-end-system.asl script. In contrast, if during the initial polling phase a system is assigned an ICMPONLY access mode, the discovery process does not call the custom-end-system.asl script. For an ICMPONLY system, the discovery process schedules the system for postprocessing right after the initial polling phase because additional probing is not applied to an ICMPONLY system.
Thus, any custom code that you add to the custom-end-system.asl script is applied to ICMPSNMP systems but not ICMPONLY systems. If you want to customize the discovery of both ICMPSNMP and ICMPONLY systems, you should add your custom code to the custom-start-post.asl script, the custom-end-post.asl script, or both.
“Discovery methods” on page 144 describes the discovery process and identifies the topology that is discovered by the IP Manager.
“Modifying discovery hook scripts” section in Chapter 3, Discovery, in the VMware Smart Assurance IP Manager User Guide, provides information on how to edit a discovery hook script to add the ASL convenience patterns, the parsing rules, and the processing rules that perform the actual processing.