Transcript Ed Koehler - Michael McNamara

©2013 Avaya Inc. All rights reserved
February 26-28, 2013 | Orlando, FL
Scalable & Simple
Multicast Solutions…
Interested?
Edwin C. Koehler
Director – Distinguished CSE
Avaya
#AvayaATF
@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.
©2013 Avaya Inc. All rights reserved
3
February 26-28, 2013 | Orlando, FL
IEEE 802.1d Flood & Learn Forwarding
Known 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
D
A
Port 1
Port 2
B
©2013 Avaya Inc. All rights reserved
4
February 26-28, 2013 | Orlando, FL
IEEE 802.1d Flood & Learn Forwarding
Unknown MACs
4). FIB Table updates MAC ‘C’ to port 4
C
3).MAC ‘C’ responds
Port 4
Port 1
A
MAC FIB
MAC B = port 2
MAC A = port 1
MAC D = port 3
MAC C = port ?
Port 3
D
1). 802.3 Frame received
MAC ‘A’ to MAC ‘C’
2). MAC ‘C’ unknown = flood
Port 2
B
©2013 Avaya Inc. All rights reserved
5
February 26-28, 2013 | Orlando, FL
IEEE 802.1d Flood & Learn Forwarding
Unknown MAC Flooding across a Virtualized Core
A
Switch 1
Switch 2
Switch 3
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
R
VLAN 200
C
D
VLAN 300
1.
2.
3.
4.
B
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.
©2013 Avaya Inc. All rights reserved
6
February 26-28, 2013 | Orlando, FL
Legacy IP Multicast Protocol
Overlay Model
PIM Multicast Overlay
Source
Register
IGMP
Snooping
RP
RPT
Prune
DR
SPT Join
(2nd)Shortest Media
Delivery Path
Source begins to
send media
Source
OSPF Unicast Overlay
L2
1st Media
Delivery Path
RPT
Join
Complex
& Touchy!!!!
IGMP
Join
IGMP
Snooping
DR
media
IGMP
Join
Receiver
R
R
R
L2
Ethernet Switching Infrastructure
(Stateless)
©2013 Avaya Inc. All rights reserved
7
February 26-28, 2013 | Orlando, FL
Which Fabric Technology is the
Answer?
• That all depends on how you qualify the question…
©2013 Avaya Inc. All rights reserved
L3 Multicast Virtualization
L3 Unicast Virtualization
L2 Multi-Site Virtualization
L2 Single-Site Virtualization
L2 Multi-Pathing
IETF MPLS
Juniper QFabric
Brocade VCS
Cisco FabricPath
IETF TRILL
STP
• VPLS
Application Extensions
Avaya Fabric Connect
Avaya Extensions
Aspirational
Single
logical Switch /
functionality
Root Bridge
Layer
3 awareness
–
Baseline
fault
Abstraction
domain
redundancy
But
it
requires:
dependent
Unicast
& Multicast
Root
100m
Service-based
Bridge
distance
–
•support
BGP
Large flooding domain
dependent
limitation
virtualization
• LDP
VLAN-based
Application-driven
•Orchestration-ready
RSVP-TE
Not
VLAN-based
shortest path
virtualization
extensibility
•virtualization
Draft-Rosen
IEEE SPB
•
•
•
••
•
•
•
•
•
L2 Loop-free Topology
8
February 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
©2013 Avaya Inc. All rights reserved
9
February 26-28, 2013 | Orlando, FL
Creating a Link State Topology
using IS-IS
1. Topology
2. IP Reachability
3. 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’
©2013 Avaya Inc. All rights reserved
10
February 26-28, 2013 | Orlando, FL
The Use of IEEE 802.1ah
(MAC-in-MAC) with ISIS
SPB Demarcation Point
Normal 802.3 Frame
DASA
802.1 ah Frame
DA SA
C-MAC Frame
C-MAC Frame
B-MAC Frame
SPB Node
0.00.05
Dyjkstra from the perspective of…
0.00.01
0.00.02
0.00.03
0.00.04
0.00.05
0.00.06
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.06
SPB Node
0.00.01
SPB Node
0.00.03
SPB Node
0.00.02
DASA
C-MAC Frame
Normal 802.3 Ethernet Switch
©2013 Avaya Inc. All rights reserved
11
February 26-28, 2013 | Orlando, FL
IEEE 802.1aq “Shortest Path Bridging” and it’s
use of 802.1ah MAC-in-MAC
“Provider Based Bridging”
Increase in Virtualization
C-SA
C-DA
C-TAG
TPID
S-TAG
I-TAG
I-SID
B-TAG
B-DA
B-SA
= Customer Source MAC
= Customer Destination MAC
= Customer TAG
= Tag Protocol IDentifier
= Service TAG
= Service Instance TAG
= Service ID
= Backbone TAG
= Backbone DA
= Backbone SA
©2013 Avaya Inc. All rights reserved
4096 Service
instances
4096x4096 Service
instances
16,777,215 Service
instances!
12
February 26-28, 2013 | Orlando, FL
Flexible Network Services
Layer 2 Virtual Service Network
Virtual Service Network
Mapping of a Layer 2 VLAN into a Virtual Service Network delivering
seamless Layer 2 extensions
IP Shortcuts
Native IP routing across the Virtual Service Fabric without
need for Virtual Service Networks or any additional IGP
the
VLAN
VLAN
Layer 3 Virtual Service Network
Mapping of a Layer 3 VRF into a Virtual Service Network delivering
seamless Layer 3 extensions
Inter-VSN Routing
Virtual Service Network
Enhancing 802.1aq by offering a policy-based Layer 3
internetworking capability of multiple Virtual Service Networks
©2013 Avaya Inc. All rights reserved
Virtual Service Network
13
Virtual Service Network
February 26-28, 2013 | Orlando, FL
Constrained Multicast in SPB Used
to Service “Flood & Learn”
10.10.10.0/24
SPB Node
0.00.05
VLAN 1000
IS-IS L2
Hello’s
TLV’s
1.
2.
3.
Topology
IP Reachability
Provisioned Services
ARP
10.10.10.11
10.10.10.0/24
Here I am!
VLAN 1000
SPB Node
0.00.04
SPB Node
0.00.01
10.10.10.0/24
IP 10.10.10.10
VLAN 1000
IP 10.10.10.11
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
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
I-SID in Hexadecimal
NICK-NAME & “3”
©2013 Avaya Inc. All rights reserved
14
February 26-28, 2013 | Orlando, FL
True L3 Multicast Delivered
‘Natively’ over IEEE 802.1aq
IP 10.10.10.12
IGMP
Snooping
SPB Node
0.00.05
10.10.10.0/24
Information on I-SID 16,220,100
Relayed to every SPB node via
IS-IS TLV’s
VLAN 1000
I-SID 1000
We are both
interested in
239.1.1.1
IGMP
Snooping
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
Crossing L3 Boundaries without
multicast routed
interfaces!
IGMP
Snooping
IP 10.10.10.11
Sending
video to
239.1.1.1
SPB Node
0.00.06
SPB Node
0.00.02
SPB Node
0.00.03
10.10.11.0/24
Dynamic I-SID
16,220,100
Set up to establish
multicast service via
IS-IS LSDB
©2013 Avaya Inc. All rights reserved
I also am
interested
in 239.1.1.1
15
VLAN 100
IGMP
Snooping
IP 10.10.11.10
February 26-28, 2013 | Orlando, FL
True L3 Multicast Delivered Inside
an IP VPN Service!!
IP 10.10.130.10
IGMP
Snooping
10.10.130.0/24
VLAN 300
SPB Node
0.00.05
Information on I-SID 16,500,000
Relayed to every SPB node via
IS-IS TLV’s
VRF
We are both
interested in
239.1.1.1
Sending
video to
239.1.1.1
IGMP
Snooping
I-SID 5100
10.10.140.0/24
VRF
SPB Node
0.00.04
VLAN 400
SPB Node
0.00.01
10.10.120.0/24
IP 10.10.140.10
VLAN 200
IGMP
Snooping
IP 10.10.120.10
VRF
SPB Node
0.00.06
SPB Node
0.00.03
Dynamic I-SID
16,500,000
Set up to establish
multicast service via
IS-IS LSDB
©2013 Avaya Inc. All rights reserved
SPB Node
0.00.02
10.10.150.0/24
I also am
interested
in 239.1.1.1
16
VRF
VLAN 500
IGMP
Snooping
IP 10.10.150.10
February 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.
©2013 Avaya Inc. All rights reserved
17
February 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,...
©2013 Avaya Inc. All rights reserved
18
February 26-28, 2013 | Orlando, FL
Deployment Scenario Video Surveillance
(IP Camera Deployment - Transportation, Airports,
Government...)
Many to Few
Routing Instance!
Senders
Senders
Senders
Senders
VLAN
VLAN
VLAN
SPB
L3VSN or
GRT Shortcuts
VLAN
Senders
VLAN
IGMP
VLAN
VLAN
Video on demand
Receiver Screens
(IP Multicast from
cameras)
Video Recorders
(IP unicast from cameras)
• SMLT BEBs in the Data Center
• Receivers are only here
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 reserved
19
February 26-28, 2013 | Orlando, FL
TV-, Video-, Ticker-, Image Distribution
Routing Instance!
Receivers
Receivers
Few to Many
VLAN
VLAN
Maybe some
Receivers
SPB
Receivers
VLAN
Receivers
L3VSN or
GRT Shortcuts
VLAN
Sender
VLAN
Receivers
VLAN
• Many of these BEBs
(BEBs might be doing SMLT)
• Only Receivers behind them
©2013 Avaya Inc. All rights reserved
• SMLT BEBs in the Data Center
20
February 26-28, 2013 | Orlando, FL
Multicast in Data Centers
TOR
Receivers
Receivers
VLAN
L2VSN
VLAN
Receivers
SPB
L2VSN
Receivers
Senders
8600
VLAN
L2VSN
VLAN
L2VSN
©2013 Avaya Inc. All rights reserved
VLAN
VLAN
Sender
Receiver
IGMP
VLAN
IGMP
VLAN
SPB
21
•Querier recognition and
drawing all streams towards
querier (wildcard querier join)
February 26-28, 2013 | Orlando, FL
Multi-Tenant IP Multicast Usage
to Support VXLAN
Multicast Shortest Path Distribution Trees
Routing Instance!
Green DC
VLAN
Red DC
VLAN
Yellow DC
VLAN
SPB
IP Multicast
Green only
L3VSN
VLAN
L3VSN
VLAN
L3VSN
IP Multicast
Red only
VLAN
IP Multicast
Yellow only
Multi-tenant Data Center
• Green and Red and Yellow users cannot
communicate
• Each has a totally separate multicast
environment
©2013 Avaya Inc. All rights reserved
22
February 26-28, 2013 | Orlando, FL
Multi-Tenant IP Multicast
Routing Instance!
Receivers
Receivers
VLAN
VLAN
Receivers
L3VSN
VLAN
Receivers
IP Unicast Server
Green users only
VLAN
VLAN
IP Unicast Server
Red users only
L3VSN
VLAN
Receivers
SPB
VLAN
Multi-tenant Data Center
• Green and Red users cannot communicate
• But they both need to receive Multicast
stream from Shared Server
©2013 Avaya Inc. All rights reserved
23
February 26-28, 2013 | Orlando, FL
What Were the Requirements to
Build SPB with IP Multicast Support?
• Simplicity
•
•
•
•
• Convergence
Configuring – Infrastructure
Provisioning – New services
Operations
Stream monitoring – end to
end transparency
• Sub 200ms failover times
• Interoperability
• With PIM/IGMP
• Virtualization Support
• Multi-tenancy
• Hosted Data Center support
• Flexibility
• No topology Dependency,
Support Rings, Meshes...
• Scalability
• Scale to the 10‘s of
thousands of streams
©2013 Avaya Inc. All rights reserved
24
February 26-28, 2013 | Orlando, FL
Thank you!
#AvayaATF
@Ed_Koehler
©2013 Avaya Inc. All rights reserved
25
February 26-28, 2013 | Orlando, FL