ASR9000 Policy 3rd party optics:

[xthuijs]

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

http://www.cisco.com/en/US/prod/collateral/routers/ps9853/data_sheet_c78-624747.html

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 3^rd 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 3^rd party product support statement:

http://www.cisco.com/en/US/prod/prod_warranty09186a00800b5594.html

[Brian Raaen]

Also, note that only the Cisco optics and SFPs on the list as supported.  Check the capatiblity list before you order your SFP or other optics.

[JARED MAUCH]

The challenge I face is that Cisco optics are not working properly in Cisco devices, including the 9K.  This defeats your claims in #1.  #2-4 are just "features" of optics.  We have been waiting a few months now to resolve an issue with Cisco first party optics in Cisco devices.  We have been disappointed in the results, including claims that "they aren't our optics".  Even after providing photos, they validated they are not counterfeit, no clear resolution has been provided.

Use Cisco optics in Cisco devices with caution.  Don't expect Cisco to support Cisco optics in their own first-party devices.

[xthuijs]

Jared:

as we discussed in August during our summit, A9K qualifies optics to make sure behavior can be guaranteed under all circumstances. There are some optics available, whether they are official cisco optics or not, rebranded or not, that the a9k may not recognize and disables them as a safety measure to identify the operator that these optics have not been qualified and may result in undesirable behavior.

Following up to our discussion, which you reitterate here is I am revising the drivers for the A9K so that when you use the unsupported tranceiver interface command or unsupport optics command basic functionality can be provided, in a consistent manner.

thanks

xander

[JARED MAUCH]

CIsco has failed to addresss the SFP-GE-T complaince issue, our first-party Cisco SFP-GE-T optics do not work properly in the ASR9000/9000V units.  You fail to address this issue as it's a supported optic per your first link and it doesn't work properly.  If you can identify when this issue would be resolved, I think it would be helpful.  At this point it dilutes the position that 3rd party optics are somehow lower standard when you can't properly talk with your own optics.

[Farooq Ahmad]

The command is  "service unsupported-transceiver". Note the s missing after tran... above. Posting because this is a hidden command so it is essential to put the right command in.  

[xthuijs]

thanks farooq for the update there, also to note, we're looking at making this default, so it wont need to be configured for explicitly forward. should make things easier forward also.

cheers!

xander

[Riccardo Romani]

i'm not able to bring up 1gb copper ports on my asr9010 , linecard is A9K-40GE-TR SFP type is SFP-GE-T . i did put the following commands under every interfaces:

transceiver permit pid all

negotiation auto

service unsupported-transceiver

without success. Can somebody help me?

[Sudqi]

transceiver permit pid all command was tried, but other vendor XFP not work

the router is ASR9K

any one can advise?