In this message 14w5d means that the switch has been up for 14 weeks and 5 days. The default in logging messages is to use system uptime as the timestamp. There is an option which you can configure to use datetime (date and time) as the logging timestamp. This is an especially good option if your switch learns time from an NTP source or if the switch has the built in clock chip that will maintain time over a reboot.
 Narayan I see your answer and agree with most of it. But the issue is not whether the switch has been configured with NTP or not. The default in logging is to use uptime. Even if NTP were configured you will get uptime in the log messages until you set the option to use datetime (which you do illustrate).
1. %C4K_EBM-4-HOSTFLAPPING: Host [mac-addr] in vlan [dec] is flapping between port [char] and port [char]
The specified host is detected as a source address on multiple ports. Typically, a host is supposed to be learned on only one port. A spanning tree loop is the most common cause of this condition. All traffic from the specified host is temporarily dropped. After 15 seconds, forwarding is reenabled. If the problem persists, the traffic from the problem host continues to be dropped indefinitely.
Recommended Action: Make sure that spanning tree is enabled to prevent spanning tree loops. If you have spanning tree disabled, make sure that you have no spanning tree loops in your network.
Common Issues with Catalyst 4500 Switches that Run Cisco IOS Software
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...