For a general overview on AVB / Milan, have a look at this article.
It is possible to enable AVB in multiple groups on a GigaCore. This allows the use of different AVB 'flavours' in the same network, for example a Milan network and an
network, but keep them in separate groups. When using AVB in multiple groups, there are a couple of attention points:
The discovery and management traffic (Mostly ATDECC / AVDECC) is VLAN tagged and therefore stays within its group. This makes the separation into multiple groups possible.
All groups will use the same gPTP grandmaster. For this reason, it is recommended to ensure that a GigaCore acts as the gPTP grandmaster when using multiple AVB groups and not an AVB end device.
The general AVB limits apply to the combination of all groups with AVB enabled:
Up to 75% of bandwidth can be used for AVB traffic on an AVB link, distributed across all groups with AVB enabled.
Up to 150 streams can be active in the network at once, distributed across all groups with AVB enabled.
AVB streams will not necessary follow the same links as the Group VLAN-tagged traffic. AVB streams flow use VLAN 2 due to the nature of MSRP and therefore don't follow the 'normal' VLAN tagged ports. It is recommended to use ISL or trunk connections between GigaCore's. In that case the AVB traffic will follow the active RSTP connections.
Redundancy
For optimal, seamless redundancy in AVB networks, it is generally recommended to have 2 separate networks. One network for all primary connections and one network for all secondary connections.
Using multiple groups with AVB enabled in 1 GigaCore network will only in a few cases result in good redundancy. For example when the primary connection to an end devices is lost, it is expected that the end device seamlessly switches to the secondary connection. A disconnection of the ISL or trunk between GigaCores in a ring topology, will not result in seamless redundancy, it can take up to 10-15 seconds for audio to be restored.
Have a look at the following video for more information on AVB redundancy.
GigaCore switches support AVB / Milan. In the current firmware versions (as of writing: GigaCore v1.4.1 of gen2 and GigaCore v3.1.0 for gen1), AVB is enabled by default on all ports. Enabling AVB on GigaCore To enable AVB on second generation ...
As many of you already know, the MILAN standard uses a specific AVB stream format in order to facilitate interoperability. Here is a link to a document from MILAN lisiting the specifications of that stream format. ...
No additional service charges or licenses are required to enable the AVB feature-set. This article applies to all GigaCore Gen2 switches. References This article outlines how to use the web interface on the second generation GigaCore switches to ...
Luminex GigaCore switches are Avnu Certified with firmware version 2.8.0 and later. All GigaCore switches, including legacy devices already installed in the field, will be capable of receiving this firmware update. No additional service charges or ...
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 Gen2 GigaCore switches. All ...