Print
this page
Email this topic
Feedback
View PDF
Download EPUBOpen Issues
The following are new open issues for supported features found in ExtremeXOS 22.1.
Open Issues, Platform-Specific, and Feature Change Requests (CRs)
| CR Number | Description |
|---|---|
| General | |
| xos0065183 | Recreating a VPN VRF with same name after deleting it produces a BGP error. |
| xos0066006 |
When ICMP redirect is received and the new gateway ARP is not resolved, the
redirect route becomes valid and is used. This results in traffic being dropped.
This problem is more apparent when the redirection happens to a host on a
different subnet because ExtremeXOS enables IP ARP checking by default.
Workaround: Disable IP ARP checking for this foreign
redirect.
|
| xos0066067 | When a configuration file (.xsf) saved in ExtremeXOS 21.1 is run on ExtremeXOS 22.1, all the configured MAC lists, primary and secondary shared-secrets in RADIUS and TACAS, and NMS shared-secrets are replaced with empty strings. |
| ACL | |
| xos0064027 | Due to limitations in slice depth, Summit X460-G2 series switches cannot have 512 single-wide rules in a single slice, causing applications like policy to not attain full capacities. Consequently, Summit X460-G2 series switches are constrained to Summit X450-G2 rule limits. |
| NetLogin | |
| xos0065247 | Unauthenticated clients in NetLogin get DHCP IP address using NetLogin- authenticated VLAN when private VLAN is configured and clients are in isolated VLAN. |
| OVSDB | |
| xos0065008 |
OVSDB schema is not cleared when changing configuration and rebooting. Workaround:
In setups where OVSDB is used to manage and configure the ExtremeXOS switch as a VTEP, the VTEP schema database must be manually cleared using the command disable ovsdb schema when the active configuration of an ExtremeXOS switch is changed using the CLI command use configuration. Failure to do so might result in OVSDB using a stale VTEP schema database. |
| xos0065504 | The command show ovsdb schema can become unresponsive when either ExtremeXOS or OVSDB are synchronizing data. |
| xos0064657, xos0064656 |
switch_fault_status and port_fault_status are not set in the hardware_vtep schema. In ExtremeXOS 22.1, for switch_port_status and port_fault_status (PSTAG-like scenarios), EMS receives a log message. |
| SNMP | |
| xos0066062 | SNMP community strings that are stored as encrypted using the command configure snmp add community community_string readonly | readwrite store-encrypted do not work after you upgrade from an earlier version of ExtremeXOS to version 22.1. |
| xos0066070 | XSF scripts with encrypted communities and v3 users created with earlier
versions of ExtremeXOS do not work on ExtremeXOS 22.1. Additionally, after loading
the script, SNMP access remains disabled in ExtremeXOS 22.1, even if it was enabled
in an earlier version of ExtremeXOS. This occurs because SNMP is disabled by default
in ExtremeXOS 22.1 and enabled by default in earlier versions. Workaround: There are two possible workarounds:
|
| xos0066086 | User-defined SNMPv3 users do not work after upgrading to ExtremeXOS 22.1 if the SNMPv3 default-users were disabled using the command disable snmpv3 default-user in ExtremeXOS 21.1 or earlier. |
| SSH | |
| xos0066027 | After downloading certificates, the commands show ssl trusted-ca and show ssl ocsp-signature-ca fail to show any output. However, PKI validation that makes use of these certificates works. |
| xos0065712 | When repeated login and logout is performed using SSH-PKI (SSH login using certificates) for about two days from eight terminals, memory leak occurs. |