Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
563 views

NNMi 10.02 QA Probes status unknown (admin active, oper unknown) with ASR9001

Hello, trying here before opening a ticket.

We have an ASR9001 with a bunch of IP SLA UDP Probes that aren't coming up monitored. In NNMi they show as Status Unknown, Administrative State Active, Operational State Unknown.

I can't seem to find what OID NNMi & QA are using to find the Operational Status but have confirmed that rttMonCtrlAdminStatus in RTTMON is active for the probes.

Are IP SLA on ASR9001 unsupported? Is there something I am missing?

 

Running NNMi 10.02 on Linux, ASR9001 running IOS-XR 5.1.3 using ciscoASR9001 device profile.

0 Likes
1 Reply
Highlighted
Respected Contributor.
Respected Contributor.

Re: NNMi 10.02 QA Probes status unknown (admin active, oper unknown) with ASR9001

Hi Nick,

Beyond the device model what we really take in to account are the MIBs that the device supports, for example for Cisco devices the QA 10.01 support-matrix shows:

 

Vendor                Feature                          MIBs Supported                                 Recommended image version

Cisco             IPSLA probes                 CISCO-RTTMON-MIB                                         12.x or higher            

Cisco                   QoS                   CISCO-CLASS-BASED-QOS-MIB                               12.x or higher

 

 from your comment on the device AdminStatus it sounds like the device more than likely supports the RTTMON mib( you may always check the supported MIBs for that specific device from NNMi UI by right-clicking on the node and selecting "MIB Information" -- "List Supported Devices"). 

By looking at the MIB tree I believe we are polling for this OID:

rttMonCtrlOperState 1.3.6.1.4.1.9.9.42.1.2.9.1.10

 

If the device seems to be responding correctly to that OID I would suggest submitting a ticket to check why NNMi/QA is unable to get the OperationalState.

Regards,

Rafa

The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP

If you find this or any post resolves your issue, please be sure to mark it as an accepted solution. If you are satisfied with anyone’s response please remember to give them a KUDOS and show your appreciation.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.