[lug] Syslog

[charles at lunarmedia.net]

lance errors on ciscos will often be the first indication that you need to
replace your cabling or you're exceeding ethernet distance specs. another
common cause of late collision errors is duplex mismatches. your host is
running 100/half and your switch is set to 100/full. ciscos don't manage
this well with some nics and even though you have it set to
auto-negotiate, you may need to hard set it.

sorry, but linux is definitely doing its job here. you can't blame the os
for logging the errors that your ciscos are sending to it :-)


On Mon, 15 Jan 2001, Stephen G. Smith wrote:

> I am sorry if this turns out to be a non linux issue.
>
> I have had a RH 6.2 machine running as a syslog server for approx 6 months
> with no errors.
> I have it do logging for 8 cisco routers and 1 cisco PIX.
>
> I am for some reason now getting the following error from 2 routers
> on a regular basis and was wondering if anyone could help me
> figure out what the problem is..
>
> 2001.15.01-15:52:37 host.mydomain.com, <189>14809: 4w4d: %LANCE-5-LATECOLL:
> Unit 0, late collision error
>
>
> Thanks,
>
> Stephen
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>