Configuring the Survivable Remote Server linked to the Branch Session Manager

Last Updated : Nov 28, 2023 |

About this task

After you add a Branch Session Manager (BSM) instance, you must configure the Communication Manager Survivable Remote Server (SRS), formerly known as Local Survivable Processor (LSP), that is linked to the BSM when deploying the BSM.

Before you begin

  • Ensure that the date and time set on the main Communication Manager server and the SRS server is the same.

Procedure

  1. On the main Communication Manager server, open a SAT session.

    Ensure that the Communication Manager is the main Communication Manager of the SRS that is linked to the BSM.

  2. On the command terminal, do the following:
    1. Run the following command:

      change node-names ip

    2. On the IP Node Names page, add the asset IP address of the BSM server and type a node name for the IP address.
    3. On the next line, add the IP address of the SRS server and type a node name for the IP address.
  3. On the command terminal, do the following:
    1. Run the following command:

      change survivable-processor <name of the SRS linked to the BSM>

    2. In Cluster ID/MID, type the cluster ID or module ID of the main Communication Manager server.
    3. In Server ID, type the server ID of the main Communication Manager server.
    4. In Processor Ethernet Network Region, type the network region of the main Communication Manager server.
    5. In Topology, type the name of the BSM topology, that is, enterprise or edge.
  4. If you are using an Avaya Aura® Media Server, do the following on the next page:
    1. In Priority with respect to Media Servers, specify a priority for the SRS server with respect to the media server.
    2. On the next page, type the name of the media server you want to use for the SRS.
  5. To add the SRS server to the list of backup servers, do the following:
    1. On the command terminal, run the following command:

      change ip-network-region <network region number of the main Communication Manager server>

    2. On the IP network region page, add the SRS to the list of backup servers.
  6. On the SRS server, log in to the Communication Manager System Management Interface (SMI) using the init login credentials.
  7. On the Administration menu, click Server (Maintenance).
  8. In the navigation pane, click Server Configuration > Server Role.
  9. On the Server Role page, do the following:
    1. In This Server is area, select a local survivable server (LSP).
    2. In the SID field, type the system ID of the main Communication Manager server.
    3. In the MID field, type the cluster ID or module ID of the main Communication Manager server.
    4. In LSP Topology, select the topology, that is, Enterprise or Edge.
    5. Ensure that the Registration address at the main server (C-LAN or PE address) and File Synchronization address at the main cluster (PE address) fields contain the IP address of the main Communication Manager server.
    6. In Configure Memory, select a memory profile for the SRS and main Communication Manager.
    7. If you are using an Avaya G4xx media gateway instead of a media server, in the Media Gateway Serial Number field, type the serial number of the media gateway.
    8. In the BSM SIP Entity IP Address (IPv4 or IPv6) field, type the asset IP address of the BSM server.
  10. In the navigation pane, click Server Configuration > Network Configuration.
  11. On the Network Configuration page, ensure that the Server ID field contains the cluster ID or module ID of the main Communication Manager server.
  12. Click Change, and then click Restart CM.
Related information
Adding a Branch Session Manager instance