Couldn't find the devices in my ciscoworks

Unanswered Question
Oct 21st, 2008

ESS Monitor running normally, with message "ESS is fully up now". But in DFM status, some devices are learning and questioned. Before this everything is OK, I have 800 devices, suddenly only 2 device with status known. I tried to fix (rediscover), right know there are 9 device questioned and 5 learning. There is some devices in status lerning/questioned. But I couldn't find the devices in my ciscoworks. How it could be?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Tue, 10/21/2008 - 09:34

What version of DFM is this? Is this LMS server integrated with ACS?

Joe Clarke Tue, 10/21/2008 - 16:54

Before doing anything else, you'll want to upgrade to LMS 3.0.1 then DFM 3.0.3. This will fix a known bug where devices may hang at 10%. After that, there is one other patch on you will need to apply to prevent your devices from hanging at 40% or slipping into a Questioned state.

LMS 3.0.1 can be downloaded from . DFM 3.0.3 can be obtained from Common Services > Software Center > Software Update once you have LMS 3.0.1 installed. The final patch you'll need to apply is for CSCsi01966, and it can be downloaded from .

riko.arizona Tue, 10/21/2008 - 18:03

"This will fix a known bug where devices may hang at 10%". Cisco device hang or device lists may hang in LMS?

Joe Clarke Tue, 10/21/2008 - 21:24

Devices may hang in a learning state at 10% within DFM prior to DFM 3.0.3.

riko.arizona Tue, 10/21/2008 - 21:49

When I want to upgrade to DFM 3.0.3, is it will impact to production devices?

I still confused about your statement, devices may hang in a learning state. What kind of devices? devices in DFM list or cisco devices (appliances)?

Joe Clarke Tue, 10/21/2008 - 21:56

No, the upgrade will not have an impact on production devices. DFM 3.0.3 is a bug fix and new device support release.

Within DFM, devices can be in either a Known, Learning, Questioned, or Pending state. There is a bug in all versions of DFM 3.0 prior to 3.0.3 where devices do not go into a Known state. Instead, they hang in Learning. If you go to DFM > Device Management > Rediscover/Delete, the discovery progress is stopped at 10%.

On top of that, there is another bug (still present in 3.0.3, but fixed with a patch) where devices may hang at 40%, or drop into a Questioned state.

riko.arizona Wed, 10/22/2008 - 20:58

You said the upgrade will not have an impact on production devices, how about the ACS? Because my LMS Server has integrated to ACS. Any impact with ACS?

How long that upgrade process take a time? If I upgrade the LMS, how about the other LMS element (CM, DFM, CS, RME), still running with existing configuration?

Joe Clarke Wed, 10/22/2008 - 21:00

There will be an impact on the LMS tasks registered with ACS. The LMS 3.0.1 upgrade does add some new tasks, so these will need to be reregistered with ACS. The upgrade can take up to about two hours depending on whether or not you choose to install the new Health and Utilization Monitor add-on, and the specs on the server. While the upgrade is running, all applications will be unusable.

riko.arizona Thu, 10/23/2008 - 02:02

How about user profile in LMS, is it changed? and how about topology, should I rebuild again or the topology still like existing configuration?

riko.arizona Mon, 11/17/2008 - 20:21

I Have upgrade from LMS 3.0 to LMS 3.0.1. When Installation process, I didn't choose register aplication with ACS Server. That's why I can't access Discover device page from CS Menu. I want to register with ACS now, how to do it? Should I click CiscoWorks_LMS_3.0_Dec_2007_Update.exe again and for the ACS Mode, I choose "Yes"?

Joe Clarke Mon, 11/17/2008 - 22:32

No. You can simply go to Common Services > Server > Security > AAA Mode Setup, and check the box to register all installed applications, then re-integrate with ACS.

riko.arizona Mon, 11/17/2008 - 23:55

How about the devices in ACS, should I re-input one by one? or just check the box to register all installed applications

Joe Clarke Tue, 11/18/2008 - 09:03

If you were previously integrated with ACS, then the device should still be in there. If not, you will need to add all of the devices you wish to manage with LMS into the ACS server. You will then need to setup your LMS user accounts in ACS to have access to those devices.

It is not sufficient to simply re-register LMS with ACS to get device access.

riko.arizona Wed, 11/19/2008 - 01:19

I have integrated with ACS. But in ACS it shows error message : "service=CM authorize-device= cmd"Schedule_dev_discovery".

I think for discovery has moved to CS menu. How to fix it? And in ACS (for IPM) only for heldesk level, can't change to the other levels

Joe Clarke Wed, 11/19/2008 - 09:13

Yes, Discovery is now part of CS. To fix these problems, you need to re-register your applications with ACS. That should address both issues.


This Discussion