Validation Methods
Validation methods are initiated differently based on subsystem vendor associated with the Data Collector policy, but perform essentially the same functions. Refer to the following table for vendor-specific validation methods.
• Test Connection - Initiates a connection attempt directly from a data collector policy screen that attempts to connect to the subsystem using the IP addresses and credentials supplied in the policy. This validation process returns either a success message or a list of specific connection errors. See
Monitoring APTARE StorageConsole for details about starting and stopping components.
• On-Demand data collection run - Initiates an immediate end-to-end run of the collection process from the Portal without waiting for the scheduled launch. This on-demand run also serves to validate the policy and its values (the same as Test Connection), providing a high-level check of the installation at the individual policy level, including a check for the domain, host group, URL, Data Collector policy and database connectivity.This is initiated at the policy-level from
Admin>Data Collection>Collectors. See
Working with On-Demand Data Collection. Refer to
Data Collectors: Vendor-Specific Validation Methods to determine which data collector policies support On-Demand collection.
• CLI Checkinstall Utility- This legacy command line utility performs both the Test Connection function and On-Demand data collection run from the Data Collector server. See
Using the CLI Checkinstall Utility.
Note: APTARE does not recommend using the CLI Checkinstall utility for any Data Collector subsystem vendor which supports On-Demand runs.
Data Collectors: Vendor-Specific Validation Methods