Kevin,
Here is your address list.
EPICS_CA_ADDR_LIST: 128.171.95.50 128.171.95.171 128.171.136.30
128.171.136.98
Does this contain the IP address of your solaris-8 IOC (or the broadcast
addres of its subnet)?
The casw program will only report a beacon anomaly when regular beacons are
disrupted and then resumed (for example when the cable is disconnected and
then reconnected).
PS: The EPICS_CAS_BEACON_ADDR_LIST variable is new in EPICS R3.14 so if your
IOC is running R3.13 both the client and the server are configured with
EPICS_CA_ADDR_LIST.
PPS: If multiple servers run on the same machine limitation in most IP
kernels prevent all of them from receiving beacons addressed to broadcast
addresses.
Jeff
> -----Original Message-----
> From: Kevin Tsubota [mailto:[email protected]]
> Sent: Monday, January 12, 2004 12:04 PM
> To: 'Jeff Hill'; 'tech-talk (E-mail)'
> Subject: RE: PV reconnect logic question
>
>
>
> Hi Jeff,
>
> Here are my Sol-8 IOC environment variables:
>
> epics> coreRelease
> ##############################################################
> ##############
> ### EPICS IOC CORE built on Jan 9 2003
> ### EPICS R3.14.1 $R3-14-1$ $2002/12/12 15:56:59$
> ##############################################################
> ##############
> epics>
> epics> epicsPrtEnvParams
> EPICS_AR_PORT: 7002
> EPICS_CAS_AUTO_BEACON_ADDR_LIST is undefined
> EPICS_CAS_BEACON_ADDR_LIST is undefined
> EPICS_CAS_BEACON_PERIOD is undefined
> EPICS_CAS_BEACON_PORT is undefined
> EPICS_CAS_IGNORE_ADDR_LIST is undefined
> EPICS_CAS_INTF_ADDR_LIST is undefined
> EPICS_CAS_SERVER_PORT is undefined
> EPICS_CA_ADDR_LIST: 128.171.95.50 128.171.95.171 128.171.136.30
> 128.171.136.98
> EPICS_CA_AUTO_ADDR_LIST: YES
> EPICS_CA_BEACON_PERIOD: 15.0
> EPICS_CA_CONN_TMO: 30.0
> EPICS_CA_MAX_ARRAY_BYTES: 16384
> EPICS_CA_REPEATER_PORT: 5065
> EPICS_CA_SERVER_PORT: 5064
> EPICS_CMD_PROTO_PORT is undefined
> EPICS_IOC_LOG_FILE_COMMAND is undefined
> EPICS_IOC_LOG_FILE_LIMIT: 1000000
> EPICS_IOC_LOG_FILE_NAME is undefined
> EPICS_IOC_LOG_INET: 128.171.97.52
> EPICS_IOC_LOG_PORT: 7004
> EPICS_TIMEZONE: CUS::360:040602:102602
> EPICS_TS_NTP_INET is undefined
> epics>
>
> According to the R3.14 CA Ref Man, section Server Beacons:
> If EPICS_CAS_BEACON_ADDR_LIST is not defined,
> EPICS_CA_ADDR_LIST is defined, and
> EPICS_CAS_INTF_ADDR_LIST is not defined,
> then the conents of EPICS_CA_ADDR_LIST will be used to
> augment the list.
>
> It looks like me setup meets this criteria yet I don't see the server
> beason.
> Is it because my EPICS_CAS_BEACON_PERIOD is not defined and
> not defaulting
> to the default 15s?
>
> I am running casw but the only time I saw a beacon anomoly whas when I
> started
> up caSnooper. I'll explicitly set my EPICS_CAS_BEACON_PERIOD but was
> wondering
> why I get no beacon anomolies.
>
>
> -----Original Message-----
> From: Jeff Hill [mailto:[email protected]]
> Sent: Monday, January 12, 2004 5:41 AM
> To: Kevin Tsubota; 'tech-talk (E-mail)'
> Subject: RE: PV reconnect logic question
>
>
>
> Kevin,
>
> Your Solaris-8 IOC (acting as a client) probably does not see
> the server's
> beacons because they are addressed to subnet on which your
> client IOC is not
> listening. The EPICS R3.14 CA reference manual explains this
> situation in
> more detail than in past versions of the manual. See the
> section entitled
> "Dynamic Changes in the CA Client Library Search Interval".
>
> It may be that a simple solution will be to expand the server's beacon
> address list so that beacons are broadcasted also on your
> Solaris-8 IOC's
> subnet. Alternatively, you could install a CA gateway
> providing transparent
> connectivity for remote clients.
>
>
> Jeff
>
> > -----Original Message-----
> > From: Kevin Tsubota [mailto:[email protected]]
> > Sent: Friday, January 09, 2004 6:02 PM
> > To: tech-talk (E-mail)
> > Subject: PV reconnect logic question
> >
> >
> > Hi,
> >
> > I have EPICS R3.14.1 IOC running on Solaris-8 and it
> connects to EPICS
> > R3.13.0b12 PVs running
> > under VxWorks. As an interim safety measure I disconnect the routes
> > between
> > the two IOCs at
> > night and reconnect them during the day.
> >
> > However when I reestablish the routes, my R3.14 IOC PV
> never reconnects
> > to
> > the VxWorks PVs.
> > It stays in STAT=LINK, SEVR=INVALID state. THe R3.14 PV is
> using a CPP
> > input link to the
> > VxWOrks PV. When I restart my R31.4 IOC it connects up right away.
> >
> > Why doesn't the R3.14 PV reconnect automatically?
> > Is there a way to force the R3.14 PV to reconnect without having to
> > restart
> > it?
> >
> > Mahalo!
> >
> > Kevin Tsubota
> > W.M. Keck Observatory
>
- References:
- RE: PV reconnect logic question Kevin Tsubota
- Navigate by Date:
- Prev:
RE: PV reconnect logic question Kevin Tsubota
- Next:
Re: compile error of EPICS 3.14.4 under windows Steven . Banks
- 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: PV reconnect logic question Kevin Tsubota
- Next:
Running epics in background in linux Rok Sabjan
- 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
|