Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

show services inline ip-reassembly statistics

Syntax

Description

Display the inline IP reassembly statistics for the Packet Forwarding Engines on one or more MPCs or Next Gen Services MX-SPC3 services card. Inline IP reassembly statistics are collected at the Packet Forwarding Engine level.

Note:

For more information on MPCs that support inline IP reassembly, refer to Protocols and Applications Supported on the MPC1E for MX Series Routers.

Options

none

Displays standard inline IP reassembly statistics for all MPCs or MX-SPC3 services card.

fpc fpc

(Optional) Displays inline IP reassembly statistics for the specified MPC or MX-SPC3 services card.

Note:

Starting with Junos OS Release 14.2, the FPC option is not displayed for MX Series routers that do not contain switch fabrics, such as MX80 and MX104 routers.

pfe pfe

(Optional) Displays inline IP reassembly for the specified Packet Forwarding Engine slot. You must specify an FPC slot number before specifying a Packet Forwarding Engine slot.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show services inline ip-reassembly statistics command. Output fields are listed in the approximate order in which they appear.

Table 1: show services inline ip-reassembly statistics Output Fields

Field Name

Field Description

FPC

MPC or MX-SPC3 services card slot number for which the statistics are displayed.

PFE

Packet Forwarding Engine on the MPC or MX-SPC3 services card for which the statistics are displayed.

Note:

The output fields displayed (per Packet Forwarding Engine) are arranged in a logical sequence from top to bottom to enable users to understand how the inline IP reassembly statistics are gathered.

The information about total number of fragments received is displayed first, and then the information about the reassembled packets and those pending reassembly are displayed. Then, the reasons why the fragments were dropped or not reassembled are displayed. Finally, the information about the fragments reassembled, fragments dropped, and fragments sent to the backup user plane PIC (services PIC) are displayed.

Total Fragments Received

Total number of fragments received and the current rate of fragments received for inline IP reassembly. The following information is also displayed:

  • First Fragments—Number of first fragments received and current rate of first fragments processed.

  • Intermediate Fragments—Number of intermediate fragments received and current rate of intermediate fragments processed.

  • Last Fragments—Number and rate of last fragments received.

Note:

Current rate refers to the current number of fragments processed per second in the instant preceding the command’s execution.

Total Packets Reassembled

Total number of packets reassembled and current rate, in the instant preceding the command’s execution, at which the packets are reassembled.

Approximate Packets Pending Reassembly

Approximate number of packets pending reassembly.

Fragments Dropped Reasons

Total number of fragments dropped reasons and the current rate of total fragment dropped reasons. The number of dropped reasons and rate corresponding to each of the following reasons are also displayed:

  • Buffers not available

  • Fragments per packet exceeded

  • Packet length exceeded

  • Record insert error

  • Record in use error

  • Duplicate first fragments

  • Duplicate last fragments

  • Missing first fragment

Note:
  • These fields indicate why a fragment was dropped. When a fragment is dropped, the corresponding reason field is incremented by 1. For example, when a fragment is dropped because the memory runs out, the Buffers not available field increases by 1.

  • The maximum number of fragments allowed for reassembly is 16. If the interface encounters a 17th fragment, it drops the entire packet and increments the Fragment per packet exceeded field by 17.

  • Current rate refers to the current number of fragment dropped reasons per second in the instant preceding the command’s execution.

Reassembly Errors Reasons

Number of errors during reassembly and the current rate of reassembly errors. The number of errors and the rate for each of the following types of errors are also displayed:

  • Fragment not found

  • Fragment not in sequence

  • ASIC errors

Note:

Current rate refers to the current number of reassembly errors processed per second in the instant preceding the command’s execution.

Aged out packets

Number of aged out packets and the current number of packets aged out per second in the instant preceding the command’s execution.

Note:

In some cases, aged out packets can refer to aged out fragments. If previous fragments of the packet have already been discarded then linking of the dropped fragments to the aged out fragments cannot occur.

Total Fragments Successfully Reassembled

Number of fragments successfully reassembled and the current number of fragments reassembled per second in the instant preceding the command’s execution.

Total Fragments Dropped

Total number of fragments dropped and the current rate of total number of fragments dropped. The number of fragments dropped and rate corresponding to each of the following reasons are also displayed:

  • Buffers not available

  • Fragments per packet exceeded

  • Packet length exceeded

  • Record insert error

  • Record in use error

  • Duplicate first fragments

  • Duplicate last fragments

  • Missing first fragment

  • Fragment not found

  • Fragment not in sequence

  • ASIC errors

  • Aged out fragments

Total fragments punted to UPIC

Number of fragments sent to the backup user plane PIC (services PIC) and current rate of fragments sent per second in the instant preceding the command’s execution

The following information applies to the Total Fragments Dropped field.

  • These fields indicate how many of the packet fragments received were then dropped due to a particular reason.

    For example, consider a packet that has 10 fragments, 9 of which have been received and stored in memory. When the tenth fragment arrives, if the memory runs out (Buffers not available), then this fragment is dropped. Because the tenth fragment has been dropped, the other 9 fragments must also be dropped. In this case, the Buffers not available field (under the Fragments Dropped Reasons field) is incremented by 1 and the Buffers not available field (under the Total Fragments Dropped field) is incremented by 10.

    For the next packet arriving, which also has 10 fragments, the first four fragments are stored but the memory runs out for the fifth fragment. Then the first 5 fragments (fifth and the first four) are dropped. In this case, the Buffers not available field (under the Fragments Dropped Reasons field) is incremented by 1 and the Buffers not available field (under the Total Fragments Dropped field) is incremented by 5.

    For fragments of the packet, if memory becomes available, the next 5 fragments (6 through 10) that arrive are stored in memory. The fragments are stored until the timeout period elapses, and are eventually dropped. In this case, the Aged out packets field is incremented by 1 and the Aged out fragments field (under the Total Fragments Dropped field) is incremented by 5.

    The fragment counters (after both packets have been processed) are as follows:

    • Fragments Dropped Reasons

      • Buffers not available 2

      • Aged out packets 1

    • Total Fragment Dropped

      • Buffers not available 15

      • Aged out packets 5

  • Current rate refers to the current total number fragments dropped per second in the instant preceding the command’s execution.

Sample Output

show services inline ip-reassembly statistics fpc

Release Information

Statement introduced in Junos OS Release 12.2X49.

Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480 and MX960 with the MX-SPC3 services card.