DFM.log grows up to 3 Giga in 3 Weeks

Answered Question

Hello,

im using cisco works on a windows server system  every 3 or 4 Weeks my backup fails because of  "no disk space".

Searching for the reason i found that DFM.log is too big. After removing  this file the backup runs propperly.

Removing this file needs to stop/start crmdmgtd.

Looking into DFM.log shows many lines of discovery output and i suppose it is the output of a debug command.

in DFM>configuration>logging  logging level configuration is not set.

Month ago i had a problem with DFM and got help from Cisco by an opend Case. i remember that during the work for

this case i was instructed to setup few  commands  like :

dmctl -s DFM put  ICF_TopologgyManager::ICF-TopologgyManager::DebugEnebled TRUE

Maybe i have to reverse  this commands, but not able tu use dmctl commands.

Correct Answer by yjdabear about 6 years 10 months ago

The good news is I don't think TopologyManager is impacted except needing to "Trigger the rediscovery of the device" for the change to take effect, according to the DFM documentation:


http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.1/user/guide/dfmfaq.html#wp1014252


So, go to NMSROOT/objects/smarts/bin

Execute the following command "dmctl -s DFM".

From the dmctl command line, enter:

1.
ICF_TopologyManager::ICF-TopologyManager::DebugEnabled FALSE
2.
ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress FALSE
3.
ICF_TopologyManager::ICF-TopologyManager::TraceRule FALSE
4.
ICF_TopologyManager::ICF-TopologyManager::DebugEnabled FALSE
5.
ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress FALSE
6.
ICF_TopologyManager::ICF-TopologyManager::TraceRule FALSE


Then trigger the rediscovery of the device to stop the growth of DFM.log

Correct Answer by yjdabear about 6 years 10 months ago

Can you elaborate on what you mean by "not able tu use dmctl commands"?


Could you not run the following command to reverse the debugging?


C:\Program Files\CSCOpx\objects\smarts\bin> dmctl -s DFM put ICF_TopologgyManager::ICF-TopologgyManager::DebugEnebled

FALSE


If so, what error messages did you get?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
yjdabear Mon, 04/19/2010 - 08:58

Can you elaborate on what you mean by "not able tu use dmctl commands"?


Could you not run the following command to reverse the debugging?


C:\Program Files\CSCOpx\objects\smarts\bin> dmctl -s DFM put ICF_TopologgyManager::ICF-TopologgyManager::DebugEnebled

FALSE


If so, what error messages did you get?

sorry, when i  wrote "i am not able" i wanted to say that i am not familiar with the usage of

the command dmctl. In my last posting i gave only an example of a command.

the full listing of the commands i have done is this:


1.      Enable the Discovery Logs.

Go to NMSROOT/objects/smarts/bin then execute the following command.

       dmctl -s DFM put ICF_TopologyManager::ICF-TopologyManager::DebugEnabled TRUE

       dmctl -s DFM put ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress TRUE

       dmctl -s DFM put ICF_TopologyManager::ICF-TopologyManager::TraceRule TRUE

       dmctl -s DFM1 put ICF_TopologyManager::ICF-TopologyManager::DebugEnabled TRUE

       dmctl -s DFM1 put ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress TRUE

       dmctl -s DFM1 put ICF_TopologyManager::ICF-TopologyManager::TraceRule TRUE


is it possible to set  all to  false  without  stopping the normal work of TopologyManager ?


thank you for your Help

Eberhard

Correct Answer
yjdabear Thu, 04/22/2010 - 10:32

The good news is I don't think TopologyManager is impacted except needing to "Trigger the rediscovery of the device" for the change to take effect, according to the DFM documentation:


http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.1/user/guide/dfmfaq.html#wp1014252


So, go to NMSROOT/objects/smarts/bin

Execute the following command "dmctl -s DFM".

From the dmctl command line, enter:

1.
ICF_TopologyManager::ICF-TopologyManager::DebugEnabled FALSE
2.
ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress FALSE
3.
ICF_TopologyManager::ICF-TopologyManager::TraceRule FALSE
4.
ICF_TopologyManager::ICF-TopologyManager::DebugEnabled FALSE
5.
ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress FALSE
6.
ICF_TopologyManager::ICF-TopologyManager::TraceRule FALSE


Then trigger the rediscovery of the device to stop the growth of DFM.log

Actions

This Discussion

Related Content