Does MPLS ping support fragmented packets

0

MPLS ping of the AR router does not support fragmented packets.

Other related questions:
Principles of ping packet fragmentation tests
Question: During routine troubleshooting, some customers require that the results of pinging large packets are used to estimate link performance for handling Ethernet service packet loss or bandwidth insufficiency problems. Generally, they require that the packets with a length of 65,500 bytes can be pinged. However, they do not tell the test principles and emphasize that the tests, especially tests for private line VIP customers, must meet this requirement. Test method: ping ip -l 65500 Answer: The following analyzes the test from the four indicators of an Ethernet performance test: 1. Packet loss rate A PC can ping a packet containing a maximum of 65,500 bytes, but the default MTU value of a PC is 1500. Therefore, the large packet needs to be fragmented before the ping operation. The PC can ping a maximum of 1472 bytes without fragmentation. Assume that the large packet is fragmented by 1472 bytes. In this case, at least 45 packets (the result of 65500 divided by 1472 is about 45) need to be sent to the peer end for the ping test. The ping operation is successful only after all the 45 packets are sent to the peer end and the peer end returns an ICMP response. It can be deduced that the possibility of the failure to ping large packets is greater than the possibility of the failure to ping small packets. To perform this test, you need to first ensure that the pinged small packets are not lost, or even each ping packet must contain 1472 bytes, because the default packet length is only 32 bytes. 2. Throughput 65,500 bytes x 8 = 524 kbits. The minimum granularity of an MSTP service is 2 Mbit/s, and the default timeout interval of the ping test is 4 seconds. However, if there is other service traffic during the test, the ping operation may fail. 3. Latency In contrast to the test without fragmentation, the latency of the test requiring fragmentation is larger. The ping test interval, which is 4 seconds by default, is sufficient only if the bandwidth meets requirements. 4. Back to back According to a local mirroring analysis, pinging a packet of 60,000 bytes can be completed in 0.02 seconds after the PC fragments the packet, and the burst traffic reaches 500 kbit/0.01s, equivalent to 50 Mbit/s. According to the analysis of throughput, a packet of 65,500 bytes requires only a bandwidth of 524 kbit/s. Therefore, the test principle is similar to that of the back-to-back system. Suggestion and conclusion: 1. The MSTP service provides a hard pipe, and the service rate is less than 100 Mbit/s or 10 Mbit/s. The minimum granularity is 2 Mbit/s. When the burst traffic exceeds the pipe rate during the large packet ping, the board buffer is required. After the buffer is full, the overflow data will be discarded. Therefore, the test on a board with small buffer cannot meet the requirement. 2. The large packet transmit speed is dependent on the PC processing capability, especially the CPU usage. As a result, sometimes a packet of 65,500 bytes can be used in the ping operation but sometimes a packet of only about 20,000 bytes can be used. That is, the performance is not reliable. 3. The EFGT buffer of EoS boards is small and the EFGS buffer is relatively large. Therefore, a packet of 65,500 bytes can be used in the ping operation on boards with an EFGS buffer.

Whether the NAT ALG supports the fragmented packet processing
The NAT ALG does not support the fragmented packet processing.

Are packet fragmentation and reassembly supported by S series switches
S series switches can send fragmented data packets with a large data volume and also reassemble received fragmented packets.

What functions does MPLS ping provide
In MPLS, the control panel used for establishing an LSP cannot detect the failure in data forwarding of the LSP. This makes network maintenance difficult. The MPLS ping mechanism detects LSP errors and locates faulty nodes. Similar to IP ping, MPLS ping checks LSP connectivity through MPLS Echo Request and MPLS Echo Reply messages. These messages are transmitted in User Datagram Protocol (UDP) packets with the port number being 3503. An MPLS Echo Request message carries FEC information to be detected, and is sent along the same LSP as other packets with the same FEC. In this manner, LSP connectivity is checked. In MPLS ping, an MPLS Echo Request message reaches the egress node of the LSP, and the control panel of the egress node checks whether the local LSR is the egress of the FEC. To prevent the egress node from forwarding the received Echo Request message to other nodes, the destination address in the IP header of the Echo Request message is set to 127.0.0.1/8 (the local loopback address), and the TTL value contained in the IP header is set to 1.

Support for MPLS and requirement for a license on an S series switch
Support for MPLS VPN on S series switches (except the S1700) is as follows: - Switch model - Minimum version supporting MPLS VPN - S5710EI - V200R002 (The S5710EI is unavailable in V200R006 and later versions.) - S5700HI - V200R001 (The S5700HI is unavailable in V200R006 and later versions.) - S5710HI - V200R003 (The S5710HI is unavailable in V200R006 and later versions.) - S5720HI - V200R007C10 - S6700EI - V200R005 (The S6700EI is unavailable in V200R006 and later versions.) - S6720EI - V200R008 - S6720S-EI - V200R009 - S7703, S7706, and S7712 - V100R003 - S9700 - V200R001 - S12704 - V200R008 - S12708 and S12712 - V200R005 - S12710 - V200R010 - S9303, S9306, and S9312 - V100R002 - S9310 - V200R010 - S9300E - V200R002 Note: For a modular switch, a license is required for MPLS. For a fixed switch, no license is required for MPLS.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top