11-15-2013 01:59 PM - edited 03-01-2019 07:27 AM
Hi,
I have some Nexus 7000 with FET-10G with xcvrInval status
Eth7/33 N5k-S1-3T-1/3 xcvrInval trunk auto auto Fabric Exte
and some other FET-10G with notconn status
Eth7/8 FEX-101 notconnec 1 auto auto Fabric Exte
If I inter exchange the position of both FET-10G the status port doesn´t change
FET-10G from 7/8 to 7/33
FET-10G from 7/33 to 7/8
7/33 holds xcvrInval status
7/8 holds notconnec status
I have reconfigured from default interface with same results
Next you´ll find the same serial number in deferent port, the diference is the current
when is xcvrInva or when is notconnec
What can I do to get FET10G in e7/33 validated?
|
now in slot 7/8
Ethernet7/8 |
transceiver is present |
type is Fabric Extender Transceiver |
name is CISCO-FINISAR |
part number is FTLX8570D3BCL-C2 |
revision is A |
serial number is FNS17201TE5 |
nominal bitrate is 10300 MBit/sec |
Link length supported for 62.5/125um fiber is 10 m |
Link length supported for 50/125um OM3 fiber is 100 m |
cisco id is -- |
cisco extended id number is 4 |
cisco part number is 10-2566-02 |
cisco product id is FET-10G |
cisco vendor id is V02 |
number of lanes 1 |
SFP Detail Diagnostics Information (internal calibration) |
---------------------------------------------------------------------------- |
Current Alarms Warnings |
Measurement High Low High Low |
---------------------------------------------------------------------------- |
Temperature 23.17 C 75.00 C 5.00 C 70.00 C 10.00 C |
[7m--More-- [m |
Voltage 3.30 V 3.63 V 2.97 V 3.46 V 3.13 V |
Current 7.50 mA 11.80 mA 4.00 mA 10.80 mA 5.00 mA |
Tx Power 17.65 dBm 22.69 dBm 8.69 dBm 18.69 dBm 12.69 dBm |
Rx Power -12.21 dBm -- 22.99 dBm 6.09 dBm 18.99 dBm 10.09 dBm |
Transmit Fault Count = 0 |
---------------------------------------------------------------------------- |
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning |
NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
Ethernet7/33 is down (Transceiver validation failed)
admin state is up, Dedicated Interface
Belongs to Po51
Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cec (bia 8478.ac23.6cec)
Description: N5k-S1-3T-1/3
MTU bytes (CoS values): MTU 1500(0-2,4-7) bytes MTU 2112(3) bytes
BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is trunk
auto-speed 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 never
Last clearing of "show interface" counters 07:22:09
0 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 0 bits/sec, 0 packets/sec
300 seconds output rate 0 bits/sec, 0 packets/sec
RX
88 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC/FCS 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
88 unicast packets 0 multicast packets 0 broadcast packets
0 output packets 0 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
Ethernet7/8 is down (Link not connected)
admin state is up, Dedicated Interface
Belongs to Po101
Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cd3 (bia 8478.ac23.6cd3)
Description: FEX-101
MTU bytes (CoS values): MTU 1500(0-2,4-7) bytes MTU 2112(3) bytes
BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is p2p
Port mode is fex-fabric
auto-speed 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 5week(s) 1day(s)
Last clearing of "show interface" counters never
0 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 0 bits/sec, 0 packets/sec
[7m--More-- [m
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 0 bits/sec, 0 packets/sec
300 seconds output rate 0 bits/sec, 0 packets/sec
RX
10588 unicast packets 0 multicast packets 0 broadcast packets
4 input packets 0 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC/FCS 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
10588 unicast packets 1 multicast packets 0 broadcast packets
4 output packets 5688 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
Solved! Go to Solution.
11-15-2013 02:35 PM
Hi Erick,
Are you using the FET-10G to connect to a fabric extender? These optics are only usable between a N7K/N5K and the fabric extender. If you have configured "switchport mode fex-fabric" and still receiving the "Transceiver validation failed" error messages this could be a sign of something else possibly hardware related. If you are trying to use the interface for something other than connecting a FEX to the Nexus then that won't work.
HTH
Ant
11-15-2013 02:35 PM
Hi Erick,
Are you using the FET-10G to connect to a fabric extender? These optics are only usable between a N7K/N5K and the fabric extender. If you have configured "switchport mode fex-fabric" and still receiving the "Transceiver validation failed" error messages this could be a sign of something else possibly hardware related. If you are trying to use the interface for something other than connecting a FEX to the Nexus then that won't work.
HTH
Ant
11-15-2013 03:10 PM
Hi Ans,
You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
NX7K-1-VDC-3T-S1-L2FP(config-if)# description FEX-101
NX7K-1-VDC-3T-S1-L2FP(config-if)# switchport
NX7K-1-VDC-3T-S1-L2FP(config-if)# switchport mode fex-fabric
NX7K-1-VDC-3T-S1-L2FP(config-if)# fex associate 101
NX7K-1-VDC-3T-S1-L2FP(config-if)# medium p2p
NX7K-1-VDC-3T-S1-L2FP(config-if)# channel-group 101
NX7K-1-VDC-3T-S1-L2FP(config-if)# no shutdown
NX7K-1-VDC-3T-S1-L2FP(config-if)#
NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
--------------------------------------------------------------------------------
Port Name Status Vlan Duplex Speed Type
--------------------------------------------------------------------------------
Eth7/33 FEX-101 notconnec 1 auto auto Fabric Exte
NX7K-1-VDC-3T-S1-L2FP(config-if)#
Thanks for your help, and have a nice weekend.
Atte,
EF
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide