Type
  • Best Practice
Description
  • This article explains the recommended and alternative methods available to configure the Multi-node monitoring with Veritas Cluster Server KM for PATROL v3.0.00.
Additional Keywords
  • Veritas Cluster Server KM for PATROL, Multi-node

Related Topics

Knowledge Base

Configuring the Multi-node Monitoring Mode with the VCS KM

KB1211 - Jan 16, 2018

Table of Contents

Introduction

When an application is installed 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 situation, users need to configure the Veritas Cluster Server KM for PATROL in Multi-node monitoring mode.

Since version 3.0.00, different methods exist to monitor multiple nodes with Veritas Cluster Server KM for PATROL:

  • The Remote Monitoring method through the virtual cluster IP (easiest method): the KM remotely monitors the entire cluster through the virtual IP in Single-node Mode
  • The Remote Monitoring method through a non-cluster node (new method): the PATROL Agent and the KM need to be installed on a central host and the KM needs to be configured to monitor nodes remotely
  • The Local Monitoring method (old method): the PATROL Agent and the KM need to be installed on all the managed nodes.
  • A mixed method (local and remote monitoring): the PATROL Agent and the KM are installed on one managed node and the KM monitors the other nodes remotely.

In this article, we will describe the above methods, indicating which are recommended and suggesting alternative ones. But before diving deep into the configuration details, let's first review the terminology used in Veritas Cluster Server KM for PATROL.

Terminology

Concept Definition
Single-node Monitoring Mode Default configuration. The KM constantly monitors the entire cluster through the managed node either locally or remotely. The monitoring between all managed nodes is not coordinated.
Multi-node Monitoring Mode Recommended configuration for cluster environments. This configuration helps avoid false alarms and duplicate alerts by coordinating the monitoring between all managed nodes. Monitoring is performed from the active cluster node (Active Multi-node Mode).
Permanent Single-node Mode Default mode when the KM is in Single-node Monitoring mode configuration.
Temporary Single-node Mode Temporary mode which occurs if no active node is monitoring in Active Multi-node Mode.
Passive Multi-node Mode Mode adopted by a passive node when this passive node finds an active node in Active Multi-node Mode.

Available Configuration Methods - Pros and Cons

  Pros Cons
Remote monitoring through the Virtual IP of the Cluster in Single Node Monitoring (New method - Recommended)
  • Monitoring is easy to set up
  • No software installed on the cluster node

 

  • Single point of failure when the PATROL Agent crashes
  • Dependent on the availability of the virtual cluster IP.
Remote Monitoring in Multi-node Mode (New method - Recommended)
  • No software installed on the cluster node
  • Does not depend on cluster functionalities or cluster nodes availability
  • Single point of failure when the PATROL Agent crashes
Local and Remote Monitoring in Multi-node Mode (Mixed method)
  • No need for a dedicated PATROL agent host
  • Single point of failure when the PATROL Agent or the cluster node running the PATROL Agent crashes

 

Local Monitoring in Multi-node Mode (Old method)
  • No need for a dedicated PATROL agent host
  • No single point of failure on the PATROL Agent or VCS nodes
  • The PATROL Agent and KM are installed on each cluster node

Recommended Methods

Remote Monitoring Through the Virtual Cluster IP (Single-node Mode)

This is a remote monitoring method introduced in v3.0.00. The entire cluster is monitored remotely through the virtual cluster IP or the hostname associated to the virtual IP.  We need a central non-cluster node with PATROL Agent and the KM installed.

To find the virtual cluster IP, we can run the command below:
Obtaining the Virtual Cluster IP

Figure 1 - Obtaining the Virtual Cluster IP

To monitor the nodes through the virtual cluster IP:

Using the PATROL Console

  1. Right-click the Veritas Cluster Server instance > KM Commands > Configuration > VCS Nodes
  2. Provide a virtual cluster IP or the hostname associated to the virtual IP
  3. Make sure the status Enabled is selected
  4. Click Update
  5. Click Close
    Remote Monitoring Through the Virtual Cluster IP – Configuring Node

    Figure 2 - Remote Monitoring Through the Virtual Cluster IP – Configuring Node

  6. Wait for the KM to create the Setup instance
  7. Set the user account to be used to read and execute Veritas Cluster Server application programs and file systems:
    • Right click the VCS Setup instance > KM Commands > Configuration > Login
    • Enter the VCS admin credentials
    • Click OK

