MXnet Switch Hardware User Manual

MXnet Switch Hardware User Manual

Supported Products

MXnet Switches

1G Switches

  1. AC-MXNET-SW10
  2. AC-MXNET-SW12
  3. AC-MXNET-SW24
  4. AC-MXNET-SW48
  5. AC-MXNET-1G-SW24E
  6. AC-MXNET-1G-SW48E

10G Switches

  1. AC-MXNET-10G-SW12C
  2. AC-MXNET-10G-SW24C
  3. AC-MXNET-10G-SW24Q
  4. AC-MNXET-10G-SW48Q
  5. AC-MXNET-10G-SW48HQ

Fiber Modules

  1. AC-1G-SFP-C
  2. AC-1G-SFP-SM
  3. AC-1G-SFP-MM
  4. AC-10G-SFPP-SM
  5. AC-10G-SFPP-MM
  6. AC-10G-SFPP-C30
  7. AC-10G-SFPP-C80
  8. AC-10G-SFPP-C100
  9. AC-25G-SFP28-SM
  10. AC-25G-SFP28-MM

Fiber Cables

  1. AC-MXNET-STACK-JUMP
  2. AC-MXNET-STACK-1M
  3. AC-MXNET-STACK-2M
  4. AC-MXNET-STACK-3M
  5. AC-10G-AOC-01
  6. AC-10G-AOC-02
  7. AC-10G-AOC-03
  8. AC-25G-AOC-01
  9. AC-25G-AOC-02
  10. AC-25G-AOC-03
  11. AC-40G-AOC-01
  12. AC-40G-AOC-02
  13. AC-40G-AOC-03
  14. AC-40G-BOC-01
  15. AC-40G-BOC-02
  16. AC-40G-BOC-03

Important Safety Instructions

Prior to installing, configuring, and operating all MXnet devices and other vendor equipment, AVPro recommends that each dealer, integrator, installer, and all other necessary personnel access and read all the required technical documentation, which can be located by visiting avproglobal.com.

Read and understand all safety instructions, cautions, and warnings in this document and the labels on the equipment.

Safety Classifications in this Document

Info
NOTE
Provides information related to system design, caveats or limitations of equipment.
Idea
TIP
Provides suggestions and considerations for installing, configuring and operating devices.
Alert
IMPORTANT/CAUTION
Provides important information for installing or operating the equipment.
Warning
WARNING
Provides critical information for situations that may cause physical damage to the equipment, installer or user.

Electrical Shock Prevention

Alert
ELECTRICAL SHOCK
The source power poses an electrical shock hazard that can potentially cause serious injury to installers and end users.
Alert
ELECTRICAL DISCONNECT
The source power outlet and power supply input power sockets should be easily accessible to disconnect power in the event of an electrical hazard or malfunction.

Weight Injury Prevention

Alert
WEIGHT INJURY
Installing some of the MXnet devices requires two installers to ensure safe handling during installation. Failure to use two installers may result in injury.

Safety Statements

Follow all of the safety instructions listed below and apply them accordingly. Additional safety information will be included where applicable.
  1. Read and keep these instructions.
  2. Heed all warnings and follow all instructions.
  3. Do not use these devices near water.
  4. Clean only with a dry cloth.
  5. Do not block any ventilation openings. Install in accordance with the manufacturer’s instructions.
  6. Do not install near any heat sources such as radiators, heat registers, stoves, or other apparatus (including amplifiers) that produce heat.
  7. Do not defeat the safety purpose of the polarized or grounding-type plug. A polarized plug has two blades with one wider than the other. A grounding-type plug has two blades and a third grounding prong. The wide blade or third prong are provided for your safety. If the provided plug does not fit into your outlet, consult an electrician for replacement of the obsolete outlet.
  8. Protect the power cord from being walked on or pinched particularly at plugs, convenience receptacles, and the point where they exit from the devices.
  9. Only use attachments and accessories specified by the manufacturer.
  10. Unplug these devices during lightning storms or when unused for long periods of time.
  11. To reduce the risk of electric shock or damage to these devices, never handle or touch the devices and power cord if your hands are wet or damp. Do not expose these devices to rain or moisture.
  12. Refer all servicing to qualified service personnel. Servicing is required when the devices have been damaged in any way, such as power supply cord or plug is damaged, liquid has been spilled, objects have fallen into the devices, the devices have been exposed to rain or moisture, does not operate normally as intended, or has been dropped.
  13. The devices and their accessories should never be exposed to open flames or excessive heat.

AC Power Connections

Alert
Surge Protection
Use a surge-protected circuit for all components and power supplies.
Alert
Electrical Disconnect

Introduction

Overview of MXnet Switches

MXnet switches are specialized managed network switches engineered specifically for professional AV-over-IP applications. They serve as the physical infrastructure backbone that connects MXnet encoders, decoders, transceivers, and control boxes, delivering the high bandwidth, low latency, and Power over Ethernet (PoE) capabilities essential for distributing video and audio in modern AV installations.
Available in both 1 Gigabit and 10 Gigabit configurations with copper and fiber connectivity options, MXnet switches provide the network infrastructure required for various MXnet ecosystems including Evolution I, Evolution II, SDVoE-based 10G systems, and the Universal Streaming Platform (USP). Whether you're building a simple residential system with a handful of endpoints or a complex enterprise installation with hundreds of distributed displays, MXnet switches deliver the performance, scalability, and reliability that professional installations demand.

How MXnet Switches Fit in MXnet Systems

In an MXnet system, switches perform three critical physical functions:

High-Bandwidth Data Transport

MXnet switches provide the physical network pathways that carry video, audio, and control data between all system components. The switch lineup includes both 1 Gigabit models for lossless compression video distribution and 10 Gigabit models for uncompressed SDVoE applications, with flexible copper and fiber connectivity options to match specific installation requirements and cable distance limitations.

Centralized Power Delivery

Many MXnet switches deliver electrical power to connected devices over the same Ethernet cables that carry data through Power over Ethernet (PoE) technology. This eliminates the need for separate power supplies at each encoder, decoder, or transceiver location dramatically simplifying installation, reducing cable runs, and minimizing potential failure points. PoE-enabled MXnet switches provide power budgets ranging from 125W to 1000W per switch, supporting devices requiring anywhere from 15.4W (IEE 802.3af - PoE) to 30W (IEE 802.3 - PoE+) to 90W (IEE 802.3bt - PoE++) per port.

Network Management and Monitoring

MXnet switches provide comprehensive visibility into the physical network infrastructure. Through the MXnet Mentor web interface, command-line management, or web GUI, installers can monitor real-time diagnostics including temperature, port link status, data rates, packet statistics, and PoE power consumption per port—enabling proactive monitoring and rapid identification of physical layer issues like cable faults, overheating, or power budget limitations. MXnet switches also support SNMP (Simple Network Management Protocol) for integration with enterprise network monitoring systems and Syslog for centralized logging and event tracking across multiple switches.

Why MXnet Switches Are Purpose-Built for AV

Unlike standard IT network switches designed for general data traffic, MXnet switches are specifically optimized for the unique physical demands of video and audio distribution:
Sustained High Throughput - Video streams generate constant bandwidth demands. MXnet switches provide switching architectures that maintain full wire-speed performance on all ports simultaneously, even under sustained high-load conditions.
High-Capacity PoE Delivery - Modern 4K encoders and decoders can require up to 60 watts of power each. Select MXnet switch models provide PoE++ (IEEE 802.3bt) support delivering up to 90W per port with total switch power budgets ranging from 125W to 1000W.
Validated for SDVoE - The 10G MXnet switch models are specifically validated for Software Defined Video over Ethernet (SDVoE) applications, ensuring they meet the stringent physical layer requirements for zero-latency, uncompressed 4K video transport.
Robust Physical Design - Professional AV installations demand 24/7/365 operation. MXnet switches feature industrial-grade components, active cooling with temperature monitoring, rack-mountable 1U form factors, and redundant power supply options on select models.

Typical Use Cases

MXnet switches are deployed across diverse installation types:
Residential AV Systems - Whole-home video distribution with centralized equipment racks and displays throughout the residence. PoE capability enables clean installations without visible power cables at each endpoint.
Hospitality - Hotels, resorts, and casinos delivering IPTV/Cable TV, streaming, digital signage, and video walls. Centralized architecture reduces in-room equipment and simplifies maintenance.
Corporate and Enterprise - Conference rooms, boardrooms, and training facilities requiring presentation systems, video conferencing, and collaboration displays with high reliability.
Education - Schools and universities interconnecting classroom displays, lecture capture systems, and distance learning infrastructure across buildings and campuses.
Healthcare - Operating room video distribution, telemedicine systems, and digital signage in mission-critical medical environments where downtime is not acceptable.
Live Events - Rental and staging companies deploying temporary video walls and multi views, camera feed routing, and digital signage with fast setup and teardown.
Control Rooms - Security operations centers and emergency management facilities where maximum uptime, redundancy, and real-time monitoring are critical.

About This Hardware Manual

This installation manual provides comprehensive guidance for the physical deployment of MXnet switches. It is designed for AV installers, system integrators, and technicians who may be working with managed network switches for the first time.

What This Manual Covers:

  1. Physical installation, rack mounting, and mechanical considerations
  2. Understanding hardware components, ports, LEDs, and indicators
  3. Cable types, specifications, and distance limitations
  4. Fiber optic transceiver selection, installation, and removal
  5. Power requirements, PoE power budgets, and electrical considerations
  6. Cooling, airflow management, and environmental requirements
  7. Physical network topology design and cabling best practices
  8. Physical layer verification and hardware troubleshooting

What This Manual Does NOT Cover:

  1. Switch configuration procedures (see MXnet CLI Guide and MXnet Web GUI Guide)
  2. Network protocol configuration (VLAN setup, IGMP settings, routing policies)
  3. MXnet Mentor software operation and system programming
  4. Encoder, decoder, and transceiver configuration (see MXnet User Manual)
  5. CBOX setup and AV routing programming (see MXnet User Manual)

Important References:

  1. For complete MXnet ecosystem information, system architecture, and endpoint details, refer to the MXnet Endpoint User Manual
  2. For switch configuration and management procedures, refer to the MXnet Switch CLI Guide and MXnet Switch GUI Guide
  3. For warranty information and technical support, refer to the Warranty and Service section
WarningCritical Safety Note: Always review the above Safety Instructions section before beginning any installation work. MXnet switches operate at high voltages, can weigh over 20 pounds, and generate significant heat during operation. Proper lifting techniques, electrical safety precautions, and adherence to all applicable electrical codes, building codes, and workplace safety regulations are mandatory.

Technical Foundations & Definitions

Devices that connect to a source device such as a media player, game console, computer etc. and convert (or encode) a signal onto the network.
Term
Definition
Access Port
A switch port configured to carry traffic for a single VLAN. Commonly used for endpoints like encoders and decoders.
Access Switch
A network switch that connects directly to endpoints (encoders, decoders, transceivers) in the MXnet system.
Control Box
The control box or 'CBOX' is the device used to communicate and configure MXnet endpoints, and is where the system logic is stored and the commands are processed. The API utilized by the Mentor web interface and third-party control systems are centralized to the CBOX to provide multipoint AV over IP distribution. 
Core Switch
A high-capacity switch that forms the backbone of the network, aggregating traffic from distribution switches.
Daisy-Chain Topology
A network layout where devices are connected in sequence, one after another
Decoder
Devices that connect to a sink device such as a television or projector and receive (or decode) signals generated by MXnet encoders.
DHCP
Dynamic Host Configuration Protocol: Automatically assigns IP addresses to devices on the network.
DNS/mDNS
Domain Name System / Multicast DNS: DNS resolves hostnames to IP addresses; mDNS enables local name resolution without a DNS server, useful for AV-over-IP discovery especially with Dante.
Distribution Switch
A switch that aggregates traffic from multiple access switches and connects to the core switch.
Encoder
Encoders are devices that connect to a source device such as a media player, game console, computer etc...and convert (or encode) a signal onto the network.
Endpoint
A generalized term used to describe an encoder, decoder, or transceiver.
Ethernet
(IEE 802.3)
The foundation of all modern wired networking, Ethernet defines how devices communicate over physical cables. MXnet systems use various Ethernet speeds depending on video resolution and compression:
  1. 1000BASE-T (1 Gigabit): Standard for compressed HD and 4K video, uses Cat5e/Cat6 copper cabling up to 100 meters
  2. 10GBASE-T (10 Gigabit Copper): For uncompressed 4K or higher bandwidth requirements, requires Cat6a or Cat7 cabling up to 100 meters
  3. 10GBASE-SR/LR (10 Gigabit Fiber): Fiber optic connections using SFP+ transceivers, SR (short range) for multimode fiber, LR (long range) for single-mode fiber
  4. 25GBASE-SR/LR (25 Gigabit Fiber): Used for high-capacity switch uplinks via SFP28 transceivers
IGMP
Internet Group Management Protocol: Manages multicast group memberships, critical for AV-over-IP systems.
IGMP Querier
A network device (often a switch or router) that sends IGMP query messages to maintain multicast group memberships when no router is present. Essential for proper multicast operation in MXnet networks.
IGMP Snooping
A feature that listens to IGMP messages to control multicast traffic efficiently, preventing unnecessary flooding.
LACP
Link Aggregation Control Protocol: Combines multiple physical links into one logical link for redundancy and increased bandwidth.

LLDP
Link Layer Discovery Protocol: Allows devices to advertise identity and capabilities to neighbors for easier network management.
MAC Address
Media Access Control Address: A unique identifier assigned to network interfaces for communication on the physical network segment.
Mentor
Mentor is the web-based setup and control interface that is hosted on the CBOX
MM Fiber
Multimode Fiber: Fiber optic cable for short-distance data transmission within buildings or within racks.
MTU/Jumbo Frames
Maximum Transmission Unit: defines the largest packet size allowed on the network. Standard Ethernet uses 1500-byte packets, but many AV-over-IP protocols use jumbo frames (up to 9000 bytes) to reduce processing overhead and improve efficiency. MXnet switches must have jumbo frame support enabled for optimal performance with SDVoE and similar protocols.
Network Switch
A network switch is a device that connects multiple devices within a local area network (LAN) and enables them to communicate efficiently. MXnet endpoints requires the use of certain network switch protocols to properly route AV traffic to its destination. 
Node
A networked device within the MXnet system, such as an encoder, decoder, transceiver, or switch.
PoE
Power over Ethernet: Technology that delivers electrical power alongside data over standard Ethernet cables, eliminating the need for separate power connections at each device. Three IEEE standards define PoE capabilities:
  1. IEEE 802.3af (PoE): Delivers up to 15.4W per port
  2. IEEE 802.3at (PoE+): Delivers up to 30W per port
  3. IEEE 802.3bt (PoE++): Delivers up to 60W (Type 3) or 90W (Type 4) per port
