Juniper ACX2000 Configuration Guide

Table 149: Link Services show interfaces Output Fields (continued)
Level of OutputField DescriptionField Name
detail extensiveFor 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
detail extensive• 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.
Assembly
exceptions
(continued)
detail extensiveFor 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.
Hardware errors
Logical Interface
All levelsName of the logical interface.Logical interface
2591Copyright © 2017, Juniper Networks, Inc.
Chapter 42: Operational Commands

Juniper ACX2000 Specifications

General

Brand	Juniper
Model	ACX2000
Category	Network Router
Language	English