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.

ASM Configuration

Adding a new Session Manager Login

Create an Administrator account. The VSM Probe 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 System Manager account password to: "not expire".

  • NAME is the account created above.
    

Configure SM SNMP Traps

This section requires the Virsae SNMP Target Profile to be set up in System Manager. If this is not the case, please refer to the System Manager Configuration Page before proceeding.

In System Manager, navigate to Manage Serviceability Agents > Serviceability Agents:

Select an agent from the Agent List window, in this case, the Session Manager and click on the Manage Profiles button.

From the Manage Profiles window, under the SNMP Target Profiles tab, select the Virsae profile, click on 'Assign' and then the 'Commit' button.

Configure SIP Station SNMP Query

To enable VSM to understand the IP Endpoint configuration, the SIP stations must allow VSM to proactively run queries.

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:

SET SNMPADD {VSM Probe IP Address (V4)}
SET SNMPSTRING {SM SNMP Community Name or public}

Configure RTCP Monitoring and Endpoint SNMP Query

To allow VSM to monitor the voice quality of SIP endpoint calls and gather phone configuration data via SNMP, configure Session Manager to send RTCP reporting to the IP address of the VSM probe.

From the main 'System Manager' dashboard, navigate to Elements > Session Manager. Navigate to Device and Location Configuration > Device Settings Groups:

Click on the 'Default Group' button.

Expand ‘Maintenance Settings’. Add the IP address of the VSM Client in the ‘IP Address For SNMP Queries’ field and add the community string to the ‘SNMP Community’ field.

SM Device Maintenance Settings Default Group Field Description

Expand 'VoIP Monitoring Manager'. Add the IP address of the VSM Client, the port for the RTCP receiver you wish to send the RTCP data to (default is 5005), and the reporting period (default is 5 seconds).

SM Device Settings Default Group Field Description

Once complete click 'Save'.

Configure CDR and Syslog

From the main System Manager navigate to Elements > Session Manager> Session Manager Administration:

From the Session Manager Administration window (shown above) select the Session Manager Instances tab, select the Session Manager and click on Edit.

Scroll down to the CDR section and configure as per the table below.


SM CDR Field Description

Scroll down to the Logging section and configure as per the table below.

If no Syslog Servers are populated, check ‘Enable Syslog Server 1’ or ‘Enable Syslog Server 2’ and fill out the form fields.

If Syslog Server 1 is populated, check ‘Enable Syslog Server 2’ and fill out the form fields as per the table above.

Note: If both Syslog Servers are already populated you cannot administer Syslog at this time. Please contact Virsae for further assistance.

SM Logging Field Description

Click on the Commit button.

SIP Tracer

Session Manager Version6.x - Version7.x

Navigate to Elements > Session Manager > System Tools > SIP Tracer Configuration:

Select the Session Manager you wish to configure from the 'Session Manager Instances' list, then click the 'Read' button at the top of the page

Configure using the table below, then click the 'Commit' button at the top of the page. Repeat this for any other Session Managers you wish to administer for SIP Trace output.

SM SIP Tracer Field Description

Session Manager Version8.x and Later

Select the Session Manager you wish to configure from the 'Session Manager Instances' list then click the 'View' button at the top of the page.

Configure as per the table below then click the ‘Commit’ button at the top of the page. Repeat this for any other Session Managers you wish to administer for SIP Trace output.

SM SIP Tracer Field Description

Web Portal Configuration

Add SM

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 SM and select ‘Manage Equipment’

At the bottom of the ‘Manage Equipment’ page click on the ‘Add Equipment’ button.

A form will open which you can populate with the equipment details.

Select the Vendor ‘Avaya’ and Product ‘Session Manager’.

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 SM Field Description

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 SM:

SNMP V1 or V2

SM SNMP V1/V2 Field Descriptions

SNMP V3

SM SNMP V3 Field Description

Complete the Equipment tab and then click on the ‘CDR’ tab. Select the ‘Enable Collection of CDR Files’ checkbox.

Web Portal – SM CDR Field Description

Test Access

Once all fields are populated Click on the 'Test Access' button. This will test that VSM can connect to the SM using the settings you have entered:

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

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

Once testing is successful, click Add.

Generate Test Alarm

Browse to System Manager and log in. Navigate to Services > Inventory from the dashboard. Navigate to Manage Serviceability Agents > Serviceability Agents:

Generate a Test Alarm by selecting the SM Agent, and clicking on the 'Generate Test Alarm' button.

Return to the VSM home page. For the particular customer, select Availability Manager > Manage Alarms:
 

The test should show as an alarm. If not, troubleshoot the configuration.

The SM configuration is now complete.