Why does Template compliance check or deploy take so long?

Unanswered Question
Jun 23rd, 2008

I need to know more about the steps and process that RME takes when you run a simple compliancy check. I ran a check against 600 content engines that only checked for NTP statements and it took about 48 hours. At another time, I checked 60 some CATOS switches that took over 36 hours? It doesn't seem to make a difference if you just run a compliancy check or a compliancy & deploy, or just a deploy job. They all take far too long.

In one case, we checked for snmp statements on CATOS switches and the first 15 devices or so only took about 4 minutes. Then it sat there forever and finally finished about 36 hours later.

Are the devices being checked sequentially instead of in parallel?

Finally, is there an improvement to this in LMS 3.x? We are running LMS 2.6 with all the latest service packs and IDU's.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Mon, 06/23/2008 - 09:50

There was a big performance problem in RME 4.0.5, and it was slightly mitigated in RME 4.0.6. However, the real performance fixes didn't go in until RME 4.1.

Your problem sounds like a deeper bug, though. I am at Networkers right now, and I can't analyze this. If this is urgent, I suggest you open a TAC service request, and they can assist you with debugging.


This Discussion