Avaya Communication Manager (ACM) Configuration

There are two parts to the configuration, the first being the server(s) under management, and the second being the supporting configuration on the web portal.

Both are covered in this chapter.

ACM Configuration

Adding a new ACM Login

The VSM Probe requires access to Avaya Communication Manager with the appropriate user rights.

This can be achieved by creating a new user within Avaya Communication Manager with user profile 18, or a read-only account with the same level of access.

Browse to the Avaya Communication Manager and log in. Click on Security > Administrator Accounts and select Add Login and Privileged Administrator and click submit:

Figure 1 – ACM Administer Accounts
Enter details as per the table below:

Figure 2 – ACM Add Login
Table 1 – ACM Add Login Field Description

Click Submit.

Figure 3 – ACM Add Login Success

Once this account has been created test it has the correct privileges by logging on a SAT and running the following non-destructive commands:
ACM Application

• display system-parameters customer-options
• list registered-ip-stations
• list measurements occupancy summary
• status ip-network-region
• monitor security-violations station-security-codes
• display alarms
• test port

ACM server Linux Bash commands

• server
• cat /etc/opt/ecs/ecs.conf
• pingall –s 1
• ifconfig –a

These commands should all return valid data. If not, the account you created is not correct.

Adding a new Media Gateway Login

The VSM Probe requires access to the Media Gateways. This can be achieved either by using the existing root account or by creating a new administrator account on each Media Gateway. To use the root account, the password needs to be added to the VSM portal and instructions are in the next section of this manual.
To add a new administrator account, refer to the completed technical requirements forms and run these commands:
G450/430:

1. Logon as 'root'

2. Run the command: 'Username [choose a username] password [choose a password] access-type admin'

3. Test you can login to the Gateway with the new credentials.

G700:

1. Logon as 'root'
2. The prompt should be 'MG-001-1'
3. Run the command: 'session stack'
4. The prompt should now be 'P330-1'

5. Run the command: 'Username [choose a username] password [choose a password] access-type admin'

6. Test you can login to the Gateway with the new credentials.

SNMP Traps and Access

SNMP traps are used to capture alarms raised by Avaya Communication Manager, SNMP Access is used by VSM to query certain information from the Avaya communication Manager
Click on SNMP > Agent Status. To make changes to SNMP configuration the Master Agent must first be stopped by clicking the 'Stop Master Agent' button, once you have completed SNMP setup Start the Master Agent again:

ACM SNMP Stop Master Agent

SNMP Access

The VSM Probe Server must be allowed to query the Avaya Communication Manager via SNMP.
Click on SNMP > Access. Click on 'Add/Change'.

ACM SNMP Access
Enter the details in the SNMP Version 2c or 3 option and click the Submit button:

SNMP Access Add/Change
ACM SNMP Access Field Description

SNMP Traps

The VSM Probe Server must be added as a destination for SNMP traps. For this reason the VSM Probe Server must be assigned a fixed IP address.
Click on SNMP > FP Traps. Enter the details in the SNMP Version 2c or 3 option and click the Submit button:

ACM SNMP Add IP Address
ACM SNMP Trap Field Description

After adding the SNMP destination it should be listed on the FP Traps page:

ACM SNMP Complete

Next the ACM application also needs to be configured to send INADS alarm information to VSM via SNMP. This is done via the shell command "almsnmpconf". To use this command, log into the ACM server Linux prompt. Execute the command:
almsnmpconf -d {VSM Probe IP ADDRESS} -c public
Where:
VSM Probe IP ADDRESS is the IP address of the VSM probe server (i.e. not the IP address of the physical server).
Check that the INAD SNMP alarms are enabled by executing the following command:
almenable
If the output is as below:

then execute the command below to enable it:
almenable –s y

1. For customers with duplicated servers, this needs to be done on each server independently.

Modify Station SNMP Settings

To complete the SNMP configuration in Avaya Communication Manager, the VSM probe server must be added to the IP Node names table as shown below and then that Name used in the IP Options page. This configuration allows VSM to request information via SNMP query:

ACM SNMP Node-names IP
ACM SNMP Node-names IP Field Description

Submit the form.

ACM SNMP System-parameters IP-Options

1. If the Download flag is set to yes as shown above then these settings will be downloaded to the phone and will overwrite any 46xxxSettings.txt file settings.

ACM SNMP System-parameters IP-Options Field Description

Submit the form.
Optional: The alternative is to make these changes in the 46xxSettings.txt files as follows. (refer to technical requirements forms):
In the SNMP section edit and uncomment the following settings. Add text as per below:

SET SNMPADD [VSM Probe IP Address (V4)]

SET SNMPSTRING [ACM SNMP Community Name] or public

1. Ensure the Avaya Communication Manager firewall is configured to pass SNMP. Click on Security > Firewall:

ACM Firewall

1. ACM policy must accept UDP 161 and 162.

Enable Syslog streaming

The following changes are required to define the VSM Probe as a destination for Avaya Communication Manager Syslog. Click on Security > Server Log Files:

ACM Syslog
ACM Syslog Field Description

