0% found this document useful (0 votes)

39 views162 pages

Aura Lab Creation

The document outlines the steps for creating AURA and AADA labs, including the deployment and configuration of System Manager (SMGR), Session Manager (SM), and Communication Manager (CM) using both vCenter Server and ESXi hosts. It details the installation of patches, setting up passwords, configuring trunks, SIP routing, and synchronization between the components. Additionally, it includes instructions for managing clusters, load balancers, and endpoints within the lab environment.

Uploaded by

patilau

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

39 views162 pages

Aura Lab Creation

Uploaded by

patilau

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 162

AURA & AADA Lab Creation

1. SMGR Deployment From ESXI Host

2. SMGR Basic Config After Deployment
3. SMGR Deployment From vCenter Server
4. SMGR Patch Installation
5. Set SMGR GUI Password
6. Set SMGR Enrollment password
7. Deploying Session Manager From vCenter Server
8. Deploying Session Manager From ESXI Host
9. SM Basic Config After Deployment
10. Trust and Replication With System Manager
11. Deploying CM Simplex using vCenter server
12. CM Deployment From ESXI Host
13. CM Basic Config After Deployment
14. CM Duplex Configuration
15. Do Null Translations
16. Adding CM 'procr' IP
17. Setting passwords for the CM default users(init and sroot)
18. Setting passwords for the default CM users (sroot and init)
19. SMGR CA Certificate Installation on CM
20. Server/Application Certificate Installation on CM
21. Add Media Server(AMS) to CM
22. Add Media Gateway to CM
23. Add CM in SMGR
24. Configure Trunk in SMGR from SM to CM
25. Configure Trunk in CM from CM to SM
26. SIP Routing Configuration from CM
27. SIP Routing Configuration from SMGR
28. CM Synchronization From SMGR
29. Application Configuration in SMGR
30. Add SIP Stations From SMGR
31. Generate and Install License For SMGR, SM, CM and AMS.
31.1. System Manager, SMGR
31.2. Session Manager, SM
31.3. Communication Manager, CM
31.4. Media Server, AMS
32. Endpoints Configuration
32.1. EmulatorSIP and 96x1 SIP Real Phone
32.2. J179Emulator
33. Add H323 Stations
34. Add Cluster CM in SMGR
35. Administering LHNR in SMGR
36. Administering Cluster CM in SIP Entities Page
37. Creating Cluster in SMGR
38. Enable Load Balancer in SMGR
39. Administering Load Balancer in SMGR
40. Configuring Trunks From Cluster CM to SM
41. Configuring Route Pattern In Cluster Options Page
42. Configuring Homing Policy in CM
43. Install CSP CA Cert on Cluster CM
44. Install SMGR CA on CSP
45. Install ADC Cert on Cluster CM
46. Setting up proper Weblm Server IP for Cluster CM
47. Enable Clustering Feature from CM SMI Page
48. Configure CM Cluster on CM
49. Check Master CM is recognized in SMGR
50. Install CCM and CSP
51. Survivable ESS Configuration
51.1.1. Duplex ESS Configuration
51.1.2. Simplex ESS Configuration
52. Take CM Full Backup
53. Restore CM Full Backup
54. CM Software Only Installation
55. How to Administer H323 and SIP Stations using script
56. SMGR Software Only Installation
57. SMGR Patch Installation
58. SMGR GEO Configuration
59. SMGR Upgrade
60. How To Upgrade Media Gateway (G450/G430) Firmware
61. Survivable LSP Configuration
»»» AURA Lab Creation Steps

1. SMGR Deployment From vCenter Server

»»» AADA Lab Creation Steps ==> New

1. SMGR Deployment From vCenter Server

2. SMGR Patch Installation
3. Set SMGR GUI Password
4. Set SMGR Enrollment password
5. SM Deployment From vCenter Server
6. Trust and Replication With System Manager
7. Generate and Install License For SMGR, SM, Cluster CM and AMS
System Manager, SMGR
Session Manager, SM
Communication Manager, Cluster CM
Centralized License
Media Server, AMS
CSP in-progress
8. Install CCM and CSP
9. Add Cluster CM in SMGR
10. Creating Cluster in SMGR
11. CM Deployment From vCenter Server
Note: 1. Deploy all CMs that you require in Cluster Environment
2. However, power ON only one CM.
12. Setting passwords for the CM default users(init and sroot) (Not included in Doc. Check with Sambhaji)
13. Adding CM procr IP
14. SMGR CA Certificate Installation on CM
15. Server/Application Certificate Installation on CM
16. Install CSP CA Cert on Cluster CM
17. Install SMGR CA on CSP
18. Enable Clustering Feature from CM SMI Page
19. Configure CM Cluster on CM
20. Add Cluster CM in SMGR
21. Creating Cluster in SMGR
22. Check Master CM is recognized in SMGR
23. Adding CM procr IP
24. Configuring Route Pattern In Cluster Options Page
25. Administering LHNR in SMGR
26. Enable Load Balancer in SMGR
27. Administering Load Balancer in SMGR
28. Administering Cluster CM in SIP Entities Page
29. Application Configuration in SMGR
30. Configure Trunk in SMGR from SM to Cluster CM
31. SIP Routing Configuration from SMGR
32.
32. Add Media Server(AMS) to CM
33. Configuring Trunks From Cluster CM to SM
34. SIP Routing Configuration from CM
35. Configuring Homing Policy in CM
36. Add SIP Stations From SMGR
37. CM Synchronization From SMGR
38. Power ON remaining CMs one by one and perform below tasks.
Note: Before you begin this make sure the previously running CM (First powered ON CM) must be running with CMRole as ‘Master CM’
Setting passwords for the CM default users(init and sroot)
SMGR CA Certificate Installation on CM
Server/Application Certificate Installation on CM
Install CSP CA Cert on Cluster CM
Install SMGR CA on CSP
Configure CM Cluster on CM
Check Node CMs getting translations from Master CM in-progress

1. SMGR Deployment From ESXI Host

1. Login to ESXI from browser.
2. Click on Virtual Machines and later click on Create / Register VM.
3. Select Deploy a virtual machine from an OVF or OVA file.

4. Provide VM Name and browse the OVA file from local and click next.

5. Select proper datastore and click next.

6. Accept License agreements and click Next.

7. Select the Deployment Options, click next and Finish.

2. SMGR Basic Config After Deployment

1. Login to ESXI Host and Power ON the SMGR VM.
2. Select SMGR VM and open its browser Console.
3. For SMGR make sure you have proper CPU and MEMORY reservations as per profile and provide user input configuration.
Note: Schedule SMGR backup and Data Encryption is user depends.
4. Login to SMGR from putty and change the password after first login.

5. Let the SMGR Maintenance operation complete and install the SMGR Mandatory Patch.
To check this Maintenance Operation login to SMGR from putty again.

3. SMGR Deployment From vCenter Server

1. Login to vCenter Server.
2. Right click on Resource pool and select Deploy OVF Template.
3. Do one of the following and click on NEXT.
Select URL option and provide the SMGR OVA path
Select Local file and browse the SMGR OVA from the local machine
4. Provide the Name for the Virtual Machine.

5. Resource Pool is selected by default, if not select the proper resource pool and click NEXT.

6. If you see ignore on top right corner click ignore and click next otherwise click next.

7. Accept License agreements and click on next.

8. Select virtual disk format as any thick provision and select any datastore and click next.

9. Select networks and click on next.

10. Fill the following mandatory fields and click on next

Below two values are recommended to enter/select

On your first CLI login, SMGR prompts to change the CLI Password.

If you want to Schedule SMGR backup, Select the required details.

Select '1' to enable EASG and '2' to disable EASG

If you want to encrypts the data select '1' else select '2' and click next.
If you select '1' system prompts to enter passwords e
Verify that you have entered the correct details and click on FINISH

11. Wait for sometime to complete the inistallation.

12. Power On the VM.

4. SMGR Patch Installation

1. Login to SMGR from putty.
You will be prompted to change the password on the first login.

2. Change the password.

Let the SMGR Maintenance operation complete.
3. Optionally, To check this Maintenance Operation, take a duplicate session using Putty, and login to SMGR using the latest password.
Once the system prompts as shown in below screenshot then install Mandatory Patch.

4. Copy SMGR Patch into /swlibrary/ directory.

For example, if you are using Filezilla application, open Filezilla and login using the Host name (IP address of SMGR), CLI username and
password, and Port (22).

5. Go to putty, and install the SMGR patch using the following command
# SMGRPatchdeploy /swlibrary/<SMGR Bin Patch>
For example, run the following command: SMGRPatchdeploy /swlibrary/System_Manager_R8.1.0.0_S7_810009814.bin

6. Enter/Press Y to proceed with the installation.

7. Enter Y to accept the license.y
Wait for the patch installation to be completed, It will take approximately 45 minutes.

Next Steps:
a. Login to SMGR GUI using SMGR's default credentials: admin/admin123

b. You must change your SMGR GUI password on your first login.

5. Set SMGR GUI Password

1. Login to SMGR GUI using default credentials(admin/admin123).
System prompts you to chage the admin password.
2. Click Change Password.

3. Reset the password, and click Enter.

The password must be highly complex.

4. Login to SMGR GUI using new password.

6. Set SMGR Enrollment password

Note: While deploying Session Manager, you will be prompted to enter the SMGR Enrollment password for initializing the Trust with
SMGR, You can set this password anytime. It is recommended to set enrollment password soon after deploying SMGR, so that you can
use this password at the time of deploying Session Manager.
1. Login to SMGR GUI and set the Enrollment password.
To add go to Services »» Security »» Certificates »» Enrollment Password

7. Deploying Session Manager From vCenter Server

4. Provide the Name for the Virtual Machine.

5. Resource Pool is selected by default, if not select the proper resource pool and click NEXT.

6. If you see ignore on top right corner click ignore and click next otherwise click next.

7. Accept License agreements and click on next.

8. Select the required profile.

9. Select virtual disk format as "Thin Provision" and select any datastore and click Next.
For SM deployment, both Thin or Think provision will work. To save the disk space, select Think provision.
10. Select networks and click on next.

11. Fill the following mandatory fields and click on next

Below two values are recommended to enter/select

The Trust Management Enrollment Password is used, to create a Trust between SM with SMGR. Keep a note of the password.

Enter the password for the default "cust" user. You can change the user name if you want.

If you want to encrypt the data select '1' else select '2' and click next.
If you select '1' system prompts to enter passwords e

Select '1' to enable EASG and '2' to disable EASG

Verify that you have entered the correct details and click FINISH.
12. Wait for sometime to complete the inistallation.
13. Power On the VM.

8. Deploying Session Manager From ESXI Host

1. Login to ESXI from browser.
2. Click On Virtual Machines and later click on Create / Register VM.
3. Select Deploy a virtual machine from an OVF or OVA file.

