"logging monitor debugging, logging buffered debugging..."

[MicJameson1]

Hello.

I'm trying to understand what this ASA5525 is logging, and to where.

May you please inform me what the below config lines mean?

If the below config lines mean debugging is presently on, shouldn't the below config be mostly removed to stop stress on the CPU? 

---

logging monitor debugging
logging buffered debugging
logging trap debugging
logging asdm debugging
logging class auth console debugging
logging class webvpn console debugging
logging class ssl console debugging

Thank you.

[Rob Ingram]

@MicJameson1 that's bad, that configuration is providing debug to console, asdm gui, syslog and local log buffer, that'll likely crash the ASA.

[MicJameson1]

Thank you.

All things being equal, if this was your ASA, what would your logging config look like?

[Rob Ingram · Accepted solution]

@MicJameson1 no debug logging, this should be used as an exception, for a short period and then disabled.

Best practice is disable logging to console/monitor, enable log buffer. Send logging information to syslog (if you have one).

[MHM Cisco World]

I initiate traffic from R1 to R2 and then use 
show conn  
and 
show lcoal-host 10.0.0.1 <<- R1

you can see there is Conn 

what I think is the traffic is not direct from ISR4K to ASA 
do in ISR4K
show ip route x.x.x.x longest <<- x.x.x.x is the destination 
check the egress interface is interface toward the ASA or not

[MicJameson1]

Hi MHM. 

This is very helpful indeed. I am placing your text in my notes.

--I think you placed this in wrong thread.--

Anyway, I resolved that ticket-- real issue was NOT at network level-- it was application level, but strange problem was that I cleared the ACL issue mid-way into troubleshoot, but issue persisted= there was 2 issues= 1 network, then 1 application layer.