基本思路：快速全局查看ERROR；通过诊断文件定位端口；清空计数观测是否CRC错误在增加
一、快速查看全局下是否存在H3C交换端口下数据包ERROR
#### 第一步：快速整体查看 ERROR
<H3C-SW>dis interface | include error
#### dis interface | include error 命令查看是否存在很多ERROR 下面看到的很多ERROR，需要定位是哪个端口
<H3C-SW>dis interface | include error
Input: 59 input errors, 2 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 2 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 2 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 25 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 16 input errors, 2 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 24 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
.............................
input: 0 input errors, 0 runts, 0 giants,- throttles, 0 CRC
0 frame, 0 overruns,- aborts,- ignored,- parity errors
output: 0 output errors, 0 underruns,- buffer failures
Input: 24 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 2 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 2 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 24 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 16 input errors, 2 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
Input: 24 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
.......................................
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
- ignored, - parity errors
Output: 0 output errors, - underruns, - buffer failures
<H3C-SW>
二、通过H3C交换机的诊断文件定位物理端口
#### 第二步：通过display diagnostic-information 生成诊断文件，ftp下载到本地，通过UE的行查找功能定位到具体的物理端口
H3C-SW>display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:y
Please input the file name(*.tar.gz)[flash:/diag_H3C-SW_20230211-182620.tar.gz]:
Diagnostic information is outputting to flash:/diag_H3C-SW_20230211-182620.tar.gz.
Please wait...
Save successfully.
<H3C-SW>
<H3C-SW>ftp 141.36.80.114
Press CTRL+C to abort.
Connected to 141.36.80.114 (141.36.80.114).
220 3Com 3CDaemon FTP Server Version 2.0
User (141.36.80.114:(none)): ftp
331 User name ok, need password
Password: ## 输入目标ftp服务器的ftp账号密码
230 User logged in
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> put diag_H3C-SW_20230211-182620.tar.gz #下载诊断文件到本地
ftp> dir
-rwxrwxrwx 1 owner group 325508 Feb 11 18:29 diag_H3C-SW_20230211-182620.tar.gz
## 用UE打开诊断文件，搜索CRC关键字，显示出所在行。看到有CRC错误双击就可以看到具体的物理接口，见下图
三、清空端口CRC计数观测错误数是否不停增加
在CRC错误包比较多的端口模式下，清空端口CRC计数，观测错误数是否不停增加，如果不停增加必须去处理端口模块和跳线等物理硬件的问题，确保CRC不增加，让硬件运行稳定了。
#### 清空计数的命令
<H3C-SW>reset counter inter
#### 查看端口的CRC情况
<H3C-SW>dis int xge2/2/0/22
Ten-GigabitEthernet2/2/0/22
Current state: UP
Line protocol state: UP
.......................
Input (total): 1239948 packets, 187207326 bytes
657163 unicasts, 505969 broadcasts, 76813 multicasts, 0 pauses
Input (normal): 1239945 packets, - bytes
657163 unicasts, 505969 broadcasts, 76813 multicasts, 0 pauses
Input: 3 input errors, 0 runts, 0 giants, 0 throttles
3 CRC, 0 frame, - overruns, 0 aborts ##此处还是有CRC的错误报告
- ignored, - parity errors
Output (total): 32289813 packets, 2249660780 bytes
31247562 unicasts, 990266 broadcasts, 51985 multicasts, 0 pauses
Output (normal): 32289813 packets, - bytes
31247562 unicasts, 990266 broadcasts, 51985 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
IPv4 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
IPv6 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
<H3C-SW>reset counter inter xge2/2/0/22