| Info |
|---|
This section makes frequent use of data contained in the Technical Requirements. All relevant sections of the Technical Requirements Data collection should be completed or known before commencing with the steps in this section. |
There
| Table of Contents |
|---|
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.
Table of Contents
...
Media Server Configuration
Adding a new AMS Login
Create an Administrator account. The VSM Probe Collector requires access with Administrative rights.
Add an account that, when used, provides access to the Linux bash prompt.
Refer to the completed technical requirements forms:
Start an SSH session. At the command prompt type:
Code Block language text $ su root
- When prompted enter the 'root' user password.
Use the command:
Code Block language text $ useradd {NAME}where NAME is the account name to create.
Use the command:
Code Block language text $ passwd {NAME}where NAME is the account name created above.
Hit enter. Enter the password then hit enter again.
Enter the command:
Code Block language text $ chage –M 99999 {NAME}To set the System Manager account password to: "not expire".
- NAME is the account created above.
| Tip |
|---|
If you do not have root access, your Business Partner or Avaya may be able to create this account on your behalf, or you can use the ‘cust’ credentials instead. |
Configuring RTCP
Navigate to the Media Servers Web administration interface then Home > System Configuration > Media Processing > General Settings. Add a Dual Unicast Monitoring Server.
| Note |
|---|
To access the media server be aware that HTTPS administration is via port 8443. In a web browser, type the following URL: https://serverAddress:8443/em, where "serverAddress" is the address of Avaya Aura®MS. For example, https://10.60.86.209:8443/em |
| Info |
|---|
Avaya Media Servers do not support the output of all RTCP information. No 'Received DSCP' values are available from Avaya Media Servers, therefore in VSM reporting and dashlets these will show as '-1' |
Anchor
Populate the fields as per the table below and then click 'Save'.
| Tip |
|---|
The Media Server will require a restart before it begins to send RTCP data. |
...
| Field | Setting |
|---|---|
Monitoring Server IP | IP Address of the VSM probe (refer to technical requirements forms)collector |
Monitoring Server Port | 5005 – see *See note |
| Info |
|---|
Note: 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. |
Configuring Syslog
Navigate to the Media Servers Web administration interface then Home > System Configuration > Logging Settings. Add a Syslog Destination Server.
Media Server Syslog
AMS Syslog Field Description
Field | Field | Setting |
|---|---|---|
Server Address | IP Address of the VSM probe (refer to technical requirements forms)collector | |
Port | 514 |
Configuring SNMP
SNMP is used to capture alarms raised by AMS and to query the AMS for information. The VSM Probe Server Collector must be added as a destination for SNMP traps.
SNMP is configured via the AMS Web Administration interface then System Configuration> Network Settings> SNMP.
AMS SNMP
Click on SNMP> Users, then select 'Add'. 
AMS SNMP User
Administer this user as SNMP V3 or 2c using the SNMP details captured in the Technical Requirements Document. Once . Once administered click 'Save'.
AMS SNMP User Field Description
Fields | Setting |
|---|---|
Security Name | SNMP Community String (refer to technical requirements forms) |
Description | Free text field to name this user is desired |
Version | Select the version of SNMP used to query this device v1/v2c, v3. |
Access rights | read-only |
Authentication Mode (V3) | SHA (recommended) |
Authentication Password (V3) | Password |
Privacy Mode (V3) | DES (recommended) |
Privacy Password (V3) | Password |
Agent Settings
Click on SNMP> Agent Settings. 
AMS SNMP Agent settings
Under General Settings, check the 'Agent Enabled' box and ensure the port is set to 161.
Referring to the SNMP user you created in the last step, enable either Version 3 or Version 1/2c and then select the SNMP User you created form from the drop-down menu.
Once administered click 'Save'.
AMS SNMP Agent Field Descriptions
Fields | Setting |
|---|---|
Agent Enabled | Checked |
Port Number | 161 |
System Location | Free text optional field |
System Contact | Free text optional field |
System Name | Free text optional field |
Version 3 – Enabled | Checked if SNMP user was created as V3 |
User | Select the SNMP user you created |
Version 1/2c - Enabled | Checked if SNMP user was created as V1/2c |
User | Select the SNMP user you created |
Trap Destinations
Click on SNMP> Destinations>Destinations.
Under General, Settings check the 'SNMP Alarm Delivery Traps' box.
Add a Trap Destination and a Trap Route using details from the technical requirements forms.
AMS Add Trap Destination Field Descriptions
Field | Setting |
|---|---|
Destination Address | The VSM probe collector IP Address |
Destination Port | 162 |
AMS Add Route Destination Field Descriptions Anchor RouteDestination RouteDestination
Field | Setting |
|---|---|
Destination Address | The VSM probe collector IP Address |
Trap Unlocked | Checked |
Version | v1/2c or v3 |
User | SNMP User created earlier |
Description | Free text field , (optional.) |
Once administered click 'Save'.
| Tip |
|---|
The Media Server will require a restart for the changes made here to take effect. |
Configuring Backups
The following changes are required to define the VSM collector as a destination for Aura Media Server backups.
When these backup files are received by the VSM collector they will then be passed up to the Virsae Cloud.
Configuring Backup Destinations
In this section, we will configure the VSM Collector as a destination for backup files.
Navigate to Tools > Back and Restore > Backup Destinations, then click the "Add" button.
Enter the details of the VSM collector into the form shown below.
If you wish to use SFTP then you will need to obtain the Secure FTP Remote Fingerprint for the Virsae Collector. The simplest way to do this is to use WinSCP and connect to the SFTP account on the Virsae collector. Once connected in WinSCP go to 'Tabs> Server/Protocol Information' then click the 'Copy to Clipboard' button.
Paste this information into notepad or your preferred text editor and then copy the MD5 Fingerprint. The is the 'Secure FTP Remote Server Fingerprint'.
| Tip |
|---|
If you have not yet set up FTP/SFTP login credentials then revisit this section. |
Press the "Test" button to check that the VSM Collector can be reached.
Once you have tested that you can reach the VSM Collector and are happy with the settings, press "Save".
You will then be redirected back to the Backup Destination page, where you will see the newly created destination.
Configuring Backup Tasks
Once the backup destination has been created, you will need to set up a task to send the required files.
Navigate to Tools > Backup and Restore > Backup Tasks, then press "Add".
Select a name for the backup, what you want to backup, where to send the backup, and when the backups will happen.
When finished press the "Save" button.
After pressing "Save" you will be redirected to the Backup Tasks page, where you will see the newly created backup task.
Web Portal Configuration
Add AMS
Login Log in 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 AMS :and select 'Manage Equipment':
At the bottom of the 'Manage Equipment' page, click on the 'Add Equipment' button.
Select the Vendor 'Avaya' and the Product 'Media '.
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 25.
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 configuration will be carried over for the next item.
Web Portal – Add Equipment
Web Portal – Add Media Server
Web Portal – Add Media Server Field Description
Field | Setting |
|---|---|
Vendor | Avaya |
Product | Media Server |
Equipment Name | Friendly name (refer to technical requirements forms) |
Username | SSH Username (refer to technical requirements forms) |
PasswordPassword (refer to technical requirements forms) | SSH Password |
IP Address/Host Name | IP Address or Hostname of server (refer to technical requirements forms)the Media server |
Site | Friendly name for the site (where this server is located) |
...
Include Page EX:SNMP_Network Conn_Tagging EX:SNMP_Network Conn_Tagging
Test Access
...
Fields
...
Setting
...
Version
...
V1, V2
...
SNMP Community String
...
Community String as administered on the server
...
Fields
...
Setting
...
Version
...
V3
...
Username
...
SNMP V3 Username (refer to technical requirements forms)
...
Authentication Protocol
...
SHA
...
Authentication Password
...
Password (refer to technical requirements)
...
Privacy Protocol
...
DES
...
Privacy Password
...
Password (refer to technical requirements forms)
Once all fields are populated Click on the 'Test Access' button.
This will test that VSM can connect to the server using the settings you have entered:
Web Portal – ACM Test Access
Both Access SSH and SNMP should return success. If not, trouble-shoot troubleshoot the configuration.
- The Access SSH test ensures the VSM probe collector can connect to, and login log in using the account configured.
- The SNMP test ensures an SNMP query can be run.
Once testing is successful, click Add.