The Symantec High Availability Configuration wizard discovers the disks which are attached and the storage which is currently mounted. Ensure that the shared storage used by the application is mounted before you invoke the wizard.

For all the SAP WebAS instances that you want to configure, the SAP HOME path must be accessible from the node from where you invoke the Symantec High Availability Configuration wizard.

The sapmnt directory with valid SIDs must be available on the node from where you invoke the Symantec High Availability Configuration wizard.

The latest VRTSsapwebas71 and VRTSacclib packages must be installed on the nodes on which you want to configure SAP WebAS application monitoring.

Before you configure the enqueue replication server, you must configure the enqueue server in the cluster.

All SAP WebAS instances must be installed using virtual hosts, so ensure that the virtual hosts are reachable from each node in the cluster.

Before you start the primary application server and additional application server, ensure that the database instance is running.

You must not restore a snapshot on a virtual machine where an application is currently online, if the snapshot was taken when the application was offline on that virtual machine. Doing this may cause an unwanted failover. This also applies in the reverse scenario; you should not restore a snapshot where the application was online on a virtual machine, where the application is currently offline. This may lead to a misconfiguration where the application is online on multiple systems simultaneously.

While creating a VCS cluster in a virtual environment, you must configure the cluster communication link over a public network in addition to private adapters. The link using the public adapter should be assigned as a low-priority link. This helps in case the private network adapters fail, leading to a condition where the systems are unable to connect to each other, consider that the other system has faulted, and then try to gain access to the disks, thereby leading to an application fault.

You must not select teamed network adapters for cluster communication. If your configuration contains teamed network adapters, the wizard groups them as "NIC Group #N" where "N" is a number assigned to the teamed network adapters. A teamed network adapter is a logical NIC, formed by grouping several physical NICs together. All NICs in a team have an identical MAC address, due to which you may experience the following issues:

Verify that the boot sequence of the virtual machine is such that the boot disk (OS hard disk) is placed before the removable disks. If the sequence places the removable disks before the boot disk, the virtual machine may not reboot after an application failover. The reboot may halt with an "OS not found" error. This issue occurs because during the application failover the removable disks are detached from the current virtual machine and are attached on the failover target system.

Verify that the disks used by the application that you want to monitor are attached to non-shared controllers so that they can be deported from the system and imported to another system.

If multiple types of SCSI controllers are attached to the virtual machines, then storage dependencies of the application cannot be determined and configured.

The term 'shared storage' refers to the removable disks attached to the virtual machine. It does not refer to disks attached to the shared controllers of the virtual machine.

If you want to configure the storage dependencies of the application through the wizard, the LVM volumes or VxVM volumes used by the application should not be mounted on more than one mount point path.

The host name of the system must be resolvable through the DNS server or, locally, using /etc/hosts file entries.