This release showcases the new equipment importer, saving engineers time, and simplifying the management and set up of VSM.
We’ve also updated protocol validation to provide you with full history of any validations you have set up, when they may have failed, and how long the outage lasted, complete with availability calculations.
VSM Equipment Importer
In VSM, it is now possible to do a bulk import of equipment for any location.
On the page, Service Desk >> Equipment Locations >> Manage Equipment, next to Add Equipment, there is an Import button, which guides the users through the import process.
Clicking import prompts the user to upload a CSV template file, which is automatically validated before user proceeds with import.
An example template can be downloaded here.
The first four columns are compulsory, and the remaining fields conditionally compulsory depending on Vendor and SNMP version selected.
Alternatively, the template can be obtained by clicking Export on the Manage Equipment and updating the downloaded CSV accordingly.
Protocol Validation History
Protocol Validation is an invaluable tool bundled with VSM. It allows users to monitor an array of protocols, for example, HTTP, HTTPS, SSH, RawSocket TCP, etc. Most commonly, it would be used to check if a website goes down, and then raise an alarm.
This functionality has now been extended to show full history of any protocol validations configured, and also calculates availability over a 24 hour, and 30 days period.
So, for example, for an HTTP protocol validation on a website, users can now see at a glance the status of their site over a 3 month period, what outages there were, and how long they lasted. For reporting purposes uptime is also calculated.
Access it under Availability Manager > Protocol Validation.
Configure it under Service Desk > Equipment Locations > (right click on location) Network > Protocol Validation Configuration
Note: protocol validation history data will only be available from 24 August 2020.
Reporting Enhancements – Capacity Manager
IP Telephony Media Report
The IP Telephony Media Report now reports on DSP consumption data for Media Servers and Media Gateways, with each Network Region displayed on a separate graph.
IP Telephony Media Summary Report
The IP Telephony Media Summary Report now allows you to report on Media Gateways and Media Servers, showing percentage DSP usage per Network Region.
Scheduled Reports – Email Subject name change
Previously, when Business Partners configured scheduled reports, the reports came through in email with subject line:
Scheduled Report Notification – <Report Name> – <Customer>
This made it difficult for users to have a good overview of their reports, where they receive them in large volume.
For easier management, the subject line has been updated to the following format:
<customer> – <Report Name> – <equipment> – <location>
Stratford Robotics – Media Gateway Timeout Report – Taihape ACM – Highbrook Drive
- Network Connectivity – Under Availability Manager, previously the Network Connectivity Report was not listing any equipment in the criteria. This has now been fixed.
- Phone Data – There was an issue with the Phone Data report with some columns missing data. This has now been fixed, and the report is now correctly populating all columns with data.
- System Health Dashlets -From the system health dashlets, it is now possible to click on the server name, and be taken directly to the access concentrator page.
- IP Network Regions End Points – Previously we did not provide a tooltip on the dashlet when a row would show the severity as red, this has now been provided. IPNR Network Region Endpoints are shown as red when the registered IP endpoints has deviated 30% from average over the last five days
In VSM, it is possible to create alarms via web hooks. It can be configured so that when passing through equipment ID, address and name then an alarm is triggered. However, there was an error causing the alarms to not be raised. This has now been fixed.
There was an issue reported with Disk thresholds, where if a disk threshold is triggered, and the user manually resolves it, it should not re-raise if the threshold criteria is breached again. This was not working correctly, and after manual resolving, it would continue to raise an alarm. This has now been fixed.
SIP Session Trace
For some customers there was a performance issue on the SIP Session Trace page, where data was not loading . This has now been fixed.