IPSLA TroubleShoot Help Document

IPSLA TroubleShoot Help Document

This document covers  basic troubleshoot and Configuration details. It also help use to find and fix the issue related to Configuration and Data Collection

Topic Covered :
  1. Monitor Configuration Fails  even though Source Device is properly Enabled with IP SLA and Cisco RTTMON-MIB working fine ?
  2. IP SLA Monitor Configuration Doesn't show Devices in Add Monitor Page even though Device is Added ?
  3. Add Monitor failed. Can't alter active monitor. Try create your own monitor again?
  4. Why Threshold Parameter Settings Update doesn't reflect in Existing IP SLA Monitor ?
  5. What Threshold Parameters are available ?
  6. Why i am getting "Source router SNMP write community may be wrong" message?
  7. What value should be configured for TIMEOUT and FRQUENCY and THRESHOLD for WAN Monitor
  8. Type of Alert Generated in IP SLA WAN Montiors ?
  9. Pre-Requirements
  10. IP SLA Monitor and OID Configuration Details.
  11. Data Collection SNMP OID being Used for IP SLA Montior VoIP/WAN RTT (icmp-echo, path-echo)
  12. What is Jitter? What is Positive and Negative Jitter?
  13. What CLI equivalent is for IP SLA Monitor from OpManager?
SNMP Version Support for IP SLA (Cisco IP SLA) in OpManager?
Action
SNMP Version
Configuration
V1/V2C
Data Collection
V1/V2C/V3

Steps :
Before Configuration of IP SLA Make sure the Source Device to be used is associated to V1 or V2C with Read And Write Community.
Proceed with Configuration. Once configuration is completed switch to SNMP V3 from Device Snapshot --> Change Credential (Test & Save Snmp V3 Credential).



1) Monitor Configuration Fails  even though Source Device is properly Enabled with IP SLA and Cisco RTTMON-MIB working fine ?
  This can be due to several reasons 
   1) WAN Test Parameter Is not properly configured under Settings --> Configuration -> IP SLA --> WAN Test Parameter
      Frequency
      TimeOut
      Frequency > TimeOut.
    Certain time value <=5-10 secs will not be supported in Some Devices. The standard recommendation is 60 secs (Default Value)
    
     From Settings --> Configuration --> IP SLA --> WAN Test Parameter 
               Check for RTT Threshold Value.
               Ideally RTT Threshold < TimeOut Value.
     
   2) Icmp Path Echo : This might not be supported in all devices. In that case disable the Trace Route from Settings--> Configuration --> IP SLA --> WAN Test Parameter
               set the Value to NO and Save it.
 
  3) SNMP with RW Community is not configured in IP SLA Source Device. 
 
 4) Network is slow and SNMP Time Out happens. In this case increase the SNMP TimeOut in SNMP Credential from OpManager.

2) IP SLA Monitor Configuration Doesn't show Devices in Add Monitor Page even though Device is Added ?
Reason: Check for Device Vendor is Cisco. Some times applying template the the vendor name is not updated with Value "Cisco".
Fix: Go to Device Snapshot and Edit Device Details " Update Vendor Name to Cisco"


3) Add Monitor failed. Can't alter active monitor. Try create your own monitor again?
Reason:
    1) No more Operation is left to Configure in Device.
    2) IP SLA Agent is not enabled and Cisco-RTTMON-MIB is not properly implemented
   To Check this Use MIB Browser From Tool. Load Cisco-RTTMON MIB and Get rttMonApplProbeCapacity value.
   " This object defines the number of new probes that can be configured on a router. The number depends on the value of rttMonApplFreeMemLowWaterMark, free bytes available on the router and the system configured rttMonCtrlAdminEntry number. Equation: rttMonApplProbeCapacity = MIN(((Free_Bytes_on_the_Router - rttMonApplFreeMemLowWaterMark)/ Memory_required_by_each_probe), rttMonApplNumCtrlAdminEntry - Num_of_Probes_already_configured)) "

  If the value returned is 0 then this will not allow to configure new monitor. If Error occurs that means IP SLA Agent is not enabled. Check with Device Support for IP SLA