Port Group
A logical grouping of switch ports for configuration purposes, often used for VLAN or QoS settings.
QoS
A logical grouping of switch ports for configuration purposes, often used for VLAN or QoS settings.
QSFP+
Quad Small Form-factor Pluggable Plus: Supports 40Gbps speeds for backbone or aggregation links.
QSFP28
Supports 100Gbps speeds for ultra-high-capacity uplinks in enterprise networks.
RJ45
Standard connector for Ethernet cables used in copper-based networking.
Ring Topology
A network layout where devices form a closed loop. Provides redundancy but requires proper configuration (e.g., STP).
SDVoE
Software Defined Video over Ethernet: A standard for delivering uncompressed, low-latency video over IP networks.
SFP
Small Form-factor Pluggable: A compact, hot-swappable transceiver module supporting 1Gbps speeds over fiber or copper.
SFP+
Enhanced version of SFP supporting 10Gbps speeds, commonly used for high-bandwidth AV-over-IP links.
SFP28
A transceiver module supporting 25Gbps speeds for advanced networking.
SM Fiber
Single-mode Fiber: Fiber optic cable for long-distance data transmission, often used in campus or enterprise backbones.
Speed-Duplex
Refers to the speed (e.g., 1G, 10G) and duplex mode (full or half) of an Ethernet link. MXnet requires full duplex for optimal performance.
SR/LR Fiber
Short Range / Long Range: Designations for fiber transceivers indicating supported transmission distances.
STP
Spanning Tree Protocol: Prevents network loops by creating a loop-free logical topology.
Star Topolgy
A network layout where all devices connect to a central switch. Recommended for MXnet deployments.
Switch Stacking
Linking multiple switches to operate as a single logical unit for scalability and simplified management.
Transceivers
Designed to encode and/or decode. This allows them to connect to a source device or sink device and in some cases both simultaneously (based on model).
Trunk Port
A switch port configured to carry traffic for multiple VLANs, typically used for uplinks between switches.
VLAN
Virtual Local Area Network: Logical segmentation of a network to isolate traffic for security and performance.
VSF
Virtual Switch Framework: A technology that allows multiple switches to operate as a single virtual switch for simplified management and redundancy.

Wiring and Connections

Proper wiring and connections are critical for reliable MXnet system performance. Everything about a successful MXnet installation revolves around the network cabling itself. The quality, distance, and handling of cables can all affect signal integrity, data throughput, and overall system reliability. This section provides detailed guidance on Ethernet cabling, fiber optic connections, power connections, and grounding practices.

Ethernet Copper Connections

Cable Requirements by System Type

MXnet 1G Systems (Evolution I, Evolution II, USP)
Cable Type: CAT 5e or better (CAT 6/CAT 6a recommended)Connector: Standard 8-pin RJ45
Operation: 1000BASE-T full duplex
Maximum Distance: 100 meters (328 feet)

MXnet 10G Systems (SDVoE)
Cable Type: Cat6a or better required
Connector: Standard 8-pin RJ45
Operation: 10GBASE-T full duplex
Maximum Distance: 100 meters (328 feet) with CAT 6a
Info
Important: Using Cat5e or Cat6 for 10G connections will severely limit performance or drastically reduce maximum distance. Always use Cat6a or better for 10GBASE-T applications.

Termination Standards

Follow TIA/EIA T568A or T568B Wiring Standards
Notes
T568B is recommended for consistency with most commercial installations

Warning
Critical: Do not mix termination standards on the same cable (e.g., T568A on one end and T568B on the other). Both ends of each cable must use the same standard

Connector Best Practices

  1. Use standard crimp-style RJ45 connectors
  2. Avoid push-through or "EZ" type connectors - these have exposed copper wiring at the tips that can cause signal interference and crosstalk
  3. Do not untwist wire pairs more than ½ inch when terminating (¼ inch or less is preferred)
  4. Remove only as much outer sheath as necessary to terminate properly
  5. Ensure all eight conductors are fully inserted and make proper contact
  6. Verify terminations with a cable tester before deployment

Cable Handling and Installation Best Practices

Bend Radius
  1. Maintain a minimum 2-inch bend radius for standard Ethernet cable (4 times the cable diameter)
  2. Avoid sharp bends, kinks, or creases that can damage internal conductors
  3. Use corner radius guides or cable management accessories for tight turns
Cable Routing
  1. Keep network cables away from AC power lines to reduce electromagnetic interference (EMI)
  2. Maintain at least 6 inches of separation from power cables when running parallel
  3. Cross power cables at 90-degree angles when unavoidable
  4. Use shielded cable (STP) in high-EMI environments
Cable Management
  1. Bundle cables loosely with velcro straps or loose zip ties
  2. Avoid tight zip ties, metal clamps, or staples that can compress or damage cables
  3. Group encoder cables together and decoder cables together on the switch for easier management
  4. Leave service loops at both ends for future adjustments or re-terminations
Cable Labeling
  1. Label both ends of every cable for easy identification
  2. Include source and destination information (e.g., "SW1-Port12 to Conference-Rm-Decoder")
  3. Use consistent labeling schemes across the entire installation
  4. Consider color-coded cables or labels for different VLANs or zones
Cable Pulling
  1. Do not exceed the manufacturer's maximum pulling tension (typically 25 lbs for Cat6/Cat6a)
  2. Pulling too hard can cause wire pairs to untwist and degrade performance
  3. Use proper cable pulling grips or kellems grips for long runs
  4. Support cables every 4-5 feet in vertical runs

Fiber Optic Connections

Fiber optic connections provide extended distance capabilities, immunity to electromagnetic interference, and enhanced security compared to copper cabling. MXnet switches support various fiber transceiver types for different speed and distance requirements.

Fiber Transceiver Types

