Re: ptrace results please look and diagnose

John Storms (jstorms@livingston.com)
Thu, 31 Jul 1997 07:34:26 -0700

This looks like you IRX-211 at 206.170.175.21 trying to reset a TCP
session. TCP/1642 is the socket used by PortMaster deamon (in.pmd) so
something on your IRX211 is trying to communicate to a PMD on 206.170.176.6
which is probably your host setting on the 211. To fix this remove
PortMaster login and device services from all ports. I'm betting its on
the s0 port. Remove these and you'll see this traffic go away.

inyo> TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack
>0x656, win 0, RST ACK

For short term relief you can probably reset the network connection using
the 'show netc' and the 'reset nXXX' commands.

At 09:37 PM 7/30/97 -0700, Rick Wagner wrote:
>
>INYO is an IRX-114 connected with a point to point circuit to a pop with
>another IRX-114 FHAUB. 207.212.142.2 is FHAUB I ran the ptrace on INYO
>which is 207.212.142.1 INYO is ether connected to 206.170.175.21 which is
>an IRX-211 and is connectred to my backbone T-1
>
>I have tons of excessive traffic on my ptp from inyo to fhaub and I am
>trying to diagnose the situation. So I created the filter below...
>in seconds it ran pages and pages of the same output.
>Do I have something set up wrong ????
>Thanks
>
>inyo> sho filter i
> 1 permit 207.212.142.2/32 0.0.0.0/0 ip
> 2 permit 206.170.175.21/32 0.0.0.0/0 ip
>inyo>
>inyo> ptrace i
>Packet Tracing Enabled
>inyo> TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack
>0x656, win 0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>TCP from 206.170.175.21.1642 to 206.170.176.6.1011 seq 5D6, ack 0x656, win
>0, RST ACK
>
>
>

---
jstorms@livingston.com
Diplomacy:  The art of saying good doggie
while seaching for a big rock.