Symantec 5 manual Configuring SuSE network interfaces, See About installing and configuring VCS on

42Preparing to install VCS Performing preinstallation tasks

■The systems can access the shared storage.

4Test the network connections. Temporarily assign network addresses and use telnet or ping to verify communications.

LLT uses its own protocol, and does not use TCP/IP. So, you must ensure that the private network connections are used only for LLT communication and not for TCP/IP traffic. To verify this requirement, unplumb and unconfigure any temporary IP addresses that are configured on the network interfaces.

The installvcs program configures the private network in the cluster during installation.

See “About installing and configuring VCS” on page 51.

Configuring SuSE network interfaces

You must perform additional network configuration on SuSE. You need not perform this procedure for the systems that run SLES 10 or later. By default, SLES 10 uses udev to achieve persistent interface names. Refer to the OS documentation for information on configuring persistent interfaces on SLES 10.

In rare cases where RedHat does not automatically configure the network interfaces, RedHat users may also have to perform the network configuration.

Review the following tasks that allow VCS to function properly:

■VCS must be able to find the same network interface names across reboots.

■VCS must have network interfaces up before LLT starts to run.

Symantec suggests the following steps for configuring network interfaces on

SUSE.

Note: You must not reboot the system between configuring the persistent interface names and configuring the interfaces to be up before starting LLT.

Note: The MAC address in the ifcfg-eth-id-mac file can be in uppercase or lowercase. SUSE, and therefore the Veritas product installer, ignores the file with lowercase MAC address if the file with uppercase MAC address is present.