The KM monitors the entire cluster through that virtual IP remotely in Single-node Mode:
Remote Monitoring Through the Virtual Cluster IP – PATROL Tree View

Figure 3 – Remote Monitoring Through the Virtual Cluster IP – PATROL Tree View

Using TrueSight

  1. Create your monitoring policy
  2. In the Add Monitoring Configuration dialog box, configure the properties:
    • From the Monitoring Solution menu, select Veritas Cluster Server.
    • From the Version menu, select the latest version
    • The Monitor Profile Veritas Cluster Server KM is automatically selected
  3. In the VCS Monitoring Settings section, click Add
  4. In the VCS System section, enter a virtual IP or the hostname associated to the virtual IP.
  5. Set the VCS Credentials
  6. Make sure Enable Multi-node Monitoring Mode is unchecked
  7. Click OK twice
  8. Click Save
  9. Make sure the policy is deployed to the PATROL Agent (in our example: rt-patrol-agent) where the entire cluster is monitored through the virtual cluster IP remotely in Single-node Mode.

Remote Monitoring from a Non-Cluster Node (Multi-node Mode)

This is a new method introduced in v3.0.00. We need a central non-cluster node to monitor the VCS nodes remotely. In our example, we have two VCS nodes, sofia and bucharest. They are both monitored remotely from rt-patrol-agent, a host outside the cluster on which the PATROL Agent and VCS KM 3.0.00 have been installed.
 

To monitor this VCS cluster remotely from a PATROL Agent node outside the cluster:

Using the PATROL Console

  1. Configure the monitoring of both nodes:
    1. Right-click the Veritas Cluster Server instance > KM Command > Configuration > VCS Nodes
    2. Specify one of the VCS node details (in our example: sofia)
    3. Make sure the status Enable is selected
    4. Click Update
    5. Repeat the same for other VCS nodes (in our example: bucharest) and click Update
    6. Click Close
      Remote Monitoring from a Non-Cluster Node – Configuring Nodes
    7. Figure 4 - Remote Monitoring from a Non-Cluster Node – Configuring Nodes
  2. Wait for the KM to create the Setup instances
  3. Set the user account to be used to read and execute Veritas Cluster Server application programs and file systems:
    • Right click the VCS Setup instance > KM Commands > Configuration > Login
    • Enter the VCS admin credentials
    • Click OK
    • Repeat the same for other VCS nodes
  4. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes
    Remote Monitoring from a Non-Cluster Node in Single-Node Mode – PATROL Tree View

    Figure 5 - Remote Monitoring from a Non-Cluster Node in Single-Node Mode – PATROL Tree View

  5. Configure the multi-node monitoring from one node:
    1. Right-click one of the System instance (in our example: System: sofia) > KM Commands > Configuration > Monitoring Mode
    2. Select Multi-node Mode
    3. From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server
    4. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    5. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: rt-patrol-agent), the System ID (a unique ID for the VCS node; in our example: sofia), and the Cluster Node Name (the hostname defined in VCS; in our example: sofia).
    6. Make sure the Remote PATROL Agent Checking option is Disabled
    7. Click Update
    8. Repeat the same for other VCS nodes (in our example: bucharest) and click Update
    9. Click Close
      Remote Monitoring from a Non-Cluster Node – Configuring the Multi-node Mode

      Figure 6 - Remote Monitoring from a Non-Cluster Node – Configuring the Multi-node Mode

A full discovery is then performed on both nodes. The VCSMonitoringMode parameter indicates which node is active and passive. Some instances on the passive node (bucharest) disappear. In our example:

  • sofia is active and the VCSMonitoringMode parameter reads 2 = Active Multi-node Mode
  • bucharest is passive and the VCSMonitoringMode parameter reads 3 = Passive Multi-node Mode.
    Remote  Monitoring from a Non-Cluster Node – PATROL Tree View

    Figure 7 - Remote Monitoring from a Non-Cluster Node – PATROL Tree View

