[c-nsp] ICMP Query : Duplicate Reply

[Gert Doering]

HI,

On Sat, Mar 18, 2006 at 06:56:30AM -0000, Gangasagar Amula wrote:
> The below output was captured when we are pinging from one vlan to other vlan.
> We have 4006 Switch involved in between.
> 
> ---------------------------------------------------------------- 
> 64 bytes from 10.176.0.51: icmp_seq=6 ttl=127 time=26.7 ms (DUP!)
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=11.1 ms
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=11.2 ms (DUP!)
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=11.6 ms (DUP!)
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=11.6 ms (DUP!)
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=12.0 ms (DUP!)
> 64 bytes from 10.176.0.51: icmp_seq=7 ttl=127 time=12.1 ms (DUP!)

This very much looks like you have a loop in your ethernet topology
somewhere - ports are connected together that should not be, and for 
some reason, spanning tree isn't disabling the ports.

> CPU utilization for five seconds:  85.63%
>                       one minute:  77.70%
>                     five minutes:  75.19%

As people have suggested in the other thread: most likely the high CPU
is related to the packet loop.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de