ExtremeXOS Feature Compatibility with V300 and V400 Virtual Port Extenders

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.

Table 1. ExtremeXOS Feature Compatibility with V300 and V400 Virtual Port Extenders
ExtremeXOS Feature Status
Ingress (first and second stage) and egress ACLs are supported with the following limitations:
  • Ingress ACLs applied to a list of extended ports results in one hardware rule per extended port. This is the same behavior as regular ports when counters and/or meters are used.
  • Egress ACLs applied to an egress port do NOT match L2 flood traffic, but egress ACLs applied to VLANs do.
  • Ingress ACLs with Replace-ethernet-destination-address action, replace-ethernet-source-address, and replace-vlan-id actions are not supported when packets are egressing extended ports.
  • L3/L4 match criteria are not available in the same egress ACL key as an extended port match.
  • ACL byte counters include an extra 8 bytes per packet (Ethertype + Etag) for the added encapsulation.
  • Egress ACLs applied to extended port LAGs are not supported. Use egress ACLs bound to VLANs/any instead.
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).
AVB Not supported.
BFD Supported, except on extended ports.
CFM Supported, except on extended ports.
Diffserv examination Supported.
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.
EDP/LLDP/CDP Supported.
Note: BPEs will not appear as EDP neighbors.
EEE Supported.
ELSM Not supported.
ERPS Supported, except that ERPS ring ports cannot be extended ports.
ESRP Not supported.
Fabric Attach
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.
HcLAG Not supported.
Identity Management Identity Management should not be enabled on cascade ports.
L2 PBR Not supported.
FDB: multi-port unicast entries Not supported.
L3: PBR 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.

L3 Tunnels

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, except for ExtremeSwitching the X695 series switch.

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:
  1. Run the command: enable mirroring to port-list 1:1 loopback 1:2. Where in this example, port 1:2 is not connected to anything.
  2. Run the command: configure mirroring add port 104:1. Where in this example, port 104:1 is the extended port.

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.
MPLS/VPLS Not supported.
Multicast: IGMP Supported.
Multicast: MVR Supported.
Multicast: PIM Supported.
Multicast: PIM Snooping Supported.
MVRP Supported.
Netlogin Dot1X and MAC Auth supported, and supported with MLAG.
Not supported:
  • Multi-supplicant (MAC-based VLANs) without ONEPolicy.
  • Port restart option.
  • Trusted ports.
WebAuth is not supported with MLAG.
Node Alias Supported.
Basic policy supported:
  • Policy scale (number of users, roles, rules) same as CB.
  • LAG rules not supported on extended ports with tci-overwrite.
  • Per-port, policy-driven, ingress rate limiting is not supported on extended ports.
  • ExtremeSwitching X695 series switches as CBs do not support tci-overwrite.
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".
PVLAN Not supported.
  • 8 queues per extended port.
  • Peak-rate supported per qosprofile per extended port.
  • CBS is 32 Kbytes.
  • Scheduling algorithms WDRR and strict priority.
  • Egress per-port rate limit per extended port.
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.
Not supported:
  • Committed-rate per qosprofile per extended port.
  • For V300, per-queue packet drop counters.
    Note: Neither show ports port_list qosmonitor {congestion} {no-refresh | refresh} {port-number} nor show ports port_list congestion {no-refresh | refresh}{port-number} increments when there is egress congestion on a V300 port. Instead, you can view egress congestion using show ports {port_list | stack-ports stacking-port-list} rxerrors {no-refresh | refresh} on the ingress port (upstream port in many cases).
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.
Software-redundant ports Supported.
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.
Note: VLAN flood traffic is not counted in the transmit counters; displayed counts include an additional 8 bytes for the Ethertype + E-tag encapsulation.
VMAN/CEP Not supported.
VMT/XNV Not supported.
VRRP Supported.

Supported for tagged and untagged tenant VLANs on extended ports.

Extended port LAG in VXLAN is not supported.

Extended ports cannot be in VXLAN network VLANs.

Extended ports cannot participate in RIOT configurations.

Ring is not supported for VXLAN extended ports.

Optimized IP Multicast Replication is not supported for VXLAN extended ports.