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 new System Platform installations (not an upgrade procedure), you must install the Services Virtual Machine as part of the platform installation process. An exception to this requirement occurs when implementing a centralized SAL system, with the SAL Gateway running on a separate, dedicated server elsewhere in your network. In this case, you disable Services Virtual Machine installation during System Platform installation.
Important When the Services VM Network Configuration window appears at the beginning of the System Platform installation for the standby server in a System Platform High Availability configuration, deselect the Enable Services VM checkbox to ensure that you install the Services VM in a disabled state. If a failover occurs later during HA system operation, the failover subsystem activates the Services VM on the former standby (now active) server, propagates the current Services VM configuration to that server, and deactivates the Services VM on the former active (now standby) server.
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/.
Before you begin
You are performing a new installation of the System Platform.
You have just completed the task, Configuring network settings for Console Domain
If you plan to deploy a stand-alone SAL gateway on a server elsewhere in your network, you must download, install, and configure the SAL 2.1 software on that server. For instructions, see the SAL gateway installation section of Avaya Secure Access Link 2.1 Gateway Implementation, available at the Avaya Support website http://support.avaya.com/.
About this task
Use this procedure to install the Services VM in an enabled or disabled state, when the Services VM Network Configuration window appears during System Platform installation .
Procedure
- If you have a separate server dedicated for centralized SAL support, uncheck the Enable Services VM option in the Services VM Network Configuration window and click OK. Otherwise, leave the Enable services VM option enabled and begin with step 2.
If you disabled the Enable Services VM option, System Platform installation automatically resumes with Configuring the time zone for the System Platform server.
- In the Services VM Network Configuration window, enter a Hostname for the Services Virtual Machine.
- Enter a Static IP address for the Services Virtual Machine.
The IP address must be on the same subnet assigned to the Domain 0 (dom0) and Console Domain (cdom) virtual machines.
- Click OK.
System Platform installation proceeds to Configuring the time zone for the System Platform server.