4.1.5 having trouble taking to 4.3.2

4.1.5 having trouble taking to 4.3.2

Post by Rich Olve » Wed, 10 Feb 1999 04:00:00



We've just added a H50 running 4.3.2.   I rlogin to it from my office
with a PowerPC running 4.1.5, and that's where I work.   Problem is that
communications freeze up intermittenly.  IE I'm in the middle of doing
something and everything stops.  At that point (from another window) I
can't ping the H50 from the PowerPC.  Here's the interesting part.  If I
go to the H50 and ping back to the PowerPC, the ping always goes
through, and then communication is restored in both directions.
        I've been talking to IBM support, but we haven't resolved the problem
yet.  We've looked into the issue of IP address conflicts, but haven't
found anything.  
        # arp -d 'IP address of the PowerPC' also restores communications.
Which is supposed to mean that the opcache is not being updated
correctly.  

That's about where we are.  

Any suggestions will be appreciated


--

   ,__o      ,__o      ,__o              +
   \ <,      \ <,      \ <,           +
(*)/ (*)  (*)/ (*)  (*)/ (*)       +
++++++++++++++++++++++++++++++++++
Rich Olver
Vector Seismic Processing
Denver, Co.
+++++++++++++++++++++++++++++++++++++++++++

 
 
 

4.1.5 having trouble taking to 4.3.2

Post by Rob Wilkinso » Wed, 10 Feb 1999 04:00:00


Are you running named..If so I suppose that could change your routing
somewhat??? I had a similar problem..I stopped the named and the problem
went away...Hope that helps..

>We've just added a H50 running 4.3.2.   I rlogin to it from my office
>with a PowerPC running 4.1.5, and that's where I work.   Problem is that
>communications freeze up intermittenly.  IE I'm in the middle of doing
>something and everything stops.  At that point (from another window) I
>can't ping the H50 from the PowerPC.  Here's the interesting part.  If I
>go to the H50 and ping back to the PowerPC, the ping always goes
>through, and then communication is restored in both directions.
> I've been talking to IBM support, but we haven't resolved the problem
>yet.  We've looked into the issue of IP address conflicts, but haven't
>found anything.
> # arp -d 'IP address of the PowerPC' also restores communications.
>Which is supposed to mean that the opcache is not being updated
>correctly.

>That's about where we are.

>Any suggestions will be appreciated


>--

>   ,__o      ,__o      ,__o              +
>   \ <,      \ <,      \ <,           +
>(*)/ (*)  (*)/ (*)  (*)/ (*)       +
>++++++++++++++++++++++++++++++++++
>Rich Olver
>Vector Seismic Processing
>Denver, Co.
>+++++++++++++++++++++++++++++++++++++++++++