Difference: ValidateROCNagios (31 vs. 32)

Revision 322010-12-17 - DavidCollados

Line: 1 to 1
 
META TOPICPARENT name="MultiLevelMonitoringOverview"

How to validate a ROC or NGI Nagios box

Line: 19 to 19
 
  1. Join tool-admins mailing list. Register here
  2. Register your node as the relevant flavour of Nagios in GOCDB (Regional-Nagios, National-Nagios)
Changed:
<
<
  1. Register for access to the SAM PI
>
>
  1. Register for access to the SAM PI (ONLY if you don't want to use ATP as the topology provider for NCG)
 
    1. open a GGUS ticket
    2. ask in the ticket to get it assigned to 'Nagios' Support Unit
    3. mention in the ticket the IP address of your Nagios instance and that you need access to the SAM PI to configure it.
Line: 32 to 32
  In order to validate your instance, please follow these steps:
  1. Ensure that all the egee-sa1 packages are upgraded. For this, the following query shouldn’t return any data:
    [root~]# repoquery --pkgnarrow=updates --disablerepo=\* --enablerepo=egee-sa1 -qa --queryformat ' yum update %{name} '
Changed:
<
<
  1. Send us the following information to sam-support@cern.ch:
    1. your ncg.conf file. The format of your file should be like this one.
    2. the result of following query executed on your Nagios box:
      [root~]# nagios -v /etc/nagios/nagios.cfg | grep Checked | grep services
    3. the glite-UI version used by you (we are currently using glite-UI-version-3.2.*-0):
      [root ~]# rpm -qa | grep glite-UI
  2. Ensure that ncg cron job is executed regularly (every 3 hours in our case): https://tomtools.cern.ch/jira/browse/SAM-402
  3. Check if your services are being tested by the metrics defined in the ROC SAM critical profile, described here: https://twiki.cern.ch/twiki/bin/view/LCG/MDDBProfilesSAM#ROC_SAM_critical
  4. Once you have done this, open a GGUS ticket to be assigned to the 'Nagios' support unit. Please mention in the ticket which is your ROC/NGI Nagios instance, so we:
>
>
  1. Ensure that ncg cron job is executed regularly (every 3 hours in our case): https://tomtools.cern.ch/jira/browse/SAM-402
  2. Check if your services are being tested by the metrics defined in the ROC SAM critical profile, described here: https://twiki.cern.ch/twiki/bin/view/LCG/MDDBProfilesSAM#ROC_SAM_critical
  3. Once you have done this, open a GGUS ticket to be assigned to the 'Nagios' support unit. Please mention in the ticket which is your ROC/NGI Nagios instance, so we:
 
    1. add the nagios instance to the ops-monitor nagios ( https://ops-monitor.cern.ch/nagios/ ) to compare the number of services and hosts with the project level instance
    2. and to compare the status of your services to the ones defined in the central Nagios instance at CERN.
    3. for a ROC to validate an NGI Nagios instance, you should use the ops-monitor nagios
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback