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.
Now my question is "what does reset mean here?". An actual reboot?
(additional question about stacking. if I have 3 switches in line 1-2-3 (no direct connection between 1 and 3). with 1 being master.
if link 1-2 goes down. master will disappear to switches 2 and 3. Am I right in assuming 2 and 3 will determine a new master between the two of them. And once link 1-2 comes back. there will be conflict between old master 1 and new master from 2/3?
what happens if middle switch 2 goes down? will 3 elect itself as master of it's now one switch stack. and once 2 comes back we have conflict between 1 and 3?
)
9 Replies
Replies have been turned off for this discussion
We would really appreciate a clarification as our stack has been acting up with reboots of switches.
If my logs say
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.
Is a reset an actual reboot of the whole switch? Or just a reset of the stack that is done without a reboot?
Welcome to the community! :)
We would really appreciate a clarification as our stack has been acting up with reboots of switches.
If my logs say
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.
Is a reset an actual reboot of the whole switch? Or just a reset of the stack that is done without a reboot?
Let me inquire this to the higher tier of NETGEAR Support. I will post here once I got a feedback.
(additional question about stacking. if I have 3 switches in line 1-2-3 (no direct connection between 1 and 3). with 1 being master.
if link 1-2 goes down. master will disappear to switches 2 and 3. Am I right in assuming 2 and 3 will determine a new master between the two of them. And once link 1-2 comes back. there will be conflict between old master 1 and new master from 2/3?
what happens if middle switch 2 goes down? will 3 elect itself as master of it's now one switch stack. and once 2 comes back we have conflict between 1 and 3?
Here are the factors determine which switch is elected as the stack master:
a. The switch that is manager always has priority to retain the role of master
b. Assigned priority
c. MAC addressBe reminded that the priority of the switch is how the stack decides what switch will be the master (stack manager). The highest priority we can give a switch is 15, though keep in mind that you can have one switch with a priority of 1 and the other switches not have any priority configured, then the switch with priority of 1 will be the master. But keep in mind that the switch with the next highest priority will be the backup if the master fails. If the priority for the switches in the stack has not been configured or they have the same priority, then the switch with the highest MAC address value will be elected as the master. If you give a priority of 0 to a switch it will never be considered for management.
Regards,
DaneA
NETGEAR Community Team
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
