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.

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

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

Field Name<br />

Statistics<br />

NCP state<br />

Protocol<br />

MTU<br />

Generation<br />

Route Table<br />

Flags<br />

Addresses, Flags<br />

Destination<br />

842<br />

Field Description<br />

Information about fragments and packets received and sent by the router. All<br />

references to traffic direction (input or output) are defined with respect to the<br />

router. Input fragments received by the router are assembled into input packets;<br />

output packets are segmented into output fragments for transmission out of<br />

the router. Each field has columns that indicate the number of frames received<br />

and transmitted, frames per second (fps), the number of bytes received and<br />

transmitted, and bits per second (bps).<br />

• Bundle—Information for each active bundle link.<br />

• Fragments: Input and Output—Total number and rate of fragments received<br />

and transmitted.<br />

• Packets: Input and Output—Total number and rate of packets received and<br />

transmitted.<br />

• Multilink class—(Multiclass MLPPP only) Information about multiclass<br />

links used in the multilink operation.<br />

• Link—Information about links used in the multilink operation.<br />

• Link name—Interface name of the link services IQ channel and state<br />

information (physical link up or down).<br />

• Input and Output—Total number and rate of fragments and packets received<br />

and transmitted.<br />

(PPP) Network Control Protocol state.<br />

• Conf-ack-received—Acknowledgement was received.<br />

• Conf-ack-sent—Acknowledgement was sent.<br />

• Conf-req-sent—Request was sent.<br />

• Down—NCP negotiation is incomplete (not yet completed or has failed).<br />

• Not-configured—NCP is not configured on the interface.<br />

• Opened—NCP negotiation is successful.<br />

Protocol family configured on the logical interface.<br />

MTU size on the logical interface. If the MTU value is negotiated down to meet<br />

the MRRU requirement on the remote side, this value is marked Adjusted.<br />

Unique number for use by <strong>Juniper</strong> <strong>Networks</strong> technical support only.<br />

Routing table in which this address exists. For example, Route table:0 refers to<br />

inet.0.<br />

Information about the protocol family flags. Possible values are described in<br />

the “Family Flags” section under “Common Output Fields Description” on<br />

page 125.<br />

Information about the addresses configured on the logical interface. Possible<br />

values are described in the “Addresses Flags” section under “Common Output<br />

Fields Description” on page 125.<br />

IP address of the remote side of the connection.<br />

Level of Output<br />

detail extensive<br />

detail extensive none<br />

detail extensive none<br />

detail extensive none<br />

detail extensive<br />

detail extensive<br />

detail extensive none<br />

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