-
Home
- Monitoring Studio Web Interface
Configure Veritas File System KM
This section explains the settings required to configure Veritas File System KM via the Monitoring Studio X Web interface.
Configuring VxFS Nodes Monitoring
Veritas File System KM allows you to monitor several VxFS cluster systems with one PATROL Agent.
To add a new node to your monitoring environment
- Access the Monitoring Studio X Web Interface.
- Click KMs > Veritas File System.
- Click the New Node… button.
Identify the Node
Provide the following information to identify the VxFS System:
| Property | Description |
|---|---|
| Hostname or IP Address | Enter the hostname or IP address of the VxFS System to be monitored. For a local host, you may enter localhost. |
| System Type | Leave the VxFS system type as UNIX/Linux, since VxFS does not support Windows platforms. |
| Node ID | ID to be used to store the node configuration in the PATROL Agent configuration. This Internal ID is automatically generated based on the Hostname or IP Address provided but can be edited if needed. |
| Enable Monitoring | Set to ON by default. Turn this property OFF to disable the monitoring of the node. |
| Create a Separate Device in TrueSight | Set to ON by default. Turn this property OFF if you do not want the VxFS node to appear as a separate device in TrueSight. |
Configure the KM User Account
A user account with administrative privileges must be configured to read and execute Veritas File System application programs and access file systems. Enter the Username and Password required to execute VxFS commands on the VxFS node.
VxFS commands can be executed as a sudo user on UNIX/Linux systems. To do so, turn the Use Sudo option ON and provide the full path of the Sudo Binary File.
Add-ons
You can monitor additional InfoScale Storage Foundation products if the following Knowledge Modules are installed and loaded on the PATROL Agent:
When these KMs are properly installed and configured, simply turn ON the option to enable monitoring. The add-on KMs will then switch to Classic Mode and share the credentials and node configuration from the VFS KM. Any configuration set in TrueSight/Helix Infrastructure Policies will be ignored.
Monitored Components
By default, all VxFS components are monitored with optimal configuration. However, you can disable and/or customize the monitoring of any component to better suit your requirements.
To configure the monitored components:
- Use the ON/OFF button to activate or deactivate the monitoring of any component in the list.
- Click on the relevant STATUS MAPPING… button to customize the status mapping for any status parameter available for that component.
- By default, alerts will automatically be acknowledged unless you modified the settings to allow manual acknowledgement. Click the AUTOMATIC button to switch to the MANUAL mode.
Configure Advanced Settings (Optional)
Monitoring Mode
By default, Veritas File System KM is configured to operate in Single-node Mode. In a cluster environment, i.e. active on one cluster node and passive on others, false alarms and duplicate alerts may occur. To avoid such a situation, you need to switch to Multi-node Mode, if you monitor Veritas File System KM from cluster nodes.
- Click the Single-node Mode button to switch to Multi-node Mode
- Select the appropriate Cluster Application and provide the Failover Group Name which is online on one cluster node and offline on the others. Leave this field blank if you previously selected Veritas Cluster File System. The Veritas File System KM will then monitor the entire cluster from the active system, which is identified by the
vxdctl -c modecommand. This method requiresvxconfigdin enable mode with its clustered state active - Click the ADD NODE button to individually add the nodes you wish to monitor. Provide the following information:
- PATROL Agent Hostname: the host from where this node is monitored
- Node ID: the internal ID specified for the VxFS node
- Cluster Node Name: the hostname defined in the selected Cluster Application.
Click the Multi-node Mode button to switch back to Single-node Mode.
VxFS Discovery
Veritas File System KM automatically discovers the application paths and the node type and the default values are set to comply with most of VxFS systems. However, you can customize these settings to better suit your requirements. Note that modifying discovery configurations should be used with caution as it affects the monitoring functionality.
To configure the VxFS Discovery settings, click the Automatic button to turn on the Custom mode and provide the following information:
- VxFS Installation Path: Provide the path to the directory where the VxFS software is installed. By default, Veritas File System KM automatically locates the VxFS software installation directory if you have installed the solution with the default recommended settings. If you have chosen to install the solution in a custom directory, you are required to provide its location.
Click the CUSTOM button to switch back to AUTOMATIC mode and discard all custom settings.
Remote Connection settings
When you configure the monitoring of a remote host, you may want to specify the time after which the connection to the remote node will time out or the maximum number of simultaneous connections allowed to the remote node:
- In the Connection Timeout field, enter the number of seconds after which the connection to the remote node will time out
- In the Maximum Connections field, enter the maximum number of simultaneous connections allowed to the remote node.
Important: Changing the values for these properties may impact the performance of your monitoring environment.
VxFS KM Temp Paths
The default VxFS KM temporary directory paths can be manually specified to better suit your requirements.
Click the DEFAULT button to switch to the CUSTOM mode and provide the following information:
- Remote Temp Directory Path: Provide the path to the directory where the temporary files are saved on remote nodes. Default is /var/tmp (on UNIX/Linux) or C:\Windows\Temp (on Windows).
- Local Temp Directory Path: Provide the path to the directory where the temporary files are saved on the PATROL Agent node (Default is
<PATROL_HOME>/lib/VFS/tmpwhere<PATROL_HOME>is the PATROL Agent installation path)
Click the CUSTOM button to switch back to the DEFAULT mode and reset all paths to their default settings.
KM Settings
The KM Settings page enables you to define the configuration mode and the Java Settings for Veritas File System KM for PATROL.
Configuration Mode
Veritas File System KM can be used with the Monitoring Studio Web interface. If the configuration is deployed using a BMC Helix/TrueSight Operations Management CMA policy, the KM will run in CMA Mode. In this mode, only the Status Mappings, Debug Settings and Java Settings can be changed via the Monitoring Studio Web interface. To allow full configuration from the Web interface, turn the Force Classic Configuration Mode option ON. This will force the KM to run in Classic Mode, ignoring any Veritas File System KM configuration deployed from the CMA policy.
Java Settings
To operate properly, Veritas File System KM requires that Java 1.8.00 or higher and a Java Runtime Environment (JRE) are installed on the same system that runs the PATROL Agent.
The Java Settings page displays information about the JRE currently in use and a list of all the JREs installed on the monitored system. You can also configure the following options to fine-tune the Java properties:
| Options | Description |
|---|---|
| Automatically Select Appropriate JRE | To let Veritas File System KM automatically find and use the most compatible JRE upon the initial discovery that occurs when the PATROL Agent and Veritas File System KM start. |
| Execute the JVM as an Alternate User | By default, the Java process is launched with the same credentials as the PATROL Agent. If the PATROL Agent’s default account does not have sufficient privileges to perform the operations required by the Java Collection Hub, another user account can be provided. |
| Java Minimum Heap Size | To customize the minimum size (in MB) of the Java Hub Heap Memory according to your environment requirements. By default, the minimum size is set to 128 MB. |
| Java Maximum Heap Size | To customize the maximum size (in MB) of the Java Hub Heap Memory according to your environment requirements. By default, the maximum size is set to 512 MB. |
| Disable JRE Pre-Validation | By default, Veritas File System KM checks that the selected JRE meets the requirements. However, you can disable this option to bypass the compatibility check. Use this option only if you are certain that the provided JRE is compatible even if the compatibility check fails. An unsuitable JRE will prevent Veritas File System KM to operate properly. |
| JVM Arguments | To provide arbitrary arguments to the java -jar … command line that Veritas File System KM uses to launch the Java Collection Hub in the Command line options field. |
The JVM needs to be restarted for your new settings to be taken in account.
Download.CFG
You can export Veritas File System KM configuration as a pconfig file (.CFG) that can be imported into a TrueSight/Helix CMA policy. All the Agents using the policy will therefore be able to monitor the same VxFS nodes.
Reinitializing Veritas File System KM
Refer to the Troubleshooting section for details.