Overview
Stacking and trunking are different ways to connect multiple network switches. The main difference is how the switches are managed: a stack operates as one logical switch, while trunk-connected switches retain their own configurations and management interfaces.
For Just Add Power systems, the configuration method determines the supported approach:
- AMP Standardized Configuration: Uses trunk connections between supported switches. AMP configures the switches and Just Add Power devices.
- AMP Alternate Configuration: The installer or network administrator configures the network and inter-switch connections to meet the multicast requirements. AMP configures the Just Add Power devices.
- Established JADConfig systems: Use supported switch stacks. The stacking information below explains these existing installations.
JADConfig is for established systems only. All new systems use AMP. JADConfig systems reach End of Support on January 1, 2027. See the JADConfig End of Support Notice for transition requirements.
Stacking
How It Works
A supported switch stack combines multiple physical switches into one logical switch with:
- One management IP address.
- One configuration for the stack.
- One management interface.
One switch, identified as the Primary or Master, manages the stack configuration. Each physical switch has a Stack ID (SID) that identifies its position within the stack.
Switch Connections
Established JADConfig stacks use designated stacking ports and a supported line or ring arrangement. Stacking-port operation differs from an Ethernet trunk carrying configured VLANs.
A ring provides an additional path for redundancy. Do not count that additional connection as extra usable bandwidth when planning an established JADConfig stack.
Stack bandwidth and connection requirements depend on the switch model. See Multi-Switch Considerations for JADConfig Systems for the model-specific limits.
Port Identification
Stack ports are identified using the Stack ID and physical port number. For example, 2/12 identifies Port 12 on the switch assigned SID 2.
Replacement
In a supported JADConfig stack, all switches must be the same manufacturer and model. A replacement must also meet the stack's firmware and configuration requirements.
The replacement switch must receive the Stack ID of the switch it replaces so the stack configuration refers to the intended ports. Assigning the Stack ID alone does not verify that the replacement is ready; follow the manufacturer's replacement procedure and confirm the stack configuration and device connections.
Supported stacks can transfer the Primary role to another member if the Primary fails. Confirm the resulting stack status and operation after a failure or replacement.
Trunking
How It Works
A trunk connection carries the required VLAN traffic between switches while allowing each switch to remain independently managed.
- Each switch has its own management IP address.
- Each switch has its own configuration.
- Each switch has its own management interface.
Trunking describes how traffic passes between switches. It does not combine the switches into one management system.
Switch Connections
General network designs can use trunk connections in line, ring, star, or other arrangements. The diagrams in this article illustrate networking concepts; they do not establish supported layouts for every Just Add Power configuration method.
AMP Standardized Configuration
Use the inter-switch topology and port assignments provided by AMP. All switches must be supported models from the same manufacturer, although supported models may differ within the system.
AMP uses 10Gb SFP+ trunk connections and Link Aggregation Groups (LAGs). Its port allocation determines how many physical links are available between neighboring switches.
Follow Multi-Switch Considerations for AMP Standardized Systems for hardware requirements, port allocation, and the connection diagram.
AMP Alternate Configuration
The installer or network administrator selects and configures the inter-switch layout. Every required path must carry the Just Add Power VLAN and meet the multicast, Jumbo Frame, and bandwidth requirements.
Follow Single VLAN Multicast Switching for the complete network requirements.
Link Aggregation and Bandwidth
A LAG combines multiple physical connections between the same two switches into one logical connection. For example, two 10Gb connections provide 20 Gbps of nominal aggregate capacity.
Traffic may not be distributed evenly across the member links. Confirm the capacity and utilization of individual members as well as the group total.
Use Plan Network Bandwidth for Just Add Power Systems for Encoder bandwidth calculations, headroom, and LAG limitations.
Port Identification
Because each switch is independently managed, identify a connection using both the switch and its physical port number. For example, record a device as connected to Switch 2, Port 12.
Replacement
A replacement switch must meet the requirements of the installed configuration method. General Ethernet compatibility does not establish compatibility with AMP Standardized Configuration or a particular multicast design.
- Standardized Configuration: Use a supported switch from the same manufacturer and preserve the required AMP settings and port assignments.
- Alternate Configuration: Have the network administrator confirm that the replacement supports the required VLANs, multicast settings, Jumbo Frames, and inter-switch capacity.
A saved configuration may be suitable for a matching replacement model and firmware. Do not assume that a configuration file can be transferred to a different model. After replacement, verify management access, endpoint connections, inter-switch links, and audio/video operation.
