When executing a scan task, an AvailabilityGuard collector remotely connects and scans various types of target systems – Linux hosts, EMC Solutions Enabler (AKA SYMCLI) server, Microsoft SQL server and so on. For each type of target system, AvailabilityGuard uses dedicated scan timeout system properties defining the maximal acceptable duration of the scan after which the collector will move one to the next scan subtask.
AvailabilityGuard administrators may adjust the default scan timeout values to optimize the scan process for the define systems scope. Tuning scan timeout values should be considered when target systems are reported with the Timed out scan status or when time out values are unnecessarily too high[1].
For each target system type, AvailabilityGuard defines two scan timeout properties:
- Timeout in minutes for scanning one system of the given type.
- Timeout in minutes for scanning all systems of the given type.
For example, a property exists to control the scan timeout for one Windows host and another property exists to control the scan timeout for all the Windows hosts.
The following table lists the scan timeout system property and the default values:
System Property |
Default Value |
Timeout for dead Data Collector, in minutes |
30 |
Timeout for scanning all BNA in minutes |
180 |
Timeout for scanning all Brocades in minutes |
180 |
Timeout for scanning all Cisco in minutes |
180 |
Timeout for scanning all databases, in minutes |
180 |
Timeout for scanning all DataDomain proxies, in minutes |
180 |
Timeout for scanning all DCNM in minutes |
180 |
Timeout for scanning all DFM proxies, in minutes |
180 |
Timeout for scanning all DSCLI proxies, in minutes |
180 |
Timeout for scanning all ECCs, in minutes |
120 |
Timeout for scanning all GoldenGate proxies, in minutes |
180 |
Timeout for scanning all HiCommand consoles, in minutes |
180 |
Timeout for scanning all HMC proxies, in minutes |
180 |
Timeout for scanning all hosts, in minutes |
180 |
Timeout for scanning all HPVirtualConnect in minutes |
180 |
Timeout for scanning all Infinidat in minutes |
180 |
Timeout for scanning all InFormCLI proxies, in minutes |
180 |
Timeout for scanning all Isilon proxies, in minutes |
180 |
Timeout for scanning all NaviCLI proxies, in minutes |
180 |
Timeout for scanning all NetApp filers, in minutes |
180 |
Timeout for scanning all NSX in minutes |
180 |
Timeout for scanning all OEM proxies, in minutes |
180 |
Timeout for scanning all RecoverPoint proxies, in minutes |
180 |
Timeout for scanning all ScaleIO in minutes |
180 |
Timeout for scanning all SCVMM in minutes |
180 |
Timeout for scanning all SMCLI proxies, in minutes |
180 |
Timeout for scanning all SVC proxies, in minutes |
180 |
Timeout for scanning all SYMCLI proxies, in minutes |
180 |
Timeout for scanning all UCS in minutes |
180 |
Timeout for scanning all Unity in minutes |
180 |
Timeout for scanning all vCenters, in minutes |
300 |
Timeout for scanning all VPLEX proxies, in minutes |
180 |
Timeout for scanning all XCLI proxies, in minutes |
180 |
Timeout for scanning all XtremIO in minutes |
180 |
Timeout for a single BNA scan, in minutes |
90 |
Timeout for a single Brocade scan, in minutes |
90 |
Timeout for a single Cisco scan, in minutes |
90 |
Timeout for a single database scan, in minutes |
20 |
Timeout for a single DataDomain scan, in minutes |
60 |
Timeout for a single DCNM scan, in minutes |
90 |
Timeout for a single DFM scan, in minutes |
60 |
Timeout for a single DSCLI proxy scan, in minutes |
60 |
Timeout for a single ECC scan, in minutes |
90 |
Timeout for a single GoldenGate scan, in minutes |
60 |
Timeout for a single HiCommand scan, in minutes |
90 |
Timeout for a single HMC scan, in minutes |
60 |
Timeout for a single host scan, in minutes |
25 |
Timeout for a single HPVirtualConnect scan, in minutes |
90 |
Timeout for a single Infinidat scan, in minutes |
60 |
Timeout for a single InFormCLI proxy scan, in minutes |
60 |
Timeout for a single Isilon scan, in minutes |
60 |
Timeout for a single NaviCLI proxy scan, in minutes |
60 |
Timeout for a single NetApp filer scan, in minutes |
30 |
Timeout for a single NSX scan, in minutes |
60 |
Timeout for a single OEM scan, in minutes |
60 |
Timeout for a single RecoverPoint scan, in minutes |
60 |
Timeout for a single ScaleIO scan, in minutes |
60 |
Timeout for a single SCVMM scan, in minutes |
90 |
Timeout for a single SMCLI proxy scan, in minutes |
60 |
Timeout for a single SVC scan, in minutes |
60 |
Timeout for a single SYMCLI proxy scan, in minutes |
90 |
Timeout for a single UCS scan, in minutes |
90 |
Timeout for a single Unity scan, in minutes |
60 |
Timeout for a single vCenter scan, in minutes |
180 |
Timeout for a single VPLEX scan, in minutes |
60 |
Timeout for a single XCLI proxy scan, in minutes |
60 |
Timeout for a single XtremIO scan, in minutes |
60 |
[1] may lead to suboptimal scan execution when a particular system is responding exceptionally slow and takes over most of the scan window at the expense of other systems in scope
Comments
0 comments
Please sign in to leave a comment.