06-05-2020 09:37 AM - edited 06-05-2020 09:38 AM
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 2
udp-jitter 1.1.5.1 5000 codec g711alaw
tos 184
threshold 60
timeout 500
frequency 15
history hours-of-statistics-kept 1
history enhanced interval 900 buckets 100
ip sla logging traps
ip sla schedule 2 life forever start-time now
ip sla reaction-configuration 2 react mos threshold-value 350 349 threshold-type immediate action-type trapOnly
event manager applet linkPoor-mos
event syslog pattern "Threshold exceeded for mos"
action 1.0 syslog msg "internet sla breach for mos"
IP SLA result:
branch1#sh ip sla st 2
IPSLAs Latest Operation Statistics
IPSLA operation id: 2
Type of operation: udp-jitter
Latest RTT: 23 milliseconds
Latest operation start time: 14:28:24 UTC Fri Jun 5 2020
Latest operation return code: OK
RTT Values:
Number Of RTT: 951 RTT Min/Avg/Max: 1/23/27 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
Number of SD Jitter Samples: 904
Number of DS Jitter Samples: 926
Source to Destination Jitter Min/Avg/Max: 0/8/1000 milliseconds
Destination to Source Jitter Min/Avg/Max: 0/9/1001 milliseconds
Over Threshold:
Number Of RTT Over Threshold: 0 (0%)
Packet Loss Values:
Loss Source to Destination: 24
Source to Destination Loss Periods Number: 43
Source to Destination Loss Period Length Min/Max: 1/2
Source to Destination Inter Loss Period Length Min/Max: 1/77
Loss Destination to Source: 25
Destination to Source Loss Periods Number: 24
Destination to Source Loss Period Length Min/Max: 1/2
Destination to Source Inter Loss Period Length Min/Max: 1/133
Out Of Sequence: 0 Tail Drop: 0
Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
Calculated Planning Impairment Factor (ICPIF): 14
MOS score: 3.96
Number of successes: 21
Number of failures: 0
Operation time to live: Forever
The results are showing a MOS score of 3.96 but the alert does not happen.
Any ideas on this one?
Solved! Go to Solution.
06-10-2020 03:11 AM
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 the opposite applies, e.g a high RTT is bad.
To recognise this the IP SLA react trigger alert logic need to be reversed for example:
%RTT-3-IPSLATHRESHOLD: IP SLAs(10): Threshold below for mos | This alert indicates a bad mos score (lower) |
%RTT-3-IPSLATHRESHOLD: IP SLAs(10): Threshold exceeded for mos | This alert indicates a good mos score (higher) |
06-10-2020 03:11 AM
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 the opposite applies, e.g a high RTT is bad.
To recognise this the IP SLA react trigger alert logic need to be reversed for example:
%RTT-3-IPSLATHRESHOLD: IP SLAs(10): Threshold below for mos | This alert indicates a bad mos score (lower) |
%RTT-3-IPSLATHRESHOLD: IP SLAs(10): Threshold exceeded for mos | This alert indicates a good mos score (higher) |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide