UTU 1.1.1 acquisition problem

Unanswered Question
Mar 16th, 2007
User Badges:

Windows 2000 Prof.

CM 4.0.5

UTU 1.1.1

The UT acquisition status is permanent running, but UT End Host Report is not actual.

Any suggestions?

Best regards,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 03/16/2007 - 09:27
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This could be due to any number of things, but it is most likely caused by IP to hostname resolution. The ut.log with vmpsadmin debugging enabled will say for certain. To enable vmpsadmin debugging, go to Campus Manager > Admin > Campus Data Collection > Debugging Options, and add the vmpsadmin module. Then restart dmgtd to get UTM to stop. Then run another full acquisition. When you think it should have stopped (i.e. when it's been running far longer than it should), look at the ut.log to see what UT is doing.

If the problem is name resolution related, the solution will be to upgrade to LMS 2.6 (i.e. CM 4.0.6 or higher). In that version we introduced a new property that bypasses OS-based hostname resolution which can really speed up UT on Windows.

amdil Wed, 03/21/2007 - 02:16
User Badges:

Thanks for answer but when I turn on debugging ANI server has status "ANI server is still initializing".

Computer restart didn't solve this issue.

Best Regards,


stevejhale Wed, 03/21/2007 - 02:28
User Badges:

I had this also, I got it going by killing the UT process in Common Services then starting it again, try reviewing the UTlog status this usually throws up some clues, I found a lot of layer2 devices in Campus Manager that did not tie in to my Common services removinbg these also speeded things up. lastly set some debug options on the UTlog, I will try to find my notes for what to debug.. Also 4.0.8 seems more solid.

Joe Clarke Wed, 03/21/2007 - 08:51
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Check the ani.log and ANIServer.log for potential errors as to why ANI is not fully initializing. Note: you may also just need to wait a bit longer. It generally takes about 20 minutes for all the daemons to settle when dmgtd is restarted.


This Discussion