The 16.02 release for the ArubaOS-Switch (Provision) wired switches includes a welcome ‘new’ feature to enable the use of unsupported transceivers.
Previously, the switches were simply blocking the use of 3th party transceivers. With this new command, the admin can override this behavior. This does not mean that these 3th party transceivers are supported, it only means that the port is no longer disabled when an unsupported transceiver is connected.
This is an example on a 2930F model
- Review the current transceiver details and state when no transceiver is connected, enable event logging
Aruba-2930F-8G-PoEP-2SFPP# show interfaces transceiver detail No transceiver found on any selected port.
Aruba-2930F-8G-PoEP-2SFPP# show tech transceivers Cmd Info : show tech transceivers transceivers Transceiver Technical Information: Port # | Type | Prod # | Serial # | Part # -------+-----------+------------+------------------+---------- === The command has completed successfully. ===
Aruba-2930F-8G-PoEP-2SFPP# debug event Aruba-2930F-8G-PoEP-2SFPP# debug destination session
- Insert unsupported transceiver, log message is shown
Aruba-2930F-8G-PoEP-2SFPP# W 01/01/90 00:15:26 00535 FFI: port 9 This switch only supports revision B and above transceivers.
- Review the updated transceiver details and state
Aruba-2930F-8G-PoEP-2SFPP# show interfaces transceiver detail No transceiver found on any selected port.
Aruba-2930F-8G-PoEP-2SFPP# show tech transceivers Cmd Info : show tech transceivers transceivers Transceiver Technical Information: Port # | Type | Prod # | Serial # | Part # -------+-----------+------------+------------------+---------- 9 | ?? | ?? | unsupported | The following transceivers have extra information: Port # Message -------- ------------------------------------- Port 9 This switch only supports revision B and above transceivers. Check: www.hp.com/rnd/device_help/2_inform for more info. === The command has completed successfully. ===
- Enable the use of unsupported transceivers and read the message 🙂
Aruba-2930F-8G-PoEP-2SFPP(config)# allow-unsupported-transceiver Warning: The use of third-party transceivers is at your own risk and may void support and warranty. Please see HPE Warranty terms and conditions. Do you agree, and do you wish to continue enabling? (Y/N) y Aruba-2930F-8G-PoEP-2SFPP(config)#
For scripted deployments, the ‘confirm’ option can be used
Aruba-2930F-8G-PoEP-2SFPP(config)# allow-unsupported-transceiver confirm Warning: The use of third-party transceivers is at your own risk and may void support and warranty. Please see HPE Warranty terms and conditions. Aruba-2930F-8G-PoEP-2SFPP(config)#
- After re-inserting the transceiver, review the updated transceiver details and state
I 01/01/90 00:21:04 00406 ports: port 9 xcvr hot-swap remove. I 01/01/90 00:21:06 03703 ports: port 9 unsupported xcvr hot-swap insert.
Aruba-2930F-8G-PoEP-2SFPP# show tech transceivers Unable to get dldp_status Unable to get ripng_status Cmd Info : show tech transceivers transceivers Transceiver Technical Information: Port # | Type | Prod # | Serial # | Part # -------+-----------+------------+------------------+---------- 9 *| 1000SX | ?? | unsupported | * third-party transceiver === The command has completed successfully. ===
Aruba-2930F-8G-PoEP-2SFPP# show interfaces transceiver detail Transceiver in 9* Interface Index : 9 Type : 1000SX Model : ?? Connector Type : LC Wavelength : 850nm Transfer Distance : 550m (50um), 300m (62.5um), Diagnostic Support : DOM Serial Number : unsupported Status Temperature : 49.460C Voltage : 3.3330V Tx Bias : 4.716mA Tx Power : 0.2394mW, -6.208dBm Rx Power : 0.0003mW, -35.228dBm Recent Alarms : Rx power low alarm Rx power low warning Recent Errors : Rx loss of signal Time Stamp : Mon Jan 1 00:24:48 1990 * third-party transceiver Aruba-2930F-8G-PoEP-2SFPP#
The switch will still generate daily log messages to warn the admin that this feature has been enables.
About Aruba Networks 
Thanx Peter!!!! It’s a welcomed feature 🙂
I wonder if this feature is available across the full line of ProVision ASIC switches or only for a certain version of PV-ASIC? I just tried a 3810 running KB.16.02.13.swi and it has this support, a 3800 running KA.16.02.0012 does not, and a 3500 running K.16.02.0012 does not.
I’ll continue to monitor as newer code releases come out.
Cheers…Jeff
Hi Jeff, indeed, the feature is only intended for ‘new’ gen switches (5400R with V2/V3 modules, 3810M, 2930F, 2920, 2930). I believe the 2530 would be added as well, but that may come in a later release.).
So no luck for 3500/3800/5400 platforms!
Thanx for the update Peter!
Hi, it seems the feature is gone in 16.03 – Do you happen to know why, or if it will be implemented later?
I had not noticed that, what switch model are you working on?
5412R zl2 and 3810M. Had to downgrade from 16.03.03 to 16.02.16.
I just did a quick test:
I booted a 3810 to KB.16.03.0003, went into config, and simply typed ‘all’ and the command did not show.
I booted back to KB.16.02.0014 did the same ‘all’ and the command tabbed out…I confirmed the change and did a ‘wr m’.
I booted back to KB.16.03.0003 and the command was still in the running config. When I did an ‘all’ again, no tabbed out command. Then I typed out the entire command ‘allowed-unsupported-transceiver’ and the a ‘?’ and there it was. So the command is still available, just hidden.
hth…Jeff
Some minor typo’s in my last post…I guess WP didn’t like some of my formatting…
Let me redo this:
I booted a 3810 to KB.16.03.0003, went into config, and simply typed ‘all’ and “tab key” and the command did not show.
I booted back to KB.16.02.0014 did the same ‘all’ and “tab key” and the command tabbed out…I confirmed the change and did a ‘wr m’.
I booted back to KB.16.03.0003 and the command was still in the running config. When I did an ‘all’ and “tab key” again, no tabbed out command. Then I typed out the entire command ‘allowed-unsupported-transceiver’ and then a ‘?’ and there it was. So the command is still available, just hidden.
hth…Jeff
Can confirm that it work on 2530 running YA.16.02.0018
/Jakob
Hi,
With the 16.03.xxx, in VSF mode for 2930F, the VSF link don’t work after a reboot (of the standby member) with a “unsuported” DAC cable also the cli “allow-unsupported-transceiver”.
But the DAC work well without VSF context.
If i create a VSF Link with 10G fiber tranceiver, it’s ok. After i add a second physical VSF Link (same VSF link number), with my “unsuported” DAC this link is ok, but after a reboot we have the same problem, the VSF DAC Link is not active. (but 10G fiber tranceiver it’s ok).
Just updates a 2920-48 and this worked a treat. Working with pretty much any SFP+ SR we try!
I known, but when one of my two 2930F (16.03) boot with VSF configuration, the VSF link don’t work with a unsupported tranceiver. Even if the command “allow-unsupported-transceiver”is active.
But if the link is not a VSF link, the link it’s ok with unsupported tranceiver.
Hi Dellaccio,
Dis you find a way to waork around this?
I have the same issue actually: unsupported transceiver not working in VSF.
Thanks
I have 2620-24(16.02.0014), but command “allow-unsupported-transceiver” does not work on this.
I have tried all the below IOS versions, still non of them worked.
RA_15_17_0013
RA_16_02_0014
RA_16_02_0020
RA_16_03_0004
RA_16_03_0005
Please help.
Hi Nikita,
1/ AFAIK, the 2620 will not receive this command, so it is limited to the Aruba branded models (2930/3810/5400R etc.).
2/ Even on the switches that support the command, the command has been made hidden, you it does not show up in the ? list anymore.
You just need to enter the command “allow-unsupported-transceiver” in the global config.