The following are new open issues for supported features found in ExtremeXOS 21.1.5-Patch1-5.
CR Number | Description |
---|---|
General | |
xos0067463 | Traffic does not distribute across LSPs and LAG after enabling L2VPN sharing feature. |
xos0062584 | The command configure web http access-profile is missing the option access-profile. |
xos0062966 | When rendezvous point receives (*, G) join, and it has
(S, G, RPT) entry, the entry should be converted to (S, G), and (S, G) join should
be sent upstream. However, sometimes wrong assert is triggered and this new entry is
dropped after a minute, resulting in complete traffic loss. Workaround: Disable, and then
re-enable PIM.
|
xos0063247 | Duplicate packets occur during MLAG link recovery when LACP is used for load sharing. |
xos0063396 | While enabling 1G links, unexpected link-down PDU is received in EAPS master. |
xos0048715 | IPv6 ECMP works for hardware-forwarded traffic, but does
not work for slow-path traffic. Workaround: Either use BFD to keep all router neighbors alive, or
configure static neighbors and static FDB entries for all router neighbors. BFD is
the preferred method.
|
xos0062399 | IPv6 BFD session for OSPFv3 flaps after disabling, and then enabling VLAN port. |
SummitStack | |
xos0062386 | With BGPv6, after port flap or failovers, some peers go into idle state. |
xos0061909 | Creating an IPFIX mirroring instance to a monitor port,
deleting the mirroring instance, and then recreating it again to a different monitor
port, causes the following error message (similar to the one below) to appear, and
IPFIX mirroring does not
work:<Erro:HAL.Mirror.Error> Slot-1: Failed to create mirroring destination for slot 2, unit 9 Entry exists Workaround: If the error appears in
the log, disable and delete the mirror instance, and then add it back
again.
|
ExtremeSwitching X620 Series Switches | |
xos0062636 |
Unexpected link switchover behavior occurs when exchanging
copper and fiber cables on ExtremeSwitching X620 combo ports.
Workaround:
|
xos0062620 | For ExtremeXOS 21.1, do not use copper DAC cables for stacking on ExtremeSwitching X620-16T switches. |
Summit X670-G2 Series Switches | |
xos0063170 | On Summit X670-G2 series switches, greater EAPS convergence time occurs with multiple VLANs (1,000 protected VLANs). |
xos0063492 | When a 1G port (SX/BASET) is used as a loopback port for mirroring to a port-list, the port does not come back to active state after disabling mirroring. |
Summit X460-G2 Series Switches | |
xos0063811 | Summit X460-G2 series switches with ExtremeXOS 15.6 through 21.1, have the
following limitations for SyncE input reference frequency:
|
xos0063412 | CFM fault not detected locally after disabling CCM for hardware Down MEP. |
ExtremeSwitching X440-G2 Series Switches | |
xos0062236 | EEE becomes disabled on combo ports after peer ports are disabled, and then enabled. |
xos0062773 | After switch boot up or restart of process dot1ag, 95% CPU utilization occurs with 32 UP MEPs (maximum value). |
xos0062895 | On ExtremeSwitching X440-G2 stack, process nettools
fails to start after rebooting with DHCPv6 client enabled. Switch reboots repeatedly
and reports the following errors:
10/20/2015 11:31:06.45 <Erro:EPM.crash_rate> Slot-1: Process netTools exceeded pre-configured or default crash rate 10/20/2015 11:31:06.45 <Erro:DM.Error> Slot-1: Process netTools Failed 10/20/2015 11:31:06.45 <Erro:DM.Error> Slot-1: Process netTools Failed 10/20/2015 11:31:06.45 <Erro:DM.Error> Slot-3: Node State[4] = FAIL (Not In Sync) 10/20/2015 11:31:06.46 <Erro:DM.Error> Slot-1: Node State[4] = FAIL (Process Failure) 10/20/2015 11:31:06.61 <Crit:NM.NodeStateFail> Slot-1: Slot-3 has failed for the reason of "Not In Sync". |
xos0062899 | DHCPv6 client remains in initializing state after
disabling, and then enabling, the port in the relay switch. Workaround: Restart process nettools, or disable,
and then enable, DHCP client.
|
xos0063678 | In ExtremeSwitching X440-G2 stack, rebooting backup slot
with CFM 32 Down MEP configuration times out with the following
errors:Error: This command is not permitted on nodes that are not active 02/16/2016 15:16:34.06 <Warn:HAL.Stacking.Warning> Slot-1: Timed out waiting for 1 reboot replies. 02/16/2016 15:16:34.06 <Warn:HAL.Stacking.Warning> Slot-1: Timed out waiting for 1 reboot replies. |
Summit X450-G2 Series Switches | |
xos0063008 | In Summit X450-G2 stack with mirroring configuration, boot up times out (after 300 seconds) while waiting for configuration checkpoint save operation to finish (FDB is still not saved). |
BGP | |
xos0060641 | When BGP is administratively shut down, it does not send notifications to peers. |
xos0063778 | If an applied BGP import policy is edited such that previously permitted routes are now denied, the BGP RIB (show bgp routes command) still shows the newly denied route(s) as active. The routing table is, however, updated correctly to reflect the new policy. |
xos0063698 | A BGP route is not replaced in the routing table by a new instance of the same prefix and length containing a different metric value. This condition can occur if an applied BGP import-policy file is edited to modify the route metric. |
MPLS | |
xos0062996 | VPLS: Traffic is not forwarded to service port
(VLAN-tagged port) when CEP egress filtering is enabled on it. Workaround: Disable CEP egress
filter.
|
NetLogin | |
xos0062680 | Switch fails to send Radius accounting message for dot1x user after clear netlogin state port <portNumber> command. |
Optics | |
xos0062092 | For Finisar LX-SFP optics, RxPower appears as "inf" instead of displaying correct value in the output of the show port transceiver information detail command. |
SNMP | |
xos0062492 | Traps having tabular variables as varbinds should include the instance along with the tabular OID. |
xos0062523 | SNMP traps for overheat and negative temperatures incorrectly report detected problems. |
xos0062525 | extremeEdpNeighborAdded/extremeEdpRemoved traps varbinds need to include the instance along with the OID. |
xos0062527 | The varbinds of extremePowerSupplyGood, extremePsuPowerStatus traps need to include the instance along with the OID. |