show interfaces (Link Services IQ)

Physical interface

Name of the physical interface.

Enabled

State of the interface. Possible values are described in the “Enabled Field” section under Common Output Fields Description.

Interface index

Physical interface index number, which reflects its initialization sequence.

SNMP ifIndex

SNMP index number for the physical interface.

Generation

Unique number for use by Juniper Networks technical support.

Link-level type

Encapsulation being used on the physical interface: Multilink-Frame-Relay-UNI-NNI Multilink-Frame-Relay-UNI-NNI (default), LinkService, Frame-relay, Frame-relay-ccc, or Frame-relay-tcc.

MTU

Maximum transmission unit size on the physical interface.

Device flags

Information about the physical device. Possible values are described in the “Device Flags” section under Common Output Fields Description.

Interface flags

Information about the interface. Possible values are described in the “Interface Flags” section under Common Output Fields Description.

Last flapped

Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

Multilink Frame Relay UNI NNI bundle options

(Multilink Frame Relay UNI NNI only) Configured information about Multilink Frame Relay bundle options.

• Device type—DCE (data communication equipment) or DTE (data terminal equipment).

• MRRU—Configured size of the maximum received reconstructed unit (MRRU): 1500 to 4500 bytes. The default is 1524 bytes.

• Bandwidth—Speed at which the interface is running.

• Fragmentation threshold—Configured fragmentation threshold: 128 through 16,320 bytes, in integer multiples of 64 bytes. The default setting is 0, which disables fragmentation.

• Red differential delay limit—Red differential delay limit among bundle links has been reached, indicating an action will occur.

• Yellow differential delay limit—Yellow differential delay among bundle links has been reached, indicating a warning will occur.

• Red differential delay action—Type of actions taken when the red differential delay exceeds the red limit: Disable link transmit or Remove link from service.

• Link layer overhead—Percentage of bundle bandwidth to be set aside for link layer overhead.

• Reassembly drop timer—Drop timeout value to provide a recovery mechanism if individual links in the link services bundle drop one or more packets: 1 through 127 milliseconds. By default, the drop timeout parameter is 0 (disabled). A value under 5 ms is not recommended.

• Links needed to sustain bundle—Minimum number of links to sustain the bundle: 1 through 8.

• LIP Hello timer—Link Interleaving Protocol hello timer: 1 through 180 seconds.

  • Acknowledgement timer—Maximum period to wait for an add link acknowledgement, hello acknowledgement, or remove link acknowledgement: 1 through 10 seconds.

  • Acknowledgement retries—Number of retransmission attempts to be made for consecutive hello or remove link messages after the expiration of the acknowledgement timer: 1through 5.

Multilink Frame Relay UNI NNI bundle options (continued)

• Bundle class—Bundle class ID.

• LMI type—Multilink Frame Relay UNI NNI LMI type: ANSI, Q.933 ANNEX A, or Consortium.

  • T391 LIV polling timer—Multilink Frame Relay UNI NNI Full status polling counter: 1 through 255, with a default value of 6.

  • T392 polling verification timer—Multilink Frame Relay UNI NNI LMI error threshold. The number of errors required to bring down the link, within the event count specified by N393. The range is 1 through 10, with a default value of 3.

  • N391 full status polling count—Multilink Frame Relay UNI NNI Full status polling counter: 1 through 255.

  • N392 error threshold—Multilink Frame Relay UNI NNI LMI error threshold: 1 through 10.

• N393 monitored event count—Multilink Frame Relay UNI NNI LMI monitored event count: 1 through 10, with a default value of 4.

• Consortium LMI Settings

  • n391dte—DTE full status polling interval in seconds: 1 through 255.

  • n392dce—DCE error threshold: 1 through 10.

  • n392dte—DTE error threshold: 1 through 10.

  • n393dce—DCE monitored event count: 1 through 10.

    n393dte—DTE monitored event count: 1 through 10.

  • t391dte—DTE polling verification timer (in seconds): 5 through 30.

  • t392dce—DCE polling verification timer (in seconds): 5 through 30.

LMI

Local Managment Interface packet statistics:

