NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
S3300-28X: behaviour after managment unit conflict.
If a managment unit conflict is detected (for whatever reason). And a new election is held and a new management unit is assigned. According to log files other stack member will reset and rejoin. ...
I just got a response from the higher tier of NETGEAR Support. As per the higher tier of NETGEAR Support, it might be possible that it is a reboot of the individual stack member. For us to confirm, kindly check the uptime of that stack member. Go to System > Stacking > Basic > Stack Configuration.
Regards,
DaneA
NETGEAR Community Team
thanks for reaching out to higher tier netgear support.
My Problem is that mine are rebooting sometimes when I do work on them and touch cables. (I know from uptime btw that they are rebooting).
The question is. Are they rebooting because something in our inwall cabling is only slightly screwed and stack members loose connection between themselves for short duration when I touch cabling. And it is default behaviour of my switches to reboot when the shortly separated members rejoin (I see the RESET entry in the log). Which would make it rather obvious where exactly my cabling problem is (namely the one connecting stack members on different floors).
Or is one or multiple of our inwall cabling totally screwed and my switches are rebooting because touching cables results in "illegal/unhealthy" currents to reach the switch resulting in this one making an emergency reboot? In which case cabling problem could be on any of the inwall ethernet connections to workplaces.
We already know it's the inwall cabling because the first thing we did is buy another S3300 switch and replace it. Didn't help. The second thing we did is replace all short cables from switch to plugs leading to inwall cabling. Didn't help either.
I just need to know if the logs say reset.
Keller-2 UNITMGR[unitMgrTask]: unitmgr.c(6588) 699 %% Reset initiated on unit 2, reason: Stack manager conflict resolution Keller-2 UNITMGR[unitMgrTask]: unitmgr.c(5347) 698 %% Management unit conflict was detected and this unit has lost the manager election. All the units in this stack will reset and join the winner stack manager 8:bd:43:6e:75:d0.
what actually is meant is reboot. If you could kindly reask higher tier netgear support. That would be great. "Might" is not helpful really. Somebody ought to know if log entry of reset is actual reboot.
My Problem is that mine are rebooting sometimes when I do work on them and touch cables. (I know from uptime btw that they are rebooting).
The question is. Are they rebooting because something in our inwall cabling is only slightly screwed and stack members loose connection between themselves for short duration when I touch cabling. And it is default behaviour of my switches to reboot when the shortly separated members rejoin (I see the RESET entry in the log). Which would make it rather obvious where exactly my cabling problem is (namely the one connecting stack members on different floors).
Or is one or multiple of our inwall cabling totally screwed and my switches are rebooting because touching cables results in "illegal/unhealthy" currents to reach the switch resulting in this one making an emergency reboot? In which case cabling problem could be on any of the inwall ethernet connections to workplaces.
We already know it's the inwall cabling because the first thing we did is buy another S3300 switch and replace it. Didn't help. The second thing we did is replace all short cables from switch to plugs leading to inwall cabling. Didn't help either.
With regard to this, it would be best that you open a chat or online support ticket with NETGEAR Support at anytime. Kindly state your concern and you may indicate a link to this forum thread as reference. In this way, a thorough investigation will conducted on your switch stack.
Regards,
DaneA
NETGEAR Community Team
I will contact support that way. Thank you for your help.
But tbh I don't really need a thorough investigation of my stack. I just need to know when a S3300 writes these log entries and talks about RESET. If what he actually does is a REBOOT.
then everything would be already clear.
Will come back after support answered the question and post it here.
Hi again,
tried contacting support, but after entering Serial Number and Date of sale it tells me my 90 day support ended already. And I have to buy some support contract.
Now I might consider doing that if I actually had a real support case! I don't.
All I wanna know is
if I see this in my logs:
Keller-2 UNITMGR[unitMgrTask]: unitmgr.c(6588) 699 %% Reset initiated on unit 2, reason: Stack manager conflict resolution Keller-2 UNITMGR[unitMgrTask]: unitmgr.c(5347) 698 %% Management unit conflict was detected and this unit has lost the manager election. All the units in this stack will reset and join the winner stack manager 8:bd:43:6e:75:d0
does that Reset mean actual reboot of units.
I really shouldn't have to buy a support contract for what is in my opinion essentially information that should be publicly available in either a manual or a FAQ.
Could you please reask the support guys on your end to confirm reset here means "it is a reboot" or "it is not a reboot".
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
