DSC Supplemental Installation Instructions.

Servers Currently Using DSC

ns1-vm.sys.oakland.edu (DNS Server running collector) dnscol1.sys.oakland.edu (standalone collector monitoring Adonis-dhe) dnscol2.sys.oakland.edu (standalone collector monitoring Adonis-nfh) netapp.sys.oakland.edu (dsc presenter)

Basic Overview of DSC

DSC is made up of two distinct parts the collector and the presenter. The collector can either run on the DNS server or it can be run on a standalone server with 2 NIC’s with one reserved for a monitor port from the DNS server. The collector in either configuration then on a scheduled basis sends via rsync over ssh all of its captured information and the presenter compiles this information for parsing by the web portion of the presenter. More detailed description of all the above can be found in the [http://dns.measurement-factory.com/tools/dsc/ DSC configuration manual].

Collector Setup

The majority of the configuration is well outlined in the DSC configuration manual, however, there were a few issues that were found and not documented.

  1. libpcap-devel package is required. On ubuntu the package is named libpcap0.8-dev and can be installed via apt-get. On redhat the package is named libpcap-devel and can be installed via yum.
  2. On the collectors, the upload-rsync.sh script calls the program “md5” which doesn’t exist on either Ubuntu 7.10 or Fedora 7. Instead “md5” was replaced with “md5sum”.

    • md5 -r $k > MD5s → md5sum $k > MD5s

  3. Also in upload-rsync.sh, I found that the script sets an environment variable RSYNC_RSH which carries the private key information does not work. To correct I insterted the following as an argument for rsync:
    • -e 'ssh -i /root/.ssh/dsc_uploader_id'

Presenter Setup

The majority of the configuration is well outlined in the DSC configuration manual, however, there were a few issues that were found and not documented.

  1. When installing PERL libraries ensure that PROC::PID::File library is installed.
  2. Ran into issue with DSC looking in the wrong spot for ploticus. Modified line 418 of /usr/lib/perl5/site_perl/5.8.8/DSC/ploticus/pm so that it pointed to the correct location of ploticus. In this specific instance ploticus was installed in /usr/bin.
  3. Created a symbolic link to /var/www/html/dsc with the following command:
    • ln –s /usr/local/dsc/share/html /var/www/html/dsc