.dm_vars file parameters

Last Updated : Feb 11, 2022 |

The .dm_vars file is a backup file of the variables specified in the all file. The following table lists the deployment environment parameters to specify in the .dm_var file:

Parameter

Description

MCS ENVIRONMENT VARIABLES

MCS_VIRTUAL_IP

To specify the virtual IP address of the Configuration Server. In the Simplex and local HA deployments, you must specify the static IP address of the Configuration Server.

ha_type

To specify the deployment environment of your contact center. You can type cold-dr for GEO-HA layer3 deployment.

MCS_IPS

To specify IP addresses of all Configuration Server instances in your contact center deployment. You must use a space to separate the IP addresses.

AES_LOGIN_URL

To specify the URL of the AE Services management console login page in the following format:

https://<AES server IP address>/aesvcs/login.xhtml, where <AES server IP address> is the virtual or static IP address of the AE Services server.

For example, https://10.1.2.12/aesvcs/login.xhtml.

NGINX ENVIRONMENT VARIABLES

MCS_CERT_FQDN

To specify the FQDN of the Configuration Server. In the geo-redundant HA deployment, you must specify the FQDN of the Configuration Server that hosts the virtual IP address.

The MCS_CERT_FQDN must match the mcsfqdn value in the systemconfig file.

MBX_CERT_FQDN

To specify the FQDN of the Routing Core Server. In the local HA and geo-redundant HA deployments, you must specify the FQDN of the Routing Core Server that hosts the virtual IP address.

The MBX_CERT_FQDN must match the mbx1fqdn value in the systemconfig file.

MBX ENVIRONMENT VARIABLES

VIRTUAL_IP

To specify the virtual IP address of the Routing Core Server in the local HA and geo-redundant HA deployments. In the Simplex deployment, you must specify the static IP address of the Routing Core Server.

TENANT

To specify the tenant name. You can type only letters.

AF_SHM_LICENSE_KEY

To provide the license key for the Avaya Contact Center – Extended Capacity solution. You must obtain the license key from the Avaya support personnel.

MBX_MEGA_INTERFACE

To provide the name of the Routing Core Server interface. For example, ens160.

For the local HA and geo-redundant HA deployments, you must add :1 to the MBX_MEGA_INTERFACE value. For example, ens160:1.

MCS_MEGA_INTERFACE

To provide the name of the Configuration Server interface. For example, ens161.

AES_PARENT_INTERFACE

To provide the name of the Routing Core Server interface. For example, ens160.

AES_GATEWAY

To specify the AE Services gateway IP address. The AES_GATEWAY value must correspond to the aes_subnet value in the mega-config.yml file. For example, 10.1.2.1.

PPM_DOMAIN

To specify the FQDN of your network. For example, avaya.com.

SHM_HA_BUFFER_SIZE_IN_MB

To specify the shared memory buffer size in megabytes. The SHM_HA_BUFFER_SIZE_IN_MB value depends on the number of logged-in agents and simultaneous calls during the failover.

To support the capacity of 30,000 simultaneously logged-in agents and 30,000 calls during the failover, set the SHM_HA_BUFFER_SIZE_IN_MB parameter to 400.

DUMP_CORE

To disable core dumps, set the DUMP_CORE value to false.

ULIMIT_VALUE

To specify the memory space to allocate for core dumps. If you disable core dumps, set the ULIMIT_VALUE value to 0.

MINIO_IPS

To specify IP addresses of all Routing Core Servers in your contact center deployment. You must use a space to separate the IP addresses.