Beginning with System Platform release 6.2, the Secure Access Link Gateway (SAL gateway) no longer runs on the System Platform Console Domain (cdom) virtual machine. Instead, SAL 2.1 runs on an independent Services Virtual Machine (services_vm domain) on your Avaya Aura® solution server. As with the prior implementation of the SAL gateway running on the cdom virtual machine, this new configuration supports secure remote access to local server resources, and forwards alarms (SNMP traps) from your local solution server to a remote Network Management System (NMS).
As of System Platform release 6.2, releases of the Services Virtual Machine are independent of System Platform releases, so your system may use the existing Services VM 1.0, or you can subsequently upgrade your system to use Services VM 1.1 (or later). When you upgrade the Services VM, the process preserves the prior Master Agent configuration. For information about how to upgrade the Services VM, see Implementing and Administering Services-VM on Avaya Aura® System Platform, available from Avaya Support ( http://support.avaya.com ). After the upgrade, you configure the Net-SNMP Master Agent in Services VM 1.1 (or later) to forward either SNMPv2c or SNMPv3 traps to your NMS.
For platform upgrades (not a new System Platform installation), the platform upgrade process manages installation of the new Services VM and SAL gateway transparently except where an administrator must enter configuration values.
For more information about SAL capabilities, see Secure Access Link 2.1 SAL Gateway Implementation, at http://support.avaya.com/.