Fiber Transceiver Type
Speed
MXnet Use Case
SFP (Small Form-factor Pluggable
1G (1000BASE-FX/SX/LX/EX/ZX)
1G endpoint connections
SFP+ (Enhanced Small Form-factor Pluggable)
10G (10GBASE-SR/LR/ER/ZR)
SDVoE endpoint connections or 1G switch uplinks
SFP28
25G (25GBASE-SR/LR)
High-capacity 10G switch-to-switch uplinks (AC-MXNET-SW12C)
QSFP+ (Quad Small Form-factor Pluggable Plus)
40G (40GBASE-SR4/LR4/ER4/CSR4)
Very high-capacity 10G switch-to-switch backbone connections
QSFP28 (Quad Small Form-factor Pluggable 28)
100G (100GBASE-SR4/LR4/ER4/DR/FR/CWDM4/SWDM4)
Ultra-high-capacity backbone links between core switches or aggregation points

Info
Fiber modules are not included with MXnet switches. However, they can be purchased directly from AVPro as a separate item.

Fiber Cable Types

Multimode Fiber Type
Core Diameter (um)
Light Source
100 MbE
1 GbE
10 GbE
25 GbE
40 GbE
100 GbE
Single-Mode (SM)








    OS1
9
1310/1550 nm Laser
5 km
5 km
10 km
10 km
10 km
10 km
    OS2
9
1310/1550 nm Laser
5 km
10 km
10 km
10 km
10 km
10 km+
Multimode (MM)








        OM1
62.5
LED
2 km
275 m
33 m
—
—
—
    OM2
50
LED
2 km 
550 m
82 m
—
—
—
    OM3
50
850 nm VSCEL Laser
2 km
550 m
300 m
70 m
100 m
100 m
        OM4
50
850 nm VSCEL Laser
2 km
550 m
400 m
100 m
150 m
150 m
    OM5
50
850-953 nm VSCEL (SWDM Capable)
2 km
550 m
400 m
100-150 m
150 m
150-200 m
(SWDM4)

Fiber Connector Types

Connector Type
Full Name
Form Factor/Fiber Count
Use Case
LC
Lucent Connector
Small form factor, duplex (2 fibers)
SFP, SFP+, SFP28, QSFP28-LR
SC
Subscriber Connector
Standard size, duplex (2 fibers)
Legacy equipment/panels
MPO/MTP
Multi-fiber Push On/Pull Off
12, 24, or 32 fibers (high-density)
QSFP+, QSFP28-SR
ST
Straight Tip
Single fiber
Legacy multimode fiber installs
FC
Ferrule Connector
Single fiber
Precision single-mode connections (legacy)

Fiber Reference Table

SFP Form Factor
Ethernet Standard
Speed
Fiber Type
Wavelength (nm)
Max Distance
Connector
100Base-FX
100 Mbps
OM1/OM2
1310
2 km
LC
1000Base-SX
1 Gbps
OM2-OM4
850
220-550 m
LC
1000Base-LX
1 Gbps
OS1-OS2
1310
10 km
LC
1000Base-EX/ZX
1 Gbps
OS2
1310/1550
40-80 km
LC

SFP+ Form Factor
Ethernet StandardSpeedFiber TypeWavelength (nm)Max DistanceConnector
10GBase-SR10 GbpsOM3/OM4850300-400 mLC
10GBase-LR10 GbpsOS2131010 kmLC
10GBase-ER10 GbpsOS2155040 kmLC
10GBase-ZR10 GbpsOS2155080 kmLC

SFP28 Form Factor
Ethernet StandardSpeedFiber TypeWavelength (nm)Max DistanceConnector
25GBase-SR25 GbpsOM4/OM585070-100 mLC
25GBase-LR25 GbpsOS2131010 kmLC
25GBase-ER25 GbpsOS2155040 kmLC
25GBase-BX254 GbpsOS21270/133010 kmLC simplex

QSFP+ Form Factor
Ethernet StandardSpeedFiber TypeWavelength (nm)Max DistanceConnector
40GBase-SR440 GbpsOM3/OM4850100-150 mMPO-12
40GBase-LR440 GbpsOS2131010 kmLC (duplex)
40GBase-ER440 GbpsOS2155040 kmLC
40GBase-CSR440 GbpsOM4850300 mMPO-12

QSFP28 Form Factor
Ethernet StandardSpeedFiber TypeWavelength (nm)Max DistanceConnector
100GBase-SR4100 GbpsOM4/OM5850100-150 mMPO-12
100GBase-LR4100 GbpsOS2131010 kmLC
100GBase-ER4100 GbpsOS2155040 kmLC
100GBase-DR100 GbpsOS21310500 mLC
100GBase-FR
100 Gbps
OS2
1310
2 km
LC
100GBase-CWDM4/SWDM4
100 Gbps
OM5 (SWDM) or OS2
850-953 (SWDM)
1310 (CWDM)
150 m (SWDM)
2 km (CWDM)
LC
Warning
Critical: Always match the transceiver type, wavelength, and connector to the correct fiber type and polarity.
  1. SR / SX / SR4 modules are designed for multimode fiber (OM3, OM4, OM5).
  2. LR / ER / ZR modules are designed for single-mode fiber (OS1, OS2).
  3. Mismatched fiber types or connectors (e.g., SR module on OS2) can result in link failure, high loss, or severe signal degradation.
  4. Always verify polarity (A↔B) and connector type (LC, MPO, or simplex) before connecting.

Fiber Transceiver Installation/Removal Procedure

Installation Steps:
  1. Prepare for Installation
    1. Put on an ESD wrist strap or anti-static gloves to prevent static discharge damage
                  
    2. Remove the dust cap from the transceiver module

    3. Inspect the fiber bores for contamination or damage
  2. Insert the Transceiver
    1. Align the transceiver with the guide rails inside the switch port
    2. Push the transceiver gently along the guide rails until you feel it snap into place. The transceiver should be fully seated and flush with the switch faceplate
Idea
The fiber transceiver modules are hot-swappable, meaning that they can be inserted or removed while power is still present in the system.
Warning
Ensure correct orientation - do not insert the transceiver upside down.
Do not look directly into the fiber bores inside the fiber transceiver module while the network switch is operating as the laser may harm the eyes.
3. Connect Fiber Cables
  1. Remove dust caps from fiber cable connectors

  2. Insert fiber connectors into the transceiver until they click into place

  3. Verify secure connection

4. Verify Operation
  1. Check link LED indicators on the switch
  2. Use switch management interface to verify link status and speed
Transceiver Removal Procedure:
1. Disconnect fiber cables from the transceiver
    1. Locate the release mechanism (pull tab, bail latch, or release button depending on transceiver type)
    2. Activate the release mechanism while gently pulling the transceiver straight out
    3. Install dust caps on the transceiver and fiber cable connectors immediately
            
    4. Store removed transceivers in protective cases
Notes
Important Notes:
Dust Protection: Always use dust caps on transceivers and fiber connectors when not connected to prevent contamination
Cleaning: Clean fiber connectors with approved fiber optic cleaning tools before each connection

Fiber Cable Handling Best Practices

Bend Radius
  1. Maintain minimum bend radius of 10 times the cable diameter (typically 1.5 inches for standard fiber patch cables)
  2. Tighter bends can cause signal loss or permanent fiber damage
  3. Use fiber-appropriate cable management accessories
Cable Routing
  1. Avoid crossing fiber cables with heavy equipment or high-traffic areas where they could be damaged
  2. Keep fiber cables away from sharp edges that could cut the jacket
  3. Do not pinch, crimp, or compress fiber cables
Cable Management
  1. Use velcro straps or loose zip ties - never over-tighten
  2. Maintain service loops for future adjustments
  3. Keep fiber cables organized and labeled at both ends
Testing and Verification
  1. Test all fiber runs with an optical power meter and light source before termination
  2. Verify acceptable insertion loss (typically <1.5dB for multimode, <0.5dB for single-mode)
  3. Document test results for each fiber run

Power Connections

Proper power connections are essential for safe and reliable switch operation. Different MXnet switch models support various power configurations.

AC Power Connections

Standard AC Power
  1. Connect to a grounded AC outlet using the supplied power cord
  2. Verify the outlet provides the correct voltage for your region (typically 100-240VAC, 50/60Hz)
  3. Ensure the outlet is properly grounded with a functioning ground pin
  4. The power outlet and switch power inlet should be easily accessible for emergency disconnection in the event of electrical hazard or malfunction
Power Cord Requirements
  1. Use only the power cord supplied with the switch or an approved replacement
  2. Ensure the cord is rated for the switch's power consumption
  3. Inspect cords regularly for damage and replace if frayed or damaged

DC Power Connections

Some models support DC power input in addition to AC:

DC Power Requirements:
  1. Verify DC voltage requirements for your specific switch model (typically -48VDC for telecom applications)
  2. Use appropriate wire gauge based on current draw and cable length
  3. Observe correct polarity - reversing polarity can damage the switch
  4. Use terminal block or connector as specified in switch documentation
  5. Secure all DC connections to prevent accidental disconnection

Redundant Power Best Practices:

  1. Connect each power supply to a separate electrical circuit for true redundancy
  2. Ensure both circuits are fed from different breaker panels or UPS units when possible
  3. Verify automatic failover operation after installation
  4. Monitor power supply status through switch management interface

Uninterruptible Power Supply (UPS) Recommendations

Always use UPS power for network switches in mission-critical installations:
  1. Protects against power outages and brownouts
  2. Provides clean, regulated power to sensitive electronics
  3. Allows graceful shutdown or continued operation during brief outages
  4. Enables monitoring of power events through SNMP or network management
UPS Sizing:
  1. Calculate total power consumption of all switches and connected PoE devices
  2. Size UPS for at least 125% of total load
  3. Consider desired runtime (typically 15-30 minutes minimum for graceful shutdown)
  4. Account for battery aging (replace batteries per manufacturer recommendations)
Power Budget Planning for PoE
  1. List all devices that will be powered by each switch
  2. Identify the PoE standard required by each device (802.3af/at/bt)
  3. Sum the maximum power draw of all connected devices
  4. Verify the total is less than 80% of the switch's PoE power budget
PoE Budgeting Example:
  1. Switch: AC-MXNET-10G-SW24C (1000W PoE budget)
  2. Maximum usable: 800W (80% rule)
  3. Connected devices: 20 decoders at 30W each = 600W total
  4. Result: Within budget with 200W headroom

Grounding and Surge Protection

Proper grounding is essential for safety, electromagnetic compatibility, and protection against electrical hazards.
Chassis Grounding

Grounding Lug:

Each MXnet switch includes a chassis grounding lug (typically on the rear panel). This lug must be bonded to the equipment rack's grounding bar or building earth ground. Use copper grounding wire appropriately sized per local electrical codes (typically 6-12 AWG). Ensure low-resistance connection by cleaning contact surfaces and using star washers

Grounding Best Practices:
  1. Bond all equipment in the rack to a common grounding point
  2. Connect the rack's grounding bar to building earth ground
  3. Follow local electrical codes and standards (NEC in US, IEC internationally)
  4. Verify ground integrity with a multimeter (should measure <1 ohm to earth ground)
  5. Document grounding connections for future reference

Surge Protection

AC Surge Protection:
  1. Install surge protectors or power conditioners on AC power inputs
  2. Use surge protectors rated for the total load of connected equipment
  3. Replace surge protectors after significant lightning strikes or surges (many have indicator lights showing protection status)
  4. Consider whole-facility surge protection at the main electrical panel for comprehensive protection
Network Surge Protection:
  1. For installations in lightning-prone areas, consider Ethernet surge protectors on long outdoor or above-ground cable runs
  2. Fiber optic cables are immune to electrical surges (one advantage of fiber over copper)
  3. Ground shielded Ethernet cables properly at both ends to reduce ESD risks

ESD (Electrostatic Discharge) Protection

  1. Use ESD wrist straps when handling transceivers or performing internal maintenance
  2. Store spare transceivers and components in anti-static bags
  3. Maintain proper humidity levels (30-50% RH) to reduce static buildup

Product Overviews

MXnet switches are available in two primary categories to match different application requirements:

1G Switches:
Designed for MXnet Evolution I, Evolution II, and USP platforms using lossless compression (proprietary MJPEG) and compressed video codecs (H.265/H.264). Available in 8-port, 10-port, 12-port, 24-port, and 48-port configurations with various PoE power budgets and fiber uplink options. Ideal for installations where HD or 4K distribution meets quality requirements and budget considerations. The new E-series switches offer enhanced features and compatibility with the upcoming Universal Streaming Platform (USP) while maintaining backward compatibility with existing 1G MXnet systems. Available in 24-port and 48-port configurations.
10G Switches:
Engineered for SDVoE applications requiring uncompressed 4K video transport. Available with copper ports (12-port and 24-port models) for installations with shorter cable runs, or fiber ports (24-port and 48-port models) for maximum flexibility and extended distances. 10G switches support the bandwidth demands of uncompressed video while providing high-speed uplinks for multi-switch installations.
Info
For detailed specifications, port configurations, and model-specific features, refer the Specs section on the AVPro Global website (https://www.avproglobal.com/) for each switch

Flexible Connectivity Options

MXnet switches offer diverse port configurations to match specific installation requirements:
  1. 1G Copper Ports (RJ45): Standard Gigabit Ethernet connections using CAT 5e or better cabling up to 100 meters (328 feet)
  2. 10G Copper Ports (10GBASE-T): High-bandwidth connections requiring CAT 6a or better cabling up to 100 meters (328 feet)
  3. SFP Fiber Slots: 1G fiber connections for extended distances beyond copper limitations
  4. SFP+ Fiber Slots: 10G fiber connections for high-bandwidth connections to endpoints over extended distances or for switch-to-switch uplinks
  5. SFP28 Fiber Slots: 25G fiber connections for very high-capacity switch-to-switch uplinks
  6. QSFP+ Slots: 40G connections for ultra-high-capacity backbone links in large installations
  7. QSFP28 Slots: 100G fiber connections for extremely high-bandwidth switch-to-switch uplinks or backbone aggregation, supporting breakout to 4x25G for flexible deployment in large-scale installations.
Info
Select models feature combo ports allowing you to choose between copper or fiber connectivity on the same physical port position, providing maximum deployment flexibility.

Scalable Power Delivery

PoE-enabled switches eliminate the need for separate power infrastructure:
Switch Model
PoE Standards
Total Power Budget
AC-MXNET-SW12
PoE, PoE+
125W
AC-MXNET-SW24
PoE, PoE+
370W
AC-MXNET-SW48
PoE, PoE+
740W
AC-MXNET-SW12C
PoE, PoE+, PoE++ (90W)
370W
AC-MXNET-SW24C
PoE, PoE+, PoE++ (60W, ports 1-8)
1000W
AC-MXNET-SW24E
PoE, PoE+
370W
AC-MXNET-SW48E
PoE, PoE+
740W
NotesPoE = 802.3af, PoE+ = 802.3at, PoE++ = 802.3bt
When planning installations, calculate total PoE requirements by adding the power consumption of all connected encoders, decoders, transceivers, transmitters, receivers, control boxes, control systems, and/or nodes. Always maintain at least 20% headroom below the switch's total PoE budget for reliability and to accommodate future expansion.

Redundant Power Options

Select models support redundant power supplies for mission-critical installations:
Models with Redundant Power:
Model
Power Supply Configuration

Redundancy Type
AC-MXNET-SW48
1x AC PSU + 1x DC PSU
AC + DC Redundant
AC-MXNET-10G-SW12C
1x AC PSU + 1x DC PSU
AC + DC Redundant
AC-MXNET-10G-SW24C
1x Hot-swappable AC PSU (supports 2 total)
Optional Dual AC Redundant (Add-on)
AC-MXNET-10G-SW24Q
1x AC PSU + 1x DC PSU
AC + DC Redundant
AC-MXNET-10G-SW48Q/48HQ
2x Hot-swappable AC PSUs
Dual AC Redundant
Info
Redundant power configurations allow automatic failover if one power supply fails, and hot-swappable PSUs enable replacement without powering down the switch.

System Cooling and Airflow

Poor thermal management can greatly shorten the lifespan of electronic devices. It’s important to use effective cooling methods—whether passive or active—to draw heat away from internal components and keep them operating within their specified temperature range. Heat buildup can also occur due to poor layout or cable placement, which can block airflow and create localized hotspots. To avoid this, ensure cables and nearby equipment do not obstruct ventilation around the components.

All MXnet switches are 1RU rack-mountable units with active cooling. Understanding airflow direction is critical for proper rack design:

  1. Side-to-Side Airflow: Most models draw cool air from one side and exhaust from the opposite side
  2. Front-to-Back Airflow: AC-MXNET-10G-SW48Q and SW48HQ draw cool air from the front and exhaust out the rear
Ensure adequate clearance for airflow and avoid blocking ventilation openings. Rack designs should consider airflow patterns to prevent hot exhaust from one device being drawn into another's intake. Maintain ambient temperature below 45°C (113°F) for reliable operation.

Hardware I/O

Port Diagrams for 1G Switches

AC-MXNET-SW10
AC-MXNET-SW12
AC-MXNET-SW24
AC-MXNET-SW48
AC-MXNET-SW10

Front Panel



Left Side Panel (Ventilation)


Right Side Panel (Ventilation)


ID
Connector
Description
1
Ethernet Ports
8x Gigabit RJ45 ports for endpoint connections
2
SFP Fiber
2x SFP Fiber ports for endpoint connections
3
Console Port
RJ45 console port for CLI access
4
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
5
Power Input
AC IEC inlet with power switch
6
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
7
Cooling Vents
Passive vents with side ventilation for airflow
AC-MXNET-SW12

Front Panel



Left Side Panel (Ventilation)


Right Side Panel (Ventilation)


ID
Connector
Description
1
Ethernet Ports
8x Gigabit RJ45 ports for endpoint connections
2
SFP+ Fiber
4x SFP Fiber+ ports for uplinking/stacking
3
Console Port
RJ45 console port for CLI access
4
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
5
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
6
Power Input
AC IEC inlet with power switch
7
Cooling Vents
Passive vents with side ventilation for airflow

AC-MXNET-SW24

Front Panel



Back Panel


Left Side Panel (Air intake)


Right Side Panel (Ventilation)


ID
Connector
Description
1
Ethernet Ports
24x Gigabit RJ45 ports for endpoint connections
2
Combo ports
4x Fiber ports for endpoint connections that can be activated instead of copper ports 22-24
3
SFP Fiber
4x SFP+ Fiber ports for uplinking/stacking
4
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
5
Console Port
RJ45 console port for CLI access
6
Management Port
Dedicated 1G RJ45 for out‑of‑band management
7
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
8
Power Input
AC IEC inlet with power switch
9
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
10
Cooling Fans
Vents for air intake fan(s)
11
Ventilation
Side ventilation for airflow
AC-MXNET-SW48

Front Panel



Back Panel


Left Side Panel (Air intake)


Right Side Panel (Ventilation)


ID
Connector
Description
1
Ethernet Ports
48x Gigabit RJ45 ports for endpoint connections
2
SFP+ Fiber
4x SFP+ Fiber ports for uplinking/stacking
3
Console Port
RJ45 console port for CLI access
4
Management Port
Dedicated 1G RJ45 for out‑of‑band management
5
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
6
Console Port
LED Indicators
RJ45 console port for CLI access
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
7
AC Power Input
AC IEC inlet with power switch
8
DC Power Input
48V DC inlet
9
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
10
Cooling Fans
Passive vents with side ventilation for airflow
11
Ventilation
Vents for air intake fan(s)

Port Diagrams for 1G E-series Switches

AC-MXNET-SW24E
AC-MXNET-SW48E
AC-MXNET-SW24E

Front Panel


Back Panel


Left Side Panel (Air intake)


Right Side Panel (Ventilation)



ID
Connector
Description
1
Ethernet Ports
24x Gigabit RJ45 ports for endpoint connections
2
SFP Uplinks
4x SFP+ (10G) uplinks
3
Console Port
RJ45 console port for CLI access
4
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
5
Power Input
AC IEC inlet with power switch
6
Grounding Screw
Chassis grouding lug for bonding to rack/earth ground
7
Cooling Fans
Vents for air intake fan(s)
8
Ventilation
Side ventilation for airflow
AC-MXNET-SW48E

Front Panel


Back Panel


Left Side Panel (Air intake)


Right Side Panel (Ventilation)



ID
Connector
Description
1
Ethernet Ports
48x Gigabit RJ45 ports for endpoint connections
2
SFP+ Uplinks
6x SFP+ (10G) uplinks
3
Console Port
RJ45 console port for CLI access
4
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
5
Power Input
AC IEC inlet with power switch
6
Grounding Screw
Chassis grouding lug for bonding to rack/earth ground
7
Cooling Fans
Vents for air intake fan(s)
8
Ventilation
Side ventilation for airflow

Port Diagrams for 10G Switches

AC-MXNET-10G-SW12C
AC-MXNET-10G-SW24C
AC-MXNET-10G-SW24Q
AC-MXNET-10G-SW48Q
AC-MXNET-10G-SW12C

Front Panel


Back Panel


Left Side Panel (Air intake)



Right Side Panel (Ventilation)



ID
Connector
Description
1
Ethernet Ports
12x 10GbE RJ45 ports for endpoint connections
2
SFP28 Uplinks
6x SFP28 (25G) uplinks
3
Console Port
RJ45 console port for CLI access
4
Management Port
Dedicated 1G RJ45 for out‑of‑band management
5
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
6
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
7
AC Power Input
AC IEC inlet
8
DC Power Input
48V-57V DC inlet
9
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
10
Cooling Fans
Vents for air intake fan(s)
11
Ventilation
Side ventilation for airflow
AC-MXNET-10G-SW24C

Front Panel


Back Panel



ID
Connector
Description
1
Ethernet Ports
24x 10GbE RJ45 ports for endpoint connections
2
QSFP Uplinks
2x QSFP (40G) uplinks
3
Console Port
RJ45 console port for CLI access
4
Management Port
Dedicated 1G RJ45 for out‑of‑band management
5
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
6
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
7
AC Power Input
AC IEC inlet
8
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
9
Cooling Fans
Vents for air intake fan(s)

AC-MXNET-10G-SW24Q

Front Panel


Back Panel


Left Side Panel (Air intake)



Right Side Panel (Ventilation)



ID
Connector
Description
1
Ethernet Ports
24x 10G SFP ports for endpoint connections
2
QSFP Uplinks
2x QSFP (40G) uplinks
3
Console Port
RJ45 console port for CLI access
4
Management Port
Dedicated 1G RJ45 for out‑of‑band management
5
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
6
LED Indicators
Power:
  1. Green = On
  2. Off = No Power
Link/Activity:
  1. Green = Link
  2. Blinking = Activity
PoE:
  1. Amber = PoE Active
  2. Off = No PoE
7
AC Power Input
AC IEC inlet
8
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
9
DC Power Input
36V-72V DC inlet
10
Cooling Fans
Vents for air intake fan(s)
11
Ventilation
Side ventilation for airflow
AC-MXNET-10G-SW48Q

Front Panel


Back Panel


Left Side Panel (Air intake)



Right Side Panel (Ventilation)



ID
Connector
Description
1
Ethernet Ports
48x 10G SFP+ ports for endpoint connections
2
QSFP Uplinks
6x QSFP (40G) uplinks
3
Console Port
RJ45 console port for CLI access
4
Management Port
Dedicated 1G RJ45 for out‑of‑band management
5
USB-A (Firmware)
USB-A port for loading switch firmware (nos.img); supports local image import
6
AC Power Input
AC IEC inlet
7
Grounding Screw
Chassis grounding lug for bonding to rack/earth ground
8
Hot Swappable Cooling Fans
Hot-swappable redundancy fans for cross-ventilation and steerable air flow
9
Cooling Fans
Vents for air intake fan(s)
10
Ventilation
Side ventilation for airflow

Networking Best Practices

This section covers hardware-level networking best practices for designing and deploying MXnet switch infrastructure. For software configuration details (VLAN setup, IGMP configuration, spanning tree settings), refer to the MXnet CLI Guide and MXnet Web GUI Guide.

Understanding Network Switch Roles

Before discussing topologies and design practices, it's important to understand the different roles switches can play in a network hierarchy. These terms originate from traditional IT networking but have important distinctions when applied to AV installations.

Traditional Network Switch Hierarchy

Access Switch:
A network switch located at the "edge" or "access layer" of a network, connecting end devices (computers, printers, phones) to the rest of the network infrastructure. In traditional IT networks, access switches handle the actual connection of endpoint devices and typically feature many lower-speed ports (1G) with a few high-speed uplink ports.
Distribution Switch:
A network switch in a hierarchical network architecture that acts as a bridge between the access layer and the core layer. Distribution switches handle routing, security policy enforcement, and data aggregation from multiple access switches before forwarding traffic to the core network. They typically feature higher port speeds and advanced routing capabilities.
Core Switch:
A network backbone switch responsible for high-speed data transfer within a network hierarchy. In traditional IT networks, core switches connect distribution switches to aggregate traffic and provide reliable connectivity across the entire network. Core switches focus exclusively on fast, reliable packet forwarding and do not connect directly to end devices.

Traditional 3-tier Switch Topology:


AV Network Switch Hierarchy: A Critical Difference

AV networks operate fundamentally differently than traditional IT networks. This distinction is crucial for anyone coming from an IT networking background or trying to understand how AV switching differs from enterprise data networking.

In traditional IT networks:
  1. Access switches connect to endpoints only
  2. Distribution switches aggregate access switches only
  3. Core switches connect to distribution switches only (never to endpoints)
  4. Strict three-tier hierarchy is maintained
In AV networks (including MXnet):
  1. Core switches often connect directly to endpoints (encoders, decoders, transceivers, control boxes, control systems, and nodes)
  2. This makes AV core switches function simultaneously as both core and access switches
  3. The traditional three-tier hierarchy is "collapsed" into a flatter structure
  4. This is intentional and optimized for AV distribution patterns
Why AV Networks Are Different:
  1. Traffic Patterns: AV systems typically use one-to-many or many-to-many video distribution (multicast), whereas IT networks are primarily one-to-one communication. This benefits from a flatter topology.
  2. Latency Sensitivity: Video and audio require minimal latency. Fewer switch "hops" between source and destination reduces latency.
  3. High Bandwidth Per Endpoint: Individual AV endpoints consume significantly more bandwidth (1-10 Gbps per encoder/decoder) than typical IT devices (10-100 Mbps). Connecting high-bandwidth endpoints directly to core switches is efficient.
  4. Centralized Equipment: AV installations often centralize source equipment in equipment rooms, making it practical to connect many endpoints directly to core switches.

The Collapsed Core or Flat Network Topology:

Most MXnet installations use what's called a collapsed core or flat network topology:
  1. One or more high-capacity switches serve as both core and access layer
  2. These switches connect directly to encoders, decoders, and transceivers (access function)
  3. These same switches also interconnect with each other via high-speed uplinks (core function)
  4. Distribution switches may be added in very large installations, but the core/access collapse is typical
Collapsed AV Network Topology:

Info
When you see documentation referring to "core switches" in MXnet installations, understand that these switches are likely connecting directly to endpoints—unlike traditional IT core switches. This is normal and expected in AV network design.

Network Topologies for MXnet Installations

The physical arrangement of how switches connect together significantly impacts installation complexity, reliability, scalability, and troubleshooting. MXnet switches support various topology configurations to match different installation requirements.
Diagram:


Description:
All endpoint switches connect directly to one or more central core switches. In smaller installations, a single switch may serve all endpoints. In larger installations, multiple switches connect to one or more central core switches.
Characteristics:
  1. Simple, easy-to-understand layout
  2. No loops to manage (simplifies spanning tree configuration)
  3. Problems are isolated to specific branches
  4. Central management point
  5. Straightforward cable routing from equipment rooms
When to Use:
  1. Recommended as the default topology for most MXnet installations
  2. Ideal when equipment rooms have centralized locations
  3. Best for installations requiring easy troubleshooting
  4. Suitable for installations of any size
Physical Implementation:
  1. Centralize one or more high-capacity switch in the main equipment room
  2. Run individual cables (copper or fiber) from the central switch(es) to each remote location
  3. In multi-switch installations, use high-speed uplinks between core switches
  4. Connect endpoints directly to the nearest switch
Hardware Considerations:
  1. Core switches should have adequate port density for all connections
  2. Use switches with high-speed uplink capabilities (SFP+/SFP28/QSFP+) for inter-switch connections
  3. If a PoE swtich is used as a core switch, ensure it has sufficient PoE budget for directly connected endpoints
  4. Plan for future expansion by leaving unused uplink ports on core switches
Advantages:
  1. Easiest to troubleshoot
  2. Most straightforward to document
  3. Least complex spanning tree configuration
  4. Easy to expand by adding switches
  5. Minimal cable interdependency
Disadvantages:
  1. May require longer cable runs from remote locations back to central core
  2. Single point of failure if only one core switch is used (mitigate with redundant cores)
  3. Can require significant fiber infrastructure for large buildings

Daisy-Chain Topology

Diagram:

Description:
Switches connect in sequence, one after another (Switch A → Switch B → Switch C → Switch D). Each switch uplinks to the next switch in the chain.
Characteristics:
  1. Follows physical layout of the building or installation
  2. Simple cabling between adjacent switches
  3. Creates dependency—downstream switches rely on upstream connections
  4. Common in AV installations where switches are located along a hallway or in adjacent rooms
When to Use:
  1. When switches are physically located in a linear arrangement
  2. In buildings where running cables back to a central location is impractical
  3. For phased installations where switches are added over time
  4. When budget or infrastructure limits preclude star topology
Physical Implementation:
  1. Connect switches sequentially using high-speed uplinks
  2. Limit chain length to 3-4 switches maximum
  3. Use link aggregation (LACP) on uplinks where supported for increased bandwidth and redundancy
  4. Ensure first switch in chain has adequate uplink capacity to core network or CBOX
Hardware Considerations:
  1. Use fiber uplinks for longer distances between switches
  2. Each switch in the chain passes traffic for all downstream switches (accumulates bandwidth)
  3. First switch in chain carries the most traffic—select the highest-capacity model rq
Alert
Uplink connections must have higher speed than total endpoint bandwidth
Avoid bottlenecks by ensuring uplink speed exceeds sum of active endpoint speeds
Info
Example: If a switch has 24x 1G endpoints, the uplink should be 10G minimum
Advantages:
  1. Simpler cabling when switches follow building layout
  2. Easier to run cables between adjacent rooms than back to central location
  3. Can be cost-effective for linear installations
  4. Allows phased expansion
Disadvantages:
  1. Single point of failure—if any connection breaks, all downstream switches lose connectivity
  2. More difficult to troubleshoot (need to check each link in sequence)
  3. Upstream switches carry aggregated traffic from all downstream switches (potential bottleneck)
  4. Latency increases with each hop
  5. Requires careful bandwidth planning to avoid congestion
Best Practices for Daisy-Chain:
  1. Limit chain length to 3-4 switches
  2. Use the highest-speed uplinks practical (10G minimum, 25G preferred)
  3. Consider link aggregation (2x 10G bonded) for higher bandwidth and redundancy
  4. Monitor bandwidth utilization on uplinks closely
  5. Document the chain order clearly for troubleshooting
  6. Plan power redundancy—losing power to one switch can affect downstream switches

Ring Topology

Diagram:


Description:
Switches form a closed loop, with each switch connecting to two neighbors. The last switch connects back to the first, creating a continuous ring.
Characteristics:
  1. Provides redundancy—traffic can flow in either direction around the ring
  2. More complex to configure properly (requires spanning tree or ring protocols)
  3. If one connection fails, traffic automatically reroutes the opposite direction
  4. Less common in typical AV installations
When to Use:
  1. When maximum redundancy is required
  2. In mission-critical installations (control rooms, healthcare, live production)
  3. When physical layout naturally forms a ring (buildings around a courtyard, circular floor plan)
  4. Industrial or utility applications where ring topologies are standard
Physical Implementation:
  1. Connect switches in a ring using dual fiber uplinks
  2. Configure spanning tree protocol (STP) or ring protocols (refer to CLI Guide)
  3. Use switches with at least two high-speed uplink ports
  4. Ensure both directions of the ring have adequate bandwidth
Hardware Considerations:
  1. Requires switches with multiple high-speed uplink ports (minimum two SFP+/SFP28 ports per switch)
  2. Use fiber connections for reliability and distance capability
  3. Both ring directions should support full traffic load (design for 50% utilization in normal operation)
  4. Consider using switches with dedicated ring protocol support
Advantages:
  1. High redundancy—automatically recovers from single link failure
  2. Traffic can flow in either direction
  3. No single point of failure in the physical connections
  4. Suitable for geographically distributed installations
Disadvantages:
  1. More complex configuration (spanning tree or ring protocols)
  2. More difficult to troubleshoot
  3. Potential for broadcast storms if misconfigured
  4. Longer convergence time during failures (depends on protocol)
  5. Not all switches support ring protocols
Best Practices for Ring Topology:
  1. Only implement ring topologies if redundancy is truly required
  2. Ensure proper spanning tree or ring protocol configuration (see CLI Guide)
  3. Test failover behavior before deployment
  4. Monitor ring health continuously
  5. Document which ports form the ring clearly
  6. Consider using switches from the same firmware version for consistency

Hybrid/Mixed Topologies

Diagram (Star + Daisy Chain):


Description:
Combining multiple topology types within a single installation. Common in large deployments where different areas have different requirements.
Example Scenarios:
  1. Star topology from core switches to distribution switches in each building
  2. Daisy-chain topology connecting multiple switches within a single floor
  3. Ring topology connecting geographically distributed buildings with star topologies within each building
When to Use:
  1. Large installations spanning multiple buildings or campuses
  2. When different areas have different physical constraints
  3. Phased installations where topology evolves over time
Best Practices:
  1. Document topology clearly with diagrams showing each section
  2. Maintain consistent switch configurations within each topology section
  3. Use high-capacity core switches at topology intersection points
  4. Monitor inter-topology links closely (these carry the most traffic)

PoE Power Budget Planning

Proper PoE power planning ensures all endpoints receive adequate power without exceeding switch capabilities or creating safety hazards.
Calculate Total PoE Requirements

Step 1: Inventory All PoE Devices

List every device that will be powered by each switch:
  1. MXnet encoders (note specific models and power requirements)
  2. MXnet decoders (note specific models and power requirements)
  3. MXnet transceivers
  4. CBOX (if PoE-powered)
  5. Any other PoE devices (IP cameras, access points, etc.)

Step 2: Determine Per-Device Power Requirements

Identify the PoE standard and maximum power draw for each device:
  1. IEEE 802.3af (PoE): Up to 15.4W at switch, 12.95W at device
  2. IEEE 802.3at (PoE+): Up to 30W at switch, 25.5W at device
  3. IEEE 802.3bt Type 3 (PoE++): Up to 60W at switch, 51W at device
  4. IEEE 802.3bt Type 4 (PoE++): Up to 90W at switch, 71W at device
Alert
Refer to encoder/decoder datasheets for specific power requirements. Most MXnet endpoints require PoE (15W).

Step 3: Sum Total Power Requirements

Add the maximum power draw of all devices to be connected to each switch.

Step 4: Apply 80% Rule

Total device power should not exceed 80% of the switch's total PoE budget. This provides:
  1. Safety margin for power supply variation
  2. Headroom for future device additions
  3. Protection against overload conditions
  4. Allowance for cable loss (longer cables lose more power)
Example Calculation:
Switch: AC-MXNET-10G-SW24C
Total PoE Budget: 1000W
Maximum Usable (80%): 800W

Planned Devices:
16x 10G TCVRs (decoders) @ 15.4W each = 480W
4x 10G TCVRs (encoders)@ 15.4W each = 240W
Total: 370W

Result: Within 80% limit ✓ (370W < 800W)
Remaining headroom: 430W for future expansion

Monitoring PoE Consumption

Regularly monitor PoE consumption to:
  1. Verify devices are receiving adequate power
  2. Identify devices drawing excessive power (may indicate malfunction)
  3. Plan for future expansion
  4. Detect approaching budget limits

Monitoring Methods:

  1. MXnet Mentor: View real-time PoE consumption per port and total switch consumption
  2. CLI: Use show commands to display PoE statistics (see CLI Guide)
  3. Web GUI: Access PoE monitoring dashboard
  4. SNMP: Integrate with network management systems for alerting
Alert
Warning Signs:
  1. PoE consumption approaching 90% of total budget
  2. Devices not powering on (may indicate budget exceeded)
  3. Intermittent device operation (may indicate insufficient power)
  4. Switch reporting PoE overload conditions
Link Aggregation (LACP) and redundancy practices improve both performance and reliability by combining multiple physical connections or providing backup paths.

What It Is:

Link Aggregation Control Protocol (LACP / IEEE 802.3ad) combines multiple physical connections into a single logical high-bandwidth link. Traffic is load-balanced across all active links, and if one link fails, traffic automatically redistributes to remaining links.

Benefits:

  1. Increased bandwidth (2x 10G links = 20G aggregate)
  2. Automatic failover if a link fails
  3. Load balancing distributes traffic efficiently
  4. No downtime during single link failure

When to Use:

  1. Switch-to-switch uplinks carrying high traffic volumes
  2. Connections to critical infrastructure
  3. Any connection where redundancy and high bandwidth are needed

Hardware Requirements:

  1. Both switches must support LACP
  2. Use identical link speeds in the aggregation group (e.g. don't mix 1G and 10G)
  3. Use same cable type (all copper or all fiber, not mixed). See Wiring and Connections above.
  4. Typically 2-8 links per aggregation group

Best Practices:

  1. Label all ports in the aggregation group clearly
  2. Use consistent cable types and lengths
  3. Configure before connecting cables (see CLI Guide for configuration)

What It Is:

Connecting switches with multiple physical paths provides redundancy—if one path fails, traffic automatically uses an alternate path. Spanning Tree Protocol (STP) prevents loops while keeping backup paths ready.

Benefits:

  1. Network remains operational during single link failure
  2. Automatic failover (typically under 1 second with RSTP)
  3. No manual intervention required
  4. Improved reliability for mission-critical installations

When to Use:

  1. Mission-critical installations requiring maximum uptime
  2. Installations where brief interruptions are unacceptable
  3. Environments with unreliable infrastructure
  4. Control rooms, live production, healthcare applications

Hardware Requirements:

  1. Switches must support STP (all MXnet switches do)
  2. Multiple uplink ports available
  3. Separate physical cable paths (different conduits if possible)

Physical Implementation Best Practices:

  1. Run redundant cables through different physical paths when possible
  2. Use different fiber strands or separate fiber cables
  3. Test failover behavior before going live
Info
Important: Spanning tree configuration is required to prevent loops. Refer to the MXnet CLI Guide for proper STP configuration.
  1. PoE vs PoE+ vs PoE++ Switch: How to Choose?
  2. Third-party Switch Requirements and Settings for Running AVPro Edge MXNET AVoIP System
To view more How-To articles and to find additional MXnet-related guides visit the MXnet Knowledge Base.

Warranty

All MXnet products are covered under AVPro Edge's 10 year warranty.


For details visit the Warranty Page.



    • Related Articles

    • MXnet Endpoints User Manual

      Supported Products Evolution I Endpoints AC-MXNET-1G-E AC-MXNET-1G-D AC-MXNET-1G-AVDM-E AC-MXNET-1G-DANTE-E AC-MXNET-1G-EWP Evolution II Endpoints AC-MXNET-1G-EV2 AC-MXNET-1G-DV2 AC-MXNET-1G-AVDM-EV2 AC-MXNET-1G-DANTE-EV2 AC-MXNET-1G-DANTE-DV2 ...

    • How To: Configure QSFP+ ports of an MXnet 10G Network Switch to operate as 4 10G SFP+ ports (4x10G Breakout Mode)

      This article provides step-by-step instructions on how to configure one or multiple QSFP+ ports to operate as 4 10G SFP+ ports (to be utilized with a 4x10G breakout cable (The breakout cable SKUs are the following: AC-40G-BOC-01, AC-40G-BOC-02, ...

    • MXnet 1G API ~ V1.26.1

      Kevin Wang, Director of Product Management, goes through using the MXNET API to control and configure the MXNet CBOX Direct. Current API Version: V1.26.1 Control Box Version: 2.71 && V4.21 and above Instructions and API attached

    • Third-party Switch Requirements and Settings for Running AVPro Edge MXNET AVoIP System

      Third-party Switch Requirements and Settings for Running AVPro MXNET AVOIP System AVPro Support does not provide assistance with the configuration of third-party network switches. If a third-party switch is used with the MXNet product line, customers ...

    • How to: Enable Port Mirroring on an AVPro MXNet Switch

      What is Port Mirroring? Port mirroring, also known as port monitoring or network tapping, is a feature in network switches that allows the network administrator to copy and send network traffic from one port (or group of ports) to another port for ...