LMS 4.0.1 - missing device model

Inventory jobs run successfully, but when running Inventory Detailed Device report, finding information missing under Chassis Model Name. Doing a MIB walk I do find Model name information is available under Standard Entitiy-MIB for the problem devices.
This is only occuring for Wireless AP 1200 (AIR-AP1232AG-A-K9) and select IOS Routers (870, 1811, and 1841). All other devices, except unsupported ones, are reporting properly.
I'm just a user of the system, but in talking with Administrators of the system - not finding the answer / cause / fix to resolve.
Is there something specific that needs to be set for these type of devices in order to pick up the model information?
Is there some update that would fix this?
Thanks in advance.

Due to issues at work, I have not been able to get back to this, but back now.
Here is a screen shot of the Missing Chassis Model Name information - also attached for readability;
Here is an excerpt of the ICServer.log that I believe is related to this;
com.cisco.nm.xms.xdi.DeviceAccessException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:258)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
Caused by:
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
Caused by:
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
com.cisco.nm.xms.xdi.DeviceAccessException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:258)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
Caused by:
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
Caused by:
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
at java.lang.Thread.run(Thread.java:662)
Let me know if there is anything else needed.
Thank you.

Similar Messages

Xen - device model: spawn failed

I have a Xen-based VM configuration which I've used without issue for well over a year. After running some updates and rebooting yesterday (either of which could be coincidental), the VM will no longer start:
# xl create leonids.xl.cfg
Parsing config from leonids.xl.cfg
libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited
It probably shouldn't matter, but here's the basic config which I pared down in an attempt to resolve this issue:
name = "vm1"
memory = 3072
vif = [ 'bridge=xenbr0' ]
disk = [
"phy:/dev/loop0p1,xvdb1,w"
builder = "hvm"
vnc = 1
vnclisten = '0.0.0.0'
vncdisplay = 1
And the loop device is created automatically by losetup after:
# modprobe loop max_parts=15
And I don't know if anything in this update would have caused it, but here's the pacman log anyway:
[2014-08-13 22:27] [PACMAN] Running 'pacman -Syu'
[2014-08-13 22:27] [PACMAN] synchronizing package lists
[2014-08-13 22:28] [PACMAN] starting full system upgrade
[2014-08-13 23:23] [PACMAN] upgraded bash (4.3.018-3 -> 4.3.022-1)
[2014-08-13 23:23] [PACMAN] upgraded chromium (36.0.1985.125-1 -> 36.0.1985.143-1)
[2014-08-13 23:23] [PACMAN] upgraded convertlit (1.8-6 -> 1.8-7)
[2014-08-13 23:23] [PACMAN] upgraded cracklib (2.9.0-2 -> 2.9.1-1)
[2014-08-13 23:23] [PACMAN] upgraded fakeroot (1.20-1 -> 1.20.1-1)
[2014-08-13 23:23] [PACMAN] upgraded gpgme (1.5.0-1 -> 1.5.1-1)
[2014-08-13 23:23] [PACMAN] upgraded kbd (2.0.1-1 -> 2.0.2-1)
[2014-08-13 23:23] [PACMAN] upgraded krb5 (1.12.1-1 -> 1.12.1-2)
[2014-08-13 23:23] [PACMAN] upgraded libiscsi (1.7.0-2 -> 1.12.0-1)
[2014-08-13 23:23] [PACMAN] upgraded libcacard (2.0.0-4 -> 2.1.0-2)
[2014-08-13 23:23] [PACMAN] upgraded libidn (1.28-2 -> 1.29-1)
[2014-08-13 23:23] [PACMAN] upgraded libmariadbclient (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:23] [PACMAN] upgraded xcb-proto (1.10-2 -> 1.11-1)
[2014-08-13 23:23] [PACMAN] upgraded libxcb (1.10-3 -> 1.11-1)
[2014-08-13 23:23] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-08-13 23:23] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Starting build: 3.16.0-2-ARCH
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> ERROR: file not found: `fsck.btrfs'
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: No fsck helpers found. fsck will not be run on boot.
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> Starting build: 3.16.0-2-ARCH
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-08-13 23:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-08-13 23:23] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-08-13 23:24] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-08-13 23:24] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-08-13 23:24] [PACMAN] upgraded linux (3.15.8-1 -> 3.16-2)
[2014-08-13 23:24] [PACMAN] upgraded lirc-utils (1:0.9.0-75 -> 1:0.9.0-76)
[2014-08-13 23:24] [PACMAN] upgraded mariadb-clients (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:24] [PACMAN] upgraded mariadb (10.0.12-2 -> 10.0.13-1)
[2014-08-13 23:24] [PACMAN] upgraded python-setuptools (1:5.4.2-1 -> 1:5.5.1-1)
[2014-08-13 23:24] [PACMAN] upgraded xfsprogs (3.2.0-1 -> 3.2.1-1)
Any ideas what may have caused this?

As an update, this problem occurs exclusively with loop devices, whether created automatically through the loop module or manually through kpartx.

ADF mobile: Reuse taskflows for different device models (resolutions) ?

Hi,
ADf 11.1.2.3.0 + mobile extension.
What's best practice to create the same mobile app for different device models (= different screen resolutions = different layout)?
I mean an app on a smartphone may use different gui components and layout than on a tablet device.
In adfmf-feature.xml the content of a feature can be either a amx page or a task flow.
Here I can add a constraint to determine e.g. the device.model and use different amx pages depending on the device model.
But how to reuse the task flow (assumtion: the taskflow is independent from the device model) and just create specific amx page per device model?
regards
Peter

Replying to an old thread.
With ADF Mobile 11.1.2.4.0, to display different content views for different devices, it is recommended that we use following property as a constraint on the content of the feature.
Property
Operator
Value
hardware.screen.diagonalSize
more
6
It applies this constraint on the devices which have screen size more than 6 inches. Which is applicable for the tablets.
For more details, look at the HR sample found at the following location in your JDev after installing the ADF Mobile Extension
jdev_install/jdeveloper/jdev/extensions/oracle.adf.mobile/Samples

Java.util.MissingResourceException: Missing device property

Hi all.
I've installed:
Sun Java Wireless Toolkit 2.5.2 for CLDC
Java Platform Micro Edition Software Development Kit 3.0 Early Access ( i suposed that it isn't necessarly)
JDK 6 Update 13
NetBeans IDE 6.5.1 (All)
After instalation i run WTK - > open sample project -> run and get this:
Warning: Could not start new emulator process:
java.util.MissingResourceException: Missing device property
Project is building without problems but i can't run it ;/ In NetBeans i have similiar problem i can't run sample projects because i have this:
Starting emulator in execution mode
com.sun.kvem.midletsuite.InvalidJadException: Reason = 22
The manifest or the application descriptor MUST contain the attribute: MIDlet-1
I've re-installed everything many times without windows :) I tried to search solutions for that but i couldn't find anything usefull.
I will be very apreciate for helping me.
Edited by: grubasek on Apr 1, 2009 3:29 AM
i have of course more partitions and WTK, NetBeans, ME SDK 3.0 are installed on other than C: but JDK is installed on C: in program files where in path is space. It has any meaning?

Did you figure this out? I've got exactly the same problem. Same error that is getting reported. The resource missing is the AMConfig.properties file which is required for the Access Manager Policy agent. Agent doesn't work until I get the WebSphere config correct.
Thanks in advance.

Numeric overflow in device model/Iteratiin limit reached Problem

I got this OTA project. We were building a tuning filter from 15kHz to 30kHz. I'm using 8th-order 1dB ripple Chebyshev low pass filter (See attachment for schematic). However, when I simulated it, sometimes works, sometimes doesn't. It either shows "Iteration limited reached" or "Numeric overflow in device model". How do I solve this type of probelm?
Thanks much.
Attachments:
1db Cheb OTA.ms12 ‏723 KB

Hello,
I have changed a few simulation custom settings to make your circuit run, basically lossening the restrictions on error calculation and iteration precision. Let me know if this fixed it for you. I'm using version 12.
Cheers,
Miguel V
National Instruments
Attachments:
1db Cheb OTA.ms12 ‏720 KB

LMS 4.2 Applications missing from Software Center

I have a problem with LMS 4.2.4 Software center on Win2K8. I have been trying to download device updates and the only product listed in software center has been:
Inventory Config And Image Management
It seems like this happened to me before and I opened a TAC case and got the list of products back but I can't seem to locate the case history. To top it off my LMS support contract is in limbo due to some administrative glitch and I am waiting for my account team to sort it out. Meanwhile I have just installed some relatively new products (3850, 4500-X) and LMS doesn't seem to recognize these completely.
The list of apps seems to be stored in the NMSROOT\lib\classpath\com\cisco\nm\xms\psu\conf\tag.properties. I stumbled accross a tag.pl script in the bin directory that modifies this file. So I searched in vain for the proper contents for the tag.properties file. In the end I just issued the following sequence to get common services back:
cd <NMSROOT>\lib\classpath\com\cisco\nm\xms\psu\conf
perl D:\Software\CSCOpx\bin\tag.pl tag.properties -a "cmf:Common Services"
So I am not sure why a perl script to modify the tag.properties file is necessary since it just seems to append the specified product to the end of the file. In any event I then went to
Admin > System > Software Center > Device Update
and sure enough CMF appears and I am able to check for and install device updates for it. However, I still seem to be unable to perform UT collection for the 3850 stack which is what I am really after. So does anyone know what product I need to add and get updates for in order to get user tracking working? In other words, what is the output of
psucli.bat -h?
Thanks,
-Jeff

Hi Jeff,
looks like tag.prop is corrupted.
it should have the below content :
ipm:IPSLA Performance Management
cmf:Common Services
lmsportal:LMS Portal
cvw:CiscoView
rme:Inventory Config And Image Management
dfm:Fault Management
lms:LAN Management Solution
upm:Device Performance Management
cm:Network Topology Layer 2 Services and User Tracking
Is this a new Installed ? if yes share the Installed.log
if you have good backup ,then try retstoring it.
Thanks-
Afroz

Ciscoworks LMS 3.0.1 RME devices management

Hello everyone,
I work with CW LMS 3.0.1 with the following product versions installed:
Products Installed
Showing 1-8 of 8 records
Product Name
Version With Patch Level
Installed Date
1.
CiscoWorks Common Services
3.1.1
02 Mar 2010, 10:34:04 CET
2.
Campus Manager
5.0.2
02 Mar 2010, 10:34:05 CET
3.
CiscoView
6.1.7
02 Mar 2010, 10:34:10 CET
4.
CiscoWorks Assistant
1.0.1
02 Mar 2010, 10:34:10 CET
5.
Device Fault Manager
3.0.5
02 Mar 2010, 14:55:12 CET
6.
Internetwork Performance Monitor
4.0.1
02 Mar 2010, 10:34:14 CET
7.
LMS Portal
1.0.1
02 Mar 2010, 10:34:17 CET
8.
Resource Manager Essentials
4.1.1
02 Mar 2010, 10:34:18 CET
Many Thanks in advance,
LucaI verified that RME has a license to support 1500 devices while the devices discovered by RME are about 1600.
Many of these devices have now been eliminated from the Network (around 200) and I want to know if there is a way to automatically remove them from CW or if I must remove them manually step by step.

In LMS 3.0.1, you must remove them manually. LMS 3.2 has a feature which can poll devices in DCR, then generate a report for those which are no longer reachable. That will then facilitate removing those devices.

Missing device registration info

After the infamous security breach of Sony's "secure" network, my device info I had registered last January is now missing. Looks like a reset of information. Also, I wasn't prompted to change my password when I logged into the Sony site as mentioned in the updated press release on Sony's site. I had to manually change my password; The issue I also have with the their passwords is I can't use special characters! Less secure in my book.

Thank you for your post.
There is further detail regarding this issue in a statement released on the PSN Blogs yesterday (5/4):
http://blog.us.playstation.com/2011/05/ ... entatives/
Keep your eye on the PSN blog for the latest up to date info on the status of the network:
http://blog.us.playstation.com
To keep current on the latest news and further updates with the Sony Online Entertainment network please visit here :
http://www.soe.com/securityupdate

LMS 4.2 Fault Monitor - Device Name and Frequency of Events

Hi all,
I've just installed LMS 4.2, like it a lot so far. But I'm running into a few problems, and I'm hoping someone out here has a suggestion.
In the Fault Monitor, the Device Name column shows the device's IP address rather than the host name. We need for it to show the host name, for ease of troubleshooting; most folks don't have the IP addresses memorized. Likewise, when an email is sent out for an event, the managed device field also shows up as the device's IP address.
The devices were all discovered with their IP addresses rather than a host name...should LMS have automatically found their host names? Regardless, I manually updated all of the device's host names, yet they still display as an IP address in the fault monitor.
Also, it appears I need to figure out some way to throttle alerts. One particular device will report an event (ie a temperature out of range) dozens of times in a polling period...several per second, even though it's the same alert. Any suggestions on where I can throttle this? My inbox is exploding.
If anyone has any ideas, I would appreciate it!
Jen

I am having the IP vs. device name issue as well. The funny thing is if you hover over the IP of the device in Fault Monitor, you can see the device name listed. I was on a conference call with Cisco recently and pointed this out. One of the reps said the faults and alerts showing IP address issue should be fixed in version 4.2.3, but I don't know if he was basing this on first-hand knowledge or was just assuming. Does anyone know if this is the case?
As for throttling alerts. I had a false positive alert from a device that I put in a custom fault group and changed the threshold on to keep them from firing. You probably have already resolved this issue, but I didn't see a resolution listed here. You would have to determine if raising a threshold for a device is adequate for your situation.
Thank you,
Mark

CiscoWorks LMS 4.0.1 and devices other than Cisco.

Hello.
Can I use some CiscoWorks LMS functions like config management, topology, with devices other than Cisco?
Thanks.
Andrea

No, RME, Campus and DFM are still hardcoded to restrict to cisco devices.
HUM and IPSLA are more open.
The functionality from the HUM will allow you to monitor availablilty, interfaces and you can add OID's yourself.
IPSLA can use non cisco devices as a target for their tests.
Cheers,
Michel

Missing device link /dev/eth0

I just recently did an FTP install of base Archlinux. I smoothly transfered to udev with not problems.etc.etc. When I finally installed Xorg and the Xfce4 WM and some plugins. IE netload. I found that my /dev/eth0 device link was missing or uncreated. Now my problem is I don't know how the hell to make the link to the device, I researched it and found that /dev/eth0 is virtually linked to the kernel modules somehow. Yet I didn't find a way to create it. So can anyone help?

Other distro's dont have /dev/eth0.
It doesnt exist and never will.
What plugin is this you speak about? what are you trying to do?

Missing Device Manager Items

Any chance someone can tell me what "Base System Device" driver(s) are missing and where to get it from these
hardware id's? The machine is a Envy 810-170st.
PCI\VEN_8086&DEV_0EE3&SUBSYS_2ACE103C&REV_04
PCI\VEN_8086&DEV_0EE3&SUBSYS_2ACE103C
PCI\VEN_8086&DEV_0EE3&CC_088000
PCI\VEN_8086&DEV_0EE3&CC_0880
Thank you!
This question was solved.
View Solution.

Mario,
There are 4 drivers under the Driver - Chipset (4) link.
Do you want me to install the "Intel Management Engine Interface Driver" or one of the others?
Ron

Macbook pro 17" 2.6ghz missing device

I've got a missing USB device when I do an install on a newer (non penryn) Macbook pro.
I'm also getting my Isight showing up routinely as a "USB video device" and/or being unrecognized... and every now and then my USB starts beeping on and off saying I've got stuff hooked up as 1.0 instead of 2.0 (even if I don't have anything hooked up)
I'm running the 2.0 Boot Camp off the install disks.
BTW... how does apple release driver updates for Boot Camp?
-=JEff

Apple drivers will be available by running Apple Update under Windows, the same way you would update the Windows version of iTunes.

Missing Device Backups in iTunes

After a new installation of Lion I restored iTunes from Time Machine. For some reason none of my Device backups are showing in the preferences pane. Any recommendations on how I can find the missing files in Time Machine and restore them to iTunes would be appreciated.

It only appears when a device is connected. If you have a device connected and it is not recognized, the following may help:
Windows computer: http://support.apple.com/kb/TS1538
Mac: http://support.apple.com/kb/TS1591

"Missing" device not missing

For one of our clients the OnPlus agent is installed and has been working great for 6+ months. A week back one of the switches went "missing", on checking the dvice its pingable, appears in cdp tables and is physically there and up.
We tried removing it and re scannign for it, but it didnt appear. We finally had to manually add it just so it would appear
On some further checking, the portal and the agent seem to have a missmatch in information the Portal shows the agent is FW version 35.46 and the Box itself (connected via the portal) show the latest version (37.59), the box is ON100-K9 v02. We had a similar FW missmatch at one of our other sites, that has a V01, but put this down to a hardwasre issue, the FW rectified itself over christmas break, and i'm pretty sure while that was going on the box we are talking about was showing it had the 37.59 version.
Bearing in mind that everything was fine untill a week ago, and all the other devices are running fine,anyone have any ideas how we can get the switch back without having to kill the box and start again?

Peter,
Can you send me a PM or email me at [email protected] with the agent and customer names. There seems to be something odd going on with this site. I'd like to investigate both the sistuation with the device sticking on an old version, and with this invisible switch.
FWIW, the next release of the firmware should rationalize this "37.59" version number, which is really and internal value and not readily translatable to the published releases. The new version should look something like "7.7.2.123". The "7.7" is the release revision, the "2" indicates this is production firmware for the device, and the "123" is the build number. This value should match the device's login splash page.

LMS 4.0.1 - missing device model

Similar Messages

Maybe you are looking for