已解决: 3560X接口狂闪绿灯

Xingxing Zhang · ‎05-17-2015

本帖最后由 zhang00xing00 于 2015-5-17 17:49 编辑
3560X接口狂闪绿灯，包括连接核心交换机、连接路由器、连接PC的接口，闪动的特别频繁。
debug ip packet发现下面信息，其中172.17.210.1是二层交换机3560X的管理IP，172.17.210.251是内网的MCU地址，为什么会抓到的全是二者之间的数据包呢？

*Mar  1 00:56:34.693: IP: tableid=0, s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), routed via FIB
*Mar  1 00:56:34.701: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending
*Mar  1 00:56:34.701:     ICMP type=5, code=1
*Mar  1 00:56:34.701: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature
*Mar  1 00:56:34.701:     ICMP type=5, code=1, Input interface drop(61), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:34.701: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature
*Mar  1 00:56:34.701:     ICMP type=5, code=1, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:34.701: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packet
*Mar  1 00:56:34.701:     ICMP type=5, code=1pak 4A2AB78 consumed in input feature , packet consumed, MCI Check(63), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature
*Mar  1 00:56:35.205:     ICMP type=5, code=1, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature
*Mar  1 00:56:35.205:     ICMP type=5, code=1, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.205: FIBipv4-packet-proc: route packet from (local) src 172.17.210.1 dst 172.17.210.251
*Mar  1 00:56:35.205: FIBipv4-packet-proc: packet routing succeeded
*Mar  1 00:56:35.205: IP: tableid=0, s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), routed via FIB
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending
*Mar  1 00:56:35.205:     ICMP type=5, code=1
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature
*Mar  1 00:56:35.205:     ICMP type=5, code=1, Input interface drop(61), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature
*Mar  1 00:56:35.205:     ICMP type=5, code=1, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.205: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packet
*Mar  1 00:56:35.205:     ICMP type=5, code=1
*Mar  1 00:56:35.565: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1, changed state to up
*Mar  1 00:56:35.716: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature
*Mar  1 00:56:35.716:     ICMP type=5, code=1, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.716: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature
*Mar  1 00:56:35.716:     ICMP type=5, code=1, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 00:56:35.716: FIBipv4-packet-proc: route packet from (local) src 172.17.210.1 dst 172.17.210.251
*Mar  1 00:56:35.716: FIBipv4-packet-proc: packet routing succeeded

cumtcisco · ‎05-17-2015

FIBipv4-packet-proc: packet routing succeeded 路由没有问题
ICMP type=5, code=1 说明是主机重定向问题

在原帖中查看解决方案

cumtcisco · ‎05-17-2015

FIBipv4-packet-proc: packet routing succeeded 路由没有问题
ICMP type=5, code=1 说明是主机重定向问题

Xingxing Zhang · ‎05-17-2015

cumtcisco 发表于 2015-5-18 09:19
FIBipv4-packet-proc: packet routing succeeded 路由没有问题
ICMP type=5, code=1 说明是主机重定向 ...

参考下面这段log能看出什么问题吗，同一时间爬取的。


*Mar  1 01:08:00.042: IP: tableid=0, s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), routed via FIB
*Mar  1 01:08:00.042: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending
*Mar  1 01:08:00.042: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Input interface drop(61), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:00.042: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:00.042: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packet
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local fLeSE 
a*Mar  1 01:08:00.t545: IP: tableid=0, s=1u72.17.210.1 (local), d=172.17.210.251 (Vlan20), routed via FIB
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251re, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FA (Vlan20), len 56, sending
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Input interface drop(61), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:00.545: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packet
*Mar  1 01:08:01.049: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.049: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.049: IP: tableid=0, s=172.17.210.1 (local), d=172.17.210.251 (Vlan20)us FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.057: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feat,ure routed via FIB
*Mar  1 01:08:01.049: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending
*Mar  1 01:08:01.057: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Input interface drop(61), rtype 1, for, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.057: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packet
*Mar  1 01:08:01.569: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.569: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.569: IP: tableid=0, s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), routed via FIB
*Mar  1 01:08:01.569: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending
*Mar  1 01:08:01.569: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, nsumed in input feature , packeot consumed, MCI Check(63), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE utput feature, Input interface drop(61), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.569: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, output feature, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:01.577: IP: s=172.17.210.1 (local), d=172.17.210.251 (Vlan20), len 56, sending full packetpak 4A33104 co
*Mar  1 01:08:02.081: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE 
*Mar  1 01:08:02.081: IP: s=172.17.210.1 (local), d=172.17.210.251, len 56, local feature, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE

blgao · ‎05-18-2015

error message 提示有MTU为0的包。。

Xingxing Zhang · ‎05-18-2015

本帖最后由 zhang00xing00 于 2015-5-19 00:04 编辑

blakegao 发表于 2015-5-18 21:49
error message 提示有MTU为0的包。。

MTU=0 跟ATM路由器有关系吗？
网络拓扑是这样的：
ATM专线------(ATM OC3 POM)路由器-----3560X(172.10.210.1)-----SW-----MCU(172.17.210.251)
ATM接口配置如下：

interface ATM3/0.19 point-to-point
 description new XXXX
 ip address 172.17.xx.xx 255.255.255.252
 no atm enable-ilmi-trap
 pvc XXXX  8/789 
  protocol ip 172.17.XX.XX broadcast
  encapsulation aal5snap
 !

Xingxing Zhang · ‎05-18-2015

现在一点思路没有，同一个网段同一个VLAN之间怎么还查询FIB表呢？应该可以通过二层MAC地址表转发啊。

*Mar  1 00:56:41.857: FIBipv4-packet-proc: route packet from (local) src 172.17.210.1 dst 172.17.210.251
*Mar  1 00:56:41.857: FIBipv4-packet-proc: packet routing succeeded

huoran1234 · ‎05-18-2015

没看懂问题是什么。。闪绿灯不是正常的么，说明有数据包在传输。

cumtcisco · ‎05-18-2015

huoran1234 发表于 2015-5-19 09:49
没看懂问题是什么。。闪绿灯不是正常的么，说明有数据包在传输。

现在是狂闪

cumtcisco · ‎05-18-2015

我还是觉得是ICMP重定向的问题，可以先关闭试一试

Xingxing Zhang · ‎05-18-2015

cumtcisco 发表于 2015-5-19 11:37
现在是狂闪

UP的接口狂闪，看的我心都慌了，明显是不正常的。
目前交换机能正常转发数据。

huoran1234 · ‎05-18-2015

zhang00xing00 发表于 2015-5-19 11:54
UP的接口狂闪，看的我心都慌了，明显是不正常的。
目前交换机能正常转发数据。

看看交换机的CPU使用率？再看看狂闪的接口的流量？