Skip to content

1.0 Release notes

Steven Noble edited this page Dec 14, 2020 · 7 revisions
Table of Contents
  1. Supported Platforms
  2. Supported Firmware
  3. Supported Cables
  4. New Features
  5. Fixed Issues
  6. Known Issues

Supported Platforms

Product Description
Delta Networks TN48M Alleycat 3xTM based 1G 1U Open Ethernet Switch, 48 1G RJ45 and 4 10G SFP ports
Delta Networks TN48M-P Alleycat 3TM based 1G 1U Open Ethernet Switch, 48 1G RJ45 PoE and 4 10G SFP ports
Delta Networks TN4810M Aldrin 2TM based 10G 1U Open Ethernet Switch, 48 10G SFP ports
Delta Networks TX4810 SpectrumTM based 1G 1U Open Ethernet Switch, 48 10G SFP ports
Edge-Core AS4224-T Alleycat 3xTM based 1G 1U Open Ethernet Switch, 48 1G RJ45 and 4 10G SFP ports
Edge-Core AS4224-P Alleycat 3xTM based 1G 1U Open Ethernet Switch, 48 1G RJ45 PoE and 4 10G SFP ports
Edge-Core AS5114 Aldrin 2TM based 1G 1U Open Ethernet Switch, 48 10G SFP ports
Mellanox SN2410 SpectrumTM based 25GbE/100GbE 1U Open Ethernet Switch, 48 SFP28 ports, 8 QSFP28 ports

Supported Firmware

Spectrum mellanox/mlxsw_spectrum-13.2008.1160 - Available via linux-firmware.

NOTE: mlxsw driver enforces earlier version 13.2007.1168. It is recommended to update it manually.

Spectrum-2 mellanox/mlxsw_spectrum-29.2008.1160 - Available via linux-firmware.

NOTE: mlxsw driver enforces earlier version 29.2007.1168. It is recommended to update it manually.

Spectrum-3 mellanox/mlxsw_spectrum-30.2008.1160 - Available via linux-firmware.

NOTE: mlxsw driver enforces earlier version 30.2007.1168. It is recommended to update it manually.

Supported Cables

For a list of the Mellanox supported cables please visit the LinkXTM Cables and Transceivers page.

New Features

NOTE: For releases earlier than 4.19 please visit 5.2 release notes page.

Kernel Category Description
1.0 Control Plane Policing (CoPP): Quality-of-Service
TC pedit TCP / UDP sport / dport: ACL
SN4600C in GA Fully certified SN4600C

Fixed Issues

Category Description Commit info
mlxsw: spectrum Adjust headroom buffers for 8x ports details
mlxsw: spectrum_router Remove inappropriate usage of WARN_ON() details
mlxsw: pci Fix use-after-free in case of failed devlink reload details
mlxsw: core Fix wrong SFP EEPROM reading for upper pages 1-3 details
mlxsw: core Increase scope of RCU read-side critical section details
mlxsw: core Free EMAD transactions using kfree_rcu() details
mlxsw: spectrum_router Fix use-after-free in router init / de-init details

Detla TN_XXYYZZ Supported Speeds

Speed [GbE] AutoNeg Force RS FEC Force FC FEC Force NO FEC Cable Cable Length (m) Limitations
100(4x) + + + + Optic Up to 100
100(4x) + + + + AOM Up to 80km
100(4x) + + + + Copper Up to 5
25/50(2x) + + + + Optic Up to 100
25/50(2x) + + + + AOM Up to 10km
25/50(2x) + + + + Copper Up to 5
10/40 + - + + Optic Up to 100
10/40 + - + + AOM Up to 80km
10/40 + - + + Copper Up to 5
1 + - - + Optic Up to 100
1 + - - + Copper Up to 5

Known Issues

Category Description
Network configuration Order of operations: Network configuration should be done bottom-up, teardown should be done top-down
ACL ACL key size: Rules that match on L2 fields and the complete IPv6 header cannot be specified
Multicast snooping MDB records mapped to the same multicast MAC will share the same MDB record in the device.
Deleting such records from the bridge driver will result in the following error being printed to the kernel log: "Unable to remove port from MC DB"
FRR FRR 7.3+ installs routes using nexthop objects which are not supported by mlxsw, causing it to reject the routes. This can be fixed by the command no zebra nexthop kernel enable. The command is available in FRR 7.3.1 onwards. See this ticket for more details
Routing When deleting an IP neighbour from user space, the neighbour transitions to FAILED state instead of being deleted completely. The neighbour is correctly deleted from the hardware data path and not marked with offload keyword. It can be deleted completely by issuing the deletion command again
Spectrum-2 Currently raising the link at 10/40Gb/s link speed is not supported when using 200Gb/s optical cables
SN3800 Split 4x25GbE not supported
SN3800 Cisco Bidi module is currently not supported
SN3800 Link is down after a few link toggles when using the MMA1B00-C100D 100G transceiver
SN3800 InfiniBand optical cables are currently not supported
SN3800 Currently raising the link at 25Gb/s / 100Gb/s link speed is not supported when using 200GbE copper cables
SN3800 Connectivity to a 3rd party switch systems may not go up when using copper and optical cables
SN3800 Traffic can be dropped due to high BER in link. Workaround: toggle the link
SN3800 High effective BER occurs when using optical and copper cables with 100GbE link speed
SN3700 At 200GbE speed, traffic drop occurs between SN3700 and IXIA
SN3700 200GbE optical cables are not supported
Packet Drops Monitoring Drop monitor needs to be built as built-in (CONFIG_NET_DROP_MONITOR=y) in order to report hardware drops