|
|
|
|
AlertActions
|
n/a
|
List of alert actions to be executed by Hitachi Disk Arrays KM for PATROL upon a problem with the managed Hitachi storage system.
|
collectionHubHeapSizeMax
|
None
|
Maximum heap size in megabytes allocated to the Java Collection Hub.
|
collectionHubHeapSizeMin
|
None
|
Minimum heap size in megabytes allocated to Java Collection Hub.
|
collectionHubOverrideJavaCommandLine
|
None
|
Command line used by the KM to launch the Java Collection Hub. This variable should only be set if instructed by Sentry Support.
|
debugEndTime
|
None
|
Specifies when the debug mode will be disabled.
Format required: YYYY/MM/DD HH:MM:SS
|
debugMode
|
0 = disabled
|
When set to '1', enables the debug mode of the KM.
Default: Not set
|
defaultReinitializationOptions
|
None
|
List of default options to be executed by Hitachi Disk Arrays KM for PATROL on reinitialization.
| • | resetThresholdManagementMode |
| • | resetRemovedPausedObjectList |
Insert a colon “;” between the variable and its value: “resetThresholds;1”; and if you enter multiple variables, they need to be separated by a carriage return.
Example: “resetThresholds;1” will display the remove thresholds option selected by default in the Reinitialize KM wizard.
|
disableJavaInformationMessage
|
0 = activated
|
When set to "1", deactivates the pop-up information message displayed when the Java settings are modified.
|
disableJRECheck
|
0 = JRE validation tests enabled
|
When set to 1, disable the validation tests of the JRE used by the KM to run Java code. This can be used to force the KM to use a non-Sun or non-Oracle JRE.
|
disablePslExecuteBugWorkaround
|
0 = activated
|
When set to ‘1’, deactivates the workaround in the KM for a bug in the PslExecute() PSL function.
If the KM detects that the version of the PATROL Agent is affected by the PslExecute() bug, it uses an alternate technique to create asynchronous threads with the event_trigger() function and the RemPsl standard event. The disablePslExecuteBugWorkaround variable disables this workaround.
|
disableVolumeMonitoring
|
0 = Volume Monitoring enabled
|
When set to 1, deactivates volumes monitoring. When the volumes monitoring is disabled, discovery and collect requests and operations are no longer performed.
|
exportScheduling
|
None
|
Time when the activity and/or LUNs Mapping Table reports will be generated. Format required: HH:MM:SS
|
forceClassicConfigMode
|
0 = disabled
|
When the KM is used with BMC ProactiveNet, all the KM configuration menus are disabled in the PATROL Consoles. To enable them, set the forceClassicConfigMode variable to 1.
|
javaPassword
|
None
|
Password associated to the javaUsername variable.
|
javaPath
|
None
|
Path to the folder containing the Java executable used by the Collection Hub.
|
javaUsername
|
None
|
Username used to launch the Java Collection Hub.
|
pausedObjectList
|
n/a
|
List of the PATROL object path of the paused objects. (i.e. for which no collection will be performed).
|
productVersion
|
Automatically set by the KM during its initialization
|
Identifies the current version of the KM in the configuration. Do not alter this value.
|
psCommand
|
n/a
|
Command used on UNIX/Linux systems to retrieve the list of the currently running processes.
Note: This command is used for debug purpose.
|
removedObjectList
|
n/a
|
List of instances that have been removed from the monitoring environment through the Remove KM Command.
|
scheduledReports
|
n/a
|
List of reports that will be automatically generated. Possible values:
| • | ACTIVITY to generate storage centers, controllers, disk folders, disks, ports and volumes activity reports |
| • | LUNS_MAPPING_TABLE to list mapped and unmapped LUNs. |
Values must be delimited by \n.
|
startupDelay
|
0 second
|
To specify the number of seconds that Hitachi Disk Arrays KM for PATROL will wait before starting its discovery. This variable may be useful on fast booting computers where the Hitachi SMI-S Provider starts after the KM and triggers an alert.
|
ThresholdsManagementMode
|
Retrieved from the KM configuration
|
Specifies how the KM should manage the alert thresholds on parameters. Please read carefully the User Guide chapter for more information on this topic.
Possible values:
| • | 'empty' (automatic detection of the suitable threshold management) |
| • | ‘as’ (through PATROL for Event Management) |
| • | ‘tuning’ (through the standard "Override parameter" mechanism) |
| • | ‘none’ (No threshold is set by the KM) |
|
