DFM 3.1.0 on LMS 3.1

Unanswered Question
Aug 3rd, 2009

Hi clarke,

Unable to pull devices from DCR CS 3.2.0 to DFM 3.1.0,In process always DFMServer is down and it is showing me 2 instance of DFMServer process i.e example DFMServer & DFMServer1 though when i restart it still get shutdown automatically.attaching the pdshow

Reply waiting for the solution.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Mon, 08/03/2009 - 08:24

This pdshow is truncated. Post the complete pdshow output along with the NMSROOT/objects/smarts/local/logs/DFM.log and DFM1.log.

lambay2000 Mon, 08/03/2009 - 08:34

when i execute a pdshow all outputs goes up in a window.Attached is the file.

there are many files in NMSROOT/objects/smarts/local/logs/ folder for DFM attached many pls refer which u need.

How can i send the full output of pdshow,what adjustment i have to do in command prompt window

Joe Clarke Mon, 08/03/2009 - 08:46

You should be redirecting the output of pdshow to a file. For example:

pdshow > pdshow.txt

The problem here appears to be corrupt DFM.rps files. Shutdown Daemon Manager, and remove the DFM.rps and DFM1.rps files under NMSROOT/objects/smarts/local/repos/icf. then restart Daemon Manager.

lambay2000 Mon, 08/03/2009 - 09:06


After removing those files i stopped and restarted the daemon but still there r no devices in DFM,

Do i have to do some extra job to pull from DCR.

LMS all processes takes 7 to 8 min to come up.


Joe Clarke Mon, 08/03/2009 - 09:12

The same DFM logs as before. The DFM.log and DFM1.log from NMSROOT/objects/smarts/local/logs.

Joe Clarke Mon, 08/03/2009 - 09:20

This is fine. You posted an old pdshow. DFM doesn't automatically manage devices by default. So, go to DFM > Device Management > Device Import, and make sure you have selected devices or groups to manage.

lambay2000 Mon, 08/03/2009 - 09:23


Nil devices are present in DFM to import i have cheked by auto as well as manual it says me there no devices to import.

Joe Clarke Mon, 08/03/2009 - 09:26

What do you see under DFM > Device Management > Discovery Status?

Joe Clarke Mon, 08/03/2009 - 09:35

Do you have any devices in DCR? Is this server integrated with ACS?

lambay2000 Mon, 08/03/2009 - 09:41

I have devices in DCR,RME pulled all the devices from the DCR but DFM is Not pulling i dont know what is problem.

Joe Clarke Mon, 08/03/2009 - 09:48

Shutdown Daemon Manager, then do the following:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmInv dmprefix=INV

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmFh dmprefix=FH

Then delete the NMSROOT/objects/smarts/local/repos/icf/DFM.rps and DFM1.rps files again. Restart Daemon Manager, and see if you can re-enable DCR auto-import by going to DFM > Device Management > Device Import > Auto Allocation, selecting "Enable AutoMode" and Manage All Devices, then click Apply.

lambay2000 Mon, 08/03/2009 - 09:58

It is gives me error it is not internal or external command.

LMS is in c:program files\cscopx

what i m doing is:

c:/program files/CSCOpx/bin/perl c:program files/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmInv dmprefix=INV

c:/program files/CSCOpx/bin/perl c:/program files/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM

c:/program files/CSCOpx/bin/perl c:/program files/CSCOpx/bin/dbRestoreOrig.pl dsn=dfmFh dmprefix=FH

Is it correct or any mistake.

Joe Clarke Mon, 08/03/2009 - 10:03

You must use DOS 8.3 file names with LMS. The commands will therefore be C:\\PROGRA~1\\CSCOpx\\bin\\perl C:\\PROGRA~1\\CSCOpx\\bin\\dbRestoreOrig.pl ...

lambay2000 Mon, 08/03/2009 - 10:05

C:\>cd program files/CSCOpx/bin/perl c:/program files/CSCOpx/bin/dbRestoreOrig.p

l dsn=dfmEpm dmprefix=EPM

The filename, directory name, or volume label syntax is incorrect.

AM getting this error can u guide me clarke where the mistake is

Joe Clarke Mon, 08/03/2009 - 10:14

I already provided you the correct command, and you are still using the long name. Again, the commands must start with:

C:\PROGRA~1\CSCOpx\bin\perl C:\PROGRA~1\CSCOpx\bin\dbRestoreOrig.pl

Joe Clarke Mon, 08/03/2009 - 10:38

Then I suggest you open a TAC service request at this point so live troubleshooting can be done.

lambay2000 Mon, 08/03/2009 - 12:25

Thanks clarke for back to back reply

appreciate ur immediate reply being cool and calm to explain,

But still i wanna ask when DCR discovers devices it should automatically discovered by DFM if auto allocation is enabled.And in manual allocation we have to import manually??? write

Then why it says no devices are selected to import.

1 question is when DFM is empty so we r importing it,,if devices are already present then what is the reason to import.

Still if u can find any solution it will good for me.

Once again thanks clarke.

Joe Clarke Mon, 08/03/2009 - 13:36

Yes, if auto-allocation is enabled in DFM, then any new device added to DCR should be automatically managed by DFM. Something is clearly broken on your server. More troubleshooting will be required to figure out where the problem lies. therefore, you should open a TAC service request so that debugging can be enabled, and log files can be analyzed.

lambay2000 Tue, 08/04/2009 - 13:21

Hey Clarke,

I wanna ask 1 question Which book i have to refer for deep troubleshooting LMS as such yesterday we perform

For example :delete DFM and DFM1 and reinitializing Database command,i was unaware of yesterday command where can i find deep troubleshooting documents for cisco LMS as am ahead of GMT +4,and you are located in US i have to wait for cisco experts response to login in netpro community.

Alternatively Wanna be like u a deep expert.


Joe Clarke Tue, 08/04/2009 - 13:49

There are no in depth troubleshooting documents for CiscoWorks which are externally available. All documents on log file analysis, and detailed architecture are generally not needed for customer use. The basic troubleshooting steps are posted in the various applications' user guides. For example, http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.1/user/guide/dfmfaq.html for DFM.


This Discussion