Jeff Hill wrote:
>
> > >2000-10-23,09:35:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> > >2000-10-23,09:43:45: 0x78dd64 (tNetTask): arptnew failed on se
>
> Perhaps these errors are resulting from attempts by arp to build an
> Ethernet address <=> IP address association, but there is already
> an inconsistent entry in its tables. I would type "arpShow" to see
> if there are configuration problems (possibly related to a back plane
> network).
There is a Wind River SPR 24397 that might be vaguely relevent to this: "A
networked target does not respond to ARP requests for proxy entries
created with arpAdd(host, eadr, ATF_PUBL)" which is fixed by the Tornado
2.0 Cumulative Patch 3 available from WindSurf. However be sure to read
the Special Instructions to this patch as it states "The fix for SPR 24397
breaks the Proxy Arp Server" unless you follow the additional instructions
given. If you're using shared memory backplane networking it's very
likely that you'll be relying on the Proxy Arp server, so you'll want to
visit the WRS FTP site, but it then looks like you don't get the patch for
this problem! I don't understand it completely myself, and I haven't
installed T2CP3 for ASD as a result.
- Andrew
--
Every great idea appears crazy to start with.
- References:
- RE: Tornado/2.0 error message Jeff Hill
- Navigate by Date:
- Prev:
RE: Tornado/2.0 error message Jeff Hill
- Next:
Looking for BURT request file example Martin Pieck
- 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: Tornado/2.0 error message Jeff Hill
- Next:
Looking for BURT request file example Martin Pieck
- 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
|