Device Type: UNKNOWN using CS and viewing devices

Unanswered Question
Apr 7th, 2009

I am having trouble with CS recognizing device types. I have over 330 devices in my database and some of them are showing up as unknown under device type. What causes this? The devices are mostly 1131 AP's but I have a 6513 that is showing up as unknown. Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Tue, 04/07/2009 - 10:50

Either your version of the Common Services MDF is out-of-date, or the devices have not been contacted via SNMP by another LMS application (e.g. Discovery, Campus Manager, RME, etc.). Once an LMS application is able to determine the sysObjectID of a device, it will update DCR with that information. Only then will DCR mark a device with its correct type.

stephenscott Tue, 04/07/2009 - 10:52

Thanks jclarke...is there a way to test SNMP connectivity to a device from CiscoWorks?

Joe Clarke Tue, 04/07/2009 - 11:01

You can do this from Device Center. You can do either Management Station to Device or try and do an SNMP Walk with a starting OID of "sysObjectID".

stephenscott Tue, 04/07/2009 - 12:21

SNMP looks like it passed...

Interface Test Results

Note: Protocol connectivity has been checked. Credentials for the protocol have not been tested. Interface Found: 172.x.x.x Status: UP ------------------------------------------------------------------------------------------ Test Results SNMPRv2c(Read) Okay sent: 5 recvd: 5 min: 0 max: 0 avg: 0 timeout: 2 min_size: 1472 protocol: snmpv3_get port: 0 SNMPWv2c(Write) Okay sent: 5 recvd: 5 min: 0 max: 0 avg: 0 timeout: 2 min_size: 1472 protocol: snmpv3_set port: 0

I can post the entire walk output if it would help. Thanks for your invaluable assistance.

Joe Clarke Tue, 04/07/2009 - 12:37

What are the sysObjectIDs from these unknown devices? Also, post NMSROOT/lib/classpath/com/cisco/nm/cwcs/mdf/mdfdata.xml .

stephenscott Tue, 04/07/2009 - 12:44

The following is a SNMP walk of device 172.x.x.x starting from sysObjectID

SNMP Walk Output

--------------------------------------------------------------------------------

sysObjectID

RFC1213-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::ciscoAIRAP1130

mdfdata.xml -> attached

Attachment: 
Joe Clarke Tue, 04/07/2009 - 12:51

This device is supported by the current MDF. Make sure the credentials in DCR are correct (i.e. that the SNMP community strings agree with what you tested), then add this device to RME, DFM, etc. It should soon be updated to show the proper type.

stephenscott Tue, 04/07/2009 - 13:36

Thanks jclarke,

I looked at the credentials and all seems right. I have a set of 16 AP's that are not working out of over 130. 9 are all on one subnet. the other 8 are on another subnet but i have some others on the subnet with the 8 that arent working that are working...is that confusing enough? I can not find anything out of sorts, but something obviously is...

All 9 on 172.16.110.x are not working

8 on 172.16.40.x are not working but 6 are.

stephenscott Tue, 04/07/2009 - 13:37

the subnet may not have anything to do with this problem...but i found it interesting.

Joe Clarke Tue, 04/07/2009 - 15:27

Then remove one of the unknown devices from DCR, and disable DCR auto-sync under RME > Admin > Device Management > Device Management Settings. Re-add the device to DCR. Then go to RME > Devices > Device Management > RME Devices, and manually add the device from DCR to RME. See if device moves to a known type.

stephenscott Tue, 04/07/2009 - 15:49

thanks j.

i tried the aforementioned process and no luck. the device type is still unknown.

Joe Clarke Tue, 04/07/2009 - 15:50

I suggest you open a TAC service request so additional debugging can be performed.

stephenscott Thu, 04/09/2009 - 09:47

One of the issues is that the SNMP requests were timing out. I fixed that. I still am having problems with LWAPP Access Points. Not really sure what is wrong there. Also MY ASA's, FWSM's, and ACS's are still showing as UNKNOWN. Any ideas for these?

Joe Clarke Thu, 04/09/2009 - 09:54

LWAPPs cannot be managed by LMS. They are not SNMP accessible. ACS cannot be managed by LMS (it's not a supported device).

The ASA and FWSM will work provided you configure SNMP correctly. In addition to specifying a community string, you need to allow the LMS server to poll them. For example, you need a command like the following:

snmp-server host inside 10.1.1.1 poll community public

And, of course, you need to make sure udp/161 is open between the LMS server and the devices.

Actions

This Discussion