• Creator
  • #4094641

    Cisco Logs

    by Ron St Juste ·


    Good Afternoon,

    Newbie here. I ran into an issue with 4 stacked Cisco 3850’s where the 4th switch was displaying amber lights and connected machines were not getting any connectivity. I had to manually power down all for devices and restart. Eventually performance returned, but now I would like to perform a Root Cause Analysis and need to know if there are logs I can review to determine to cause of the switch hanging.

    Does anyone know if this is possible and what to do to retrieve these logs.


You are posting a reply to: Cisco Logs

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Answers

  • Author
    • #4096109

      SSH & CLI – cisco log

      by msd82004 ·

      In reply to Cisco Logs

      Yes, Cisco 3850 switch logs can be retrieved for root cause analysis. It can be useful to review the switches’ logs for information regarding their operation, errors, and issues.

      SSH or the command-line interface (CLI) are the two ways to retrieve Cisco 3850 logs. Here are the steps to follow:

      SSH or console cable to connect to the switch.

      Provide the appropriate credentials and enter the privileged EXEC mode.

      Type configure terminal to enter global configuration mode.

      Use the following command to enable logging: logging buffered <size> (replace <size> with the desired buffer size, for example, 4096).

      Show logging displays the buffer logs. Most recent log entries will be displayed.

      Save the logs to a file for further analysis by using the show logging | redirect <filename> command (replace <filename> with the desired file name).

      Note: Logs are saved to flash memory by this command.

      You can then copy the log file to an external device using the copy flash:<filename> <destination> command (replace <filename> with the log file name and <destination> with the destination location, such as an FTP or TFTP server).

      Check the logs for errors, warnings, or events that preceded the switch hanging or amber lights. Using this information, you can identify the root cause.

      Typically, Cisco switches store logs in different categories, including systems, interfaces, and spanning trees. By focusing on the relevant log category, you can narrow down your analysis.

      You can find more details on logging commands and options in the Cisco documentation specific to your switch model.

      I think it might be work !!

Viewing 0 reply threads