10Gb Interfaces are not coming up after upgrade (ASR-1001)

[RichardS3]

Hi,

After we upgraded our ASR-1001X to 17.03.04a from 17.03.03 we ran into the issue that the 10gb interfaces are not coming up anymore.

We see the following in the logs:

*Oct 20 10:17:50.807: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named TP-self-signed-1544645743.server has been generated or imported by crypto-engine
*Oct 20 10:17:53.293: %IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REQ_SUC: 0/0/0: License request is successful for interface_10g feature
*Oct 20 10:17:53.295: %IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REQ_SUC: 0/0/1: License request is successful for interface_10g feature
*Oct 20 10:17:53.305: %SPA_OIR-6-ONLINECARD: SPA (BUILT-IN-2T+6X1GE) online in subslot 0/0
*Oct 20 10:17:54.230: %IOSXE_SPA-6-UPDOWN: Interface TenGigabitEthernet0/0/0, link down due to remote fault
*Oct 20 10:17:54.237: %IOSXE_SPA-6-UPDOWN: Interface TenGigabitEthernet0/0/1, link down due to remote fault
*Oct 20 10:17:55.244: %LINK-3-UPDOWN: Interface TenGigabitEthernet0/0/0, changed state to down
*Oct 20 10:17:55.281: %LINK-3-UPDOWN: Interface TenGigabitEthernet0/0/1, changed state to down

The other side is a Nexus switch and it is connected with a Twinax cable (Cisco SFP-H10GB-CU3M)

We ran into the same problem when we went to version 17.06.01a, but when we start the old version again everything works fine.

Does anyone have any idea why the 10gbit interfaces are not working anymore with newer versions?

Thanks in advance!

/ Richard

[balaji.bandi]

Looks for Bug, raise an TAC case.

[marce1000]

 1) Is there anything in the logs of the nexus ?     2) Review if you need ROMMON upgrade (or not) : https://www.cisco.com/c/en/us/td/docs/routers/asr1000/release/notes/xe-17-3/asr1000-rel-notes-xe-17-3.html#concept_zdm_2nx_5bb

   https://www.cisco.com/c/en/us/td/docs/routers/asr1000/rommon/asr1000-rommon-upg-guide.html

 M.

[marce1000]

 -  You may want to review this bug report too, although then I do not understand how it previously worked :

                  https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo21898

 M.

[johnlloyd_13]

hi,

can you post 'show license all'

[RichardS3]

We did upgrade our ROMMON to 17.3(1r).

After a shut & no shut on the 10gb ports nothing appears in the logs on the Nexus switches.

I did notice now that when I shut the port I get the following message in the logs:

Oct 26 10:39:22.070: %TRANSCEIVER-3-NOT_SUPPORTED: SIP0/0: Detected for transceiver module in TenGigabitEthernet0/0/1, module disabled 

But I assume that is because the port is being shut (we get this message with the older, working, version as well).

[marce1000]

 - But would that then be aligned with https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo21898  (regardless of version) ?
 M.

[networkgeek2]

I have experienced the exact same issue with an ASR1001-X with Twinax cables between it and a Nexus 6k switch. When running v. 17.3.4a, the router says the transceivers are unsupported (twinax cables. First proline, then genuine cisco. It would not recognize either). Downgrading back to 17.3.3 fixes the issue. Unfortunately I do not have SNT coverage on the router I experienced this issue with so I'm unable to open a TAC case. Maybe if we have more chime in here with this issue Cisco will notice.

[RichardS3]

I did open a case and I got the reply that the Twinax cables aren't on the hardware compatibility matrix. After replacing the Twinax cables for fiber with SFP-10G-SR it worked.

It feels ridiculous that Cisco doesn't support their own Twinax cables and even more that a minor upgrade makes it suddenly stop working...

[paul driver]

Hello

thanks for the update and sharing your findings