Resolved Issues in ExtremeXOS 22.7.1-Patch1-17

The following issues were resolved in ExtremeXOS 22.7.1-Patch1-17. ExtremeXOS 22.7.1-Patch1-17 includes all fixes up to and including ExtremeXOS, 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, and ExtremeXOS 22.7. For information about those fixes, see the release notes for the specific release.

Table 1. Resolved Issues, Platform-Specific, and Feature Change Requests (CRs) in 22.7.1-Patch1-17
CR Number Description
xos0077144 After applying web access profile, the error log message "<Erro:cm.sys.LoadApplCfgObjFail>" appears after rebooting.
xos0076885 HTTPS sessions persist in "CLOSE_WAIT" state resulting in web access issues.
xos0077100 Switch fails to send tech-support data to collector after reboot.
xos0077094 Switch incorrectly defers sending tech-support data at the configured interval in some scenarios.
xos0075415 Inactive IPv6 static routes are moved to active after a reboot in BFD strict mode.
xos0075117 The command enable iproute bfd strict needs to display "require reboot" information message.
xos0074298 Static routes become active even though BFD session is not yet established after a reboot resulting in traffic loss.