4. Provide VM Name and browse the OVA file from local and click next.

5. Select proper datastore and click next.

6. Accept License agreements and click Next.

7. Select the Deployment Options, click next and Finish.

Note: SM Profile is based on user requirement.

9. SM Basic Config After Deployment

1. Login to ESXI Host and Power ON the SM VM.
Note: Make sure before power ON, set the Hard Disk size based on the SM Version and Profile, check this in below link.
https://confluence.forge.avaya.com/display/ASM/SM+Profiles#SMProfiles-EncryptedCoreSessionManager(8.1EOVA)

2. Select SM VM and open its browser Console.

3. Provide User Configuration.

10. Trust and Replication With System Manager
We must create a trust between SMGR and SM to sync the data properly.

1. Login to SMGR and SM from putty.

SM and SMGR should run on same date and time.
2. To check if SMGR and SM are running on the same date and time or not, run the following command on both SMGR and SM: "date"
Check the date and time displayed on the below CLIs.
In this example, the date on SMGR (left image) and SM (right image) is matching.

3. If the date and time on SM is not matchign with SMGR, then set the date and time in SM.
In SM CLI, run the below command to change the date in SM with root user
# date -s "<Copy SMGR date and paste it in SM CLI>"
For example, date -s "Thu Feb 10 06:17:50 IST 2022"
4. Put SMs FQDN in SMGR.

Note: Make sure SMGR FQDN must existing in SM /etc/hosts file and SM FQDN must existing in SMGR /etc/hosts file

5. Login to SMGR GUI and add Locations and Domains. To add Domains go to Elements »» Routing »» Domains

To add Locations go to Elements »» Routing »» Locations

6. Login to SMGR GUI and add SM in SIP Entities. To add go to Elements »» Routing »» SIP Entities.
Note: SM should have 2 IPs, one is for Management IP (At the deployment time we given this IP) and one for Asset IP which we give while
adding SM in SIP Entities.
In this below screenshot, we should add Asset IP (New IP) for SM.
7. Now add SM in Inventory. To add go to Services »» Inventory »» Manage Elements.
Note: While adding SM in Inventory Use Management IP (which we already provided at the deployment time.)
8. Check the SM current ‘Service State’. To check go to Elements »» Session Manage »» Dashboard.

SM is in No connection state which means Trust and Replication with SMGR is not done.

9. Set the Enrollment Password on SMGR, To set Go To Services »» Security »» Certificates »» Enrollment Password

10. Login to SM using putty, and execute the following command to start Trust and Replication with SMGR

## initTM

We must see this after successful Trust and Replication

11. To check the Replication, go to Services »» Replication

System may take some time to show the updated status.
11.

If SM is in Maintenance Mode or in Deny state, then the SM services will not work. For example, you can register the phone.
If SM running on ‘Maintenance Mode’, You must change the SM Service State to ‘Accept New Service’ mode.

12. Go To Elements »» Session Manage »» Dashboard, Select the Session Manager entry (check box), and from the "Service State" drop-down,
select Accept New Service.
.

13. Click Confirm.

14. Check whether SM is having both Management and Asset IP.

Login to SM from putty.
11. Deploying CM Simplex using vCenter server
1. Login to vCenter Server.
2. Right-click on Resource pool and select Deploy OVF Template.
3. Do one of the following and click NEXT.

* Select URL option and provide the path of your local server where your CM OVA is available.
* Select Local file and browse the CM OVA from your local machine

4. Provide the Name for the Virtual Machine.

5. Resource Pool is selected by default, if not select the proper resource pool and click NEXT.
6. If you see ignore on top right corner, click Ignore and click NEXT, otherwise click NEXT.

7. Accept License agreements and click NEXT.

8. Select the required configuration (Profiles or user profiles), and click Next.

9. Select virtual disk format as "Thin Provision" and select any datastore and click Next.
For CM deployment, both Thin or Think provision will work. To save the disk space, select Think provision.

10. Select networks and click on next.

11. Fill the mandatory fields and click Next.

Make sure to make a note of the Admin user credentials that you provide. On your first login to CM, you must use the same
11.

credentials.

Select '1' to enable EASG and '2' to disable EASG.

For testing purpose, you can disable EASG. If you enable EASG, you will be prompted to enter Challenge-Response while logging into CM.

If you want to encrypts the data select '1' else select '2' and click next.
If you select '1' system prompts to enter passwords e
12. Verify the details and click FINISH.

Deploying process will take few mnts.

13. Start the CM.

Additional info:
* When CM is deployed using vCenter server, on your first login, you will be forced to change the Admin password
* On successful deployment, CM provides two default users: init, sroot

Next Steps:
login to CM using the "Privileged Administrator User Login" credentials you provided during the depoyment. On your first login, system prompts
you to change the Admin password.
Set password for the two default users: init, sroot

12. CM Deployment From ESXI Host

1. Login to ESXI from browser.

2. Click On Virtual Machines and later click on Create / Register VM.

3. Select Deploy a virtual machine from an OVF or OVA file.

4. Provide VM Name and browse the OVA file from local and click next.

5. Select proper datastore and click next.

6. Accept License agreements and click Next.

7. Select the Deployment Options, click next and Finish.

13. CM Basic Config After Deployment

1. Login to ESXI Host and Power ON the CM VM.

2. Select CM VM and open its browser Console.

3. Login to CM using default credentials and do Network setup.

craft/craft01 »»» For Signed OVA
init/itsgrand3 »»» For Development OVA
3.

4. Login to CM and reboot it or restart the VM.

14. CM Duplex Configuration

Note: For Duplex Configuration you must need two different networks, one is for eth0 and other is one is for eth1
eth0 is CM Physical IP
eth1 is Duplication IP

1. Deploy Duplex CMs and power ON.

2. Set the hostname for both Duplex CMs from SMI page.
Go to Administration »» Server Configuration »» Network Configuration
Update Host Name and click on change

3. Install SMGR CA Certificate and Server/Application Certificate on both Duplex CMs. Follow below links.
Note: Before install Certs, ensure that SMGR and LSP must be running on same date and time.
SMGRCACertificateInstallationonCM
Server/ApplicationCertificateInstallationonCM

4. Set the hostname and server ID for both the CMs from SMI Page.
Go to Administration »» Server Configuration »» Network Configuration
Update Host Name, Server ID and click on change

Duplex CM1
Duplex CM2

5. Configure Alias and Duplication IP for both Duplex CMs in Network Configuration Page.
Go to Administration »» Server Configuration »» Network Configuration
Note: The Alias IP must be same for both CMs

Duplex CM1

Duplex CM2
6. Update parameters in Duplication Parameters page.
Go to Administration »» Server Configuration »» Duplication Parameters
Provide Duplex CM2 details in Duplex CM1 and
Provide Duplex CM1 details in Duplex CM2

Duplex CM1

Duplex CM2
7. Restart both CMs using reboot command
# reboot

8. By default Duplex CMs starts with BUSY OUT mode. To check execute below command.
# server

Check Duplication Link, it should be up

Check Mode: BUSY OUT (By default it is BUSY OUT). When its in BUSY OUT mode you should release it by executing below command in both
CMs.
# server -r

After releasing the servers, one Duplex CM will be running in Active Mode and other Duplex CM will be running in Standby Mode. Check below
screenshot.
15. Do Null Translations
16. Adding CM 'procr' IP
1. Login to CM CLI.
2. save translations using cli command 'save_trans' and restart the CommunicaMgr service using using cli command 'drestart 1 4'
3. Go to sat, Add CM procr IP.

17. Setting passwords for the CM default users(init and sroot)

1. Login to CM using the "Privileged Administrator User Login" credentials you provided during the deployment.
On your first login, system prompts you to change the Privileged Admin password (either EASG is enabled or disabled)

Info:
If EASG is enabled during CM deployment, system will ask for Response Code for the default "sroot" and "init" users. "sroot" user is restricted to
CLI only. "init" user can access CLI and SMI pages.
If EASG is disabled during CM deployment, system will directly ask for Password if you login using "sroot" and "init" users. Since, we have NOT
set the passwords, you cannot login at all using these users. In this case, you can login to CM CLI or SMI using the Privileged user "ppminit"
account ONLY (for example, "ppminit" user can only login CLI and SMI)
EASG is used to allow Avaya Support personnel to troubleshoot customer issues.

2. Login as sroot user using the following command: su sroot.

Only the "sroot" user can perform the system level configurations. For example, updating the config files.

Do one of the following:

If Do

Scenario 1: If EASG is enabled, system prompts you to enter the Respone code Generate response code for the sroot user:

for the Challenge. To generate Response code, go to:

http://ssdp.dr.avaya.com/ASG_WebMobile/ind

Enter the required details and click Query.

Copy the Reponse from the ASG Web Mobile res

field of the CLI.

On the CM CLI, you will be at the "sroot" user lev

Scenario 2: If EASG is not enabled, system promts you to enter the password for As a Privileged user, enable EASG:

the "sroot" user. To enable EASG, run the following command:

# sudo /sbin/EASGManage -f --enableEASG
Info: Since we Do Not know the password of sroot at this stage, Restart the CM: # reboot (Masthan, I am at P

you must enable EASG.

You must first enable EASG to set the passwords for the default

users (sroot and init).

Now that the EASG is enabled, Generate respon

To generate Response code, go to:

http://ssdp.dr.avaya.com/ASG_WebMobile/ind

Copy the Reponse from the ASG Web Mobile res

field of the CLI.

On the CM CLI, you will be at the "sroot" user
3. When you are at the "sroot" user level, change "ecs.conf" file.
This is required to
To do so, enter:
# vi /etc/ecs.conf
UseASG disabled
Customer-Root enabled
save the file

After changing ecs.conf file, You will return to the sroot user. At the "sroot" user level, execute the following command:
# setPlatformAttributes

Generate new password for the users init and sroot.

# passwd init (It will ask you the new password for the user init )
# passwd sroot (It will ask you the new password for the user sroot )

Note: By default init and sroot password configured as init/itsgrand3 and sroot/sroot01 for
development ova.

4. Now try login to CM using init User.

18. Setting passwords for the default CM users (sroot and init)
1. Login to CM using the "Privileged Administrator User Login" credentials you provided during the depoyment.
On your first login, system prompts you to change the Privileged Admin password (either EASG is enabled or disabled)

Info:
If EASG is enabled during CM deployment, system will ask for Response Code for the default "sroot" and "init" users. "sroot" user is restricted to
CLI only. "init" user can access CLI and SMI pages.
If EASG is disabled during CM deployment, system will directly ask for Password if you login using "sroot" and "init" users. Since, we have NOT
set the passwords, you cannot login at all. In this case, only Privileged user (for example, "ppminit" user can only login CLI and SMI)
EASG is used to allow Avaya Support personnel to troubleshoot customer issues.

