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. 90
Tip
In the Extreme Networks Fabric Connect SPB implementation, each BEB reserves I-SIDs in
the range 16,000,001 – 16,600,000 for IP Multicast streams. Each allocated I-SID in that
range defines one unique IP Multicast stream (1 Group address + 1 Source IP address)
rooted at that BEB node. I-SIDs in that range are not allowed for use when creating L2
VSNs or L3 VSNs.
Note
The same I-SID, say 16,000,001, on different BEBs designates a completely different IP
Multicast tree, which could well have been dynamically assigned to a different multicast
group address and even to a different VSN.
Tip
The same Group Addresses (as well as Source IP addresses) can be reused in different
VSNs.
The BEB will then IS-IS announce to the Ethernet Fabric the existence of the IP Multicast stream using an IP
Multicast TLV containing the above-recorded information.
Figure 45 IP Multicast with SPB