How does eHealth determine if a response path is Jitter MOS (Legacy KB ID CNC TS34544 )

Document ID : KB000051920
Last Modified Date : 14/02/2018
Show Technical Document Details
For any configured rttMon test, eHealth checks for the following OIDs during discovery:


           $CISCO.9.42.1.5.2.1.4          ;# rttMonLatestJitterOperRTTMin
           $CISCO.9.42.1.5.2.1.33         ;# rttMonLatestJitterOperOWSumSD
           $CISCO.9.42.1.5.2.1.42         ;# rttMonLatestJitterOperMOS


1. If it responds with a value for the first OID, it is "Jitter".
2. If it responds with a value for the second, it is upgraded to "Jitter One Way".
3. If it responds with a value for the last, it is upgraded to "Jitter MOS".


 


 From example device "Router1-RH":



    1.3.6.1.4.1.9.9.42.1.5.2.1.4.130, Gauge       , 0


    1.3.6.1.4.1.9.9.42.1.5.2.1.33.130, Gauge       , 0


    1.3.6.1.4.1.9.9.42.1.5.2.1.42.130, Gauge       , 0


 


 Discovered path element:


Router1-RH-Jitter-130-TOS-184-AP


*The path was assgined a "Response Path with Jitter" agent type/MTF.


 



 From example device "Router2-RH":



    1.3.6.1.4.1.9.9.42.1.5.2.1.4.131, Gauge       , 76


    1.3.6.1.4.1.9.9.42.1.5.2.1.33.131, Gauge       , 1918


    1.3.6.1.4.1.9.9.42.1.5.2.1.42.131, Gauge       , 406



 Discovered path element:


Router2-RH-JitterMOS-131-TOS-184-AP


*The path was assigned a "Response Path with Jitter-MOS" agent type/MTF.

.

Related Issues/Questions:
How does eHealth determine if a response path is Jitter MOS
How does eHealth determine if a response path is Jitter One Way
How does eHealth determine if a reponse path is Jitter

Problem Environment:
eHealth


(Legacy KB ID CNC TS34544 )