Re: Interface getting down - Page 2

Fernando Galvao · ‎10-20-2017

I'm having a Nexus 3064pq in Layer core being a core network. Today I have a problem where a 10Gbps port (1/36) is falling out of nowhere. It gets down and only returns when we remove the gbic cisco and put it back. We already changed the Gbic and the problem continues.

What can it be? Below the log:

show logging logfile | include 1/36
2017 Oct 12 14:59:00 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/36 is down (Transceiver Absent)
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 12 14:59:04 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 12 15:41:31 UTC CORE-CISCO %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/36, hardware type changed to No-Transceiver
2017 Oct 12 15:42:10 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 12 15:42:10 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 12 15:42:10 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 12 15:42:10 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 12 15:42:10 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 13 15:41:39 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 13 15:41:43 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 13 15:41:43 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 13 15:41:43 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 13 15:41:43 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 13 15:41:43 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 17 15:57:57 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 17 15:58:00 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 17 15:58:00 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 17 15:58:00 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 17 15:58:00 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 17 15:58:00 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 17 16:31:56 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 17 16:31:59 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 17 16:31:59 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 17 16:31:59 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 17 16:31:59 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 17 16:31:59 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 17 17:00:57 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 17 17:10:11 UTC CORE-CISCO %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/36, hardware type changed to No-Transceiver
2017 Oct 17 17:10:58 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 17 17:10:58 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 17 17:10:58 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 17 17:10:58 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 17 17:10:59 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 17 17:12:08 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 17 17:12:11 UTC CORE-CISCO %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/36, hardware type changed to No-Transceiver
2017 Oct 17 17:12:32 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 17 17:12:32 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 17 17:12:32 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 17 17:12:32 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 17 17:12:32 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk
2017 Oct 20 15:26:53 UTC CORE-CISCO %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet1/36 is down (Link failure)
2017 Oct 20 15:38:24 UTC CORE-CISCO %ETHPORT-5-IF_HARDWARE: Interface Ethernet1/36, hardware type changed to No-Transceiver
2017 Oct 20 15:38:38 UTC CORE-CISCO %ETHPORT-5-SPEED: Interface Ethernet1/36, operational speed changed to 10 Gbps
2017 Oct 20 15:38:38 UTC CORE-CISCO %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/36, operational duplex mode changed to Full
2017 Oct 20 15:38:38 UTC CORE-CISCO %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet1/36, operational Receive Flow Control state changed to off
2017 Oct 20 15:38:38 UTC CORE-CISCO %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet1/36, operational Transmit Flow Control state changed to off
2017 Oct 20 15:38:38 UTC CORE-CISCO %ETHPORT-5-IF_UP: Interface Ethernet1/36 is up in mode trunk

cprajapati · ‎06-07-2018

I Did every thing , replaced cable , replace SFP but having the same issue.

Can any one let me know the solution on same

SNTX · ‎07-06-2022

hi i have the same problem with my nexus 3064 with dwdm networks.

my switch send loss to dwdm provider port and cause a flap when circuit must witch from master to slave

provider tells me:

They should be able to advise how to increase “carrier-delay down” time on your ports in order to not send LOS during protection switch (sub 50ms flaps).

When there is an outage on spare or main route, fault there is triggering protection switch, so protection is working, but can not be set to revertive due to LOS respond from your ports, so the service will stay where it currently is.
The only way to trigger protection switch is to lockout spare route (say to system to not use it).

In summary, protection is working when fault will on main (will switch to spare) or on spare (will switch to main), but the service will stay there and can not manually or auto revert back to main unless spare will be locked, due to LOS from your ports.

Please, escalate this to your vendor to advise why your ports are ending LOS in case of sub 50ms flap due to protection switch

motiar · ‎03-03-2021

Hi Andrea,

I have a similar problem, can you please have a look, whether you have any idea?

https://community.cisco.com/t5/network-management/nexus-5596-switche-keep-droping-the-traffics/m-p/4299265#M138973

Regards

Motiar

mohammed.aljazaeri · ‎03-30-2023

kindly i have Nexus 9000 series and this command doesn't work on the 9000 series

show platform software ethpc event-history interface

do you know if there is any similar command to it on nexus 9000 ??

rajinishsk31482 · ‎03-15-2020

%ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet2/15, operational Receive Flow Control state changed to off
2020 Mar 15 11:55:00

ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet2/15, operational Transmit Flow Control state changed to off

jen2181918 · ‎06-20-2020

Have you solved it? Please tell me how to solve it.

Jason Stack · ‎08-31-2020

I have a Nexus 3K with similar issue. We have a carries circuit 1G and could not get the port to light. We added no negotiate auto, solved the issue.

interface Ethernet1/38
speed 1000
description WASABI-FLEXENTIAL
switchport access vlan 3300
no negotiate auto
udld enable
no shutdown

motiar · ‎03-03-2021

Hi Fernando,

How did you solve the problem? I have a similar problem, can you have a look?

https://community.cisco.com/t5/network-management/nexus-5596-switche-keep-droping-the-traffics/m-p/4299265#M138973

Regards

Motiar

omertebi · ‎02-17-2022

hello, i faced this issue too today , i was connecting cisco nexus 9k to cisco C2960-24TC-L through UTP uplink , i changed the media to auto and put fiber cable with SFP and set the configuration in the cisco 2960 to ( switchport mode trunk
switchport nonegotiate ) , on the nexus i put the configuration (switchport mode trunk
duplex full), it works fine and shine

Regards

Omer