OWG Meeting 9-May-2012

From GlueXWiki
Revision as of 10:54, 11 May 2012 by Wolin (Talk | contribs)

Jump to: navigation, search

Agenda

  • Announcements
    • Summer students and projects
  • Review of minutes from 25-Apr-2012 meeting
  • Network monitoring at JLab - Bryan Hess
  • Agenda for the Collaboration Meeting May 21-23
  • EVIO status report - Carl, Elliott
  • Recent online plans and purchases - Hovanes
  • Barcode scanner - Elliott
  • Hall D Component Inventory Database - Elliott
    • telecom info, location hierarchy
  • Counting House status - Hovanes
  • 12GeV Schedule - Hovanes, David, Elliott
  • Elog and Accelerator division projects - Graham
  • DAQ group - Bryan, Dave A, Graham
    • CODA3, EVIO, ECS/CSS, raw event file, disentangler, readout list
  • EPICS - Hovanes, Vanik
    • transferring some projects to Accelerator Div.
  • Controls - Elliott
  • Electronics, trigger and DAQ status reports - Chris, Alex, Dave, Fernando, Ben, Ed, William, Bryan
  • Mantis Task Tracker
  • Midas Elog


  • Calibration/Alignment issues?
  • Computer system manager


Time/Location

1:30 PM Wed 9-May-2012 CC F326


Announcements

Let Elliott know if you have projects for summer students. So far we've only attracted one student from CNU, and we could use more.


Next Meeting

Note: Collaboration Meeting 23-May-2012

1:30 PM Wed 6-Jun-2012 CC F326


Minutes

Present: Elliott W, Simon T, Bryan Hess, Carl T, Mark I, Bryan M, Vanik K, Beni Z.


Network Monitoring

Bryan Hess, head of networking in the computer center, explained how they monitor hundreds of networking switches at the lab, see his slides for many details.

  • All monitoring done in-band.
  • Extensive checking and archiving of results for later analysis.
  • Monitor latency, packet loss, throughput as early warning of future switch failure.
  • Network configurations stored in svn.
  • They do NOT monitor "edge" devices (e.g. computers, about 5000 total), just the networking infrastructure.
  • They also do not monitor end-user applications, services, etc.
  • Monitoring system is "JNet", written by Bryan and Brent.
  • Switches indexed by location, gives information about what is connected to the switch, including phones.
  • Nightly and continuous checking.
  • 24x7 support for networks by CC (via calling Guard Shack), Bryan and/or Brent gets called as needed.
  • Accelerator manages completely separate networks, almost nothing in common with CC networks.
  • Best way to reset switch is to cycle power, thus we need an out-of-band power reset system.

Finally, Bryan says it should be no problem feeding alarms from JNet into the Hall D online alarm system.


EVIO Status