RCV Err 增加且端口呈琥珀色闪烁

网络工程 转变 第一层 电缆 纤维 布线
2022-02-03 09:32:29

有时千兆端口开始闪烁琥珀色灯，当我这样做时，sh int count err我可以看到“RCV err”如何增长。

SW-Floor-2#show int gig 2/0/27 counters err

Port        Align-Err     FCS-Err    Xmit-Err     Rcv-Err  UnderSize  OutDiscards
Gi2/0/27            0           1           0       10134          0            0

Port      Single-Col  Multi-Col   Late-Col  Excess-Col  Carri-Sen      Runts     Giants
Gi2/0/27           0          0          0           0          0          0          0

有时界面关闭并在另一侧自动上升。

这是我的日志：

W-Floor-2#sh log
Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.



No Inactive Message Discriminator.


    Console logging: level debugging, 95104 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 329 messages logged, xml disabled,
                     filtering disabled
    Buffer logging:  level debugging, 95104 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level informational, 92800 message lines logged
        Logging Source-Interface:       VRF Name:

Log Buffer (4096 bytes):
.0 dBm. (SW-Floor-2-3)
Nov 28 21:20:34: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low warning; Operating value: -18.9 dBm, Threshold value: -17.0 dBm.
Nov 28 21:24:13: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.3 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 21:24:15: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.3 dBm, Threshold value: -19.0 dBm.
Nov 28 21:28:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/51, changed state to down
Nov 28 21:28:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/51, changed state to up
Nov 28 21:30:34: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-3)
Nov 28 21:30:36: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm.
Nov 28 21:32:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to down
Nov 28 21:32:41: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to down
Nov 28 21:34:15: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.5 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 21:34:17: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.5 dBm, Threshold value: -19.0 dBm.
Nov 28 21:40:37: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-3)
Nov 28 21:40:39: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm.
Nov 28 21:44:17: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 21:44:19: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm.
Nov 28 21:47:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/3, changed state to down
Nov 28 21:47:55: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/3, changed state to down
Nov 28 21:47:58: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/3, changed state to up
Nov 28 21:47:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/3, changed state to up
Nov 28 21:50:39: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -20.0 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-3)
Nov 28 21:50:41: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -20.0 dBm, Threshold value: -19.0 dBm.
Nov 28 21:54:19: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 21:54:21: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm.
Nov 28 22:00:41: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -20.0 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-3)
Nov 28 22:00:43: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -20.0 dBm, Threshold value: -19.0 dBm.
Nov 28 22:04:21: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.6 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 22:04:23: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.6 dBm, Threshold value: -19.0 dBm.
Nov 28 22:10:43: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-3)
Nov 28 22:10:45: %SFF8472-5-THRESHOLD_VIOLATION: Gi3/0/51: Rx power low alarm; Operating value: -19.4 dBm, Threshold value: -19.0 dBm.
Nov 28 22:14:23: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm. (SW-Floor-2-2)
Nov 28 22:14:25: %SFF8472-5-THRESHOLD_VIOLATION: Gi2/0/27: Rx power low alarm; Operating value: -19.8 dBm, Threshold value: -19.0 dBm.





SW-Floor-2#show controllers ethernet-controller gig 1/0/27

     Transmit GigabitEthernet1/0/27           Receive
   3079381646 Bytes                       1150071762 Bytes
    169736103 Unicast frames               157574604 Unicast frames
      3325069 Multicast frames                513275 Multicast frames
       939914 Broadcast frames                258543 Broadcast frames
            0 Too old frames               313695412 Unicast bytes
            0 Deferred frames               79832894 Multicast bytes
            0 MTU exceeded frames           29254751 Broadcast bytes
            0 1 collision frames                   0 Alignment errors
            0 2 collision frames                  82 FCS errors
            0 3 collision frames                   0 Oversize frames
            0 4 collision frames                   0 Undersize frames
            0 5 collision frames                  19 Collision fragments
            0 6 collision frames
            0 7 collision frames               24108 Minimum size frames
            0 8 collision frames            54768642 65 to 127 byte frames
            0 9 collision frames            50404995 128 to 255 byte frames
            0 10 collision frames            5592659 256 to 511 byte frames
            0 11 collision frames            3267416 512 to 1023 byte frames
            0 12 collision frames           44348443 1024 to 1518 byte frames
            0 13 collision frames                  0 Overrun frames
            0 14 collision frames                  0 Pause frames
            0 15 collision frames
            0 Excessive collisions             89236 Symbol error frames
            0 Late collisions                    251 Invalid frames, too large
            0 VLAN discard frames              29197 Valid frames, too large
            0 Excess defer frames                 48 Invalid frames, too small
       114355 64 byte frames                       0 Valid frames, too small
     46406323 127 byte frames
     48216664 255 byte frames                      0 Too old frames
      5748932 511 byte frames                      0 Valid oversize frames
      3592061 1023 byte frames                     0 System FCS error frames
     69828220 1518 byte frames                     0 RxPortFifoFull drop frame
        94531 Too large frames
            0 Good (1 coll) frames
            0 Good (>1 coll) frames

我检查了两边的双工及其设置的全双工。我更换了跳线，更换了 SFP 模块，但问题仍然存在。

请帮忙。

对不起我的英语不好。

2个回答

你没有足够的力量。如果您更换了 SFP 和跳线，则需要尝试不同的水平光纤。您可能在光纤接线板上有不良的光纤端接。我会在那里找一家电缆供应商对光纤进行一些测试并纠正发现的任何问题。他们将拥有适当的测试设备。

始终从第 1 层开始进行故障排除。

端口 Gi2/0/27 和 Gi3/0/51 上的接收功率水平太低，无法进行可靠传输。正如 Ron 已经指出的，这是一个第一层问题。当超出功率预算时，您需要增加预算或降低衰减。

功率损耗/衰减可能由以下原因引起：

  • 过长
  • 不合适的光纤类型
  • 不良接头
  • 脏污或损坏的光纤连接器
  • 光纤弯曲半径低于公差
  • 有缺陷的收发器
  • 单模/多模光纤类型失配
  • 不良/缺失模式调节
  • APC/SPC 端面不匹配
  • PHY 不适合光纤类型/长度

还要检查相反方向的光纤/远端端口是否存在相同问题，指示一般问题（长度、系统不匹配），而不是端口特定问题（污垢、损坏）。

如果您可以排除所有这些 - 特别是潜在的不匹配 - 您可以选择具有更高功率预算的 PHY 类型，它可能能够处理光纤的衰减。例如，您可以使用 -EX 或 -ZX 来代替 1000BASE-LX(10)。有关更具体的信息，您需要在问题中添加有关使用的光纤类型、长度和 SFP 类型的详细信息。

其它你可能感兴趣的问题
上一篇是否可以同时将 syslog 和 SNMP 陷阱发送到两个不同的地址？ 下一篇数据路径中的vlan标签在哪里变化？