Unknown Device Type in CM

My Campus Manager is not properly identifying one of my switches. The device is a Catalyst 3548 running 12.0(5.2):
Whitesnake#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5.2)XU, MAINTENANCE INTERIM SOFTWARE
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 17-Jul-00 18:29 by ayounes
Image text-base: 0x00003000, data-base: 0x00301F3C
ROM: Bootstrap program is C3500XL boot loader
Whitesnake uptime is 5 weeks, 4 days, 18 hours, 2 minutes
System returned to ROM by power-on
System image file is "flash:c3500XL-c3h2s-mz-120.5.2-XU.bin"
cisco WS-C3548-XL (PowerPC403) processor (revision 0x01) with 16384K/1024K bytes of memory.
Processor board ID FAA0423J10S, with hardware revision 0x00
Last reset from power-on
Management station to device reports it is reachable for both telnet and snmp read and write. snmpwalk of sysbjectID reports:
The following is a SNMP walk of device 10.10.96.7 starting from sysObjectID
SNMP Walk Output
sysObjectID
RFC1213-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::cat3548XL
or, with numercial output chosen:
The following is a SNMP walk of device 10.10.96.7 starting from sysObjectID
SNMP Walk Output
sysObjectID
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.9.1.278
The Supported Device Table indicates that this sysObjectID is supported.
I am running everything at the latest patch levels. Specifically, my CM is Version 5.2.1 and my CM Devcice Package is 6.0. Yet, the device remains"unknown":

The most common error for unknown devices is the SNMP community string not being set correctly. Verify that its showing up correctly under the Common Services ---> Devices and Credential Management --->Device Management --> Expand All Devices and search for the problematic device and update the credential and snmp RO and RW community strings.
Then re-run data collection and launch topology services.
If the above steps does not work, get the following information.
1. Enable debug from data collection under Campus Manager ---> Administration ---> Debugging Options --> Data Collection and select the "topo module". Also enable Debug under Campus Manager ---> Administration --> Debugging Options --> Topology and change Debug level to "trace".
2. Start a new data collection.
3. Launch Topology Map again.
4. Upload the ani.log file from CSCOpx/log/ani.log
5. From the Java Console, copy and paste the outputs to a text file.
-nael

