Debug not showing up at the console on new 4507s.

[Charles Hill]

Debug is not showing up on the console.  I have configured logging console.  My older switches, if an interface goes down or is brought up, it shows up on the console, but not on the new 4507s.  Any help would greatly be appreciated.

WS-C4507R-E

cat4500e-ipbase-mz.122-53.SG2.bin

TG-4507#sh logging
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes,
0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

    Console logging: level debugging, 82 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging:  level debugging, 1 messages logged, xml disabled,
                     filtering disabled
    Exception Logging: size (8192 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level informational, 84 message lines logged

Log Buffer (4096 bytes):

Mar  3 21:07:03.494: %SYS-5-CONFIG_I: Configured from console by chill on consol
e
PTG-4507#

[Richard Burts · Accepted solution]

I am not clear what the real problem is. The title of your post suggests that logging on the console is not working. But this line from the output that you posted looks like the logging to the console is working:

Console logging: level debugging, 82 messages logged

So if you are in a session on the console, and you go into config t, and then you exit/end from config t, do you get a message on the console? If so then logging to the console is working.

From reading you post I can guess that your real issue is that when interfaces go down or come back up that you are not getting the syslog messages that you expect. If that is the case then try this command configured under the interface:

logging event link-status

HTH

Rick

[Charles Hill]

Thanks for the response Rick.

Enabling "logging event link-status global" resolved my issue.

[johnlloyd_13]

hi,

try to enable this command and test again.

4507#terminal monitor