[Ace] CA Beacons failing on Hall A Slow Controls Net

[Brian Bevins]

Do we manage the 188-191 subnet or does Hall A? It's listed as the "Hall 
A Slow Controls" network. Our gateway cagwhla, which provides access to 
Ops, etc. for Hall A clients is reporting errors like this:

Jul 27 15:35:41 !!! Errlog message received (message is above)
../../../../src/cas/io/bsdSocket/casDGIntfIO.cc: CA beacon (send to 
"129.57.191.255:5065") error was "Connection refused"

over and over again every 15 seconds as it tries to send CA server 
beacons to that network. "Connection refused" seens like a weird error 
for a broadcast. William is commenting out that subnet from the beacon 
list for now. Oddly, we can send other broadcast traffic (like PV name 
resolution requests) to that subnet with no problems (port 5064 rather 
than 5065).

Can we fix this? Or do I need to get in touch with someone from Hall A?

Thanks,
--Brian

-- 
Brian S. Bevins, PE
Computer Scientist / Mechanical Engineer
Thomas Jefferson National Accelerator Facility

     "The urge to save humanity is almost always only a false-face
      for the urge to rule it."
                                     -- H. L. Mencken