Thanks for the reply. One of the guys with us actually put a sniffer (an actual hardware suitcase) on the network, but didn't notice anything unusual. Like you, I suspected that it might have been a poorly configured app or some broadcast traffic. If the trouble was showing up at the packet level, the guy looking at the sniffer couldn't see it. I didn't look at it personally since we were all looking at different potential problems and comparing notes. When we go to put in the 3550, I'll probably throw my own sniffer on the line to catch some traffic if the problem reoccurs.
At 07:09 PM 12/21/2002 -0600, you wrote: >On Sat, 2002-12-21 at 13:10, Craig Columbus wrote: > > I worked on a network move for a brokerage company last week and > > encountered a VERY strange problem. > >sounds like a broadcast problem to me... did you happen to capture any >traffic? what were the interface counters like? when did the slowdown >start? suddenly or gradually? I'm betting on a poorly-configured or >poorly-designed app assuming a /24 subnet or something, but that's a >stretch too. > >My approach would be to capture some traffic with Ethereal and figure out >1) if it's a broadcast problem, and 2) if so, what app. > >If it's not broadcasts, the next question is whether or not it's a traffic >thing at all. Again, captures might provide a clue. Otherwise, you have >to narrow down *why* things slow down. find the bottleneck - is it really >on the wire between the computer and the first switch, or is it between >server and switch, etc. > >Sounds like fun! keep us posted. > > -sd Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59708&t=59682 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