FIX:
  1) Delete In Active or Not in use Monitor from the Device and then create a new monitor.
  2) Check for Supported Device :
     http://cfn.cloudapps.cisco.com/ITDIT/CFN/jsp/by-feature-technology.jsp?dtid=osscdc000283 and Apply Filter as IP SLAs ICMP echo Operations.


4) Why Threshold Parameter Settings Update doesn't reflect in Existing IP SLA Monitor ?
   IP SLA In OpManager as of now support apply once threshold settings available at the time of Configuration. The threshold value used at the time configuration is written in Source Device Configuration.
   When ever an update is done from Threshold Settings page this will be applicable only for new Monitors only.


5) What Threshold Parameters are available ?
WAN Monitor : Settings --> Configuration --> IP SLA --> WAN Threshold Template

Threshold Parameter
Upper Limit / Lower Limit
Data Type
Range
Monitor
ROUND TRIP TIME
RISING_RTT, FALLING_RTT
INT
0-60000 msec
WAN

6) Why i am getting "Source router SNMP write community may be wrong" message?
Please check for below possibilities :
  1. Verify the device through telnet whether the write community is enabled or nott
  2. Make sure you enter a valid(which is enabled in source) write community string in the field.
  3. The device may not responded due to busy for this instance, please try again.

7) What value should be configured for TIMEOUT and FRQUENCY and THRESHOLD for WAN Monitor
TimeOut : Max Time to complete the sla operation. Use to restart the sla operation.
Threshold :Boundary value measured over SLA Operation. i.e RTT, Jitter. If violated it's said SLA Violation. Used to activate a response to SLA Violation like SNMP Trap or Secondary Operation.
Frequency: Specifies the duration between initiating each RTT operation
SLA Configuration follows the below : Frequency > Timeout > Threshold.


8) Type of Alert Generated in IP SLA WAN Montiors ?
   IP SLA WAN Monitor Keeps track of 2 Type of Alert.
   1) Availability Threshold Violation : If the availability % is less than 100 an Alert will be generated. This is calculated as below 
                ( Total_Completions / Total_Initiations ) * 100  <  100

  2) Round Trip Time Threshold Violation : If the  Avg_RTT exceeds the RTT Threshold Value it will generate an Alert


9)  Pre-Requirements:
1) Source Device must be Cisco Device with IP SLA Enabled .
2) Source Device should be added in OpManager
3) SNMP with RW Permission should be associated to Source Device properly.
4) Source Device should be reachable from the OpManager Server. Test with ping <IPADDRESS> if not reachable make sure it should be reachable.
5) For VoIP/Video Monitor IP SLA Responder should be enabled in the Destination Device (If Cisco Device)
6) Destination Device is not required to get added in the Opmanager Service. If it's added for other reason there is no relation with respect to IP SLA Monitor Configuration.


10. Monitor Configuration Details : OID and its Values Sample :

IP SLA Configuration OID Details :
WAN RTT Monitor :
OID
Name
Description
Value (Configuration)
1.3.6.1.4.1.9.9.42.1.2.1.1.9
rttMonCtrlAdminEntry --> rttMonCtrlAdminStatus
Status of the Montior i.e Active
4
1.3.6.1.4.1.9.9.42.1.2.1.1.4
rttMonCtrlAdminEntry --> rttMonCtrlAdminRttType
Type of RTT Operation to be performed
1(icmp echo)
1.3.6.1.4.1.9.9.42.1.2.1.1.5
rttMonCtrlAdminEntry --> rttMonCtrlAdminThreshold 
Administrative threshold limit to generate a threshold
100 (WAN Test Parameter RTT)
1.3.6.1.4.1.9.9.42.1.2.1.1.2
rttMonCtrlAdminEntry  --> rttMonCtrlAdminOwner
Entity that created this table row.
OpManager
1.3.6.1.4.1.9.9.42.1.2.1.1.6
rttMonCtrlAdminEntry --> rttMonCtrlAdminFrequency
Duration between initiating each RTT operation.
WAN Test Parameter (Frequency)
1.3.6.1.4.1.9.9.42.1.2.1.1.7
rttMonCtrlAdminEntry --> rttMonCtrlAdminTimeout
Specifies the duration to wait for a RTT operation completion.
WAN Test Parameter (TimeOut)
1.3.6.1.4.1.9.9.42.1.2.1.1.10
rttMonCtrlAdminEntry --> rttMonCtrlAdminNvgen
When set to true, this entry will be shown in 'show running' command and can be saved into Non-volatile memory.
1




1.3.6.1.4.1.9.9.42.1.2.2.1.1
rttMonEchoAdminEntry --> rttMonEchoAdminProtocol
Protocol To be used to perform RTT Operation
2
1.3.6.1.4.1.9.9.42.1.2.2.1.2
rttMonEchoAdminEntry --> rttMonEchoAdminTargetAddress
Destination IP Address
IP V4 Address
1.3.6.1.4.1.9.9.42.1.2.2.1.3
rttMonEchoAdminEntry --> rttMonEchoAdminPktDataRequestSize
Payload in bytes.
24 (WAN Test Parameter)
1.3.6.1.4.1.9.9.42.1.2.2.1.6
rttMonEchoAdminEntry --> rttMonEchoAdminSourceAddress
Source IP address 
IP V4 Address
1.3.6.1.4.1.9.9.42.1.2.2.1.9
rttMonEchoAdminEntry --> rttMonEchoAdminTOS
Type of Service
30 (WAN Test Parameter)
Scheduler:



1.3.6.1.4.1.9.9.42.1.2.5.1.1
rttMonScheduleAdminEntry --> rttMonScheduleAdminRttLife
Life Time of the Monitor. Forever
2147483647
1.3.6.1.4.1.9.9.42.1.2.5.1.2
rttMonScheduleAdminEntry --> rttMonScheduleAdminRttStartTime
This is the time when this conceptional row will activate.

1.3.6.1.4.1.9.9.42.1.2.5.1.3
rttMonScheduleAdminEntry --> rttMonScheduleAdminConceptRowAgeout
Age Out
WAN Test Parameter




Reaction Trigger: (Round Trip Time)



1.3.6.1.4.1.9.9.42.1.2.6.1.1
rttMonReactAdminEntry --> rttMonReactAdminConnectionEnable
True to generate Trigger if Connection Loss to destination occurs
1
1.3.6.1.4.1.9.9.42.1.2.6.1.2
rttMonReactAdminEntry --> rttMonReactAdminTimeoutEnable
True to generate Trigger if TimeOut to destination occurs
1
1.3.6.1.4.1.9.9.42.1.2.6.1.3
rttMonReactAdminEntry --> rttMonReactAdminThresholdType
This object specifies the conditions under which rttMonCtrlOperOverThresholdOccurred is changed
2 ( immediate)
1.3.6.1.4.1.9.9.42.1.2.6.1.4
rttMonReactAdminEntry --> rttMonReactAdminThresholdFalling
Lower RTT Threshold Limit
75
1.3.6.1.4.1.9.9.42.1.2.6.1.5
rttMonReactAdminEntry --> rttMonReactAdminThresholdCount
This object defines the 'x' value of the xOfy condition
specified in rttMonReactAdminThresholdType		5
1.3.6.1.4.1.9.9.42.1.2.6.1.6
rttMonReactAdminEntry -->  rttMonReactAdminThresholdCount2
This object defines the 'y' value of the xOfy condition
specified in rttMonReactAdminThresholdType		5
1.3.6.1.4.1.9.9.42.1.2.6.1.7
rttMonReactAdminEntry --> rttMonReactAdminActionType
Specifies what type(s), if any, of reaction(s) to generate if an operation violates
2 (trap Only)
1.3.6.1.4.1.9.9.42.1.2.6.1.8
rttMonReactAdminEntry --> rttMonReactAdminVerifyErrorEnable
If true, a reaction is generated when a RTT
operation causes rttMonCtrlOperVerifyErrorOccurred
to change its value		1