2. Login as sroot user using the following command: su sroot.

Only the "sroot" user can perform the system level configurations. For example, updating the config files.

Do one of the following:

If Do

Scenario 1: If EASG is enabled, system prompts you to enter the Respone code Generate response code for the sroot user:

for the Challenge. To generate Response code, go to:

http://ssdp.dr.avaya.com/ASG_WebMobile/ind

Enter the required details and click Query.

Copy the Reponse from the ASG Web Mobile res

field of the CLI.

On the CM CLI, you will be at the "sroot" user lev

Scenario 2: If EASG is not enabled, system promts you to enter the password for As a Privileged user, enable EASG:

the "sroot" user. To enable EASG, run the following command:

# sudo /sbin/EASGManage -f --enableEASG
Info: Since we Do Not know the password of sroot at this stage, Restart the CM: # reboot (Masthan, I am at P
you must enable EASG.

You must first enable EASG to set the passwords for the default

users (sroot and init).

Now that the EASG is enabled, Generate respon

To generate Response code, go to:

http://ssdp.dr.avaya.com/ASG_WebMobile/ind

Copy the Reponse from the ASG Web Mobile res

field of the CLI.

After changing ecs.conf file, You will return to the sroot user. At the "sroot" user level, execute the following command:
# setPlatformAttributes

Generate new password for the users init and sroot.

# passwd init (It will ask you the new password for the user init )
# passwd sroot (It will ask you the new password for the user sroot )

Note: By default init and sroot password configured as init/itsgrand3 and sroot/sroot01 for
development ova.

4. Now try login to CM using init User.

5. Assign Weblm IP for getting CM license using below command.

# weblmurl <Weblm server IP>
# If your CM is deployed on public network or private IP is Natted then use below IP for weblm
to get CM license.
# weblmurl 135.9.181.63

6. Do the null translations.

Info: On a fresh CM installtion, majority of the commands will NOT work. To make the CM commands work, you must do the null translations.
For example, run the following command: change <Esc+h>. You will see only one command, change system-paramters. PSB screenshot.
Just an FYI..... You cannot login to CM CLI as a "root" user. You must first login as a init user, and then go become a "root" user.

Login to CM with sroot user and go to: cd /etc/opt/defty/ folder.

Enter: ls -lrt

We have to make them empty.

Follow the commands provided in the following screenshot.
7. Login to CM and go to sat, Add CM procr IP.

8. Login to CM SMI and provide hostname, DNS.

If you have already provided the Hostname and DNS during the deployment, they will appear here.
19. SMGR CA Certificate Installation on CM
1. Login to SMGR GUI.

2. Go to Services »» Security »» Certificates »» Authority

Under CA Functions click on CA Structures & CRLs and Download PEM file.

3. Login to CM SMI page.

4. Go to Administration »» Server Administration and click on Download files under Miscellaneous. Browse the certificate and click on download
button. Take the File name of Download Files Results.

5. Click on Trusted Certificates under Security, click on add button. Paste the file name which took in above step and click open. Provide any name
and select Repositories C.
20. Server/Application Certificate Installation on CM
Before you begin:

Ensure that SMGR and CM date/time must sync.

1. Login to CM and generate Certificate Signing Request. Copy the key after generated request.

NOTE: We must give this ‘Common Name’ while adding End Entity in SMGR
2. Login to SMGR and add ‘End Entity’. To add End Entity, go to Services »» Security »» Certificates »» Authority. Provide all required inputs.
NOTE: We must give same ‘Common Name’ here which you already given in CM while generating CSR

In the Certificate Profile drop-down list, if you not see ENDUSER option, select the default option.
3. Check whether the end entity added or not, if added click on PUBLIC WEB. A new tab will open after clicking PUBLIC WEB. Go to that tab and
click on “Create Certificate from CSR” under Enroll. Provide Username and Enrollment code which was already given while adding end entity and
paste key which copied while generating CSR on CM.

After clicking OK a pem will download automatically, if not downloaded then click on Download Certificate.

4. Login to CM SMI page. Go to Administration »» Server Administration and click on Download files under Miscellaneous. Browse the certificate
and click on download button. Copy the File name of Download Files Results (The File name appears under the File column).

5. Click on Server/Application Certificates under Security, click on add button. Paste the file name which took in above step and give enrollment
password and click open select Repository C. Restart CM.
6. Reboot the CM.

21. Add Media Server(AMS) to CM

1. Login to CM, go to sat and add node-names for AMS.

2. Do one of the following:

If Do

Option1: If you want to

use TCP

Option 2: If you want to Add TLS signaling-group to AMS. Check AMS ‘Node Name’ and ‘Far-end Domain’.
use TLS

Info: TLS is used to secure

the entire call processing.
Add Media server in CM. Specify AMS Signaling Group Number and check Node Name and Network Region.

Check AMS is added or not and check the state of AMS.

If AMS state is showing as ‘PINS’ with TLS signaling.

a. CM and AMS must have the same SMGR CA, so install the SMGR CA Certificate on AMS which is already
installed on CM.
To Install SMGR CA on AMS
Login to SMGR GUI.
Go to Services »» Security »» Certificates »» Authority
Under CA Functions click on CA Structures & CRLs and Download PEM file.
a. Login to AMS GUI and install SMGR CA Cert to Trust Store.
https://<AMS IP>:8443/emlogin/

3. Add TLS signaling-group to AMS. Check AMS ‘Node Name’ and ‘Far-end Domain’.

If added TCP signaling-group to AMS then add CM IP in AMS under Trusted Nodes.
Login to AMS GUI.
https://<AMS IP>:8443/emlogin/

4. Now Check AMS state in CM.

If AMS is still showing Pending In Service (PINS) then restart AMS from GUI.
22. Add Media Gateway to CM
1. Login to Media Gateway and take the ‘Serial No’ by executing ‘show sys’ command.

2. Login to CM, go to Sat and add media gateway.

3. Again, login to Media Gateway and provide the CM IP.

# Execute ‘show mgc list’, if MG displays any CM IP which means currently this MG is registered with that CM. Execute below command to
remove that CM ip.
# Execute ‘clear mgc list’
# Now set your CM ip in MGs mgc list by executing below command.
# set mgc list < cm ip >
# Check whether your CM ip is added in the mgc list or not by executing below command.
# ‘show mgc list’
# Save the above configuration
# copy running-config startup-config
# Restart the Media Gateway.
# reset

4. Check is Media Gateway added and Registered or not.

Login to CM, Go to SAT and execute list media-gateway
5. Follow below steps to register Media Gateway with TLS connection.

Download SMGR CA Cert (SystemManagerCA.cacert.pem) and copy to any server like Linux or SM

Change above downloaded certificate from the format pem to crt

SystemManagerCA.cacert.pem =====> SystemManagerCA.cacert.crt

# copy scp root-ca h248reg < cert_file_with_path> <scp_file_server >

Here , cert_file_with_path is full path of the certificate in Linux/SM
Ex: copy scp root-ca h248reg /home/dvit/SystemManagerCA.cacert.crt 172.16.0.2

Login to CM, change the Media-Gateway Link Encryption Type: tls-only

# Go to sat
# ch media-gateway 1
Link Encryption Type: tls-only
# save trans

6. Check is Media Gateway added and Registered or not.

23. Add CM in SMGR

1. Login to SMGR UI and Go to Services »» Inventory »» Manage Elements.

Note:
CM Type is Standalone for Non-Cluster/Array CM
CM Type is Node for Cluster/Array CM

2. Check is CM added in Inventory page or not.

3. Add CM in SIP Entities Page. Go to Elements è Routing »» SIP Entities »» New

4. Check is CM added in SIP Entities Page or not.

24. Configure Trunk in SMGR from SM to CM

We have to link CM and SM to establish communication between CM and SM.

1. Make sure CM, SM, Domains and Location must be added in SMGR.

2. Add Entity Links in SMGR from SM to CM. Go to Elements »» Routing »» Entity Links »» New
SIP Entity 1 Means »» SM, SIP Entity 2 Means »» CM
3. Check Entity Links added or not.

25. Configure Trunk in CM from CM to SM

1. Login to CM, go to SAT and add SM Asset IP in Node Names Page.
Enter details as below.
For AMS, enter AMS IP address
For SM, mention SM Asset IP address (Info: We give Management IP address while deploying SM)

2. Add SIP signaling group to SM.

3. Add Dialed String for DAC, this combination of code we will provide in Trunk group as TAC.

4. Add SIP Trunk Group in CM

Info: If, In case, Numbering Format field does not accept "private" value, then you must go to "change system-parameters customer options"
screen and go to page 6, and set the "Private Networking" field to "y".

5.
5. Check If Trunk Group is added or not.

6. Check if Trunk Group is showing IN-SERVICE or Not.

7. Specify Domain name in ip-network-region form.

8. Specify Audio codec in ip-codec-set

9. Save the translation on CM by executing ‘save translation’ command in SAT.

26. SIP Routing Configuration from CM

1. Login to CM, Go to SAT and add Dialed String for extensions.

2. Specify Trunk Group Number in router pattern page.

Note: Specify lev0-pvt for Private Trunk, this you can check in trunk group page3.

3. Specify Router Pattern number in aar analysis page.

Edit or remove default configuration.
4. Specify your dialed string details in private-numbering page.

Note: Incase if you are using public trunk then specify your dialed string details in
public-numbering page. # change public-numbering page

5. Save the translations.

27. SIP Routing Configuration from SMGR

1. Add Routing Policies. Go to Elements »» Routing »» Routing Policies »» New and click on New, specify required details and click on ‘Select
under SIP Entity as Destination’ , Select your CM and then commit.

Check the Routing Policies added or not by just refreshing this page.

2. Add Dial Patterns. Go to Elements »» Routing »» Dial Patterns »» New and click on New, specify Dial Pattern, Min length, Max length and SIP
domain. Click on Add under ‘Originating Locations
and Routing Policies’ and select your location and Routing Policies, and click on commit.

Check the Dial Patterns added or not by just refreshing this page.
3. Check added Dial Patterns are reflected in matching Routing Policies or not. Go to Elements »» Routing »» Routing Policies »» Edit

28. CM Synchronization From SMGR

1. Login to SMGR UI, Go to Services »» Inventory »» Synchronization »» Communication System
Select the CM and select the Sync type and click on Now.

Note: Before Sync make sure Privilege User is working.

29. Application Configuration in SMGR

1. Add Application in SMGR, To add Go to Elements »» Session Manager »» Application Configuration »» Application
Click on New button and specify Application Name, SIP Entity (CM Entity) and select your CM under ‘CM System for SIP Entity.
2. Add Application Sequence, To add Application Sequences, Go to Elements »» Session Manager »» Application Configuration »»
Application Sequences. Click on New button, specify Name and select your Application from ‘Available Applications’. Check whether the
Application is added in ‘Applications in this Sequence’.