• Input—Number of packets arriving on the interface (nn) and timestamp of the most recent packet arrival, in the format:

  Input: nn (last seen hh:mm:ss ago)

  Output—Number of packets sent out on the interface (nn) and how much time has passed since the last packet was sent, in the format:

  Output: nn (last seen hh:mm:ss ago)

DTE Statistics

Statistics about information transferred from the data terminal equipment (DTE) to the data communications equipment (DCE).

• Enquiries sent—Number of link status enquiries sent from the DTE to the DCE.

• Full enquiries sent—Number of full enquiries sent from the DTE to the DCE.

• Enquiry responses received—Number of enquiry responses received by the DCE from the DTE.

• Full enquiry responses received—Number of full enquiry responses received by DCE from the DTE.

DCE Statistics

Statistics about information transferred from the DCE to the DTE.

• Enquiries received—Number of enquiries received by the DCE from the DTE.

• Full enquiries received—Number of full enquiries received by the DCE from the DTE.

• Enquiry responses sent—Number of enquiry responses sent from the DCE to the DTE.

• Full enquiry responses sent—Number of full enquiry responses sent from the DCE to the DTE.

Common Statistics

Statistics about messages snet between the DTE and the DCE.

• Unknown messages received—Number of received packets that do not fall into any other category.

• Asynchronouts updates received—Number of link status peer changes received.

• Out-of-sequence packets received—Number of packets for which the sequence of the packets received is different from the expected sequence.

• Keepalive responses timed out—Number of keepalive responses that time out when no Local Management Interface (LMI) packet was reported for n392dte or n393dce intervals. (See LMI settings.)

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical interface. All references to traffic direction (input or output) are defined with respect to the Packet Forwarding Engine (PFE). Input traffic refers to the fragments received by the ingress PFE, which get assembled into Layer 3 input packets. Output packets refer to the IP packets transmitted out of the ingress PFE to the LSQ, which get segmented into output fragments.

DLCInn

Data-link connection identifier (DLCI) number of the logicial interview. The following information is displayed.

• Flags—Values are:

  • Active—Set when the link is active and the DTE and DCE are exchanging information.

  • Down—Set when the link is active, but no information is received from the DTE.

  • DCE unconfigured—Set when the corresponding DCLI in the DCE is not configured.

  • Configured—Set when the correspondening DLCCI is configured.

  • DCE-Configured—Displayed when the command is issued from the DTE.

DLCI Statistics

(Frame Relay) Data-link connection identifier (DLCI) statistics.

• Active DLCI—Number of active DLCIs.

• Inactive DLCI—Number of inactive DLCIs.

Input rate

(Redundant LSQ) Rate of bits and packets received on the interface.

Output rate

(Redundant LSQ) Rate of bits and packets transmitted on the interface.

Statistics last cleared

Time when the statistics for the interface were last set to zero.

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical interface. All references to traffic direction (input or output) are defined with respect to the router. Input fragments received by the router are assembled into input packets; output packets are segmented into output fragments for transmission out of the router.

Frame exceptions

Information about framing exceptions. Includes events recorded under Exception Events for each logical interface.

• Oversized frames—Number of frames received that exceed maximum frame length. Maximum length is 4500 Kb (kilobits).

• Errored input frames—Number of input frame errors.

• Input on disabled link/bundle—Number of frames received on disabled links. These frames can result either from an inconsistent configuration, or from a bundle or link being brought up or down with traffic actively flowing through it.

• Output for disabled link/bundle—Number of frames sent for a disabled or unavailable link. These frames can result either from an inconsistent configuration, or from a bundle being brought up or down while traffic is flowing through it.

• Queuing drops—Total number of packets dropped before traffic enters the link services IQ interface. Indicates that the interface is becoming oversubscribed.

Buffering exceptions

Information about buffering exceptions. Includes events recorded under Exception Events for each logical interface:

• Packet data buffer overflow—Packet buffer memory is full. This overflow can occur when the aggregate data rate exceeds the physical link services IQ interface capacity.

