SAL Gateway

Avaya service technicians and Avaya Partners can use Secure Access Link (SAL) to gain access to the following remote access and alarming features:

Remote access to support personnel 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.

SAL Gateway is embedded in System Platform, but the software is also available separately for standalone deployments.

Remote accessibility and alarming

System Platform uses SAL to manage alarming and remote access. 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 existing Internet connectivity of customer to facilitate remote support. All communication that is outbound from the customer environment uses encapsulated Hypertext Transfer Protocol Secure (HTTPS). For uploading from the customer site to an Avaya or Avaya Partner site, SAL requires a bandwidth of at least 90 KBps with latency not greater than 150 ms (round trip). Avaya Partners without a SAL Core Concentrator Server must provide their own IP-based connectivity to deliver remote services. For example, B2B VPN connection.

Note

Avaya Partners and customers must configure and register SAL before installing Messaging. An improperly implemented or a nonfunctional SAL delays or prevents Avaya support. System Platform and SAL do not support modem connections.

Standalone SAL Gateway

For a large network with many Avaya devices, you might select a standalone SAL Gateway instead of the SAL Gateway that is embedded in System Platform. You might prefer a standalone gateway if you have a large network with many Avaya devices. With a standalone gateway, you can consolidate alarms from many Avaya devices and send those alarms from one SAL Gateway rather than from multiple SAL Gateways. For more information about a standalone SAL Gateway, see Secure Access Link on http://support.avaya.com.

If you use a standalone SAL Gateway, you must add standalone SAL Gateway 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 embedded SAL Gateway 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, such as System Domain (dom 0), Console Domain (cdom), and Messaging.