Paul Unbehagen-ATF_Demystifying Fabrics V2

Report
©2013 Avaya Inc. All rights reserved
February 26-28, 2013 | Orlando, FL
Demystifying Fabrics
When, Where and Why…
Paul Unbehagen
Chief Architect
Avaya Networking
#AvayaATF
@punbehagen
©2013 Avaya Inc. All rights reserved
February 26-28, 2013 | Orlando, FL
It’s On!
• Info provided via Twitter:
• Demystifying Fabrics (#Fabrics)
• Deployment Option for Avaya VENA DToR (#dToR)
• Software defined networking #SDN
©2013 Avaya Inc. All rights reserved
3
February 26-28, 2013 | Orlando, FL
The (Data Center) Network Fabric..?
©2013 Avaya Inc. All rights reserved
4
February 26-28, 2013 | Orlando, FL
The Agile Network..!
©2013 Avaya Inc. All rights reserved
5
February 26-28, 2013 | Orlando, FL
Not all Fabrics are the same
Replace Spanning Tree Protocol
©2013 Avaya Inc. All rights reserved
?
6
Replace Spanning Tree Protocol
OSPF
PIM
MPLS
BGP
LDP
February 26-28, 2013 | Orlando, FL
Which Fabric Technology is the Answer..?
©2013 Avaya Inc. All rights reserved
Application Awareness
L3 Multicast Virtualization
L3 Unicast Virtualization
L2 Multi-Site Virtualization
L2 Single-Site Virtualization
L2 Multi-Pathing
IETF MPLS
Juniper QFabric
Brocade VCS
STP
•
Cisco FabricPath
•
••
Aspirational
Single logical
Root
Bridge –
functionality
Baseline
Switch
/ fault
Layer
3 Awareness
dependent
Abstraction
But
it requires:
redundancy
domain
Unicast
& Multicast
flooding
Service-based
•Large
BGP
support
Root
100m
Bridge
distance
–
domain
•virtualization
LDP
Application-driven
dependent
limitation
Orchestration-ready
•VLAN-based
RSVP-TE
extensibility
Not
VLAN-based
shortest path
•virtualization
Draft-Rosen
virtualization
• VPLS
IETF TRILL
••
•
••
•
•
•
•
IEEE SPB – Multi-Vendor
Avaya VENA Fabric Connect
Avaya Extensions
That all depends on how you qualify the question…
L2 Loop-free Topology
7
February 26-28, 2013 | Orlando, FL
Technology Compared
L2 loopfree
Topology
L2
Multipathing
L2
Virtualization
L3
Virtualization
Single
DC
Unicast
Multiple/
hosted
DC
Multicast
Other virtualization:
- IPv6 Virtualization
- Application based Virtualization
-…
Spanning Tree
802.1Q
TRILL/FabricPath
Vlan
based
SPB IEEE
Service
based
SPB IETF (draft Unbehagen)
MPLS/BGP/LDP/RSVP-TE/Draft-Rosen/VPLS
©2013 Avaya Inc. All rights reserved
8
February 26-28, 2013 | Orlando, FL
Forwarding Comparison
Outer Layer 2 header is replaced at each hop with an appropriate Layer 2 header for the next hop and a hop count is decreased
TRILL
X
Host X
MAC Z
Rbridge A
TRILL Nickname TA
FCS
Payload
MAC C
MAC B
Router B
X | Y
TA | TE
Z | B
Inner-Eth
TRILL
Outer-Eth
FCS’
Payload
SPB
X
MAC D
MAC N
Payload
X | Y
TA | TE
Inner-Eth
TRILL
Host Y
MAC I
Rbridge E
TRILL Nickname TE
MPLS
Router D
Router C
X | Y
TA | TE
Inner-Eth
TRILL
FCS’’
MAC H
MAC F
C | D
Outer-Eth
Y
Eth
N | F
Outer-Eth
FCS’’’
Payload
X | Y
TA | TE
Inner-Eth
TRILL
H | I
Outer-Eth
Route Lookup
Host X
Host Y
SPB B
SPB A
FCS
SPB C
X | Y
Payload
SPB D
Y
SPB E
A | E
Eth
SPB is much simpler, lower cost, OAM-transparent solution
©2013 Avaya Inc. All rights reserved
9
February 26-28, 2013 | Orlando, FL
Loop Handling…
SPB
TRILL & FabricPath
MAC-B
MAC-A
2/11
•
2/12
MAC-B
MAC-A
Ingress SPB Forwarding
Database
2/11
MAC-A
2/12
MAC-B
TTL
2/11
2/12
TTL allow loop and discard it after value reach 0
– Give up on the problem, dimensioning the crater..
•
SPB’s RPFC (Reverse Path Forwarding Check) does not allow loops
– Prevents Loops before they begin
©2013 Avaya Inc. All rights reserved
10
February 26-28, 2013 | Orlando, FL
Provisioning New Services..?
• Causes:
• Based on VLANs
• Touch-points everywhere
• ..?
• Impact:
•
•
•
•
•
©2013 Avaya Inc. All rights reserved
11
Error prone
Slows time-to-service
Constrains agility
Virtualization unfriendly
..?
February 26-28, 2013 | Orlando, FL
Subnets Spanning Data Centers..?
©2013 Avaya Inc. All rights reserved
12
February 26-28, 2013 | Orlando, FL
Migrating Applications & Virtual Machines..?
©2013 Avaya Inc. All rights reserved
13
February 26-28, 2013 | Orlando, FL
Start With Carrier-Grade
Foundations
Instantaneous
Recovery
©2013 Avaya Inc. All rights reserved
14
February 26-28, 2013 | Orlando, FL
Encompass Data Center, Campus Core & Edge
End-to-End
©2013 Avaya Inc. All rights reserved
15
February 26-28, 2013 | Orlando, FL
Need To Add New Services..?
Edge-Only
Provisioning
©2013 Avaya Inc. All rights reserved
16
February 26-28, 2013 | Orlando, FL
Need To Add Multicast..?
Receiver
Receiver
Multicastfor-Free
Sender
©2013 Avaya Inc. All rights reserved
17
February 26-28, 2013 | Orlando, FL
Need To Add Greater Separation..?
Integrated
Routing & VRF
©2013 Avaya Inc. All rights reserved
18
February 26-28, 2013 | Orlando, FL
Need To Add More Capacity..?
Real-Time
Maintenance
©2013 Avaya Inc. All rights reserved
19
February 26-28, 2013 | Orlando, FL
SPB’s Forwarding Model
All traffic is forwarded in the most optimal path based on SPF calculations
Replication done at optimal point
based on shortest path algorithm
Packets only traverse SPF links,
no out of order packets, only
Edge-8
nodes that are a member of the
same service receive packets
Multicast traffic originates at Edge-1.
One multicast packet sent to Core-1.
Edge-9
Edge-1
Edge-6
Core-1
Core-2
Edge-2
Unicast
and Multicast always followEdge-3
the same path
No intervention needed, no root bridges, just turn it on
Edge-4
VLANCommon
evolves into
a
Service
with
simple
end
point
provisioning
VLAN service
©2013 Avaya Inc. All rights reserved
20
Edge-5
February 26-28, 2013 | Orlando, FL
TRILL’s Forwarding Model Problem
unicast and multicast can take different paths
In Trill model, unicast and multicast take different paths
Replication NOT done at optimal point,
but to the SPF to the root bridge
Multicast traffic originates at Edge-1.
One multicast packet sent to a root bridge.
Edge-8
Edge-9
Root Bridge
Edge-1
Unicast can take a different path,
risking reordering packets
Core-1
Edge-2
Edge-6
Core-2
Edge-3
Edge-4
Edge-5
Common VLAN service
©2013 Avaya Inc. All rights reserved
21
February 26-28, 2013 | Orlando, FL
TRILL’s Forwarding Model Problem
the solution is worse then the original problem… Make every edge a ROOT Bridge!
To get best multicast model they have to make every edge a root bridge
Packets sent to non-service participating
Lots of manual config of where root bridges exist
nodes, just to be dropped
Multicast traffic originates at Edge-1.
Causing
every edge to receive a packet whether it has a service or not
One multicast packet sent to Core-1.
Edge-8
Edge-9
Root Bridge
Edge-1
Core-1
Edge-2
Edge-6
Core-2
Edge-3
Edge-4
Edge-5
Common VLAN service
©2013 Avaya Inc. All rights reserved
22
February 26-28, 2013 | Orlando, FL
Avaya’s Approach
©2013 Avaya Inc. All rights reserved
23
February 26-28, 2013 | Orlando, FL
Game-Changing Functionality
Three pillars of value to Fabric Connect
Fast
Flexible
Secure
©2013 Avaya Inc. All rights reserved
•
•
•
•
Provision at the “edge”
One Configuration Command
Optimized Link State Protocol
Fast to Converge, heal,& add, delete, move services
• Extend services anywhere seamlessly
• True service virtualization with ease
• L2, L3, Multicast, VRFs…
• As much service isolation as needed
• Carrier type virtualization, zero complexity
• Network Invisibility to users
24
February 26-28, 2013 | Orlando, FL
An Innovative Approach to a
Growing Problem
ERS 8800
Fabric Connect Core
VSP 9000
VSP 9000
North-South/CoreToR Interconnects
VSP 7000
SDSN
Distributed
Data Center
SDSN
Distributed Top-of-Rack
©2013 Avaya Inc. All rights reserved
25
SDSN
February 26-28, 2013 | Orlando, FL
Flexible Network Services
Trill and FabricPath can only do L2
Layer 2 Virtual Service Network
Virtual Service Network
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
SPB enables all service types
Mapping of a Layer 2 VLAN into a Virtual Service Network delivering
seamless Layer 2 extensions
26
Virtual Service Network
February 26-28, 2013 | Orlando, FL
Technology Evolution
Completely unique solution to the real DC problem
Fabric Connect
•
•
•
3-D design
Optimized for actual traffic
flow
True, extensible virtualization
for Networking, Compute,
and Storage
©2013 Avaya Inc. All rights reserved
27
February 26-28, 2013 | Orlando, FL
Service Oriented Networking
The Benefit of SPB
Network Service Layer is independent from infrastructure provider
Network
Service Layer
Layer 3
Virtualized
Multicast
Service
Layer 3
Virtualized
Unicast
Service
Layer 3
Multicast
Service
Layer 2
(E-LAN)
Virtualized
Service
VXLAN
Service
E-Line
Service
RFC 6329 IS-IS / 802.1aq (SPBm)
802.1ah (MACinMAC)
(2-16 BVLANs)
Forwarding
Plane
Dark
Fiber
Physical
Infrastructure
©2013 Avaya Inc. All rights reserved
CWDM/
DWDM
E-LINE/VPWS
(PBB - or MPLS
based)
E-LAN/VPLS
(two end-points)
ADN/SDN
Service
Customer
Service
Layer
SPB
Layer
Infrastructure
Layer
SONET, SDH, Ethernet, etc…
28
February 26-28, 2013 | Orlando, FL
Multiple Service Providers
Connectivity
Layer
E-Tree
Service
“ACME“
Control
Plane
Layer 3
Unicast
Service
Integrated Multicast value
Powerful Integrated IP Multicast support for an alternative to PIM
• Key Characteristics:
• Use Cases:
•
•
•
IP Video Surveillance
IPTV
VMware VXLAN integration
IPMC
ISIS
IGMP
ISIS
ISIS
ISIS
ISIS
both Edge & Core
VSP 9000
•
ISIS
Join 239.0.0.10
ISIS
IGMP
•
ISIS
ISIS
Receiver
Multicast Sender
Group 239.0.0.10
ERS 8800
•
ISIS
ISIS
• Availability:
•
Join 239.0.0.10
Core; Edge to be added in 3.4
Join 239.0.0.10
IGMP
•
Receiver
Standard IGMP at the Access
Autonomic within the Fabric
No need for PIM or DVMRP
complexity
L2 or L3 Virtual Services Networks
IGMP
•
•
•
Join 239.0.0.10
Receiver
Receiver
©2013 Avaya Inc. All rights reserved
29
February 26-28, 2013 | Orlando, FL
Summary
•
Standards
• SPB: IEEE 802.1aq Shortest Path Bridging
• 802.1aq supports two modes, SPB VID (SPBV) and SPB MAC (SPBM) where the
ERS 8600/8800 supports SPBM
• SPBV uses Q-in-Q IEEE 802.1ad encapsulation
• SPBM uses mac-in-mac IEEE 802.1ah (Supported by Avaya and others)
•
•
IEEE protocols that have already been deployed in carriers and enterprises around the world
FabricPath
• No standards, completely proprietary from Cisco
•
TRILL
• TRILL is a IETF standard reinventing IEEE protocols that have already been
deployed in carriers and enterprises around the world
• KEY NOTES
•
SPB has successfully demonstrated multi-vendor interoperability
•
•
•
http://ieee802.org/1/files/public/docs2011/aq-ashwood-smith-spbm-3rd-interop-0718-v01.pdf
FabricPath is totally proprietary – how does a Cisco customer migrate to TRILL?
With TRILL, no two vendors implementation is the same; no multi-vendor interoperability!!
©2013 Avaya Inc. All rights reserved
30
February 26-28, 2013 | Orlando, FL
Thank you!
#AvayaATF
@punbehagen
©2013 Avaya Inc. All rights reserved
31
February 26-28, 2013 | Orlando, FL

similar documents