SRO DAQ test stand
From Hall A Wiki
Run SRO CODA
User and hostname: hatdaq@hatestlab1
- startCoda
- Load configuration: testsro
- Connect -> Download -> Prestart -> Start -> End
- Note:
- need to reset CODA at the end of each run when running the SRO CODA
- DiagGUI: at "/home/hatdaq/fe_diaggui"; do "./DiagGUI ROC_apol1.txt"
- Remote power cycle the crate: hatestlabcrate1 (hostname)
VNC
- The VNC server is running as a systemd service at "hatdaq@hatestlab1". To check the status of the VNC server:
systemctl status vncserver@\:5.service
- The VNC can be connected at the VDI desktop or ifarm by doing
vncviewer -via hatdaq@hatestlab1 :5
; the password is the "hatdaq" account password
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 VTP/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 linux from attempting to route general 'JLab/Internet' traffic on that interface. It also seems to fix a packet-loss problem with the CODA aggregator service.
- Command line (as root):
nmcli connection modify your_device_name ipv4.never-default true
- Command line (as root):
- VXS Crate/Power Control: "hatestlab1.jlab.org"
- VTP: "apolvtp1": one ethernet connection to the network switch for booting, and one local fiber connection to "hatestlab1" as stated above
- Single-board computer: "apol1"
- ``Other important/useful network connected devices for the SRO setup?``: HV crate control board? (to be installed)