After installing the RPMs, the installer continues to create configuration files and copies them to each system:
Creating Cluster Server configuration files ............ Done
Copying configuration files to north.................... Done
Copying configuration files to south.................... Done
Cluster Server configured successfully.
If you chose to configure the cluster in secure mode, the installer also configures the Symantec Product Authentication Service. Depending on the mode you chose to set up Authentication Service, the installer creates security principal or executes the encrypted file to create security principal on each node in the cluster. The installer creates the VxSS service group, creates Authentication Server credentials on each node in the cluster, and Web credentials for VCS users, and sets up trust with the root broker. Then, the installer proceeds to start VCS in secure mode.
The installer verifies on all the nodes if all NICs have PERSISTENT_NAME set correctly.
If the persistent interface names are not configured correctly for the network devices, the installer displays the following warnings:
Verifying that all NICs have PERSISTENT_NAME set correctly on north: For VCS to run correctly, the names of the NIC cards must be boot persistent. CPI WARNING V-9-122-1021 No PERSISTENT_NAME set for NIC with MAC address 00:11:43:33:17:28 (present name eth0), though config file exists! CPI WARNING V-9-122-1022 No config file for NIC with MAC address 00:11:43:33:17:29 CPI WARNING V-9-122-1022 No config file for NIC with MAC address 00:04:23:ac:25:1f
Set the PERSISTENT_NAME for all the NICs.
See Configuring SuSE network interfaces.
Caution If the installer finds the network interface name to be different from the name in the configuration file, then the installer exits.