...
| 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 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.
...
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' |
Populate the fields as per the table below and then click 'Save'.
...
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.
...
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 an FTP/SFTP login credentials then revisit this section. |
Press the "Test" button to check that the VSM Collector can be reached.
...
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 fields, 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 server:
...
Media Server SNMP V1/V2 Field Descriptions
...
Fields
...
Setting
...
Version
...
V1, V2
...
SNMP Community String
...
Community String as administered on the server
...
Media Server SNMP V3 Field Description
...
Fields
...
Setting
...
Version
...
V3
...
Username
...
SNMP V3 Username
...
Authentication Protocol
...
SHA
...
Authentication Password
...
Password
...
Privacy Protocol
...
DES
Include Page EX:SNMP_Network Conn_Tagging EX:SNMP_Network Conn_Tagging
...
Privacy Password
...
Test Access
Once all fields are populated Click on the 'Test Access' button.
...