30. Add SIP Stations From SMGR

Note: SIP Stations must be added from SMGR and get reflected in CM. Before add SIP station make sure the CM Synchronization is successful.

1. Make sure the Dialed String is added in both SMGR and CM.
2. To add SIP station, Go to Users »» User Management »» Manage Users. Click on New button and provide all required data.
Login name will be in the email format. For example, [email protected]

Enter and confirm "Comm-profile" password. For example, enter "123456".

Enable CM Endpoint Profile. Select the required fields as shown below.
Give Security code as 123456. Click on Extension Editor (Highlighted in red box) and specify below highlighted inputs and click on commit button.
3. Check the User added successfully in both SMGR and CM.
To check in SMGR just refresh the Manage User Page.

4. To check in CM, Login to CM CLI, Goto SAT and execute ‘list station’

Note: User must replicate in CM automatically after successfully added in SMGR

31. Generate and Install License For SMGR, SM, CM and AMS.
1. Login to SMGR UI and take the Primary Host ID.
Go to Services »» Licenses »» Server properties
2. Login to Weblg site with your handle and check whether you have permission for generating license. If you don’t have then either you Request
Access or reach out to respective product person for the license.
https://weblg.global.avaya.com/WebLGAura/

31.1. System Manager, SMGR

Prerequisite, Take Primary Host ID from SMGR, Login to SMGR GUI Go to Services »» Licenses »» Server properties

1. Login to weblg site https://weblg.global.avaya.com/WebLGAura/

Click on Generate License

2. Select SMGR product from drop down and click on SMGR Version and paste the Primary Host ID that you copied in step1 and click on Add. After
Add that host ID must list under Host ID List. Also select the License Duration and Feature and click on Generate. Download the xml file.
Login to SMGR and install SMGR License which is generated above. To install Go To
Services »» Licenses »» Install license
31.2. Session Manager, SM
1. Take Primary Host ID from SMGR and login to Weblg site https://weblg.global.avaya.com/WebLGAura/
Go to Services »» Licenses »» Server properties

2. Select SM product from drop down and click on SM and paste the Primary Host ID that you copied in step1 and click on Add.
After you click Add, that host ID must list under Host ID List. Also select the License Duration, Product Information and Feature Information and
click on Generate. Download the xml file.
Note: Here I am generating license for 2 SMs that’s why I mentioned 2 for Session Manager Instances. So, based on your requirement fill the
Feature Information.
Download the ".xml" license file. (Optionally, rename it appropriately for your identification. For example, SMLicenseForSMGR229)

Login to SMGR and install SM License which is generated above. To install Go To

Services »» Licenses »» Install license
31.3. Communication Manager, CM
1. Take Primary Host ID from SMGR and login to weblg site https://weblg.global.avaya.com/WebLGAura/
Go to Services »» Licenses »» Server properties

2. Select CM product from drop down and click on CM Version, Select Communication Manager and Call Center, Click on Next, Paste the Primary
Host ID that you copied in step1 and remove hyphen symbol from Host ID and again add hyphen symbol after Host ID and add five-digit number
click on Add button. After Add that host ID must list under Host ID List.

Example: Host ID: AB-CD-EF-GH-IJ-KL-MN è ABCDEFGHIJKLMN-10001

Also select the License Duration, Feature Information for Communication Manager and Call Center and click on Generate. Download the xml file.
Note: For Cluster/Array CM please do check Distributed CM and specify Distributed CM Instances.
Login to SMGR and install SM License which is generated above. To install Go To
Services »» Licenses »» Install license
31.4. Media Server, AMS
1. Take Primary Host ID from SMGR and login to weblg site https://weblg.global.avaya.com/WebLGAura/
Go to Services »» Licenses »» Server properties

To get the Primiary Host ID, Login to SMGR UI and take the Primary Host ID.
Go to Services »» Licenses »» Server properties

2. Login to AMS, click Generate License.

3.
3. Select AMS product from drop down and click on Media_Server and paste the Primary Host ID that you copied in step1 and click on Add.
After Add that host ID must list under Host ID List. Also select the License Duration and Feature and click on Generate. Download the xml file.

Note: Here I am generating license for 2 AMS that’s why I mentioned 2 for Media Server Instances so, based on your requirement fill the Feature
Information.

Login to SMGR and install AMS License which is generated above. To install Go To
Services »» Licenses »» Install license
32. Endpoints Configuration

32.1. EmulatorSIP and 96x1 SIP Real Phone

1. Download and install EmulatorSIP softphone.
2. Open Emulator Click on More and click on Admin and provide default admin access code 27238 and hit enter.

3. Admin Procedure,
Select ADDR, and Specify Gateway, Mask and HTTP Server save the configuration.
Select SIP, Select SIP Global Settings, Specify the SIP Domain, and set Proxy Policy to Manual, save the configuration.
Select SIP Proxy Server, and Click on New, Give SIP Proxy (SM Asset IP), Transport Type and SIP Port (TCP: 5060, TLS: 5061), save the
configuration.
<For documentation team, use TCP>

Note: For TLS you must configure Http Server IP (Linux server and enable httpd service) in ADDR and have 46xxsettings.txt, 96x1Supgrade.txt/
96xxSupgrade.txt (Based on phone type), and SMGR CA cert file in /var/www/html location
46xxsettings.txt File

SET TLSSRVRID 0
SET TRUSTCERTS <SMGRCA Cert Name>
4. Restart the Emulator or Close and Open emulator again. And check the configuration.
Emulator should get your windows IP as phone IP.
Note: SIP Proxy Configuration must look like below which means the emulator get the cert for TLS registration from Httpd server.

5. Register 2 SIP Stations.

6. Make SIP Call.

32.2. J179Emulator
1. Download and install J179Emulator
http://135.27.162.154/share_folder/SetupJ179EmulatorSIP4_0_6_0.exe

2. Open J179 Emulator, click on Admin and provide default access code 27238, and click Enter
Perform the following Administration using the Up and Down arrows:
IP Configuration »» Check the Ethernet IPv4 address. (By default, softphone will take the IP address of your system on which the softphone
is installed)
IP configuration > Servers »» Specify HTTP Server IP (This is mandatory for SIP TLS calls). (Not requried for TCP)
SIP »» SIP global settings. Set SIP domain name and SIP proxy policy to Manual. (In the SIP domain field, enter the name provided for Hos
tname Domain field during the SM deployment)
SIP proxy list »» Give SIP Proxy (SM Asset IP), Transport Type and SIP Port (TCP: 5060, TLS: 5061), save the configuration.

Note: For TLS 221. you must configure Http Server IP (Linux server and enable httpd service) in ADDR and have 46xxsettings.txt, 96x1Supgrade.
txt/ 96xxSupgrade.txt (Based on phone type), and SMGR CA cert file in /var/www/html location

46xxsettings.txt File

SET TLSSRVRID 0
SET TRUSTCERTS <SMGRCA Cert Name>

3. Restart the Emulator or Close and Open emulator again. And check the configuration.
Emulator should get your windows IP as phone IP.
Note: SIP Proxy Configuration must look like below which means the emulator get the cert for TLS registration from Httpd server.

4. Register two SIP Station.

5. Make SIP Call.

33. Add H323 Stations

1. Login to CM, go to SAT and add Dialed string for stations.
2. Add h323 station as per dialplan.

Note: Must enable IP SoftPhone if registering stations on softphone/emulators.

Enabling IP Video softphone is user requirement.

3. Check is H323 station added or not.

34. Add Cluster CM in SMGR

1. Login to SMGR UI and Go to Services »» Inventory »» Manage Elements »» New

For Duplex CM
* In the Hostname or IP Address field, enter one of the duplex CM IP
* In the Alternate IP Address field, enter other Duplex CM IP
* In the Alias IPv4 Address field, Enter the Duplex CM Alias IP which is provided during Duplex CM Configuration in CM SMI Page.

For Simplex CM
* For Simplex CM, Hostname or IP Address and Alias IPv4 Address will be same
2. Select CM Type as Node.
3. Provide all required values in SNMP Attributes (S) Page

35. Administering LHNR in SMGR

1. Add LHNR in SMGR, Go to, Elements »» Session Manager »» Network Configuration »» Local Host Name Resolution »» New
Provide same FQDN for all node CMs.

36. Administering Cluster CM in SIP Entities Page

1. Add CM in SIP Entities Page. Go to Elements »» Routing »» SIP Entities »» New
For Cluster CM, Provide the FQDN which is created in Administering LHNR in SMGR Section
2. Check whether CM is added in SIP Entities Page or not by refreshing the page.

37. Creating Cluster in SMGR

1. Login to SMGR UI and Go to Elements »» Communication Manager »» Manage Cluster »» Create New Cluster

2. Check whether the cluster is created or not by refreshing the page

3. Ensure that the Cluster Name provided in the name field must appear in the Inventory Page.
Go to Services »» Inventory »» Manage Elements

38. Enable Load Balancer in SMGR

1. To enable Load Balancer login to SMGR UI, Go to Elements »» Session Manager »» Global Settings

2. Check whether Load Balancer is enabled or not by just refreshing the page.

39. Administering Load Balancer in SMGR

1. To do login to SMGR UI, Go to Elements »» Session Manager »» Network Configuration »» Load Balancer »» New

2. Check whether Load Balancer Details added or not by refreshing this page

40. Configuring Trunks From Cluster CM to SM

2. Add all Cluster SMs in 'Cluster session-manager' page.

To add, Login to CM CLI go to SAT, execute following command and provide same SM Names which are added in step1.
3. Add SIP signaling group to SM.

4. Add Dialed String for DAC, this combination of code we will provided in Trunk group as TAC.

5. Add SIP Trunk Group in CM

6. Check If Trunk Group is added or not.

7. Check if Trunk Group is showing IN-SERVICE or Not.

8. Specify Domain name in ip-network-region form.

9. Specify Audio codec in ip-codec-set

10. Save the translation on CM by executing ‘save translation’ command in SAT.

41. Configuring Route Pattern In Cluster Options Page

1. Login to CM CLI, Go to SAT, execute following command and provide route-pattern number.

2. Save the translation on CM by executing ‘save translation’ command in SAT.

42. Configuring Homing Policy in CM

1. Login to CM CLI, Go to SAT, execute following command and define homing policy.
* Homing Policy 1(CallByCall) and 2(Persistent) are pre-defined by default.
* Homing Policy 3,4,5... 20 can be customized.

2. To use CallByCall homing-policy follow below steps.

We must first define homing-policy in COR. For example i am considering COR1 for CallByCall Policy.
Execute the following command.
# change cor 1
3. To use Persistent or custom policies follow below steps.
We must first define homing-policy in COR. For example i am considering COR11 for Pesistent/Custom Policy.
# change cor 11