Once the details have been entered click the Submit button.
At the SAT terminal enter the command 'Change Logging-Levels', on page 1 set the 'Log Data Values' field to 'Both' and All Action Values (with the exception of Display, Get, List, Monitor and Status) to 'y' and on page 2 set the 'Log PMS/AD Transactions' field to 'Y':

ACM Logging Levels Page 1

ACM Logging Levels Page 2

1. These changes increase the logging level to add a greater level of Change Manager reporting.

ACM Logging Levels Field Description

Submit the form.

Configure Off-site Backups

The following changes are required to define the VSM Probe as a destination for ACM Backups. These Backup files will be sent from the VSM Probe to the Virsae Cloud. Click on Data Backup/Restore > Schedule Backup > Add:

ACM Off-site Backups
ACM Off-site Backups Field Description

Click Add New Schedule.

Configure CDR (Optional)

Complete this section if the CDR feed from the customer will use VSM as a destination.

1. The more data that can be fed into VSM, the better the outcome will be. If there is a CDR application already in use, configure the secondary CDR feed.

The following changes are required to define the VSM Probe as a CDR destination.
Use the command 'Change IP-Services' and add the service type for the CDR1 or 2:
 
ACM IP-Services Page 1
Go to page 3 and check the setting for the CDR you just configured are as shown in the image below:

ACM IP-Services Page 3
ACM IP-Services Field Description

Submit the form.
Use the command 'Change System-Parameters CDR' – using either the primary if available or the secondary if the primary is already used enter the output type as 'Unformatted' and names the output Endpoint CDR1 or CDR2:  

ACM System-parameters CDR
ACM CDR Field Description

Submit the form.

Configure RTCP for VQM

The following changes are required to define the VSM Probe as the destination for RTCP (Voice Quality) traffic from the UC environment:

ACM System-parameters IP-Options
ACM System-parameters IP-Options Field Description

1. A single Equipment Location can support multiple RTCP Receivers. Each individual ACM and its adjuncts should report to a separate discrete RTCP Receiver using a unique port for each.

Submit the form.

Optional: Change 46xxsettings.txt file. The following lines can be added to the 46xxsettings file:

SET RTCPMON [VSM Probe IP Address (V4)]SET RTCPMONPORT 5005SET RTCPMONPERIOD 5

1. This setting in the 46xx Settings file is mandatory if you have SIP stations and you wish to receive VQM for their calls. For SIP configuration, refer to SM section of this manual. The phones will need to be restarted.

Web Portal Configuration

Add ACM

Login to the VSM web portal using your credentials and password. For the particular customer, select Service Desk > Equipment Locations. Right-click on the Equipment Location (Appliance) that will serve this particular ACM:

Web Portal - All Equipment Locations
Click on Manage Equipment.

Web Portal – Manage Equipment
Click on Add Equipment.
A form will open which you can populate with the equipment details as per table 12.
If you are adding more than one piece of the same equipment type check the 'Add another' box at the bottom of the form and the bulk of the configuratuon will be carried over for the next item.

Web Portal – Add Equipment


Web Portal - ACM Configure Equipment
Web Portal – Add ACM Field Description

Complete the Equipment tab and then click on the SNMP Query tab.
Click on the down arrow, and select the SNMP verion you wish VSM to use for querying the ACM:
SNMP V1 or V2

Web Portal – ACM SNMP V1/V2 Query
ACM SNMP V1/V2 Field Descriptions

SNMP V3

Web Portal – ACM SNMP V3 Query
ACM SNMP V3 Field Description

Under the 'Avaya Phones' section enter the SNMP Community String to be used for querying phones and then click the '+' button.
Once all fields are populated Click on the Test Access button. This will test that VSM can connect to the ACM using the settings you have entered:

Web Portal – ACM Test Access
Both Access and SNMP should return success. If not, trouble-shoot the configuration.

1. The Access test ensures the VSM probe can connect to, and login using the account configured.
2. The SNMP test ensures an SNMP query can be run.

Once testing is successful, click Add.

Testing Alarm Receipt

Right-click on the ACM you just added:

Web Portal – Updated Avaya Product List
Click on Generate Test Alarm. The command should execute successfully. If not, trouble-shoot the configuration.

Return to the home page. For the particular customer, select Availability Manager > Manage Alarms.
The Test should show as an alarm. If not, trouble-shoot the SNMP Trap configuration.

1. This test has ACM generate an SNMP trap and ensures VSM receives the same.

Configure Site Mapping (Optional)

Often the name assigned to the IP Network Region in the ACM configuration is not meaningful to the support team. Update the Site Name if you want to assign something different in these fields. The name you enter will be used to identify the site when reporting alarms.

1. This step is entirely optional and in most cases depends on the requirements of the support team.

On the Manage Equipment Page, right-click on the ACM, then click Edit.  Click on the Site Mappings Tab. 

1. Updating this form using the IPNR (IP Network Region) configuration in ACM may not be available immediately following an installation. If this step doesn't work, try again in 24 hours.

The IP Network Region numbers and names are presented from the ACM: