04-01-2015 11:27 PM
We've been using Cisco SG500 switches for our office for about 3yrs now. Last year we moved offices and were running 2 locations in parallel for a few months, so for the new office we brought 6x new SG500 and run them in a stack with 5G SFP interconnects and they have been running great since powered on 9 months ago. Pretty basic setup running in L2 mode as our Checkpoint is our gateway, voice VLAN with CDP for VOIP Phones/POE and a few VLANS and we manage it all via the Web GUI.
Anyway, this afternoon our fileserver dropped of the lan for a couple of minutes, then came back and seemed fine, but a couple of users couldn't connect. They were getting authentication errors and when I looked at the server its network profile was Public instead of Domain? What was worse is that we had a 2x NIC team in LACP and of the NICs was showing LACP Authentication Error. Thats the problem.
So I try the web gui and no response. Ping works but http/s for the gui doesn't and pings are in the 200ms range from a usual 1>5. I go down to the server room and connect into a free port on the stack and nothing, port comes up but I dont get DHCP? Go back to my desk in a live port and works fine. Hmmm. I got to my syslog for the switch and it isn't logging anymore, hasn't since the file server drop issue so this is when it started but nothing untoward in the logs. The only similar timing was I recently bounced some new VM ware serves which also have some LAG ports configured (not LACP) but I'd done this several times this week without issue.
I try a console connection and that doesn;t work either! So all I can think is something has caused the management service on the stack to crash, so my only option is shut the stack down and power it up again, so I'm going to do this tomorrow AM as its a public holiday.
Has anyone else seen this happen with the SG series switches? Its a first for us in 3 years thats all so a little confused how it would affect the entire stack anyway.
06-09-2015 11:51 AM
Hi Andy,
How did it work? Did reboot help?
Aleksandra
07-02-2015 02:13 AM
Yes the reboot worked. We had to reboot the entire stack though as just doing the affected switch didn't bring back the management interface, so i had to do the stack master as well which caused the whole stack to go down.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide