Resolved Issues in ExtremeXOS 21.1.5-Patch1-2

The following issues were resolved in ExtremeXOS 21.1.5-Patch1-2. ExtremeXOS 21.1.5-Patch1-2 includes all fixes up to and including ExtremeXOS 11.6.5.3, and earlier, ExtremeXOS 12.0.5, ExtremeXOS 12.1.7, ExtremeXOS 12.2.2-patch1-12, ExtremeXOS 12.3.6, ExtremeXOS 12.4.5, ExtremeXOS 12.5.5, ExtremeXOS 12.6.3, ExtremeXOS 12.6.5.2-Patch1-3, ExtremeXOS 12.7.1, ExtremeXOS 15.1.5.4-Patch1-9, ExtremeXOS 15.2.4.5-Patch1-5, ExtremeXOS 15.3.1.4-patch1-47, ExtremeXOS 15.3.5.2-patch1-10, ExtremeXOS 15.4.2.8, ExtremeXOS 15.5.5.2, ExtremeXOS 15.6.5, ExtremeXOS 15.7.3, ExtremeXOS 16.1.3, ExtremeXOS 21.1.1, ExtremeXOS 21.1.2, ExtremeXOS 21.1.3, and ExtremeXOS 21.1.4. For information about those fixes, see the release notes for the specific release.

Resolved Issues, Platform-Specific, and Feature Change Requests (CRs) in ExtremeXOS 21.1.5-Patch1-2

CR Number	Description
General
xos0070993	The STP port link-type configuration is not retained when a untagged port is deleted from a VLAN that is part of an STP domain and then added in another VLAN that is also part of the STP domain. This results in the port behaving like a normal STP port, even though the configuration appears in the output of the "show configuration stpd" command.
xos0071077	The "tag" match condition is not working with BGP routing policies.
xos0071222	Need a mechanism to suppress generation of IGMP-triggered queries when receiving STP topology changes.
xos0071340	In the output of show mvrp ports counters event command, MVRP LeaveAll Tx packets appear as Rx packets.
xos0071450	In the output of show ports command, the usual expression for excluding “0” entries is not working as expected.
xos0071468	In WMLAG, static MAC address of second peer is not flushed from FDB table during failures.
xos0071532	EDP process ends unexpectedly with signal 6 when receiving EDP packets with zero length on the TLV.
xos0071607	Memory leak for process hal occurs after executing command "debug hal show forwarding distribution".
xos0071654	Process netTools stops responding when CNAME record is present.
xos0071768	With two connected switches with one running ExtremeXOS and one running EOS, MSTI information is omitted from STP BPDUs sent by the ExtremeXOS switches.
xos0071869	PIM register policy allows unpermitted group address packets when the source is in the permitted list.
xos0071872	NetLogin process ends unexpectedly with signal 11 when processing multiple web authentication requests from the same client.
xos0071877	PTPv2 Layer 2 Sync-E packets are duplicated and therefore egress at twice the ingress rate.
xos0071912	When using "ipaddress" keyword for DHCP option 78, the DHCP ACK is sent with an incorrect value.
xos0071076	The command configure tacacs timeout does not take effect.
xos0071135	Service VMAN packets are being forwarded in slowpath after deleting VPLS instance.
xos0071686	Nettools process ends unexpectedly with signal 11 when same policy is applied as user ACL and UDP profile.
xos0071745	Multicast packets are dropped for some sources when the route to the source network changes.
xos0071862	Need ACL match condition to filter OSPF packet types.
xos0071965	ExtremeXOS switches send BPDUs with sender Bridge-ID when EOS switches are the root.
xos0070819	Information about PSU fan airflow direction needs to be added to the show power command.
xos0071730	BFD enabled warning message appears when BFD is re-configured, even though it is already enabled.
xos0071728	A few MPLS LSPs remain in down state after several link flap events in LSP path.
SummitStack
xos0071781	New BFD sessions created after stack failover remain in down/initial state if BFD flaps occur prior to failover.
xos0070018	In the command show checkpoint-data output, need to show IPML connection status between master and backup in a stack.
xos0071254	Login issues occur when using Telnet to connect to other slots from master node with RADIUS mgmt-access enabled.
xos0071783	STP process ends unexpectedly with signal 11 when disabling active link to trigger Backup root.
xos0071107	Uptime is reset after the first failover, but generally is not reset after subsequent failovers.