The logging buffer by default varies from platform to platform, as does the logging level associated with it.

If you would like to log to your syslog and to your buffer concurrently, you can do that.

You could add the command 'logging buffered 1000000 debugging'. This would add 1 MB of a logging buffer at the highest level. There's a good chance right now that the logging buffer is set to only log errors and lower rather than debugging.

hth,

nick

hi,

thanks for reply if i use the command

'logging buffered 1000000 debugging'

would this start debugging

ON on switch,will it put load on cpu?

also if i go to config mode and come bACK

and do sh log will that show that i went to

config mode by vty?

thanks

Mahesh

If Nick had read carefully in your original post he would have seen this line:

Buffer logging: level debugging, 49 messages logged

which clearly shows that your logging buffer is already operating at level debugging.

To answer your other question, no, setting the logging level to debugging will not start a debugging process and will not cause any extra load on the CPU. All that it does is to enable writing messages to the logging buffer and to control the severity level of messages that will be accepted in the logging buffer. And if you go into config mode and exit from config mode then it should put a line into the logging buffer showing that.

HTH

Rick

Yes, but still very common :)

-nick

Hi Mahesh,

Logging buffered only allows for the router to use some RAM to put debugs. It's like opening a cardboard box. You're not putting things in it, but you can. And this is a 1 MB cardboard box. Logging to the buffer creates almost no CPU utilization. I've done 'debug all' on routers with this before (albeit not much traffic on them) and the CPU utilization was below 10%.

Yes, going to config mode and exiting is an easy way of testing logging.

hth,

nick

Hi

thanks for great reply