Specifying the underlying domains

An administrator uses the IC Domain Configuration objects to specify the underlying VoIP Availability Manager, IP Availability Manager, and Adapter Platform domains in a VoIP Availability Manager deployment. Doing so provides the sources of topology and events for the Global Manager and associates each underlying domain with the proper DXA file.

The expectation is that a user will either accept the default VoIP Availability Manager named VoIP-AM or make a copy of the default to create a new VoIP Availability Manager having a different name, say EAST-VoIP-AM.

This section provides procedures for the following two configuration scenarios:

• Configuration scenario 1: A VoIP Availability Manager deployment containing a VoIP Availability Manager named VoIP-AM, an IP Availability Manager named INCHARGE-AM, and an Adapter Platform named INCHARGE-OI.

• Configuration scenario 2: A VoIP Availability Manager deployment containing a VoIP Availability Manager named EAST-VoIP-AM, two IP Availability Managers named EAST-AM1 and EAST-AM2, and an Adapter Platform named EAST-OI.

  To specify the underlying domains in a more complex VoIP Availability Manager deployment, consult the VMware Smart Assurance Service Assurance Manager Configuration Guide.

  Note:

  Depending upon the Service Assurance Manager version, Business Impact Manager may or may not appear listed as an underlying domain. For version 8.0, INCHARGE-MBIM is listed as an underlying domain which you can enable. For version 7.2, Business Impact Manager is not listed but is automatically enabled as part of the Global Manager. The following scenarios assume that 7.2 Business Impact Manager is deployed.