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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

What level of syslogging for duplex mismatch?

I have syslogging at notification level and informational level on various devices throughout my network. However, even though it shows up with a "show logging" I am not getting a syslog event sent me to when there is a duplex mismatch? I have discovered two mismatches by doing a show logging on the switch that were not sent as messages. Does anyone have any experience with this? It is confusing.

  • Network Management
1 REPLY
Blue

Re: What level of syslogging for duplex mismatch?

You're seeing it in "show logging" because that's controlled by "logging buffered [syslog level]". To have it sent to your syslog server, adjust "logging trap [syslog level]".

http://www.cisco.com/univercd/cc/td/doc/product/software/ios11/dbook/dintro.htm

Limiting Messages to a Syslog Server

To limit how many messages are sent to the syslog servers, use the logging trap router configuration command. The full syntax of this command follows:

logging trap level

no logging trap

The logging trap command limits the logging messages sent to syslog servers to messages with a level up to and including the specified level argument. The level argument is one of the keywords listed in Table 1-1.

To send logging messages to a syslog server, specify its host address with the logging command.

The default trap level is informational.

The no logging trap command disables logging to syslog servers.

The current software generates four categories of syslog messages:

Error messages about software or hardware malfunctions, displayed at the errors level.

Interface up/down transitions and system restart messages, displayed at the notification level.

Reload requests and low-process stack messages, displayed at the informational level.

Output from the debug commands, displayed at the debugging level.

601
Views
0
Helpful
1
Replies