©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL #AvayaATF Scalable & Simple Multicast Solutions… Interested? Edwin C. Koehler Director – Distinguished CSE

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL So what’s wrong with today’s multicast networks? Today’s multicast networks are built on a protocol overlay model Typically PIM on top of OSPF RIP or static routes can be used Protocol Independent Multicast (PIM) builds its service distribution tree by referencing the unicast routing table Reverse Path Forwarding This protocol overlay model works over a stateless flood and learn Ethernet switching environment The protocol overlay creates a ‘pseudo-state’ for the multicast service This approach leads to strong dependencies on timers and creates an environment where any network topology changes create a disruption of the service. 3

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL A B C D MAC FIB MAC B = port 2 MAC A = port 1 MAC D = port Frame received MAC ‘A’ to MAC ‘B’ Port 1 Port 2 Port 3 Port 4 IEEE 802.1d Flood & Learn Forwarding Known MAC 4

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL A B C D MAC FIB MAC B = port 2 MAC A = port 1 MAC D = port 3 MAC C = port ? 1) Frame received MAC ‘A’ to MAC ‘C’ 2). MAC ‘C’ unknown = flood 3).MAC ‘C’ responds 4). FIB Table updates MAC ‘C’ to port 4 Port 1 Port 2 Port 3 Port 4 IEEE 802.1d Flood & Learn Forwarding Unknown MACs 5

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL A B C D R VLAN 100VLAN 200 VLAN 300 MAC FIB MAC B = port 2 MAC A = port 1 MAC D = port 3 MAC C = port ? MAC FIB MAC B = port 3 MAC A = port 5 MAC D = port 2 MAC C = port ? MAC FIB MAC B = port 2 MAC A = port 1 MAC D = port 2 MAC C = port ? 1.MAC ‘A’ sends a frame to MAC ‘C’. 2.MAC ‘C’ is unknown to Switch 1 3.Due to the fact that MAC ‘C’ is on a traversal VLAN, all switches that are members of the VLAN need to flood for MAC ‘C’. 4.MAC ‘C’ responds but must communicate to MAC’A’ via the router function which is running in switch 2. Flood for MAC ‘C’ Switch 1Switch 2 Switch 3 IEEE 802.1d Flood & Learn Forwarding Unknown MAC Flooding across a Virtualized Core 6

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL OSPF Unicast Overlay PIM Multicast Overlay Ethernet Switching Infrastructure (Stateless) R R R RP DR L2 IGMP Snooping IGMP Snooping Source Receiver Source Register Source begins to send media IGMP Join IGMP Join RPT Join RPT Prune SPT Join media 1 st Media Delivery Path (2 nd )Shortest Media Delivery Path Complex & Touchy!!!! Legacy IP Multicast Protocol Overlay Model 7

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Aspirational functionality But it requires: BGP LDP RSVP-TE Draft-Rosen VPLS Avaya Fabric Connect IEEE SPB Avaya Extensions Baseline redundancy Root Bridge – dependent Not shortest path Which Fabric Technology is the Answer? That all depends on how you qualify the question… 8 STP IETF TRILL Cisco FabricPath Brocade VCS Juniper QFabric IETF MPLS L2 Loop-free Topology L2 Multi-Pathing L2 Single-Site Virtualization L2 Multi-Site Virtualization L3 Unicast Virtualization L3 Multicast Virtualization Application Extensions Root Bridge – dependent Large flooding domain VLAN-based virtualization Single logical Switch / fault domain 100m distance limitation VLAN-based virtualization Abstraction Service-based virtualization Orchestration-ready Layer 3 awareness Unicast & Multicast support Application-driven extensibility

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Native Multicast over Shortest Path Bridging IEEE 802.1aq “Shortest Path Bridging” provides a dramatic evolution to the Ethernet Forwarding Control Plane (where SPBM stands for SPB MAC-in-MAC) Stateful Topology Use of IS-IS L2PDU and extended Type, Lengthm, Value fields Universal Forwarding Label IEEE 802.1ah “MAC-in-MAC” encapsulation (B-MAC) Provisioned Service Paths Individual Service Identifiers (I-SID) These three component technologies at a high level comprise the major evolution offered by SPBM. The end result is a very stateful and deterministic forwarding plane for Next Generation Ethernet 9

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Dyjkstra SPT from the perspective of SPB node IS-IS L2 Hello’s TLV’s 1.Topology 2.IP Reachability 3.Provisioned Services SPB Node * SPB Node SPB Node SPB Node SPB Node SPB Node * IEEE SPB ‘Nick Name’ Creating a Link State Topology using IS-IS 10

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL SPB Node SPB Node SPB Node SPB Node SPB Node SPB Node Dyjkstra from the perspective of… Normal Frame B-MAC Frame SPB Demarcation Point ah Frame C-MAC Frame Normal Ethernet Switch All frame forwarding in the SPB Domain occurs by the DA/SA information in the B-MAC (C-MAC info is transferred but NOT propagated in the SPB Core!) SADA C-MAC Frame DASA Normal Ethernet Switch DASA C-MAC Frame The Use of IEEE 802.1ah (MAC-in-MAC) with ISIS 11

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL C-SA = Customer Source MAC C-DA = Customer Destination MAC C-TAG= Customer TAG TPID= Tag Protocol IDentifier S-TAG = Service TAG I-TAG = Service Instance TAG I-SID = Service ID B-TAG = Backbone TAG B-DA = Backbone DA B-SA = Backbone SA Increase in Virtualization 16,777,215 Service instances! 4096x4096 Service instances 4096 Service instances IEEE 802.1aq “Shortest Path Bridging” and it’s use of 802.1ah MAC-in-MAC “Provider Based Bridging” 12

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Flexible Network Services 13 Mapping of a Layer 2 VLAN into a Virtual Service Network delivering seamless Layer 2 extensions Layer 2 Virtual Service Network Mapping of a Layer 3 VRF into a Virtual Service Network delivering seamless Layer 3 extensions Layer 3 Virtual Service Network Native IP routing across the Virtual Service Fabric without the need for Virtual Service Networks or any additional IGP IP Shortcuts Enhancing 802.1aq by offering a policy-based Layer 3 internetworking capability of multiple Virtual Service Networks Inter-VSN Routing

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Dyjkstra SPT for I-SID 1000 from the perspective of SPB node IS-IS L2 Hello’s TLV’s SPB Node SPB Node SPB Node SPB Node SPB Node SPB Node VLAN Topology 2.IP Reachability 3.Provisioned Services IP IP /24 NICK-NAME & “3” I-SID in Hexadecimal Example : Nickname = , I-SID = 1000 (0x3e8) Source & RPF are known! BMAC Dest. Multicast Address = 03:00:01:00:03:e8 ARP Here I am! Constrained Multicast in SPB Used to Service “Flood & Learn” 14

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL SPB Node SPB Node SPB Node SPB Node SPB Node SPB Node VLAN 1000 IP IP /24 Sending video to We are both interested in IP VLAN /24 IP I also am interested in Dynamic I-SID 16,220,100 Set up to establish multicast service via IS-IS LSDB IGMP Snooping IGMP Snooping IGMP Snooping IGMP Snooping I-SID 1000 Information on I-SID 16,220,100 Relayed to every SPB node via IS-IS TLV’s Crossing L3 Boundaries without multicast routed interfaces! True L3 Multicast Delivered ‘Natively’ over IEEE 802.1aq 15

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL SPB Node SPB Node SPB Node SPB Node SPB Node SPB Node VLAN 400 VLAN 300 VLAN 200 IP IP / / /24 Sending video to We are both interested in IP VLAN /24 IP I also am interested in IGMP Snooping IGMP Snooping IGMP Snooping IGMP Snooping VRF Dynamic I-SID 16,500,000 Set up to establish multicast service via IS-IS LSDB I-SID 5100 Information on I-SID 16,500,000 Relayed to every SPB node via IS-IS TLV’s True L3 Multicast Delivered Inside an IP VPN Service!! 16 VRF

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Why SPB with Multicast? Complexity With today‘s legacy protocols (PIM) it is very complicated to build and operate an IP Multicast routed network Scalability PIM networks don‘t scale to the levels the new apps are requiring it to. Convergence Multicast convergence in case of failure in a PIM network is in the 10s of seconds or even minutes and not sub-second as L2 network protocols “Multi-tenancy” For multi-tenant applications new scalable IP-MC model was required Dependancy on Unicast Routing Table This model does not optimal for convergence and design reasons. 17

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Applications Well known Applications Surveillance TV, Video Distribution PC Image Distribution Ticker Distribution (Trading) Image Distribution New Applications Data Center IP overlay models such as VXLAN, NVGRE,... 18

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Deployment Scenario Video Surveillance (IP Camera Deployment - Transportation, Airports, Government...) 19 SPB VLAN L3VSN or GRT Shortcuts Senders IGMP SMLT BEBs in the Data Center Receivers are only here Routing Instance! VLAN Senders Video on demand Receiver Screens (IP Multicast from cameras) Video Recorders (IP unicast from cameras) Many to Few Be sure to stop and see Pelco’s Endura Multicast Video Surveillance Solutions running onAvaya’s Fabric Connect Native Multicast!

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL SPB VLAN L3VSN or GRT Shortcuts Receivers Sender VLAN Maybe some Receivers Many of these BEBs (BEBs might be doing SMLT) Only Receivers behind them SMLT BEBs in the Data Center Routing Instance! Few to Many 20 TV-, Video-, Ticker-, Image Distribution

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL SPB VLAN Receivers Senders Receivers Sender Receiver SPB VLAN L2VSN IGMP L2VSN IGMP Querier recognition and drawing all streams towards querier (wildcard querier join) TOR Multicast in Data Centers

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL VLAN Multi-Tenant IP Multicast Usage to Support VXLAN 22 SPB L3VSN Green DC Red DC Yellow DC IP Multicast Green only Green and Red and Yellow users cannot communicate Each has a totally separate multicast environment Multi-tenant Data Center Routing Instance! VLAN IP Multicast Red only L3VSN IP Multicast Yellow only Multicast Shortest Path Distribution Trees

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Multi-Tenant IP Multicast SPB VLAN L3VSN Receivers IP Unicast Server Green users only Green and Red users cannot communicate But they both need to receive Multicast stream from Shared Server Multi-tenant Data Center Routing Instance! VLAN IP Unicast Server Red users only L3VSN 23

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL What Were the Requirements to Build SPB with IP Multicast Support? Simplicity Configuring – Infrastructure Provisioning – New services Operations Stream monitoring – end to end transparency Flexibility No topology Dependency, Support Rings, Meshes... Scalability Scale to the 10‘s of thousands of streams Convergence Sub 200ms failover times Interoperability With PIM/IGMP Virtualization Support Multi-tenancy Hosted Data Center support 24

©2013 Avaya Inc. All rights reservedFebruary 26-28, 2013 | Orlando, FL Thank you! #AvayaATF