Hi Ralph
Thank you very much. I managed to configure two gateways between the machine and a beamline (1 for each path), the gateway options I configured are:
1.
Home
2.
CIP
3.
SIGNORE
4.
Put log
5.
Log
6.
Prefix
I had to configure UDP broadcasts on the server using this link:
https://wiki-ext.aps.anl.gov/epics/index.php/How_to_Make_Channel_Access_Reach_Multiple_Soft_IOCs_on_a_Linux_Host because I was having a problem that when 2 gateways are running, one of them will be actually working and serving PVs.
I still have some questions and issues:
1.
Regarding SIP and SIGNORE It is still not clear for me. If I have hosts defined in SIP does that mean the rest are ignored? And
if I have hosts in SIGNORE does that mean the rest are being served?
2.
For some reason the gateway.restart script does not work. I have to kill the gateway and start it again for the changes to take
effect.
3.
SIP did not work for me, whenever I set it I get the attached log (gw.txt) and the gateway will become unusable.
4.
Attached also is the access file that I load into the gateway:
a.
If the IOC itself has no ACF file loaded, the gateway ACF works just fine. And if it is not loaded the gateway will provide read
only.
b.
If the IOC has an ACF file loaded, the gateway ACF will not work, i.e., no write access through the gateway. In the IOC's ACF
file (similar to the attached one) I added the gateway server's host and usernames. I even added the host and usernames of the host that is actually writing to the PV through the gateway but nothing works.
Best Regards,
Abdalla.
From: Ralph Lange [mailto:[email protected]]
Sent: Tuesday, April 17, 2018 4:00 PM
To: EPICS Tech Talk <[email protected]>
Cc: Abdalla Ahmad <[email protected]>
Subject: Re: PV gateway renders PVs as disconnected
Hi Abdalla,
You're definitely on the right path!
For your five data paths, you are currently using five Gateways in what I would call the "mesh" configuration, i.e. one Gateway for each data path. To simplify the setup, you could shrink the solution down to a "star", where each of the
networks is served by exactly one Gateway. For such a "star", you have two options: all Gateways point outwards (i.e. each network "sees" exactly one Gateway which is serving data from all other networks) or all Gateways point inwards (i.e. each networks sees
one Gateway per other network). The preferred option depends on how often the configuration is changed and how much Gateway restarts are affecting your users.
SIP and CIP are the central configuration options.
SIP = Server IP defines where the Gateway serves data to, i.e. where its clients are.
CIP = Client IP defines where the Gateway is getting data from, i.e. where its IOCs are.
SIP addresses may be multiple, but always have to be specific addresses.
CIP addresses may include broadcast addresses to reach many IOCs at a time.
Given three networks A B C (with broadcast address .255) and a Gateway host that is connected to all of them using addresses A.a B.b and C.c
GatewayA: SIP=A.a CIP=B.255 C.255
GatewayB: SIP=B.b CIP=A.255 C.255
GatewayC: SIP=C.c CIP=A.255 B.255
Star inwards:
GatewayA: SIP=B.b C.c CIP=A.255
GatewayB: SIP=A.a C.c CIP=B.255
GatewayC: SIP=A.a B.b CIP=C.255
If you mix the two concepts, you will get into trouble (PVs available on multiple routes).