Best Practise - Monitoring LMS 3.2 - System

Unanswered Question
Oct 29th, 2009
User Badges:

Hi there,


are there any best practises how to monitor LMS 3.2 system for faulty conditions?


Is it possible to extract problems like Campus DataCollections was not started, RME-Invenory fails for xxx devices, CW2000-process xyx died unexpected ...


Is there any script include in LMS usable for system/application monitoring?



Thanks for your thoughts


Best Regards


Lothar

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 10/29/2009 - 07:38
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The Daemon Manager itself tries to maintain daemon health. It can detect if a daemon dies, and it will try to restart it.


However, if you want to monitor health on your own, the pdshow command is the way to do it. Most daemons should always be running. In LMS 3.2, you may have a few which can be down in a healthy system:


DFMCTMStartup

DataPurge

CSDiscovery

UTMajorAcquisition

CWAPublisher

DCRDevicePoll

FDRewinder (Solaris only)

(any numbered process like 1001)


Any other daemon should be running.


RME also has the ability to notify you if a job fails. Go to RME > Admin > System Preferences > Collection Failure Notification, and enable notifications when the desired collection fails.

Actions

This Discussion