Configuring application monitoring by using the Symantec High Availability Configuration Wizard

To configure a generic application for monitoring by using the Symantec High Availability Configuration Wizard:

  1. Launch the Symantec High Availability Configuration Wizard.
  2. Review the information on the Welcome panel and click Next.
  3. Select Generic Application, and then click Next.
  4. On the Component Selection panel, enter a name for the component and click Add Component.

    The component you added appears in the Component box.

  5. Specify the following details to configure the component for monitoring:
    • Start program: The complete path of the start program script.

    • Stop program: The complete path of the stop program script.

    • Program to force-stop the application: If you selected the Specify application force-stop program option, enter the complete path of the force-stop program script.

      Note:

      If you do not select the 'force-stop' option, VCS uses the stop program script that you specify for stopping the application.

    • At least one or more of the following:

      • Monitor program: The complete path of the monitor program script.

      • Application-related processes to monitor: Names of the application processes that must be monitored.

      • Application-generated PID files: Path names of the process ID (PID) files of your application.

    • Enable intelligent monitoring for this application: Select or clear this option to enable or disable intelligent monitoring for the application component. This option is selected by default. Symantec recommends that you enable intelligent monitoring of the application component.

    • User: The user name. Ensure that you specify a valid user with adequate privileges on the virtual machine where you configure the application. Else, application monitoring may fail.

    To remove a component from the Component box, use the Remove icon.

  6. To specify more application components for monitoring, repeat step 4 to step 5. Else, click Next.
  7. On the Storage Selection panel, select the appropriate mount points for the application instances that require storage, and click Next.

    Note:

    The Storage Selection panel does not appear if shared storage is not attached to the virtual machine.

  8. On the Define Start-Stop Order panel, to define the dependency between the components, select an application component from the Parent Component box and then select the components that it depends on from the Depends on box. When starting the application, the components are brought online in the defined order.

    Note:

    The Define Start-Stop Order panel appears only when you have added more than one component for monitoring.

  9. Click Next.
  10. On the Configuration Inputs panel, use the Edit icon to specify the user name and password of the systems for the VCS cluster operations.

    Cluster systems lists the systems included in the cluster configuration. Application failover targets lists the systems to which the application can fail over. Move the required systems to the Application failover targets list. Use the up and down arrow keys to define the priority order of the failover systems. The local system is selected by default for both, the cluster operations and as a failover target.

  11. Skip this step if you do not want to add more systems to your cluster.

    To add a system to the cluster, on the Configuration Inputs panel, click Add System. In the Add System dialog box, specify the following details of the system that you want to add to the VCS cluster and click OK:

    System Name or IP address

    Specify the name or IP address of the system that you want to add to the VCS cluster.

    User name

    Specify the user account for the system.

    Typically, this is the root user.

    Password

    Specify the password for the user account mentioned.

    Use the specified user account on all systems

    Select to use the specified user account on all those cluster systems that have the same user name and password.

    The wizard validates the details, and the system then appears in the Cluster Systems list.

    To remove a system from the cluster or from the Application failover targets list, use the Remove icon.

  12. Skip this step if you do not want to modify the default security settings for your cluster.

    If you want to modify the security settings for the cluster, click Advanced Settings. In the Advanced settings dialog box, specify the following details and click OK.

    Use single sign-on authentication

    Select to configure single sign-on using VCS Authentication Service for cluster communication.

    This option is enabled by default.

    Use VCS user privileges

    Select to configure a user with administrative privileges to the cluster.

    Specify the username and password and click OK.

    Note:

    The Advanced Settings link is not visible if the cluster is already created.

  13. Click Next.
  14. On the Network Details panel, select the type of network protocol to configure the VCS cluster network links and then specify the adapters for network communication. By default, the links are configured over Ethernet.

    Note:

    Symantec recommends that one of the network adapters must be a public adapter. You may assign low priority to the VCS cluster communication link that uses the public adapter.

    Depending on the network over which you want to configure the links, select one of the following:

    • Use MAC address for cluster communication (LLT over Ethernet) : Select the adapter for each network communication link. You must select a different network adapter for each communication link. This communication type configures the links over the non-routed network. Choose this mode only if the failover target systems reside in the same subnet.

    • Use IP address for cluster communication (LLT over UDP): Select the type of IP protocol and then specify the required details for each communication link. This communication type configures the links over the routed network. Choose this mode if the failover target systems reside in the same or different subnets. The adapters that you select must have an IP address. Symantec recommends that the IP address assigned to these adapters should be in different subnets.

      Select the IP protocol (IPv4 or IPv6) and then specify the following:

      Network Adapter

      Select a network adapter for the communication links.

      You must select a different network adapter for each communication link.

      IP Address

      Specify the IP address for cluster communication over the specified UDP port.

      Port

      Specify a unique port number for each link. You can use ports in the port range 49152 to 65535.

      A specified port for a link is used for all the cluster systems on that link.

      Subnet mask (IPv4)

      Displays the subnet mask details.

      Prefix (IPv6)

      Displays the prefix details.

    By default, one of the links is configured as a low-priority link on a public network interface. The second link is configured as a high-priority link. To change a high-priority link to a low-priority link, click Modify. In the Modify low-priority link dialog box, select the link and click OK.

  15. Click Next.
  16. Skip this step if you do not want to specify a virtual IP address for the application component. In this case, you must delete the Subnet mask details that the wizard automatically populates in the Subnet Mask field and click Next

    On the Virtual Network Details panel, select the IP network (IPV4 or IPv6). The IPv4 protocol is selected by default.

    Select the appropriate component and specify the following details for each failover system:

    Virtual IP address

    Specify a unique virtual IP address.

    You can specify only one virtual IP address for each component.

    Subnet Mask (for IPv4)

    Specify the subnet mask details.

    Prefix (for IPv6)

    Select the prefix details.

    Network Adapter

    Select the network adapter that will host the virtual IP.

    If you want to add another virtual IP address, click Add virtual IP address.

  17. Click Next.
  18. If you selected mount points for your application in step 7, the Target ESX Details panel appears.

    On the Target ESX Details panel, specify all the ESX hosts to which virtual machines can fail over. Each ESX host must be able to access the required shared datastores that contain visible disks.

    To specify the ESX hosts, click Add ESX Host and in the Add ESX Host dialog box, specify the following details and click OK:

    ESX hostname or IP address

    Specify the target ESX hostname or IP address.

    The virtual machines can fail over to this ESX host during vMotion. All the additional ESX hosts should have access to the datastore on which the disks used by the application reside.

    User name

    Specify a user account for the ESX host. The user account must have administrator privileges on the specified ESX host.

    Password

    Specify the password for the user account provided in the User name text box.

    The wizard validates the user account and the storage details on the specified ESX hosts.

    If you want to remove an ESX host, use the Remove icon.

  19. Click Next.
  20. On the Summary panel, review the VCS cluster configuration summary and then click Next to proceed with the configuration.

    If the network contains multiple clusters, the wizard verifies the cluster ID with the IDs assigned to all the accessible clusters in the network. The wizard does not validate the assigned ID with the clusters that are not accessible during the validation. Symantec recommends that you to validate the uniqueness of the assigned ID in the existing network. If the assigned ID is not unique or if you want to modify the cluster name or cluster ID, click Edit. In the Edit Cluster Details dialog box, modify the details as necessary and click OK.

  21. On the Implementation panel, the wizard creates the VCS cluster, configures the application for monitoring, and creates cluster communication links.

    The wizard displays the status of each task. After all the tasks are complete, click Next.

    If a configuration task fails, click View Logs to check the details of the failure. Rectify the cause of the failure and run the wizard again to configure application monitoring.

  22. Click Next and then click Finish to complete the wizard workflow.

    This completes the application monitoring configuration.

    If the application status shows as not running, click Start... to start the configured components on the system.