Similar Messages

  • Unknown Device Type in LMS v3.1

    I have quite a number unknown devices registered under CS. How do I add new packages into LMS v3.1 so that these devices can be discovered correctly?

    Download  and install the latest mdf package from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-cd-one available for your version of Common Services. Also double check (by snmpwalk with oid=.1.3.6.1.2.1.1.2) that devices are really supported in LMS 3.1

  • Device Type "Unkown"

    All,
      I am in the process of configuring a new 5508 WLC and five 3702I APs.  Looking at the Client Monitoring page I can see all the client associated with the APs but The Device Type says “Unknown.”
    Is there anything that can be done to change/resolve the “Unknown” Device Type?  Thanks for the assistance!
      Dave

    Enable HTTP Profiling and RADIUS Profiling under the SSID > Advanced tab.  
    Sometimes, it will be able to identify what kind of machine and generic OS, like "Apple OS" or "Windows 7".  Won't be able to determine, for example, if your Andriod is running what firmware.

  • Unknown Device Event Type from a router

    Hi,
    I just included my first router within the reporting devices and decided to take a look at the raw events coming in to the MARS. To my surprise I see just two types of events :
    - Generic IOS syslog
    - Unknown Device Event Type
    This second one looks like SNMP because every message begins with "SNMPv2-SMI::enterprises." and seems to contain OIDs and data. Is this normal or am I having some kind of problem? The syslog messages seem to be interpreted correctly; in fact they generated a few incidents when there were some problems on one of the interfaces. I'm worried that the SNMP messages (traps?) are not being understood.
    Thanks for your help,
    Joe

    Yes, I realize that. Unfortunately I don't have access to the router and I'll have to ask what has been configured. I was wondering why MARS sees this data as raw events, if indeed they are SNMP traps. Does MARS listen on port 162 UDP?
    Thanks,
    Joe

  • Unknown Device Event Type Adobe?

    Starting yesterday I have about 60 notifications that state "Unknown Device Event Type" and the packet was dropped inline. The majority of the Raw message starts out with....P...L...E.... and has ...Adobe..d...in the message body. Maybe Adobe sent out an update that is causing this? Different Source, Destinations and Ports in the notifications. No virus or spyware on the network that I can find.

    They're apparently IPS alarms? Take a look at the raw message and it should tell you the signature ID. Then look that up on mySDN.
    http://tools.cisco.com/MySDN/Intelligence/searchSignatures.x

  • CUOM - Call Manager unknown MDF device type

    Hi All,
    When i added the CUCM in Operation manager , device type shown as "Unkonwn".
    We tried with remove the add it again. Restart with Server & service. NO GO
    Suspecting the beloe Bug. Is any workaround for this.
    CSCsd58055
    The Devices report may show a device's capability as UnknownMDFType.
    The Devices report displays a device's capability as UnknownMDFType, if the device is not supported by Operations Manager.
    Workaround:
    None.
    Thanks,
    Sriram.P

    Hi Sriram,
    You should try posting this in the Bug Discussion portion of CSC
    https://supportforums.cisco.com/community/netpro/online_tools/bugs?view=all
    Cheers!
    Rob
    "Show a little faith, there's magic in the night" - Springsteen

  • Windows needs to install driver software for your unknown device

    Windows needs to install driver software for your unknown device
    This is the message that i get when ever i plug in my ipod touch to my computer. the computer is running on vista. i dont know what to do, because i tried to follow the steps suggested, but it didnt work, the computer said that it couldnt find anything and to check with apple for some driver software. HELP!!!

    The iPod touch and iPhone do not use the same type of USB drivers that other Apple devices use. They both require Apple Mobile Device Services to be running. Using this tech article as a guide, you can easily fix this: http://support.apple.com/kb/TS1567

  • Satellite P775-S7320 Unknown Device issue

    Unknown Device
    Device Type:     Universal Serial Bus controllers
    Manufacturer:    (Standard USB Host Controller)
    Location:            Port_#0002.Hub_#0004
    Windows has stopped this device because it has reported problems. (Code 43)
    I'm trying to figure out what this device is before I open the laptop and start poking around.
    Any info would help, thanks in advance.

    I can remove all external USB devices and the issue still exists. The internal webcam is USB and working fine, so is the toutchpad but also working fine. I suspect another internal USB device, but I have no idea what else is USB. I don't use the WiDi and wondering if that is considered an internal USB connected device.

  • Unknown devices z60m

    Unknown device on other Devices
    FN+ Hibernate not working
    Fn+ Easy Eject Not working
    Solved!
    Go to Solution.

    Hi sajimathew,
    Could you please provide some more info about your computer and OS like what Windows version do you use and is it 32 or 64 bit? What is the model/type of your z60m? You should find a sticker under the computer in the format "xxxx-yyy" where the X is 4 numbers and the Y is numbers and letters (for example 4328-3EG). Do NOT post your serial number in public, i'm only asking for the model number.
    Did you clean install Windows using a standard windows installation CD/DVD or did you use a Lenovo recovery CD/DVD set?
    For the Fn + function key to work you need to install the hotkey features software. The other unknown devices is probably some missing drivers because you did a clean install.
    I would recommend that you download Lenovo system update that will give you a list of drivers and lenovo software for your computer and it will give you the option to download and install all the drivers as well as other Lenovo software. That will save you a lot of time and work compared to downloading and installing each driver manually. You also have the option to deselect a driver or lenovo software if you don't want everything.
    http://www-307.ibm.com/pc/support/site.wss/tvsu-update.html
    Version 4.0 is for Windows 7 only while 3.14 is for XP and Vista. After using system update and if there still are some missing drivers or features that won't work you could reply to this thead asking for further help. In case of missing drivers it's helpful if you include the hardware ID which you can find by doubleclicking the device in device manager, select the details tab and select hardware IDs from the dropdown box.
    -gan

  • HP Pavilion TS 14: Unknown Device (Windows 8.1)

    Just wanted to share my experience after reformatting my brand new HP Pavilion TS 14.
    - it came with Windows 8, but do not like all the bloat that comes with OEM installed OSes.
    - backed everything up, and reformatted.
    Now.. i was able to find most of the drivers on HP's website for the specific model.
    - except for 1.
    Unknown Device
    ACPI\VEN_ASD&DEV_0001
    ACPI\ASD0001
    *ASD0001
    i actually found a post on here and the expert said it was related to Graphics.
    - but i installed all of AMD drivers & Software.
    - i even updated via Windows Update.
    Googling was  not fruitful, as this specific model is either too new or not popular.
    But eventually did find it.
    Device type: System devices
    Manufacturer: AMD (ATI)
    Provider: Advanced Mirco Devices, Inc
    Version: 1.1.0.0017
    Date: 2013-02-07
    Operation Systems: Windows 8, Windows 8 (64bit)
    File size: 57.5 KB
    Download: http://www.magicdriver.com/driver92740-ver_1.1.0.0​017.html
    Note: it says Windows 8.. but it's compatible with Windows 8.1 also.
    My Specs:
    HP Pavilion TouchSmart 14
    Windows 8.1 x64
    AMD Catalyst 13.12 (latest WHQL)
    I am NOT an HP employee.

    Hi, This Solved the same problems with my HP 15-d074nr.
    I had to download the file, but it was in .rar- extension so i had to rename to .rar and unrar in a folder a manually instal via device manager.
    BBbut i Worked Great afte hours googling.
    Thanks Bro

  • MSI K8N Neo4 Platinum "Unknown Flash Type" at boot

    I get a unknown flash type error at start up. Also a OS Loading error and just hangs there. If I hard boot/ F11/ choose boot disc as my 160gig seagate ATA drive the OS loads. I don't want to have to boot this way everytime I start up. Any Ideas?
    Mike

    Kept get various blue screens-never the same one. Decided it was some kind of viris or bad boot drive. Replaced old drive-did total reinstall of OS. Installed all drivers for the motherboard from the supplied driver disc- there are NO yellow ? marks on any of the devices or controller in Device manager.

  • Unsupported device type

    After a power outage OSB has lost the ability to use two of its three tapes drives. I've hard rebooted the library. I've pulled the power cord on the library. The OSB server has been rebooted multiple times. I've tried putting the drives out of service and bringing them back up. When going to the Configure -> Device - Tape2 (or Tape3) I see this message at the top of the screen/
    no hardware info is available for drive tape2 - unsupported device type (not tape or library)
    no hardware info is available for drive tape3 - unsupported device type (not tape or library)
    Transcripts of jobs show these errors:
    Error: can't open device tape3 - device file not found (OB scsi device driver)
    Error: can't open device tape2 - unsupported device type (not tape or library) (OB scsi device driver)
    I'm not sure what to do. All the tape drives are the same so obviously the drivers exist. How do I get these drives working again?
    Thanks.

    What OS are you running?
    It sounds like the device attach points have moved. If this is a Linux system then you can do "obtool lsdev -l" to see what /dev/sg entry your devices are looking at, and then do "sg_map -x -i" to see what /dev/sg your devices are really using. Then you can update the device attach points to point to the correct entry using "obtool chdev -a"
    For example :
    obtool lsdev -l
    Drive0:
    Device type: tape
    Model: [none]
    Serial number: 882E70020M
    In service: yes
    Library: L700
    DTE: 1
    Automount: yes
    Query frequency: [undetermined]
    Debug mode: no
    Blocking factor: 512
    Max blocking factor: 512
    Current tape: [unknown]
    Use list: all
    Drive usage: 2 months, 1 week
    Cleaning required: no
    UUID: dddc4eaa-f143-102b-b28c-001ec9b5e6ee
    Attachment 1:
    Host: dukdaa01
    Raw device: /dev/sg2
    sg_map -x -i
    /dev/sg0 0 0 32 0 13 DP BACKPLANE 1.05
    /dev/sg1 0 2 0 0 0 /dev/sda DELL PERC 6/i 1.22
    /dev/sg2 1 0 0 0 5 /dev/scd0 TEAC DVD-ROM DV28EV D.AE
    /dev/sg3 3 0 0 1 1 /dev/nst0 IBM ULTRIUM-TD2 333K
    obtool chdev -a dukdaa01:/dev/sg3 Drive0
    Thanks
    Rich

  • ThinkPad Yoga S1 - Windows 10 unknown device

    I did a clean installation of Windows 10 on my ThinkPad Yoga S1. After onstalling all drivers I still get followig device missing in device manager:
    Unknown Device:Device Type: other devicesManufacturer: unknownPlace: Synaptics SMBus Driver I already installed Synaptics ThinkPad UltraNav Driver 19.0.12.61 from 7/30/2015, so this does not change anything here. What driver is missing and can Lenovo provide it soon?

    Also have an S1 with non-functioning palm rejection. The pen worked earlier, but now it no longer functions. It works in that it can calibrate itself in Wacom Pen settings, but otherwise refuses to register. UPDATE: restoring default settings under Wacom Pen settings has reenabled the pen and palm rejection appears to work again. Note: I installed recent Wacom FEEL drivers, which are the drivers that work with this model, among other tablet PCs with Wacom tech.

  • First boot fails - Filesystem type unknown, partition type 0x7

    Just done a straight forward install of Arch onto it's own disk drive, however there are two other drives present in the system.
    Grub menu comes up ok but then Arch errors with:
    root (hd2,0)
    Filesystem type unknown, partition type 0x7
    Error 17: Cannot mount selected partition
    Any suggestions?
    Thanks,

    hokasch wrote:
    What you still did not really tell us - how are you booting up? I.e. where is your first grub stage installed? How did you manage things with the debian install? Your problem is the root(x,x) line, not the kernel line. This line specifies the boot partition (grub's root/ where to find the kernel).
    Coming from the windows world where for years we have just relied on changing the boot order of drives in the BIOS to choose which MBR to boot from I simply assumed it was just as easy in the Linux world, this is obviously not the case.
    If you want to continue that way, just install grub to the MBR of each disk with a linux install and configure grub to use that drive as the first drive (e.g. set the root line to hd(0,0) if /boot is the first partition). IIRC, changing the boot order in the Bios will pull the selected drive to the beginning. That would fit your inital error (but you did not say how you booted into grub then...). You can double-check that behaviour by using the find commands in the grub shell (see my earlier post).
    Going with grub2/grub's root by uuid only really makes sense if you put grub2 on the MBR of a drive which is always installed and selected as primary in Bios (obviously, all other grub2 files must be on that drive too).
    Just done another completely clean install and noticed that even though I select 'Partition access method - uuid' it doesn't seem to actually work that way, at least checking menu.lst showed no signs of any uuids.  What is the point of having an install option if it is then ignored.
    This refers to your fstab, not the bootloader config.
    Sorry hokasch, it got a bit difficult to answer your earlier post as by the time I read it Debian had been trashed and I think I had redone the Arch install a few times by then as well.
    If I have understand you correctly what you are saying is that if I were to install arch on a drive which at install time is the only drive in the machine then root(x,x) would refer to hd0 in my case root (hd0,1) as I have an NTFS partition at the beginning of the drive.  Alternatively I could just edit grub's menu.lst afterwards.  That way as long as the drive is first in the BIOS boot order it will boot ok.  My mistake seems to have been trying to install the first grub stage to somewhere other than the MBR, I may have missunderstood the capabilities of partition identification by uuid.
    Ok lets go back to a single drive environment
    hd0,0 = NTFS boot partition
    hd0,1 = Arch /Boot - this contains grub & vmlinuz-linux
    hd0,2 = Arch swap
    hd0,3 = Arch /
    If I want to boot Windows I set hd0,0 as active/bootable, if I want to boot arch I set hd0,1 as active/bootable.  Actually not sure how to change the active partition to a linux one but come back to that later.  For the moment hd0,1 is the bootable partition.  This is the only drive in the system.  I have a by-uuid entry in menu.lst which allows me to boot if the other entries fail.  menu.lst looks like this:
    # (0) Arch Linux
    title Arch Linux
    root (hd0,1)
    kernel /vmlinuz-linux root=/dev/sda4 ro
    initrd /initramfs-linux.img
    Now I see part of the confusion, as you advised, the root (hdx,x) line actually refers to the 'grub root' / 'linux boot' not the 'linux root'.  And the other confusion is that the kernel line root= does not refer to the location of /vmlinuz-linux but to the actual linux root.  Now I think I understand that bit.
    Now to add another disk to the system.  Change drive order in BIOS so that arch disk is top of the boot order.
    Fails to boot: Unable to find root device /dev/sda4!
    Boot to knoppix to see the disk & partition layout:
    hd0,0 = NTFS
    hd0,1 = NTFS
    hd0,2 = NTFS
    hd0,3 = NTFS
    hd0,4 = NTFS
    hd0,4 = NTFS
    hd0,4 = NTFS
    hd1,0 = NTFS boot partition
    hd1,1 = Arch /Boot - this contains grub & vmlinuz-linux
    hd1,2 = Arch swap
    hd1,3 = Arch /
    So clearly /dev/sda4 is now an NTFS partition.
    If appears that grub & linux do not see disk drives in the same order as the BIOS boot order causing /dev/sda4 to point towards the wrong partition.
    Off at a bit of a tangent here but while I think of it is there a way of regenerating the menu.lst to search for instances of windows on NTFS partitions now that I have access to ntfs-3g.
    Thanks,
    Last edited by NickC_UK (2012-02-21 14:25:04)

  • Firewire Bus/Unknown Device?

    Hello to all. I just picked up a New 2.3GHz Power Mac and when I was checking the System Profiler in the Firewire section it reads Firewire Bus
    Unknown Device
    FireWire Bus:
    Maximum Speed: Up to 800 Mb/sec
    Unknown Device:
    Manufacturer: Unknown
    Model: Unknown Device
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    The funny thing is I have nothing plugged into any of the Firewire Ports! The other strange thing is I have a 20 inch Cinema Display (which has a USB and Firewire Hub built into the back of the display) and If I plug that Firewire plug into the Computer I get a Duplicate reading of the info above (looks like this):
    FireWire Bus:
    Maximum Speed: Up to 800 Mb/sec
    Unknown Device:
    Manufacturer: Unknown
    Model: Unknown Device
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Unknown Device:
    Manufacturer: Unknown
    Model: Unknown Device
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    I called Apple and They had me run every test under the sun. As a last resort They had me erase the Drive and do a reinstall of just the basic Apple Software and this is what I ended up with. I thought maybe one of you kind folks might have some idea of what the **** is going on.
    Thanks
    Michael
    Dual-Core 2.3GHz PowerPC G5   Mac OS X (10.4.6)   2.5 GB DDR2 SDRAM

    Thanks so much for your replies. So what is the technical explaination for this because I have been on the phone with Apple for hours over the last 2 days send them all sorts of system data. I even mentioned the fact that I have seen postings listed on this forum with other people with the same Unkown Error issue happening to there Dual Core machines and the people I have spoken with at Apple are acting like the have never heard of this before. I only noticed this Unknown Device thing because I am in the Audio Recording business and I am having a problem with my Digidesign DIGI002 interface giving me this slight distortion problem coming out of the 002 unit. But this was happening when I had the 002 connected to my Powerbook 17inch 1.33. I figured it was some type of software issue but now I'm checking into the 002 as the culprit! And the people down at Digidesign have never heard about this Unknown Device Issue as well and think that could be messing up the 002 but I do not have this Unknown Device thing going on with my Powerbook. So I'm stumped!
    Thanks again!
    Michael
    Dual-Core 2.3GHz PowerPC G5   Mac OS X (10.4.6)   2.5 GB DDR2 SDRAM

Maybe you are looking for