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. 149
For user VLANs that need to be IP routed on the Distribution SMLT cluster, it is therefore necessary to
implement some form IP Gateway Redundancy on the IP interfaces of that VLAN on each switch forming
the cluster. It is also desirable that both nodes in the SMLT cluster can perform IP routing in tandem for
traffic that they receive from their own SMLT links, so that the active/active traffic forwarding enjoyed for
L2 flows translates into active/active forwarding for IP routed flows also.
Extreme Networks VSP series offers three deployment models to achieve this:
• Virtual Router Redundancy Protocol (VRRP) with Backup-Master extensions.
• Routed-SMLT (RSMLT) with Edge extensions.
• Distributed Virtual Routing (DVR).
Note
The VRRP and RSMLT options are supported with both IPv4 and IPv6. DVR is currently
only supported with IPv4.
VRRP with Backup-Master Extensions
VRRP is the IETF standard for IP Gateway Redundancy (RFC 3768 VRRPv2 for IPv4; RFC 5798 VRRPv3 for IPv4
and IPv6) whereby two or more IP routers can share a VRRP IP Gateway interface which at any given time is
active on the VRRP Router elected as Master. End user devices should be configured with the VRRP IP address
as default gateway.
The role of the VRRP elected Master is to:
(i) Generate VRRP Hellos.
(ii) Reply to ARP requests for the VRRP IP by providing the corresponding VRRP MAC address.
(iii) IP route traffic received with Destination MAC address the VRRP MAC.
Figure 87 SMLT with VRRP Backup-Master
Extreme Networks fully complies with the VRRP standard (both for IPv4 and IPv6 and supporting both
VRRPv2 and VRRPv3), but can enhance its operation on SMLT clustering by activating the Backup-Master
functionality. The Backup-Master functionality should be enabled on the VRRP instance of both switches
forming the SMLT cluster. One of the switches will naturally be elected as VRRP Master for the VRRP
instance, as per the standard. Backup-Master has no effect on the VRRP Master switch, which will continue
to perform all of (i), (ii) and (iii) listed above. Backup-Master will instead allow the VRRP Backup switch to
also take “ownership” of the VRRP MAC and thus to perform (iii) in tandem.