• Fragment data buffer overflow—Fragment buffer memory is full. This overflow can occur when excessive differential delay is experienced across the links within a single bundle, or when the aggregate data rate exceeds the physical link services IQ capacity. Check the logical interface exception event counters to determine which bundle is responsible.

Assembly exceptions

(Multilink Frame Relay end-to-end only) Information about assembly exceptions. Includes events recorded under Exception Events for each logical interface.

An assembly exception does not necessarily indicate an operational problem with the physical link services IQ interface itself. If multilink-encapsulated traffic is dropped or reordered after a sequence number has been assigned, the interface records one or more exception events. The physical interface can drop multilink-encapsulated fragments itself as a result. Any multilink packets or fragments dropped by the interface itself result in packet or fragment drop counts on individual logical interfaces. If the logical interface drop counts are zero, but exception events are seen, the most likely cause is a problem with the individual link interfaces. Even if the logical interface fragment drop counts are nonzero, excess differential delay or traffic losses on individual interfaces can be the root cause.

• Fragment timeout—The drop timer expired while a fragment sequence number was outstanding. Occurs only if the drop timer is enabled. This timeout can occur if the differential delay across the links in a bundle exceeds the drop-timer setting, or if a multilink packet is lost in transit while the drop timer is enabled. These events do not necessarily indicate any problem with the operation of the physical link services IQ interface itself, but can occur when one or more individual links drop traffic. Check the logical interface exception event counters to determine which bundle is responsible.

• Missing sequence number—A gap was detected in the sequence numbers of fragments on a bundle. These events do not necessarily indicate any problem with the operation of the physical link services IQ interface itself, but can occur when one or more individual links drop traffic. Check the logical interface exception event counters to determine which bundle is responsible.

• Out-of-order sequence number—Two frames with out-of-order sequence numbers within a single link. This event indicates that an individual link within a bundle reordered traffic, making the link services IQ interface unable to correctly process the resulting stream. Check the logical interface exception event counters to determine which bundle is responsible.

• Out-of-range sequence number—Received a frame with an out-of-range sequence number. These events can occur when a large amount of multilink-encapsulated traffic is lost or the multilink peer is reset, so that a large jump in sequence numbers results. A small number of these events can occur when the far end of a bundle is taken down or brought up. Check the logical interface exception event counters to determine which bundle is responsible.

Hardware errors (sticky)

(Multilink Frame Relay end-to-end only) Information about hardware errors:

• Data memory error—A memory error was detected on the interface DRAM. Indicates possible hardware failure. Contact Juniper Networks technical support.

• Control memory error—A memory error was detected on the interface DRAM. Indicates possible hardware failure. Contact Juniper Networks technical support.

Egress queues

Total number of egress queues supported on the specified interface.

Queue counters

Queue number and its associated user-configured forwarding class name.

• Queued packets—Number of queued packets.

• Transmitted packets—Number of transmitted packets.

• Dropped packets—Number of packets dropped by the ASIC's RED mechanism.

Logical interface

Name of the logical interface.

Index

Logical interface index number, which reflects its initialization sequence.

SNMP ifIndex

Logical interface SNMP interface index number.

Generation

Unique number for use by Juniper Networks technical support.

Flags

Information about the logical interface. Possible values are described in the “Logical Interface Flags” section under Common Output Fields Description.

Encapsulation

Encapsulation being used: PPP or Multilink PPP.

Bandwidth

Speed at which the interface is running.

Bundle options

(Multilink Frame Relay end-to-end interfaces only)

• MRRU—Configured size of the maximum received reconstructed unit (MRRU): 1500 through 4500  bytes. The default is 1504 bytes.

• Drop timer period—Drop timeout value to provide a recovery mechanism if individual links in link services bundle drop one or more packets: 0 though 2000  milliseconds. Values under 5 ms are not recommended. The default setting is 0, which disables the timer.

• Sequence number format—Short sequence number header format (MLPPP only).

• Fragmentation threshold—Configured fragmentation threshold: 64 through 16,320  bytes, in integer multiples of 64  bytes. The default setting is 0, which disables fragmentation.

• Links needed to sustain bundle—Minimum number of links to sustain the bundle: 1 through 8.

