GigaCore recommended settings for a grandMA3 MA-Net3 setup

GigaCore recommended settings for a grandMA3 MA-Net3 setup

Intro

When setting up a grandMA3 Session, multicast protocols are used, either MA-Net3 for the connection between grandMA3 consoles, grandMA3 processing units ( PU's) and grandMA3 Nodes, or streaming ACN as output from the console or into the console.

When using only Art-Net with a console in combination with Art-Net DMX nodes or fixtures, the following info does not apply, as this is just unicast or broadcast network traffic.

Why IGMP matters.

As both MA-Net3 and sACN are multicast protocols, it is important to setup  IGMP correctly on your network, especially on larger setups, where multiple console locations and a distributed PU or Node network is used. 
This prevents unnecessary network traffic being broadcasted over the network.
Failure to setup IGMP correctly on the network can lead to MA devices not being able to join sessions or sACN devices not receiving data.

A general recommendation that can be used is:
  1. Configure all the links between switches as ISL (trunk)
  2. Use seperate groups for MA-Net3, sACN and Art-Net
  3. Set a central switch as your IGMP querier  for all these groups (either at FOH with the consoles or in the control room or dimmer world with the grandMA3 processing units)
  4. when using redundant links, set the same central switch that is being used as IGMP querier as the root bridge.
  5. Enable "IGMP snooping" on the groups. (this is enabled by default on GigaCores)
  6. Disable "unknown flooding" on these groups (this is set as disabled by default on GigaCores)
  7. RlinkX can be used on ports for edge devices like grandMA3 consoles, processing units and nodes. (this is enabled by default on all ports of a Gigacore)
  8. RlinkX should be disabled on ports connecting to third party network equipment or on ports connecting to network equipment that might be connected / disconnected or powered of or on during the show. 

For small setups, with 1 or 2 switches and using only MA-Net3 or sACN changing these settings will even not be needed as the settings are setup by default on Gigacores, as we will see in the next examples. All DMX-nodes in these examples can also be sACN enabled lighting fixtures, media servers...

For larger setups, the location of the IGMP querier and Root bridge should be determined per specific case.

MA Lighting recommends that, if practically possible, all calculationg session members (category A members) like grandMA3 consoles and processing units should be connected to the same  switch or switches at one location (most of the time this will be FOH). This is also the location where the IGMP querier and root bridge should be placed.

Example 1  : 1 Console, 1 Switch and 1 or more DMX -Nodes

  1. Nothing to configure

Example 2  : 1 Console, 1 Switch and 1 or more grandMA3 devices

  1. Nothing to configure

Example 3  : 1 Console, 2 Switches and 1 or more DMX -Nodes

  1. set up ISL between switches (This is preferred but not necessary)


Example 4  : 1 Console, 2 Switches and 1 or more grandMA3 device

  1. set up ISL between switches (This is preferred but not necessary)

Example 5 : 1 Console, multiple switches and a mix of grandMA3 devices and DMX-nodes

  1. set up ISL between switches 
  2. Configure groups for MA-Net and sACN
  3. Set the switch closest to the console as IGMP Querier

Example 6 : 1  Console, multiple switches in a redundant loop and a mix of grandMA3 devices and DMX-nodes

  1. set up ISL between switches 
  2. Configure groups for MA-net and sACN
  3. Set the switch closest to the console as IGMP Querier and Root Bridge

Example 7 : Multiple Consoles on different locations, multiple switches in a redundant loop and a mix of grandMA3 devices and DMX-nodes

  1. set up ISL between switches 
  2. Configure groups for MA-Net and sACN
  3. Set the most central switch as IGMP Querier and Root Bridge


    • Related Articles

    • IP Multicast and IGMP

      Introduction IP Multicast is a method of sending IP packets to a group of interested Receivers in a single transmission. It uses specially reserved Multicast Address blocks (Class D: 224.0.0.0 – 239.255.225.255). It is often employed for streaming ...

    • GigaCore API documentation

      In the attached document you can find all the web API commands available for the second generation GigaCore. The API is also available on the device itself by browsing to http://{YOUR_DEVICE_IP}/api/doc This API works for the following devices: ...

    • GigaCore Bitfocus Companion Streamdeck module

      Introduction Luminex products have an open HTTP API. This API can be used to integrate with other software applications. The GigaCore API is documented here (generation 2) and here (generation 1). One such application is Bitfocus Companion, a ...

    • Gigacore Switches and Avid S6L

      As most of you probably know by now, Gigacore switches can be used to connect the different units in an Avid S6L system. The procedure to configure Gigacore switches is described by Avid in this document : ...

    • Linux Reverse Path Filtering and Multicast Packet Drops on Edge Devices

      Introduction Linux kernel's reverse path filtering (RPF) is a security feature designed to help prevent IP address spoofing. While effective for security, this feature can cause unintended side effects, such as dropping legitimate multicast packets. ...