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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Field Name<br />

Bundle status<br />

(MLPPP) or<br />

Multilink class<br />

status (Multiclass<br />

MLPPP)<br />

Field Description<br />

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

Information about bundle status:<br />

• Remote MRRU—MRRU value received from remote peer. If negotiation has<br />

not been initiated, the default value is displayed.<br />

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

Chapter 22: Link Services Interface Operational Mode <strong>Command</strong>s<br />

• Transmitted 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 within a single link. This event indicates that an individual link within<br />

a bundle reordered traffic, making the multilink interface unable to correctly<br />

process the resulting stream.<br />

• Out-of-range sequence number—Received a frame 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 />

841

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

Saved successfully!

Ooh no, something went wrong!