Configuring Netgear M4250/M4300 switch for Livewire+ AES67

Prev Next

Disclaimer - Read This First

This configuration guide is provided without warranty. Telos Alliance is not responsible for any issues that may be encountered. Telos Support is not the responsible party to provide additional support in configuration or troubleshooting.

Contact Netgear Support for questions regarding network topology, switch models, configuration, troubleshooting or software updates. Netgear provides excellent support to its customers.

If you have an existing AOIP network built on a different brand of switches do not attempt to add the Netgear M4250/M4300 into the environment.  

WARNING

Some customers have reported issues with IGMP on Netgear switches running newer firmware and utilizing the Livewire profile. Netgear is aware of these issues and working to resolve them. See below for details.

Programming

For the initial switch configuration please follow Netgear installation guide and user manual

Netgear M4250 docs HERE

Netgear M4300 docs HERE

Check/ update firmware

Before proceeding, check the Firmware Version shown on the Device Details section of the Overview page.

For the M4250,  please make sure you are running firmware version 13.0.5.16 or higher

For the M4300, please make sure you are running firmware version 12.0.19.12 or higher

Check the Netgear downloads center to obtain current firmware for your switch model/port count

Netgear M4250 firmware HERE

Netgear M4300 firmware HERE

Assign Livewire+ Network Profiles to Ports

WARNING! DO NOT USE LIVEWIRE+ PROFILE!

December 2025

An IGMP issue with Netgear AV Line switches was discovered when connecting any two Studio Core/Edge, QOR.16 or QOR.32 products to ports configured with the Livewire+ profile. Until the issue is resolved, do NOT use the “Telos Alliance/Livewire+ AES67” profile. This issue is currently known to be a problem in the following firmware versions:

M4250 Firmware Version 13.0.5.16 and 13.0.5.20

M4300 Firmware Version 12.0.19.12 and 12.0.19.15

All customers using Telos Alliance products should simply use the AES67 profile instead until the issue is resolved. Note: no changes need to be made to your Telos products. You are not required to use PTP clock with this profile. You can still run all Livewire+ devices using the Livewire clock if you prefer.

The original instructions are still below with a temporary correction. This page will be updated once a fix is released.

Using the “AV Login”.  Log in to the switch, and go to the Network Profiles page

Set the ports to use the “Telos Alliance/ Livewire+ AES67” “AES67”profile.   Please see the Netgear user manual for more details regarding these profiles and how to apply them to the switchports

If dealing with multiple switches, make sure this profile is applied across all ports on each switch

Save changes to the switch

IMPORTANT! Please click the Save button at the top of the page to save the configuration to memory. Otherwise all changes will be lost if the switch is rebooted or powered down

That's it! If you have additional edge switches please repeat the steps above

Confirming IGMP multicast operation (optional)

The AES67 profile automatically enables IGMP

Check that multicast groups table starts populating

On the left hand navigation select Multicast

The multicast group's table should start showing entries as more devices come online and start requesting Livewire or AES67 multicast streams.

Confirm that IGMP Querier Election is correct

If there are multiple Netgear switches installed we can confirm that the IGMP Querier is only running on one switch (core switch). We can confirm that the edge switches indicate IGMP Querier is coming from the core switch

On the left hand navigation click on Diagnostics and then select Terminal

You will be prompted to log in from the CLI, use the same credentials used for the web ui

On the core switch, or central switch type in the command "show igmpsnooping querier detail"

Reference the VLAN defined in previous steps (in the Network Profile VLAN column). VLAN 550 is what we are using in this example, and below we observe the "Operational State" shows "Querier"

(RED-CORE-RACK1)#show igmpsnooping querier detail

VLAN 550 :   IGMP Snooping querier status
----------------------------------------------
IGMP Snooping Querier VLAN Mode................ Enable
Querier Election Participate Mode.............. Enable
Querier VLAN Address........................... 0.0.0.0
Operational State.............................. Querier
Querier MAC Address............................ 94:a6:7e:79:15:72
Operational version............................ 2
Operational Max Resp Time...................... 120

(RED-CORE-RACK1)#

Repeat the same command but do this on any connected Edge switches

For the same VLAN, we observe the "Operational State" shows "Non-Querier"

Additionally "Last Querier Address" should equal the Management IP of the switch that is running the IGMP Querier

(RED-EDGE2-RACK1)#show igmpsnooping querier detail

VLAN 550 :   IGMP Snooping querier status
----------------------------------------------
IGMP Snooping Querier VLAN Mode................ Enable
Querier Election Participate Mode.............. Enable
Querier VLAN Address........................... 0.0.0.0
Operational State.............................. Non-Querier
Last Querier Address........................... 10.0.2.5
Querier MAC Address............................ 94:a6:7e:79:15:72
Operational version............................ 2
Operational Max Resp Time...................... 120

(RED-EDGE2-RACK1)#