cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2812
Views
0
Helpful
1
Replies

Getting Physical port failure error on Nexus 7000 switch

nayanpanchal
Level 1
Level 1

I've Nexus 7010 switch installed in my DC. I've conncected Cisco router to one of the Ports. On the same port I'm getting following error message and hence, unable to form EIGRP neighborship.

DR-CORE-SW-S01-NEXUS7K %MODULE-2-MOD_SOMEPORTS_FAILED:

Module 1 (serial: JAF*******NGK) reported failure on ports 1/2-1/2 (Ethernet) due

to R2D2 : Speed patch failed - no frames transmitted in device 143 (error 0xc8f0

1273)

Please suggest what is the solution for this.

1 Accepted Solution

Accepted Solutions

acampbell
VIP Alumni
VIP Alumni

Hi,

Looks like you are hitting a bug

CSCtq34950 Bug Details
R2D2 : Speed patch failed - no frames transmitted
Symptom:

Ports randomly lose connectivity with error messages

%MODULE-2-MOD_SOMEPORTS_FAILED: Module 2 (serial: XXXXXXXX) reported failure on
ports 2/36-2/36 (Ethernet) due to R2D2 : Speed patch failed - no frames
transmitted in device 143 (error < error-code>)

Conditions:

Issue is seen with N7K-M148GT-11 module.

Workaround:

Move connected device to another port.

Further Problem Description:

This issue is triggered by physical layer event (link up, link down or speed
change) and occurs due to a race condition. It should be fixed in 5.1(5) or
later, and 5.2(2) or later releases.

Regards,
Alex.
Please rate useful posts.

Regards, Alex. Please rate useful posts.

View solution in original post

1 Reply 1

acampbell
VIP Alumni
VIP Alumni

Hi,

Looks like you are hitting a bug

CSCtq34950 Bug Details
R2D2 : Speed patch failed - no frames transmitted
Symptom:

Ports randomly lose connectivity with error messages

%MODULE-2-MOD_SOMEPORTS_FAILED: Module 2 (serial: XXXXXXXX) reported failure on
ports 2/36-2/36 (Ethernet) due to R2D2 : Speed patch failed - no frames
transmitted in device 143 (error < error-code>)

Conditions:

Issue is seen with N7K-M148GT-11 module.

Workaround:

Move connected device to another port.

Further Problem Description:

This issue is triggered by physical layer event (link up, link down or speed
change) and occurs due to a race condition. It should be fixed in 5.1(5) or
later, and 5.2(2) or later releases.

Regards,
Alex.
Please rate useful posts.

Regards, Alex. Please rate useful posts.
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:

Review Cisco Networking products for a $25 gift card