Regression #14269
closed1100/2100: switch ports not enabled for auto-mdi-x
0%
Description
In 23.01 the 1100 switch ports do not support auto-MDI/X. The customer try to connect 1100 with 2100 and no success, to fix it needs cross-over cable or switch in the middle.
I tested the 1100 connected directly to the 3100 and it works fine without a crossover cable. Physical loop between interfaces on 1100 shows no carrier, looks like the affected device is 1100, I don't have 2100 to check on it.
Related issues
Updated by Peter Poulos over 1 year ago
aleksei prokofiev wrote:
In 23.01 the 1100 switch ports do not support auto-MDI/X. The customer try to connect 1100 with 2100 and no success, to fix it needs cross-over cable or switch in the middle.
I tested the 1100 connected directly to the 3100 and it works fine without a crossover cable. Physical loop between interfaces on 1100 shows no carrier, looks like the affected device is 1100, I don't have 2100 to check on it.
Hi Alex, i have tested a loop back on the 2100, ports dont light up, 2100 is also AFFECTED. hope this helps :)
Updated by Jim Pingle over 1 year ago
- Tracker changed from Bug to Regression
- Subject changed from 1100: switch ports not enabled for auto-mdi-x to 1100/2100: switch ports not enabled for auto-mdi-x
- Assignee set to Luiz Souza
- Priority changed from Normal to High
- Target version set to 23.05
Updated by Jim Pingle over 1 year ago
- Related to Regression #13993: Switch ports on 7100/1100/2100 do not have Auto MDI-X support enabled added
Updated by Steve Wheeler over 1 year ago
- Status changed from New to Feedback
- Affected Architecture SG-2100 added
The same fix that applied to the 7100 is already in 23.05 snapshots. The switch ports link MDI and MDIX there as expected.
Tested:
23.05-DEVELOPMENT (arm64) built on Mon Apr 10 06:05:58 UTC 2023 FreeBSD 14.0-CURRENT
Updated by Jim Pingle over 1 year ago
- Status changed from Feedback to Duplicate
Fix appears to be in and working for me as well. I get a link between the LAN and OPT ports on an 1100 running a 23.05 snapshot.
Given that the same fix applies to all of these, this should probably be marked a duplicate instead of a distinct issue.