Testing LSP failover

Last Updated : Dec 22, 2022 |

About this task

If you have an S8300 Server installed and configured as an LSP in the Branch Gateway, you need to perform a test to make sure that the LSP takes over control of the Branch Gateway if the Branch Gateway becomes disconnected from the primary MGCs (Media Gateway Controller).

Note:

If SLS mode is enabled and the primary controller and LSP fail, then the Branch Gateway enters SLS mode.

For more information about testing LSP failover, see Auto Fallback for H.248 Gateways in Administering Network Connectivity on Avaya Aura® Communication Manager and the Migrate H.248 MG to primary" screen command in Avaya Aura® Communication Manager Screen Reference.

Procedure

  1. Verify that valid translation are file synchronized to the LSP by logging into Avaya Aura® Communication Manager from the LSP and listing either stations or trunks, see Administering Avaya Aura®Communication Manager, 03-300509.

    Verify that the list of stations or trunks is valid. If the files are not synchronized, verify that you have correctly configured the required IP addresses for the primary controllers) (MGC). If you are using Avaya IW to configure Branch Gateway, the following are the key actions that must be done in the wizard to ensure correct IP address configuration:

    1. On the Usage options screen, install an LSP that is associated with an S8300 server Primary Controller.

      After you select the usage option, the Primary Controller IP Address screen appears and calls for the required addresses for your primary controller type. Configure the following IP address for each primary controller type:

      Primary media gateway controller

      Number of IP addresses to be configured

      IP addresses to configure

      S8300 server

      1

      The IP address of the primary S8300 server
    2. On the Primary Controller IP Address screen, enter all the required IP addresses for the primary controller type.

      There may be a delay after running Avaya IW until the LSP is registered with the primary MGC and the translations are file synchronized.

    You must add the LSP server correctly to the Main Communication Manager server.

  2. If valid translations are not file synchronized to the LSP, do the following:
    1. From a SAT session running on the primary controller, verify that the LSP node-name and IP address are correctly entered.
    2. Use the save translation lsp command to start the file synchronization process.
    3. Log in again to Avaya Aura® Communication Manager from the LSP and list either stations or trunks.
    4. Verify that the list of stations or trunks is valid.
  3. Disconnect Branch Gateway from the primary controller, ensuring that all telephones are still connected or have network connectivity to the Branch Gateway.
  4. Verify that you can make calls between local telephones using the outside lines connected locally to the Branch Gateway.