Jonathan, TJ, Jamie, Dave:
Following h1guardian1's upgrade to a 2-cpu, 40 hyper-threaded core machine on Wednesday, I started trending its ethernet port statisics Friday afternoon. Every 10 minutes ifconfig reports the port input/output errors. Jamie and TJ will see if any EPICS-CA errors correlate to ethernet port issues.
When the script was started the only error was an accumulated 1048 receive overruns (i.e. RX FIFO errors). We suspected that these may have been acquired when h1pemey/DAQ were restarted Thursday.
No further errors have been seen since program start (see attachment)
Just as a note to the connection errors with h1guardian1, I quickly trended the H1:GRD-{node}_CONNECT channel for 6 of the more used nodes (ISC_LOCK, IMC_LOCK, OMC_LOCK, ISC_DRMI, ALS_YARM, ALS_XARM) and there was only one connection error over the weekend. These nodes used to have multiple a day, so this seems like a good sign, but a more thorough investigation is still needed.
