Cisco Interfaces Unknown State

Hello all,

I have searched and seen some cases of this in past discussions. We're seeing some interfaces go into the unknown state even though in NCM if I refresh the interfaces they show up/up. Other interfaces on these devices do not come up in the Unknown State. We've seen it on several devices, seems to be more common on 10g interfaces, could be coincidence, not sure. Just wondering if someone could point me down a path or shed some light.

NCM Version 7.0.2

NPM Version 10.4

Thanks for looking!

Find more posts tagged with

interface_status

network_performance_monitoring

network_configuration_manager

Accepted answers

All comments

stuartwhyte

Hi,

I had this on a couple of implementations, specifically with 6500's. It was confirmed as a bug & fixed in 10.5.

Stuart

sjocchiogrosso

No sure what kind of devices you are working with, but some devices tend to the SNMP IfIndex when rebooting. You might want to look for a while to keep the same SNMP ifindex persistently. Typically if SolarWinds has 'unknown' interfaces it because the SNMP ifindex no longer exists on the device.

for example on Cisco devices's it could snmp-server mib ifndex persist -depending on your device family and IOS version of course

net_guy

I'm seeing it the most on the Cisco ACE modules in the 6500 chasis.

net_guy

Thanks Stuart... I am seeing this in the ACE modules in a 6500 chassis. Let me see what I can find in the release notes and see if we can update.