perfSONAR

• http://www.perfsonar.net/
• http://code.google.com/p/perfsonar-ps/wiki/NPToolkitQuickStart
• based on http://www.knoppix.net/ distro

Node Info

These have a single network connection.

Location	Hostname	IP	Power Outlet	Switch Port	KVM	Test Type
101-37	psmsu01.aglt2.org	192.41.231.19	PDU-101-2,20	10.10.2.9,unit 1,g43	9	Delay
101-36	psmsu02.aglt2.org	192.41.231.20	PDU-101-2,19	10.10.2.9,unit 1,g44	10	Bandwidth

Koi Hardware

Setup the BIOS so that:

• CD is only boot device
• Quickboot disabled
• Big logo disabled
• Node turns on at power restore (in power -> apm settings menu)

perfSONAR setup

perfSONAR 2.0 requires a CD-ROM to run from. The Knoppix 4.x distribution uses AuFS (UNIONFS) to

• burn and verify CD-ROM with iso image
• set the BIOS as above
• make sure that the harddrive is ready to use. I just removed all partitions (knoppix will make a file system on /dev/sda, seems fine)
• boot system from CD, which needs to remain in the drive after installation
• work your way through the menus (see instructions from perfSONAR) localized as follows
  • Site settings:
    • site name: AGLT2-MSU
    • communities of interest: LHC USATLAS
    • connection speed: 1GBps
  • Enable/disable services
    • Enable SSH
    • for Delay test node: select Disable Stock Bandwidth Services
      which will disable BWCTL, NDT, NPAD
    • for Bandwidth test node: select Disable Stock Latency Services
      which will disable OWAMP, PingER
  • Configure BWCTL (even if disabled): no limit, using '*' where suggested
  • Configure NTP servers: Internet2's Atlanta, Chicago, Houston, ESnet NY, Naval Obs Columbus
  • Configure OWAMP (even if disabled): no limit, using '*' where suggested
  • Static IP:
    • interface: eth0
    • ip address: cf. table above
    • netmask: /24
    • gateway: 192.41.231.1
    • DNS servers: MSU's 35.8.2.41 and 35.9.68.12
  • Time zone: US/Michigan
• Exit configuration menu, automatic reboot, setup is done.

• Notes:
  • the config script is /KNOPPIX/usr/local/bin/nptoolkit-configure.py
  • The boot sequence always invokes this config menu script,
    but this step automatically times out and startup proceeds after 60s,
    assuming the node is already configured.

-- PhilippeLaurens - 23 Feb 2009