• Multilink classes—Number of multilink classes negotiated.

• Link layer overhead—Percentage of bundle bandwidth to be set aside for link-layer overhead.

Bundle status (MLPPP) or Multilink class status (Multiclass MLPPP)

Information about bundle status:

• Remote MRRU—MRRU value received from remote peer. If negotiation has not been initiated, the default value is displayed.

• Received sequence number—Sequence number for received packets.

• Transmitted sequence number—Sequence number for transmitted packets.

• Packet drops—Number and byte count of output packets that were dropped, rather than being encapsulated and sent out of the router as fragments. The packet drop counter is incremented if there is a temporary shortage of packet memory on the AS PIC, which causes packet fragmentation to fail.

• Fragment drops—Number and byte count of input fragments that were dropped, rather than being reassembled and handled by the router as packets. This counter also includes fragments that have been received successfully, but had to be dropped because not all fragments that constituted a packet had been received. The fragment drop counter is incremented when a fragment received on constituent links is dropped. Drop fragments can be triggered by sequence ordering errors, duplicate fragments, timed-out fragments, and bad multilink headers.

• MRRU exceeded—Number of reassembled packets exceeding the MRRU. This counter is not implemented in this release.

• Fragment timeout—The drop timer expired while a fragment sequence number was outstanding. Occurs only if the drop timer is enabled. This timeout can occur if the differential delay across the links in a bundle exceeds the drop-timer setting, or if a multilink packet is lost in transit while the drop timer is enabled.

• Missing sequence number—A gap was detected in the sequence numbers of fragments on a bundle.

• Out-of-order sequence number—Two frames with out-of-order sequence numbers within a single link. This event indicates that an individual link within a bundle reordered traffic, making the multilink interface unable to correctly process the resulting stream.

• Out-of-range sequence number—Received a frame with an out-of-range sequence number. These events can occur when a large amount of multilink-encapsulated traffic is lost or the multilink peer is reset, so that a large jump in sequence numbers results. A small number of these events can occur when the far end of a bundle is taken down or brought up.

• Packet data buffer overflow—Packet buffer memory is full. This overflow can occur when the aggregate data rate exceeds the physical link services IQ interface capacity.

• Fragment data buffer overflow—Fragment buffer memory is full. This overflow can occur when excessive differential delay is experienced across the links within a single bundle, or when the aggregate data rate exceeds the physical link services IQ capacity.

Statistics

Information about fragments and packets received and sent by the router. All references to traffic direction (input or output) are defined with respect to the router. Input fragments received by the router are assembled into input packets; output packets are segmented into output fragments for transmission out of the router. Each field has columns that indicate the number of frames received and transmitted, frames per second (fps), the number of bytes received and transmitted, and bits per second (bps).

• Bundle—Information for each active bundle link.

  • Fragments: Input and Output—Total number and rate of fragments received and transmitted.

  • Packets: Input and Output—Total number and rate of packets received and transmitted.

  • Multilink class—(Multiclass MLPPP only) Information about multiclass links used in the multilink operation.

• Link—Information about links used in the multilink operation.

  • Link name—Interface name of the link services IQ channel and state information (physical link up or down).

  • Input and Output—Total number and rate of fragments and packets received and transmitted.

NCP state

(PPP) Network Control Protocol state.

• Conf-ack-received—Acknowledgement was received.

• Conf-ack-sent—Acknowledgement was sent.

• Conf-req-sent—Request was sent.

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

• Not-configured—NCP is not configured on the interface.

• Opened—NCP negotiation is successful.

Protocol

Protocol family configured on the logical interface.

MTU

MTU size on the logical interface. If the MTU value is negotiated down to meet the MRRU requirement on the remote side, this value is marked Adjusted.

Generation

Unique number for use by Juniper Networks technical support only.

Route Table

Routing table in which this address exists. For example, Route table:0 refers to inet.0.

Flags

Information about the protocol family flags. Possible values are described in the “Family Flags” section under Common Output Fields Description.

Addresses, Flags

Information about the addresses configured on the logical interface. Possible values are described in the “Addresses Flags” section under Common Output Fields Description.

