14.12.2012 Views

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Junos</strong> <strong>OS</strong> 12.1 <strong>Interfaces</strong> <strong>Command</strong> <strong>Reference</strong><br />

Table 148: show interfaces (Redundant Link Services IQ) Output Fields (continued)<br />

Field Name<br />

Bundle status<br />

(MLPPP)<br />

874<br />

Field Description<br />

Information about bundle status:<br />

• Received sequence number—Sequence number for received packets.<br />

• Transmit sequence number—Sequence number for transmitted packets.<br />

• Packet drops—Number and byte count of output packets that were dropped,<br />

rather than being encapsulated and sent out of the router as fragments. The<br />

packet drop counter is incremented if there is a temporary shortage of packet<br />

memory on the AS PIC, which causes packet fragmentation to fail.<br />

• Fragment drops—Number and byte count of input fragments that were<br />

dropped, rather than being reassembled and handled by the router as packets.<br />

This counter also includes fragments that have been received successfully<br />

but had to be dropped because not all fragments that constituted a packet<br />

had been received. The fragment drop counter is incremented when a<br />

fragment received on constituent links is dropped. Drop fragments can be<br />

triggered by sequence ordering errors, duplicate fragments, timed-out<br />

fragments, and bad multilink headers.<br />

• MRRU exceeded—Number of reassembled packets exceeding the MRRU. This<br />

counter is not implemented in this release.<br />

• Fragment timeout—The drop timer expired while a fragment sequence number<br />

was outstanding. Occurs only if the drop timer is enabled. This timeout can<br />

occur if the differential delay across the links in a bundle exceeds the<br />

drop-timer setting, or if a multilink packet is lost in transit while the drop timer<br />

is enabled.<br />

• Missing sequence number—A gap was detected in the sequence numbers of<br />

fragments on a bundle.<br />

• Out-of-order sequence number—Two frames with out-of-order sequence<br />

numbers occurred within a single link. This event indicates that an individual<br />

link within a bundle reordered traffic, making the multilink interface unable<br />

to correctly process the resulting stream.<br />

• Out-of-range sequence number—A frame was received with an out-of-range<br />

sequence number. These events can occur when a large amount of<br />

multilink-encapsulated traffic is lost or the multilink peer is reset, so that a<br />

large jump in sequence numbers results. A small number of these events can<br />

occur when the far end of a bundle is taken down or brought up.<br />

• Packet data buffer overflow—Packet buffer memory is full. This overflow can<br />

occur when the aggregate data rate exceeds the physical link services IQ<br />

interface capacity.<br />

• Fragment data buffer overflow—Fragment buffer memory is full. This overflow<br />

can occur when excessive differential delay is experienced across the links<br />

within a single bundle, or when the aggregate data rate exceeds the physical<br />

link services IQ capacity.<br />

Level of Output<br />

detail extensive none<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!