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: | RE: PV gateway renders PVs as disconnected |
From: | "Abdalla Ahmad" <[email protected]> |
To: | Ralph Lange <[email protected]>, EPICS Tech Talk <[email protected]> |
Date: | Tue, 17 Apr 2018 11:58:03 +0000 |
Hello all Thank you for your suggestions and sorry for not following-up with this case. The setup is as follows: We have 4 VLANs: Office, machine and 2 beamlines. The plan is to transfer machine PVs to the other VLANs, and both VLANs to the machine. So we have the following connections: 1.
Machine => Office 2.
Machine
ó XAFS 3.
Machine
ó IR And any beamline that follows will follow the same setup.
The server hosting the gateways is a virtual server with one network interface seeing all VLANs through network rules set by the network engineers. Each gateway will ignore requests from the other VLANs. Right now I am experimenting with multiple gateways setup; 1 gateway for each connection so we have a total of 5 gateways. Here is an attempt for configuration gateway_home="/home/user/gateway/machine_office/" gateway_cip="list of ip addresses go here" gateway_signore="10.1.1.20" #Example host to ignore. Works fine gateway_putlog="caput.log" gateway_log="gateway.log" gw_test=$(ps aux | grep /gateway | wc -l) if [[ "$gw_test" -lt 2 ]]; then echo "True" gateway -home "${gateway_home}" \ -log "${gateway_log}" \ -putlog "${gateway_putlog}" \ -cip "${gateway_cip}" \ -signore "${gateway_signore}" \ -server else echo "Gateway is already running." fi This setup works fine and I am configuring another gateway for such a disconnection issue. I have few questions: 1.
I have learned from the video that, as I mentioned, each gateway will ignore the other gateways using the "signore" option. The
broadcast address won't work and I have to add manually each host from each VLAN and with the increasing number of hosts this process is totally cumbersome. Isn't there any easy way to do this? 2.
What does the "sip" option exactly do? And is there any other options that I must use? 3.
Is it necessary to have a gateway setup per connection? Is there a better setup for our case? Looking forward for your suggestions!
J Abdalla From: [email protected] [mailto:[email protected]]
On Behalf Of Ralph Lange Hi Abdalla, How is your network context/setup? From your mail we know that there are multiple networks. You write that your virtualized Gateway host only has one network interface. Is that one (virtual) "physical" interface, or one logical interface? In other words: does that Gateway
machine have a VLAN setup? How are data producers (IOCs) and data consumers (clients) distributed over the different LANs you mention? Let me say that in such a multi-network setup it is very unlikely that a Gateway works without configuration. Also, unless there is a clear separation between networks with producers and networks with consumers (without overlap), you are likely to need more than one Gateway instance. Have you read the "Gateway Configurations" chapter in the Gateway User Guide on
https://epics.anl.gov/extensions/gateway/index.php? Cheers, On Wed, Mar 28, 2018 at 2:33 PM, Abdalla Ahmad <[email protected]> wrote:
|