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 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.

Media Server Configuration

Adding a new AMS Login

Create an Administrator account. The VSM Collector requires access with Administrative rights.

Add an account that, when used, provides access to the Linux bash prompt.


  • Start an SSH session. At the command prompt type:

    $ su root
    • When prompted enter the 'root' user password.
  • Use the command:

    $ useradd {NAME}
    • where NAME is the account name to create.

  • Use the command: 

    $ passwd {NAME}
    • where NAME is the account name created above.

  • Hit enter. Enter the password then hit enter again.

  • Enter the command: 

    $ chage –M 99999 {NAME}
    • To set the account password to: "not expire".

    • NAME is the account created above.

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.

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


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'


Populate the fields as per the table below and then click 'Save'.

The Media Server will require a restart before it begins to send RTCP data.


FieldSetting

Monitoring Server IP

IP Address of the VSM collector

Monitoring Server Port

5005 – *See note

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.

Field

Setting

Server Address

IP Address of the VSM collector

Port

514

Configuring SNMP

SNMP is used to capture alarms raised by AMS and to query the AMS for information. The VSM 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.


Click on SNMP> Users, then select 'Add'.


Administer this user as SNMP V3 or 2c. Once administered click 'Save'.


AMS SNMP User Field Description

Fields

Setting

Security Name

SNMP Community String

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.

 

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 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.

Under General, Settings check the 'SNMP Alarm Delivery Traps' box.

Add a Trap Destination and a Trap Route.

AMS Add Trap Destination Field Descriptions

Field

Setting

Destination Address

VSM collector IP Address

Destination Port

162


AMS Add Route Destination Field Descriptions

Field

Setting

Destination Address

VSM 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'.

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'.

         

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

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 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 '.


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 configuration will be carried over for the next item.


Web Portal – Add Media Server Field Description

Field

Setting

Vendor

Avaya

Product

Media Server

Equipment Name

Friendly name

Username

SSH Username

Password

SSH Password 

IP Address/Host Name

IP Address or Hostname of the Media server

Site

Friendly name for the site (where this server is located)


SNMP

Complete the Equipment tab and then click on the ‘SNMP Query’ tab.

Click on the down arrow, and select the SNMP version you wish VSM to use for querying the equipment:

SNMP V1 or V2

FieldSetting

Version

V1, V2

SNMP Community String

Community String as administered on this equipment

SNMP V3


FieldsSetting

Version

V3

Username

SNMP V3 Username (refer to technical requirements forms)

Authentication Protocol

SHA (Recommended)

Authentication Password

Password (refer to technical requirements)

Privacy Protocol

DES (Recommended)

Privacy Password

Password (refer to technical requirements forms)


Network Connectivity


Network connectivity settings are configured at the location level and apply to all equipment by default. See here for more information.

The default location-level network connectivity settings (which are detailed in the link above) may be overridden for specific equipment using this tab.

SettingDescription
Disable Network Connectivity Ping for EquipmentSelect 'No' (this is the default) to send out ping tests. Select 'Yes' to disable ping tests from being sent out.
Ping Frequency (minutes)Defines the amount of time (in minutes) between each ping test.
Raise an alarm when maximum ping exceeds (x) msCheck this box and define a time (in milliseconds) to raise an alarm when the ping response time exceeds your set maximum time limit.
Raise an alarm when the average ping exceeds (x) msCheck this box and define a time (in milliseconds) to raise an alarm when the ping response time exceeds your set average time limit.
Raise an alarm when packet loss exceeds (x) %Check this box and define a percentage to raise an alarm when the packet loss of pings sent exceeds your set limit.

You can define alarm raising conditions using all, none or a mixture of the above “Raise an alarm when” settings


Tagging

From the add equipment pop up you can create new tags, apply existing ones, or disassociate existing tags for a specific piece of equipment.

Essentially, this tab implements the functionality on the Manage Tags page but localizes any configuration to the equipment being configured.

See here for more information.

Test Access

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:


Both SSH and SNMP should return success. If not, troubleshoot the configuration.

  1. The SSH test ensures the VSM collector can connect to, and log in using the account configured.
  2. The SNMP test ensures an SNMP query can be run.

Once testing is successful, click Add.



  • No labels