Extreme Networks Deployment Guide

Deployment Guide for Extreme Networks AVB-Enabled Switches

The Professional AV world comprises live performance venues, concert halls, recording studios, stadiums, telepresence suites, building PA Systems, campuses, consumer systems, and wherever else high quality audio and video are mission critical. Though parallels exist, the requirements for Pro AV are not the same as those for VoIP and IP multicast. In Pro AV, the goal is to deliver high quality experiences that are as close to perfect as possible, which requires deterministic delay, high bandwidth, delivery without drops, and calculated synchronization to multiple endpoints for example, audio speakers measured in hundreds of microseconds.

Executive Summary
This document provides a brief overview of Audio Video Bridging (AVB) and how to congure and verify AVB capabilities on Extreme Networks AVB-enabled switches. AVB capabilities are available on select Extreme switches running ExtremeXOS 15.3 or later and require purchase of an AVB Feature pack. For more information please visit http://www.extremenetworks.com/solutions/avb.aspx.

2013 Extreme Networks, Inc. All rights reserved. Do not reproduce.

Extreme Networks Deployment Guide

AVB Advantages and Concepts

Audio Video Bridging (AVB) leverages IEEE standards to introduce Ethernet networking to the world of Professional Audio and Video. AVB replaces traditional analog AV networks and proprietary digital systems with standards-based Ethernet. The following are the IEEE 802.1 Audio Video Bridging (AVB) standards: IEEE 802.1BA: Audio Video Bridging (AVB) Systems IEEE 802.1AS: Timing and Synchronization for Time-Sensitive Applications IEEE 802.1Qak: Multiple Registration Protocol (MRP) & Multiple VLAN Registration Protocol (MVRP) IEEE 802.1Q (was 802.1Qav): Forwarding and Queuing for Time-Sensitive Streams (FQTSS) IEEE 802.1Q (was 802.1Qat): Stream Reservation Protocol (SRP) / Multiple Stream Reservation Protocol (MSRP). This technology ensures audio and video can leverage a predened amount of the bandwidth for AVB audio. This amount is 75% of the maximum data rate; the other 25% of bandwidth can be used for other data. (Note: These percentage allocations can be adjusted as required across all Extreme Networks AVB-enabled switches.) Two additional draft standards rely on IEEE 802.1 AVB to provide professional quality Audio Video. IEEE 1722 - Layer 2 Transport Protocol for TimeSensitive Streams, which allows easier porting of applications currently IEEE 1394 (FireWire) to AVB. IEEE 1733 - extends RTCP for RTP streaming over AVB-supported networks. To expand the inuence and role of AVB, the leaders of the Professional AV world formed the AVnu Alliance. The AVnu Alliance is responsible for: 1. Driving standardization 2. Provide education and training on AVB concepts and advantages 3. Promote AVB not just in the ProAV industry but also in the automotive, silicon manufacturing, and consumer electronic industries 4. Ensuring AVB interoperability through AVB plugfests and certication testing

The Professional Audio Video world has stringent requirements that require diligence during the AVB switch conguration process. This deployment guide will take you through all the key steps.

Anatomy of an AVB Network

An AVB network has three major componenets: Endpoints Controller AVB switches In an AVB network, an endpoint can be classied as a talker, a listener, or both. Endpoints act as the AVB gateways and perform the A/D, D/A conversion and formatting and other audio processing functions. Endpoints are connected to actual audio sources and sinks. In Figure 1, the sources are the Xbox, microphones, iPod and guitar. The sinks are speakers or recording devices. The controller discovers all the talkers and listeners, and displays them to the operator, which then decides what connections are to be made using the controller. Without the controller, the AVB network is just a collection of devices, neither transmitting nor receiving any streams. A stream is a single audio source that a talker creates and transmits across the AVB network. The destination of this stream is one or more listeners. Talkers can have multiple sources and generate multiple streams. Listeners can have multiple sinks. The operator not only has to decide which talker/listener to connect, but also which sources/streams on the talker will connected to a particular sink on the listener.

2 2013 Extreme Networks, Inc. All rights reserved.

