Specifications

Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.4 Release Notes
85
Resolved Issues in ExtremeXOS 12.4.2-patch1-10
The following issues were resolved in ExtremeXOS 12.4.2-patch1-10. ExtremeXOS 12.4 includes all fixes
up to and including ExtremeXOS 11.1.4.4, ExtremeXOS 11.2.3.3, ExtremeXOS 11.3.4.5,
ExtremeXOS 11.4.4.7, ExtremeXOS 11.5.2.10, ExtremeXOS 11.6.5.3, ExtremeXOS 12.0.5,
ExtremeXOS 12.1.5, ExtremeXOS 12.2.2, and ExtremeXOS 12.3.6. For information on those fixes, see the
release notes for the specific release.
Summit Family Switches
PD4-1408048258 If stacking is enabled on a Summit X480 switch, MPLS commands are not supported in
ExtremeXOS 12.4. If the switch is a standalone system, MPLS is supported. This limitation
applies to ExtremeXOS 12.4 software only.
ACL
PD4-1825834531,
PD4-1809345751
The HAL process dies with signal 11 if the refresh policy fails and the following error is
displayed.
Unable to find the flow redirect used with the redirect-name
keyword, policy not installed
ESRP
PD4-464792522 A load-shared port in a host attach configuration is deleted without a warning or error
when sharing is disabled on the port.
Table 49: Resolved Issues, Platform-Specific and Feature PDs
PD Number Description
General
PD4-1738654737,
PD4-1738654681
ExtremeXOS software does not correctly recognize the following mini-GBIC modules:
• 100FX/1000LX dual speed SFP, part number 4050-00020-02
• 100FX SFP, part number 4050-00030-03
PD4-1695304439 After configuring an EMS xml-notification target, the name of the target is not included in
the output of the show configuration command.
Summit Family
PD4-1519936031,
PD4-1179290841
A kernel-error and reboot loop error occurs when upgrading a switch from ExtremeXOS
12.3.3.6 to ExtremeXOS 12.4 when an ACL is configured as a super VLAN.
PD4-1679170868 On a Summit X480 switch, the system watchdog may reboot if the disable iproute
sharing and enable iproute sharing commands are run in quick succession with
an excessive number of BGP routes (more than 512,000) installed in the routing table.
The system may also experience a BGP process crash if the disable bgp and
enable bgp commands are run in quick succession using an excessive number of
BGP routes (more than 300,000) installed in the routing table.
Workaround: Allow 5 minutes between running the disable and enable commands if
these commands are run in succession.
Table 48: Resolved Issues, Platform-Specific and Feature PDs (Continued)
PD Number Description