CMS Configuration
Adding a new CMS Login
Create an Administrator account. The VSM Probe requires access with Administrative rights. Add an account that when used provides access to the Solaris / Linux bash prompt.
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 username 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.
SNMP
SNMP is used to capture alarms raised by CMS. The VSM Probe Server 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:
CMS Alarm Origination Manager
The system displays the following message. Enter the number associated with the SNMP/SAL option, and press Enter:
CMS Alarm Origination Manager - SNMP
The system displays a list of SNMP configuration options. Enter the number associated with the Add an SNMP User option, and press Enter:
CMS Alarm origination Manager Add SNMP User
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) |
CMS SNMP User Configuration
The following summary screen is presented. Press Enter to accept:
CMS SNMP User Summary
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:
CMS Alarm Origination Manager Add SNMP Connection
Enter the number associated with NMS, and press Enter:
CMS Add Network Management System
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 probe server |
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 |
CMS SNMP Connection Configuration
Enter y.
The following summary screen is presented. Press Enter to accept:
CMS SNMP Connection Summary
Press Enter.
The system adds the SNMP Connection, then displays the following screen when done:
SNMP Connection added
Enter q to quit, and press Enter.
Login to the VSM Web Portal. For the particular customer, select Availability Manager > Manage Alarms:
CMS Test INADS
The Test Alarm should show as an alarm. If not, trouble-shoot the configuration.
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 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 (Appliance) 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’.
Web Portal – Add Equipment
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) |
Web Portal - CMS Configure Equipment
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 CMS:
SNMP V1 or V2
Web Portal – CMS SNMP V1/V2 Query
CMS SNMP V1/V2 Field Descriptions
Fields | Setting |
Version | V1, V2 |
SNMP Community String | Community String as administered on the CMS |
SNMP V3
Web Portal – CMS SNMP V3 Query
CMS SNMP V3 Field Description
Fields | Setting |
Version | V3 |
Username | SNMP V3 Username (refer to technical requirements forms) |
Authentication Protocol | SHA |
Authentication Password | Password (refer to technical requirements) |
Privacy Protocol | DES |
Privacy Password | Password (refer to technical requirements forms) |
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:
Web Portal – CMS Test Access
Both SSH and SNMP should return success. If not, trouble-shoot the configuration.
Once testing is successful, click Add.