跳转到主内容

Exciting new changes are coming to the Knowledge Base site soon!
Starting April 4, 2023, you will notice Support-Specific categorization and improvements to the search filters on the site. In May, we will be launching a new and enhanced Site UI and Navigation. To know more, read our Knowledge Article.

netif.linkErrors :网络接口上的链路错误过多

Views:
24
Visibility:
Public
Votes:
0
Category:
aff-series<a>netif.linkErrors</a><a>2008601371</a><a>交换机接口</a>
Specialty:
hw
Last Updated:

适用场景

在 CNA 以太网端口中具有 SFP 的所有 FAS 和 AFF 系统。

问题描述

  • EMS 错误: 

Wed Dec 21 07:50:26 +0900 [Node-02: intr: netif.linkErrors:error]: Excessive link errors on network interface e0a. Might indicate a bad cable, switch port, or NIC, or that a cable connector is not fully inserted in a socket. On a 10/100 port, might indicate a duplex mismatch.
 

  • 运行状况警报:
         Node: node_name
      Resource: Ethernet1/29/1
      Severity: Major
  Indication Time: Mon Jan 04 16:15:33 2021
      Suppress: false
     Acknowledge: false
   Probable Cause: The percentage of inbound packet errors of switch interface
          "switch_name(XXXXXXXXXXX)/Ethernet1/29/1" is above the warning threshold.
  Possible Effect: Communication between nodes in the cluster might be degraded.
Corrective Actions: 1) Migrate any cluster LIF that uses this connection to another port connected to a cluster switch.            For example, if cluster LIF "clus1" is on port e0a and the other LIF is on e0b, run the following             command to move "clus1" to e0b: "network interface migrate -vserver vs1 -lif clus1 -sourcenode node1           -destnode node1 -dest-port e0b"
           2) Replace the network cable with a known-good cable.
           If errors are corrected, stop. No further action is required. Otherwise, continue to Step 3.
           3) Move the network cable to another port on the node (if available). Migrate the cluster LIF to             the new port.
           If errors are corrected, contact technical support to troubleshoot the original node port.
           Otherwise, continue to Step 4.
           4) Move the network cable to another available cluster switch port.
           Migrate the cluster LIF back to the original port.
           If errors are corrected, contact technical support to troubleshoot the original switch port.
           If errors persist, contact technical support for further assistance.
  • 受影响端口的交换机输出:
switch# show interface ethernet1/30/1
Ethernet1/30/1 is up
admin state is up, Dedicated Interface
Hardware: 1000/10000 Ethernet, address: c4b2.3923.44be (bia c4b2.3923.44be)
MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is access
full-duplex, 10 Gb/s, media type is 40G
Beacon is turned off
Auto-Negotiation is turned on FEC mode is Auto
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
Last link flapped 2d01h
Last clearing of "show interface" counters never
2 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 128 bits/sec, 0 packets/sec
30 seconds output rate 488 bits/sec, 0 packets/sec
input rate 128 bps, 0 pps; output rate 488 bps, 0 pps
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 56 bits/sec, 0 packets/sec
300 seconds output rate 240 bits/sec, 0 packets/sec
input rate 56 bps, 0 pps; output rate 240 bps, 0 pps
RX
8411106309 unicast packets 967656 multicast packets 13768 broadcast packets
8412087733 input packets 43163351724834 bytes
5217690361 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 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
7770700631 unicast packets 13544676 multicast packets 49080 broadcast packets
7784294387 output packets 38422960748860 bytes
4654752709 jumbo packets
3026723 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
 
switch# show interface ethernet1/29/1
Ethernet1/29/1 is up
admin state is up, Dedicated Interface
Hardware: 1000/10000 Ethernet, address: c4b2.3923.44ba (bia c4b2.3923.44ba)
MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is access
full-duplex, 10 Gb/s, media type is 40G
Beacon is turned off
Auto-Negotiation is turned on FEC mode is Auto
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
Last link flapped 31week(s) 6day(s)
Last clearing of "show interface" counters never
5 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 56 bits/sec, 0 packets/sec
30 seconds output rate 536 bits/sec, 0 packets/sec
input rate 56 bps, 0 pps; output rate 536 bps, 0 pps
Load-Interval #2: 5 minute (300 seconds)
300 seconds input rate 56 bits/sec, 0 packets/sec
300 seconds output rate 240 bits/sec, 0 packets/sec
input rate 56 bps, 0 pps; output rate 240 bps, 0 pps
RX
7713969836 unicast packets 967594 multicast packets 17685 broadcast packets
7714955115 input packets 38161937396451 bytes
4627068033 jumbo packets 0 storm suppression packets
699 runts 0 giants 3070040 CRC 0 no buffer
3312963 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
8387321873 unicast packets 13544593 multicast packets 45130 broadcast packets
8400911596 output packets 43070148619178 bytes
5206464024 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

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device