Showing results for 
Search instead for 
Did you mean: 
Cisco Employee
Cisco Employee

The ASR 9000 supports only the SFPs/XFPs/SFP+ optics listed in the datasheets:

As part of bringing up the interface, the system checks to see what type of optic is installed and if it's a valid part number.  If the part number is not something supported, A9K will not bring up the link and shows an error message to the console/vty, PFM (platform fault manager, show pfm location all) and syslog. 

There is a CLI command that allows to skip this check.  The command goes under the physical interface, and is "transceiver permit pid all".  Another command that allows us to skip the vendor check is " service unsupported-tranceiver " (hidden and global config). 

What these commands DO:

  • It skips the "is this a recognized optics module" check and basically sets the answer to "yes"...allowing the system to POSSIBLY bring up the interface the rest of the way.
    • This will generate a PFM alarm of warning level indicating the system is running in a potentially UNSUPPORTED configuration.

What these commands DO NOT do:

  • It DOES NOT magically allow any random optics module to work in the system.  Contrary to popular belief, there is a LOT of variance in how different vendors implement optical modules. 

Some specific examples:

    1. Some optics/vendors have different ways of       communicating with the host systems.
    2. Some modules support things like optical power       monitoring, some do not.
    3. Some modules support extended temperature operation,       some do not.
    4. Some modules have lower/higher reliability/MTBF       numbers than others.

These commands also do NOT imply support of the optic and is merely a best effort capability.

With that in mind, the guidelines are :

If it's a supported Cisco part with the proper PID, we support it, and we'll make it work. 

If it's not, you can TRY the transceiver permit pid all command. 

TAC can’t support this.

A9K policy is not to break the use of 3rd party optics, however it can happen that in between releases due to driver changes a previously unsupported optics that was brought up with override commands may not function after a release upgrade or SMU application.

Official Cisco 3rd party product support statement:

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: