Re: [nsp] Traceroute inconsistencies

From: Nick (nick@arc.net.my)
Date: Wed Feb 13 2002 - 00:30:18 EST


Thanks for your replies. After much investigation and strips of paracetemol:

The only 'load-balancing is from 200.100.225.66 <BR1> to
200.100.225.3/200.100.225.195<SW1>.
Then to 200.100.224.42 <BR2> to 200.100.224.42 <AR1>.
>From here onwards it is a single link all the way to
200.100.255.8/200.100.255.12 <samebox>.

But from 200.100.224.42<AR1> to 200.100.255.8<samebox> there are hops 4 and
5 included while to 200.100.255.12<samebox> there was none.

We found that there was an arp leak/loop for 200.100.255.12<samebox> from
the customers wireless bridge network which was included in the <AR1> arp
cache. Some bad cost-cutting cabling on their wireless bridge and switch was
fixed and the arp cache on <AR1> cleared and everything back to normal.

Thanks guys.

-nick



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:33 EDT