demystifying fabrics when, where and why…


#AvayaATF

Demystifying FabricsWhen, Where and Why…

Paul UnbehagenChief ArchitectAvaya Networking

@punbehagen


©2013 Avaya Inc. All rights reserved

February 26-28, 2013 | Orlando, FL

It’s On!

• A friendly competition among presenters• Help @punbehagen win

• Easy to remember name• @randy_cross? Too forgettable

• Tweet this session with #AvayaATF and #SDN• You could win a iPad Mini…

• If you don’t have a twitter account…• Get one, you can delete after the show

• Help me WIN by coming to my other sessions (and Tweeting!)• Demystifying Fabrics (#Fabrics)• Deployment Option for Avaya VENA DToR (#dToR)

3



The (Data Center) Network Fabric..?

4



The Agile Network..!

5


6

Not all Fabrics are the same

Replace Spanning Tree Protocol Replace Spanning Tree ProtocolOSPFPIM

MPLSBGPLDP

?




Which Fabric Technology is the Answer..?

7

Avay

a VE

NA

Fabr

ic C

onne

ctAv

aya

Exte

nsio

nsIE

EE S

PB –

Mul

ti-Ve

ndor

• Aspirational functionality

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

• Baseline redundancy

• Root Bridge –dependent

• Not shortest path

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 Awareness• 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

That all depends on how you qualify the question…



L2 loopfreeTopology

Spanning Tree802.1Q

L2Multipathing

TRILL/FabricPath

L 2 Virtualization

Vlan based

SPB IEEEService based

L 3 Virtualization

SPB IETF (draft Unbehagen)

Unicast Multicast

Other virtualization:

MPLS/BGP/LDP/RSVP-TE/Draft-Rosen/VPLS

- IPv6 Virtualization- Application based Virtualization- …

SingleDC

Multiple/ hostedDC

Root Bridge

Dependency

Large Flooding Domain

Root Bridge

Dependency Not shortest

path

Technology Compared

8



Forwarding Comparison

Outer-EthZ | B

Rbridge ATRILL Nickname TA Router B Router C Router D Rbridge E

TRILL Nickname TE

Host X Host YMAC Z MAC B MAC C MAC D MAC N MAC F MAC H MAC I

TRILL

N | F

Host X Host Y

SPB A SPB B SPB C SPB D SPB E

A | E

Eth

Route Lookup

TRILL

SPB

EthMPLS

C | D H | IPayload

Payload

TA | TEX | Y

X

Y

Inner-Eth

Outer-EthTRILLPayload

TA | TEX | Y

Inner-Eth

Outer-EthTRILLPayloadTA | TEX | Y

Inner-Eth

Outer-EthTRILLPayload

TA | TEX | Y

Inner-Eth

X

Y

X | Y

FCS

FCS’

FCS’’

FCS’’’

FCS

SPB is much simpler, lower cost, OAM-transparent solution

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

9



Loop Handling…

TTL allow loop and discard it after value reach 0Give up on the problem, dimensioning the crater..

SPB’s RPFC (Reverse Path Forwarding Check) does not allow loopsPrevents Loops before they begin

Ingress SPB Forwarding Database

2/11 MAC-A 2/12 MAC-B

MAC-A

2/11 2/12

MAC-BMAC-A

2/11 2/12

MAC-B

TTL

SPB TRILL & FabricPath

10



Provisioning New Services..?

11

• Causes:• Based on VLANs• Touch-points everywhere• ..?

• Impact:• Error prone• Slows time-to-service• Constrains agility• Virtualization unfriendly• ..?



Subnets Spanning Data Centers..?

12



Migrating Applications & Virtual Machines..?

13



Start With Carrier-Grade Foundations

InstantaneousRecovery

14



Encompass Data Center, Campus Core & Edge

End-to-End

15



Need To Add New Services..?

Edge-OnlyProvisioning

16



Need To Add Multicast..?

Sender

Receiver Receiver

Multicast-for-Free

17



Need To Add Greater Separation..?

IntegratedRouting & VRF

18



Need To Add More Capacity..?

Real-TimeMaintenance

19



SPB’s Forwarding Model

Multicast traffic originates at Edge-1.One multicast packet sent to Core-1.

Replication done at optimal point based on shortest path algorithm

Edge-1

Edge-2

Edge-4

Core-2Core-1

Edge-5

Edge-6

Edge-8Edge-9

Common VLAN service

Packets only traverse SPF links, no out of order packets, only nodes that are a member of the same service receive packets

Edge-3Unicast and Multicast always follow the same pathNo intervention needed, no root bridges, just turn it onVLAN evolves into a Service with simple end point provisioning

All traffic is forwarded in the most optimal path based on SPF calculations

20



Multicast traffic originates at Edge-1.One multicast packet sent to a root bridge.

Replication NOT done at optimal point, but to the SPF to the root bridge

Edge-1

Edge-2

Core-2Core-1

Common VLAN service

TRILL’s Forwarding Model Problemunicast and multicast can take different paths

Root Bridge

Edge-3Edge-4 Edge-5

Edge-6

Edge-8Edge-9

Unicast can take a different path, risking reordering packets

In Trill model, unicast and multicast take different paths

21



Multicast traffic originates at Edge-1.One multicast packet sent to Core-1.

Packets sent to non-service participating nodes, just to be dropped

Edge-1

Edge-2

Core-2Core-1

Common VLAN service

TRILL’s Forwarding Model Problem

the solution is worse then the original problem… Make every edge a ROOT Bridge!

Root Bridge

Edge-3Edge-4 Edge-5

Edge-6

Edge-8Edge-9

To get best multicast model they have to make every edge a root bridgeLots of manual config of where root bridges existCausing every edge to receive a packet whether it has a service or not

22


23

Avaya’s Approach


©2013 Avaya Inc. All rights reserved February 26-28, 2013 | Orlando, FL24

Game-Changing Functionality

Three pillars of value to Fabric Connect

Fast

Flexible

Secure

• 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



Distributed Top-of-Rack

North-South/Core-ToR Interconnects

Fabric Connect Core

DistributedData Center

VSP 9000

ERS 8800

VSP 7000

SDSN

SDSN

SDSN

An Innovative Approach to a Growing Problem

VSP 9000

25



Flexible Network Services

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

Trill and FabricPath can only do L2

SPB enables all service types

26




Technology Evolution

27

Completely unique solution to the real DC problem

• 3-D design• Optimized for actual traffic

flow• True, extensible virtualization

for Networking, Compute, and Storage

Fabric Connect



Service Oriented Networking

The Benefit of SPBNetwork Service Layer is independent from infrastructure provider

SONET, SDH, Ethernet, etc…

Layer 3 Virtualized MulticastService

Layer 3 Virtualized

UnicastService

Layer 3Multicast

Service

Layer 3UnicastService

Layer 2(E-LAN)

Virtualized Service

Infras-tructure

Layer

RFC 6329 IS-IS / 802.1aq (SPBm)

802.1ah (MACinMAC)(2-16 BVLANs)

Forwarding Plane

Control Plane

Physical Infrastructure

Dark Fiber

CWDM/DWDM

E-LINE/VPWS(PBB - or MPLS

based)

E-LAN/VPLS(two end-points)

ConnectivityLayer

Network Service Layer

SPB Layer

CustomerService

Layer

“ACME“

Multiple Service Providers

VXLANService

E-LineService

E-TreeService

ADN/SDN Service

28



February 26-28, 2013 | Orlando, FL29

Integrated Multicast value

• Key Characteristics:• Standard IGMP at the Access• Autonomic within the Fabric• No need for PIM or DVMRP complexity• L2 or L3 Virtual Services Networks

• Use Cases:• IP Video Surveillance• IPTV• VMware VXLAN integration

• Availability:• ERS 8800

• both Edge & Core

• VSP 9000• Core; Edge to be added in 3.4

ISIS

ISIS ISIS

ISISISIS

ISISISIS

ISIS ISIS

ISIS

ISIS

Join 239.0.0.10

IGM

PIG

MP

Join 239.0.0.10

IGM

P

Join 239.0.0.10

IPMC

Receiver

Receiver

Receiver

Join 239.0.0.10

IGM

P

Receiver

Multicast SenderGroup 239.0.0.10

Powerful Integrated IP Multicast support for an alternative to PIM



February 26-28, 2013 | Orlando, FL30

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


Thank you!#AvayaATF

31

@punbehagen

demystifying fabrics when, where and why…

Documents

rights reservedfebruary

fl2013 avaya

avayaatf2013 avaya

dtor32013 avaya

question2013 avaya

avaya vena dtor

flwhich fabric technology

punbehagen wineasy