Hi All,
We are seeing node status as Unknown even though the device is managed in NPM and it passed SNMP credentials as well.. Can somebody tell me how to fix this please?
Is this after you have fully added the node into the managed nodes? What is your polling interval set to?
Yes, the nodes are fully managed in our NPM. The polling interval is set for 120 seconds. Still not sure why our interfaces details are unknown.
Select the troubled node within the "Manage Nodes" section of NPM. Then click "List Resources" if you have the option to force a refresh after the listed resources for that node show up, do this as well. Are they still showing as unknown?
Yes, tried this many times. Still no luck. Same result.
Is this happening to a single node, all nodes, or a few of them?
Have you tried to restart the Orion services?
I have seen issues like this when the ifindex (identifier that SNMP uses to poll info details about an interface) is not persistent, if the ifindex changes it might stop polling for the status of the interface, or polling the incorrect one.
What is the vendor and model of the node you are having issues with?
In Cisco devices there is a commando to have ifindex set as persistent.
Catalyst 6500 Release 12.2SX Software Configuration Guide - SNMP IfIndex Persistence [Cisco Catalyst 6500 Series Switche…
I think this is a good start to enable the SNMP if index in all the devices. We use Cisco vendor devices in our environment. Let me try this and update you. Thanks for your headsup.
Hi , Unfortunately setting the SNMP if index persistent didnt fix the issue . Still we could see the Interface status are unknown in Solarwinds.
When I deleted the Interface and re enable it again through list resource for few seconds it is showing UP and again going to Unknown status. This is really affecting our visibility to the device status , especially it affects in netflow as mainly the interface details are important for netflow . I have already raised a case with vendor and they suggested to apply hot fix 4 , even after applying still the issue remains open.
This is occuring for ISR series , Cisco 3925 series as well and still there are other versions having the same issue in solarwinds.
Sorry to hear that.
Have you tried restarting all Solarwinds services?
If you do an SNMP walk for the interfaces do you see the same IfIndex that NPM is showing for the interface in question?
You can try a walk for the OID 1.3.6.1.2.1.2.2.1.2, this will provide the interface name or description, the last digit will be index.
Hope this helps.
So I have found out the problem and found a workaround!. The problem is these interfaces are unknown specifically in one particular polling engine. When I changed the device polling to a different polling engine, everything is working as expected. We have moved our critical devices to a new polling engine now . But what makes me to wonder is there is some missing components in the problematic polling engine that makes it not to poll the interfaces or probably makes the Interface status as Unknown.
How to find what are the components installed in working polling engine and non working polling engine for these Interface related problems ?
In my case, it's happening for virtual machine's not all but some of them intermittently. When i do list resources again same interface got discovered with same name and showing status up.
I also faced the same problem for one of my windows server. I changed the polling engine of that node and it started showing status up. Then i again re-assigned the previous polling engine and now it's working.
Hope it helps to solve your issue.
