Each WAN and VoIP Alert setup will go through a configuration wizard to identify the networks they want to be alerted to and the type of alert associated with it.
Use Case : With each type of alert, the customer can choose the Service level thresholds for loss latency and utilization or MOS and be alerted accordingly. This will help them keep their SLA’s/SLO’s at check for each network
Use case: Alerts can also be proactive. They can set values to be lower than expected and be alerted of an issue as they get closer to the identified Performance degradation level.
This feature is currently in beta and will be made available under MI and SD-WAN+ licenses. For more information please refer to the KB article
... View more
WAN and VoIP: Dates back to 21 days with a minimum window of 15 minutes
Web App: Dates back to 21 days with a minimum window of 15 minutes over 1 week only
Use cases :
Greater visibility into granular details of an issue
Analyze trends such as loss or latency that range over a week
Look into specific time periods independent of when the issue is reported
Things to keep in mind :
Time zone notations are not available. The default Time zone will sync up to the user's browser accessing the MI page.
Cannot currently choose arbitrary date values outside of the standard 00, 15, 30, 45
Disabled typing into the ‘start’ and ‘end’ date box.
... View more
As the name suggests, VoIP health will now have the capability to monitor VoIP servers with Private IP addresses in DC’s that are accessible over VPN.
You can add the private IP address using the “Configure VoIP servers” option and once saved the VoIP stats to the given VoIP server will be monitored. The “Private IP” field can be selected from the dropdown box under Interface, to view VoIP stats for On-Prem or private IP address server.
Best Effort Monitoring
There are some VoIP servers that do not allow or drop the ICMP pings used to monitor VoIP services such as MOS, loss, latency, and jitter. However, as VoIP services are critical and hard to identify the exact issue, we have integrated the Best Effort monitoring to VoIP Health to give a “nearest” best estimation on VoIP performance for a given link.
This tool will measure the performance of the “nearest hop” that responds to ICMP. By enabling 'Ping Nearest Hop' under the Configure VoIP server option, the MX will start pinging to the nearest best available hop to the configured VoIP server and show the MOS, loss latency, and jitter stats to it. By enabling this, the process of elimination of faulty hops becomes easy and hence reducing the Mean Time Resolution for the problem at hand.
For more information on how to enable VoIP On-Prem and Best Effort Monitoring and the working of each component, please refer to the KB Article.
This will require no firmware upgrade and organizations with SDW+ or MI license can use this feature.
... View more