S6700EI ping the loopback ip address failed with the big packets in the mpls situation

Latest reply: Apr 26, 2017 01:58:25 1128 1 0 0

S6700EI is PE or P of the IP/MPLS backbone network. If the customer tried to ping the loopback IP address with packet’s size 7000byte, the last packet always dropped .And at the same time there is cpu-defend drop statistic under mpls-fib-hit. However the customer tried to ping the interface IP address with packet’s size 7000byte, it is always successful and no drop statistic under mpls-fib-hit.

(1)ping the loopback IP address:

[Switch]ping -f -s 7000 1.1.1.1                                           

  PING 1.1.1.1: 7000  data bytes, press CTRL_C to break                         

    Reply from 1.1.1.1: bytes=7000 Sequence=1 ttl=255 time=14 ms               

    Reply from 1.1.1.1: bytes=7000 Sequence=2 ttl=255 time=11 ms               

    Reply from 1.1.1.1: bytes=7000 Sequence=3 ttl=255 time=14 ms                

    Reply from 1.1.1.1: bytes=7000 Sequence=4 ttl=255 time=27 ms               

    Request time out                                                           

                                                                               

  --- 1.1.1.1 ping statistics ---                                              

    5 packet(s) transmitted                                                    

    4 packet(s) received                                                       

    20.00% packet loss                                                         

round-trip min/avg/max = 11/16/27 ms                                       

(2)ping the interface IP address:

[Switch]ping -f -s 7000 100.0.0.2                                         

  PING 100.0.0.2: 7000  data bytes, press CTRL_C to break                      

    Reply from 100.0.0.2: bytes=7000 Sequence=1 ttl=254 time=2 ms              

    Reply from 100.0.0.2: bytes=7000 Sequence=2 ttl=254 time=2 ms              

    Reply from 100.0.0.2: bytes=7000 Sequence=3 ttl=254 time=2 ms              

    Reply from 100.0.0.2: bytes=7000 Sequence=4 ttl=254 time=1 ms              

    Reply from 100.0.0.2: bytes=7000 Sequence=5 ttl=254 time=2 ms              

                                                                                

  --- 100.0.0.2 ping statistics ---                                            

    5 packet(s) transmitted                                                    

    5 packet(s) received                                                        

    0.00% packet loss                                                          

    round-trip min/avg/max = 1/1/2 ms 

 

The software version of S6700EI is V200R005.

This is the topology:

960eb01cf9c54cc889c90c9f4b7691f2

  • x
  • convention:

ms.america
Created Apr 26, 2017 01:58:25 Helpful(0) Helpful(0)

(1)    We checked the cpu-defend statistic and found that when the customer ping the loopback address it matched the packet type of mpls-fib-hit, and there are drop statistics on the packet type of mpls-fib-hit. However, when the customer ping the interface address it matched the packet type of ICMP, and there are no drop statistics on the packet type of ICMP.

(1)the cpu-defend statistic when ping the loopback IP address:

2383872da273474584f3866247c741c1

(2)the cpu-defend statistic when ping the interface IP address:

5d21f4dad2a54e098da3b35523e2ed7d

  

(2)    Why the customer ping different IP address, the ICMP packets matched different packet type. Because the switch only distributes mpls label to the IP host routes with 32-bit addresses by default, and won’t distributes mpls label to the direct route.

The mpls lsp:

f84b9bd66eec47aab0a91f108332425b

The mpls configuration:

4828b8d51bca4208b0055e3b3c6a1a99

 

(3)    The packet will include the mpls head when you ping the loopback address, but the packet won’t include the mpls head when you ping the interface address. The priority of mpls-fib-hit is higher than ICMP, so the packets with the mpls head are matched the packet type of mpls-fib-hit.

 

(4)    Why the last packet always dropped when the customer ping the loopback IP address. Because the cpcar of the packet type of ICMP is larger than mpls-fib-hit.

(1)the cpcar of ICMP:

384276f7c0e14a9d9c00d945883bdc13

(2) the cpcar of mpls-fib-hit:

188ddf343f544aaf89971f26a0e4023d

 

(5)    For huawei switch, the data packets are transferred by the chips, and it won’t affect the business and the ping test is only used to check the network is connected well.

transparent.gif Root Cause

The switch only distributes mpls label to the IP host routes with 32-bit addresses by default, and won’t distributes mpls label to the direct route. The ICMP packets with the mpls head are matched the packet type of mpls-fib-hit, but the ICMP packets without the mpls head are matched the packet type of ICMP. And the cpcar of the packet type of ICMP is larger than mpls-fib-hit.

transparent.gif Solution

This is a normal behavior for our switch and it won’t affect the business.

  • x
  • convention:

Reply

Reply
You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login