The Adapter filters devices using regular expressions loaded from ASAM_BASEDIR/smarts/conf/DevicesNotInEffect.conf. Each line of the file represents one regular expression. Lines may begin with a “#” character to denote a comment. Comment lines are ignored when loading the file.
Filtered devices do not appear in Domain Managers. They are ignored during 5620 SAM EMS server processing. Filtering reduces the number of objects stored inside VMware Smart Assurance servers and lessens the process load on the Adapter. Filtering is recommended on devices that are in a constant state of flux, where monitoring is not desired.
The Adapter loads filters from the DevicesNotInEffect.conf file only on Adapter startup. If you wish to change filters during Adapter runtime, you may invoke the following asl rules:
alcatel-sam/showFilters.asl— Print the currently loaded filters in the Adapter.
alcatel-sam/deleteFilters.asl—Delete the filters given from the specified filter frontend. This is usually a file front end loaded with the --file flag passed to sm_adapter. Filters are deleted based on exact string matching.
alcatel-sam/insertFilters.asl—Insert the filters given from the specified filter frontend. This is usually a file front end loaded with the --file flag passed to sm_adapter.
alcatel-sam/clearFilters.asl—Remove all filters in the Adapter.
Managing devices not in effect on page 142 describes how you can use these scripts to manage the filters.
The addition and deletion of filters at runtime will not change what the Adapter is currently filtering on. A full discovery (invoked from alcatel-sam/discover.asl) or a router-specific discovery (invoked from ASAM/routerDiscover.asl) is required to reload the Adapter's internal filtering list. A discovery is required because reloading the filter list requires several (potentially long) processes to run in order to clean up (newly) filtered objects that may exist in InCharge servers.