Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Sending continuous Debug level syslog ...good?

This thread has been viewed 0 times
  • 1.  Sending continuous Debug level syslog ...good?

    Posted Jan 04, 2013 02:36 PM

    This is more of a is this ok kind of question

     

    I need to enable debug level syslog for a particular AP and send it out to a syslog server until we can reproduce an issue.

     

    Now I know it is not best practice to leave debug level logs on all the time on the controller, etc.. but what problems may I run into if I do this...

     

    I may have to keep this going for example like 2 weeks...



  • 2.  RE: Sending continuous Debug level syslog ...good?

    EMPLOYEE
    Posted Jan 07, 2013 09:26 AM

     

    in my experience, syslog debug level can be a bit excessive, and the majority of the messages are not terribly

    helpful in daily monitoring.

     

    i'd stick to WARN or INFO level for daily use.

     

     It is good practice to have syslog servers configured on all network devices, and be prepared to enable

    appropriate and useful levels of syslog messages for troubleshooting purposes.

     

    And as always, SNMP traps and any level of syslog messages correlated at a central server are an excellent source

    of chronological event information covering the entire network.



  • 3.  RE: Sending continuous Debug level syslog ...good?

    Posted Jan 08, 2013 10:46 AM

    Thanks for the feedback on this.

     

    I will leave it as is for now as the logs are being analyzed by someone else. I'd rather give them everything and they can filter out what they do not need.