debug ip packet acl troubleshoots that packets are discarded when R3680 with source address pings to the address of remote directly-connected equipment.

Publication Date:  2012-07-27 Views:  251 Downloads:  0
Issue Description
Networking map: --(E0130.32.128.1/28) R3680_1 (S3:0130.32.129.13) � (S3:0130.32.129.14) R3680_2―

故障现象:



At R3680_1, the address of 130.32.129.14 with source address of 130.32.128.1/28pingR3680_2 discards packets sometimes.



I. Turn on the switch of debug



Quidway(config)#logging?



bufferedSetbufferedloggingparameters



consoleSetconsolelogginglevel



hostSetlogginghostparameters



monitorSetterminalline(monitor)logginglevel



onEnableloggingtoallsupporteddestinations



Quidway(config)#loggingon



Quidway(config)#loggingmonitor



II. Perform ACL data stream matching



Quidway(config)#access-listnormal100 permitip130.32.128.1 0.0.0.0      130.32.129.14      0.0.0.0



Quidway(config)#access-listnormal100 permitip130.32.129.14      0.0.0.0   130.32.128.1      0.0.0.0



Quidway(config)#access-listnormal100 denyipanyany



III. Turn on debug for ACL



Quidway#debuippacket?







<1-199>Access-listNumber



Quidway#debuippacket100



IV. Perform test:

Quidway#ping-a130.32.128.1 130.32.129.14 

Alarm Information
No

Handling Process
R3680E_1

guangzhou#



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7791,Offset=0,TTL=255,Protocol=1,Chksum=59799



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15697,Offset=0,TTL=255,Protocol=1,Chksum=59799



s=130.32.129.14,d=130.32.128.1,if=Serial3:0,Sending



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7795,Offset=0,TTL=255,Protocol=1,Chksum=58775



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15699,Offset=0,TTL=255,Protocol=1,Chksum=58775



s=130.32.129.14,d=130.32.128.1,if=Serial4:0,Sending



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7801,Offset=0,TTL=255,Protocol=1,Chksum=57239



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15707,Offset=0,TTL=255,Protocol=1,Chksum=57239



s=130.32.129.14,d=130.32.128.1,if=Serial4:0,Sending



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7813,Offset=0,TTL=255,Protocol=1,Chksum=54167



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15711,Offset=0,TTL=255,Protocol=1,Chksum=54167



s=130.32.129.14,d=130.32.128.1,if=Serial3:0,Sending



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7817,Offset=0,TTL=255,Protocol=1,Chksum=53143



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15713,Offset=0,TTL=255,Protocol=1,Chksum=53143



s=130.32.129.14,d=130.32.128.1,if=Serial3:0,Sending



guangzhou#



 According to the test result, the packets that R3680_2 responds to R3680_1 are transmitted via Serial4:0, so R3680_1 cannot receive it. It could be located that the problem arises from route of R3680_2. At R3680_2, set the next hop of the static route to 130.32.128.1/28 to 130.32.129.13, and the problem is solved. Consequently, at R3680_1, the address 130.32.129.14 with source address of 130.32.128.1/28pingR3680_2 will not discard packets then.

 

Root Cause
V. Test result and the solution:

R3680E_1



beijing#ping-a130.32.128.1130.32.129.14



PING130.32.129.14:56databytes,pressCTRL_Ctobreak



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7791,Offset=0,TTL=255,Protocol=1,Chksum=56533



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Sending



Replyfrom130.32.129.14:bytes=56Sequence=0ttl=255time=39ms



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15697,Offset=0,TTL=255,Protocol=1,Chksum=1913



s=130.32.129.14,d=130.32.128.1,if=Serial3:0,Received



Deliveredtohighlevelprotocol.



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7795,Offset=0,TTL=255,Protocol=1,Chksum=0



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Sending



Requesttimeout



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7801,Offset=0,TTL=255,Protocol=1,Chksum=39636



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Sending



Requesttimeout



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=7813,Offset=0,TTL=255,Protocol=1,Chksum=2



s=130.32.128.1,d=130.32.129.14,if=Serial3:0,Sending



Replyfrom130.32.129.14:bytes=56Sequence=3ttl=255time=40ms



IP:Version=4,HdrLen=5,TOS=0,TotalLen=84



ID=15711,Offset=0,TTL=255,Protocol=1,Chksum=63864



s=130.32.129.14,d=130.32.128.1,if=Serial3:0,Received



Replyfrom130.32.129.14:bytes=56Sequence=4ttl=255time=40ms



---130.32.129.14pingstatistics---



5packetstransmitted



3packetsreceived



40.00%packetloss



round-tripmin/avg/max=39/39/40ms



beijing#

 

END