ExtremeXOS Feature Compatibility with V300 and V400 Virtual Port Extenders shows which ExtremeXOS features are supported, or are not supported, or that have limitations when used with V300 and V400 Virtual Port Extenders.
Ingress (first and second stage) and egress ACLs are supported with the following limitations:
Note: When installing ACL rules bound to a set of ports, rules are replicated for each port if there are ACL counters and counter compression is not enabled or if the ports are extended ports.
Note: You can consume an excessive number of ACLs if you bind them to each individual (extended) port in cases where you have many extended ports. To avoid this, consider policy (role-based assignments per user) for access-control (see Policy Roles), ACLs bound to VLANs, wildcarded applications (see Configuring the ACL Rule on the Interface ), or two-stage ACLs (see Two-Stage ACL).
|BFD||Supported, except on extended ports.|
|CFM||Supported, except on extended ports.|
|Disable slot||Not supported.
Note: You can take a BPE slot offline by disabling the corresponding cascade port(s).
|Dot1p examination||Disabled by default on extended ports; enabled by default on controlling bridge cascade ports. Use cascade port Dot1p examination for extended port traffic to conserve ACL hardware resources.|
|EAPS||Supported, except that EAPS ring ports cannot be extended ports.|
Note: BPEs will not appear as EDP neighbors.
|ERPS||Supported, except that ERPS ring ports cannot be extended ports.|
ExtremeXOS Fabric Attach (FA) supports FA servers and FA Proxies to be Extended Edge Switching controlling bridge (CB) nodes connected with bridge port extenders (BPEs) in two different topologies:
|FDB: Limit learning||Supported.|
|FDB: MAC lockdown||Supported.|
|FDB: Static and blackhole entries||Supported, except that multi-port unicast FDBs entries are not supported.|
|Flood rate-limit||Not supported on extended ports.|
|Identity Management||Identity Management should not be enabled on cascade ports.|
|L2 PBR||Not supported.|
|FDB: multi-port unicast entries||Not supported.|
|L3: Gateway routers||Gateway router connected to extended port LAGs is not supported.|
|L3: IP unicast forwarding||Maximum gateways (using configure iproute sharing max-gateways max_gateways ) must be greater than or equal to the number of active extended LAG members.|
|L3: Routing protocols||
Supported on CB; not supported on extended ports.
Supported on CB ports.
Not supported on extended ports.
The default and only supported algorithm on extended port LAGs is "custom."
|V300 Virtual Port Extender LEDs||Supported. For information about the location of BPE LEDs, see the V300 Virtual Port Extender Quick Reference Guide.|
|V400 Virtual Port Extender LEDs||Supported. For information about the location of BPE LEDs, see the V400 Virtual Port Extender Quick Reference Guide.|
Mirroring extended ports is supported.
Mirroring to extended ports is supported on all Universal platforms.
Ingress mirroring of an extended port will include an 802.1BR E-tag.
Note: Workaround: You can avoid this 802.1BR E-tag by doing the following:
Mirroring to BPE cascade ports is not supported.
Limitations: Only known traffic to extended ports can be egress mirrored.
|MLAG||Supported on cascade ports; not supported on extended ports. Not supported on cascade ports when in stacking mode.|
|Multicast: PIM Snooping||Supported.|
|Netlogin||Dot1X and MAC Auth supported, and supported with MLAG.
Not supported:WebAuth is not supported with MLAG.
Basic policy supported:
|PoE||Supported on select BPE models. See Supported Bridge Port Extender Models. Operator limit configuration is not
supported on cascade ports.
Note: The V300-8P-2T-W model is both a powered device (PD) and power supplying equipment (PSE). For information about its power output, see the ExtremeSwitching Hardware Installation Guide for Switches Using ExtremeXOS Version 30
|Ports: Flooding||Disabling flooding is supported.|
|Ports: Jumbo frame||
Enabling/disabling jumbo support on extended ports is supported; cascade-ports default to jumbo enabled.
For V300, only 1522, 2048, 10240 sizes are supported. Configuring jumbo frame sizes other than those values results in the next larger frame size being used for ingress; an egress filter enforces the MTU based on the actual jumbo size for the egress port.
The max-frame-size on V400 is enforced only on ingress, and not on egress. The V300 enforces on both ingress and egress.
|Ports: Learning||Disabling/enabling learning supported.|
|Ports: Statistics||On V300 ports, show port packet displays all packets 1024+ as "1024-1518". The "Jumbo" column is always "0".|
Note: For V300, all queue shapers are disabled on a port if either of the two highest priority queues are in weighted round robin (WRR) on that port.
Note: Dot1p examination is enabled by default on cascade ports, but disabled by default on extended ports.
Note: When using hyrbid QoS scheduling, strict-priority queues must be the highest number queues.
|Restart port||Not supported on extended ports. Use disable/enable port commands.|
|sFlow||Supported: sFlow hardware sampling on Extended Edge Switching extended ports is provided by the underlying Extended Edge Switching cascade port hardware. As such, the configured sample rate is programmed on the cascade port and is provided in aggregate to all subtended sFlow-enabled Extended Edge Switching extended ports.|
|STP||Supported, primarily for edge loop detection (edge guard); supported with MLAG redundancy for RSTP and MSTP protocol modes.|
Supported; users specify VLAN membership using <slot>:<port> notation; protocol VLANs not supported.
|VLAN: statistics||Supported on extended ports.|