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