The following issues were resolved in ExtremeXOS 16.1.3-Patch1-4. ExtremeXOS 16.1.3-Patch1-4 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, and ExtremeXOS 16.1.3. For information about those fixes, see the release notes for the specific release.
Resolved Issues, Platform-Specific, and Feature Change Requests (CRs) for ExtremeXOS 16.1.3-Patch1-4
| CR Number | Description |
|---|---|
| General | |
| xos0056368 | Kernel errors occur after disabling sharing configuration on ISC ports of MLAG. For example: "exvlan: handleVsmKernelRequest:8545: handleVsmKernelRequest Invalid Ingress port: 1000008 got" |
| xos0061841 | FDB entries are not learned again after limit learning is unconfigured, and then configured again, with PSTAG configuration in SummitStacks. |
| xos0063082 | Updating DSCP value is not getting refreshed for Dynamic ACL. |
| xos0063463 | Static FDB created on PSTag VLAN port is incorrectly displayed in show configuration. |
| xos0063761 | Traffic not getting forwarded after disable/enable sharing when traffic ingressing port is part of both port specific tag (PSTag) and service VMAN (untagged port). |
| xos0063948 | Clearflow delta values are randomly not calculated properly. |
| xos0063968 | HAL process ends unexpectedly after changing/reverting service VLAN tag. |
| xos0064063 | Packet-Resolution match conditions need to be added as ACL match conditions. |
| xos0064067 | Traffic loss occurs in MLAG setup when ingress port and ISC port reside on different hardware unit and when internal port number for both these ports are same. |
| xos0064179 | MAC movement occurs in switch acting as an STP root bridge when PVST+ BPDUs are sent by peer switch using STP blocked port. |
| BlackDiamond 8800 Series Switches | |
| xos0063511 | Memory allocation failure messages appear with MSM-96 after failover: "MSM-B: RX: Failed to allocate mem, unit 0, chan 1 dv 0, i 15, rv -2" |
| BlackDiamond X8 Switches | |
| xos0063546 |
The following error message may appear when BlackDiamond X8 modules are rebooted after configuring port partition: Erro:Kern.Card.Error> Slot-2: _setSchedMode: u:p=1:006 schedMode=1 err=Invalid parameter |
| Summit X670 Series Switches | |
| xos0063263 | On Summit X670 series switches, 1000BaseSX optics are incorrectly detected as 100BaseFX. |
| Summit Family Switches | |
| xos0059831 | In Summit X670 and X770 series switches, the QSFP+ end of 10GB-4-F10-QSFP cable is incorrectly detected as non-Extreme certified. |
| xos0061506 | In Summit X440-G2 and X460-G2 series switches, the combo port comes up as active even though when link peer port is down. |
| xos0062700 | When upgrading from ExtremeXOS 15.7 or earlier to 16.1, image download fails if image was installed in backup node first and master node second. |
| xos0063548 | LX100 optics are not working on 10G ports. |
| xos0063919 | On standby nodes, IP ARP refresh and Neighbor refresh are now disabled on VR-Mgmt. Primary and backup nodes use the configured enabled/disabled setting. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB