The following are new open issues for supported features found in ExtremeXOS 22.5.1-Patch1-9.
Open Issues, Platform-Specific, and Feature Change Requests (CRs)
| CR Number | Description |
|---|---|
| ExtremeSwitching X620 Series Switches | |
| xos0070048 | When reverting from failover back to master in stack, on FHR router with static
entry added on LHR, the following errors
appear:11/08/2017 03:45:00.68 <Erro:HAL.IPv6Mc.Error> Slot-1: Unable to Add IPmc vlan 20 for 1:3 s,G=2001:0011:0000:0000:0000:0000:0000:0002,ff07:0000:0000:0000:0000:0000:0000:0001 IPMC 1, unit 0 Entry not found 11/08/2017 03:45:04.74 <Erro:HAL.IPv6Mc.Error> Slot-1: Unable to Del IPmc vlan 20 for 1:3 s,G=2001:0011:0000:0000:0000:0000:0000:0002,ff07:0000:0000:0000:0000:0000:0000:0001 IPMC 1, unit 0 Entry not found |
| ExtremeSwitching X690 Series Switches | |
| xos0071218 | On ExtremeSwitching X690-48x switches, the flow control appears as "None" for the first 8 ports. |
| xos0071226 | RIOT support for the ExtremeSwitching X690 series switches reduces the ECMP group limit by half for maximum gateway settings. See Supported Limits for Edge License. |
| BGP Auto-peering | |
| xos0070932 | With BGP auto-peering and VXLAN setup, traffic is not forwarded to some RTEPs, when back-to-back ECMP links are connected. |
| Extended Edge Switching | |
| xos0068764 | Enabling EAPS master on primary extended port with multiple VLANs (~300 protected VLANs for EAPS Domain), high EAPS convergence time occurs. |
| xos0071958 |
Loading a script with a configuration that enables sharing on a cascade port
causes the command to fail if the BPE slot is detected before sharing is applied
on the cascade port.
Workaround: Disable all the
ports, load the configuration script, and then re-enable the ports.
|
| xos0072214 |
In MLAG scaled configuration, with broadcast traffic flowing between CB and extended ports, ISC link flaps may cause tier 2,3, and 4 BPEs CSP sessions to go down. BPEs do not recover automatically. Workaround: To recover, reboot the controlling bridge, or disable, and then
enable, the CB's native cascade ports.
|
| VXLAN | |
| xos0072043 |
On an unconfigured switch, adding a static route by a VXLAN tunnel with traffic
flowing may cause a warning message in the log. The condition is harmless and can
be ignored. There will be about a dozen messages in the log, with the main
identifying message being similar
to:
WARNING: CPU: 0 PID: <XYZ> at kernel/softirq.c:146 __local_bh_enable_ip+0x7a/0xa0() Workaround: Save the configuration, and then reboot.
|
Print
this page
Email this topic
Feedback
View PDF
Download EPUB