Backup Server Network Region is recommended to use. Because if the Preferred CM is down then the station/user can't Home on Preferred CM.
To avoid this configure Backup Server Network Region field (1-2000) and configure the Backup CMs in the same Network Region.

In this Configuration if the Preferred CM(ALMOND) goes down, then the user/station will home on the BACKUP SERVERS (CM) in the priority
defined above screenshot.
4. Administer COR in station form so that the user/station can act as per the homing policy.
In this configuration COR1 is CallByCall Policy and COR11 is Persistent Policy.

Note:
* CallByCall Policy behavior: When the call is initiating(off hook), User/Station can Home on any one of the Cluster CM. After call ends the user
/station will UNHOME from the CM.
* Persistent Policy behavior: When the call is initiating for the first time, user/station will home on the preferred CM. On all future calls user
/station will use same preferred CM for call processing.

5. save the translations

43. Install CSP CA Cert on Cluster CM

1. Take CSP CA Cert.

Go to following page of Cluster FQDN and click "Download as PEM" under "CA: CertManagerCA"

https://Cluster_FQDN/ejbca/retrieve/ca_certs.jsp

Example: https://pusntzh135.apac.avaya.com/ejbca/retrieve/ca_certs.jsp

2. Login to CM SMI page.

Go to Administration »» Server Administration and click on Download files under Miscellaneous. Browse the certificate and click on download
button. Take the File name of Download Files Results.
3. Click on Trusted Certificates under Security, click on add button. Paste the file name which took in above step and click open. Provide any name
and select Repositories C.

4. Check whether CSP CA is added in Communication Manager Repository.

44. Install SMGR CA on CSP

We need to install certificate of SMGR CA who signed CM's CSR on CSP.

1. FTP SMGR's CA cert to CCM and execute the following commands on CCM. These commands are to be given from root ("su -" and not "su
root")
# ccm release cert-manager crtmgr -ac eventing-kafka-cp-kafka-kafkatruststore <smgr-ca.pem>
1.

You should see following o/p.

[root@da-ccm cust]# ccm release cert-manager crtmgr -ac eventing-kafka-cp-kafka-kafkatruststore PERF-SMGR.pem

"status": "CREATED",

"statusCode": 201,

"timestamp": "12-01-2021 12:08:02",

"message": "eventing-kafka-cp-kafka-kafkatruststore : Certificate added to store successfully"

Restart Kafka.
# kubectl -n avaya-kafka rollout restart sts eventing-kafka-cp-kafka

2. Install SMGR CA on Zookeeper with the following command.

# ccm release cert-manager crtmgr -ac eventing-kafka-cp-zookeeper-kafkaconnecttruststore <smgr-ca.pem>

You should see the similar output as mentioned in step2.

Restart Zookeeper

# kubectl -n avaya-kafka rollout restart sts eventing-kafka-cp-zookeeper

45. Install ADC Cert on Cluster CM

1. Take ADC Cert.
Note: Contact Sambhaji if you want to use public ADC.
To use public ADC make sure CM must be reachable from public network.
Make sure you used domain as 'avaya.com' for all components like CM, SM, SMGR and CSP.

Owner ADC Cert

Sambhaji Gayake

2. Login to CM SMI page.

Go to Administration »» Server Administration and click on Download files under Miscellaneous. Browse the certificate and click on download
button. Take the File name of Download Files Results.

3. Click on Trusted Certificates under Security, click on Add button. Paste the file name which you took in above step and click open. Provide any
name and select Repositories C.

4. Check whether ADC CA is added or not.

46. Setting up proper Weblm Server IP for Cluster CM

1. Login to CM SMI Page, Go to Administration »» Licensing »» WebLM Configuration
Give proper WebLM Server IP and submit the form.
You can also setting up the WebLM Server IP from CLI. Login to CM from putty and execute below command.
# weblmurl <IP> Example: weblmurl 14.16.0.100

47. Enable Clustering Feature from CM SMI Page

1. Login to CM SMI Page, Go to Administration »» Licensing »» Feature Administration
Select Current Setting and Display the page, Enable Clustering Feature and submit the form.

2. Check the Clustering Feature enabled is reflected in customer options page.

48. Configure CM Cluster on CM

Pre-requisites: Get all below details of CCM, CSP and CM Before install cluster.
»» Configure proper DNS IP in CM from SMI Page which is already used in CSP.
»» CCM IP, User Name and Password.
»» Data Center Name (This name we give at the time of CSP Installation)
»» KafkaFQDN, PrimaryZooFQDN (These FQDNs we give at the time of CSP Installation)
»» MyFQDN, MyAliasFQDN (These are CM FQDNs)
These FQDNs you can configure from CM SMI Page.

1. Apply 10.1.0.2 patch.

2. Login to CM SMI, Go to Administration »» Administration/Server (Maintenance) »» Network Configuration

3. Login to CM SMI, Go to Administration »» Administration/Server (Maintenance) »» Cluster Enablement

Note: Select 'yes' for having CM metrics on Prometheus and provide CCM User IP, User ID and Password.
CM metrics are like CPU, Memory, Homed Users Count, AMS resources utilization etc...

4. Save the page once you are done with the required config. CM will prompt you to restart the CM.
5. Check kafka status using below command and verify the highlighted in the screenshot.
# kafkactl status

6. Login to CM CLI, Go to sat, Add CM procr IP and save the translations using sat command 'save translation'
Note: You must perform this on the first CM that you configured in Cluster environment .
7. Verify the Master CM IP in "cluster master-cm" page.
Login to CM CLI, Go to SAT and execute the following command.
# display cluster master-cm

8. Repeat step1 to step4 and step6 for remaining CMs in the cluster.
9. Stop all CMs using 'stop -acf' command.

49. Check Master CM is recognized in SMGR

1. To do login to SMGR UI, Go to Elements »» Communication Manager »» Cluster Management »» Manage Cluster

2. Check Synchronization is automatically started with Master CM ( When SMGR recognized Master first time ), If not started then start
synchronization manually.
To do, Login to SMGR UI, Go to Inventory »» Synchronization »» Communication System

50. Install CCM and CSP

Please follow below link for CCM and CSP installation.

Flex Adoption Guide Release 1.3.0.0 - S143 Interim GA Drop 2

CSP Installation Guide

51. Survivable ESS Configuration

51.1.1. Duplex ESS Configuration
Before you begin
Ensure that the Main CM (either Simplex CM or Duplex CM) is up and running.

a. Deploy Duplex CMs with "CM Main/Survivable Max Users 41000", Follow below Link for deploying CM.
DeployingCMSimplexusingvCenterserver
b. Power ON both Duplex ESS CMs
c. Set the hostname for both the CMs from SMI Page.
Go to Administration »» Server Configuration »» Network Configuration
Update Host Name and click on change
d. Do the Duplex Configuration between ESS CMs. Follow below link.
CMDuplexConfiguration

e. Make sure that ESS CM version must be equivalent or greater than Main CM version. To check this execute below command and verify
Contains and UPDATE

# swversion

g.
h.

51.1.2. Simplex ESS Configuration

52. Take CM Full Backup

1. Login to CM SMI Page
2. Go to Administration »» Data Backup/Restore »» Backup Now

Select Full Backup under Data Sets

Provide the machines details where you want to the backup file to be copied. In below screenshot i am taking CM Full backup into the remote
server.

Note: Starting from CM 10.2 Encrypt backup using pass phrase is mandatory. so please do provide a 14 digit pass phrase code
3. To check that the backup file is properly created with proper size.
Go to Administration »» Data Backup/Restore »» Backup Logs

Here check the File Size and Status

Sometimes the backup file not created with proper size even though the status is SUCCESS, so make sure that the backup file is created with
proper size.

53. Restore CM Full Backup

1. Login to CM SMI Page
2. Go to Administration »» Data Backup/Restore »» View/Restore Data

Here two options are available to restore the backup. One is restore backup from remote server and the other one is to restore backup from CM
itself (for this you need to copy the backup file to CM )

Option 1: Restoring backup from remote server

Option 2: Restoring backup from local server (Means CM)

Make sure the backup file is present in that Local Directory

3. Once you click on View button you will see all backup files available in that directory.
Identify the backup file and select the file and also fill the Restore/Preview Settings

Note: The Pass Phrase is mandatory if the backup file is take on 10.2 CM and you need to provide the same Pass Phrase code to restore the
backup.
4. After successful restore Restart the CM.
Go to Administration »» Server »» Shutdown Server

54. CM Software Only Installation

1. Before you begin ensure that you have Rhel8.4 instance
For 10.1 and 10.2 Rhel8.4 is required
For 8.1 Rhel7.4 is required

2. Follow below steps to setup CM using the Software Only installer

3. Ensure that you configured proper repo, if not please use below repo
vi /etc/yum.repos.d/rhel8.repo

[codeready]
name=Red Hat Enterprise Linux $releasever $basearch
baseurl=http://10.129.176.245/RHEL-REPOSITORY/RHEL8/updates/codeready-builder-for-rhel-8-x86_64-rpms
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

[appstream]
name=Red Hat Enterprise Linux $releasever $basearch
baseurl=http://10.129.176.245/RHEL-REPOSITORY/RHEL8/updates/rhel-8-for-x86_64-appstream-rpms
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
[server-base]
name=Red Hat Enterprise Linux $releasever $basearch
baseurl=http://10.129.176.245/RHEL-REPOSITORY/RHEL8/updates/rhel-8-for-x86_64-baseos-rpms
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

[epel]
name=Red Hat Enterprise Linux $releasever $basearch
baseurl=http://10.129.176.245/RHEL-REPOSITORY/RHEL8/updates/epel
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

4. Get the .iso file

curl http://eagle.dr.avaya.com/field_base70/cm8-822.pj/_mipslx.O/field/ISO/CM-08.0.0.0.822-e67-1.iso -O

5. Mount the .iso file to /mnt/iso

mkdir /mnt/iso
mount -o loop,ro CM*.iso /mnt/iso

6. Verify that the manifest is for the files in the current directory
cd /mnt/iso
sha256sum -c CM-*.mf

7. (optional) Verify that the certificate file is from Avaya (Download# https://confluence.forge.avaya.com/download/attachments/137162082
/AvayaRootCert.pem?api=v2)

8. You must first copy the Avaya Product Root CA to ~/root

openssl verify -CAfile ~/AvayaRootCert.pem CM-*.cert

9. Verify the signature after extracting the public key

openssl x509 -in CM*.cert -pubkey -noout > /tmp/key
openssl dgst -sha256 -verify /tmp/key -signature CM*.sig CM*.mf

10. Install the Red Hat RPMs required by CM, you can run ./install-CM -c Large to copy/paste the yum install command
yum localinstall -y /mnt/iso/avaya-cm-setup*.rpm

Note: As below RPM versions are updating in 10.2 we need to execute below commands for 10.2 Software Only CM
yum module reset -q -y php
yum module enable -y php:7.4
yum module reset -q -y nginx
yum module enable -y nginx:1.20
yum update -y php
yum update -y nginx-filesystem

11. At this point you can run the installer

./install-CM
Answer the installer questions to configure the system.
At the end when the install is complete the server will reboot.

55. How to Administer H323 and SIP Stations using script

1. Follow below link to administer H323 and SIP station

Administer H323 and SIP stations using script

56. SMGR Software Only Installation

1. Before you begin ensure that you have Rhel8.4 instance as per SMGR profile.

2. Ensure that the proper repo is configured in Rhel8.4, if not please use below repo.

vi /etc/yum.repos.d/rhel8.repo

[server-base]
name=Red Hat Enterprise Linux $releasever $basearch
baseurl=http://10.129.176.245/RHEL-REPOSITORY/RHEL8/updates/rhel-8-for-x86_64-baseos-rpms
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

3. Preparing for Software-only deployment

a. Ensure that the system is configured with RHEL8 yum repository

b. You must have the following partitions

/var/lib/pgsql/data
/emdata
/perfdata
/swlibrary

c. Ensure that the network interface naming convention is configured to old network scheme names. System Manager requires old network
scheme eth0 and eth1.
Note: If you do not configure the old network scheme names, the deployments fails.

d. Procedure:
e. Log in to the RHEL instance as a default user and switch to the root account. To create a directory, run the following command:
mkdir /swlibrary/installer

f. Download the Avaya Aura application ISO to the RHEL instance.

g. To mount the ISO, run the following command:

mount -o loop AvayaAuraSystemManager-10.1.x.0.xxxxxx_vxx.iso /mnt

