Q-SYS Networking and Topologies (Part 4)
| Site: | QSC |
| Course: | Q-SYS Quantum Level 1 Training (Online) |
| Book: | Q-SYS Networking and Topologies (Part 4) |
| Printed by: | Guest user |
| Date: | Saturday, 23 November 2024, 6:22 PM |
Description
Video Transcript
00:07
Welcome back.
00:08
So, we’ve covered many different topologies using only Q-SYS equipment,
00:13
but we know in the practical world all sorts of things get integrated to Q-SYS.
00:17
In fact that openness is probably the exact reason you use it.
00:21
We’ll start with Dante integration, as it’s a common use case.
00:25
The most basic use case is a Q-SYS system using LAN A for Q-SYS peripherals and Q-LAN,
00:31
and a dedicated network for the CDN64, or Q-SYS Dante card.
00:36
As we discussed before, we use what’s called the differentiated services code point (DSCP)
00:42
to prioritize traffic in the switches.
00:45
Q-SYS adds a DSCP value to PTPv2 and Q-LAN packets.
00:50
Audinate-based devices such as the CDN64 do the same thing with PTPv1 and Dante.
00:56
These values are then associated with priorities in the infrastructure called QoS queues.
01:03
In this case, the Q-LAN switch would be configured according to Q-LAN guidelines.
01:08
Values 46, 34 and 26 would be prioritized in that order, as those are the DSCP values for PTPv2,
01:17
Q-LAN Audio and Q-LAN video respectively.
01:20
The Dante switch would be configured with the values recommended by Audinate.
01:25
They use 56 for PTPv1, 46 for audio packets and 8 as a ‘reserved’ value for some special functionality.
01:33
If we look at the Q-SYS design properties under the File menu in Q-SYS Designer,
01:38
we see that Q-SYS has QoS presets that can remap these DSCP values.
01:44
In this case, we’d use the default Q-LAN values. This leads us to the next use case.
01:50
We can converge Dante and Q-LAN on to the same network as shown in this diagram.
01:56
To make QoS setup simpler, we choose the ‘Audinate’ QoS preset in the design file,
02:02
which allows us to use the Audinate DSCP values in the switch setup.
02:07
Now of course this is very often the case when software-based dante is used in conjunction
02:12
with Q-SYS peripherals in a Core 110f system.
02:15
Software-based dante will ALWAYS use the Audinate DSCP values regardless of the QoS preset chosen.
02:22
We’re only remapping Q-LAN values to match.
02:26
If we’d like a separate network for Software-based dante, that is still possible.
02:31
The Q-SYS design properties dialog allows us to choose the network interface
02:36
used by Dante using the ‘interface’ parameter.
02:39
Remember, LAN A is ALWAYS the primary Q-LAN network. That is not selectable.
02:45
And for our final feat, consider this masterpiece: Redundant Q-LAN
02:50
and Dante networks on the same infrastructures.
02:53
In this case we’d use the Audinate QoS preset and assign the Software Dante interface to ‘Both’ as shown.
03:02
Another audio transport commonly integrated into Q-SYS is AES67,
03:08
which has been supported since Q-SYS Designer version 6.0.
03:12
Like software-based Dante, the interface used by the AES67 transport can be selected in software.
03:19
AES67 can be integrated with Q-LAN using LAN A as shown in the top diagram
03:25
or separated on to LAN B as shown at the bottom diagram.
03:29
Rather than being a global design setting like Software-based dante, the interface selection for AES67
03:35
transmitters and receivers is in the control dialog for the block itself.
03:39
There is an ‘auto’ selection, but best practice is to select the appropriate interface manually.
03:45
Remember AES67 makes use of multicast audio streams exclusively.
03:50
As many AES67 endpoints are also 100Mbps devices,
03:55
you’ll want to make sure to enable IGMP snooping and filtering to protect them from saturation.
04:01
A good rule of thumb is to enable IGMP features when you have more than 5 AES67 streams on the network.
04:08
Now there’s the matter of QoS and AES67 integration.
04:12
Let’s say I have an AES67 endpoint and Q-LAN on the same network.
04:18
How should I prioritize the traffic?
04:20
As we discussed before, we use what’s called the differentiated services code point (DSCP)
04:25
to prioritize traffic in the switches.
04:27
Q-SYS adds a DSCP value to PTPv2 and Q-LAN packets.
04:32
The switch is then configured to recognize those markings and make them a higher priority than others.
04:37
The AES67 standard suggests that PTPv2 and audio packets carry the same DSCP markings as Q-LAN.
04:44
Those are 46 and 34 respectively.
04:48
The good news then is if you’re integrating with an AES67 device that follows the standard,
04:53
you can follow the Q-SYS network setup guidelines and you’re done.
04:57
That’s not the most realistic case, however,
04:59
as most AES67 integrations are actually done using Audinate chipsets
05:05
that do and do not follow the AES67 standard under certain circumstances.
05:10
DSCP markings for each packet type in Audinate-based devices
05:14
depends on the product being used and the Dante firmware version.
05:19
Here’s how it works:
05:20
All Audinate Ultimo devices, which are typically small devices up to 4 audio channels
05:26
use the same DSCP values as Dante when placed in AES67 mode.
05:31
This includes most current Attero Tech by QSC wall plates.
05:35
Higher channel count Audinate devices based on the Brooklyn II or Broadway chipsets vary
05:41
depending on the firmware version of the device.
05:44
Devices running Dante firmware v4.1 and below carry Audinate DSCP values,
05:50
while those at v4.2 and above carry the AES67 standard values.
05:55
Another thing to remember is that AES67 makes use of PTPv2,
06:00
while Audinate devices must still participate in a PTPv1 domain even if in AES67 mode.
06:07
This makes configuring QoS a little trickier, so let’s first make sure we know how to get the information we need
06:13
to understand our particular use case.
06:17
To determine the Audinate firmware version running on a given device,
06:21
we use Dante controller software, which can be downloaded from the Audinate web site.
06:26
If we start up Dante controller and navigate to the ‘Device Info’ tab,
06:30
we see each device and the Dante version it’s running.
06:33
Keep in mind that the manufacturer’s firmware version often doesn’t match this version,
06:38
so you want to make sure you’re looking here.
06:40
In this case, we see a device running 4.1.3.5.
06:45
We know that it will use Audinate DSCP values when in AES67 mode.
06:51
This endpoint is running 4.2.0.28. Now we need to know what device type it is.
06:59
The device type can be found by double-clicking on the device in that view.
07:04
Navigate to the status tab, and the device type can be found here.
07:09
Again, if this is Broadway or Brooklyn II and the firmware version was 4.2 or higher,
07:14
then you know the DSCP values for AES67 mode will be as shown.
07:19
As they said at the end of every GI Joe cartoon, ‘Knowing is half the battle’.
07:25
Now that we know what devices we have and the DSCP values they’ll carry,
07:29
we have to decide how to set up the Q-SYS QoS Preset and the switch QoS queues.
07:35
There are three major cases we’ll have… so, let’s explore each one.
07:38
The first case is where we have Q-SYS, and all or some combination of Ultimo-based devices
07:45
or older firmware Brooklyn II and Broadway devices.
07:49
All those devices will carry the Audinate DSCP values.
07:53
Here we use the Audinate QoS Preset in Q-SYS designer,
07:57
and set up our switches with the Audinate queuing settings.
08:01
The next case is where we have Q-SYS integrated to all Brooklyn II or Broadway devices.
08:07
As you can see this is a little more complex. We have different DSCP markings for the two PTP standards.
08:13
The QoS setup in the infrastructure may depend on the abilities of the switch.
08:18
If the switch allows multiple DSCP values to be placed in the same QoS queue,
08:23
then we’d like PTPv1 and 2 to be the SAME priority.
08:28
The setup would be exactly as shown in the table.
08:31
If the switch does not allow multiple DSCP values to be placed in the same queue,
08:36
then of course each value would need to be placed into its own queue.
08:40
This of course requires one more queue, but that should be fine.
08:43
It doesn’t matter which of PTPv2 and v1 is placed in the highest queue as long as they’re
08:49
both prioritized above all other network traffic.
08:53
Since 56, 46 and 34 are all used in this case, the QoS preset for Q-SYS
09:00
shouldn’t be a problem in either the QLAN or Audinate setting.
09:03
We’d recommend QLAN so that all PTPv2 traffic carries the same markings.
09:09
We have the same concerns if we have a mix of Ultimo and Newer Firmware Brooklyn II or broadway devices.
09:17
We’d set things up exactly as the previous case.
09:20
Note these last two cases can be simplified if the interface to Q-SYS
09:25
can use the CDN64 or software-based Dante.
09:29
If you can have all the new firmware Brooklyn II and broadway devices use Dante,
09:33
then all the other devices will use Audinate values.
09:36
Use the Audinate QoS Preset in Q-SYS and you’re set.
09:40
This concludes our look at common topologies and use cases…now we’ll turn our attention to network troubleshooting.