VoIP Monitor:
OID
Name
Description
Value (Configuration)
1.3.6.1.4.1.9.9.42.1.2.1.1.9
rttMonCtrlAdminEntry --> rttMonCtrlAdminStatus
Status of the Montior i.e Active
4
1.3.6.1.4.1.9.9.42.1.2.1.1.4
rttMonCtrlAdminEntry --> rttMonCtrlAdminRttType
Type of RTT Operation to be performed
9 (udp echo)
1.3.6.1.4.1.9.9.42.1.2.1.1.2
rttMonCtrlAdminEntry  --> rttMonCtrlAdminOwner
Entity that created this table row.
OpManager
1.3.6.1.4.1.9.9.42.1.2.1.1.6
rttMonCtrlAdminEntry --> rttMonCtrlAdminFrequency
Duration between initiating each RTT operation.
VoIP Call Settings
1.3.6.1.4.1.9.9.42.1.2.1.1.7
rttMonCtrlAdminEntry --> rttMonCtrlAdminTimeout
Specifies the duration to wait for a RTT operation completion.
VoIP Call Settings
1.3.6.1.4.1.9.9.42.1.2.1.1.10
rttMonCtrlAdminEntry --> rttMonCtrlAdminNvgen
When set to true, this entry will be shown in 'show running' command
and can be saved into Non-volatile memory.
1




1.3.6.1.4.1.9.9.42.1.2.2.1.1
rttMonEchoAdminEntry --> rttMonEchoAdminProtocol
Protocol To be used to perform RTT Operation
2
1.3.6.1.4.1.9.9.42.1.2.2.1.2
rttMonEchoAdminEntry -> rttMonEchoAdminTargetAddress
Destination IP Address
IP V4 Address
1.3.6.1.4.1.9.9.42.1.2.2.1.5
rttMonEchoAdminEntry --> rttMonEchoAdminTargetPort
Payload in bytes.
24 (WAN Test Parameter)
1.3.6.1.4.1.9.9.42.1.2.2.1.6
rttMonEchoAdminEntry --> rttMonEchoAdminSourceAddress
Source IP address 
IP V4 Address
1.3.6.1.4.1.9.9.42.1.2.2.1.7
rttMonEchoAdminEntry --> rttMonEchoAdminSourcePort
Source Port
16584 VOIP Call Settings
1.3.6.1.4.1.9.9.42.1.2.2.1.9
rttMonEchoAdminEntry --> rttMonEchoAdminTOS
Type of Service
30 VoIP Call Settings
1.3.6.1.4.1.9.9.42.1.2.2.1.27
rttMonEchoAdminEntry --> rttMonEchoAdminCodecType
Simulated VoIP Coded
G711U (VoIP Threshold Template)
1.3.6.1.4.1.9.9.42.1.2.2.1.31
rttMonEchoAdminEntry --> rttMonEchoAdminICPIFAdvFactor
MOS Advantage Factor
MOS (VoIP Threshold Template)
Scheduler



1.3.6.1.4.1.9.9.42.1.2.5.1.1
rttMonScheduleAdminEntry --> rttMonScheduleAdminRttLife
Life Time of the Monitor. Forever
2147483647
1.3.6.1.4.1.9.9.42.1.2.5.1.2
rttMonScheduleAdminEntry --> rttMonScheduleAdminRttStartTime
This is the time when this conceptional row will activate.

1.3.6.1.4.1.9.9.42.1.2.5.1.3
rttMonScheduleAdminEntry --> rttMonScheduleAdminConceptRowAgeout
Age Out
WAN Test Parameter




Reaction Trigger : (MOS, Jitter, Latency,PacketLoss, Round Trip Time)



