scalable & simple multicast solutions… interested?


#AvayaATF

Scalable & Simple Multicast Solutions…Interested?Edwin C. KoehlerDirector – Distinguished CSEAvaya

@Ed_Koehler


©2013 Avaya Inc. All rights reserved

February 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



A

B

C

D

MAC FIBMAC B = port 2MAC A = port 1MAC D = port 3 802.3 Frame received

MAC ‘A’ to MAC ‘B’

Port 1

Port 2

Port 3

Port 4

IEEE 802.1d Flood & Learn ForwardingKnown MAC

4



A

B

C

D

MAC FIBMAC B = port 2MAC A = port 1MAC D = port 3MAC C = port ?

1). 802.3 Frame receivedMAC ‘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 ForwardingUnknown MACs

5



A B

C D

RVLAN 100 VLAN 200

VLAN 300 VLAN 300




1. MAC ‘A’ sends a frame to MAC ‘C’.2. MAC ‘C’ is unknown to Switch 13. 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 1 Switch 2 Switch 3

IEEE 802.1d Flood & Learn ForwardingUnknown MAC Flooding across a Virtualized Core

6



OSPF Unicast Overlay

PIM Multicast Overlay

Ethernet Switching Infrastructure(Stateless)

R

R

R

RP

DRDR

L2L2

IGMPSnooping

IGMPSnooping

Source Receiver

SourceRegister

Source begins to send media

IGMPJoin

IGMPJoin

RPTJoinRPT

Prune

SPT Join

media

1st MediaDelivery Path

(2nd)Shortest Media Delivery Path

Complex& Touchy!!!!

Legacy IP Multicast Protocol Overlay Model

7




• Aspirational functionality

• But it requires:• BGP• LDP• RSVP-TE• Draft-Rosen• VPLS

Avay

a Fa

bric

Con

nect

IEEE

SPB

Avay

a Ex

tens

ions

• 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

TRI

LL

Cisc

o Fa

bric

Path

Broc

ade

VCS

Juni

per Q

Fabr

ic

IETF

MPL

S

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




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



DyjkstraSPT from the perspective of SPB node 0.00.01

IS-IS L2 Hello’sTLV’s

1. Topology2. IP Reachability3. Provisioned Services

SPB Node0.00.01*

SPB Node0.00.02

SPB Node0.00.03

SPB Node0.00.04

SPB Node0.00.05

SPB Node0.00.06

* IEEE SPB ‘Nick Name’

Creating a Link State Topologyusing IS-IS

10



SPB Node0.00.01

SPB Node0.00.02

SPB Node0.00.03

SPB Node0.00.04

SPB Node0.00.05

SPB Node0.00.06

Dyjkstra from the perspective of…0.00.010.00.020.00.030.00.040.00.050.00.06

Normal 802.3 Frame

B-MAC Frame

SPB Demarcation Point802.1 ah Frame

C-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!)

SADA C-MAC FrameDASA

Normal 802.3 Ethernet Switch

DASAC-MAC Frame

The Use of IEEE 802.1ah (MAC-in-MAC) with ISIS

11



C-SA = Customer Source MACC-DA = Customer Destination MACC-TAG = Customer TAGTPID = Tag Protocol IDentifierS-TAG = Service TAGI-TAG = Service Instance TAGI-SID = Service IDB-TAG = Backbone TAGB-DA = Backbone DAB-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



Flexible Network Services

13

Mapping of a Layer 2 VLAN into a Virtual Service Network delivering seamless Layer 2 extensions

Layer 2 Virtual Service NetworkVirtual Service Network

Mapping of a Layer 3 VRF into a Virtual Service Network delivering seamless Layer 3 extensions

Layer 3 Virtual Service NetworkVirtual Service Network

Native IP routing across the Virtual Service Fabric without the need for Virtual Service Networks or any additional IGP

VLAN VLAN

IP Shortcuts

Enhancing 802.1aq by offering a policy-based Layer 3 internetworking capability of multiple Virtual Service Networks

Virtual Service Network

Virtual Service Network

Inter-VSN Routing



DyjkstraSPT for I-SID 1000 from the perspective of SPB node 0.00.01

IS-IS L2 Hello’sTLV’s

SPB Node0.00.01

SPB Node0.00.02

SPB Node0.00.03

SPB Node0.00.04

SPB Node0.00.05

SPB Node0.00.06

VLAN 1000

VLAN 1000

VLAN 1000

1. Topology2. IP Reachability3. Provisioned Services

IP 10.10.10.10

IP 10.10.10.11

10.10.10.0/24

10.10.10.0/24

10.10.10.0/24

NICK-NAME & “3” I-SID in Hexadecimal

Example : Nickname = 0.00.01 , I-SID = 1000 (0x3e8) Source & RPF are known! BMAC Dest. Multicast Address = 03:00:01:00:03:e8

ARP10.10.10.11

Here I am!

Constrained Multicast in SPB Used to Service “Flood & Learn”

14



SPB Node0.00.01

SPB Node0.00.02SPB Node

0.00.03

SPB Node0.00.04

SPB Node0.00.05

SPB Node0.00.06

VLAN 1000

VLAN 1000

VLAN 1000

IP 10.10.10.10

IP 10.10.10.11

10.10.10.0/24

10.10.10.0/24

10.10.10.0/24

Sending video to 239.1.1.1

We are both interested in

239.1.1.1

IP 10.10.10.12

VLAN 100

10.10.11.0/24

IP 10.10.11.10

I also am interested

in 239.1.1.1

Dynamic I-SID 16,220,100Set up to establish multicast service via IS-IS LSDB

IGMPSnooping

IGMPSnooping

IGMPSnooping

IGMPSnooping

I-SID 1000

Information on I-SID 16,220,100Relayed to every SPB node viaIS-IS TLV’s

Crossing L3 Boundaries without multicast routedinterfaces!

True L3 Multicast Delivered‘Natively’ over IEEE 802.1aq

15



SPB Node0.00.01

SPB Node0.00.02SPB Node

0.00.03

SPB Node0.00.04

SPB Node0.00.05

SPB Node0.00.06

VLAN 400

VLAN 300

VLAN 200

IP 10.10.140.10

IP 10.10.120.10

10.10.140.0/24

10.10.130.0/24

10.10.120.0/24

Sending video to 239.1.1.1

We are both interested in

239.1.1.1

IP 10.10.130.10

VLAN 500

10.10.150.0/24

IP 10.10.150.10

I also am interested

in 239.1.1.1

IGMPSnooping

IGMPSnooping

IGMPSnooping

IGMPSnooping

VRF

VRF

VRF

Dynamic I-SID 16,500,000Set up to establish multicast service via IS-IS LSDB

I-SID 5100

Information on I-SID 16,500,000Relayed to every SPB node viaIS-IS TLV’s

True L3 Multicast Delivered Inside an IP VPN Service!!

16

VRF




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




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



Deployment Scenario Video Surveillance(IP Camera Deployment - Transportation, Airports, Government...)

19

SPB

VLAN

VLAN

VLAN

VLAN

VLAN

VLAN

L3VSN orGRT Shortcuts

Senders

IGMP • SMLT BEBs in the Data Center• Receivers are only here

Routing Instance!

VLAN

Senders

Senders

Senders

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!



SPB

VLAN

VLAN

VLAN

VLAN

VLAN

VLAN

L3VSN orGRT Shortcuts

Receivers

Receivers

Receivers

Receivers

Receivers

Sender

VLAN

Maybe someReceivers

• 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



SPB

VLAN

VLAN

VLAN

VLAN

VLAN

VLAN

Receivers

Receivers

Receivers

Senders

Receivers

SenderReceiver

SPB

VLAN

VLAN

L2VSN

IGMP

L2VSN

L2VSN

L2VSN

IGMP •Querier recognition and drawing all streams towards querier (wildcard querier join)

TOR

8600

21

Multicast in Data Centers



VLAN

VLAN

VLAN

VLAN

VLAN

Multi-Tenant IP Multicast Usage to Support VXLAN

22

SPB

L3VSN

Green DC

Red DC

Yellow DC

IP MulticastGreen only

• Green and Red and Yellow users cannot communicate

• Each has a totally separate multicast environment

Multi-tenant Data Center

Routing Instance!

VLAN

IP MulticastRed onlyL3VSN

L3VSNIP MulticastYellow only

Multicast Shortest Path Distribution Trees



Multi-Tenant IP Multicast

SPB

VLAN

VLAN

VLAN

VLAN

VLAN

L3VSN

Receivers

Receivers

Receivers

Receivers

Receivers

IP Unicast ServerGreen 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

VLANIP Unicast ServerRed users only

L3VSN

23




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


Thank you!#AvayaATF

25

@Ed_Koehler

scalable & simple multicast solutions… interested?

Documents