Experimental Physics and
Industrial Control System

Hi- anyone know what these "invalid UDP request" messages mean?  They've 
just started appearing during the boot of an mv2700/R3.13.10 vxWorks IOC. 
The numbers after "gtw01:" appear to be port numbers mostly associated with 
edm processes on solaris machines.

thanks,
Mike

-----

# Start EPICS
iocInit( getenv("RESOURCE_DEF") )
############################################################################
Starting###   iocInit
@(#)EPICS IOC CORE built on Oct  9 2006
###  @(#)Version R3.13.10 $2004/04/15 13:36:02$
############################################################################

iocInit: All initialization complete
CAS: invalid (damaged?) UDP request from gtw01:46316 ?
CAS: invalid (damaged?) UDP request from gtw01:39871 ?
CAS: invalid (damaged?) UDP request from gtw01:46316 ?
CAS: invalid (damaged?) UDP request from gtw00:36836 ?
CAS: invalid (damaged?) UDP request from gtw00:44255 ?
CAS: invalid (damaged?) UDP request from gtw01:45271 ?
CAS: invalid (damaged?) UDP request from gtw00:45758 ?
CAS: invalid (damaged?) UDP request from gtw01:46316 ?
...

Replies:

RE: "invalid UDP request" during boot Jeff Hill

References:

Re: VxWorks time() Ralph Lange

Re: VxWorks time() Andrew Johnson

Navigate by Date:

Prev: Re: problem in communicating to the GPIB device with ASYN4-6 Emmanuel Mayssat

Next: RE: "invalid UDP request" during boot 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: VxWorks time() Andrew Johnson

Next: RE: "invalid UDP request" during boot 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