LMS 3.1. Device Type UNKNOWN but reachable in CM

Unanswered Question
Jul 9th, 2009
User Badges:

In my DCR there are several devices (most of them 3560) which are marked as unknown device type, but CM identifies them correctly. SNMP Walk from Device Center works fine too. CS is 3.2.0 (MDF 1.23) and CM 5.1.3.

Any ideas what could be the reason why the device type is not updated?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 07/09/2009 - 06:37
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the sysObjectID of the devices and the NMSROOT/lib/classpath/com/cisco/nm/cwcs/mdf/mdfdata.xml file.

t.kraemer Thu, 07/09/2009 - 07:01
User Badges:

Device Center SNMP walk shows sysObjectID "CISCO-PRODUCTS-MIB::catalyst3560G48PS", which should be 1.3.6.1.4.1.9.1.616.



Attachment: 
Joe Clarke Thu, 07/09/2009 - 07:05
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Are these devices also managed by RME? If so, has their inventory been collected successfully?

t.kraemer Thu, 07/09/2009 - 08:14
User Badges:

Seems to be a problem caused by an bulk import of these devices. Checking the last Device Discovery Summary, I could not find one of them.

I'm just wondering that CM works fine.

Joe Clarke Thu, 07/09/2009 - 10:12
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Data Collection works independently from the MDF. Hence Campus can properly show the device type, but there may be a problem with DCR, or with some other application. That is why I asked if RME was managing these switches.

t.kraemer Thu, 07/09/2009 - 22:51
User Badges:

Hi jclarke,


I think I found it. CW conntects these devices through NAT and I set an discovery filter, which excludes the real ip addresses.

It seems, that CSDiscovery apply the filter to the real and not the NAT adresses. Am I right with this assumption?

Actions

This Discussion