When the units do not boot up at the same time, such as when some units are powered down just after reloading and powered up later to
join the stack, they do not participate in the election process even though the units that boot up late may have a higher priority configured.
This happens because the master and standby have already been elected, hence the unit that boots up late joins only as a member.
When an up and running standalone unit or stack is merged with another stack, based on election, the losing stack reloads and the master
unit of the winning stack becomes the master of the merged stack. For more details, see sections
Add Units to an Existing Stack
and
. It is possible to reset individual units to force them to give up the management role or reload the whole stack
from the CLI to ensure a fully synchronized bootup.
Example of Viewing Stack Members
Virtual IP
You can manage the stack using a single IP, known as a virtual IP, that is retained in the stack even after a failover.
The virtual IP address is used to log in to the current master unit of the stack. Both IPv4 and IPv6 addresses are supported as virtual IPs.
Use the following command to configure a virtual IP:
Dell(conf)#virtual-ip {ip-address | ipv6–address | dhcp}
Failover Roles
If the stack master fails (for example, is powered off), it is removed from the stack topology.
The standby unit detects the loss of peering communication and takes ownership of the stack management, switching from the standby
role to the master role. The distributed forwarding tables are retained during the failover, as is the stack MAC address. The lack of a
standby unit triggers an election within the remaining units for a standby role.
After the former master switch recovers, despite having a higher priority or MAC address, it does not recover its master role but instead
takes the next available role.
To view failover details, use the
show redundancy
command.
MAC Addressing on Stacks
The stack has three MAC addresses: the chassis MAC, interface MAC, and null interface MAC.
All interfaces in the stack use the interface MAC address of the management unit, and the chassis MAC for the stack is the master’s
chassis MAC. The stack continues to use the master’s chassis MAC address even after a failover. The MAC address is not refreshed until
the stack is reloaded and a different unit becomes the stack master.
NOTE:
If the removed management unit is brought up as a standalone unit or as part of a different stack, there is a possibility of
MAC address collisions.
A standalone is added to a stack. The standalone and the master unit have the same priority, but the standalone has a lower MAC address,
so the standalone reboots. In the second example, a standalone is added to a stack. The standalone has a higher priority than the stack, so
the stack (excluding the new unit) reloads.
Example of Adding a Standalone with a Lower MAC Address to a Stack
----------STANDALONE BEFORE CONNECTION---------------
Standalone#show system brief
Stack MAC : 00:01:e8:d5:ef:81
-- Stack Info --
Unit UnitType Status ReqTyp CurTyp Version Ports
------------------------------------------------------
0 Management online
898
Stacking
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...