Using TrueSight

  1. Configure the monitoring of a VCS node (in our example: sofia)
    1. Create the monitoring policy
    2. In the Add Monitoring Configuration dialog box, configure the properties:
      • From the Monitoring Solution menu, select Veritas Cluster Server
      • From the Version menu, select the latest version
    3. The Monitor Profile Veritas Cluster Server KM is automatically selected
    4. In the VCS Monitoring Settings section, click Add
    5. Provide the hostname or IP address of the VCS system to be monitored
    6. Set the VCS Credentials
    7. Click OK
  2. Resume the procedure to configure the monitoring of all other VCS nodes (in our example: bucharest)
  3. Click OK and Save
  4. Make sure the policy is deployed to the PATROL Agent on the non-cluster node (in our example: rt-patrol-agent)
  5. Wait for the KM to create the instances in Permanent Single-node Mode on both managed nodes
  6. Configure the multi-node monitoring:
    1. Edit your monitoring policy
    2. Click the action button inline of the VCS system for which you wish to configure the multi-node monitoring mode and click Edit
    3. Check the Enable Multi-node Monitoring Mode box and configure the Multi-node Mode
    4. From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server
    5. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    6. Make sure the Enable Remote PATROL Agent Checking box is unchecked
      Remote Monitoring from a Non-Cluster Node – Configuring the Multi-node Monitoring

      Figure 8 - Remote Monitoring from a Non-Cluster Node – Configuring the Multi-node Monitoring

  7. In the Monitoring Nodes section:
    1. Click Add to configure the nodes to be monitored
    2. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: rt-patrol-agent), the Server ID (a unique ID for the VCS node; in our example: sofia), and Cluster Node Name (the hostname defined in VCS; in our example: sofia)
    3. Click OK
    4. Resume the procedure for each VCS node in the policy that is part of the Multi-node mode configuration (in our example: bucharest).
    5. In our example, we configured the monitoring nodes sofia and bucharest as follows:
      Configuring the Monitoring Node – sofia

      Figure 9 - Configuring the Monitoring Node – sofia

      Configuring the Monitoring Node – bucharest

      Figure 10 - Configuring the Monitoring Node – bucharest

  8. Click OK and Save. The monitoring policy should like this: two managed nodes (sofia and bucharest) in same multi-node configuration without remote PATROL Agent checking.
    Remote Monitoring from a Non-Cluster Node – Monitoring Policy

    Figure 11 - Remote Monitoring from a Non-Cluster Node – Monitoring Policy

Alternative Methods

Local and Remote Monitoring (Multi-node Mode)

This method is a combination of the new remote monitoring method introduced in v3.0.00 and the old local monitoring method. The PATROL Agent and the VCS KM are installed on one of the VCS node (in our example: bucharest) and monitors it locally and the other nodes remotely (in our example: sofia).

To configure local and remote monitoring in multi-node mode:

Using the PATROL Console

  1. Configure the monitoring of both nodes:
    1. Right-click the Veritas Cluster Server instance > KM Command > Configuration > VCS Nodes
    2. Specify the local VCS node details (in our example: bucharest)
    3. Make sure the status Enable is selected
    4. Click Update
    5. Repeat the same for other remote VCS nodes (in our example: sofia) and click Update
    6. Click Close

      Figure 12 - Local and Remote Monitoring Method – Configuring Nodes

  2. Wait for the KM to create the Setup instance
  3. Set the user account to be used to read and execute Veritas Cluster Server application programs and file systems:
    1. Right click the VCS Setup instance > KM Commands > Configuration > Login
    2. Enter the VCS admin credentials
    3. Click OK
    4. Repeat the same for other VCS nodes
  4. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes.
  5. Configure the multi-node monitoring from one node:
    1. Right-click one of the System instance (in our example: System: bucharest) > KM Commands > Configuration > Monitoring Mode
    2. Select Multi-node Mode
    3. From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server
    4. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    5. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: bucharest), the System ID (a unique ID for the VCS node; in our example: bucharest), and the Cluster Node Name (the hostname defined in VCS; in our example: bucharest)
    6. Ensure the Remote PATROL Agent Checking option is Disabled
    7. Click Update
    8. Repeat the same for other VCS nodes (in our example: sofia) and click Update
    9. Click Close
      Local and Remote Monitoring Method – Configuring Multi-node Mode Monitoring

      Figure 13 - Local and Remote Monitoring Method – Configuring Multi-node Mode Monitoring

A full discovery is then performed on both nodes. The VCSMonitoringMode parameter indicates which node is active and passive. In our example:

  • sofia is active and the VCSMonitoringMode parameter reads 2 = Active Multi-node Mode
  • bucharest is passive and the VCSMonitoringMode parameter reads 3 = Passive Multi-node Mode.
    Local and Remote Monitoring Method – PATROL Tree View

    Figure 14 - Local and Remote Monitoring Method – PATROL Tree View

Using TrueSight

  1. Configure the monitoring of a VCS node (in our example: sofia)
    1. Create the monitoring policy
    2. In the Add Monitoring Configuration dialog box, configure the properties:
    3. From the Monitoring Solution menu, select Veritas Cluster Server
    4. From the Version menu, select the latest version The Monitor Profile Veritas Cluster Server KM is automatically selected
    5. In the VCS Monitoring Settings section, click Add
    6. Provide the hostname or IP address of the VCS system to be monitored
    7. Set the VCS Credentials
    8. Click OK
  2. Resume the procedure to configure the monitoring of all other VCS nodes (in our example: bucharest)
  3. Click OK and Save
  4. Make sure the policy is deployed to the PATROL Agent on the VCS node where the PATROL Agent and VCS KM are installed (in our example: bucharest)
  5. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes
  6. Configure the Multi-node monitoring:
    1. Edit your monitoring policy
    2. Click the action button inline of the VCS node for which you wish to configure the Multi-node monitoring mode and click Edit
    3. Check the Enable Multi-node Monitoring Mode and configure the Multi-node Mode
    4. From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server
    5. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    6. Make sure the Enable Remote PATROL Agent Checking box is unchecked
      Local and Remote Monitoring Method – Configuring the Multi-node Monitoring

      Figure 15 - Local and Remote Monitoring Method – Configuring the Multi-node Monitoring

  7. In the Monitoring Nodes section:
    1. Click Add to configure the nodes to be monitored
    2. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: bucharest), the Server ID (a unique ID for the VCS node; in our example: bucharest), and Cluster Node Name (the hostname defined in VCS; in our example: bucharest)
    3. Click OK
    4. Resume the procedure for each remote VCS node in the policy that is part of the Multi-node mode configuration (in our example: sofia)
    5. In our example, we configured the monitoring nodes bucharest and sofia as follows:
      Configuring the Monitoring Node - bucharest

      Figure 16 - Configuring the Monitoring Node - bucharest

      Configuring the Monitoring Node - sofia

      Figure 17 - Configuring the Monitoring Node - sofia

  8. Click OK and Save. The monitoring policy should look like this: two managed nodes (sofia and bucharest) in same multi-node configuration without remote PATROL Agent checking.

    Local and Remote Monitoring Method – Monitoring Policy

    Figure 18 - Local and Remote Monitoring Method – Monitoring Policy

A full discovery is then performed on both nodes. The VCSMonitoringMode parameter indicates which node is active and passive. In our example:

  • sofia is active and the VCSMonitoringMode parameter reads 2 = Active Multi-node Mode
  • bucharest is passive and the VCSMonitoringMode parameter reads 3 = Passive Multi-node Mode.

Local Monitoring (Multi-node Mode)

This method is used in versions older than v3.0.00. Although this method is maintained in v3.0.00 for customers who do not wish to change their configuration immediately, Sentry Software does not recommend using it due to the complexity of installing the PATROL Agent and the KM on every cluster node.

In this method, nodes are monitored locally. The status of the remote node is checked using an Agent-to-Agent communication.

Using the PATROL Console

  1. Configure the monitoring of the local node:
    1. Right-click the Veritas Cluster Server instance > KM Command > Configuration > VCS Nodes
    2. Specify the local VCS node details (localhost or the hostname of the local node)
    3. Make sure the status Enable is selected
    4. Click Update
    5. Click Close

      Figure 19 - Local Monitoring Method – Configuring Nodes

  2. Wait for the KM to create the Setup instance.
  3. Set the user account to be used to read and execute Veritas Cluster Server application programs and File systems:
    • Right click the VCS Setup instance > KM Commands > Configuration > Login
    • Enter the VCS admin credentials
    • Click OK
  4. Repeat the same steps above to configure the other VCS nodes through their PATROL Agent and KM installations
  5. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes. Duplicate alerts should be triggered
  6. Configure the multi-node monitoring from one node:
    1. Right-click one of the System instance (in our example: System: sofia) > KM Commands > Configuration > Monitoring Mode
    2. Select Multi-node Mode
    3. From the Cluster Application pull-down list, select appropriate cluster application. In our example : Veritas Cluster Server
    4. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    5. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: sofia), the System ID (a unique ID for the VCS node; in our example: localhost), and the Cluster Node Name (the hostname defined in VCS; in our example: sofia).
    6. Make sure the Remote PATROL Agent Checking option is Enabled
    7. Click Update
    8. Repeat the same for other VCS nodes (in our example: bucharest) and click Update
    9. Click Close

      Figure 20 - Local Monitoring Method – Configuring the Multi-node Monitoring Mode

  7. Since the Remote PATROL Agent Checking is Enabled, provide the PATROL Agent configuration details for all PATROL Agents monitoring the VCS nodes and click OK.
    Configuring PATROL Agent Details - sofia

    Figure 21 - Configuring PATROL Agent Details - sofia


    Configuring PATROL Agent Details - bucharest

    Figure 22 - Configuring PATROL Agent Details - bucharest

