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. 42
then ensure that equal cost shortest path load balancing can be leveraged across the SPB Fabric to reach
the SMLT cluster BEB nodes.
Tip
The SMLT-Virtual-BMAC can be either auto generated or manually provisioned. If auto
provisioned, the system will simply use the SMLT’s Primary nodal BMAC with the least
significant byte set to 0x80.
Tip
Extreme recommends that the SMLT-Virtual-BMAC configuration should follow the same
criteria used for nodal BMAC / IS-IS System ID. If the latter is manually provisioned, then
so should the SMLT-Virtual-BMAC. If instead auto configuration is used, then both should
be allocated in that manner.
IS-IS Area
SPB operates in unison with IS-IS, which acts as a link state routing protocol for the Ethernet Fabric. IS-IS
needs to operate within a given IS-IS area and as such every SPB BEB or BCB node will need to be
configured with the same IS-IS area.
Note
The SPB standard only defines operation over a single IS-IS area.
Tip
Extreme Networks will support Multi-Area Fabric Connect in future. When Multi-Area
becomes available the IS-IS Area configuration will be leveraged by new functionality on
Multi-Area BEB nodes to interconnect services across different areas.
Note
The IS-IS area format is <AFI>.<AreaID>, where AFI is two hex digits and Area ID is four
hex digits. Extreme recommends to select SPB IS-IS area IDs 49.xxxx
5
where the AFI = 49
indicates locally administered NSAP addresses.
Tip
Extreme Networks VSP platforms can automatically assign the IS-IS area if deployed in
Zero Touch Fabric (ZTF) mode and are connected to an already existing SPB fabric.
IS-IS System ID
Like every IS-IS router, a BEB or BCB node must be allocated a unique IS-IS System ID. In the Extreme
Networks SPB implementation, the IS-IS System ID (six octets) also becomes the nodal BMAC of the SPB
node. Refer back to Backbone MAC Address on page 41.
5
For guidelines on allocating SPB unique identifiers refer to reference documentation
[8].