PE in Communication Manager Administration

Last Updated : Oct 07, 2026 |
Prolog information
Metadata
Keywords:
Processor Ethernet administration is always performed on the main server. The Survivable Remote or Survivable Core Server receives the translations from the main server during registration or when you perform a save translations lsp, save translations ess, or save translations all command on the SAT of the main server.
When communication with the main server is lost, you can perform administration on an active Survivable Remote Server or an active Survivable Core Server. In this case, the administration is temporary until the communication to the main server is restored. At that time, the Survivable Remote or Survivable Core Server registers with the main server and receives the file sync. The file sync will overwrite any existing translations.
This section outlines the screens used in the administration of Processor Ethernet. For more information on these screens, see Avaya Aura® Communication Manager Screen Reference.
  • IP Node Names screen
    If the PE interface is enabled in the license file, the system displays the PE interface (procr) automatically on the IP Node Names screen. You cannot add the PE interface to the IP Node Names screen.
  • IP Interfaces screen
    Administer the PE interface on the IP Interfaces screen. It is possible to have the PE interface administered on the same system. On some server types, the PE interface is automatically added. To see if the PE interface is already added to your system, use the command display ip-interface procr. To add the PE interface, use the command add ip-interface procr.
    Administer the PE interface on the main server if the main server is Avaya Solutions Platform S8300 and for one or more of the following entities, use the PE interface of the main server to register with the main server:
    • AE Services, CMS, CDR adjuncts
    • Branch gateways
    • H.323 gateways or endpoints.
      For configurations that do not use the PE interface on the main server, do not administer the IP Interfaces screen. This is true even if the Survivable Core or Survivable Remote Server is using the PE interface. The IP Interfaces screen is automatically populated for a Survivable Core or Survivable Remote Server.
  • Survivable Processor screen
    The Survivable Processor screen is used to add a new Survivable Remote Server and also provides a means to connect one of the three supported adjuncts (CMS, CDR, AESVCS) to a Survivable Remote or Survivable Core Server. The Survivable Processor screen is administered on the main server. The translations are sent to the Survivable Core or Survivable Remote Server during a file sync.
Related links
Administering Survivable Core Servers for PEAdministering Survivable Remote Servers for PEAdjuncts with PE