Network Virtualization using Extreme Fabric Connect
Table Of Contents
- Table of Contents
- Table of Contents
- Table of Contents
- Table of Figures
- Table of Figures
- Table of Tables
- Conventions
- Introduction
- Reference Architecture
- Guiding Principles
- Architecture Components
- User to Network Interface
- Network to Network Interface
- Backbone Core Bridge
- Backbone Edge Bridge
- Customer MAC Address
- Backbone MAC Address
- SMLT-Virtual-BMAC
- IS-IS Area
- IS-IS System ID
- IS-IS Overload Function
- SPB Bridge ID
- SPBM Nick-name
- Dynamic Nick-name Assignment
- Customer VLAN
- Backbone VLAN
- Virtual Services Networks
- I-SID
- Inter-VSN Routing
- Fabric Area Network
- Fabric Attach / Auto-Attach
- FA Server
- FA Client
- FA Proxy
- FA Standalone Proxy
- VPN Routing and Forwarding Instance
- Global Router Table
- Distributed Virtual Routing
- Zero Touch Fabric (ZTF)
- Foundations for the Service Enabled Fabric
- IP Routing and L3 Services over Fabric Connect
- L2 Services Over SPB IS-IS Core
- Fabric Attach
- IP Multicast Enabled VSNs
- Extending the Fabric Across the WAN
- Distributed Virtual Routing
- Quality of Service
- Consolidated Design Overview
- High Availability
- Fabric and VSN Security
- Fabric as Best Foundation for SDN
- Glossary
- Reference Documentation
- Revisions
Network Virtualization Using Extreme Fabric Connect
© 2019 Extreme Networks, Inc. All rights reserved. 157
routing domain end-point is provisioned (VRF/L3 VSN). The same is true when activating IP Multicast
within a service.
Tip
With MPLS architectures, the end-point provisioning goes only as far as the PE distribution
node and in no cases to the access switches. This is true for both IPVPN and VPLS service
types. In the case of Draft Rosen Multicast VPNs, the MPLS core will need to be PIM
enabled.
Indeed, in an Extreme Networks Fabric Connect architecture, if we assume that all the L3 VSN routing
domains are already in place, adding a new application or new user to the network can be completely
liberated by any human intervention on the network switches as users can be assigned to the correct L2
segment via identity based routing (RADIUS Authentication with Fabric Attach) and new VMs can be
automatically attached to the correct server VLAN by the network management automatic provisioning
software or Fabric Attach in the OVS software in the hypervisor.
Loop Detection and Protection Mechanisms
So far, we have covered how human error can have an impact on network provisioning when software
configuring the network devices and how Fabric Connect minimizes these risks. There is however another
important area which is prone to human errors and which is physical patching of cables, fibres and the
patch panels which both make use of. We will also include here human errors originating from personnel
configuring the server hypervisors in the data center, since these components have software-based
vSwitches within them which, if misconfigured, can ultimately lead to the same network failure conditions.
Figure 92 Loop Forming on Access VLAN
These failure conditions fall into two categories; both are very serious:
• Loops forming on access L2 VLANs. A full bridging loop will result in broadcast/multicast traffic
being looped around at the rate of the slowest link in the loop. With gigabit in the wiring closet