Difference between revisions of "SRO DAQ test stand"

From Hall A Wiki
Jump to: navigation, search
(Run SRO CODA)
Line 9: Line 9:
 
# DiagGUI: at "/home/hatdaq/fe_diaggui"; do "./DiagGUI ROC_apol1.txt"
 
# DiagGUI: at "/home/hatdaq/fe_diaggui"; do "./DiagGUI ROC_apol1.txt"
 
# Remote power cycle the crate: hatestlabcrate1 (hostname)
 
# Remote power cycle the crate: hatestlabcrate1 (hostname)
 +
 +
 +
=== Network ===
 +
* hatestlab1:
 +
** The primary network interface for the host is 129.57.37.126 on eno8303
 +
** The VTP is connected directly to the DAQ host (hatestlab1) through a dedicated fiber connection (no switch/router). The kernel name for this interface is 'ens5f1np1' and it is on the (internal) 192.168.1.x network
 +
** There is also an iDRAC connection (2nd cat6 cable) plugged in.  That is not available within linux, but is on the network for admin purposes at hatestlab1-idrac.jlab.org. (129.57.37.126)
 +
** '''NOTE''': The VPT/fibre interface has been flagged "use connection only for resources on its network" (sometimes called 'local-traffic only' or 'never use this network for default route'.  This prevents that interface from attempting to route general 'JLab/Internet' traffic and also seems to fix a packet-loss problem with the CODA aggregator service.
 +
*** Command line: <code>nmcli connection modify your_device_name ipv4.never-default true</code>
 +
 +
* VXS Crate/Power Control
 +
 +
* VTP
 +
 +
* Single-board computer
 +
 +
* ``Other important/useful network connected devices for the SRO setup?``

Revision as of 15:17, 15 January 2025

Run SRO CODA

User and hostname: hatdaq@hatestlab1

  1. startCoda
  2. At a different terminal: coda_emu_pag PAGG1
  3. Load configuration: testsro
  4. Connect -> Download -> Prestart -> Start -> End
  • Note:
  1. need to reset CODA at the end of each run when running the SRO CODA
  2. DiagGUI: at "/home/hatdaq/fe_diaggui"; do "./DiagGUI ROC_apol1.txt"
  3. Remote power cycle the crate: hatestlabcrate1 (hostname)


Network

  • hatestlab1:
    • The primary network interface for the host is 129.57.37.126 on eno8303
    • The VTP is connected directly to the DAQ host (hatestlab1) through a dedicated fiber connection (no switch/router). The kernel name for this interface is 'ens5f1np1' and it is on the (internal) 192.168.1.x network
    • There is also an iDRAC connection (2nd cat6 cable) plugged in. That is not available within linux, but is on the network for admin purposes at hatestlab1-idrac.jlab.org. (129.57.37.126)
    • NOTE: The VPT/fibre interface has been flagged "use connection only for resources on its network" (sometimes called 'local-traffic only' or 'never use this network for default route'. This prevents that interface from attempting to route general 'JLab/Internet' traffic and also seems to fix a packet-loss problem with the CODA aggregator service.
      • Command line: nmcli connection modify your_device_name ipv4.never-default true
  • VXS Crate/Power Control
  • VTP
  • Single-board computer
  • ``Other important/useful network connected devices for the SRO setup?``