Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Interface Polling stopped. Could not remap interface -- message

NPM 10.1.1 sp1

After upgrading to 10.1.1 I am getting hundreds of these messages from my long-time installed Cisco routers. I did see something about an snmp-server ifindex persist setting which I know isn't in our routers. Truthfully, I don't know if I was getting these events in NPM 9.5 but I suspect not. What can I do to fix this? I've got 70 routers running in my network.

Thanks Much

Find more posts tagged with

Accepted answers

All comments

MarieB

Hi rmmagow--

Yep, this changed with NPM 10.0. Check out the info below for more info:

This is due to the interface index value changing in the router/switch. One thing that can cause this is a reload of the device. Orion monitor interfaces by this value and if it changes, and will no longer receive SNMP information about the interface resulting in an unknown value.

The snmp-server ifindex persist setting means enabling the snpm ifindex on the device.

This may also apply:

This is a change we recently put in for 10.0. What has happened is that your interface has changed both ifDescription and ifIndex. Hence, when we go to try and remap the interface on the rediscovery interval we don't find a match in the database. If an interface changes both its index and name, we consider this a new or different interface. This new event is to tell you of this situation and have you take action.

Most likely your interface has gone into the Unknown status as we no longer are gathering statistics and status for it.

The quick work around is to remove the Unknown interface and add in the newly named/indexed interface. But with that you lose your history. To keep your history you have to be a little more brave and update the database directly.

Steps for this:

Stop NetPerfMon service.
Check the interface index and interface description match:
SELECT InterfaceID, NodeID, InterfaceName, InterfaceIndex FROM Interfaces WHERE NodeID =
- Walk the IF MIB on the device using the SNMP MIB Browser.
- Compare the ifIndex with the InterfaceIndex in the table. Compare the ifDescription with the InterfaceName in the database. Both should be an exact match.
Update your Interfaces table with the actual values.
Restart your standard poller (NetPerfMon Service).

pack

I have removed an interface from firewall configuration and I don't see it on Node Resources on Orion. However, node is still generating alert "interface xxx is in an unknown state" on node and "Interface Polling stopped. Could not remap interface. Check ifDescription changed" events.

Has anyone seen similar issue?

How do we fix it?

Karlo.Zatylny

Hi Pack,

Are you saying that you removed the interface from the device or from Orion or both?

If you removed it from the device but not Orion, then remove it from Orion via the Node Management page, select Interfaces from the dropdown and delete the Unknown interface.

If you removed it from Orion and the events are still firing for a deleted interface, then make sure it is actually not in the interfaces table "SELECT * FROM Interfaces WHERE NodeID = XX" and restart the NetPerfMon service if it is actually deleted.

If that doesn't fix your issue, then open a support ticket so we can see what is going on.

Thanks

Bahlkris

What if you removed the interfaces from the device, but not orion. And they don't show up in the node management but they do show up in the system manager console on the server.

-b

thunter99

Can this event be disabled? I don't see a default event in the Advanced Alerts dialog. With a large core router, this can create thousands of events during a network reconfig.