Extreme Networks Deployment Guide

Figure 1 - Ethernet AVB Network

Connecting these elements is the AVB-enabled switch (in the graphic above, the Extreme Networks Summit X440.) The role of the switch is to provide support for the control protocols: gPTP - master clock determination, clock distribution, clock delay calculation MSRP - L2 multicast support, bandwidth reservation MVRP automatic VLAN creation and propagation Once the endpoints are connected to the AVB switch, auto-discovery and conguration begin. The endpoints are automatically added to the AVB network by the switch. In addition, a new VLAN with VLAN ID = 2 is created. This VLAN is used to carry all streams transmitted. Each endpoint must have an IP address so the controller can discover and control the endpoint.

Extreme Networks Switch Conguration Details

Extreme Networks provides an easy setup process. From the CLI, simply type: enable AVB enable AVB ports all (or you can use a ports list) NOTE: No port restrictions. All ports can be AVB enabled. The commands above enable gPTP, MSRP and MVRP. These protocols are necessary for auto-conguration of the AVB network. In addition, two new priority queues are created in the switch. Since existing switch congurations may conict with the AVB conguration, it is recommended to use switches which do not have a saved conguration booted. Clearing the switch conguration is recommended. All AVB-enabled ports must be part of the default VLAN. Where multiple switches form the AVB network, this rule still stands. Spanning Tree is compatible with AVB and should be used in complex networks. NOTE: The default VLAN will be untagged across all ports. If untagged VLANs are not allowed across a trunk

3 2013 Extreme Networks, Inc. All rights reserved.

Extreme Networks Deployment Guide

connecting two Extreme Network switches, then tag the default VLAN. NOTE: Most endpoints have two interfaces that are connected to the AVB network: the control interface and the AVB interface that carries payload. Where only one interface is connected to the AVB network, the endpoint may be locally connected to a LabX switch. Be aware of potential loops caused by endpoint operators. As AVB endpoints are connected to the AVB-enabled ports, they must rst support gPTP. If the endpoint does not support gPTP, it will not be allowed in the AVB network. The AVB aware switch is capable of determining which ports should be allowed to participate in the AVB network automatically. Thus, non-AVB devices connected to an AVB port will not be allowed to join the AVB network. Take care in creating VLANs on the switch since MVRP will propagate these VLANs to other switches and endpoints. Avoid problems by setting the transmit ag to OFF for the vlam. The following command will not advertise the VLAN with VID 50 across port 1-19: cong mvrp tag 50 port 1-19 transmit off To check the operation of an AVB network, a few commands will provide you a good idea of what is going on. show avb shows if the device connected to the port is AVB capable. The command will show all ports enabled for AVB support.

* X460-24p.3 # sh avb gPTP status : Enabled gPTP enabled ports : *1d *2d 6d *7m 11d 12d *16m 17d 21d *22m MSRP status MSRP enabled ports : Enabled : *1 *2 6 *7ab 11 12 *16ab 17 21 *22ab : Enabled : *1 *2 6 *7 11 12 *16 17 21 *22

*3d 8d *13m 18d *23d *3 8 *13 18 *23 *3 8 *13 18 *23

4d 9d *14m 19d *24s 4 9 *14ab 19 *24ab 4 9 *14 19 *24

5d 10d *15d 20d

5 10 *15 20

MVRP status MVRP enabled ports

5 10 *15 20

To be AVB-capable, the port must be enabled in all three sections and must pass the next two requirements. First, in the gPTP section d m and s indicate whether the port is disabled, master or slave, respectively. The port must have an m or s state.

4 2013 Extreme Networks, Inc. All rights reserved.

Extreme Networks Deployment Guide

Secondly, the port must have an MSRP state of a, b, or ab. If these requirements are not met, then the port will not be added to the AVB neighborhood. Some of the talkers will have many streams available and it becomes difficult to determine talker and stream information. The best approach is to focus on a particular stream. The command shown in the text box below will give you stream id (MAC + identier string) and the associated multicast MAC address. Without the port # in the command, you can get a long list of stream IDs that may be more confusing than helpful.