1.3.6.1.4.1.9.9.42.1.2.19.1.2
rttMonReactEntry--> rttMonReactVar
This object specifies the type of reaction configured for a
probe.		1 
1.3.6.1.4.1.9.9.42.1.2.19.1.3
rttMonReactEntry--> rttMonReactThresholdType
This object specifies the conditions under which the notification ( trap ) is sent.
2 (immediate)
1.3.6.1.4.1.9.9.42.1.2.19.1.4
rttMonReactEntry--> rttMonReactActionType
Specify what type of Reaction Trigger is generated
2 (trap only)
1.3.6.1.4.1.9.9.42.1.2.19.1.6
rttMonReactEntry--> rttMonReactThresholdFalling
Lower Threshold Limit
75 (VoIP Threshold Template)
1.3.6.1.4.1.9.9.42.1.2.19.1.5
rttMonReactEntry--> rttMonReactThresholdRising
Upper threshold Limit
100 (VoIP Threshold Template)
1.3.6.1.4.1.9.9.42.1.2.19.1.11
rttMonReactEntry -->  rttMonReactStatus
Status of the RTT Row
4 ( CreateandGo)

11. Data Collection SNMP OID being Used for IP SLA Montior VoIP/WAN RTT (icmp-echo, path-echo)
VOIP Monitor : udp-jitter for VoIP
Name
OID
Desc
rttMonJitterStatsCompletions
.1.3.6.1.4.1.9.9.42.1.3.5.1.2
The number of jitter operation that have completed successfully
rttMonJitterStatsOverThresholds
.1.3.6.1.4.1.9.9.42.1.3.5.1.3
The number of jitter operations that violate threshold
rttMonJitterStatsRTTSum
.1.3.6.1.4.1.9.9.42.1.3.5.1.5
The sum of RTT's that are successfully measured
rttMonJitterStatsNumOfRTT
.1.3.6.1.4.1.9.9.42.1.3.5.1.4
The number of RTT's that are successfully measured.
rttMonJitterStatsRTTMin
.1.3.6.1.4.1.9.9.42.1.3.5.1.8
The minimum of RTT's that were successfully measured
rttMonJitterStatsRTTMax
.1.3.6.1.4.1.9.9.42.1.3.5.1.9
The maximum of RTT's that were successfully measured
rttMonJitterStatsIAJIn
.1.3.6.1.4.1.9.9.42.1.3.5.1.61
Interarrival Jitter (RFC 1889) at sender
rttMonJitterStatsIAJOut
.1.3.6.1.4.1.9.9.42.1.3.5.1.60
Interarrival Jitter (RFC 1889) at responder
rttMonJitterStatsAvgJitter
.1.3.6.1.4.1.9.9.42.1.3.5.1.62
The average of positive and negative jitter values for SD and DS direction.
rttMonJitterStatsMinOfMOS
.1.3.6.1.4.1.9.9.42.1.3.5.1.56
The minimum of all MOS values for the jitter operations in hundreds
rttMonJitterStatsMaxOfMOS
.1.3.6.1.4.1.9.9.42.1.3.5.1.57
The maximum of all MOS values for the jitter operations in hunderds
rttMonJitterStatsAvgJitterSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.63
The average of positive and negative jitter values in SD direction
rttMonJitterStatsAvgJitterDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.64
The average of positive and negative jitter values in DS direction
rttMonJitterStatsPacketLossSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.34
The number of packets lost when sent from source to destination
rttMonJitterStatsOWSumSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.41
The sum of one way times from source to destination
rttMonJitterStatsNumOfOW
.1.3.6.1.4.1.9.9.42.1.3.5.1.51
The number of one way times that are successfully measured
rttMonJitterStatsOWMinSDNew
.1.3.6.1.4.1.9.9.42.1.3.5.1.52
The minimum of all one way times from source to destination
rttMonJitterStatsOWMaxSDNew
.1.3.6.1.4.1.9.9.42.1.3.5.1.53
The maximum of all one way times from source to destination
rttMonJitterStatsNumOfPositivesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.12
The sum of number of all positive jitter values from packets sent from source to destination
rttMonJitterStatsSumOfPositivesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.13
The sum of all positive jitter values from packets sent from source to destination
rttMonJitterStatsNumOfNegativesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.18
The sum of number of all negative jitter values from packets sent from source to destination.
rttMonJitterStatsSumOfNegativesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.19
The sum of RTT's of all negative jitter values from packets sent from source to destination
rttMonJitterStatsMinOfPositivesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.10
The minimum of absolute values of all positive jitter values from packets sent from source to destination
rttMonJitterStatsMaxOfPositivesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.11
The maximum of absolute values of all positive jitter values from packets sent from source to destination
rttMonJitterStatsMinOfNegativesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.16
The minimum of all negative jitter values from packets sent from source to destination.
rttMonJitterStatsMaxOfNegativesSD
.1.3.6.1.4.1.9.9.42.1.3.5.1.17
The maximum of all negative jitter values from packets sent from source to destination
rttMonJitterStatsPacketLossDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.35
The number of packets lost when sent from destination to source
rttMonJitterStatsOWSumDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.46
The sum of one way times from destination to source
rttMonJitterStatsOWMinDSNew
.1.3.6.1.4.1.9.9.42.1.3.5.1.54
The minimum of all one way times from destination to source
rttMonJitterStatsOWMaxDSNew
.1.3.6.1.4.1.9.9.42.1.3.5.1.55
The maximum of all one way times from destination to source
rttMonJitterStatsNumOfPositivesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.24
The sum of number of all positive jitter values from packets sent from destination to source
rttMonJitterStatsSumOfPositivesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.25
The sum of RTT's of all positive jitter values from packets sent from destination to source
rttMonJitterStatsNumOfNegativesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.30
The sum of number of all negative jitter values from packets sent from destination to source
rttMonJitterStatsSumOfNegativesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.31
The sum of RTT's of all negative jitter values from packets sent from destination to source
rttMonJitterStatsMinOfPositivesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.22
The minimum of all positive jitter values from packets sent from destination to source.
rttMonJitterStatsMaxOfPositivesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.23
The maximum of all positive jitter values from packets sent from destination to source
rttMonJitterStatsMinOfNegativesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.28
The minimum of all negative jitter values from packets sent from destination to source
rttMonJitterStatsMaxOfNegativesDS
.1.3.6.1.4.1.9.9.42.1.3.5.1.29
The maximum of all negative jitter values from packets sent from destination to source.
rttMonJitterStatsPacketOutOfSequence
.1.3.6.1.4.1.9.9.42.1.3.5.1.36
The number of packets arrived out of sequence
rttMonJitterStatsPacketMIA
.1.3.6.1.4.1.9.9.42.1.3.5.1.37
The number of packets that are lost for which we cannot determine the direction.
rttMonJitterStatsPacketLateArrival
.1.3.6.1.4.1.9.9.42.1.3.5.1.38
The number of packets that arrived after the timeout.
rttMonJitterStatsError
.1.3.6.1.4.1.9.9.42.1.3.5.1.39
The number of occasions when a jitter operation could not be initiated because an internal error
rttMonJitterStatsBusies
.1.3.6.1.4.1.9.9.42.1.3.5.1.40
The number of occasions when a jitter operation could not be initiated because a previous jitter operation has not been completed.
rttMonStatsTotalsInitiations
.1.3.6.1.4.1.9.9.42.1.3.3.1.2
The number of RTT operations that have been initiated. This number includes all RTT operations which succeed or fail for whatever reason
WAN Monitor (icmp-echo)
Name
OID
Desc
rttMonStatsCaptureCompletions
.1.3.6.1.4.1.9.9.42.1.3.1.1.5
The number of RTT operations that have completed without an error and without timing out
rttMonStatsCaptureOverThresholds
.1.3.6.1.4.1.9.9.42.1.3.1.1.6
No of RTT operation that exceeded the Threshold Limit.
rttMonStatsCaptureSumCompletionTime
.1.3.6.1.4.1.9.9.42.1.3.1.1.7
Accumulated completion Time of RTT operation completed successfully
rttMonStatsCaptureCompletionTimeMax
.1.3.6.1.4.1.9.9.42.1.3.1.1.10
The max completion time of any RTT operation which completes successfully
rttMonStatsCaptureCompletionTimeMin
.1.3.6.1.4.1.9.9.42.1.3.1.1.11
The min completion time of any RTT operation which completes successfully
rttMonStatsCollectNumDisconnects
.1.3.6.1.4.1.9.9.42.1.3.2.1.1
No of times the path between end point is disconnected.
rttMonStatsCollectTimeouts
.1.3.6.1.4.1.9.9.42.1.3.2.1.2
The number of occasions when a RTT operation was not completed before a timeout occurred. Depends on the Time Out value configured
rttMonStatsCollectBusies
.1.3.6.1.4.1.9.9.42.1.3.2.1.3
The number of occasions when a RTT operation could not be initiated because a previous RTT operation has not been completed
rttMonStatsCollectDrops
.1.3.6.1.4.1.9.9.42.1.3.2.1.5
The number of occasions when a RTT operation could not be initiated because some necessary internal resource (for example memory, or SNA subsystem) was not available, or the operation completion could not be recognized.
rttMonStatsCollectSequenceErrors
.1.3.6.1.4.1.9.9.42.1.3.2.1.6
the number of RTT operation completions received with an unexpected sequence identifier.
Possible reasons may be:
1) A duplicate packet was received 
2 A response was received after it had timed-out
3) A corrupted packet was received and was not detected
rttMonStatsVerifyErrors
.1.3.6.1.4.1.9.9.42.1.3.2.1.7
The number of RTT operation completions received with data that does not compare with the expected data
rttMonStatsCollectNoConnections
.1.3.6.1.4.1.9.9.42.1.3.2.1.4
The number of occasions when a RTT operation could not be initiated because the connection to the target has not been established
rttMonStatsTotalsInitiations
.1.3.6.1.4.1.9.9.42.1.3.3.1.2
The number of RTT operations that have been initiated. This number includes all RTT operations which succeed or fail for whatever reason

