DEPLOYING AND EVOLVING FABRICS IN EXISTING NETWORKS Scott Fincher Global Solutions Architect Avaya Networking
Thank you Sponsors! Global Sponsors Gold Sponsors Silver Sponsors
Join the Conversation @Avaya #AvayaATF
CHALLENGES WITH TODAY S NETWORKS Enabling Network Connectivity is not seen as a Service delivery Today s Enterprise networks are typically flat ; delivering network segmentation and virtualization is not straight forward Security = firewalling, but does not have to be. Often used to enforce segmentation Provisioning network connectivity takes too long Loop free L2 topologies often require unreliable Spanning Tree Protocol Enabling a stretched solution for virtual machine migrations is a big challenge Enabling seamless Wireless Roaming is a big challenge IoT and IPv6? Making a non fabric network IPv6 ready is a large project. Security surveillance is typically handled by separate infrastructure why? 2016 Avaya Inc. All right reserved 4
SDN Fx CAN CO-EXIST WITH LEGACY NETWORKS A Fabric enabled Enterprise Network is an Enterprise Service Provider Network The following slides depict several network scenarios and show why a fabric makes sense and how it can be deployed. Starting with a single switch deployment the benefits are shown up to a large multi-site enterprise deployment All Avaya SDN Fx Technologies (Fabric Connect, Fabric Extend, Fabric Attach) are part of the solution set depicted. 2016 Avaya Inc. All right reserved 5
INTERCONNECTIVITY OPTIONS PROVIDE FOR EVOLUTION Fabric Networks can be connected to legacy networks seamlessly Fabric Networks can be operated as overlays on top of legacy networks Whole infrastructure rips are NOT a requirement A network can evolve to end to end Fabric over time 2016 Avaya Inc. All right reserved 6
FABRIC TO NON-FABRIC INTERCONNECTIVITY OPTIONS Layer 2 - PEERING 802.1Q vist 802.1Q MLT LACP Seamless redundant connectivity options for L2 MC-LAG LACP SMLT vist vpc VSS 802.1Q vist 2016 Avaya Inc. All right reserved 7
FABRIC TO NON-FABRIC INTERCONNECTIVITY OPTIONS Layer 3 Unicast (IPv4 & IPv6) - PEERING 802.1Q vist w/rsmlt 802.1Q, Static Routing, RIP, RIPng, OSPFv2&v3, BGP+ Static Routing RIP, RIPng, OSPFv2&v3, BGP/BGP+ For proper route redistribution use IS-IS Accept Policies w/ external metrics Fabric interoperates with all routing protocols Static Routing RIP, RIPng, OSPFv2&v3, BGP/BGP+ For proper route redistribution use IS-IS Accept Policies w/ external metrics 2016 Avaya Inc. All right reserved 8
FABRIC TO NON-FABRIC INTERCONNECTIVITY OPTIONS Layer 3 IPv4 Multicast - PEERING 802.1Q vist w/rsmlt 802.1Q Static Routing RIP, OSPF, BGP, Static MC Receivers Static Routing RIP, OSPF, BGP Static MC Receivers For proper route redistribution use IS-IS Accept Policies w/ external metrics Note: VOSS Release 6.0 will provide SPB-PIM Gateway functionality for dynamic interconnection of PIM with Fabric Connect. Static Routing RIP, OSPF, BGP Static MC Receivers For proper route redistribution use IS-IS Accept Policies w/ external metrics 2016 Avaya Inc. All right reserved 9
FABRIC TO NON-FABRIC INTERCONNECTIVITY OPTIONS Fabric over IP or L2 Core using Fabric Extend - OVERLAY L2/IP Fabric Extend provides an overlay solution over L2 and/or L3 core & WAN/MAN networks 2016 Avaya Inc. All right reserved 10
NETWORK DEPLOYMENT SCENARIOS Single Switch 2-Tier Network w/ collapsed backbone 3-Tier Network 4-Tier Network Large Multi-site Enterprise Network 2016 Avaya Inc. All right reserved 11
SINGLE SWITCH DEPLOYMENT Reasons to deploy a fabric in a single switch deployment: VLAN Translation Function Seamless L3 Services Seamless IP multicast User Single Access Switch Servers 2016 Avaya Inc. All right reserved 12
2-TIER NETWORK DESIGN Collapsed Core End to end Fabric Reasons to deploy a fabric in a 2-Tier Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Server Integration Simplification with OVS on Linux Hypervisors and VPS with Vmware Seamless vmotion End-to-End Network Segmentation/ Virtualization enablement Highly Resilient Seamless IP Multicast IoT ready (IPv6) User Access Distribution Servers 2016 Avaya Inc. All right reserved 13
3-TIER NETWORK DESIGN Option 1 User Access Focus Reasons to deploy a fabric in a 3-Tier Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Campus Network Segmentation/ Virtualization enablement Highly Resilient MC-LAG/vIST User Access Distribution/ Core (L3) Access TOR Servers 2016 Avaya Inc. All right reserved 14
3-TIER NETWORK DESIGN Option 2 Focus Reasons to deploy a fabric in a : Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion Network Segmentation/ Virtualization enablement L2 segment stretch Highly Resilient multi-pathing w/ fast failover MC-LAG/vIST User Access Distribution/ Core (L3) Access TOR Servers 2016 Avaya Inc. All right reserved 15
3-TIER NETWORK DESIGN Option 3 End-to-end Fabric Reasons to deploy a fabric in a 3-Tier Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Server Integration Simplification with OVS on Linux Hypervisors and VPS with Vmware Seamless vmotion End-to-End Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover Seamless IP Multicast IoT ready (IPv6) User Access Distribution/ Core (L3) Access TOR Servers 2016 Avaya Inc. All right reserved 16
4-TIER NETWORK DESIGN Option 1 Fabric Core Reasons to deploy a fabric in a 4-Tier Network: Enterprise Provider Infrastructure Services: L2 transparent, switched, ETREE L3 routed Service enabled: Edge Provisioning only (no VLANs in core) Core Network Segmentation/ Virtualization enablement Highly Resilient IoT ready (IPv6) core Ready to extend Fabric further User Access Distribution/ Core (L3) Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 17
4-TIER NETWORK DESIGN Option 2 User Access Focus Reasons to deploy a fabric in a 4-Tier Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Campus Network Segmentation/ Virtualization enablement Highly Resilient User Access Distribution/ Core (L3) Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 18
4-TIER NETWORK DESIGN Option 3 Focus Reasons to deploy a fabric in a : Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Network Segmentation/ Virtualization enablement L2 segment stretch for Seamless vmotion Traffic Tromboning avoidance with DGW redundancy Highly Resilient multi-pathing w/ fast failover User Access Distribution/ Core (L3) Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 19
4-TIER NETWORK DESIGN Option 4 End-to-End Fabric Reasons to deploy a fabric in a 4-Tier Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion traffic tromboning avoidance with DGW redundancy End-to-End Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover Seamless IP Multicast IoT ready (IPv6) User Access Distribution/ Core (L3) Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 20
LARGE ENTERPRISE NETWORK Option 1 User Access Focus Reasons to deploy a fabric in a Large Enterprise Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Campus Network Segmentation/ Virtualization enablement Highly Resilient IoT ready Fabric Extend L2/IP User Access Distribution MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 21
LARGE ENTERPRISE NETWORK Option 2 Distribution Layer Focus (existing IP Backbone remains untouched) Reasons to deploy a fabric in a Large Enterprise Network: Enterprise Provider Infrastructure Services: L2 transparent, switched, ETREE L3 routed Service enabled: Edge Provisioning only (no VLANs in core) Core Network Segmentation/ Virtualization enablement Highly Resilient IoT ready (IPv6) core Ready to extend Fabric further L2/IP User Access Distribution Fabric Extend over IP MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 22
LARGE ENTERPRISE NETWORK Option 3 User Distribution and Access Fabric Reasons to deploy a fabric in a Large Enterprise Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) End-to-End Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover Seamless IP Multicast IoT ready (IPv6) L2/IP User Access Distribution Fabric Extend Layer 2 MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 23
LARGE ENTERPRISE NETWORK Option 4 End-to-end Fabric over IP MAN/WAN Reasons to deploy a fabric in a Large Enterprise Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion traffic tromboning avoidance with DGW redundancy End-to-End Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover Seamless IP Multicast IoT ready (IPv6) L2/IP User Access Distribution Fabric Extend over MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 24
LARGE ENTERPRISE NETWORK Option 5 Leaf Fabric Layer Reasons to deploy a fabric in a : L2/IP subnet segment stretch Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion traffic tromboning avoidance with DGW redundancy Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover L2/IP OSPF w/ecmp User Access Distribution Fabric Extend over MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 25
LARGE ENTERPRISE NETWORK Option 6 Stretched Data Fabric Layer Reasons to deploy a fabric in a : L2/IP subnet segment stretch Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion traffic tromboning avoidance with DGW redundancy Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover L2/IP OSPF w/ecmp Fabric Connect Fabric Extend User Access Distribution Fabric Extend over MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 26
LARGE ENTERPRISE NETWORK Option 5 End-to-end Fabric Reasons to deploy a fabric in a Large Enterprise Network: Spanning Tree Replacement with Fabric Service enabled: Edge Provisioning only (no VLANs in core) Seamless WLAN roaming (FA) Server Integration Simplification with OVS on Linux Hypervisors and VPS with VMware Seamless vmotion traffic tromboning avoidance with DGW redundancy End-to-End Network Segmentation/ Virtualization enablement Highly Resilient multi-pathing w/ fast failover Seamless IP Multicast IoT ready (IPv6) User Access Distribution MAN/WAN Backbone Spine (L3) Access Leaf Servers 2016 Avaya Inc. All right reserved 27
CHALLENGES ARE ADDRESSED WITH A FABRIC SOLUTION Enabling Network Connectivity is not seen as a Service delivery Today s Enterprise networks are typically flat ; delivering network segmentation and virtualization is not straight forward Security = firewalling, firewalls become firewalls again. No longer used to enforce segmentation Provisioning network connectivity takes too long Loop free L2 topologies often require unreliable Spanning Tree Protocol Enabling a stretched solution for virtual machine migrations is a challenge Enabling seamless Wireless Roaming is a challenge IoT and IPv6? Making a non fabric network IPv6 ready is a large project. Security surveillance is typically handled by separate infrastructure why? 2016 Avaya Inc. All right reserved 28
Visit Our Smart City Expo Hours Monday, April 4 Tuesday, April 5 Wednesday, April 6 Thursday, April 7 6:30pm 9:00pm 7:00am 8:30am 7:00am 8:30am 7:00am 8:30am 12:15pm 1:30pm 12:15pm 1:30pm (Expo closes after breakfast) 6:00pm 8:00pm
Complete your survey at the end of the session in the Mobile App
2016 Avaya Inc. All right reserved 31