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. 85
FA Zero Touch Provisioning
The main focus of Fabric Attach is to attach end users and applications or IoT devices to Fabric I-SID
services and in the examples covered above we have seen that this is achieved by either the FA Client or
the FA Proxy requesting service attachment to some L2 I-SID and VLAN pair towards the FA Server.
However, the same Fabric Attach LLDP mechanisms can also be leveraged to ease provisioning of FA
Proxy access switches and FA Client management connectivity in the reverse direction.
FA Server switches will typically be in a core/distribution role and from a provisioning perspective must
have already been deployed before any FA Proxy or FA Clients are connected to the network. Part of the
FA Server provisioning configuration will determine what FA management VLAN should be put in place
and advertised to attached FA Proxy and FA Client devices. In some cases, the FA Server will be acting as
default gateway for that management VLAN, while in other cases the FA Server will simply act as an L2VSN
BEB for accessing a fabric-wide management segment.
Note
In both cases, the FA Server will need to associate to a Fabric Attach enabled port a
management I-SID. This I-SID will be used to either map to a local platform VLAN where
an IP Gateway interface is created or it can simply be the I-SID of a fabric-wide L2VSN
management segment.
The Fabric Attach Element TLV optionally allows the FA Server to announce the management VLAN to
downstream FA Proxy switches and FA Clients. From Figure 44, note that only the management VLAN ID is
advertised by FA messages. This is because the corresponding I-SID for the management VLAN only has
significance on the FA Server and is of no use to FA Proxy or FA Client devices.
Figure 44 FA Signalling of Management VLAN from FA Server
The advertised FA management VLAN can take one of the possible values listed in Table 11.
In addition to the FA management VLAN, every Fabric Attach device is able to indicate whether the traffic
that it will transmit on its FA port is either all tagged, all untagged, or a combination of both tagged and
untagged using the Element TLV State field.
Table 11 – Fabric Attach Management VLAN ID Values
FA Mgmt
VLAN ID
Description of management VLAN
0
No management VLAN exist; the FA Server port was not configured with one.
1..4094
A tagged management VLAN exists and the FA Server will only accept q-tagged traffic for
it on the corresponding VLAN ID.
4095
An untagged management VLAN exist and the FA Server will accept untagged traffic for
it.