在对一个间歇性问题提出一些建议后,我正在调查。我们在同一地点有两座大楼,由我们拥有的5.48亿纤维连接,大约10年前就安装好了。在过去的6-8个月中,我们得到了一些连接下降和间歇性问题。边缘开关是一个Cisco 3650 (WS-C3650-24PS),运行sw版本03.03.03se,由SM光纤上的1000BaseLX SFP连接,连接到Cisco 2960 (WS-C2960XR-24TS-I),运行sw版本15.2(6)E1,在SM光纤上由1000 by连接。
该站点正在经历看似随机的连接下降(数据包丢失60-80%),如果我们关闭/不关闭边缘开关端口,它将在短时间后恢复连接。
我们已经用OTDR测试了光纤运行,运行过程中没有明显的问题,但是在远端的一些损失会说它需要清理。我已经对纤维进行了粗略的清洗,用新的电缆替换了SFP和补丁电缆,我们仍然看到2960上有小错误/输入错误,而未知协议在3650上下降,但没有输入错误。
从3650上的接口输出
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseLX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 541000 bits/sec, 211 packets/sec
5 minute output rate 2726000 bits/sec, 322 packets/sec
1596899766 packets input, 440076865414 bytes, 0 no buffer
Received 86226449 broadcasts (53907138 multicasts)
0 runts, 0 giants, 0 throttles
302323 input errors, 302323 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 53907138 multicast, 0 pause input
0 input packets with dribble condition detected
3026685808 packets output, 2453674763063 bytes, 0 underruns
0 output errors, 0 collisions, 24 interface resets
616832 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 out2960上的接收接口:
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseLX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:15, output 00:00:00, output hang never
Last clearing of "show interface" counters 1d00h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1966000 bits/sec, 232 packets/sec
5 minute output rate 424000 bits/sec, 152 packets/sec
16712081 packets input, 13739039186 bytes, 0 no buffer
Received 193868 broadcasts (170085 multicasts)
6147 runts, 0 giants, 0 throttles
48719 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 170085 multicast, 0 pause input
0 input packets with dribble condition detected
9738314 packets output, 2762251700 bytes, 0 underruns
0 output errors, 0 collisions, 0 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有人有什么可能的建议吗?
更新: Cisco 2960

思科3650

发布于 2019-02-07 12:25:35
302323输入错误,302323 CRC,0帧,0溢出,0忽略
我认为这是关键信息。显然,从2960发射机到3650接收器的光纤是非常糟糕的。如果你已经排除了收发信机和补丁电缆,再次检查光纤类型不匹配(SMF vs MMF和SPC vs APC),剩下的是暗光纤及其终端。
如果没有多余的纤维链可以移动,您可以考虑在剩下的链上尝试一对bidi收发器(1000BASE-BX10)。
在OTDR显示终止问题的情况下,末端插孔需要适当的清洗或更换。
来自ODM的光学Tx和Rx水平总是要用一粒盐来测量--但是如果它们有点精确的话,4-5 dB损耗对于仅仅5000万SMF来说是一个很大的损失。只是为了确保: SMF是非常敏感的最小弯曲半径-你需要确保你的补丁线永远不会低于该半径(约5厘米)。
https://networkengineering.stackexchange.com/questions/56704
复制相似问题