AV Network Best Practices (Pakedge Configuration)
“The network is the foundation of a reliable system.”
Best Practice’s AV Network
Not All Managed Switches are Created Equal
“There are AV Centric Managed Switches Pre-configured out of the box and some Managed Switches Need to be Configured to Support Information Below”
All Pakedge Managed Switches are Layer 3, however will need to be Configured.
*These configurations are for Networks that will NOT be using SONOS.
For Networks that will be using SONOS (5 or More Devices), please see the end of document.
Enable STP, Set to:
- MSTP (Multiple Spanning Tree Protocol) “Because Android/Google TV Uses Ethernet [V]LAN or inter-VLAN”
Root Bridge Priority:
- Default 32768 Should Be Fine when using (1) Managed Switch
- Max Age should be 20
- Forward Delay should be 15
- When using more than (1) Managed Switch
- Main Managed Switch needs to be the LOWEST Number, making it the Priority.
- Example: 32768
- Next Managed Switch needs to be a HIGHER Number, so all traffic gets Managed by the Priority Switch.
- Example: 36864
- Main Managed Switch needs to be the LOWEST Number, making it the Priority.
*If you don’t change these settings, the Managed Switch with the LOWEST MAC Address will assume Priority.
Example of Root Bridge Priority in a Daisy Chanin Configuration
Example of Root Bridge Priority in a Star Topology Configuration
- Main Managed Switch will be the LOWEST, while the Managed Switches off the Priority Switch can all be the same, just needs to be a HIGHER number.
Port Settings:
- Set All to Priority 128
Admin Edge Port:
- Have this un-ticked on every port.
Loop Protection Configuration:
- Don’t Turn on Loop Protection
- Do not use Loop Protection on uplink ports between switches with spanning tree enabled. Loop Protection is designed for unmanaged switches that drop spanning tree BPDUs.
- BPDU? BPDU are the parts of the spanning tree protocol (STP). They allow the switches to obtain information about each other. The spanning tree protocol enabled the switches in redundant local area network need to exchange the information between each other for spanning tree protocol to work properly so, for the proper exchange of information between spanning tree protocol the bridge protocol data unit (BPDU) is used.
For Networks that will be using SONOS (5 or More Devices)
STP (Spanning Tree Protocol):
- Sonos (SonosNet)
- Needs STP
- Android/Google TV (“Zero-Configuration Networking” Protocols, including Multicast version of DNS Service Discovery ([m]DNS-SD) Ethernet [V]LAN or inter-VLAN), Nest (Weave), Ring (Z-Wave), Apple (Real Time Streaming Protocol (RTSP), Apples Bonjour (“Zero-Configuration Networking“) etc…
- All Needing MSTP
Configure (2) Managed Switches
Program one Managed Switch that has ALL Sonos devices to:
- Spanning Tree Protocol to STP
- Set Path Cost to Specific and Path Cost to 10 for Each Port with a Sonos Device
Program the other Managed Switch to MSTP and Follow Above Instructions
Loading...
Reload document 
Open in new tab