Fabric Connect Multicast A Technology Overview. Ed Koehler - Director DSE. Avaya Networking Solutions Group

Fabric Connect Multicast A Technology Overview Ed Koehler - Director DSE Avaya Networking Solutions Group IAUG Newport RI, November 2013

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. 2011 Avaya Inc. All rights reserved. 2

IEEE 802.1d Flood & Learn Forwarding Known MAC 802.3 Frame received MAC A to MAC B A Port 1 C Port 4 Port 3 D MAC FIB Mac B = port 2 Mac A = port 1 Mac D = port 3 Port 2 B 2011 Avaya Inc. All rights reserved. 3

IEEE 802.1d Flood & Learn Forwarding Unknown MAC 4). FIB Table updates MAC C to port 4 C 3).MAC C responds Port 1 A Port 4 Port 3 D MAC FIB Mac B = port 2 Mac A = port 1 Mac D = port 3 Mac C = port? 1). 802.3 Frame received MAC A to MAC C 2). MAC C unknown = flood B Port 2 2011 Avaya Inc. All rights reserved. 4

Switch 1 Switch 2 Switch 3 IEEE 802.1d Flood & Learn Forwarding Unknown MAC flooding across a virtualized core MAC FIB Mac B = port 2 Mac A = port 1 Mac D = port 2 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 3 Mac C = port? A C 100 200 R 300 300 Flood for MAC C B D 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, all switches that are members of the 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. 2011 Avaya Inc. All rights reserved. 5

Legacy IP Multicast Protocol Overlay Model PIM Multicast Overlay Snooping Source begins to end media Source DR Source Register 1 st Media Delivery Path RP RPT Join RPT Prune SPT Join (2 nd )Shortest Media Delivery Path DR media Join Complex & Touchy!!!! Snooping Join Receiver OSPF Unicast Overlay R L2 R R L2 Ethernet Switching Infrastructure (Stateless) 2011 Avaya Inc. All rights reserved. 6

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

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,Length,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 2011 Avaya Inc. All rights reserved. 8

Creating a Link State Topology using IS-IS 0.00.05 IS-IS L2 Hello s TLV s 1). Topology 2). IP Reachability 3). Provisioned Services 0.00.06 0.00.04 0.00.03 0.00.01* Dyjkstra SPT from the perspective of SPB node 0.00.01 0.00.02 * IEEE SPB Nick Name 2011 Avaya Inc. All rights reserved. 9

The use of IEEE 802.1ah (MAC-in-MAC) with ISIS Normal 802.3 Frame DA SA C-MAC Frame SPB Demarcation Point 802.1 ah Frame 0.00.05 DA SA C-MAC Frame B-MAC Frame Normal 802.3 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!) 0.00.06 Dyjkstra from the perspective of 0.00.01 0.00.02 0.00.03 0.00.04 0.00.05 0.00.06 0.00.04 0.00.03 0.00.01 0.00.02 DA SA C-MAC Frame Normal 802.3 Ethernet Switch 2011 Avaya Inc. All rights reserved. 10

IEEE 802.1aq Shortest Path Bridging and it s use of 802.1ah MAC-in-MAC Provider Based Bridging Increase in Virtualization 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 4096 Service instances 4096x4096 Service instances 16,777,215 Service instances! 2011 Avaya Inc. All rights reserved. 11

Flexible Network Services Layer 2 Virtual Service Network Mapping of a Layer 2 into a Virtual Service Network delivering seamless Layer 2 extensions Virtual Service Network IP Shortcuts Native IP routing across the Virtual Service Fabric without the need for Virtual Service Networks or any additional IGP Layer 3 Virtual Service Network Mapping of a Layer 3 VRF into a Virtual Service Network delivering seamless Layer 3 extensions Virtual Service Network Inter-VSN Routing Enhancing 802.1aq by offering a policy-based Layer 3 internetworking capability of multiple Virtual Service Networks Virtual Service Network Virtual Service Network 2011 Avaya Inc. All rights reserved. 12

Constrained Multicast in SPB used to service Flood & Learn 10.10.10.0/24 1000 Here I am! 10.10.10.0/24 1000 IP 10.10.10.11 0.00.06 0.00.05 0.00.04 0.00.03 1). Topology IS-IS 2). IP L2 Reachability Hello s TLV s 3). Provisioned Services 10.10.10.0/24 1000 0.00.01 IP 10.10.10.10 Dyjkstra SPT for I-SID 1000 from the perspective of SPB node 0.00.01 0.00.02 ARP 10.10.10.11 Example : Nickname = 0.00.01, I-SID = 1000 (0x3e8) Source & RPF are known! BMAC Dest. Multicast Address = 03:00:01:00:03:e8 NICK-NAME & 3 I-SID in Hexadecimal 2011 Avaya Inc. All rights reserved. 13

True L3 Multicast delivered native over IEEE 802.1aq IP 10.10.10.12 Snooping 10.10.10.0/24 1000 We are both interested in 239.1.1.1 10.10.10.0/24 1000 Snooping IP 10.10.10.11 0.00.06 0.00.05 0.00.04 Dynamic I-SID 16,000,001 Set up to establish multicast service via IS-IS LSDB Information on I-SID 16,000,001 Relayed to every SPB node via IS-IS TLV s 0.00.03 I-SID 1000 I also am interested in 239.1.1.1 Snooping 0.00.01 0.00.02 10.10.10.0/24 1000 10.10.11.0/24 100 Sending video to 239.1.1.1 IP 10.10.10.10 Crossing L3 Boundaries without multicast routed interfaces! Snooping IP 10.10.11.10 2011 Avaya Inc. All rights reserved. 14

IP 10.10.130.10 True L3 Multicast delivered inside an IP VPN Service!! Snooping 10.10.130.0/24 300 We are both interested in 239.1.1.1 10.10.120.0/24 200 Snooping IP 10.10.120.10 VRF 0.00.06 0.00.05 VRF 0.00.04 Dynamic I-SID 16,000,002 Set up to establish multicast service via IS-IS LSDB Information on I-SID 16,000,002 Relayed to every SPB node via IS-IS TLV s I-SID 5100 0.00.03 VRF I also am interested in 239.1.1.1 Snooping 10.10.140.0/24 VRF 0.00.02 400 0.00.01 10.10.150.0/24 500 Sending video to 239.1.1.1 IP 10.10.140.10 Snooping IP 10.10.150.10 2011 Avaya Inc. All rights reserved. 15

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. 2011 Avaya Inc. All rights reserved. 16

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,... 2011 Avaya Inc. All rights reserved. 17

Deployment Scenario Video Surveillance (IP Camera Deployment - Transportation, Airports, Government...) Routing Instance! Many to Few Senders Senders SPB Senders Senders L3VSN or GRT Shortcuts Video on demand Receiver Screens (IP Multicast from cameras) Senders Video Recorders (IP unicast from cameras) 18 SMLT BEBs in the Data Center are only here Be sure to stop and see Pelco s Endura Multicast Video Surveillance Solutions running onavaya s Fabric Connect Native Multicast! 2011 Avaya Inc. All rights reserved. 18

TV-, Video-, Ticker-, Image Distribution Routing Instance! Few to Many SPB Maybe some L3VSN or GRT Shortcuts Sender Many of these BEBs (BEBs might be doing SMLT) Only behind them SMLT BEBs in the Data Center 19 2011 Avaya Inc. All rights reserved. 19

Multicast in Data Centers TOR 8600 SPB L2VSN L2VSN Senders L2VSN L2VSN Sender Receiver SPB Querier recognition and drawing all streams towards querier (wildcard querier join) 20 2011 Avaya Inc. All rights reserved. 20

Multi-Tenant IP Multicast Usage to Support VXLAN Multicast Shortest Path Distribution Trees Routing Instance! Red DC Green DC SPB L3VSN IP Multicast Green only L3VSN IP Multicast Red only Yellow DC L3VSN IP Multicast Yellow only Multi-tenant Data Center Green and Red and Yellow users cannot communicate Each has a totally separate multicast environment 21 2011 Avaya Inc. All rights reserved. 21

Multi-Tenant IP Multicast Routing Instance! SPB L3VSN IP Unicast Server Green users only IP Unicast Server Red users only L3VSN Green and Red users cannot communicate But they both need to receive Multicast stream from Shared Server Multi-tenant Data Center 22 2011 Avaya Inc. All rights reserved. 22

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 100ms failover times Interoperability With PIM/ Virtualization Support Multi-tenancy Hosted Data Center support 2011 Avaya Inc. All rights reserved. 23