Aruba CX 6200F: no 10G value in the speed command on port 1/1/25 with a Cisco SFP-10G-SR
We are refreshing the core of a small office and put in a pair of Aruba CX 6200F. The link between the two switches is meant to be a 10G trunk on the SFP+ uplinks, and I cannot get either box to admit that 10G exists on that port.
- 2x Aruba CX 6200F Switch Series, trunk on port 1/1/25
- Cisco SFP-10G-SR in both ends
- allow-unsupported-transceiver enabled on both switches
What I get when I try to pin the rate, and what the prot looks like afterwards:
switch(config-if)# speed ?
auto
1000-full
100-full
10-full
switch# show interface 1/1/25 transceiver
1/1/25 SFP+SR*
switch# show interface 1/1/25 physical
1/1/25 is down
Speed:The largest value the parser offers is 1000-full, the transceiver line carries an asterisk, and the port sits down with no speed at all.
What I already did:
- reseated both modules and moved the pair to another SFP+ port
- turned allow-unsupported-transceiver off and back on, then rebooted one switch
- swapped the duplex patch cord between the two switches
Is the missing 10G value the switch quietly refusing the Cisco module, or am I turning the wrong knob? How do I pin this trunk to 10G?
Also available in: English
العربية
Deutsch
Español
Français
हिन्दी
Bahasa Indonesia
Italiano
日本語
한국어
Nederlands
Polski
Português
Русский
Türkçe
Tiếng Việt
简体中文
Comments 3
Short version: the missing 10G value is normal, and it has nothing to do with the module being Cisco.
On AOS-CX an SFP/SFP+ port does not accept a configured speed while a transceiver is inserted. The port runs at the fixed rate of whatever sits in the cage, so 10G comes from the SFP-10G-SR itself and not from a speed keyword. What you see in
speed ?is what the platform can offer a port without optics, which is why the list stops at 1000-full. There is no 10000-full to select, and you are not missing a licence or a feature.The asterisk is the second half of the confusion. It says the module is not on the supported list and is being tolerated because of allow-unsupported-transceiver. Tolerated means the port is driven normally; it does not mean the switch is holding the link down.
So drop the speed configuration entirely and treat the remaining down state as an ordinary optical problem: both ends have to be a working SR module, and it is worth reading
show interface 1/1/25 transceiverandshow interface 1/1/25 physicalon both switches with the fibre swapped end for end. With a healthy SR pair the port comes up at 10G on its own.One caveat before you settle on third-party optics for the core: the first thing you will be asked in a support case is to reproduce the fault with a module from the Aruba list, so keeping one supported pair on the shelf saves an argument later.
The asterisk is not a failure indicator. It only marks a module that AOS-CX does not carry on its own list and that you are tolerating with allow-unsupported-transceiver. A module the switch really refused would not be listed as SFP+SR at all.
Before anyone guesses at the speed keyword: post
show interface 1/1/25 brieffrom both switches. And say whether either of tohse two SR modules has ever carried a link anywhere else. Tolerated is not the same as tested, and a module with a dead transmitter draws exactly this picture, port down and no speed.Neither module has been proven anywhere else. Both came out of the same tray and went straight into this trunk, so there is no port where I have watched them light up.
show interface 1/1/25 briefis identical on either side, trimmed to the columns that matter:Same asterisk, no speed value. The patch cord between them is a short duplex multimode jumper that carries a 1G pair without complaints when I move it.