SAL Gateway

Secure Access Link (SAL) provides the remote access and alarming features to Avaya service technicians and Avaya Partners. SAL provides:

Remote access to support personnel for accessing supported devices.
A user interface to configure managed devices, Concentrator Remote and Core Servers, and other settings.
Redundancy in gateways for enhanced service availability.
Diagnostic facilities that ensure that all gateway components operate as required.

System Platform includes an embedded SAL Gateway. SAL Gateway software is also available separately for stand-alone deployments.

Remote accessibility and alarming

System Platform uses SAL to manage alarming and remote access. The SAL provides network based remote access to Avaya Services, potentially eliminating the need for a service technician to visit the customer site. System Platform uses the customer’s existing Internet connectivity to facilitate remote support. All communication is outbound from the customer’s environment using encapsulated Hypertext Transfer Protocol Secure (HTTPS). SAL requires upload bandwidth (customer to Avaya or Avaya Partner) of at least 90 KB/s with latency no greater than 150 ms (round trip). Avaya Partners without a SAL Core Concentrator Server must provide their own IP-based connectivity (for example, B2B VPN connection) to deliver remote services.

Note

Avaya Partners and customers must configure and register SAL before installing Messaging. Avaya support will be delayed or not possible if SAL is improperly implemented or not operational. System Platform and SAL do not support modem connections.

Stand-alone SAL Gateway

You can choose to use a stand-alone SAL Gateway instead of the SAL Gateway that is embedded in System Platform. You might prefer a stand-alone gateway if you have a large network with many Avaya devices. The stand-alone gateway makes it possible to consolidate alarms from many Avaya devices and send those alarms from one SAL Gateway rather than multiple SAL Gateways sending alarms. See Secure Access Link on http://www.avaya.com/support for more information on stand-alone SAL Gateway.

If you use a stand-alone SAL Gateway, you must add it as an SNMP trap receiver for System Platform. See Adding an SNMP trap receiver. You can also disable the SAL Gateway that is embedded in System Platform so that it does not send duplicate heart beat messages to Avaya. See Disabling SAL Gateway.

SAL Gateway configuration

The SAL Gateway includes a Web-based user interface that provides status information, logging information, and configuration interfaces. You must configure the SAL Gateway and other devices for alarming and remote access. The devices include System Domain (dom 0), Console Domain (cdom), and Messaging. To configure SAL, perform the following steps:

Register the system: Register the system to obtain the information that you must later enter through the SAL administrative interface. To provide service and support to registered customers, Avaya assigns a Solution Element ID (SE ID) and Product ID to each SAL Gateway that you register. This data is critical for the correct execution of various Avaya business functions and tools. For more information, see Registering the system.

Note
Submit the registration form three weeks before the planned installation date.
Configure the SAL Gateway: The SAL Gateway provides remote access to those devices that are configured for remote access within it. The SAL Gateway controls connections to managed elements and new or updated models and also authenticates certificates. For more information, see Adding managed devices to the SAL Gateway.
Submit the registration form: Complete and submit the Universal Install Product Registration Request Form after the installation is complete. For more information, see Submitting the registration form.