
Stack Group/Port Numbers
By default, each unit in Standalone mode is numbered stack-unit 1.
A maximum of eight 10G stack links or two 40G stack links can be made between two units in a stack. The front end ports are
divided into 16 stack groups, each with 40G of bandwidth. Stack groups 0 through 11 correspond to 10G stack groups with four ports
each. Stack groups 12 to 15 are one 40G port each.
The front end ports accommodate SFP, SFP+ and QSFP+.
•
Ports are divided into 16 stack-groups (0 to 15) as shown in the following example. The stack groups must be of a single speed -
either all 10G or all 40G.
– stack-group 0 corresponds to ports 0-3, stack-group 1 corresponds to ports 4-7, so on through stack-group 11.
– stack-group 12 corresponds to the 40G port 48, stack-group 13 corresponds to port 52, so on through stack group 15.
Figure 126. Stack-Group Assignments
You can connect the units while they are powered down or up. Stacking ports are bi-directional.
When a unit is added to a stack, the management unit performs a system check on the new unit to ensure the hardware type is
compatible. A similar check is performed on the Dell Networking OS version. If the stack is running Dell Networking OS version
8.3.12.0 and the new unit is running an earlier software version, the new unit is put into a card problem state.
•
If the unit is running Dell Networking OS version 8.3.10.x, it is upgraded to use the same Dell Networking OS version as the stack,
rebooted, and joined the stack.
•
If the new unit is running an Dell Networking OS version prior to 8.3.10.x , the unit is put into a card problem state, Dell
Networking OS is not upgraded, and a syslog message is raised. The unit must be upgraded to Dell Networking OS version
8.3.12.0 before you can proceed.
Syslog messages are generated by the management unit:
•
before the management unit downloads its Dell Networking OS version 8.3.12.0 or later to the new unit. The syslog includes the
unit number, previous version, and version being downloaded.
•
when the firmware synchronization is complete.
•
if the system check fails, a message such as a hardware incompatibility message or incompatible uboot version is generated. If
the unit is placed in a card problem state, the management unit also generates an SNMP trap.
•
if the software version of the new unit predates Dell Networking OS version 8.3.12.0 , the management unit puts the new unit
into a card problem state and generates a syslog that identifies the unit, its Dell Networking OS version, and its incompatibility for
firmware synchronization.
NOTE: You must enter the
stack-unit stack-unit stack-group stack-group
command when adding units to
a stack to ensure the units are assigned to the correct groups.
NOTE: Any scripts used to streamline the stacking configuration process must be updated to reflect the Command Mode
change from EXEC to CONFIGURATION to allow the scripts to work correctly.
Stacking
827
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...