Destination

IP address of the remote side of the connection.

Local

IP address of the logical interface.

Broadcast

Broadcast address on the logical interface.

Generation

Unique number for use by Juniper Networks technical support.

Logical interface

Name of the logical interface.

Index

Logical interface index number, which reflects its initialization sequence.

SNMP ifIndex

Logical interface SNMP interface index number.

Generation

Unique number for use by Juniper Networks technical support.

Flags

Information about the logical interface. Possible values are described in the “Logical Interface Flags” section under Common Output Fields Description.

SNMP-Traps

SNMP trap notifications are enabled.

Encapsulation

Encapsulation being used: PPP, Multilink PPP, or Multilink-FR.

Last flapped

Date, time, and how long ago the interface went from down to up. The format is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

Bandwidth

Speed at which the interface is running.

Bundle links Iinformation

Information about the bundled links.

• Active bundle links—Number of active links.

• Removed bundle links—Information about links used in the multilink operation.

• Disabled bundle links—Number of disabled links.

Bundle options

(Multilink Frame Relay end-to-end interfaces only)

• MRRU—Configured size of the maximum received reconstructed unit (MRRU): 1500 through 4500  bytes. The default is 1504 bytes.

• Drop timer period—Drop timeout value to provide a recovery mechanism if individual links in link services bundle drop one or more packets: 0 though 2000  milliseconds. Values under 5 ms are not recommended. The default setting is 0, which disables the timer.

• Inner PPP Protocol field compression—Inner PPP protocol compression is enabled or disabled.

• Sequence number format—Short sequence number header format (MLPPP only).

• Fragmentation threshold—Configured fragmentation threshold: 64 through 16,320  bytes, in integer multiples of 64  bytes. The default setting is 0, which disables fragmentation.

• Links needed to sustain bundle—Minimum number of links to sustain the bundle: 1 through 8.

• Multilink classes—Number of multilink classes negotiated.

• Link layer overhead—Percentage of bundle bandwidth to be set aside for link-layer overhead.

Bundle status (MLPPP)

Information about bundle status:

• Received sequence number—Sequence number for received packets.

• Transmit sequence number—Sequence number for transmitted packets.

• Packet drops—Number and byte count of output packets that were dropped, rather than being encapsulated and sent out of the router as fragments. The packet drop counter is incremented if there is a temporary shortage of packet memory on the AS PIC, which causes packet fragmentation to fail.

• Fragment drops—Number and byte count of input fragments that were dropped, rather than being reassembled and handled by the router as packets. This counter also includes fragments that have been received successfully but had to be dropped because not all fragments that constituted a packet had been received. The fragment drop counter is incremented when a fragment received on constituent links is dropped. Drop fragments can be triggered by sequence ordering errors, duplicate fragments, timed-out fragments, and bad multilink headers.

• MRRU exceeded—Number of reassembled packets exceeding the MRRU. This counter is not implemented in this release.

• Fragment timeout—The drop timer expired while a fragment sequence number was outstanding. Occurs only if the drop timer is enabled. This timeout can occur if the differential delay across the links in a bundle exceeds the drop-timer setting, or if a multilink packet is lost in transit while the drop timer is enabled.

• Missing sequence number—A gap was detected in the sequence numbers of fragments on a bundle.

• Out-of-order sequence number—Two frames with out-of-order sequence numbers occurred within a single link. This event indicates that an individual link within a bundle reordered traffic, making the multilink interface unable to correctly process the resulting stream.

• Out-of-range sequence number—A frame was received with an out-of-range sequence number. These events can occur when a large amount of multilink-encapsulated traffic is lost or the multilink peer is reset, so that a large jump in sequence numbers results. A small number of these events can occur when the far end of a bundle is taken down or brought up.

• Packet data buffer overflow—Packet buffer memory is full. This overflow can occur when the aggregate data rate exceeds the physical link services IQ interface capacity.

• Fragment data buffer overflow—Fragment buffer memory is full. This overflow can occur when excessive differential delay is experienced across the links within a single bundle, or when the aggregate data rate exceeds the physical link services IQ capacity.

