Skip to content

Dell s6010-on 40gb switch LED failures when ports are configured as fanout #74

@ballisox

Description

@ballisox

Issue:
Dell s6010-on 40gb port LEDs remain off / do not activate when configured as fanout.

openswitch version 3.1 Dev 2

Steps to reproduce:

  1. On the s6010-on 40gb switch, execute command: sudo opx-config-fanout e101-028-0 4x1 10g
  2. Port e101-028-0 will be successfully deleted.
  3. Ports e101-028-1, e101-028-2, e101-028-3, e101-028-4 will successfully created.
  4. Using the dell compatible 40gb QSFP+ to 4x10 SFP+ Breakout Active Optical cables, connect the 40gb transceiver to the fanout configured port.
  5. Connect the 10gb transceivers to any 10gb device that can establish a 10gb link and ensure the device and switch ports are configured to transmit and receive traffic.
  6. Run opx-ethtool against the fanout configured ports on the switch.

opx-ethtool results should look similar to this:

Settings for e101-028-1:
Channel ID: 1
Transceiver Status: Disable
Media Type: QSFP+ 40GBASE-CR4-1.0M
Part Number: Q-4SAO01
Serial Number: S1811020204
Qualified: Yes
Administrative State: UP
Operational State: UP
Supported Speed (in Mbps): [10000]
Auto Negotiation : off
Configured Speed : 10000
Operating Speed : False
Duplex : full

  1. Note, the 10gb links LED's light up correctly.
  2. Note, the 40gb transceiver connected to the s6010-on LEDs remain off.
  3. TX/RX traffic is successful.

We do not see this behavior on the 10gb s4048-on switch when the 40gb ports are configured in fanout using the same cable. The 40gb link on the s4048-on switch lights up orange.

Also, all ports on the s6010-on switch can be trunked or connected to other 40gb links and the LEDs will light up green.

issue appears to be isolated to the s6010-on switch when ports are configured as fanout.
issue occurs on multiple s6010-on switches

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions