Re: RE: Sniffing out a firewall problem

[Peter Lukas <plukas () oss uswest net>]

I was really trying more to give an example of the problem flags that can
be gathered locally with netstat before charging out and assessing other
devices for problems. Typically, that information could be gathered to
generate a report of troubles on the network when combined with other
factors (traffic amounts, duplex settings, etc).

Next time, I'll be sure to pipe the message through /bin/lawyer to avoid
a semantics debate with the peanut gallery, though...  ;-)

Peter

On Sat, 3 Nov 2001, Ryan Russell wrote:

> On Sat, 3 Nov 2001, Peter Lukas wrote:
>
> > You'll get some pretty useful stats. Typically, any system with Ierrs,
> > Oerrs or Collis will be experiencing a problem. Check caples, duplex
> > settings and of course, the card /switch port itself.
>
> Please be careful about making blanket statements about collisions
> automatically meaning problems.  On any connection that is supposed to be
> half-duplex Ethernet-style, collisions are perfectly normal, and you have
> to measure collisions against total traffic to even have a rudimentary
> problem measurement.
>
> Sorry, it's a pet peeve of mine.  When I used to be primarily a network
> engineer, I would have systems administrators come to me and report that
> the system was reporting collisions, please fix the network.  I'd reply
> that it was running half-duplex.  <blank stare>
>
>                                       Ryan

_______________________________________________
firewall-wizards mailing list
firewall-wizards () nfr com
http://list.nfr.com/mailman/listinfo/firewall-wizards