cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
21490
Views
0
Helpful
7
Replies

FEX ports in SDP timeout/SFP Mismatch 6.2(2a) - Nexus 7009

raghvendra321
Level 1
Level 1

Hi ,

 

kinldy help me to get rid of this problem , when i try to enable fex port in individual port or port channel it give me this error. I have rebooted and erase/renew the configuration but could not succeed. Appreciate your help and advise.

 

Regards,

Raghu

1 Accepted Solution

Accepted Solutions

Hi Raghu,

 

So you dual homing a fex? Is it coming up fine over second switch?  I see it is link not connected?

About SDP timeout//Mismatch, it could be due to variable reason. Please try 

1. Replace the SFP

2. Replace the fiber

3. Move the parent port to another from Eth3/11 (I would prefer you moving to another port group asic. If you can let me know which line card, i can help you)

3. If above did not help, change the port on FEX

4. If no help, try swapping connection between the N7k-1 and N7K-2 

 

Hope this helps. Please do remeber to rate all helpful posts.

 

Thanks,

Madhu.

 

 

View solution in original post

7 Replies 7

Hello Raghu,

 

could you please provide us the logs when you perform this. Also share a show int <>

 

Thanks,

Madhu

HI Madhukrishnan,

Please find below details.

 

Ethernet3/11 is down (SDP timeout/SFP Mismatch)
admin state is up, Dedicated Interface
  Hardware: 1000/10000 Ethernet, address: 5087.8942.6ec6 (bia 5087.8942.6ec6)
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, medium is broadcast
  Port mode is fex-fabric
 10 Gb/s  auto-duplex,, media type is 10G
  Beacon is turned off
  Auto-Negotiation is turned on
  Input flow-control is off, output flow-control is off
  Auto-mdix is turned on
  Rate mode is dedicated
  Switchport monitor is off 
  EtherType is 0x8100 
  EEE (efficient-ethernet) : n/a
  Last link flapped 00:03:04
  Last clearing of "show interface" counters never
  0 interface resets
  Load-Interval #1: 30 seconds
    30 seconds input rate 2960 bits/sec, 0 packets/sec
    30 seconds output rate 0 bits/sec, 0 packets/sec
  Load-Interval #2: 5 minute (300 seconds)
Rack-23_N7k-1# show version 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy 

==========================

Secondary:

 

Rack-24_N7k-2# sh interface ethernet 3/11
Ethernet3/11 is down (Link not connected)
admin state is up, Dedicated Interface
  Hardware: 1000/10000 Ethernet, address: 0008.2f2d.3226 (bia 0008.2f2d.3226)
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, medium is broadcast
  Port mode is fex-fabric
 10 Gb/s  auto-duplex,, media type is 10G
  Beacon is turned off
  Auto-Negotiation is turned on
  Input flow-control is off, output flow-control is off
  Auto-mdix is turned on
  Rate mode is dedicated
  Switchport monitor is off 
  EtherType is 0x8100 
  EEE (efficient-ethernet) : n/a
  Last link flapped 00:00:09
  Last clearing of "show interface" counters never
  0 interface resets

Hi Raghu,

 

So you dual homing a fex? Is it coming up fine over second switch?  I see it is link not connected?

About SDP timeout//Mismatch, it could be due to variable reason. Please try 

1. Replace the SFP

2. Replace the fiber

3. Move the parent port to another from Eth3/11 (I would prefer you moving to another port group asic. If you can let me know which line card, i can help you)

3. If above did not help, change the port on FEX

4. If no help, try swapping connection between the N7k-1 and N7K-2 

 

Hope this helps. Please do remeber to rate all helpful posts.

 

Thanks,

Madhu.

 

 

HI Madhu,

thanks for your suggestion.

however i have figured it out. It was due to Dual home connectivity ove nexus 7k and Nexus 7k doesnot support dual home like 5k. i connected Fex parallely which mean 1 fex go to 1 7k. and issue got resolved.

 

 

Hi Raghu,

 

Glad to hear issue resolved and thanks for sharing with us.

 

Regards,

Madhu

FYI, I ran into this same issue and was able to resolve it by shutting down the port on the Nexus side, reseating the FET module and fiber connectors on both ends, then turning the port back up. It's not a sexy solution, but it did the trick for me, and may save someone else a headache or money.

Orlando_Native
Level 1
Level 1

I understand how this works for fiber connections; but how about copper?  I have a Nexus 6001T switch with 48 copper ports.   They can be defined as mode "fex-fabric"; but how does one connect a FEX (eg; a 2248TP-E) to the switch in this case?  I tried inserting a regular GLC-T SFP in the uplink port on the FEX; but it would appear the FEX doesn't like GLC-T transceivers.  Would one insert the RJ45 patch cable into a "regular" FEX port instead?

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: