Configuring LSP Survivable Processor on main Communication Manager

Last Updated : Nov 21, 2023 |
Prolog information
Metadata
Keywords:
Configure the main Communication Manager to accept WebSocket connections from Local Survivable Processor (LSP) in Edge mode that matches the configured Serial Number.
When an Edge mode LSP is configured, the main Communication Manager listens to Edge LSP connections on TCP port 2940. You need to configure a reverse proxy to forward LSP connection to the Communication Manager procr interface TCP port 2940.
Configuring an LSP as Edge mode provides a local IP address to forward connections to or from this LSP server.
The available connections using the LSP local address are the following:
  • HTTPS to the LSP SMI
  • SSH to the LSP Linux shell
  • SNMP set/get on the LSP
  • SNMP traps from the LSP
  • Syslogs from the LSP
Note:
If you configure a local loopback address for the LSP (127.0.x.y), you can connect to the LSP only from the main Communication Manager.
If a loopback address is used for the LSP, then SNMP traps and Syslog events will be forwarded using the main Communication Manager IP address.
Here, you can create an SSH tunnel from your PC to the main Communication Manager LSP loopback address and port 10443, using a client as putty, to tunnel the HTTPS connection to the LSP by connecting to localhost on your PC.
SSH and HTTPS connections from the LSP to the main Communication Manager are impossible, and possible only from the main Communication Manager to LSP.
An LSP administrator can disable or re-enable remote SSH and HTTPS connections through the tunnel using the awtun_config Linux shell command:
  • awtun_config disable/enable ssh
  • awtun_config disable/enable https
  1. Start a SAT session on main Communication Manager.
  2. Type change node-names ip name to change the node-name to name or add name as a node.
  3. Press Enter.
  4. The SAT displays the IP NODE NAMES screen.
  5. In the Name field, type in the node name for identifying the LSP node.
  6. In the IP address field, type in the IP address of any available data center address in the same subnet as the Communication Manager procr interface or any local loopback address (127.x.y.z).
    ADDITIONAL INFORMATION:
    Note:
    The main Communication Manager is configured to forward connections between this address and the LSP and can be considered a virtual LSP IP address.
    Local addresses in the same subnet as the procr are supported in Cloud environments only for simplex Communication Manager configurations.
    If you assign an IPv6 address to the LSP, the address will be configured on the main Communication Manager loopback interface and it cannot support TCP syslog or SMNP informs.
  7. Press Enter to submit the command.
  8. Type add survivable-processor name to add the survivable-processor with node-name name. The main Communication Manager console displays the SURVIVABLE PROCESSOR screen.
    ADDITIONAL INFORMATION:
    You can use change survivable-processor name to modify the configuration.
  9. In the Topology field, type edge to add Edge topology.
  10. Enter the LSP ID/MID and Server ID values.
  11. In the Serial Number field, enter the serial number of the Communication Manager LSP from the SMI Server Role page.
  12. Press Enter to submit the command.