Correct NNMi to use ifHighSpeed on discovered node

[NickRad]

Hello, Wondering if anyone else had had a similar issue and if they have resolved it. I have one particular node (Cisco ASR9922 at IOS-XR 6.6.3) that has been discovered and NNMi has resolved to use the ifSpeed metric instead of ifHighSpeed for this node.

It knows about ifHighSpeed for this node, it records the interfaces correctly but the internal interface speed is still trying to use the incorrect value from ifSpeed (4294967295) instead of the 10G+ from ifHighSpeed. This is causing a bit of issues with NPS now as the interfaces are coming up at well over 100% utilization. I have tried rediscovery of the node (but not deleting and adding it back). I do not wish to manually set interface speed for this entire node, All of our other ASR's seem to not have an issue.

Thoughts?

[NickRad · Accepted solution]

I'll see myself out. Problem resolved itself over the weekend.

[Eugene Kopyshev]

Hello,

When interfaces table directs NNMi to use HighCounters, that might happen that the ifXTable is incomplete or incorrect. In that sad case the NNMi falls back to rfc1213. Probably, if you switch on deeper trace of logging you see that right at the statusPoll time. I may advise further if you collect and share two tables: interfaces, ifXTable.

BR,