The ATLAS TDAQ network consists of four separate Ethernet based networks which together total over 4000 ports with 200 edge switches and 6 multi-blade chassis switches at the core. System checks are invoked at every level of the installation. The full installation is described in different static databases. Tools are provided to automatically cross-check these for consistency. The configuration management is centralized: configuration files stored in a database are distributed to all devices and the actual settings are periodically verified. Monitoring systems are deployed to validate the connectivity, identify malfunctions and confirm the resources availability upon request from TDAQ control. Relevant operational statistics (e.g., port status and throughput) are continuously logged and made available to TDAQ control. Watches and alarms are set for dynamic threshold violations and the complete instantaneous status can be viewed at different levels of abstraction in a 3D fly-through. A tool-set has been developed to demonstrate aggregate achievable cross-sectional bandwidth for TDAQ-specific traffic profiles, as well as to analyze traffic flows and hot spot behaviour.
[1]
F Glege.
The Rack Wizard, a graphical database interface for electronics configuration
,
2003
.
[2]
Rob Enns,et al.
NETCONF Configuration Protocol
,
2006,
RFC.
[3]
Peter Phaal,et al.
InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks
,
2001,
RFC.
[4]
E. Manola-Poggioli,et al.
MANUFACTURING AND TEST FOLDER: MTF
,
2002
.
[5]
E. Panikashvili,et al.
Design Tools for Large Networks
,
2007,
2007 15th IEEE-NPSS Real-Time Conference.
[6]
Hans Bergsten.
JavaServer Pages
,
2000
.
[7]
P. Amaudruz,et al.
The TIGRESS DAQ/Trigger system
,
2008,
2007 15th IEEE-NPSS Real-Time Conference.
[8]
B. Martin,et al.
GETB-a gigabit ethernet application platform: its use in the ATLAS TDAQ network
,
2006,
IEEE Transactions on Nuclear Science.