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 145: Link Services show interfaces Output Fields (continued)<br />

Field Name<br />

Multilink Frame<br />

Relay UNI NNI<br />

active bundle links<br />

statistics<br />

(continued)<br />

Frame exceptions<br />

Buffering<br />

exceptions<br />

824<br />

Field Description<br />

• LIP—Link Interleaving Protocol information.<br />

• Rcv—Number of messages received.<br />

• Xmt—Number of messages transmitted.<br />

• add_lnk—ADD__LINK message notifies the peer endpoint that the local<br />

endpoint supports frame processing. It is generated on both ends of a bundle<br />

link when a bundle link endpoint is ready to become operational.<br />

• lnk_ack—ADD_LINK_ACK message notifies the peer that the local router has<br />

received a valid ADD_LINK message.<br />

• lnk_rej—ADD_LINK_REJ message notifies the peer that the local router has<br />

received an invalid ADD_LINK message.<br />

• hello—HELLO message notifies the peer that the local router is up. Both ends<br />

of a link bundle generate this message.<br />

• hel_ack—HELLO_ACK message notifies the peer that the local router has<br />

received a valid HELLO message.<br />

• lnk_rem—REMOVE_LINK message notifies the peer that the local router has<br />

received a REMOVE_LINK message.<br />

• rem_ack—REMOVE_LINK_ACK message notifies the peer that the local router<br />

has received a valid ADD_LINK message.<br />

For Multilink Frame Relay end-to-end only. Information about framing<br />

exceptions. Includes events recorded under Exception Events for each logical<br />

interface.<br />

• Oversized frames—Number of frames received that exceed maximum frame<br />

length. Maximum length is 4500 Kb (kilobits).<br />

• Errored input frames—Number of input frame errors.<br />

• Input on disabled link/bundle—Number of frames received on disabled links.<br />

These frames can result either from an inconsistent configuration, or from a<br />

bundle or link being brought up or down with traffic actively flowing through<br />

it.<br />

• Output for disabled link/bundle—Number of frames sent for a disabled or<br />

unavailable link. These frames can result either from an inconsistent<br />

configuration, or from a bundle being brought up or down while traffic is<br />

flowing through it.<br />

• Queuing drops—Total number of packets dropped before traffic enters the<br />

link services IQ interface. Indicates that the interface is becoming<br />

oversubscribed.<br />

For Multilink Frame Relay end-to-end only. Information about buffering<br />

exceptions. Includes events recorded under Exception Events for each logical<br />

interface:<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<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 interface capacity. Check the logical interface exception event<br />

counters to determine which bundle is responsible.<br />

Level of Output<br />

detail extensive<br />

detail extensive<br />

detail extensive<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!