show interfaces (Link Services)

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's 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 (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).

Statistics last cleared

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

Link flags

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

Hold-times

Current interface hold time up and hold time down, in milliseconds, in the format Up n ms, Down n ms.

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.

• 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.

• 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 that is 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: 1 through 5.

Multilink Frame Relay UNI NNI bundle options (continued)

• Bundle class—Bundle class ID.

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

  • 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.

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.

Multilink Frame Relay UNI NNI bundle errors

Information about Multilink Frame Relay bundle errors.

• Packet drops—Number of packets dropped.

• Fragment drops—Number of fragments dropped.

• MRRU exceeded—Number of times a packet was dropped because the configured MRRU value was exceeded.

• Exception events—Exception events counter.

Multilink Frame Relay UNI NNI bundle statistics

Information about Multilink Frame Relay bundles.

• Fragments—Bundle fragment information.

  • Input—Total number and rate of frames and packets received, in Frames, fps (frames per second), Bytes, and bps (bits per second).

  • Output—Total number and rate of frames and packets transmitted, in Frames, fps, Bytes, and bps.

• Packets—Bundle packet information.

  • Input—Total number and rate of frames and packets received, in Frames, fps (frames per second), Bytes, and bps (bits per second).

  • Output—Total number and rate of frames and packets transmitted, in Frames, fps, Bytes, and bps.

Multilink Frame Relay UNI NNI bundle links information

Multilink Frame Relay UNI NNI active bundle links statistics

(Multilink Frame Relay UNI NNI only) Display information for each active bundle link.

• Frames—Number of multilink control frames received on this bundle link.

• fps—Rate of multilink control frames received on this bundle link (in frames per second).

• Bytes—Number of bytes received on this bundle link.

• bps—Number of bits per second received on this bundle link.

• interface-name—Name of the bundle link interface.

• Input—Total number and rate of frames and packets received.

• Output—Total number and rate of frames and packets transmitted.

• Current differential delay—Compare this bundle link's round trip time to the average of all bundle links' round trip times in ms (milliseconds).

• Recent high differential delay—Highest differential delay value from the latest 10 intervals, in milliseconds.

• Times over red diff delay—Number of times this bundle link exceeded the configured red differential delay limit.

• Times over yellow diff delay—Number of times this bundle link exceeded the configured yellow differential delay limit.

Multilink Frame Relay UNI NNI active bundle links statistics (continued)

• LIP—Link Interleaving Protocol information.

• Rcv—Number of messages received.

• Xmt—Number of messages transmitted.

• add_lnk—ADD__LINK message notifies the peer endpoint that the local endpoint supports frame processing. It is generated on both ends of a bundle link when a bundle link endpoint is ready to become operational.

• lnk_ack—ADD_LINK_ACK message notifies the peer that the local router has received a valid ADD_LINK message.

• lnk_rej—ADD_LINK_REJ message notifies the peer that the local router has received an invalid ADD_LINK message.

• hello—HELLO message notifies the peer that the local router is up. Both ends of a link bundle generate this message.

• hel_ack—HELLO_ACK message notifies the peer that the local router has received a valid HELLO message.

• lnk_rem—REMOVE_LINK message notifies the peer that the local router has received a REMOVE_LINK message.

• rem_ack—REMOVE_LINK_ACK message notifies the peer that the local router has received a valid ADD_LINK message.

Frame exceptions

For Multilink Frame Relay end-to-end only. 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

For Multilink Frame Relay end-to-end only. 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 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 interface capacity. Check the logical interface exception event counters to determine which bundle is responsible.

Assembly exceptions

For 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 interface itself. If multilink-encapsulated traffic is dropped or reordered after a sequence number has been assigned, the assembling multilink interface records one or more exception events. The multilink interface can drop multilink-encapsulated fragments itself as a result. Any multilink packets or fragments dropped by the physical link services 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.

Assembly exceptions (continued)

• 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 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 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 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. Check the logical interface exception event counters to determine which bundle is responsible.

• Out-of-range sequence number—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. Check the logical interface exception event counters to determine which bundle is responsible.

Hardware errors

For 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.

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, Multilink - FR or Multilink - PPP

Bandwidth

Speed at which the interface is running.

Bundle options

For Multilink Frame Relay end-to-end interfaces only:

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

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

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

• Fragmentation threshold—Configured fragmentation threshold: 128 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.

• Interleave fragments—State of the process that interleaves long packets with high-priority ones. Only Disabled is currently supported.

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

Bundle status (MLPPP) or Multilink class status (MC-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.

• 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.

Bundle status (MLPPP) or Multilink class status (MC-MLPPP) (continued)

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

• Fragment timeout—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—Gap 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—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 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 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.

Bundle errors

Information about bundle errors.

• Packet drops—Number and byte count of output packets that were dropped, rather than being encapsulated and sent out of the router as fragments.

• Fragment drops—Number and byte count of input fragments that were dropped, rather than being reassembled and handled by the router as packets.

• MRRU exceeded—Number of reassembled packets exceeding the MRRU.

• Exception events—Number of exceptional events encountered other than MRRU exceeded errors. These events are categorized under the physical interface: Frame exceptions, Buffering exceptions, and Fragment exceptions. Exception events do not necessarily indicate that the multilink interface is not operating properly. Individual link failures can produce exceptional events.

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.

• Bundle—Information about bundles.

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

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 address flags. 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.