LEMON and Serial Console installation on testbed machines

The method used for installation of lemon monitoring and serial access services on the testbed machines is a meta-package rpm. This rpm will install all packages needed for lemon services and will configure serial access (meaning access on the testbed machines through serial connection).

For this have been created our own repositories for SL3/i386 and SL4/i386/x86_64. All repositories are accessible for both installers, apt and yum, but in principle SL3 is apt based and SL4 yum based. The configuration files for this repos are:

• APT - in /etc/apt/sources.list.d create lemon.list:

        rpm http://grid-deployment.web.cern.ch/grid-deployment lemon/apt/current/i386 sl3
        

• YUM - in /etc/yum.repos.d create lemon.repo:
  • i386:

          [lemon]
          name=Lemon
          baseurl=http://grid-deployment.web.cern.ch/grid-deployment/lemon/apt/current/i386/RPMS.sl4/
          enabled=1
          protect=1
          

  • x86_64:

          [lemon]
          name=Lemon
          baseurl=http://grid-deployment.web.cern.ch/grid-deployment/lemon/apt/current/x86_64/RPMS.sl4/
          enabled=1
          protect=1
          

After the repo files are created you can install the meta-package rpm.

The meta-rpm is lemon-serialconsole-install-gd (v2.02) and install the following packages:

• for lemon services: ncm-ncd, cdp-listend, ncm-query, ncm-cdispd, CERN-CC-ccm-conf, edg-fabricMonitoring-agent, edg-fabricMonitoring-api, edg-fabricMonitoring-mrs, lemon-cli, lemon-host-check, lemon-sensor-parse-log, lemon-sensor-exception, ncm-fmonagent, CERN-CC-lemon-servers-transport
• for serial access configuration: serialconsole-install-gd

If everything is OK, all services are configured and started after the installation. The meta-rpm could be installed stand-alone or could be included in a kickstart installation.

For a stand-alone install follow next steps:

• apt based:

        #apt-get update
        #apt-get install lemon-serialconsole-install-gd
        

• yum based:

        #yum clean all
        #yum install lemon-serialconsole-install-gd
        

After the installation is finished, check if the following services are started (if not start them): cdp-listend, ncm-cdispd and edg-fmon-agent. Check if you can login on the machine using serial line.

Old (first) method for LEMON installation on testbed machines

After a basic installation of the SLC OS on a plain testbed machine, you need to set-up some additional repositories (quattor and lemon repos) and install some packages (minimal NCM framework and lemon software).

Additional packages needed are:

• for minimal NCM framework: perl-AppConfig-caf ncm-ncd cdp-listend ncm-query ncm-cdispd CERN-CC-ccm-conf
• for lemon service: edg-fabricMonitoring-agent edg-fabricMonitoring-api edg-fabricMonitoring-mrs lemon-cli lemon-host-check lemon-sensor-parse-log lemon-sensor-exception ncm-fmonagent

For YUM setup, additional repositories in /etc/yum.repos.d are the following:

• create quattor.repo

[main]
[quattor]
name=quattor
baseurl=http://quattorsw.web.cern.ch/quattorsw/software/quattor/yum/1.2/$basearch/RPMS.quattor_sl4
enabled=1
protect=1

• create lemon.repo

[lemon]
name=Lemon
baseurl=http://linuxsoft.cern.ch/lemon/linux/RPMS/$basearch/sl4/stable/
enabled=1
protect=1
gpgcheck=1
gpgkey=http://linuxsoft/lemon/RPM-GPG-KEY-lemon

• create lemon-servers.repo

[lemon-servers]
name=Lemon Servers
baseurl=http://linuxsoft.cern.ch/lemon/cern/
enabled=1
protect=1
gpgcheck=1
gpgkey=http://linuxsoft/lemon/RPM-GPG-KEY-lemon

where $basearch stands for host architecture i386, x86_64, etc. Please adjust the architecture and operating system accordingly to point to the correct area in the repositories.

Note: Or you can copy the repository files templates from /afs/cern.ch/project/gd/scratch/gstoicea. Don't forget to adjust the repos files.

In general all needed packages are in quattor or lemon repositories with one exception: CERN-CC-ccm-conf. The last version of this one could be found at following address: http://swrep.cern.ch/swrep. This package could be installed using 'rpm -Uvh' command from http://grid-deployment.web.cern.ch/grid-deployment/lemon/ (you can check to see if it's the last version at the above address).

The procedure used for monitoring setup is taken from lemon documentation (see below), but there are some differences. The procedure is the following:

• create the necessary yum repositories files for quattor and lemon;
• install NCM framework:

#yum install perl-AppConfig-caf ncm-ncd cdp-listend ncm-query ncm-cdispd
#rpm -Uvh http://grid-deployment.web.cern.ch/grid-deployment/lemon/CERN-CC-ccm-conf-1.3.1-1.noarch.rpm

• check if the following services are running:

#service cdp-listend status
#service ncm-cdispd status

If not then start them:

#service cdp-listend start
#service ncm-cdispd start

• initialize the whole thing:

#ccm-initialise
#ccm-fetch

• to check whether you have downloaded your profile correctly, run the following command. You should see some printout.

#ncm-query --dump /

and you will see the whole loaded profile

