CA beacon errors

[mattei <pierre.mattei@cea.fr>]

Hi,

Since last friday we get the following message on all our VME IOCs:

../online_notify.c: CA beacon routing (connect to "132.166.255.255:5065") error 
was "S_errno_EHOSTUNREACH"

Probably some new device on the network is replying with a "Connection refused" 
message to our broadcasts and we have to find it.

As a workaround, we have added a CA address list to our VMEs. The following 
example declares two Linux PCs:

putenv "EPICS_CA_AUTO_ADDR_LIST=NO"
putenv "EPICS_CA_ADDR_LIST=132.166.31.146 132.166.29.139"

This works fine when the caRepeater is running on the two PCs. If we stop the 
caRepeater on one machine, then we get the CA beacon error message on the VME 
for the two machines.

We use wireshark to see what happens on the network, and in fact after the first 
connect error in online_notify.c the following calls to connect don't send any 
frame and return error, even if we restart the caRepeater on the PC.

We are using EPICS 3.14.11 and VxWorks 6.7.

Best regards,


--
Pierre MATTEI & Yves LUSSIGNOL
CEA Saclay
DSM/IRFU/SIS
pierre.mattei@cea.fr
yves.lussignol@cea.fr