Previous Topic: Background ImagesNext Topic: How to Update a High Availability Implementation with Multiple NICs


How to Implement a Tiered CA SOI Deployment in a MSCS Environment

As an administrator, you can configure a tiered CA SOI deployment. The deployment uses CA SOI Domain connectors to send service information from lower-tier (or remote) SA Managers to an Enterprise SA Manager. You can configure a tiered CA SOI deployment for high availability, so that not only does each individual CA SOI instance fail over appropriately, but the CA SOI Domain connectors can also detect a failover in their remote SA Managers and switch to collecting data from the secondary node when required.

Each CA SOI instance requires its own cluster, and distributing components across systems requires multiple clusters per instance. Each cluster must have the same CA SOI components installed on each necessary node.

Complete the following process to implement a tiered CA SOI deployment in a MSCS environment:

  1. Install all remote CA Catalyst and CA SOI instances and configure them for high availability according to the instructions in How to Implement CA SOI in a MSCS Environment.
  2. Install the Enterprise CA SOI tier, including CA SOI Domain connectors for each remote CA SOI tier, on nodes in a separate cluster from the other tiers and configure the CA Catalyst and CA SOI enterprise tier for high availability according to the instructions in How to Implement CA SOI in a MSCS Environment.

    Adhere to the following conventions when installing CA SOI Domain connectors as part of the enterprise tier:

    The tiered CA SOI deployed is configured for high availability. Each tier can fail over as with a typical high availability implementation, and if a remote tier fails over, the CA SOI Domain connector can collect information from its secondary node for transmittal to the Enterprise SA Manager.