path-echo (Hop By Hop View) + icmp-echo
Name
OID
Desc
rttMonStatsCaptureCompletions
.1.3.6.1.4.1.9.9.42.1.3.1.1.5
The number of RTT operations that have completed without an error and without timing out
rttMonStatsCaptureOverThresholds
.1.3.6.1.4.1.9.9.42.1.3.1.1.6
No of RTT operation that exceeded the Threshold Limit.
rttMonStatsCaptureSumCompletionTime
.1.3.6.1.4.1.9.9.42.1.3.1.1.7
Accumulated completion Time of RTT operation completed successfully
rttMonStatsCaptureCompletionTimeMax
.1.3.6.1.4.1.9.9.42.1.3.1.1.10
The max completion time of any RTT operation which completes successfully
rttMonStatsCaptureCompletionTimeMin
.1.3.6.1.4.1.9.9.42.1.3.1.1.11
The min completion time of any RTT operation which completes successfully
rttMonStatsCollectNumDisconnects
.1.3.6.1.4.1.9.9.42.1.3.2.1.1
No of times the path between end point is disconnected.
rttMonStatsCollectTimeouts
.1.3.6.1.4.1.9.9.42.1.3.2.1.2
The number of occasions when a RTT operation was not completed before a timeout occurred. Depends on the Time Out value configured
rttMonStatsCollectBusies
.1.3.6.1.4.1.9.9.42.1.3.2.1.3
The number of occasions when a RTT operation could not be initiated because a previous RTT operation has not been completed
rttMonStatsCollectDrops
.1.3.6.1.4.1.9.9.42.1.3.2.1.5
The number of occasions when a RTT operation could not be initiated because some necessary internal resource (for example memory, or SNA subsystem) was not available, or the operation completion could not be recognized.
rttMonStatsCollectSequenceErrors
.1.3.6.1.4.1.9.9.42.1.3.2.1.6
the number of RTT operation completions received with an unexpected sequence identifier.
Possible reasons may be:
1) A duplicate packet was received 
2 A response was received after it had timed-out
3) A corrupted packet was received and was not detected
rttMonStatsVerifyErrors
.1.3.6.1.4.1.9.9.42.1.3.2.1.7
The number of RTT operation completions received with data that does not compare with the expected data
rttMonStatsCollectNoConnections
.1.3.6.1.4.1.9.9.42.1.3.2.1.4
The number of occasions when a RTT operation could not be initiated because the connection to the target has not been established
rttMonStatsTotalsInitiations
.1.3.6.1.4.1.9.9.42.1.3.3.1.2
The number of RTT operations that have been initiated. This number includes all RTT operations which succeed or fail for whatever reason
rttMonStatsCollectAddress
.1.3.6.1.4.1.9.9.42.1.3.2.1.8
Specifies the address of the target for the this RTT operation. This address will be the address of the hop along the path to Destination IP Address
12. What is Jitter? What is Positive and Negative Jitter?
Jitter : Inter-packet delay variance. This variance may vary due to network behavior during packet transfer between source and destination. Network slowness, congestion or delay in network (like queuing, arriving through alternate routes, and so on). Useful to diagnose real-time traffic applications such as VoIP, Video Over VoIP, real-time conferencing.
e.g:
If 10 ms is ideal inter-packet delay.
Positive Jiiter : If packet arives in 12 ms apart then 2 is Positive Jitter
Negative Jitter:  If packet arrivies in 8 ms part then 2 is negative Jitter 
Conclusion: Positive Jitter values are undesirable. 0 Jitter values is ideal.