[INFO] Subtree: /
+-/
  +-hardware
    +-bios
      $ vendor : (string) 'American Megatrends Inc.'
      $ version : (string) '080010 (12/16/2005)'
    +-cards
      +-nic
        +-0
          $ bus : (string) 'pci'
          $ hwid : (string) '00-30-48-85-AB-38'
          $ manufacturer : (string) 'Intel Corporation'
          $ maxspeed : (long) '1024000'
          $ media : (string) 'Ethernet'
          $ name : (string) '82541GI/PI Gigabit Ethernet Controller'
        +-1
          $ bus : (string) 'pci'
          $ hwid : (string) '00-30-48-85-AB-39'
          $ manufacturer : (string) 'Intel Corporation'
          $ maxspeed : (long) '1024000'
          $ media : (string) 'Ethernet'
          $ name : (string) '82541GI/PI Gigabit Ethernet Controller'
    +-contract
      $ warrantyid : (string) 'it_cd1001168'
    $ cpucount : (long) '2'
    +-cpus
      +-0
        $ model : (string) 'Intel(R) Xeon(TM) CPU 2.80GHz'
        $ ncpu : (double) '1'
        $ si2k : (long) '1037'
        $ speed : (long) '2800'
        $ vendor : (string) 'GenuineIntel'
      +-1
        $ model : (string) 'Intel(R) Xeon(TM) CPU 2.80GHz'
        $ ncpu : (double) '1'
        $ si2k : (long) '1037'
        $ speed : (long) '2800'
        $ vendor : (string) 'GenuineIntel'
..............................................................................
..............................................................................
      +-nameserver
        $ 0 : (string) '137.138.16.5'
        $ 1 : (string) '137.138.17.5'
      +-timeserver
        $ 0 : (string) 'ip-time-1'
        $ 1 : (string) 'ip-time-2'
    $ quattor_managed : (string) 'no'
    +-responsible
      $ familyname : (string) 'PONCET'
      $ forename : (string) 'LOUIS'
    $ siterelease : (string) '---'

If you do

#ncm-query --dump /system

[INFO] Subtree: /system
+-system
  $ ccdbname : (string) '????'
  $ ccdomain : (string) 'GD'
  +-cluster
    $ itcontact : (string) 'Louis.Poncet@cern.ch,Yvan.Calas@cern.ch,Maarten.Litmaath@cern.ch,Di.Qing@cern.ch,Antonio.Retico@cern.ch'
    $ itsection : (string) 'FIO-FS'
    $ name : (string) 'lxnoq'
    $ subname : (string) 'lcgcert'
    $ tplname : (string) 'pro_type_lcgcert_noq'
    $ type : (string) 'non-quattor'
    $ usercontact : (string) 'Louis.Poncet@cern.ch,Yvan.Calas@cern.ch,Maarten.Litmaath@cern.ch,Di.Qing@cern.ch,Antonio.Retico@cern.ch'
  $ contract : (string) 'E'
  $ defaultstate : (string) 'unmanaged'
  +-filesystems
  $ function : (string) 'LCG software certification'
  $ importance : (long) '20'
  +-kernel
    $ version : (string) '---'
  +-network
    $ domainname : (string) 'cern.ch'
    $ hostname : (string) 'lxb6130'
    +-interfaces
      +-eth0
        $ gateway : (string) '128.142.1.1'
        $ ip : (string) '128.142.131.101'
        $ netmask : (string) '255.255.0.0'
        $ switchmedium : (long) '1024000'
    +-nameserver
      $ 0 : (string) '137.138.16.5'
      $ 1 : (string) '137.138.17.5'
    +-timeserver
      $ 0 : (string) 'ip-time-1'
      $ 1 : (string) 'ip-time-2'
  $ quattor_managed : (string) 'no'
  +-responsible
    $ familyname : (string) 'PONCET'
    $ forename : (string) 'LOUIS'
  $ siterelease : (string) '---'

and you'll see only the system subcomponent. If some subcomponent is not present in your profile file you'll get an error message.

#ncm-query --dump /system/monitoring
[ERROR] Path: '/system/monitoring' does not exist

• install lemon packages for a minimal Lemon monitoring together with some basic tools

#yum install edg-fabricMonitoring-agent edg-fabricMonitoring-api edg-fabricMonitoring-mrs lemon-cli lemon-host-check lemon-sensor-parse-log lemon-sensor-exception ncm-fmonagent
#yum install CERN-CC-lemon-servers-transport

• check if edg-fmon-agent service is started. If not start it.
• configure ncm components:

#ncm-ncd --configure --all

• now you need to run the fmonagent NCM component. Do not forget to download the newest version of the configuration template

#ccm-fetch
#ncm-ncd --co fmonagent

In general after all this procedure monitoring must work. Check on the lemon monitoring page (http://lemonweb.cern.ch/lemon-status/entry.php) if the machine is now monitored by introducing the host name in the 'Search host' box (bottom left).

Final Note: Check if necessary services (cdp-listend, edg-fmon-agent and ncm-cdispd) are activated to be started automatically at the boot time.

A HOWTO could be found at http://lemon.web.cern.ch/lemon/doc/howto/lemonization_howto.shtml (maybe not so up-to-date; good for guiding).

-- LouisPoncet - 22 Jun 2007 -- GabrielStoicea - 25 Sep 2007