Experimental Physics and
Industrial Control System

"J. Lewis Muir" <[email protected]> · Tue, 31 May 2011 11:20:38 -0500

On 5/20/11 11:08 AM, Jeff Hill wrote:
> In any case, the indirect cause might be an explicit unicast address in
> EPICS_CAS_BEACON_ADDR_LIST (defaulting to EPICS_CA_ADDR_LIST). The RFC's say
> that the network kernel can respond with "destination unreachable" ICMP
> error response to a IP packet with a unicast destination address, but not to
> a IP packet with a broadcast destination address. Since the ICMP destination
> unreachable isn't returned if there is a valid udp receiver for the
> destination frame then starting and stopping the other ca server might have
> an impact on the occurrence of the message.

Hi, Jeff.

Thanks for your help.  Based on your suggestion that the
indirect cause might be an explicit unicast address in
EPICS_CAS_BEACON_ADDR_LIST, I added the following environment
settings to both IOCs and rebooted:

===
putenv "EPICS_CAS_AUTO_BEACON_ADDR_LIST=NO"
putenv "EPICS_CAS_BEACON_ADDR_LIST=192.168.0.127 192.168.0.255"
===

The CA beacon routing error messages on the consoles have now
gone away.

Thanks!

Lewis

-- 
J. Lewis Muir
Software Engineer
IMCA-CAT

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System