Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi there, I would like to use IP SLA UDP Jitter to alert when the MOS score is greater than 3.5. My config: ip sla 2udp-jitter 1.1.5.1 5000 codec g711alawtos 184threshold 60timeout 500frequency 15history hours-of-statistics-kept 1history enhanced int...
Hi there, My environment has the following: Branch router, ISR4451-X, version 16.12.1bvManage, version 19.2.0I'd like to configure a IPSEC tunnel to Zscaler, the interface should be sourced from VPN0 so that i can use the public IP address attached t...
For cEdge routers that are connected to MPLS and need to establish control connections to the Cisco Cloud, these connections will back haul over MPLS and exit onto the internet via centralised hub firewalls. What NAT solution is recommended at the hu...
Hi there, On the link below under the “Administrative Ports Used by vManage NMS” section is mentions 'incomming' traffic: https://sdwan-docs.cisco.com/Product_Documentation/Getting_Started/Viptela_Overlay_Network_Bringup/01Bringup_Sequence_of_Events/...
I have an EEM script that watches IP-SLA then is supposed to send a SYSLOG message, event manager applet linkPoor-rtt authorization bypassevent syslog pattern "Threshold occurred for rtt"action 1.0 syslog msg "internet sla breach for rtt" I see the ...
My bad, figured it out For MOS monitoring, the SYSLOG messages need to be read or actioned upon differently to standard RTT. For example a high MOS score score of 5 indicates excellent quality, whereas a low score of 2 indicates poor quality.For RTT ...
Hi @paul driver Thanks for your reply, that was my conclusion too, so the IP-SLA will only fail when the responder is unreachable. It seems like a missed opportunity, but do you agree it is not possible to make the IP-SLA fail using, for example, RT...
The Cisco BUG ID is not a public one, but the number = CSCvq47600 Zscaler bug ID for the same issue = 58687 Did you clear your crypto session after applying the fix?
Yes, turning the feature on, so that it can be disabled. You can verify if you are having the same problem by using the 'show crypto session' command. This will display the IPsec SA traffic flows of your session. In the error condition you will see ...
