Configuration Guide

Table Of Contents
©2021 Extreme Networks, Inc. All rights reserved
October 2021
61
either layer 2 or layer 3 networks. Hub and spoke plus mesh topologies are supported. Fabric extend is
supported natively as of release 5.0 for the VSP 8000 and VSP 7200 and with the ONA for the VSP 4000.
Please note the following with using Fabric extend:
Premier license is required on the VSP 4000, VSP 7200, and VSP 8000 for Fabric Extend
VSP 7200 and VSP 8000 support VXLAN Tunneling in hardware, no ONA is required
VSP 4000 does not support VXLAN Tunneling in hardware, hence an ONA is required to do the
tunneling
o
One ONA required per VSP 4000 where FE tunnels need to be terminated
Logical Interface Count per device or port:
o VSP 4450, VSP 7200, VSP 8000: 250
o VSP 4850: 24
Fragmentation and reassembly is required if IP MTU <1594 bytes
o
SPB over IP session headers and encapsulation results in an Ethernet MTU size of 1594
bytes
o
VSP 4000 + ONA combination is required for fragmentation and reassembly wherever FE
tunnels need to be terminated
o
Fragmentation and reassembly is done by the ONA
o
VSP 7200 and VSP 8000 do not support fragmentation and reassembly
Combining VSP 7200 and VSP 8000 with ONA is not supported
Tunnels can originate and terminate on any of the hardware combinations below if fragmentation
and reassembly is not a requirement:
o
(VSP 4000 + ONA), VSP 7200, and VSP 8000
Optional Fabric Extend Manager with Extreme Fabric Orchestrator can be used to manage tunnel
configuration in an FE-domain
Latency
Fabric Connect itself does not pose any stringent latency requirements on an NNI link. NNI links can stretch
thousands of miles across the globe, as long as the physical Ethernet or emulated Ethernet integrity is
guaranteed. IS-IS timers are typically very long (multi-seconds) thus, a link won’t time-out due to extended
distance between the NNI ports. If packet loss occurs on the Ethernet links, then application layers will have
to retransmit packets. If excessive packet loss occurs, then links might drop due to missed IS-IS hello
packets. The effect of latency on upper layers protocol and applications should be borne in mind.