For the single main server, adjuncts can use the PE interface of the main server for connectivity to the main server. For the Survivable Remote and Survivable Core Servers, there are three adjuncts, the CMS, AESVCS, and the CDR, that are supported using the Survivable Remote or Survivable Core Server’s PE interface. This section provides a high-level overview of the adjuncts supported by the Survivable Core and Survivable Remote Servers and how they are administered to use the PE interface.

• Survivable CMS

  Starting with CMS Release 13.1, you can use a Survivable CMS co-located at the site of the Survivable Core or Survivable Remote Server. A Survivable CMS is a standby CMS that collects data from a Survivable Remote or Survivable Core Server when the main server is not operational or when the customer is experiencing a network disruption. A Survivable CMS should not be located at the same location as the main server.

  During normal operations, the Survivable CMS has a connection to the Survivable Core or Survivable Remote Server but does not collect data or support report users. Only the main CMS server collects data. When a Survivable Core Server assumes control of one or more port networks, or a Survivable Remote Server is active, the Survivable Core Server and/or the Survivable Remote Server sends data to the Survivable CMS.

• CDR

  The server initiates the connection to the CDR unit and sends call detail information over the configured link. The link remains active at all times while the CDR unit waits for data to be sent by a connected server. In the case of a Survivable Core or Survivable Remote Server, data will not be sent until the survivable server becomes active. Some CDR units can collect data from multiple servers in a configuration, separately or all at once. For information on the capability of your CDR unit, check with your CDR vendor.

  The CDR unit is administered on the IP Services screen. To use the PE interface, procr must be entered in the Local Node field.

• AESVCS

  AESVCS (Application Enablement Services) supports connectivity with a maximum of 16 servers. Since AESVCS cannot tell which server is active in a configuration, it must maintain a constant connection with any server from which it might receive data. An Avaya Server listens for AESVCS after it boots up. The AESVCS application establishes the connection to the server.

  If the adjunct terminates solely on the main server’s PE interface, you do not have to administer the Survivable Processor screen. If AESVCS connects to a Survivable Remote or Survivable Core Server, you must administer the Survivable Processor screen in addition to the IP Services screen.