cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3774
Views
0
Helpful
3
Replies

Catalyst 3850 Error Log

kshong
Level 1
Level 1

Hello Everybody.

I have some problems with Catalyst 3850.

I got logs from C3850 Switch, but I couldn't fine the meaning of logs.

Does anybody know what is the meaning of the logs?

LOG-1(C3850)

.May 27 13:28:47: FAIL: 1 xinetd[3754]:  brelay_service connections per second from=10.0.2.0

.May 27 13:29:17: Activating service brelay_service 1 xinetd[3754]: er second from=10.0.2.0

.May 28 11:41:47: %LINK-3-UPDOWN: Interface Vlan2210, changed state to down

.May 28 11:41:49: %LINK-3-UPDOWN: Interface Vlan2210, changed state to up

.May 28 17:27:47: %LINK-3-UPDOWN: Interface Vlan2210, changed state to down

.May 28 17:27:49: %LINK-3-UPDOWN: Interface Vlan2210, changed state to up

.May 29 02:03:32: %LINK-3-UPDOWN: Interface Vlan2210, changed state to down

.May 29 02:03:34: %LINK-3-UPDOWN: Interface Vlan2210, changed state to up

.May 30 09:36:34: %LINK-3-UPDOWN: Interface Vlan2210, changed state to down

.May 30 09:36:36: %LINK-3-UPDOWN: Interface Vlan2210, changed state to up

Tahnk you.

3 Replies 3

Hi

I have not seen this error message before, it looks like a service used in linux, 

https://supportforums.cisco.com/discussion/10782486/how-configure-xinetd-applications-write-system-log

TFTP and xinetd (Linux)

https://www.cisco.com/en/US/docs/security/pix/pix63/pdm30/installation/guide/pdm30XA.pdf

I recommend open a case with the Cisco TAC in order to verify this log deeply. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Below  logging configurations
R2#show log
Syslog logging: enabled (12 messages dropped, 0 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.
No Inactive Message Discriminator.

    Console logging: level debugging, 70 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: disabled
    Buffer logging:  disabled, xml disabled,
                     filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.
ESM: 0 messages dropped
    Trap logging: level informational, 74 message lines logged

By default, a switch sends the output from system messages and debug privileged EXEC commands to a logging process. Stack members can trigger system messages. A stack member that generates a system message appends its hostname in the form of hostname-n, where n is a switch range from 1 to 4, and redirects the output to the logging process on the active switch. Though the active switch is a stack member, it does not append its hostname to system messages. The logging process controls the distribution of logging messages to various destinations, such as the logging buffer, terminal lines, or a UNIX syslog server, depending on your configuration. The process also sends messages to the console.

When the logging process is disabled, messages are sent only to the console. The messages are sent as they are generated, so message and debug output are interspersed with prompts or output from other commands. Messages appear on the active consoles after the process that generated them has finished.

You can set the severity level of the messages to control the type of messages displayed on the consoles and each of the destinations. You can time-stamp log messages or set the syslog source address to enhance real-time debugging and management. For information on possible messages, see the system message guide for this release.

You can access logged system messages by using the switch command-line interface (CLI) or by saving them to a properly configured syslog server. The switch software saves syslog messages in an internal buffer on a standalone switch, and in the case of a switch stack, on the active switch. If a standalone switch or the stack master fails, the log is lost unless you had saved it to flash memory.

You can remotely monitor system messages by viewing the logs on a syslog server or by accessing the switch through Telnet, through the console port, or through the Ethernet management port. In a switch stack, all stack member consoles provide the same console output.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/system_management/configuration_guide/b_sm_3se_3850_cg/b_sm_3se_3850_cg_chapter_01100.html.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: