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
- References:
- CA beacon routing error S_errno_ECONNREFUSED J. Lewis Muir
- RE: CA beacon routing error S_errno_ECONNREFUSED Jeff Hill
- Navigate by Date:
- Prev:
Re: Xenomai Linux David Kline
- Next:
RE: Xenomai Linux nick.rees
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: CA beacon routing error S_errno_ECONNREFUSED Jeff Hill
- Next:
trouble with 64-bit Window7 Matt Newville
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|