The following are new open issues for supported features found in ExtremeXOS 30.7.
| Defect Number | Description |
|---|---|
| ExtremeSwitching X620 Series Switches | |
| EXOS-26182 | With 1G optic in fiber combo port, copper link does not become active when fiber link is removed. Issue does not occur when using 10G optics. |
| ExtremeSwitching X690 Series Switches | |
| EXOS-26640 | ExtremeXOS 30.7 disables auto active/standby by default when creating BGP auto-peering. To enable auto active/standby, use the following command after BGP auto-peering is created: delete mlag peer SYS_EASYLAG_OFF. |
| EXOS-26614 |
On ExtremeSwitching X695 series switches with more than 1,021 router interfaces and VRRP, IP traffic to the VRRP MAC might be dropped. Workaround: The first time VRRP is enabled on a VLAN, the number of router interfaces must be below 1,022 or above 1,022—not equal. You can view the current number of router interfaces using the command debug hal show ipv4Intf | include "L3 Interfaces". |
| ExtremeSwitching X670-G2 Series Switches | |
| EXOS-26651 | PTPv2 is not available for ExtremeSwitching X670-G2 series switches. |
| EVPN | |
| EXOS-26412 | Rebooting an MLAG peer in an EVPN environment causes an excessive length of time for convergence to occur. |
| EXOS-26729 |
With LACP in BGP/EVPN VXLAN configurations, missing FDB MACs/ARPs occur from a remote VTEP with the following log message on the remote VTEP: <Warn:BGP.UpdateMgr.RtNotAdvertLargeUpdtMsg> A route cannot be advertised because it is too large to fit into the maximum allowed size of a BGP UPDATE message. VR = <vr number> Destination address AFI/SAFI = 4587545 Destination address prefix =<7 32 bit Hex strings forming the BGP route prefix> Destination address prefix length = 216 Workaround: Do not configure a LAG port on more than:
Alternatively, you can avoid these limits using a static port share that does not specify the LACP protocol. Note: The LACP protocol is used if explicitly configured in the sharing commands.
The preceding limitations also apply to any MLAGs using an LACP-enabled port
share.
|
| FDB | |
| EXOS-26648 |
When you configure an explicit time using the configure time command, it might cause the switch to experience traffic loss or perform software forwarding instead of hardware forwarding. Workaround: Save, and then reboot, the switch. |
| VLAN | |
| EXOS-20311 | When changing RTEP tenant VLAN IP address, error messages occur. |
| EXOS-29579 | Unable to ping directly connected hosts on a specific VLAN due to a missing local route in the hardware. |