Active and Standby Switch Election and Reelection
All stack members are eligible to be the active switch or the standby switch. If the active switch becomes unavailable, the standby switch becomes the active switch.
An active switch retains its role unless one of these events occurs:
The switch stack is reset.
The active switch is removed from the switch stack.
The active switch is reset or powered off.
The active switch fails.
The switch stack membership is increased by adding powered-on standalone switches or switch stacks.
The active switch is elected or reelected based on one of these factors and in the order listed:
The switch that is currently the active switch.
The switch with the highest stack member priority value
even if you change the priority or add a higher priority member to the stack you still have to reboot the stack to change the election, so the correct answer is D.
The re-election of a primary switch in a Cisco StackWise stack follows a specific order of events that cause the switch to lose its primary role. Here’s the typical order:
1. **When the stack primary is reset** (D): This is the most immediate event that causes the primary switch to lose its role, as it involves the primary switch going offline.
2. **When a switch with a higher priority is added to the stack** (A): The addition of a new switch with a higher priority can trigger the re-election process. However, the new switch must be integrated into the stack and recognized before it can assume the primary role.
3. **When the priority value of a stack member is changed to a higher value** (C): Changing the priority value of an existing stack member to a higher value can cause it to become the primary switch. This change takes effect after the next stack election process, which might occur immediately or during the next stack event.
i will go with D
the question is asking "when", none of the other options will trigger the action.
only D will trigger the new elections assuming that some changes have been made
As per Cisco documentation:
Note: If you reset the stack primary, it would reset the whole stack.
Which means that the original stack primary would more than likely be elected as the primary again.
To add a switch, as a primary, to a stack, complete these steps:
Change the priority value of the switch to be added to a value greater than the highest priority of the stack.
With the new switch powered on, connect the StackWise ports of the switch to the stack.
The election for the stack primary occurs, and the new switch is elected as the primary since it has the highest priority value.
The members of the previous stack reboot themselves to join the new stack.
So D could be true, but I believe based on the documentation that A is the best answer.
B. When a stack member fails.
In a Cisco StackWise stack, the StackWise primary switch is the designated master switch that handles certain control plane functions and provides stack-wide coordination. If the StackWise primary switch fails or becomes unreachable, the stack will automatically elect a new StackWise primary switch from the remaining stack members. This ensures the continuity and resilience of the stack operation.
Therefore, option B is the correct answer. The StackWise primary switch loses its role when a stack member fails.
If you reset/reboot only the primary switch in a switch stack, then, during the time that the primary switch is rebooting, the remaining switches in the stack will need to elect a new primary switch, which would most likely be the switch that is acting as the standby switch.
I am having trouble with the answer D, everyone seems to prefer it but by resetting the stack, the same master could be re-elected, resulting in no changes. A definitely makes the current master/active switch lose its master role. A reboot may happen to certain models when a higher priority switch is added to the stack. Why are Cisco putting in so many tricky questions, it all depends on certain circumstances. In this case, I go with A.
Adding a new member with higher priority is definitive. The current active will lose that role indefinitely. In D, after the reboot, the active will resume its role after reelection. I believe it's A too, but it's one of those questions...
Let's see what happens after A and after D.
A. when a switch with a higher priority is added to the stack
=> election is triggered, and the stack member with the higher priority becomes the new primary
D. when the stack primary is reset
=> election is triggered, and the current stack primary gets to be reelected
https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/71925-cat3750-create-switch-stks.html#anc16
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/ha_stack_manager/configuration_guide/b_hastck_3se_3850_cg/b_hastck_3se_3850_cg_chapter_010.html
The primary is only change after answer A), otherwise the current primary retains its role.
I think it should be A, based on https://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/71925-cat3750-create-switch-stks.html#anc16
So, in D by default when it is reseted it meand that election will be and there is a chance for the primary be elected again or not, but if you add a new node with higher priority it means 2 things:
1)it will be rebooted anyway
2)based on priority value the new memeber will be primary
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Jason233
Highly Voted 1 year, 9 months agoBryCR
1 year, 7 months agobora4motion
Highly Voted 1 year, 6 months agomerlow6674
Most Recent 6 days, 9 hours ago[Removed]
2 weeks, 3 days ago[Removed]
6 days, 21 hours agoemkay2022
5 months, 2 weeks agodjedeen
9 months, 3 weeks agoKingCon
10 months, 1 week agoWereAllinThisTogether
11 months agojeffro9898
11 months, 1 week agoando2023
12 months agoteikitiz
11 months, 1 week agoHungarianDish_111
1 year, 2 months agomikhailov_ivan90
1 year, 4 months agojucevabe
1 year, 9 months agojucevabe
1 year, 9 months ago