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

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

Third-party switches need to support the features or functionality below and enable/disable some settings to support the MXNET AV-over-IP system.

1.       IGMP Settings

2.       MTU Settings

3.       POE budget

4.       Disable EEE

 

1.      IGMP Settings

1.1.   IGMP Version 2

The AVPro MXNET AV-over-IP Ecosystem is based on the IGMP version 2. So, please make sure your switch is (capable of) running on IGMP Version 2.

1.2.   IGMP V2 Snooping

IGMP snooping is a method that network switches use to identify multicast groups; Deciding which groups of decoders receive the same network traffic, like video, audio, and control streams. IGMP Snooping enables switches to forward IP packets to the correct devices (such as decoder) in their network.

For example - Cisco CLI command to enable IGMP Snooping: Device(config)# ip igmp snooping vlan vlan-id

1.3.   IGMP V2 Querier

The responsibility of the IGMP Querier is to send out IGMP group membership queries on a timed interval, and to retrieve IGMP membership reports from active members, and allowing updating of the IGMP group membership tables.

For example - Cisco CLI command to enable IGMP Querier: Device(config)# ip igmp snooping querier

1.4.   IGMP V2 Immediate Leave

When enabling IGMP Immediate Leave, the device immediately removes a port when it detects the IGMP Version 2 leave message on that port. You should use the Immediate-Leave feature on every port in the VLAN.

Immediate Leave is supported only on IGMP Version 2 hosts.

For example  Cisco CLI command to enable IGMP Immediate Leave:  Device(config)# ip igmp snooping vlan vlan-id immediate-leave

1.5.   Unknown Multicast Dropping or Unregistered Multicast Flooding

Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table. This feature enables the device to forward unknown multicast data to the router port only. If the device does not have a router port, unknown multicast data will then be dropped.

If you do not enable Unknown Multicast Dropping or Unregistered Multicast Flooding, the unknown multicast data will flood the VLAN to which the data belongs.

1.6.   Example: IGMP Settings of Cisco Catalyst Switches

Switch> enable

Switch# configure terminal

Switch (config)# vlan 1

Switch (config-vlan) # name default vlan

Switch (config-vlan) # ip address 192.168.1.1 255.255.255.0

Switch (config-vlan) # end

Switch (config)# ip igmp snooping

Switch (config)# ip igmp snooping querier 192.168.1.1

Switch (config)# ip igmp snooping querier version 2

Switch (config)# ip igmp snooping vlan 1 immediate-leave

Switch (config-vlan) # exit

Switch#  copy running-config startup-config

2.      MTU Settings

The MTU size needs to be changed to over 9000 bytes to support the AVPro MXNET AV-over-IP system.

The MTU is the maximum payload length for a particular transmission media. For example, the MTU for Ethernet is typically 1500 bytes. 

A jumbo frame is an Ethernet frame with a payload greater than the standard maximum transmission unit (MTU) of 1,500 bytes. Jumbo frames are used on local area networks that support at least 1 Gbps and can be as large as 9,000 bytes or even bigger. Because jumbo frames are not defined in the IEEE 802.3 specifications for Ethernet, vendor support for jumbo frames and their maximum transmission units may vary.

Jumbo frames provide a number of benefits over the traditional - IEEE 802.3 - ethernet MTUs. These include:

·         The amount of frames sent across the network is reduced.

·         The number of ethernet headers are reduced as a result of fewer frames.

·         The reduction in frames results in few headers being required.

·         CPU cycles are reduced at the sender and receiver side due to few headers needing to be built and read.

·         Network bandwidth is reduced due to the reduction in headers.

For example, the Cisco CLI command to change MTU size to 9000: Device(config)# system mtu jumbo 9000

 

3.      POE Budget

POE switches will power the MXNET endpoints; each MXNET endpoint (encoder or decoder) consumes 6-9 watts. Therefore, we need to identify the POE budget before purchasing. For example, a 24-port 370-watt PoE switch can supply up to 15.4 W of power per port on all 24 ports, meaning you can connect 24 MXNET endpoints on the 24-port switch. Likewise, a 48-port 740-watt Gigabit PoE switch can power up to 48 MXNET endpoints.

4.      Disable EEE

Energy Efficient Ethernet (EEE) is an IEEE 802.3az standard that is designed to reduce power consumption in Ethernet networks during idle periods.

If the switch supports EEE, please make sure you disable the EEE function because as it may cause issues in some cases.

For example - Cisco CLI command to disable EEE: Device(config)# system mtu jumbo 9000

 

 

 

 



    • Related Articles

    • MXNet Ecosystem Training

      Dolby Vision Support, Dolby Atmos Downmixing Support, Quick Switching, endless sources routed to endless displays; Welcome to MXNet. Join Tom and John from AVPro as they give integrators an introduction to the AV over IP/Networked AV system called ...
    • MXNet: AV over IP Complete System Set-Up! (With TIMER!)

      John Tumbleson (The Mind Behind MXNet Mentor) and Tom Devine (Noob) put together an entire AV over IP system using MXNet Encoders, Decoders and an MXNet Network Switch racing against the clock to complete the system as fast as they can!  The goal of ...
    • How To: MXNET System Design Summary

      This video is brought to you by Kevin Wang, Director of Product Management. MXNet is the AV over IP  video distribution ecosystem from AVPro Edge. With the MXNet Ecosystem,  integrators finally have an end-to-end solution developed with them in mind. ...
    • How To: Using the MXNET API ~ V1.12

      Kevin Wang, Director of Product Management, goes through using the MXNET API to control and configure the MXNet CBOX Direct. Current API Version: V1.12 Control Box Version: 1.70 and above Presentation and API Attached
    • AVPro Edge: Path of the Product

      AVPro Edge takes a different approach to our product's path. From development to installing and everything in between, this video goes gives you the inside look at the AVPro Edge method.