Experimental Physics and
Industrial Control System

Sue Witherspoon <[email protected]> · Wed, 02 Apr 2008 16:30:20 -0400

In the startup are the lines:
hostAdd "devnet",   "129.57.228.1"
# use this for IOC's which are on 129.57.{228,229,230,231}
routeAdd "0.0.0.0", "devnet"
I couldn't run tcpdump but I could run casw on the 236 subnet and I'm
getting no broadcasts from iocfb1.
I can ping from each IOC and see the other IOC.
When I switch between different kernels and EPICS I've had to burn the
flash to go from tornado 1.0.1 to 2.2.1. And then change links that
point to the different versions.
My original thought was there is some parameter in the kernel or epics
that I'm missing because I am communicating from the 230 to the 236
network if both IOCs are running epics 3.13 and tornado 1.0.1. And
within a subnet I can communicate regardless of the kernel or EPICS version.
-Sue
Paul Sichta wrote:

I've added the following to the st.cmd boot file. The IP is the IP of
the gateway for the subnet of the IOC server.
# for beyond-subnet CA clients
routeAdd "0", "198.35.10.10"
-ps

Geoff Savage wrote:

Can you run tcpdump on a linux box in the 236 subnet to look for the
broadcast from iocfb1?

Does a ping from each IOC see the other IOC?

What do you do to switch between the different kernels and EPICS
versions when you boot? Are you missing a non-EPICS configuration in
this process?
Geoff
On Apr 2, 2008, at 12:33 PM, Sue Witherspoon wrote:

Greetings,

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.

Again, if iocfb1 is running Epics 3.13.2 and Tornado 1.0.1 then there
is no link error and there's communication between the two subnets,
but if iocfb1 is running Epics 3.14.8.2 and Tornado 2.2.1 then I get
a link error. Any suggestions?
Here is my setup:
 iocmc1 129.57.236.20         iocfb1 129.57.230.101
 Epics 3.13.2                         Epics 3.14.8.2
 mvme-2700                          mvme-2700
 Tornado 1.0.1                      Tornado 2.2.1
  database record  on iocfb1 129.57.230.101
      record(ai,"iocfb1:mc1com1") {
        field(DESC,"analog input record")
        field(SCAN,"Passive")
        field(INP,"iocmc1:heartbeat.VAL")
       }
 database record on iocmc1  129.57.236.20
     record(calc,"iocmc1:heartbeat") {
        field(DESC,"calculation record")
        field(SCAN,"1 second")
       }
  resource.def file  for iocfb1
      putenv ("EPICS_CA_AUTO_ADDR_LIST = YES")
      putenv ("EPICS_CA_ADDR_LIST = 129.57.239.255")
  bootParams:
boot device          : dc0
processor number     : 0
host name            : devfs
file name            : /devsite/op/iocs/iocfb1/vx/vxWorks.st
inet on ethernet (e) : 129.57.230.101:fffffc00
inet on backplane (b):
host inet (h)        : 129.57.228.40
gateway inet (g)     : 129.57.228.1
user (u)             : vxwrks
ftp password (pw) (blank = use rsh):
flags (f)            : 0x80
target name (tn)     : iocfb1
startup script (s)   : /devsite/op/iocs/iocfb1/startup
 resource.def file for iocmc1 EPICS_CA_ADDR_LIST DBF_STRING
"129.57.211.255 129.57.243.255 129.57.255.10"
 bootParams:
boot device          : dc
processor number     : 0
host name            : opsfs
file name            : /opssite/op/iocs/iocmc1/vx/vxWorks.st
inet on ethernet (e) : 129.57.236.20:fffffc00
host inet (h)        : 129.57.236.40
user (u)             : vxwrks
flags (f)            : 0x80
target name (tn)     : iocmc1
startup script (s)   : /opssite/op/iocs/iocmc1/startup

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System