h. To copy the ISO content to the directory, run the following command
cp -rvf /mnt/* /swlibrary/installer

i. Run the following command to unmount the /mnt directory:

umount /mnt

j. Delete the downloaded ISO file.

k. To install dependencies, run the following command:

yum install SMGR-Dependencies-0.1-1.noarch.rpm -y

l. To configure the python to version 3 in RHEL 8, run the following command:

alternatives --set python /usr/bin/python3

m. Set the system-wide crypto policy to LEGACY on the RHEL 8.x and later operating system by running the following command.
update-crypto-policies --set LEGACY

n. Disable SELinux, if already enabled.

vi /etc/selinux/config
SELINUX=disabled

o. To remove cloud-init package for AWS, run the following command:

systemctl stop cloud-init
systemctl disable cloud-init
yum remove cloud-init -y

p. Run below command to change Network interface names to eth0 and eth1
sh /swlibrary/installer/setnetwork.sh

q. Reboot the system.

4. Checking the Environment.

a. Ensure that the required RPMs are already installed.

b. Log in to the RHEL instance as a default user and switch to the root account. You must run the installer as a root user.

c.
4.

c. Go to, cd /swlibrary/installer.

d. To check for installer environment check, do one of the following:

For profile 2, type the following command:
./Install_System_Manager_10.1.0.0.xxxxxx -c -p 250Kuser

For profile 3, type the following command:

./Install_System_Manager_10.1.0.0.xxxxxx -c -p 250Kuser-prof3

For profile 4, type the following command:

./Install_System_Manager_10.1.0.0.xxxxxx -c -p 300Kuser-prof4

The system checks for the environment against the installer. During this time, you cannot perform any other action.
If the check fails, take necessary steps to fix errors and perform the installer check again.

5. Deploying System Manager Software-Only ISO image using the OS console

a. Ensure that you already performed Step3 and Step4.

b. Log on to the RHEL instance.

c. Go to the /swlibrary/installer directory.

d. Run the following installation script as a root user:

./Install_System_Manager_10.1.0.0.xxxxxx
The system runs the command and displays the system changes.

e. Press Enter to continue.

The installer checks the package and environment settings.
The System Manager system displays the following message:
A reboot will be required in order to complete this. Please exit any other sessions before continuing.

f. Press Enter to continue.

g. In the Enter profile field, check the message and type the required System Manager profile from the following:
Press 1 for profile 2
Press 2 for profile 3
Press 3 for profile 4

h. Press Enter on the End User License Agreement page.

i. Press Space to read the license agreement.

j. Press Y to accept the license terms.

The installation process begins.

k. At the Enhanced Access Security Gateway (EASG) prompt, read the EASG information, and do one of the following:
To enable EASG (Recommended), type 1.
To disable EASG, type 2.

l. Select the required Backup definition parameter for System Manager schedule backup.

m. Verify the configuration details and press Enter to continue.

n. At the Do you want to continue prompt, type y.

After the installation is complete the system reboots.

o. To verify the post installation status, type the following command:

tail -f /var/log/Avaya/PostDeployLogs/post_install_sp.log
On successful post installation, System Manager displays a message.
For example: exit status of eject command is....

p. Delete the /swlibrary/installer directory.

q. Access System Manager web console using IP address or FQDN.

If installation is successful, System Manager displays the following message:
Installation of latest System manager patch is mandatory

57. SMGR Patch Installation

1. Login to SMGR CLI
Make sure that there is no SMGR Maintenance Operation is in-progress, In case if SMGR Maintenance Operation is running then wait until it is
completed.
2. Copy SMGR patch file to /swlibrary/
3. Execute below command for patch install
# SMGRPatchdeploy /swlibrary/<SMGR Patch file>

Provide password for cust user

Press Enter key to read the license

4. Please see the log /var/log/Avaya/SMGR_Patch.log for more details about patch installation.

58. SMGR GEO Configuration

SMGR Geo Configuration Steps:

1. Configuring the Primary SMGR CRL on the Secondary System Manager

2. Adding the trusted certificate of primary server to the secondary System Manager server
3. Configuring Geographic Redundancy
4. Enabling the Geographic Redundancy replication

Prerequisites For The Geographic Redundancy setup

In a Geographic Redundancy setup, the two standalone System Manager servers that you designate as primary and secondary servers must meet the
following requirements:

a. Contain the same version of the software that includes software packs.

b. Contain the same profile for primary and secondary System Manager Geographic

c. Contain the same version of the System Manager software that includes service pack and software patches.

d. Contain the same parent domain names for two System Manager systems. For example, smgr.abc.com and smgr.xyz.com are invalid
domain names because the parent domain names abc and xyz are different.

e. Communicate with each other over the network by using the IP address and FQDN.

f. In the Geographic Redundancy setup, the primary and secondary System Manager must use the same VFQDN.

g. Have a synchronized network time.

h. Use DNS to ensure that the name resolution is automatic. Otherwise, you must resolve the IP address and the host name in the /etc
/hosts file on the primary and secondary System Manager servers.

i.
h.

i. Have network latency that is less than 500 ms.

Usual procedure of Copying the CRL URL from Firefox

a. On the web browser, type https://<Fully Qualified Domain Name>/SMGR, the System Manager URL
b. On the address bar, click the Lock icon.
c. Click View certificates.
d. On the Certificate dialog box, do the following:
Click on the Details tab.
Scroll down and click the CRL Distribution Points field.
The system displays the CRL URL in the text box.
For example: http://<vFQDN>/ejbca/publicweb/webdist/certdist?cmd=crl&issuer=CN=System%20Manager%20CA,OU=MGMT,
O=AVAYA
Press Ctrl+C and copy the URL in Notepad for configuring CRL download in the Geographic Redundancy set up.
Click Ok

Usual procedure Copying the CRL URL from Chrome

c. On pop up click on Certificate is not valid, a new certificate viewer will be opened
d. On Certificate Viewer popup, click on Details
Under Certificate Fields, Select CRL Distribution Points
From Field Value copy URL and paste it in notepad
For example: http://grsmgr.avaya.com/ejbca/publicweb/webdist/certdist?cmd=crl&issuer=CN=System%20Manager%20CA,OU=MGMT,
O=AVAYA
e. Close the pop window
f.

Configuring the Primary SMGR CRL on the Secondary System Manager

a. Access the login page of the primary System Manager server.

b. Copy the CRL of the browser certificate. Follow above steps

c. Replace the vFQDN in the CRL with the IP address of the primary System Manager server.
For example, the CRL in the certificate is:
http://grsmgr.avaya.com/ejbca/publicweb/webdist/certdist?cmd=crl&issuer=CN=System%20Manager%20CA,OU=MGMT,O=AVAYA

The new CRL for the certificate will be:

http://172.16.2.5/ejbca/publicweb/webdist/certdist?cmd=crl&issuer=CN=System%20Manager%20CA,OU=MGMT,O=AVAYA

Where, <vFQDN> and <ip-address> are the respective vFQDN and IP address.

d. Log on to the secondary System Manager web console.

e. On the System Manager web console, click Services > Security > Configuration > CRL Download > Add
In Job Name, type the job name
In Job Frequency, set the frequency and recurrence to schedule the job within a few minutes after the CRL addition. (Just increase the
Task time)
In CRL Distribution Point, paste new CRL and click on Add.
Once you click on Add, a CRL URL will be listed under Distribution Point

Click on Commit

Ensure that the job is completed successfully.

f. After completion of job, Last Run Status must be successful

Adding the trusted certificate of primary server to the secondary System Manager server

Procedure:

a. Log in to the primary System Manager web console.

b. On the System Manager web console, click Services > Security > Certificates > Authority > CA Functions > CA Structure & CRLs
download the PEM file
c. Log in to the secondary System Manager web console.

d. On the System Manager web console, click Services > Inventory > Manage Elements
Select the System Manager and click on More Actions > Manage Trusted Certificates > Add
Select Import from file and choose file
Click on Retrieve Certificate
Click on Commit
Configuring Geographic Redundancy
Before you begin

a. Log on to the Secondary System Manager web console of the standalone server that you require to designate as the secondary server
and perform the following:

On the System Manager web console, click Services > Geographic Redundancy >Configure

In the dialog box, provide the details of the primary System Manager server in the following fields:
* Primary Server Username
Enter the system administrator user name that you use to log on to the primary System Manager server.

* Primary Server Password

Enter the system administrator password that you use to log on to the primary System Manager server.
* Primary Server IP

* Primary Server FQDN

Note: The configuration process takes about 30 minutes. However, the duration might vary depending on the size of the
data on the primary System Manager server.

The server that you configured becomes the secondary server and the other standalone server becomes the primary System Manager
server.

b. To view the status of the Geographic Redundancy configuration during the restart of the two application servers, perform one of the
following:
Log on to the web console of the primary System Manager server and perform the following:
a. On the System Manager web console, click Services > Geographic Redundancy
b. Refresh the GR Health page.
If Enable is available, the configuration is complete.

Log in to the secondary System Manager server as system administrator by using the command line interface and perform the following:
a. Do tail –f /home/ucmdeploy/quantum/autoReconfig.log
The system displays the progress during the restart of the two application servers. When the second application server restart
completes, the system displays the following messages:
SMGR :: operationStatus=success

SMGR :: Quantum has been successfully configured as a secondary.

Enabling the Geographic Redundancy replication

Enable the Geographic Redundancy replication between the two servers to ensure that the data gets continuously replicated between the primary and
secondary System Manager servers.

Before you begin

Log on to the System Manager web console of the primary server.

Ensure that CLI passwords on primary and secondary System Manager servers do not expire.
60 days after the System Manager CLI password expires, Geographic Redundancy becomes nonoperational. You must set a new password on
primary and secondary System Manager servers for Geographic Redundancy to become operational again.

Procedure:

a. On the System Manager web console, click Services > Geographic Redundancy.

b. Click Enable Replication.

The system displays the progress information in the Enable GR Status section.

Note: Because the server becomes unavailable, you cannot gain access to the web console. Wait until the process is complete
before you continue with the next step.

c. If the enabling process is successful, the system displays the Geographic Redundancy replication status as Enabled.

If the process fails, the system displays an error message with the replication status as Failed on the primary the System Manager web
console.
The primary server remains in the failed state while the secondary server rolls back to the previous state. Verify if the system has raised
an alarm for a temporary network connectivity failure. Retry when the network connectivity is restored. If the problem persists, contact
Avaya service personnel.

59. SMGR Upgrade

1. Before begin make sure SMGR deployed with new release OVA and provided same network and FQDN.
2. Login to SMGR CLI and wait until the system "SMGR Maintenance operation" is completed.
System will only shows "!! Installation of latest System manager patch is mandatory."
3. Copy data migration patch and System Manger mandatory patch and SMGR backup file to /swlibrary/
4. Execute below command for SMGR Upgrade

# upgradeSMGR /swlibrary/<datamigration bin file> -m -v

Provide password for cust user

Provide SMGR backup file full path
Provide SMGR Mandatory patch full path
5. Execute below command to check Upgrade Status

# tail -f /var/log/Avaya/datamigration/data_migration.log

6. Will see the below successful messages on your successful upgrade

60. How To Upgrade Media Gateway (G450/G430) Firmware

1. Login to Media Gateway and execute below command to check the Gateway Model

# show system

Check the Model and download the firmware as per your MG Model

2. Download G450/G430 latest firmware from below link to any linux server.
Username and Password qualityrules/qualityrules

G450 http://info.dr.avaya.com/defty/mg/callaway_hw/BUILD_43_11_0

G450v4 http://info.dr.avaya.com/defty/mg/saturn_hw/BUILD_43_11_0

G430 http://info.dr.avaya.com/defty/mg/venus_hw/BUILD_43_11_0

G430v3 http://info.dr.avaya.com/defty/mg/mars_hw/BUILD_43_11_0

3. Execute below command to the current firmware

# show image version

Here, MG is running on 41.0.50 version with the boot bank bank-B, So upgrade boot bank bank-A to latest
4. Execute below command to upgrade the MG firmware, when you execute this command you will be asked for the username and password of
linux server

# copy scp SW_imageA /home/dvit/g450_sw_43_11_0.bin 172.16.0.2

Here,
/home/dvit/g450_sw_43_11_0.bin is the firmware full path in the linux server
172.16.0.2 is the linux server IP

5. Execute below command to check the firmware copy status.

# show download software status 10
If Running State : Writing . . . (Copy Is still in-progress)
If Running State: Idle (Copy done successfully)

6. Check the boot bank is showing the copied version or not

# sh image version

7. Set the boot bank to latest using below command.

# set boot bank bank-A

8. Save the configuration and reset MG

# copy running-config startup-config
# reset

61. Survivable LSP Configuration

Before you begin:
Ensure that the Main CM (either Simplex CM or Duplex CM) is up and running.
Info: For LSP, you MUST use Simplex CM OVA only.

1. Deploy CM with "CM Survivable Max Users 1000", Follow below Link for deploying CM.
DeployingCMSimplexusingvCenterserver
2. Power ON LSP.
3. Make sure that LSP CM version must be equivalent or greater than Main CM version. To check this execute below command and verify Contains
and UPDATE

# swversion

4. <Optional> Update the hostname from CM SMI Page.

Go to Administration »» Server Configuration »» Network Configuration
Update Host Name and click on change

Info: When deploying CM, by default the host name is taken as "server1". This leads to confusion when taking backup or generating a license (as
we give the CM host name value), as all CMs by default take "server1" as their host name.

Note: Before install Certs, ensure that SMGR and LSP must be running on same date and time.
5. Install SMGR CA Certificate and Server/Application Certificate on LSP. Follow below links.
SMGRCACertificateInstallationonCM
Server/ApplicationCertificateInstallationonCM
Ensure that SMGR is always greater or equal to CM version.

6. Login to LSP CM SMI Page and configure the below parameters in the Server Role page
Go to Administration »» Server Configuration »» Server Role
* SID
* MID
* Registration address at the main server
Note:
If your Main CM is Duplex CM then provide Duplex CM Alias/Virtual IP here.
If your Main CM is Simplex CM then provide Simplex CM Physical IP here.
* File Synchronization address at the main cluster
Note:
If your Main CM is Duplex CM then provide Duplex CMs physical IPs as mentioned below.
If your Main CM is Simplex CM then provide Simplex CM Physical IP here.
* Main Server's Memory Setting

By default, SID and MID value is set to 1. However, you can configure MID value.

7. Login to LSP CM SMI Page and change the SID value in Network Configuration Page
Go to Administration »» Server Configuration »» Network Configuration

By default, the Server ID set to 1, you can change as per your configuration requirement.

8. Login to CM CLI go to SAT and add LSP IP in node-name page using below command.
# change node-names ip
8.

Add Survivable-processor for LSP using below command

# add survivable-processor <Name>
Here you need to provide the same name that you provided in node-names page for LSP
# add survivable-processor NLSP
Provide Cluster ID/MID value and Server ID value, You already defined these values in step 5 and step6. So provide same values here and
submit the page.

9. To register LSP with Main CM we need media resource. Media resource can be Media Gateway (G450/430) Or Media Server (AMS)
Register LSP using Media Gateway
* Login to Media Gateway CLI and execute command and ensure that your Main CM IP is configured under PRIMARY MGC HOST. Check
below

* Now add your LSP IP in SECONDARY MGC HOST and ensure that IP is displayed.
Register LSP Using Media Server
* Before you begin make sure Main CM is configured at least one AMS. To check this go to Main CM SAT and execute below command.
# list media-server
* If Media Server is configured and showing its state as INS then add this Media Server number in Survivable page using below command.
# change survivable-processor NLSP (LSP name )
Go to page 2, and set Priority with respect to Media servers : 2

Go to page 3 and provide Media Server number and submit the form.

10. Once all above configuration is done LSP should registered with Main CM. To check this go to Main CM SAT and execute below command
# list survivable-processor

11.
Limitations (and work arounds)

Limitation: Stations added in CM are not reflected in SMGR.

Description: If you add Stations directly in CM, they are not showing up in SMGR (Users > User Management > Manage Users)
Work around: Add Stations using SMGR only.

Limitation: Every license generated is linked to a specific SMGR (SMGR Host ID)
Description: When we generate a license for CM, SM, or other components, we must specify the Host ID of the SMGR. Every SMGR has a Unique Host
ID. This means, if you generate a License using an SMGR's Host ID deployed on 148.147.161.229, then all the licenses generated using this Host ID must
be installed on the same SMGR.(Users > User Management > Manage Users).
For example, if your SMGR IP is 148.147.161.229, and the Primary Host ID of this SMGR is V4-DB-16-B3-3A-D4-01, then if you generate a License for
CM using this Host ID (V4-DB-16-B3-3A-D4-01), then you must install this license on the same SMGR (148.147.161.229). This License will not work if you
try to install in on another SMGR that a different IP.

Troubleshooting:

If your Stations are not getting registered to Session Manager, then check the following:

1. On SMGR, go to Elements > Session Manager > Dashboard. In the below screenshot, the License Mode is Restricted. Which means your SM license is
not active, or invalid, or expired.
Solution: Go to WebLg, and generate a new SM license. Then, install the SM license in SMGR (Services > Licenses > Install License). The status of the Li
cense Mode must display, "Normal".

2. While you "Add SIP stations from SMGR", when you click Commit, you might encournter possible errors, and here they are.

Scenario 1: For example, Unable to add Stations. Check your System Customer options page.
For this, go to CM CLI and enter: ch sys cus.
Increase the "Maximum Stations" limit. For example, enter 1000 or based on your CM Footprint you selected during deployment.

Scenario 2: In the below case, go to CM CLI and enter: ch sys cus

In the Change system Parameters Customer Options screen, enter values for OPS and others as required. Ensure that the entered values are Not more
than the Footprint that you selected during deployment.
If you get an error that says, Enhanced 500 or EC500 is disabled, then in the Change system Parameters Customer Options screen, go to page 5, and
enable the Enhanced EC500 field.

Scenario 3: If you get the following errors, in SMGR, go to Users > User Management > Manage Users. Select the user for which the error popped up, and
click Edit.
Click Identity tab, and update the Password. Provide a new password that was not provided to other users earlier.

3. When you launch a Softphone, ideally it should open the Admin Password screen. If your Softphone opens with a dafult Extention, then you must do the
following:

On the Keyboard, press "NumLock" key (lock your numbers), and press "Del" key. It will then delete the extension and opens up the Admin Password
screen. Then enter, 27238 (craft) and login.

Approach 2

1. Login to CM CLI and switch to sroot user. Stop CM services using below command.
# stop -acf
2. Install cluster on CM using below command and provide necessary inputs.
# installCMCluster -i
2.

Customer ID:
Data Center Name:
Other Data Center Name/s:
Kafka FQDN:
Primary Zookeeper FQDN:
Secondary Zookeeper FQDN:
ADC URL:
My FQDN:
Alias FQDN:
Note: For Simplex CM My FQDN and Alias FQDN is same.
For Duplex CM these two will be different.

Enter CCM IP:

Enter CCM user ID:

3.
3. Start CM using below command.
# start -ac

Note: If the configuration is not proper/missed/CSP is not in good state, then CommunicaMgr Service will be taking more time for UP. This we
can check by doing below step 4.

4. Check kafka status using below command and verify the highlighted in the screenshot.
# kafkactl status

5. Login to CM CLI, Go to sat, Add CM procr IP.

6. Verify the Master CM IP in "cluster master-cm" page.

Login to CM CLI, Go to SAT and execute the following command.
# display cluster master-cm
7. Do the same for all your cluster CMs.

Software Only CM Deployment.

AES
TSAPI LINK
Here Switch CTI Link Number is Link number in CM
CTI USER

NetApp Clustered Data ONTAP 82 CLI Commands Sort by Task
No ratings yet
NetApp Clustered Data ONTAP 82 CLI Commands Sort by Task
6 pages
PTP Configuration and Loopback Settings
No ratings yet
PTP Configuration and Loopback Settings
6 pages
CCMM and Outbound Installation and Maintenance Guide
No ratings yet
CCMM and Outbound Installation and Maintenance Guide
1,024 pages
CCMA Technical Requirements and Operating System Configuration Guide
No ratings yet
CCMA Technical Requirements and Operating System Configuration Guide
112 pages
L2 Switch Nip
No ratings yet
L2 Switch Nip
6 pages
CCMS Technical Requirements and Operating System Configuration Guide For The Co-Resident Server
No ratings yet
CCMS Technical Requirements and Operating System Configuration Guide For The Co-Resident Server
114 pages
Resumen Cisco Vs Juniper Commands
No ratings yet
Resumen Cisco Vs Juniper Commands
5 pages
CMSE LG v2 PDF
No ratings yet
CMSE LG v2 PDF
222 pages
SMG Installation Guide 10 9 1
No ratings yet
SMG Installation Guide 10 9 1
60 pages
Contact Center, CS1000, M1 and Voice Processing Guide
100% (3)
Contact Center, CS1000, M1 and Voice Processing Guide
432 pages
CyberGuard SG User Manual 3.1.2 20051220
No ratings yet
CyberGuard SG User Manual 3.1.2 20051220
288 pages
Prerequisites Readiness Sheet HSM v2
No ratings yet
Prerequisites Readiness Sheet HSM v2
43 pages
OBM880211 MA5600T VoIP Service Configuration Exercise Guide (H.248) ISSUE 1.00
No ratings yet
OBM880211 MA5600T VoIP Service Configuration Exercise Guide (H.248) ISSUE 1.00
10 pages
Alcatel Omniswitch Commands
No ratings yet
Alcatel Omniswitch Commands
14 pages
Fortiswitchos 6.0.0 Admin Guide
No ratings yet
Fortiswitchos 6.0.0 Admin Guide
244 pages
Ecs4120-Ec Cli R01 20160627 PDF
No ratings yet
Ecs4120-Ec Cli R01 20160627 PDF
917 pages
FusionSphere V100R003C00 Quick Installation and Configuration Guide 01 PDF
100% (1)
FusionSphere V100R003C00 Quick Installation and Configuration Guide 01 PDF
33 pages
Network Device Setup Checklist
No ratings yet
Network Device Setup Checklist
6 pages
B BNG Cg43xasr9k
No ratings yet
B BNG Cg43xasr9k
324 pages
Unigy NetworkRequirementsGuide v5210
No ratings yet
Unigy NetworkRequirementsGuide v5210
44 pages
Esa Cli
No ratings yet
Esa Cli
2 pages
Section 1 - Plan, Install, Configure and Upgrade Vcenter Server and Vmware Esxi Section 1 - Plan, Install and Upgrade Vmware Esx/Esxi
No ratings yet
Section 1 - Plan, Install, Configure and Upgrade Vcenter Server and Vmware Esxi Section 1 - Plan, Install and Upgrade Vmware Esx/Esxi
30 pages
Red Hat Enterprise MRG-2-Messaging Installation Guide-En-US
No ratings yet
Red Hat Enterprise MRG-2-Messaging Installation Guide-En-US
44 pages
Fortiswitchos 6.4.0 Admin Guide
No ratings yet
Fortiswitchos 6.4.0 Admin Guide
333 pages
VCP 4.0 Words of Gratitude: Vmware
No ratings yet
VCP 4.0 Words of Gratitude: Vmware
71 pages
99-Book 723611 1285 0
No ratings yet
99-Book 723611 1285 0
745 pages
Fortiswitchos 6.0.3 Admin Guide PDF
No ratings yet
Fortiswitchos 6.0.3 Admin Guide PDF
253 pages
LTRT 17940 MSBG Series Cli Reference Guide For System and Voip Functionalities Ver 64 - 1
No ratings yet
LTRT 17940 MSBG Series Cli Reference Guide For System and Voip Functionalities Ver 64 - 1
160 pages
FortiVoice Ultra Detailed Installation Explained
No ratings yet
FortiVoice Ultra Detailed Installation Explained
3 pages
Cisco HyperFlex Edge Pre-Install Guide
No ratings yet
Cisco HyperFlex Edge Pre-Install Guide
7 pages
AG - OC01 - E1 - P1 Narrow Band Data Configuration V1.1 20p
No ratings yet
AG - OC01 - E1 - P1 Narrow Band Data Configuration V1.1 20p
20 pages
NS TrafficMgmt Guide
100% (1)
NS TrafficMgmt Guide
798 pages
Fortiswitchos 6.0.2 Admin Guide
No ratings yet
Fortiswitchos 6.0.2 Admin Guide
247 pages
ECS4150 Series CLI Reference Guide R02
No ratings yet
ECS4150 Series CLI Reference Guide R02
936 pages
Oring PDF
No ratings yet
Oring PDF
11 pages
MITEL BP Virtualization
No ratings yet
MITEL BP Virtualization
191 pages
19 - FortiSwitchOS Admin Guide - Standalone Mode
No ratings yet
19 - FortiSwitchOS Admin Guide - Standalone Mode
311 pages
Configure NTP on Cisco 2960 Switch
No ratings yet
Configure NTP on Cisco 2960 Switch
982 pages
Mivoice Mx-One: Install and Upgrade
No ratings yet
Mivoice Mx-One: Install and Upgrade
236 pages
MA5600 Multi-Service Access Module Operation and Maintenance
No ratings yet
MA5600 Multi-Service Access Module Operation and Maintenance
14 pages
MA5600 Network Configuration Guide
No ratings yet
MA5600 Network Configuration Guide
48 pages
CCMA Installation and Maintenance Guide
No ratings yet
CCMA Installation and Maintenance Guide
2,016 pages
Force10-S60 Reference Guide6 En-Us
No ratings yet
Force10-S60 Reference Guide6 En-Us
1,132 pages
ZTE - MDU Conf.
No ratings yet
ZTE - MDU Conf.
2 pages
VDS Design Best Practices
No ratings yet
VDS Design Best Practices
53 pages
2marines Server Breakdown
No ratings yet
2marines Server Breakdown
11 pages
Programming Guide 201
No ratings yet
Programming Guide 201
326 pages
01 Installation Document For UCCX 80
No ratings yet
01 Installation Document For UCCX 80
37 pages
MC Lag
No ratings yet
MC Lag
423 pages
ONTAP Tool9
No ratings yet
ONTAP Tool9
38 pages
FortiADC 4 4 0 Handbook D Series Revision1
No ratings yet
FortiADC 4 4 0 Handbook D Series Revision1
388 pages
Avaya IP Phone Registration Steps
No ratings yet
Avaya IP Phone Registration Steps
10 pages
Command Reference Guide
No ratings yet
Command Reference Guide
20 pages
IPCAgility PortsandProtocols v32
No ratings yet
IPCAgility PortsandProtocols v32
15 pages
Roger Skyline 2.en
No ratings yet
Roger Skyline 2.en
16 pages
Hitachi Storage Replication Adapter 2.1: For Vmware® Vcenter Site Recovery Manager™ 5.1/5.5 Deployment Guide
No ratings yet
Hitachi Storage Replication Adapter 2.1: For Vmware® Vcenter Site Recovery Manager™ 5.1/5.5 Deployment Guide
68 pages
Unix Cookbook
No ratings yet
Unix Cookbook
3 pages
User & Group Management Tutorial
No ratings yet
User & Group Management Tutorial
10 pages
Top 50+ Linux Commands You MUST Know - DigitalOcean
No ratings yet
Top 50+ Linux Commands You MUST Know - DigitalOcean
32 pages
Passwords
No ratings yet
Passwords
471 pages
10g Admin
No ratings yet
10g Admin
7 pages
DevOps Basics: Key Tools & Concepts
No ratings yet
DevOps Basics: Key Tools & Concepts
93 pages
Users and Groups
No ratings yet
Users and Groups
2 pages
Move or Migrate User Accounts From Old Linux Server To A New Linux Server
No ratings yet
Move or Migrate User Accounts From Old Linux Server To A New Linux Server
22 pages
Linux Lab Exercise Summary
No ratings yet
Linux Lab Exercise Summary
35 pages
Security Principles for IT Professionals
No ratings yet
Security Principles for IT Professionals
52 pages
29.2 HP-UX Trusted Systems
No ratings yet
29.2 HP-UX Trusted Systems
35 pages
PGW Post
No ratings yet
PGW Post
9 pages
Linux Command Guide for Admins
No ratings yet
Linux Command Guide for Admins
6 pages
Red-Teaming Active Directory Lab #3 (ELS - CORP) (Attack Path 2)
No ratings yet
Red-Teaming Active Directory Lab #3 (ELS - CORP) (Attack Path 2)
33 pages
Linux-PAM Guide for Sysadmins
No ratings yet
Linux-PAM Guide for Sysadmins
5 pages
OCA Solaris 11 System Admin Exam Guide
No ratings yet
OCA Solaris 11 System Admin Exam Guide
12 pages
Module 7: Cifs Shares and Sessions: Exercise
No ratings yet
Module 7: Cifs Shares and Sessions: Exercise
3 pages
IoTSecurity Lab1 IoTGoat
No ratings yet
IoTSecurity Lab1 IoTGoat
4 pages
Cryptographic Protocols Research
No ratings yet
Cryptographic Protocols Research
60 pages
LCI 102 Exam Question - Wrong-Job 47
No ratings yet
LCI 102 Exam Question - Wrong-Job 47
8 pages
Access Appliance Upgrade Guide
No ratings yet
Access Appliance Upgrade Guide
39 pages
Solaris RBAC User Management Guide
No ratings yet
Solaris RBAC User Management Guide
3 pages
Linux Assignment
No ratings yet
Linux Assignment
8 pages
Redhat Comand
No ratings yet
Redhat Comand
44 pages
T24 Essentials Key Points
100% (2)
T24 Essentials Key Points
14 pages
Crontab Guide for Linux Users
No ratings yet
Crontab Guide for Linux Users
1 page
LDAP Intergration With AIX, Linux and DB2
No ratings yet
LDAP Intergration With AIX, Linux and DB2
17 pages
Hands On Guide For Linux Admin (QA) (By KV - Reddy) .PDF - Superuser - Sudo
No ratings yet
Hands On Guide For Linux Admin (QA) (By KV - Reddy) .PDF - Superuser - Sudo
210 pages
Python Programming Practicals by Aryan
No ratings yet
Python Programming Practicals by Aryan
99 pages
Basic LINUX Commands That A DBA Should Know Oracle Database Experience
100% (2)
Basic LINUX Commands That A DBA Should Know Oracle Database Experience
47 pages