Capacity Manager 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 Capacity Manager data collection and can be added using:
Admin > Advanced > Parameters, described in Adding an Advanced Parameter. EMC_MULTIPATH_OFF
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 Data Collector level.
Use this parameter to turn off EMC PowerPath Multi-Pathing Collection. Servers can have EMC PowerPath and Device Mapper multi-paths at the same time on Linux. If your environment has file systems on Device Mapper multi-pathed disks, it is required to turn off EMC PowerPath.
EMC_VMAX_INCLUDE_ALL_MASKINGVIEWS
Valid Values: Y or N (Default = N)
Scope: This parameter can be set at the Data Collector level.
Use this parameter for EMC Symmetrix VMAX array collection when the path between the initiator and target are missing. Data Collector parsers which construct the storage path use the command:
symaccess -sid <sid>list view -v -detail
When the Data Collector parser constructs the storage path, it assumes that masking view names are unique, so it does not process information from 2nd instance of the same view name. This causes the path to be ignored. Set this advanced parameter to have the parser processes paths from all instance of masking views.
Set this parameter only when
symaccess -sid <sid>list view -v -detail
is showing multiple instances of the masking view.
HDS_HTM_JPCCTRL_PATH
Valid Values: Text string
Scope: This parameter can be set at the Domain and Data Collector levels.
Used for Hitachi Array performance collection (Hitachi Tuning Manager).
It defines the relative path for executing the JPCCTRL command. This is required when the executables for jpcctrl and jpcrdef are at locations that are different from what is defined in the Data Collector policy.
For example, if the value for HDS_HTM_JPCCTRL_PATH is set to /opt, the command path for jpcctrl will be:
/opt/jp1pc/tools/jpcctrl
To use this parameter, take the steps similar to this example:
1. Identify the location of the jpcrdef and jpcrpt files/commands (HTnM location). For example, if these two files (commands) exist in C:\ProgramFiles\HiCommand\TuningManager\PerformanceReporter\tools\, then the HTnM install location would be C:\ProgramFiles(x86)\HiCommand\TuningManager\.
2. Check if the jpcctrl file (command) exists in the location: HTNM_LOCATION\jp1pc\tools\. If it does, then the Data Collector should run without any issues. If it does not, create the HDS_HTM_JPCCTRL_PATH Advanced Parameter with a value of: C:\ProgramFiles(x86)\HiCommand\TuningManager\
REMOTE_RAID_AGENT
Valid Values: Y or N (Default = N)
Scope: This parameter can be set at the Data Collector level.
Used for Hitachi array performance collection (Hitachi Tuning Manager). Configure this advanced parameter when there are distributed RAID agents (remote RAID agents).
If the value is set to Y, the Data Collector displays the configuration and status of Collection Manager and Agent services on all the remote hosts. Set the REMOTE_RAID_AGENT parameter to Y when we want to get the status of the agent services on all the hosts.
If no value is set, or the value is set to N, the Data Collector checks the operating status of all services on the local host of the Tuning Manager system.
SYMSTAT_COUNT
Valid Values: Numeric (Default = See below)
Scope: This parameter can be set at the Data Collector level.
Used for EMC Symmetrix array performance collection.
Use this advanced parameter to gather more granular performance data. This parameter sets the count of data sets for the custom interval. Use this in conjunction with
SYMSTAT_INTERVAL_SECONDS.
Default Values:
If these advanced parameters are not set, then the defaults are set to:
• count = 1
• interval is derived from the polling frequency of the performance probe.
SYMSTAT_INTERVAL_SECONDS
Valid Values: Numeric in seconds (Default = See below)
Scope: This parameter can be set at the Data Collector level.
Used for EMC Symmetrix array performance collection.
Use this advanced parameter to gather more granular performance data. This parameter customizes the data collection interval. Use this in conjunction with
SYMSTAT_COUNT.
Default Values:
If these advanced parameters are not set, then the defaults are set to:
• count = 1
• interval is derived from the polling frequency of the performance probe.
The reason for using CLIENT is that in some cases the CIM server appears to not return all requested relationships. Using CLIENT will require more disk space on the collector (but not excessive - 10s or 100s of MB) and will tend to take longer before persisting at the start of collection, but less time at the end.