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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: cross subnet CA communication |
From: | Sue Witherspoon <[email protected]> |
To: | Andrew Johnson <[email protected]> |
Cc: | Tech-talk <[email protected]> |
Date: | Wed, 02 Apr 2008 15:12:15 -0400 |
Yes, the 129.57.239.255 is the broad address for the 236 subnet. I have tried using the actual address (129.57.236.20) also but neither seems to open the flood gates of communication.
Any other thoughts?
Thanks in advance,
Sue
Andrew Johnson wrote:Hi Sue,
Sue Witherspoon wrote:I have a curious problem concerning multi-subnet connectivity when converting from Epics 3.13.2 to Epics 3.14.8.2. Using the same network setup and database the 3.13 db can communicate across subnets while the 3.14 db gets a link error.
I'm having difficulty understanding your subnet architecture; the IP addresses you're using don't seem to match up — I think you just have a typo in your EPICS_CA_ADDR_LIST setting.
From your description you have a heartbeat calc record on iocmc1 (129.57.236.20) which you would like to monitor from an ai record on iocfb1 (129.57.230.101). In order for that link to work, the EPICS_CA_ADDR_LIST on iocfb1 must include the 129.57.236.xxx subnet, but you're pointing it to the 129.57.239.xxx subnet instead:
resource.def file for iocfb1 putenv ("EPICS_CA_AUTO_ADDR_LIST = YES") putenv ("EPICS_CA_ADDR_LIST = 129.57.239.255")
HTH,
- Andrew