cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

150
Views
0
Helpful
1
Replies
Beginner

No Logging on switches for weeks

We have found that many campus switches have stopped logging since weeks. It is not fixed time line for each switch. We have 4507+E, 3650s in the environment. Below is the log from one of the switch. Logging stopped from 23 weeks. Any ideas? Do I have to involve TAC here?

 

Logging configuration as below.

 

nzairnet1#show run | i logging
logging host 10.150.0.187
logging host 10.150.0.20
logging synchronous
logging synchronous

 

Log shows as below

 

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

No Active Message Discriminator.

 

No Inactive Message Discriminator.


Console logging: level debugging, 2451 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 3052 messages logged, xml disabled,
filtering disabled
Exception Logging: size (8192 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 3049 message lines logged
Logging to 10.150.0.187 (udp port 514, audit disabled,
link up),
632 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging Source-Interface: VRF Name:

Log Buffer (32768 bytes):
.150.4.48 4/0 (hold time expired) 0 bytes
002707: 22w1d: %BGP-5-NBR_RESET: Neighbor 10.150.4.48 reset (BGP Notification sent)
002708: 22w1d: %BGP-5-ADJCHANGE: neighbor 10.150.4.48 Down BGP Notification sent
002709: 22w1d: %BGP_SESSION-5-ADJCHANGE: neighbor 10.150.4.48 IPv4 Unicast topology base removed from session BGP Notification sent
002710: 22w1d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.174.141)
002711: 22w1d: %BGP-5-ADJCHANGE: neighbor 10.150.4.48 Up
002712: 22w1d: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
002713: 22w1d: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
002714: 22w6d: %BGP-3-NOTIFICATION: sent to neighbor 192.168.140.7 4/0 (hold time expired) 0 bytes
002715: 22w6d: %BGP-5-NBR_RESET: Neighbor 192.168.140.7 reset (BGP Notification sent)
002716: 22w6d: %BGP-5-ADJCHANGE: neighbor 192.168.140.7 Down BGP Notification sent
002717: 22w6d: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.140.7 IPv4 Unicast topology base removed from session BGP Notification sent
002718: 22w6d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Standby -> Active
002719: 22w6d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Active -> Speak
002720: 22w6d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Speak -> Standby
002721: 22w6d: %BGP-5-ADJCHANGE: neighbor 192.168.140.7 Up
002722: 22w6d: %HSRP-5-STATECHANGE: Vlan10 Grp 10 state Speak -> Standby
002723: 22w6d: %HSRP-5-STATECHANGE: Vlan10 Grp 10 state Standby -> Listen
002724: 22w6d: %HSRP-5-STATECHANGE: Vlan10 Grp 10 state Speak -> Standby
002725: 22w6d: %HSRP-5-STATECHANGE: Vlan10 Grp 10 state Standby -> Listen
002726: 22w6d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Standby -> Active
002727: 22w6d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Active -> Speak
002728: 22w6d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Speak -> Standby
002729: 23w0d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Standby -> Active
002730: 23w0d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Active -> Speak
002731: 23w0d: %HSRP-5-STATECHANGE: Vlan232 Grp 232 state Speak -> Standby
002732: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.206)
002733: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.206)
002734: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
002735: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
002736: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.200)
002737: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.200)
002738: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.200)
002739: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.200)
002740: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
002741: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
002742: 23w0d: %SYS-5-CONFIG_I: Configured from console by kpmg on vty0 (10.150.0.200)
002743: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized to the standby supervisor
002744: 23w0d: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized to the standby supervisor
002745: 23w1d: %SSH-4-SSH2_UNEXPECTED_MSG: Unexpected message type has arrived. Terminating the connection from 10.150.0.200
002746: 23w1d: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Standby -> Active
002747: 23w1d: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Active -> Speak
002748: 23w1d: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Speak -> Standby
002749: 23w2d: %HSRP-5-STATECHANGE: Vlan202 Grp 202 state Standby -> Active
002750: 23w2d: %HSRP-5-STATECHANGE: Vlan202 Grp 202 state Active -> Speak
002751: 23w2d: %HSRP-5-STATECHANGE: Vlan202 Grp 202 state Speak -> Standby
002752: 23w3d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Standby -> Active
002753: 23w3d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Active -> Speak
002754: 23w3d: %HSRP-5-STATECHANGE: Vlan203 Grp 203 state Speak -> Standby
002755: 23w3d: %HSRP-5-STATECHANGE: Vlan201 Grp 201 state Standby -> Active

1 ACCEPTED SOLUTION

Accepted Solutions
Collaborator

Re: No Logging on switches for weeks

 

Hi,

It is not that your switches have stopped logging but that the logging is set to "log uptime". check your config for the command "service timestamp log uptime"

Run show version on the switch and it should show the uptime around 23 weeks, the same as in the logs

If you need to log the time, you will need to enter "service timestamp log datetime"

Thanks

John

**Please rate posts you find helpful**

View solution in original post

1 REPLY 1
Collaborator

Re: No Logging on switches for weeks

 

Hi,

It is not that your switches have stopped logging but that the logging is set to "log uptime". check your config for the command "service timestamp log uptime"

Run show version on the switch and it should show the uptime around 23 weeks, the same as in the logs

If you need to log the time, you will need to enter "service timestamp log datetime"

Thanks

John

**Please rate posts you find helpful**

View solution in original post

CreatePlease to create content
Content for Community-Ad