(Private) X440-Prf.2 # sh msrp stream port 6 Stream Id Destination Port Dec Vid Cls/Rn ----------------------- ----------------- ---- ---- ---- -----a0:36:9f:0c:77:38:00:00 91:e0:f0:00:66:f1 6 Fail 2 A/1 Failure Code : (16) First val chg 4 stream id Total Streams: 1

BW --------7.488 Mb

------------------------------------------------------------------------------BW : Bandwidth, Cls : Traffic Class, Dec : Prop. Declaration Types, Rn : Rank MSRP Declaration Types: Adv : Talker Advertise, Fail : Talker Fail, Ready : Listener Ready AskFail RdyFail : Listener Asking Failed, : Listener Ready Failed,

(Private) X440-Prf.3 # sh msrp stre port 6 Stream Id Destination ----------------------- ----------------a0:36:9f:0c:77:38:00:00 91:e0:f0:00:f4:c4 Total Streams: 1

Port ---6

Dec ---Adv

Vid ---2

Cls/Rn -----A/1

BW --------7.488 Mb

------------------------------------------------------------------------------BW : Bandwidth, Cls : Traffic Class, Dec : Prop. Declaration Types, Rn : Rank MSRP Declaration Types: Adv : Talker Advertise, Fail : Talker Fail, Ready : Listener Ready (Private) X440-Prf.3 # AskFail RdyFail : Listener Asking Failed, : Listener Ready Failed,

In the example above, the rst execution of the command showed that the stream declaration failed.

5 2013 Extreme Networks, Inc. All rights reserved.

Extreme Networks Deployment Guide

In the second execution, the declaration is successful and it is a talker advertise declaration. The reason the stream had this failure is due to a change in the properties of the stream; in this case, it was the multicast MAC address that changed. Once the multicast MAC address is restored, the declaration is now successful. The output of the command shows the BW reserved for this audio stream: 7.488 Mbps. This can be veried indirectly by showing port utilization. The next box shows a simple show fdb command
(Engineering) X440-48p-10G.3 # sh fdb Mac Vlan Age Flags Port / Virtual Port List -----------------------------------------------------------------------------00:04:96:51:d3:d1 Default(0001) 0008 d m 24 00:0a:35:69:4b:06 SYS_VLAN_0002(0002) 0004 d m 15 00:0a:35:69:4b:06 Default(0001) 0012 d m 15 00:1d:c1:06:3d:64 Default(0001) 0006 d m 24 00:1d:c1:06:49:38 Default(0001) 0005 d m 24 00:1d:c1:06:50:8e Default(0001) 0007 d m 24 00:21:70:e1:55:52 Default(0001) 0003 d m 24 00:26:b9:e0:7c:5b Default(0001) 0006 d m 24 00:26:b9:eb:69:21 Default(0001) 0031 d m 24 00:50:43:00:00:42 Default(0001) 0005 d m 24 00:50:43:00:00:43 Default(0001) 0006 d m 24 00:50:56:9c:3d:15 Default(0001) 0063 d m 24 00:50:c2:4e:db:0e Default(0001) 0031 d m 24 00:60:e0:01:7b:74 Default(0001) 0049 d m 24 00:90:5e:12:fc:1f Default(0001) 0002 d m 12 00:a0:7e:11:03:2a SYS_VLAN_0002(0002) 0006 d m 24 00:a0:7e:11:03:2a Default(0001) 0007 d m 24 08:00:3e:26:0a:03 SYS_VLAN_0002(0002) 0135 d m 24 08:00:3e:26:0a:03 Default(0001) 0101 d m 24 0e:0e:0e:0e:00:21 Default(0001) 0008 d m 24 10:1f:74:ea:99:fd Default(0001) 0007 d m 24 91:e0:f0:00:53:00 SYS_VLAN_0002(0002) 0000 sr 24 <<<<< see note 91:e0:f0:00:fc:80 SYS_VLAN_0002(0002) 0000 sr 12, 15 <<<<< see note a0:36:9f:0c:77:38 Default(0001) 0009 d m 24 b8:ac:6f:8f:50:37 Default(0001) 0004 d m 24 b8:ac:6f:8f:50:39 Default(0001) 0044 d m 24 d4:9a:20:db:ef:d8 Default(0001) 0005 d m 24 Flags : d - Dynamic, s - Static, p - Permanent, n - NetLogin, m - MAC, i - IP, x - IPX, l - lockdown MAC, L - lockdown-timeout MAC, M- Mirror, B - Egress Blackhole, b - Ingress Blackhole, v - MAC-Based VLAN, P - Private VLAN, T - VLAN translation, D - drop packet, h - Hardware Aging, o - IEEE 802.1ah Backbone MAC, S - Software Controlled Deletion, r - MSRP Total: 27 Static: 2 Perm: 0 Dyn: 25 FDB Aging time: 300 (Engineering) X440-48p-10G.4 # Dropped: 0 Locked: 0 Locked with Timeout: 0

