Unsolved
1 Rookie
•
4 Posts
0
133
S6100-ON Using SFP+ modules in QSFP+ ports.
I am trying to move some (8) 10G links in my data center from a S4810 to an S6100. Transceiver is a CDW 10G-SR fiber module. Works fine in the S4810.
Moving to the S6100, I use a Dell 407-BBRO QSFP+ to SFP+ adapter. Plug the 407-BBRO into the QSFP+ port, and then connect the 10G-SR Transceiver into the 407-BBRO.
When connecting the 10G-SR transceiver, I see a message "%S6100-ON:1 %IFAGT-5-UNSUP_OPTICS: Non-qualified optics in stack-unit 1 module 4 port 1" on the console, so the S6100 seems to detect that a 10G SFP+ transceiver has been inserted in the QSFP+ port. However, it has no link/activity and line protocol shows as down:
show int fo 1/4/2
fortyGigE 1/4/2 is up, line protocol is down
Hardware is DellEMCEth, address is aa:bb:cc:dd:ee:ff
Current address is aa:bb:cc:dd:ee:ff
Non-qualified pluggable media present, SFP+ type is 10GBASE-SR
Medium rate is unknown, Wavelength is 850nm
SFP+ receive power reading is -3.7284dBm
No transmit power
Interface index is 2109701
Internet address is not set
Mode of IPv4 Address Assignment : NONE
DHCP Client-ID :aabbccddeeff
MTU 9416 bytes, IP MTU 9398 bytes
LineSpeed 40000 Mbit
Flowcontrol rx off tx off
ARP type: ARPA, ARP Timeout 04:00:00
Last clearing of "show interface" counters 01:04:19
Queueing strategy: fifo
Input Statistics:
0 packets, 0 bytes
0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts
0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte pkts
0 Multicasts, 0 Broadcasts, 0 Unicasts
0 runts, 0 giants, 0 throttles
port is configured very basically as:
interface fortyGigE 1/4/1
no ip address
mtu 9416
switchport
no shutdown
I added "allow unsupported-transceiver" to the running configuration, this made no difference.
anything else I need to do to get the link online?
I can daisy-chain the S4810 to the S6100 using a direct-connect QSFP copper cable and leave the SFP+ modules in the 4810, but I prefer to not do this if at all possible, and just use the S6100 to run everything, makes it easier for me to to manage.
I should mention the switch has been fully updated to the latest rev of OS 9 available on the support site. I do not have a license for OS 10.
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
March 27th, 2024 20:33
JohnHolmes,
With it throwing the error I would think it is either the transceiver or the SFP+ to QSFP+ cable that isn't compatible with the S6100. After some searching it does look like the transceiver may be compatible, despite the page here not listing it. Now since you didn't provide any details on the cable used, I can't clarify it is supported. Would you provide the part number for the cable you are using, and we can check it.
Let me know.
JohnHolmes
1 Rookie
1 Rookie
•
4 Posts
0
March 28th, 2024 16:24
@DELL-Chris H
The "error" is normal. It is actually an informational message indicating a non-Dell transceiver has been inserted. I get similar messages on all of my S4810's, although obviously the formatting is slightly different.
I am using a Dell 407-BBRO QSFP+ to SFP+ adapter, into which I insert the CDW 10GBASE-SR transceiver. A 100' run of (OM3 if memory serves me) fiber connects the transceiver to a remote S4810, where I have another CDW 10GBASE-SR transceiver.
Line protocol remains down when I connect the transceiver with the fiber connection in the S6100, but if I move the transceiver from the S6100 to a S4810 immediate under it, the link works (the S4810 below the S6100 has been in use for some time, I am attempting to eliminate it and move everything to the S6100 so I can move it to another wiring closet).
The problem isn't the transceivers or the fiber cable (they work fine connected between the S4810 below the S6100 and my remote wiring closets)
My S6100 is connected to the S4810 immediately below it with a direct connect QSFP copper cable. I could leave the SFP+ modules in the S4810 and just run things this way, but I'd much prefer to just move everything off the S4810 to the S6100.
(edited)
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
0
March 28th, 2024 20:17
Thank you.
Would you confirm the specific model of the CDW, as I think that may be the culprit?
JohnHolmes
1 Rookie
1 Rookie
•
4 Posts
0
March 28th, 2024 20:43
SFP-10G-SR-CDW is the only identifier.