The following issues were resolved in ExtremeXOS 30.6.1-Patch1-11. ExtremeXOS 30.6.1-Patch1-11 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, ExtremeXOS 12.7.1, ExtremeXOS 15.1.5, ExtremeXOS 15.2.4, ExtremeXOS 15.3.3, ExtremeXOS 15.4.1, ExtremeXOS 15.5.1, ExtremeXOS 15.5.2, ExtremeXOS 15.6.1, ExtremeXOS 15.6.2, ExtremeXOS 15.7.1, ExtremeXOS 16.1, ExtremeXOS 16.1.2, ExtremeXOS 16.1.3, ExtremeXOS 21.1, ExtremeXOS 22.1, ExtremeXOS 22.2, ExtremeXOS 22.3, ExtremeXOS 22.4, ExtremeXOS 22.5, ExtremeXOS 22.6, ExtremeXOS 30.1, ExtremeXOS 30.2, ExtremeXOS 30.3, ExtremeXOS 30.4, ExtremeXOS 30.5, and ExtremeXOS 30.6. For information about those fixes, see the release notes for the specific release.
| Issue Number | Description |
|---|---|
| xos0077879 | Static NSI bindings go into the pending state when dynamic binding with identical NSI is removed. |
| xos0078656 | FDB entries learned on NetLogin-enabled bridge port extender (BPE) ports point to CPU, causing traffic loss. |
| xos0078699 | On a configuration with Extended Edge Switching with MLAG, the setup becomes unstable when NetLogin is configured on bridge port extender (BPE) trusted ports. |
| EXOS-24243 | Extended Edge Switching (VPEX) process ends unexpectedly with signal 11 due to invalid cascaded port configuration. |
| EXOS-24242 | On a configuration with Fabric Attach and MLAG, failover times after a switch reboot are slightly increased, and need to be reduced. |
| EXOS-24137 | Convergence takes 6 seconds when port down/up coincides with optics polling interval (once in 300 seconds). |
| EXOS-24131 | Need a mechanism to bring up MLAG ports in a staggered manner. |
| EXOS-24123 | With an ExtremeSwitching X670-G2 SummitStack acting as a Fabric Attach proxies, you cannot create a VLAN with "v" in the name along with the system VLAN tag number. For example, if the system VLAN is "SYS_VLAN_0200", trying to create a VLAN named "v200" produces an error message stating that the VLAN already exists. |