NOTE: for AVB the important entries are the multicast entries denoted with ags sr. These are AVB controller created multicast streams. The multicast entries are showing the egress ports.

6 2013 Extreme Networks, Inc. All rights reserved.

Extreme Networks Deployment Guide

Other Considerations
MSRP Considerations 1. All ports need to belong to VLAN Default. 2. All ports connected directly to an AVB end point need to be an untagged member of VLAN Default because IEEE 1722 and IEEE 1722.1 control packets are transmitted as untagged frames. It is acceptable for VLAN Default to be tagged on trunk ports connecting switches. 3. Disable Rx/Tx pause. MVRP Considerations 1. All MVRP enabled ports must be part of Default VLAN, before enabling AVB on the switch. 2. Check if the transmit ag is turned on for any of the VLAN tags. (Default is ON.) At the two edges, create VLAN at both the ends and assign tag to it, before adding ports statically to check for VLAN propagation. 3. Support for 4094 (1-4094) VLANs is there. Additional Important Details 1. AVB is enabled on Extreme Networks switches with purchase of an AVB feature pack. 2. AVB capabilities are available on select Extreme switches running ExtremeXOS 15.3 or later and require the addition of an AVB Feature pack. For more information please visit http://www. extremenetworks.com/solutions/avb.aspx. 3. Do not modify anything on QoS Proles being used by AVB. In particular, do not change any of the following: max or min bandwidth settings. 4. Do not add port rate limiter on AVB ports. 5. Be very careful about ACLs. ACLs are used to allow AVB frames with valid reservations onto AVB queues, and to prevent other frames from getting onto these AVB queues. It may be possible to add an ACL that defeats the existing AVB ACLs. 6. Do not change dot1p mapping to map traffic to the AVB QoS Proles. 7. All ports running AVB must be members of VLAN

Default w/Tag = 1. a. All ports connected to an endpoint must be untagged in VLAN Default. b. Default VLAN must be added to the default stpd for all ports (autobind). 8. Rx and Tx pause must be disabled on AVB ports per IEEE 802.1Q-2011. While not strictly allowed by IEEE 802.1Q-2011, AVB will still work if prioritybased ow control (PFC) is used on non-AVB queues. 9. VID translation not supported. Other vendor-specic items 1. For Marvell UMAN, cong mrp port <port#> timers leave-all 20000 leave-all is sent out every 10-15 seconds (20 seconds using above command); the endpoint must respond within 600ms otherwise port is pruned. The 600ms is adjustable to 3 seconds. 2. For the Yamaha mixer 64in/out, increasing the gPTP delay threshold may help with whether port is gPTP capable cong network-clock gPTP port <port #> peer-delay neighbor-thresh 40 microseconds

Corporate and North America Phone +1 408 579 2800

Europe, Middle East, Africa and South America Phone +31 30 800 5100

Asia Pacic Phone +65 6586 9200

Japan Phone +81 3 5842 4011

www.extremenetworks.com 2013 Extreme Networks, Inc. All rights reserved. Extreme Networks, the Extreme Networks Logo, Summit are either registered trademarks or trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other trademarks are the trademarks of their respective owners. Specications are subject to change without notice. 1895_01 02/13