Hi Matthew,
Actually the issue is not on client side. CArepeater is used for client
applications to share the beacon UDP port (e.g. EDM screens and also
IOCs because they can be clients to one another...). We are wondering
here, how to host multiple soft IOCs on the same computer, possibly
sharing the same UDP CA request port. For broadcast UDP packets this is
not really an issue, because Linux UDP stack is implemented in such a
way that it by default fans out the packet to all services running on
that particular port. Though, I'm not convinced that this is really
standard UDP stack behavior and that we have any guaranties it will
still work with future versions of Linux kernel. The second problem is
that at some stage ITER may also want to configure some client to send
unicast requests. Then it will for certain not work on Linux because in
that case only one IOC will in fact receive the request.
I see a few possibilities here:
o) Ignore the problem and assume that in ITER broadcast UDP will always
be used and there will be no problems in future. This is also ok if we
assume that at some stage they will switch to EPICS v4 where port
sharing will no longer be an issue.
o) Do something with modular epics and have only one IOC application
running, hosting all the required IOCs as modules.
o) Assign different ports to different IOCs. This will very likely
course cause a lot of other manageability issues.
Cheers,
Anze Zagar.
On Fri, 2010-09-24 at 11:22 +0100, [email protected] wrote:
> Here at ITER, t
> Hi Pam,
>
> We use the CArepeater UDP server on our linux hosts.
>
> http://www.slac.stanford.edu/comp/unix/package/rtems/epics-3.14.6/base/html/CAref.html#Repeater
>
> Is that what you need?
>
> Cheers,
> Matthew
>
>
> ______________________________________________________________
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Pam Gurd
> Sent: 24 September 2010 09:18
> To: EPICS tech-talk
> Subject: Soft IOCs and Port Numbers
>
>
>
> hey're asking me about how to manage the problem of ensuring
> that each of the soft IOCs running on a host has a distinct
> port number.
>
>
>
> What have people done to solve this problem?
>
>
>
> Thanks.
>
>
>
> Pam.
>
>
>
>
>
>
>
> --
>
> This e-mail and any attachments may contain confidential, copyright
> and or privileged material, and are for the use of the intended
> addressee only. If you are not the intended addressee or an authorised
> recipient of the addressee please notify us of receipt by returning
> the e-mail and do not use, copy, retain, distribute or disclose the
> information in or attached to the e-mail.
> Any opinions expressed within this e-mail are those of the individual
> and not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for
> any damage which you may sustain as a result of software viruses which
> may be transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in
> England and Wales with its registered office at Diamond House, Harwell
> Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United
> Kingdom
>
>
>
- Replies:
- RE: Soft IOCs and Port Numbers Jeff Hill
- References:
- Soft IOCs and Port Numbers Pam Gurd
- RE: Soft IOCs and Port Numbers matthew.pearson
- Navigate by Date:
- Prev:
RE: Soft IOCs and Port Numbers matthew.pearson
- Next:
RE: Soft IOCs and Port Numbers Jeff Hill
- 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: Soft IOCs and Port Numbers matthew.pearson
- Next:
RE: Soft IOCs and Port Numbers Jeff Hill
- 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
|