Host Collection Advanced Parameters
Warning: Making changes to Advanced Parameters should not be undertaken unless the user understands the impact of the parameter changes. If undesired results occur, revert the settings and contact APTARE Global Support Services or visit the APTARE Community web site for further guidance.
The following advanced parameters apply to a variety of general collection functions, not necessarily associated with a particular subsystem.
Admin > Advanced > Parameters, described in Adding an Advanced Parameter. APP_DISK_PATH
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Text value (Default is a null value)
Scope: This parameter can be set at the Domain or Data Collector level or for a specific OS, or for a specific host.
Applications, such as Oracle ASM, may have devices created from disk aliases located in any directory. This parameter enables you to provide a list of directories that will contain the alias devices that are of interest.
A colon-separated list of paths for disk locations provides a mapping to non-standard locations.
Example: APP_DISK_PATH=/dev/oracleasm/disks:/dev/raw
HBAVERIFY_NUM_DELAY_SECS
Valid Values: Integer (in seconds)
Scope: This parameter can be set at the Data Collector level.
HBAverify command output varies with every run and may or may not provide all the Physical Disk drives. The command will be executed until all the LUN-derived disks are found. The logic excludes Direct Attached Storage disks while running hbaverify. This advanced parameter can be set to configure the number of extra runs for the command and the delay between the subsequent execution.
HOST_CONNECTION_PROTOCOL
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Text value (Default = WMI|SSH|TELNET)
Scope: This parameter can be set at the Data Collector level only.
Use this parameter to control which protocol is used for the host connection. For example, to turn off Telnet, use WMI|SSH.
HOST_CONNECTION_TIMEOUT
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Numeric value in seconds (Default = 60 seconds)
Scope: This parameter can be set at the Data Collector level only.
Use this parameter to set the period of time allowed before the host connection times out.
HOST_SOCKET_TIMEOUT
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Numeric value in seconds (Default = 180 seconds)
Scope: This parameter can be set the socket time-out for connections to hosts, for an OS, or for a specific host.
Use this parameter to update the command time-out for Windows servers for Windows host data collection. A corresponding time-out must be configured for the WMI Proxy server.
To set the time-out for the WMI Proxy server:
1. Edit the file:
<HOME>\APTAREWMIServer\conf\aptarewmiserver.properties
2. Modify or add this line to set the value in seconds: command_timeout=<value>
3. Restart the WMI Proxy server.
Example:
To set the time-out to 10 minutes, set the HOST_SOCKECT_TIMEOUT advanced parameter to 600 and modify the WMI Proxy file and set command_timeout=600. Then, restart the WMI Proxy server.
IGNORE_FILE_SYSTEMS
Use this parameter to filter a list of file systems for host resources data collection.
Valid Values: Example: /proc|/ahafs|/testfs
Scope: This parameter can be set at the Domain or Data Collector level.
This advanced parameter can be used to avoid reporting a data collection error for the File System category of a Host Resource collection, when a file system does not have a capacity value in the output of the df -k command.
More than one file system can be specified. In this case, file systems need to be separated by a pipe character ( | ).
IS_EMULEX_MAPPING_STRICT_CHECKING
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Y or N (Default = N)
Scope: This parameter can be set at the Domain or Data Collector level or for a specific OS, or for a specific host.
Emulex HBA mapping in Windows environments requires the SCSI bus-LUN-target mapping to strictly match the physical drive. Sometimes there may be a data collection issue where the LUNs are mapping to the wrong device names. This can happen if there are multi-paths using the same target and SCSI OS LUN in the output.
Use this parameter to turn on strict checking of the mapping.
NUM_HBAVERIFY_RUN
Valid Values: Integer
Scope: This parameter can be set at the Data Collector level.
HBAverify command output varies with every run and may or may not provide all the Physical Disk drives. The command will be executed until all the LUN-derived disks are found. The logic excludes Direct Attached Storage disks while running hbaverify. This advanced parameter can be set to configure the number of extra runs for the command and the delay between the subsequent execution.
STRICT_HOST_KEY_CHECKING
This parameter is shipped in the Portal software and is listed in the Add Advanced Parameter window.
Valid Values: Y or N (Default = N)
Scope: This parameter can be set at the Domain or Data Collector level only.
Use this parameter in the context of connecting to hosts through SSH via the use of private keys (that is, no password authentication).
• When the value is N, the “known hosts” file will automatically be updated when the Data Collector connects to host for the first time, or when the host’s key has changed.
• When the value is Y, the “known hosts” file will have to be manually maintained.
USE_VIO_RESTRICTED_SHELL
Valid Values: TRUE or FALSE (Default = FALSE) - Note that this is a case-insensitive value.
Scope: This parameter can be set at the Data Collector level.
Collection of host resources capacity data from IBM VIO/AIX servers can now use the VIO restricted shell to execute VIO commands, as supported by IBM. This collection method is enabled via this advanced parameter.