Cdom and SAL Gateway IP address assignments

Note

This prerequisite for reassigning IP addresses to the Cdom virtual machine and embedded SAL Gateway do not apply to Avaya Aura solutions that have already deployed a remote stand-alone SAL Gateway server. In this case, IP addresses assigned to your system should remain unchanged, as you will not enable the Services Virtual Machine during the platform upgrade process. During an upgrade, the System Platform installation software verifies if your system already uses the local SAL Gateway. If the system is not using the local SAL Gateway, the System Platform installation program automatically installs the Services Virtual Machine in a disabled state, which also disables its embedded SAL Gateway.

Either procedure requires you to assign a new IP address to the Cdom virtual machine, and then assign the former Cdom IP address to the SAL Gateway. The Avaya customer must provide any site-specific IP address assignments.

With System Platform versions 6.2 and later, a new Services Virtual Machine hosts the SAL Gateway unless you have already deployed a remote SAL Gateway server. By assigning the previous Cdom IP address to the embedded SAL Gateway, and a new IP address to the Cdom Virtual Machine, you will not have to redefine alarm destinations for template applications running on the same server. This is possible because the IP address of the SAL Gateway remains unchanged throughout the upgrade process. Completing this process also helps to ensure that the SAL Gateway remains in communication with Avaya (or an Avaya Partner) during the upgrade event.

The following two tables illustrate an example of Dom0, Cdom, and embedded SAL Gateway address assignments before and after completing this System Platform upgrade prerequisite: