Scalable simple multicast solutions interested
This presentation is the property of its rightful owner.
Sponsored Links
1 / 25

Scalable & Simple Multicast Solutions… Interested? PowerPoint PPT Presentation


  • 70 Views
  • Uploaded on
  • Presentation posted in: General

Scalable & Simple Multicast Solutions… Interested?. Edwin C. Koehler Director – Distinguished CSE Avaya. @ Ed_Koehler. 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

Download Presentation

Scalable & Simple Multicast Solutions… Interested?

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Scalable simple multicast solutions interested

Scalable & Simple Multicast Solutions…Interested?

Edwin C. Koehler

Director – Distinguished CSE

Avaya

@Ed_Koehler


So what s wrong with today s multicast networks

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.


Ieee 802 1d flood learn forwarding known mac

IEEE 802.1d Flood & Learn ForwardingKnown MAC

C

MAC FIB

MAC B = port 2

MAC A = port 1

MAC D = port 3

Port 4

802.3 Frame received

MAC ‘A’ to MAC ‘B’

Port 3

A

D

Port 1

Port 2

B


Ieee 802 1d flood learn forwarding unknown macs

IEEE 802.1d Flood & Learn ForwardingUnknown MACs

4). FIB Table updates MAC ‘C’ to port 4

MAC FIB

MAC B = port 2

MAC A = port 1

MAC D = port 3

MAC C = port ?

C

3).MAC ‘C’ responds

Port 4

Port 1

Port 3

A

D

1). 802.3 Frame received

MAC ‘A’ to MAC ‘C’

2). MAC ‘C’ unknown = flood

Port 2

B


Ieee 802 1d flood learn forwarding unknown mac flooding across a virtualized core

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

Switch 3

Switch 1

Switch 2

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 ?

VLAN 100

VLAN 200

R

B

A

C

D

VLAN 300

VLAN 300

Flood for MAC ‘C’

MAC ‘A’ sends a frame to MAC ‘C’.

MAC ‘C’ is unknown to Switch 1

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’.

MAC ‘C’ responds but must communicate to MAC’A’ via the router function which is running in switch 2.


Legacy ip multicast protocol overlay model

Legacy IP Multicast Protocol Overlay Model

Source

Register

1st Media

Delivery Path

Complex

& Touchy!!!!

PIM Multicast Overlay

RP

RPT

Join

IGMP

Join

IGMP

Snooping

IGMP

Snooping

RPT

Prune

DR

DR

SPT Join

IGMP

Join

Source begins to

send media

(2nd)Shortest Media

Delivery Path

media

Source

Receiver

OSPF Unicast Overlay

R

L2

R

R

L2

Ethernet Switching Infrastructure

(Stateless)


Which fabric technology is the answer

Which Fabric Technology is the Answer?

  • That all depends on how you qualify the question…

Avaya Extensions

Avaya Fabric Connect

Application Extensions

  • Aspirational functionality

  • But it requires:

    • BGP

    • LDP

    • RSVP-TE

    • Draft-Rosen

    • VPLS

  • Single logical Switch / fault domain

  • 100m distance limitation

  • VLAN-based virtualization

  • Root Bridge –dependent

  • Large flooding domain

  • VLAN-based virtualization

  • Abstraction

  • Service-based virtualization

  • Orchestration-ready

  • Layer 3 awareness

  • Unicast & Multicast support

  • Application-driven extensibility

  • Baseline redundancy

  • Root Bridge –dependent

  • Not shortest path

IETF MPLS

L3 Multicast Virtualization

L3 Unicast Virtualization

IEEE SPB

L2 Multi-Site Virtualization

IETF TRILL

Cisco FabricPath

Brocade VCS

Juniper QFabric

L2 Single-Site Virtualization

L2 Multi-Pathing

STP

L2 Loop-free Topology


Native multicast over shortest path bridging

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


Creating a link state topology using is is

Creating a Link State Topologyusing IS-IS

Topology

IP Reachability

Provisioned Services

SPB Node

0.00.05

IS-IS L2 Hello’s

TLV’s

SPB Node

0.00.04

SPB Node

0.00.01*

Dyjkstra

SPT from the perspective of SPB node 0.00.01

SPB Node

0.00.06

SPB Node

0.00.03

SPB Node

0.00.02

* IEEE SPB ‘Nick Name’


The use of ieee 802 1ah mac in mac with isis

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

SPB Demarcation Point

Normal 802.3 Frame

802.1 ah Frame

DA

SA

DA

SA

C-MAC Frame

B-MAC Frame

SPB Node

0.00.05

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

SPB Node

0.00.04

SPB Node

0.00.01

SPB Node

0.00.06

SPB Node

0.00.03

SPB Node

0.00.02

Dyjkstra from the perspective of…

0.00.01

0.00.02

0.00.03

0.00.04

0.00.05

0.00.06

DA

SA

C-MAC Frame

Normal 802.3 Ethernet Switch


Ieee 802 1aq shortest path bridging and it s use of 802 1ah mac in mac provider based bridging

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!


Flexible network services

Flexible Network Services

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

  • Layer 2 Virtual Service Network

Virtual Service Network

Virtual Service Network

Virtual Service Network

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

  • Layer 3 Virtual Service Network

Virtual Service Network

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

  • Inter-VSN Routing

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

  • IP Shortcuts

VLAN

VLAN


Constrained multicast in spb used to service flood learn

I-SID in Hexadecimal

NICK-NAME & “3”

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

ARP

10.10.10.11

10.10.10.0/24

IS-IS L2 Hello’s

TLV’s

SPB Node

0.00.05

Topology

IP Reachability

Provisioned Services

VLAN 1000

Here I am!

10.10.10.0/24

VLAN 1000

SPB Node

0.00.04

SPB Node

0.00.01

10.10.10.0/24

IP 10.10.10.10

VLAN 1000

Dyjkstra

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

SPB Node

0.00.06

SPB Node

0.00.03

IP 10.10.10.11

SPB Node

0.00.02

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


True l3 multicast delivered natively over ieee 802 1aq

True L3 Multicast Delivered‘Natively’ over IEEE 802.1aq

Information on I-SID 16,220,100

Relayed to every SPB node via

IS-IS TLV’s

IGMP

Snooping

IP 10.10.10.12

Sending video to 239.1.1.1

SPB Node

0.00.05

10.10.10.0/24

VLAN 1000

IGMP

Snooping

I-SID 1000

We are both interested in 239.1.1.1

10.10.10.0/24

VLAN 1000

SPB Node

0.00.04

SPB Node

0.00.01

10.10.10.0/24

IP 10.10.10.10

Crossing L3 Boundaries without multicast routed

interfaces!

VLAN 1000

IGMP

Snooping

SPB Node

0.00.06

IP 10.10.10.11

SPB Node

0.00.02

SPB Node

0.00.03

Dynamic I-SID 16,220,100

Set up to establish multicast service via IS-IS LSDB

10.10.11.0/24

IGMP

Snooping

I also am interested in 239.1.1.1

VLAN 100

IP 10.10.11.10


True l3 multicast delivered inside an ip vpn service

True L3 Multicast Delivered Inside an IP VPN Service!!

IP 10.10.130.10

Information on I-SID 16,500,000

Relayed to every SPB node via

IS-IS TLV’s

IGMP

Snooping

SPB Node

0.00.05

Sending video to 239.1.1.1

10.10.130.0/24

VLAN 300

VRF

IGMP

Snooping

I-SID 5100

We are both interested in 239.1.1.1

10.10.140.0/24

VRF

VLAN 400

SPB Node

0.00.04

SPB Node

0.00.01

10.10.120.0/24

IP 10.10.140.10

VLAN 200

VRF

IGMP

Snooping

SPB Node

0.00.06

IP 10.10.120.10

SPB Node

0.00.02

SPB Node

0.00.03

10.10.150.0/24

Dynamic I-SID 16,500,000

Set up to establish multicast service via IS-IS LSDB

IGMP

Snooping

I also am interested in 239.1.1.1

VRF

VLAN 500

IP 10.10.150.10


Why spb with multicast

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.


Applications

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,...


Deployment scenario video surveillance ip camera deployment transportation airports government

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

Many to Few

Routing Instance!

Senders

VLAN

Senders

VLAN

SPB

L3VSN orGRT Shortcuts

Senders

VLAN

VLAN

Video on demand Receiver Screens(IP Multicast from cameras)

VLAN

Senders

VLAN

Senders

VLAN

Video Recorders(IP unicast from cameras)

  • SMLT BEBs in the Data Center

  • Receivers are only here

IGMP

Be sure to stop and see Pelco’s Endura Multicast Video Surveillance Solutions running onAvaya’s Fabric Connect Native Multicast!


Tv video ticker image distribution

TV-, Video-, Ticker-, Image Distribution

Routing Instance!

Few to Many

Receivers

VLAN

Maybe someReceivers

Receivers

VLAN

SPB

L3VSN orGRT Shortcuts

VLAN

Receivers

VLAN

VLAN

Sender

Receivers

VLAN

VLAN

Receivers

  • Many of these BEBs (BEBs might be doing SMLT)

  • Only Receivers behind them

  • SMLT BEBs in the Data Center


Multicast in data centers

Multicast in Data Centers

L2VSN

L2VSN

TOR

Receivers

L2VSN

8600

VLAN

L2VSN

SPB

Receivers

VLAN

Receivers

VLAN

VLAN

VLAN

Sender

Receiver

Senders

VLAN

VLAN

IGMP

VLAN

Receivers

IGMP

SPB

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


Multi tenant ip multicast usage to support vxlan

Multi-Tenant IP Multicast Usage to Support VXLAN

Multicast Shortest Path Distribution Trees

Routing Instance!

L3VSN

L3VSN

Green DC

VLAN

SPB

IP MulticastGreen only

L3VSN

VLAN

Red DC

VLAN

IP MulticastRed only

VLAN

Yellow DC

VLAN

VLAN

IP MulticastYellow only

Multi-tenant Data Center

  • Green and Red and Yellow users cannot communicate

  • Each has a totally separate multicast environment


Multi tenant ip multicast

Multi-Tenant IP Multicast

Routing Instance!

Receivers

VLAN

L3VSN

Receivers

VLAN

SPB

IP Unicast ServerGreen users only

VLAN

Receivers

L3VSN

VLAN

IP Unicast ServerRed users only

VLAN

Receivers

VLAN

VLAN

Receivers

Multi-tenant Data Center

  • Green and Red users cannot communicate

  • But they both need to receive Multicast stream from Shared Server


What were the requirements to build spb with ip multicast support

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


Scalable simple multicast solutions interested

@Ed_Koehler


  • Login