Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Detecting & Alerting on Interface Errors / improperly set duplex

All,

Due to auto-negotiation problem between our Cisco Cat5000 switches and our workstation NIC's, we've hard coded all switch ports to 100/Full. Occasionally, we will have a user plug in a new machine or NIC that is set to 100/Auto. In these cases the duplex negotiation usually fails -- the NIC selects half and the switch is set to full. The result is extremely poor performance and lots of errors occuring very rapidly on the switch port: Align-Err, FCS-Err, and Runts.

I'm looking for a way to monitor the ports on the switch to detect when these errors begin to occur and then alert me to their presence.

Thanks,

Pete

1 REPLY
Silver

Re: Detecting & Alerting on Interface Errors / improperly set du

Pete,

You can do this with either your syslog or trap functions. I believe all link messages are sent with Severity 4. See the following links for more information.

NMS Best Practices (see logging)

http://www.cisco.com/en/US/partner/products/hw/switches/ps663/products_tech_note09186a0080094713.shtml

Common Error Messages on Catalysts:

http://www.cisco.com/warp/customer/473/34.shtml

Example log message (this is from a 6500 but it would be simular to 5000)

Dec 24 04:33:05.374: %PM_SCP-SP-4-LCP_FW_ABLC: Late collision message from module 3, port:010

Dec 24 04:33:56.398: %PM_SCP-SP-4-LCP_FW_ABLC: Late collision message from module 3, port:05

Hope this helps,

Don

95
Views
0
Helpful
1
Replies
CreatePlease login to create content