Avaya Experience Portal VKM Guide

Overview

This guide provides the instructions to configure the monitoring of the Avaya Experience Portal using the Nectar AEP VKM; a core component of Nectar Foundation.

About this Guide

This guide explains how to:

Deploy SNMP on the AEP
Enable AEP Module
Configure the AEP VKM in the Nectar Platform
View Monitoring

Audience

This guide is intended for system administrators or engineers who have system administration access and technical knowledge of Avaya VPMS and a familiarity with deploying Nectar Foundation.

Supported Software Versions

• Nectar v8.7
• Avaya Experience Portal r4.x, 5.x, 6.x and 7.x

Deploy SNMP on the AEP

Deploying SNMP on the AEP includes the following tasks:

• Configure SNMP on the Primary VPMS
• Start the SNMP Service

Configure SNMP on the Primary VPMS

Follow these steps to configure SNMP in the Avaya VPMS:

1. Log in to the VPMS.

2. Navigate to System Configuration > SNMP.

• The Add SNMP Trap Configuration window appears.

Add SNMP Trap Configuration 

3. Select NMS as the Device using the drop-down.

4. Enter the IP address of the RIG server in the IP Address/Hostname text box.

5. Select a SNMP Version, such as 1, using the drop-down.

6. Click Save.

7. Click SNMP Agent Settings.

The SNMP Agent Settings window appears.

8. Check the appropriate Enable SNMP Version check box.

The version you select must match the version you selected in Step 5.

9. In the Security Name text box, enter the read only community string.

10. In the Authorized for SNMP Access section, click one of the following:

• Allow All IP Addresses
• Allow Only the Following; then enter the allowed RIG IP address/hostname.

11. Click Save.

Start the SNMP Service

This process is non-disruptive. However, Nectar recommends performing these changes during a scheduled maintenance window.

1. Access the VPMS with sroot/root permissions.

2. Log in as sroot or su sroot to ensure you have appropriate permission.

3. At the shell prompt, determine the status of the SNMP service using the following command:

service avpSNMPAgentSvc status

4. Start the SNMP service using the following command:

service avpSNMPAgentSvc start

5. Start the SNMP service when you reboot using the following command:

chkconfig avpSNMPAgentSvc on

6. After the SNMP service starts, test the system with a SNMP walk. 

Nectar recommends running this test before you run the VKM.

7. If you need to change the SNMP configuration, make the changes and restart the SNMP service using the following command (at the

shell prompt):

service avpSNMPAgentSvc restart

Enable AEP Module

Follow these steps to enable the AEP module:

1. Navigate to RIG > Module Configuration. The Module Configuration window appears.

2. Select Avaya Experience Portal.

Enable Avaya Experience Portal

3. Click Apply.

4. To restart the RIG and apply the changes:

• Navigate to RIG > Admin > Restart.
• When the following message appears, click Yes.

Restart 

Configure the AEP VKM in the Nectar Platform

Configuring the AEP VKM consists of the following tasks:

• Add the Primary VPMS
• WebServer Application Pollers
• Add a Secondary VPMS

Add the Primary VPMS

Follow these steps to add the primary VPMS:

1. Navigate to Modules > Avaya > Experience Portal.

The Avaya Experience Portal - Management Servers window appears.

Avaya Experience Portal - Management Servers

2. Right-click and select Add.

Add a Server

The Add Management Server window appears.

Add Management Server 

3. Enter the following information for the VPMS:

Table - Add VPMS Configuration

4. Click Add.

The new VPMS appears in the Avaya Experience Portal window.

New Primary VPMS 

WebServer Application Pollers

Nectar will periodically poll the back-end web servers to confirm that they are responding to AEP requests. Some WebServers may return 500 instead of 200. In the event that this occurs, follow these steps to modify the pollers.

• Navigate to Health > Elements > Poll Functions.
• Select and right-click on the Poll Function. 

The Edit Poll Functions dialog box appears

Edit Poll Functions 

• In the URLParams field, enter User-Agent=Mozila.
• Click Update.

Add a Secondary VPMS

Follow these steps to add a secondary VPMS to the primary VPMS:

1. Select the primary VPMS, right-click and select Add to Selected Cluster.

Add to Selected Cluster 

The Add Management Server window appears (see Figure 4-3).

2. In the Add Management Server window, enter the following for the secondary VPMS:

• Name
• Description
• IP
• Community string

3. Click Add.

The new secondary VPMS appears in the Avaya Voice Portal window below the primary VPMS cluster.

New Secondary VPMS

View Monitoring

This section explains how to:

• View Experience Portal Applications
• View Experience Portal MPPs
• View the Experience Portal Display

View Experience Portal Applications

Follow these steps to view the Experience Portal applications:

1. Navigate to Modules > Avaya > Experience Portal. The Avaya Experience Portal window appears.

2. Right-click on a VPMS and select View > Applications.

The Applications on pane appears to the right and lists the applications on the VPMS and associated attributes.

View Experience Portal MPPs

Follow these steps to view the Experience Portal Media Processing Platforms (MPPs):

1. Navigate to Modules > Avaya > Experience Portal. The Avaya Experience Portal window appears.

2. Right-click on a VPMS and select View > MPPs.

The Voice Portal MPPs on pane appears to the right and lists the MPPs and associated attributes.

View the Experience Portal Display

Follow these steps to view the Experience Portal display:

1. Navigate to Modules > Avaya > Experience Portal. The Avaya Experience Portal window appears.

2. Right-click on a VPMS and select View > Display.

The Experience Portal Display on pane appears to the right with a map showing the relationship and status of the VPMS, MPPs, and applications. It shows the MPP name, IP address, number of active calls, CPU usage percentage, memory usage percentage, and disk usage percentage. The map also shows the names of the applications and URLs.