Per Port Logging

[m-rosebury]

Does anybody know if it is possible to do syslog logging on a per port basis? This is to avoid getting the "%LINK-4-ERROR: ... is experiencing errors" messages on certain ports where customers set the duplex incorrectly. "no logging event link-status" seems to have no effect on this and setting the logging to a lower level would avoid getting the messages on ports where they need to be seen.

The switches in question are 3500XL IOS 12.0(5)WC8.

Thanks

Matt

[owillins]

I haven't seen any examples of per port logging but you can configure the ports with autonegotiation so that the mismatches do not occur. Here is a troubleshooting doc that might help.

http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a0080094781.shtml

[Kevin Dorrell]

Setting the ports to autonegotiation does not guarantee that you will not get a duplex mismatch, and might even prevoke it. Autonegotiation works correctly only it the other side is autonegotiating. The link should be auto-auto, or forced-forced.

(There is one other combination that works: auto-half. This is because the default for autonegotiation is half-duplex.)

Kevin Dorrell

Luxembourg

[m-rosebury]

I know how to set auto-negotiation thanks it is our customer that does not.

Thanks

Matt

[Kevin Dorrell]

As far as I know, there is no way to set error syslogging selectively by port. The command you suggest "no logging event link-status" concerns only log messages due to the port going up and down. The only thing I can suggest is filtering the messages at the syslog server.

The error rate has to be really significant before you get the LINK-4-ERROR message. Not sure what the exact figure is ... does anyone out there know? And the sampling interval?

Or have a word with your customer, making it clear that they will get better performance if they set their duplex correctly!

Kevin Dorrell

Luxembourg