A full discovery is then performed on both nodes. The VCSMonitoringMode parameter indicates which node is active and passive. In our example:

  • sofia is active and the VCSMonitoringMode parameter reads 2 = Active Multi-node Mode
  • bucharest is passive and the VCSMonitoringMode parameter reads 3 = Passive Multi-node Mode.

Some instances on the passive node (bucharest) disappear.
Local Monitoring Method – PATROL Tree View

Figure 23 - Local Monitoring Method – PATROL Tree View

Using TrueSight

  1. Configure the monitoring of a VCS node on which the PATROL Agent is installed
    1. Create the monitoring policy
    2. In the Add Monitoring Configuration dialog box, configure the properties:
    3. From the Monitoring Solution menu, select Veritas Cluster Server
    4. From the Version menu, select the latest version
    5. The Monitor Profile Veritas Cluster Server KM is automatically selected
    6. In the VCS Monitoring Settings section, click Add
    7. Enter localhost as the hostname of the VCS system to be monitored
    8. Set the VCS Credentials
    9. Click OK twice.
    10. Click Save.
      Local Monitoring Method – Configuring the VCS Systems Monitoring

      Figure 24 - Local Monitoring Method – Configuring the VCS Systems Monitoring

  2. Make sure the policy is deployed to all VCS nodes in the cluster (in our example, sofia and bucharest).
  3. Wait for the KM to create the instances in Permanent Single-node Mode on all managed nodes
  4. Configure the Multi-node monitoring:
    1. Edit your monitoring policy
    2. Click the action button inline of the VCS system for which you wish to configure the Multi-node monitoring mode and click Edit
    3. Check the Enable Multi-node Monitoring Mode and configure the Multi-node Mode
    4. From the Cluster Application pull-down list, select appropriate cluster application. In our example: Veritas Cluster Server
    5. In the Failover Group Name field, enter the failover group name, which is online on one cluster node and offline on the others. In our example: ClusterService
    6. Check the Enable Remote PATROL Agent Checking box
      Local Monitoring Method – Configuring the Multi-node Monitoring

      Figure 25 - Local Monitoring Method – Configuring the Multi-node Monitoring

  5. In the Monitoring Nodes section:
    1. Click Add to configure the nodes to be monitored
    2. Provide the PATROL Agent Hostname (host where the PATROL agent is installed; in our example: bucharest), the Server ID (localhost), and Cluster Node Name (the hostname defined in VCS; in our example: bucharest)
    3. Click OK
    4. Resume the procedure for each VCS node that is part of the Multi-node mode configuration (in our example: sofia). In our example, we configured the bucharest node as follows:
      Local Monitoring Method – Configuring the Multi-node Monitoring

      Figure 26 - Local Monitoring Method – Configuring the Multi-node Monitoring

  6. In the PATROL Agent Configuration section, click Add and provide the required information
    Local Monitoring Method – Setting the PATROL Agent Configuration

    Figure 27 - Local Monitoring Method – Setting the PATROL Agent Configuration

  7. Click OK
  8. Resume the procedure for each VCS node that is part of the Multi-node mode configuration
  9. Click Save. The monitoring policy should look like this: one managed node (localhost) in multi-node mode with remote PATROL Agent checking.
    Local Monitoring Method – Monitoring Policy

    Figure 28 - Local Monitoring Method – Monitoring Policy

A full discovery is then performed on both nodes. The Monitoring Mode indicates which node is active and passive. In our example:

  • sofia is active and the Monitoring Mode reads 2 = Active Multi-node Mode
  • bucharest is passive and the Monitoring Mode reads 3 = Passive Multi-node Mode.