EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: CA Errors, but everything works fine !!!
From: "Jeff Hill" <[email protected]>
To: "'Emmanuel Mayssat'" <[email protected]>, <[email protected]>
Date: Mon, 8 Aug 2005 09:12:03 -0600
Hello Emmanuel,

There are two IP addresses in the diagnostic attached {192.168.1.202,
192.168.1.201}. The source ports vary, but appear to be monotonically
increasing as would be the case with ephemeral port assignments. Therefore,
I am not guessing packet damage is the cause.

I would have a close look at what types of programs are being run at
{192.168.1.202, 192.168.1.201}. You can use netstat to determine what ports
are currently in use, and there are typically OS dependent mechanisms to
identify what process is using what port numbers.

I notice in the diagnostic below that the CA protocol element being rejected
is a CA beacon message. I suspect that someone on your LAN has configured a
CA server to send beacons to the CA server port (an invalid configuration).
More details are in the CA reference manual.

Jeff

> -----Original Message-----
> From: Emmanuel Mayssat [mailto:[email protected]]
> Sent: Saturday, August 06, 2005 3:05 PM
> To: [email protected]
> Subject: CA Errors, but everything works fine !!!
> 
> Hello,
> 
> When I start my IOC, everything works fine.
> Nevertheless, I get the following error/warning messages:
> 
> CAS: Request from 192.168.1.202:33453 => cmmd=13 cid=0x32a type=11
> count=5080 postsize=0
> CAS: Request from 192.168.1.202:33453 =>  available=0xc0a801ca  N=0
> paddr=0x87b7970
> CAS: invalid (damaged?) UDP request from 192.168.1.202:33453 ?
> CAS: request from 192.168.1.201:32836 => "invalid (damaged?) request
> code from UDP"
> CAS: Request from 192.168.1.201:32836 => cmmd=13 cid=0x45f type=11
> count=5074 postsize=0
> CAS: Request from 192.168.1.201:32836 =>  available=0xc0a801c9  N=0
> paddr=0x87dbf64
> CAS: invalid (damaged?) UDP request from 192.168.1.201:32836 ?
> CAS: request from 192.168.1.201:32837 => "invalid (damaged?) request
> code from UDP"
> CAS: Request from 192.168.1.201:32837 => cmmd=13 cid=0x45f type=11
> count=5072 postsize=0
> CAS: Request from 192.168.1.201:32837 =>  available=0xc0a801c9  N=0
> paddr=0x87dbf64
> CAS: invalid (damaged?) UDP request from 192.168.1.201:32837 ?
> 
> 
> Any idea of what is going on ?
> --
> Emmanuel



References:
CA Errors, but everything works fine !!! Emmanuel Mayssat

Navigate by Date:
Prev: CA Errors, but everything works fine !!! Emmanuel Mayssat
Next: msi command for building synApps 5.1 J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: CA Errors, but everything works fine !!! Emmanuel Mayssat
Next: msi command for building synApps 5.1 J. Lewis Muir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·