The following are limitations in ExtremeXOS system architecture that have yet to be resolved.
Known Issues, Platform-Specific, and Feature Change Requests (CRs)
| CR Number | Description |
|---|---|
| General | |
| xos0062115 | For ExtremeSwitching X440-G2 and X620 series switches, Dot1p is not set properly in the CVID translated packet. |
| xos0062068 | For extremeErpsRingNodeType, node type of RPL Neighbor returns value "nonRplOwner" for SNMP get. |
| xos0062131 | In VMANs, CEP port does not transmit ELRP packets, unlike untagged/tagged ports. |
| xos0062466 | For ExtremeSwitching X440-G2 and X620 series switches, VLAN traffic is not dropped if the port is classified both as VLAN tagged and VMAN CEP port. However, Dot1p value is set to "0" in egress for all priorities in VLAN traffic. |
| xos0062119, xos0063047 | For ExtremeSwitching X440-G2 and X620 series switches, "qosmonitor congestion counter" for egress port does not appear in the output of the show ports qosmonitor congestion command when a port list is specified, instead of a single egress port. |
| xos0063413 | In Chalet, when switching between earlier versions of
ExtremeXOS and version 21.1, the Apps tab does not appear. Workaround: Reload the web page or clear the cache.
|
| SSH | |
| xos0063327 | If a switch is downgraded from ExtremeXOS 21.1 to previous releases, with RSA key saved, the key becomes invalid. |
| VXLAN | |
| xos0060213 | Same port cannot be a part of network as well as tenant VLANs. |
| xos0063148 | Rate-limit actions do not work when the port is added as VXLAN tenant on VLAN ports. |
| xos0059594 | Egress mirroring of VXLAN traffic is not supported. |
| xos0059464 |
With no network ports configured and the switch receives VXLAN traffic from the access VLAN side, traffic is sent to the CPU, causing high BCMRx usage (around 50%), which in turn affects other parts of the system, such as OSPF (neighbor flap), pings etc. The frames are going to the CPU because they have the MAC DA and Destination IP address of the local switch. This behavior is no different than if the switch were a non-VXLAN-capable switch. By default all ports can terminate VXLAN traffic. If network ports are deleted with configure virtual-network delete network ports portlist any VXLAN traffic on these ports is sent to the CPU. |
| xos0062919 | With VXLAN configuration, after rebooting the following
error
appears:<Erro:HAL.IPv4Mc.GrpTblFull> IPv4 multicast entry not added. Hardware Group Table full. |
| Summits and ExtremeSwitching Series Switches | |
| xos0063046 | On ExtremeSwitching X440-G2 and Summit X460-G2 series switches, for the 1G combo ports if fiber is the preferred medium and a copper cable is inserted, and then a fiber cable is also inserted, the link switches from copper mode to fiber mode, and a link flap occurs. |
| Summit X460-G2 Series Switches | |
| xos0062225 | For Summit X4460-G2 switches, when HwBFD session is enabled, configuring authentication is ineffective (session stays up despite a password mismatch between the neighbors). |
| Summit X670-G2 Series Switches | |
| xos0062486 | For Summit X670-G2 series switches, configuring overhead bytes using configure forwarding rate-limit overhead-bytes does not work with egress ACL meter. |
| SummitStack | |
| xos0062687 | For Summit X450-G2 and X620 SummitStacks, after stack
reboots, the following error message
appears:<Warn:DM.Warning> Slot-2: mcmgr cannot write msg_id 5 to MASTER connection 0 This error can be ignored. No functional problem has occurred. |
| xos0066970 | In the output of the show fan command, the fan tray revision and part number appears only for first fan tray in stack. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB