Response Path not discovered on device Cisco ASR9K Series
search cancel

Response Path not discovered on device Cisco ASR9K Series


Article ID: 8600


Updated On:


CA eHealth


Response Paths which were pre-configured on Cisco ASR9K router are not discovered by eHealth.

For example, on device "Cisco IOS XR Software (Cisco ASR9K Series), Version 5.3.3" the Response Destination and Response Source elements are missing after the eHealth discovery completed.


eHealth 6.3.3.xxeHealth 6.3.2.xxeHealth 6.3.1.xxeHealth 6.2.2.xxAny Operating System


The problem is with the device MIB configuration for the Cisco ASR9K series device.

During discovery for Response Paths, eHealth checks for the presence and values of the following RTTMON mib objects:

rttMonCtrlAdminOwner (

rttMonCtrlAdminStatus (

If any of these two OIDs is missing, Response Paths are not discovered.

The Cisco ASR9K/XR device does not support the OID rttMonCtrlAdminOwner (, hence Response Paths will not be discovered because are missing this OID entry which define the owner of the Path.


eHealth have the Discovery parameter 'NH_DISCOVER_IPSLA_NO_OWNER_STRING’ that can be used to work around this MIB issue.  Setting this discovery parameter to "Yes" in the Discover Policy will allow eHealth discovery process to use the Admin Status only to discover the Response Path element on devices where the OID rttMonCtrlAdminOwner ( is missing, meaning it has no owner string defined in the MIB.

To set this parameter from OneClick for eHealth select the Discover Policy used to discover the device, in the Parameters section search for “Discover - IPSLA no owner string elements – NH_DISCOVER_IPSLA_NO_OWNER_STRING” and set its value to Yes 


<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKSLAA4" alt="Capture.PNG" width="990" height="217">

Save the change and (re)discover the device.



1558700561781000008600_sktwi1f5rjvs16p41.png get_app