13. What CLI equivalent is for IP SLA Monitor from OpManager?
WAN Monitor : icm-echo
ip sla 126
 icmp-echo $TargetIP_Address source-ip $Source_IPAddress
 request-data-size 25
 tos 30
 owner $OwnerName
 threshold 150
 timeout 60000
ip sla schedule 126 life forever start-time 13:19:32 Mar 27 ageout 60

WAN Monitor - path-echo
icmp path-echo : Hop By Hop View : IF TraceRoute is enabled
ip sla 127
 path-echo $TargetIP_Address source-ip $Source_IPAddress
 tos 30
 request-data-size 25
 owner $OwnerName
 threshold 150
 timeout 60000
 paths-of-statistics-kept 2
 hops-of-statistics-kept 15
ip sla schedule 127 life forever start-time 13:15:34 Mar 27

Voip Monitor : udp-jitter for VoIP
ip sla 121
 udp-jitter $TargetIP $TargetPort source-ip $SourceIPAddress source-port 16385 codec g711ulaw advantage-factor 4
 tos 30
 owner $OwnerName
 timeout 60000
ip sla schedule 121 life forever start-time 08:30:35 Mar 21 ageout 60
Reaction-Configuration:
ip sla reaction-configuration 121 react rtt threshold-value 100 75 threshold-type immediate action-type trapOnly
ip sla reaction-configuration 121 react mos threshold-value 500 350 threshold-type immediate action-type trapOnly
ip sla reaction-configuration 121 react jitterSDAvg threshold-value 30 25 threshold-type immediate action-type trapOnly
ip sla reaction-configuration 121 react packetLossSD threshold-value 1 1 threshold-type immediate action-type trapOnly








      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • IPSLA monitoring

                    • How to Enable Debug For IPSLA

                      Please do the following : Stop OpManager Rename logs folder  add the below parameter in their wrapper.conf file  wrapper.java.additional.<next-number-in-the-series>=-DADV_WIFIMEDIATION_DEBUG=true Restart OpManager Try adding WAN RTT monitor now  ...

                    • Configuring a non-admin user for WMI monitoring (domain level)

                      For non-admin users to perform WMI monitoring in OpManager, the user profiles need to be configured accordingly in your network. This can be done: On a device level (configuring individual devices) - Link to KB On a domain level (configuring the ...

                    • Ports used by OpManager

                      Please refer the details mentioned under the heading "Port requirements"  https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html

                    • Set interval for SMS clean up

                      We can set the value for SMS out clearing period, so that you need not to run the delete query every time, and it will clear the queue in one day.  Following steps will help to do the same. 1. Take a backup of DataManagement.xml file under ...

                      Related Products