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. 86
Consequently, a freshly deployed wiring closet switch can automatically:
• Discover the FA Server.
• Become an FA Proxy device.
Tip
Extreme ERS and ExtremeXOS platforms operate in FA Proxy mode by default.
• Configure its uplink ports to the FA Server for VLAN tagging.
If a management VLAN is advertised by the FA Server, it can automatically:
• Create the management VLAN
• Assign the management VLAN on the uplink to the FA Server.
• Obtain an IP address via DHCP.
The objective is to ease deployment of the FA Proxy wiring closet switches which can be deployed with
minimal initial configuration (if not in factory defaults) and obtain their final configuration once discovered
and onboarded via Extreme Management Center.
Caution
Current FA Zero Touch Provisioning capability on FA Proxy devices (ERS and
ExtremeXOS) does not automatically create an MLT/LAG when the discovered FA-Server
is an SMLT cluster. In this case, only one of the uplinks will be used until the final config is
pushed down from the management station which will then have to include the MLT/LAG
config.
Caution
VLACP configuration, if in use on the FA Server ports, will also not be automated by FA. In
this case, it is necessary to pre-configure VLACP on the FA Proxy switch before it can
even communicate with the rest of the network.
Fabric Attach will also advertise the management VLAN to any attached FA clients, but whether or not this
information is used by the FA Client will depend on the FA Client type and the desired deployment model.
The scope of the management VLAN is to be able to access and manage all devices which are VLAN aware
and part of the network infrastructure. If the FA Client is an ExtremeWireless AP, it could make sense for
those APs to obtain their DHCP IP management addresses via the same management VLAN (which
remains separate from any other VLAN the AP uses for wireless users). Whereas if the FA Client is a video
surveillance camera, which typically uses a single untagged network connection, there is no use for a
management VLAN.
Tip
On Extreme ERS platforms it is possible to disable propagation of the FA management
VLAN towards the access ports. Hence the FA management VLAN can still be used by the
ERS (as it is advertised by the FA Server), but is not propagated to any FA Client devices.
Even in the case of an ExtremeWireless FA Client it may sometimes be preferred to let the APs obtain their
IP addresses via DHCP over a separate VLAN/IP subnet from the one being used by the FA Proxy wiring
closet switches (the latter typically have statically assigned IPs while APs always use DHCP).