The following are limitations in ExtremeXOS system architecture that have yet to be resolved.
Defect Number | Description |
---|---|
General | |
EXOS-27922 | Beginning with ExtremeXOS 31.2, PTPv2 is not supported on X460-G2 and X670-G2 switches. |
EXOS-28479 | For ExtremeSwitching 5520 and 5420 series switches, inner tag dot1P is not examined with LAG. |
EXOS-29242 | Multihop EBGP sessions established over GRE tunnels configured in user VR do not appear when there are more than 5 sessions. |
ExtremeSwitching 5420 Series Switches | |
EXOS-28685 | Path MTU discovery and IP fragmentation does not work when a packet is L3 routed to a VPEX extended port on the ExtremeSwitching 5420 series switch controlling bridge platform. Other controlling bridges are not affected. |
EXOS-28964 | Due to limited RAM, the following warn logs are observed when attempting to
install a summit-arm image in a 5420 or 5420
stack:<Warn:EPM.Upgrade.State> Upgrade status Installation time may be greater than expected due to a lack of memory resources <Warn:HAL.Sys.Warning> Switch low on Memory. OS KBytes total 1002660 free 4992. This can occur normally during image upgrade. |
EXOS-29316 |
The ExtremeSwitching 5420 series XE ports default to Auto Negotiation=ON when a 1G optic is inserted. Workaround: To use a 1G optic in an ExtremeSwitching 5420 series XE port, run the configure ports <port_list> auto off speed 1000 duplex full command and save the configuration. |
EXOS-29327 | ExtremeSwitching 5420 series switch control plane CPU congestion, caused by
heavy CPU-bound traffic, results in unexpected and undesirable drops for some other
types of CPU-bound traffic. This can cause control plane learning or protocol
convergence issues. Workaround: Manually apply rate metering for traffic causing the CPU congestion to alleviate the resource contention. |
Extended Edge Switching | |
EXOS-29130 | GRE Tunnel IPv4 traffic software gets forwarded if extended port is used in the tunnel transport VLAN. |
SummitStacking | |
EXOS-28766 | A file system corruption occurs when a USB clone tar saved with ExtremeXOS
31.3 is used for cloning by an ExtremeXOS or earlier release. Workaround: Upgrade the device to ExtremeXOS 31.3 before performing the clone. |