TenGigE Interface Sometime fault

ty.chan007 · ‎01-13-2014

Hi,

I am facing a problem where my TenGigE interface is sometime down.

Diagram:

ASR1K <----> ASR9K

Log on ASR1K :

.Jan 14 07:56:31 GMT+7: %IOSXE_SPA-6-UPDOWN: Interface TenGigabitEthernet0/2/0, link down due to remote fault

On ASR9K, i don't find any log.

By Shut/Commit and No Shut/Commit on ASR9K, the link resumed to normal.

Any idea?

PS: the fiber path cord is around 5m.

Regards,

CT

Leo Laohoo · ‎01-13-2014

Post the output to the command "sh interface Ten 0/2/0".

ty.chan007 · ‎01-13-2014

PE#sh int ten0/2/0

TenGigabitEthernet0/2/0 is up, line protocol is up

Hardware is SPA-1X10GE-L-V2, address is 30f7.0d42.2c20 (bia 30f7.0d42.2c20)

Description: CONNECT ME01-POP1 (T1/30) - TRUNK

MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,

reliability 255/255, txload 255/255, rxload 1/255

Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set

Keepalive not supported

Full Duplex, 10000Mbps, link type is force-up, media type is 10GBase-LR

output flow-control is on, input flow-control is on

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:05, output hang never

Last clearing of "show interface" counters never

Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 18443

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 29572000 bits/sec, 5833 packets/sec

5 minute output rate 30406000 bits/sec, 4014 packets/sec

8553385575 packets input, 5321708311292 bytes, 0 no buffer

Received 241799997 broadcasts (0 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 996344186 multicast, 0 pause input

6257933590 packets output, 5661214436454 bytes, 0 underruns

0 output errors, 0 collisions, 5 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

Leo Laohoo · ‎01-13-2014

PS: the fiber path cord is around 5m.

Full Duplex, 10000Mbps, link type is force-up, media type is 10GBase-LR

Uhhhhh ... WHAT?????

Leo Laohoo · ‎01-13-2014

reliability 255/255, txload 255/255, rxload 1/255

Can you post the "sh interface" from the remote end?

ty.chan007 · ‎01-13-2014

Here is the status on ASR9K:

RP/0/RSP0/CPU0:9K-01-SCT#sh int ten0/0/2/2

Tue Jan 14 11:11:51.864 GMTKH

TenGigE0/0/2/2 is up, line protocol is up

Interface state transitions: 9

Hardware is TenGigE, address is 10f3.110c.98de (bia 10f3.110c.98de)

Layer 1 Transport Mode is LAN

Description: CONNECT PE

Layer 2 Transport Mode

MTU 1514 bytes, BW 10000000 Kbit (Max: 10000000 Kbit)

reliability 255/255, txload 0/255, rxload 0/255

Encapsulation ARPA,

Full-duplex, 10000Mb/s, link type is force-up

output flow control is off, input flow control is off

loopback not set,

Last input 00:00:00, output 00:00:00

Last clearing of "show interface" counters never

5 minute input rate 26035000 bits/sec, 3524 packets/sec

5 minute output rate 22788000 bits/sec, 5196 packets/sec

6267071861 packets input, 5670584827328 bytes, 98098 total input drops

0 drops for unrecognized upper-level protocol

Received 736499 broadcast packets, 20857 multicast packets

0 runts, 0 giants, 0 throttles, 0 parity

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

8566988780 packets output, 5330087075217 bytes, 735 total output drops

Output 242283785 broadcast packets, 996960399 multicast packets

0 output errors, 0 underruns, 0 applique, 0 resets

0 output buffer failures, 0 output buffers swapped out

9 carrier transitions

Leo Laohoo · ‎01-13-2014

1. Can you confirm what is the length of the fibre optic patch cable?

2. On the switch, can you post the output to the command "sh interface Ten 0/2/0 transceiver prop"?

ty.chan007 · ‎01-13-2014

1. Confirm the cable length is around 5m (or less then 10m)

2. Below is the output:

ME4900#sh int te1/30 transceiver detail

ITU Channel not available (Wavelength not available),

Transceiver is internally calibrated.

mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.

++ : high alarm, + : high warning, - : low warning, -- : low alarm.

A2D readouts (if they differ), are reported in parentheses.

The threshold values are calibrated.

High Alarm High Warn Low Warn Low Alarm

Temperature Threshold Threshold Threshold Threshold

Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)

--------- ------------------ ---------- --------- --------- ---------

Te1/30 34.7 74.0 70.0 0.0 -4.0

High Alarm High Warn Low Warn Low Alarm

Voltage Threshold Threshold Threshold Threshold

Port (Volts) (Volts) (Volts) (Volts) (Volts)

--------- --------------- ---------- --------- --------- ---------

Te1/30 0.00 N/A N/A N/A N/A

Optical High Alarm High Warn Low Warn Low Alarm

Transmit Power Threshold Threshold Threshold Threshold

Port (dBm) (dBm) (dBm) (dBm) (dBm)

--------- ----------------- ---------- --------- --------- ---------

Te1/30 -2.0 4.4 0.4 -8.2 -12.2

Optical High Alarm High Warn Low Warn Low Alarm

Receive Power Threshold Threshold Threshold Threshold

Port (dBm) (dBm) (dBm) (dBm) (dBm)

------- ----------------- ---------- --------- --------- ---------

Te1/30 -11.7 4.4 0.4 -14.4 -18.4

Leo Laohoo · ‎01-13-2014

1. Confirm the cable length is around 5m (or less then 10m

Ok, then finally, can you post the output to the command "sh inventory". I think I know where the problem is.

Leo Laohoo · ‎01-13-2014

PS: the fiber path cord is around 5m.

Full Duplex, 10000Mbps, link type is force-up, media type is 10GBase-LR

If what you are saying is correct, that the fibre optic patch cable is only 5 to 10 metres and the fibre optic used is LR (or LONG REACH), then what your Cisco appliance is behaving (ports go down) is normal.

This is because you are using LR fibre optic modules to shoot at a very short distance. At 5 to 10 metres you should be using 10GBase-SR.

ty.chan007 · ‎01-13-2014

OK, thanks.

I will make it longer and also put attenuators.

Thanks so much for the input.

Leo Laohoo · ‎01-13-2014

I will make it longer and also put attenuators.

I am not sure if attenuators are enough. You need to replace the fibre optic modules (and cable) if the distance is too short.

ty.chan007 · ‎01-14-2014

Some people say it maybe a bug. Is it possible?

Leo Laohoo · ‎01-14-2014

Some people say it maybe a bug. Is it possible?

LOL! No it is not a bug.

Someone is using LR fibre modules to shoot traffic down a 5 METRE DISTANCE. That's not a bug. That's @#$%^&*!!! stupidity.

Michael Kaciuba · ‎12-07-2015

* Minimum cabling distance for -SR, -LRM, -LR, -ER modules is 2m, according to the IEEE 802.3ae.