Re: cross subnet CA communication

[Andrew Johnson <anj@aps.anl.gov>]

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
--
When a distinguished but elderly scientist states that something is
possible, he is almost certainly right.  When he states that something
is impossible, he is very probably wrong.  -- Arthur C. Clarke