Implementation in a Microsoft Cluster Server Environment › How to Update a High Availability Implementation with Multiple NICs

How to Update a High Availability Implementation with Multiple NICs

As an administrator, you must manually correct the virtual node name suffix in all necessary places.

MSCS 2008 typically requires two NIC interfaces: one for the internal heart beat and another for the public network. Additional NICs may exist, such as one for a private network. If you have performed a high availability implementation of CA SOI in an environment with additional NICs that have different domain suffixes, the resource kit automatically uses the suffix from the cluster node instead of the virtual node.

Important! This process is only necessary in the atypical use case described, when multiple NICs cause a situation where the suffix of the cluster nodes differs from that of the virtual node.

Complete the following process to correct the virtual node name suffix in an environment with multiple NICs:

1. Complete all steps in How to Implement CA SOI in a MSCS Environment.
2. Make a backup copy of the SOI_HOME\resources directory on the shared disk.
3. Offline the CA SOI cluster resources.
4. Update all XML files in the SOI_HOME\resources directory with the virtual node name defined so that it uses the correct suffix. Files that require updates include the following:
   • eventManagerServerConfig.xml
   • Configurations\SSA_IFW_servername.xml
   • Configurations\mtc_servername.xml
5. Update the following files to update the suffix in the virtual node name:
   • SOI_HOME\tomcat\webapps\activemq-web\WEB-INF\caifwmq.xml
   • SOI_HOME\SamUI\webapps\sam\server-config.xml
   • SOI_HOME\tomcat\common\classes\eventManagerClientConfig.xml
   • SOI_HOME\ServiceDiscovery\connectivityContext.xml

   Note: Some of these files may not exist if the component is not installed on the same cluster or if the specific option was not selected as part of the CA SOI installation.

6. Update the following Registry files located at SOI_HOME\tomcat\registry\topology\physical\node0\sor to update the suffix in the virtual node name:
   • restserver.xml
   • sorapp.xml
   • ssaserver.xml
   • wsman.properties

   Note: These files may not exist if the SA Manager was installed on a different cluster.

7. Run SOI_HOME\tomcat\registry\registryloader.bat.

   The updated files are loaded into the Registry.

8. Online the CA SOI cluster resources.
9. Remove any duplicate connectors that use the old virtual node name suffix.
10. (Optional) Repeat this procedure if necessary for an implementation that uses multiple clusters.

Note: A separate process is required for cluster implementations of CA Event Integration-based Event connector. For more information, see the CA Event Integration documentation.