Restrictions and Limitations
The following list identifies TRILL feature limitations in ExtremeXOS
15.4:
- Multicast, flood, and broadcast traffic is limited to 6G per 240G packet processor.
- Multicast is not supported. All multicast traffic is transmitted over a single DTree.
- Only supports forwarding to one neighbor RBridge per port.
- No support for Hybrid TRILL VLANs. A VLAN must either be a TRILL network VLAN or an access
VLAN.
- Hybrid ports are not supported (though VLANs can have TRILL network ports and native 802.1Q
Ethernet ports in the same VLAN).
- On a transit Rbridge, the VLANs being transported still consume hardware resources
(multicast indices and FDB entries) if VLAN pruning is enabled, even if the VLAN is not present
on the transit Rbridge.
- Hitless failover high availability is not supported.
- TRILL is supported on the default VR only.
- Network recovery times are similar to other routing protocols, such as Open Shortest Path
First (OSPF).
- No Operations and Management (OAM) protocol (for example, Bidirectional Forwarding Detection
[BFD]) fault detection is provided— only link LoL and Hello timeouts.
- No RBridge TRILL peering authentication to prevent network spoofing.
- IGMP snooping must be disabled on access VLANs before they are added to
TRILL (disable igmp
snooping
vlan
vlan_name).
- MLAG and TRILL are not supported on the same VLANs/ports. Enabling MLAG for a different set
of VLANs/ports puts the entire switch in software learning mode, including TRILL FDB
entries.
- The following protocol features cannot be configured on a TRILL network VLAN:
- IP forwarding
- IP routing protocols
- IP multicast protocols
- MPLS
- ESRP
- Ring protocols (for example: EAPS, ERPS)
- MLAG
- Private VLANs
- VLAN translation
- VLAN aggregation
- VMANs
- VPLS
- VRR
- STP
- Customer edge ports (CEP)
- Multicast snooping
- Any type of tunneling (for example: GRE, IPv6-to-IPv4, IPv6-in- IPv4)
Print
this page
Email this topic
Feedback
View PDF
Download EPUB