ArubaOS-Switch 16.02: unsupported transceiver option

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.

This entry was posted in ArubaOS-Switch and tagged , , . Bookmark the permalink.

8 Responses to ArubaOS-Switch 16.02: unsupported transceiver option

  1. Jeff Carrell says:

    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

  2. toothstone says:

    Hi, it seems the feature is gone in 16.03 – Do you happen to know why, or if it will be implemented later?

  3. Jeff Carrell says:

    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

    • Jeff Carrell says:

      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

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s