Setting up the PE interface

Last Updated : Nov 02, 2020 |

About this task

This section contains general and high-level steps for configuring and administering the PE interface. As each system has unique configuration requirements, refer to the Avaya Support website at http://support.avaya.com for more details.

Procedure

  1. Load the appropriate template.
  2. Configure the PE interface on the server using the server System Management Interface (SMI).

    See Configuring the PE interface on the server using the server SMI.

  3. On the IP Node Names screen on the Communication Manager System Access Terminal (SAT), enter the name for each survivable core server, survivable remote server, and adjunct.

    The SAT command is change node-name. You do not have to add the PE interface (procr) to the IP Node Names screen. Communication Manager adds the PE interface automatically. For information about this screen, see Avaya Aura® Communication Manager Screen Reference.

  4. For a single main server, use the IP Interfaces screen to enable branch gateway registration, H.323 endpoint registration, gatekeeper priority, network regions, and target socket load.

    On some platform types, the IP Interfaces screen is already configured.

    Use the SAT command display ip-interfce procr to see if the PE interface is already configured. If it is not, use the SAT command add ip-interface procr to add the PE interface.

  5. Use the Processor Channel Assignment screen (command change communication-interface processor-channels) and the IP Services screen (change ip-sevices) to administer the adjuncts that use the PE interface on the main server:
    • Enter p in the Interface Link field on the Processor Channel Assignment screen.

    • Enter procr in the Local Node field on the IP Services screen.

  6. For adjunct connectivity to a survivable core server or survivable remote server, use the Survivable Processor - Processor Channels screen to:
    • Use the same processor channels information as the main server by entering i(nherit) in the Enable field.

    • Use different translations than that of the main server by entering o(verwrite) in the Enable field. After entering o(verwrite), you can enter information specific to the survivable core server or survivable remote server in the remaining fields.

    • Disable the processor channel on the survivable core server or survivable remote server by entering n(o) in the Enable field.

  7. Execute a save translations all, save translations ess, or save translations lsp command to send (file sync) the translations from the main server to the survivable core server or survivable remote server.