SG 300-20 Link Issues

digitalchild · ‎07-05-2011

Hello,

I've searched around and can't seem to find anyone else with this problem.

I've got an sg 300-20 installed in my network that is showing quite a few errors with links dropping on both the data and voice vlans.

The ram log is littered with these:

2147482407 2011-Jul-06 09:07:32 Informational %LINK-I-Up: g8

2147482408 2011-Jul-06 09:07:26 Warning %LINK-W-Down: g8

2147482409 2011-Jul-06 09:07:00 Informational %LINK-I-Up: g8

2147482410 2011-Jul-06 09:06:58 Warning %LINK-W-Down: g8

2147482411 2011-Jul-05 23:03:14 Informational %LINK-I-Up: g11

2147482412 2011-Jul-05 23:03:12 Warning %LINK-W-Down: g11

G8 has a PC plugged into it and g11 has an SPA 504g cicso phone plugged into it.

The ports change (this is just a sample)

Network setup is the following:

UC320 => SG300-20

PC's on even ports

Phones on odd ports.

uc320 running phones and data vlans and DHCP server.

VLANS:

vlan 1 (data) untagged on all ports on sg 300

vlan 100 (voice) tagged on ports that have the phones plugged in.

Port 1 of uc320 => G20 on sg 300-20 for uplink.

G20 is also tagged with voice vlan.

STP is off. (I've tried it with and without this turned on without any difference).

Green Ethernet is off.

QoS is at defaults.

Everything else is default.

I can't seem to work out where in the network this would occur. Any help or direct would be greatly appreciated.

apex_tech · ‎11-09-2012

Same thing here, first switch was in place for about 1 year, then it started doing this, disabled STP (had some small switches in place). That only stopped it for about 1 day, came back with several messages, always picks on the same ports. Called and got a replacement switch, the reason why: If you notice if you do manual time set on the switch not NTP it will reset it to the factory time for the firmware! So new switch came in, everything was fine for about 2 weeks - then BAM! Started happening again, going down today to see if I can remove the last of the non cdp enabled switches, and install a small 8 port SG. Using smartport, will define as switch, no vlans are in use. Will set each port manually and see if that resolves it.

Would like to know what the deal is myself, application in use there is extremely network intensive perhaps its pushing the switch too far and this site needs a catalyst series to handle... Would hate to have to eat it, but will do to make the client happy!

darko.velickovic · ‎02-05-2013

Hello,

Same problem here, I have three SG300-52 ports, and link are droping all the time. Is it possible that no one from Cisco did not reply to this or give some advice how to fix this problem.

Bellow log:

2147483447 2013-Feb-05 19:30:20 Notice %SYSLOG-N-NEWSYSLOGSERVER: configure new syslog server 192.168.1.9

2147483449 2013-Feb-05 19:28:28 Informational %AAA-I-CONNECT: New http connection for user fortuna, source 192.168.1.113 destination 192.168.1.251 ACCEPTED

2147483455 2013-Feb-05 17:57:18 Informational %AAA-I-DISCONNECT: http connection for user fortuna, source 192.168.1.3 destination 192.168.1.251 TERMINATED

2147483456 2013-Feb-05 17:56:19 Warning %STP-W-PORTSTATUS: gi11: STP status Forwarding

2147483457 2013-Feb-05 17:56:14 Informational %LINK-I-Up: gi11

2147483458 2013-Feb-05 17:56:12 Warning %LINK-W-Down: gi11

2147483460 2013-Feb-05 17:45:29 Warning %STP-W-PORTSTATUS: gi36: STP status Forwarding

2147483461 2013-Feb-05 17:45:25 Informational %LINK-I-Up: gi36

2147483462 2013-Feb-05 17:45:22 Warning %LINK-W-Down: gi36

2147483463 2013-Feb-05 17:39:22 Warning %STP-W-PORTSTATUS: gi26: STP status Forwarding

2147483464 2013-Feb-05 17:39:17 Informational %LINK-I-Up: gi26, aggregated (1)

2147483465 2013-Feb-05 17:39:16 Warning %LINK-W-Down: gi26, aggregated (1)

2147483466 2013-Feb-05 17:39:12 Informational %LINK-I-Up: gi26

2147483467 2013-Feb-05 17:39:11 Warning %LINK-W-Down: gi26

2147483468 2013-Feb-05 17:31:04 Informational %AAA-I-DISCONNECT: http connection for user fortuna, source 192.168.1.82 destination 192.168.1.251 TERMINATED

2147483470 2013-Feb-05 17:25:49 Warning %STP-W-PORTSTATUS: gi43: STP status Forwarding

2147483471 2013-Feb-05 17:25:44 Informational %LINK-I-Up: gi43

2147483472 2013-Feb-05 17:25:44 Warning %STP-W-PORTSTATUS: gi23: STP status Forwarding

2147483473 2013-Feb-05 17:25:41 Warning %LINK-W-Down: gi43

2147483474 2013-Feb-05 17:25:40 Informational %LINK-I-Up: gi23

2147483475 2013-Feb-05 17:25:38 Warning %LINK-W-Down: gi23

2147483476 2013-Feb-05 17:25:36 Warning %STP-W-PORTSTATUS: gi48: STP status Forwarding

2147483477 2013-Feb-05 17:25:31 Informational %LINK-I-Up: gi48

2147483478 2013-Feb-05 17:25:29 Warning %LINK-W-Down: gi48

2147483479 2013-Feb-05 17:19:25 Warning %STP-W-PORTSTATUS: gi40: STP status Forwarding, aggregated (1)

2147483480 2013-Feb-05 17:19:20 Informational %LINK-I-Up: gi40, aggregated (1)

2147483481 2013-Feb-05 17:19:18 Warning %LINK-W-Down: gi40, aggregated (1)

2147483482 2013-Feb-05 17:15:36 Warning %STP-W-PORTSTATUS: gi40: STP status Forwarding

2147483483 2013-Feb-05 17:15:36 Warning %STP-W-PORTSTATUS: gi36: STP status Forwarding

2147483484 2013-Feb-05 17:15:32 Informational %LINK-I-Up: gi40

2147483485 2013-Feb-05 17:15:31 Informational %LINK-I-Up: gi36

2147483486 2013-Feb-05 17:15:28 Warning %LINK-W-Down: gi36

2147483487 2013-Feb-05 17:15:14 Warning %LINK-W-Down: gi40

2147483488 2013-Feb-05 17:14:29 Informational %INIT-I-Startup: Warm Startup

2147483489 2013-Feb-05 17:13:59 Informational %AAA-I-CONNECT: New http connection for user fortuna, source 192.168.1.82 destination 192.168.1.251 ACCEPTED

2147483490 2013-Feb-05 17:13:35 Informational %AAA-I-CONNECT: New http connection for user fortuna, source 192.168.1.3 destination 192.168.1.251 ACCEPTED

2147483492 2013-Feb-05 17:13:09 Notice %SYSLOG-N-LOGGING: Logging started.

2147483493 2013-Feb-05 17:12:51 Warning %STP-W-PORTSTATUS: gi9: STP status Forwarding

2147483494 2013-Feb-05 17:12:46 Informational %LINK-I-Up: gi9

2147483495 2013-Feb-05 17:12:43 Warning %STP-W-PORTSTATUS: gi26: STP status Forwarding

2147483496 2013-Feb-05 17:12:41 Warning %STP-W-PORTSTATUS: gi10: STP status Forwarding

2147483497 2013-Feb-05 17:12:40 Warning %STP-W-PORTSTATUS: gi6: STP status Forwarding

2147483498 2013-Feb-05 17:12:40 Warning %STP-W-PORTSTATUS: gi37: STP status Forwarding

2147483499 2013-Feb-05 17:12:39 Warning %STP-W-PORTSTATUS: gi30: STP status Forwarding

2147483501 2011-Nov-13 00:33:38 Informational %LINK-I-Up: gi26

2147483502 2011-Nov-13 00:33:38 Warning %STP-W-PORTSTATUS: gi42: STP status Forwarding

2147483503 2011-Nov-13 00:33:37 Informational %LINK-I-Up: gi10

2147483504 2011-Nov-13 00:33:36 Informational %LINK-I-Up: gi6

2147483505 2011-Nov-13 00:33:36 Informational %LINK-I-Up: gi37

2147483506 2011-Nov-13 00:33:35 Informational %LINK-I-Up: gi30

Thanks in advance

Darko

Tom Watts · ‎02-05-2013

Hi Darko, can you give more details about what is connecting to the switch? A small diagram would be fantastic.

-Tom
Please mark answered for helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

apex_tech · ‎02-06-2013

from your log entries it looks like your switch is rebooting itself

2147483488 2013-Feb-05 17:14:29 Informational %INIT-I-Startup: Warm Startup

2147483489 2013-Feb-05 17:13:59 Informational %AAA-I-CONNECT: New http connection for user fortuna, source 192.168.1.82 destination 192.168.1.251 ACCEPTED

2147483490 2013-Feb-05 17:13:35 Informational %AAA-I-CONNECT: New http connection for user fortuna, source 192.168.1.3 destination 192.168.1.251 ACCEPTED

2147483492 2013-Feb-05 17:13:09 Notice %SYSLOG-N-LOGGING: Logging started.

If you can I would disable STP, all the green ethernet stuff, bonjour, CDP, and anything else that is not absolutely required. See if it stabilizes the switch, it did for us. I updated ours to the most recent firmware version version as well. I had to disable STP on it even after it was replaced because of the occasional reboot. Our environment was a flat small network, no VOIP, just a couple of switches and to main switches (one located in each building) connected by fiber between. The funny thing about all this - they had some old dell switches that were not manageable. I talked them into spending the extra money to get manageable switches (VOIP and other services in the near future) from Cisco, only to have to disable all the extras...lol...

Oh and to complicate matters, it would send out malformed CDP packets when it rebooted... they also had a Cisco SA520... yes... it would reboot upon receiving malformed cdp packets. So we had to disable CDP on the SA520. Ya... it was a rough month but everything is quiet now.

darko.velickovic · ‎02-06-2013

Thank you all for fast reply. I want to clarify that this was not happen before 05.02.2013, suddenly it start with all switches… Very strange thing is that the ports between switches were never down also all was fine with the ports where the servers are. Tried whole day to find some rule, also track everything with syslog server. I will give you log files and excel files with cumulative ports down on all switches…

I appreciate all your effort and help.
Regards

Darko

abccisco2011 · ‎03-24-2016

Did anyone found a solution to this? I am also having the same problem. I disabled STP and it was fine for 2 days after that the problem came back again?

Thanks for your help in advance.

Sushant