Statistics

Information about frames, bytes, and bits per second received and sent by the router. All references to traffic direction (input or output) are defined with respect to the router. Each field has columns that indicate the number of frames received and transmitted, frames per second (fps), the number of bytes received and transmitted, and bits per second (bps).

The bundle, multilink, and network statistics are reported by the Packet Forwarding Engine (PFE). The Multi Link Detail statistics like fragments, non-fragments and LFI are reported by the PIC.

However, the PFE reports an extra overhead of 2 bytes in the output when compared with the Multilink Detail Statistics. This is due to the service-cookie in the PFE which does the link demux for the ML header.

The difference in the bytes received and transmitted from Network and Multilink interfaces and Multilink statistics for each member link is divided between the ML and the PPP headers. For example the header counter for a long sequence configuration would be as follows.

• Input side - Total overhead = 6 bytes.

  • ML: 4 bytes of ML header = 1 byte of Flag + 3 bytes of long sequence number.

  • PPP: 2 bytes of protocol field.

• Output side - Total overhead = 11 bytes.

  • ML: 4 bytes of ML Header = 1 byte of Flag + 3 bytes of Long sequence number.

  • PPP: 5 bytes = 4 bytes of header + 1 byte of Idle flag.

  • 2 bytes of Service Cookie.

• Bundle—Information for each active bundle link.

  • Multilink: Input and Ouput—Total number and rate of multilink frames, bytes, and bits per second received and transmitted. It is a module connecting LSQ PIC and its member link. Multilink Input displays L2 fragments received from the member link to the LSQ PIC. Multilink Output displays the L2 fragments transmitted from LSQ PIC to the member links.

  • Network: Input and Output—Total number of network frames, bytes, and bits per second received and transmitted. It refers to the packets transmitted from an ingress interface to the PFE and then to the LSQ PIC. Network Input displays the L3 packets received from the LSQ PIC to the PFE. Network Output displays the L3 packets transmitted from PFE to LSQ PIC.

• Link—Information about links used in the multilink operation.

  • Link name—The interface name of the link services IQ channel and state information (physical link up or down) and up time.

  • Input and Output—Total number and rate of frames, bytes, and bits per second received and transmitted.

Multilink detail statistics

Frames, bytes, and bits per second received and sent by the bundle. All references to traffic direction (input or output) are defined with respect to the router. Each field has columns that indicate the number of frames received and transmitted, frames per second (fps), the number of bytes received and transmitted, and bits per second (bps).

The difference in the bytes received and transmitted from the bundle is divided between the ML and the PPP headers. For example the header counter for a long sequence configuration would be as follows:

• Input side - Total overhead = 6 bytes.

  • ML: 4 bytes of ML header = 1 byte of Flag + 3 bytes of long sequence number.

  • PPP: 2 bytes of protocol field.

• Output side - Total overhead = 9 bytes.

  • ML: 4 bytes of ML Header = 1 byte of Flag + 3 bytes of Long sequence number.

  • PPP: 5 bytes = 4 bytes of header + 1 byte of Idle flag.

• Bundle—Information for the bundle link.

  • Fragments: Input and Output—Total number and rate of multilink fragments received and transmitted.

  • Non-fragments: Input and Output—Total number and rate of nonfragmented multilink frames received and transmitted.

  • LFI: Input and Output—Total number and rate of link fragmented and interleaved frames and bytes.

Protocol

Protocol family configured on the logical interface.

MTU

MTU size on the logical interface. If the MTU value is negotiated down to meet the MRRU requirement on the remote side, this value is marked Adjusted.

Generation

Unique number for use by Juniper Networks technical support only.

Route Table

Routing table in which this address exists. For example, Route table:0 refers to inet.0.

Addresses, Flags

Information about the addresses configured on the logical interface. Possible values are described in the “Addresses Flags” section under Common Output Fields Description.

Destination

IP address of the remote side of the connection.

Local

IP address of the logical interface.

Broadcast

Broadcast address on the logical interface.

Generation

Unique number for use by Juniper Networks technical support.