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.

CMS Configuration

Adding a new CMS Login

Create an Administrator account. The VSM Collector requires access with Administrative rights. Add an account that when used provides access to the Solaris / Linux bash prompt.

The CLINT license is required to be active on CMS servers for some dashlet features to work. This is generally a free license and is activated by Avaya.

Create CMS user account:

  • SSH connect to the CMS and log in using your ‘cmssvc’ credentials or a ‘super user’ account.
  • 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 you want to create and hit enter
  • Use the command “passwd NAME” where NAME is the account name you just created to set the account password and hit enter
  • Enter the password then hit enter (you will need to do this twice)
  • Enter the command “chage -M 99999 NAME” where NAME is the account you just created and hit enter to set the CMS account password to not expire.
  • Enter the command “usermod -g 1001 NAME” where NAME is the account you just created. This will add the new user to the CMS user group.
If you do not have root access Your Business Partner or Avaya may be able to create this account on your behalf.

SNMP

SNMP is used to capture alarms raised by CMS. The VSM collector must be added as a destination for SNMP traps.

SNMP is configured via the CMS management portal.


Configuring an Alarm Destination

Start the Alarm Origination Manager by running the following command:

/cms/aom/bin/aom_tool

The system displays the following messages. Enter the number associated with the Configure the Alarm Destination option, and press Enter:


The system displays the following message. Enter the number associated with the SNMP/SAL option, and press Enter:

 

The system displays a list of SNMP configuration options. Enter the number associated with the Add an SNMP User option, and press Enter:

 

The system displays the input prompt for SNMP username. Enter the following details:

CMS SNMP User Field Description

Fields

Setting

SNMP username

VirsaeV3 (or an alternative of your choice)

SNMP Version

V3

Access Level

Rouser: Read Only

Security Level

authPriv: Authenticated/Encrypted

Authentication Protocol

MD5

Authentication Password

Choose an Authentication Password (refer to technical requirements)

Encryption Protocol

DES

Encryption Password

Choose a Encryption Password (refer to technical requirements forms)



The following summary screen is presented. Press Enter to accept:


The system adds the SNMP user, then displays the following screen when done. Enter the number associated with the Add an SNMP connection option, and press Enter:


Enter the number associated with NMS, and press Enter:


The system displays the input prompt for the destination IP address. Enter the following details:

CMS SNMP Connection Field Description

Fields

Setting

Destination IP Address

IP address of the VSM collector

Destination Port Number

162

Notification Type

Trap

SNMP User

VirsaeV3 (or the alternative you added earlier)

Alarm ID

Accept the Default

Customer ID

Accept the Default

Customer Name

Accept the Default


Enter y.


The following summary screen is presented. Press Enter to accept:

Press Enter.


The system adds the SNMP Connection, then displays the following screen when done:

Enter q to quit, and press Enter.


Login to the VSM Web Portal. For the particular customer, select Availability Manager > Manage Alarms:

 

The Test Alarm should show as an alarm. If not, trouble-shoot the configuration.

This test has CMS generate an SNMP trap and ensures VSM receives the same.


CMS External Call History (Optional)

If CMS is licensed for External Call History (ECHI) then this feed can be directed to VSM.

VSM will receive this feed via SFTP or FTP.

You can check if the Handler is installed by checking if the /export/home/pserv/ech/ directory exists on the CMS server

Navigate to CMS ECHI Configuration for setup instructions.


Web Portal Configuration

Add CMS

Login to the VSM web portal using your credentials and password.

For your customer, select Service Desk > Equipment Locations. Right-click on the Equipment Location that will serve this particular CMS 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 as per the table below. 

Select the Vendor ‘Avaya’ and Product ‘Call Management System’.


 

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

Field

Setting

Vendor

Avaya

Product

Call Management System

Equipment Name

Friendly name for this CMS

Username

The administrative username you added to CMS earlier

Password

The administrative password you added to CMS earlier

IP Address / Host Name

IP Address of server (Virtual in duplicated servers)

Site

Friendly name for core 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 CMS 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 login using the account configured.
The SNMP test ensures an SNMP query can be run.

Once testing is successful, click Add.











  • No labels