10/40GbE per port runs only in NO-FEC and Force mode (ignores user configuration)
10/40
-
-
+
Copper
Up to 3
30
10/40GbE per port runs only in NO-FEC and Force mode (ignores user configuration)
25
-
+
-
Optic
Up to 100
40
25GbE per port runs only in RS-FEC and Force mode (ignores user configuration). LR modules are supported only when the device supports RS-FEC with these modules
25
-
+
-
Copper
Up to 5
40
25GbE per port runs only in RS-FEC and Force mode (ignores user configuration). LR modules are supported only when the device supports RS-FEC with these modules
50
-
+
-
Optic
Up to 100
40
50GbE per port runs only in RS-FEC and Force mode (ignores user configuration)
50
-
+
-
Copper
Up to 5
40
50GbE per port runs only in RS-FEC and Force mode (ignores user configuration)
100
-
+
-
Optic
Up to 100
40
100GbE per port runs only in RS FEC and Force mode (ignores user configuration). LR4/BiDi/SWDM4 modules are supported only when the device supports RS-FEC with these modules
100
-
+
-
Copper
Up to 100
40
100GbE per port runs only in RS FEC and Force mode (ignores user configuration). LR4/BiDi/SWDM4 modules are supported only when the device supports RS-FEC with these modules
200
-
+
-
Optic
Up to 30
60
Mellanox to Mellanox only
200
-
+
-
Copper
Up to 2
60
Mellanox to Mellanox only
SN3800 Supported Speeds
Speed [GbE]
AutoNeg NO FEC
Force RS FEC
Force NO FEC
Cable
Cable Length (m)
Link up time (sec)
Limitations
10
-
-
+
Optic
Up to 100
20
10
-
-
+
Copper
Up to 5
20
25
-
+
-
Optic
Up to 100
60
25
-
+
-
Copper
Up to 5
60
50
-
+
-
Optic
Up to 100
60
50
-
+
-
Copper
Up to 5
60
100
-
+
-
Optic
Up to 100
60
100
-
+
-
Copper
Up to 5
60
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. 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