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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | PV Access issue when moving between subnets |
From: | Jim Larsson via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 23 Aug 2023 13:48:41 +0000 |
Hello Tech Talk,
We have encountered an issue with pv access when a host running an ioc switch network. The host is a mini-pc and obtains a new ip from dhcp. After the switch, the pvs from the ioc are not accessible with pv access, e.g., pvget. However, the pvs can still be obtained with channel access (both before and after switching network). Some findings after switching network: => Pv access works if the ioc is restarted. => Pv access works if executing 'stopPVAServer' and 'startPVAServer' in the ioc shell. => Pvget locally doesn't work. => pvget to an ioc on a different host on the network works. => Channel access continuous to work after switching network. Versions: pvAccess server v7.1.6 epics-base v7.0.7 # ioc shell
> pvasr EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075 EPICS_PVAS_BEACON_ADDR_LIST = EPICS_PVAS_AUTO_BEACON_ADDR_LIST = YES EPICS_PVAS_BEACON_PERIOD = 15 EPICS_PVAS_BROADCAST_PORT = 5076 EPICS_PVAS_SERVER_PORT = 5075 EPICS_PVAS_PROVIDER_NAMES = QSRV local Has anyone else experienced something similar? Preferably we would like to find a solution so that it is not required to restart the ioc for pv access to work (same as channel access). Kind regards,
Jim
|