cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1395
Views
0
Helpful
1
Replies

SF220/SG220 problems

csabasztanity
Level 1
Level 1

Hi there,

I need help regarding SF220/SG220-series switches. I have not found any articles on the Cisco community forums (not even anywhere else) regarding the 220-series so I decided to write down my problems.

I have some experience on using SF220/SG220 series switches. We have about 4 sites with these models. 3 sites have multi-level switching architecture such as having a core switch under which there is/are one or more access switches.

My problems (used different firmware: 1.0.0.17, 1.0.0.19. 1.1.1.2) in every case:

  • time settings are not held after reboot, however running-config was definitely saved to startup-config .
  • even if system time is good the syslog time has 8 hours time slide.
  • ports go up/down. Even worse if spanning tree (non-rapid) is enabled becasue in that case port is unavailable for about 30-50 seconds. Ports in question are towards (amongst others) other core network devices such as router (draytek) and access points (ruckus)

I have limited knowledge on STP and in networking but I do know that my configuration should work as SF200/SG200 series on 20+ sites are set up the same way with the same other networking bits and the work brilliantly.

Also checked spanning tree stats on specific ports on SF220/SG220 series ports and they showed mostly "Configuration BDPUs Transmitted". In cases where there was value other than 0 on "TCN BDPUs Received" line the up/down event happens many more times than the counter value so the up/down behavior must be independent of spanning tree

Energy settings are set untouched in every case.

Any help would be appreciated as I am keen to sort the issue (if possible anyway).

1 Reply 1

Austin Sabio
Level 4
Level 4

This is a normal behavior that some platform shows the wrong time after a reboot that's why NTP mechanism is needed. 

if you're referring to syslog time on the server side, then its a server time config matter. Otherwise, I would say check your config.it should have the following

service timestamps log datetime localtime show-timezone

I would suggest that you read about Cisco IOS clock and NTP. 

http://packetlife.net/blog/2011/mar/28/cisco-ios-clocks-and-ntp/

https://supportforums.cisco.com/document/24156/router-log-timestamp-entries-are-different-system-clock-when-ntp-configure

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/bsm/configuration/15-2mt/bsm-time-calendar-set.html#GUID-72B44542-E058-48AD-9796-6FB441AE3318

I hope this helps. Good Luck! 

Review Cisco Networking for a $25 gift card