Juniper JUNOSE 11.2, Configuration Manual

Page: 178 / 772

•
Up — Traffic can flow on the interface
•
Offline — Traffic cannot flow because hardware is unavailable
•
Down — Traffic cannot flow because of a problem in the interface at the current
protocol layer
•
LowerLayerDown — Traffic cannot flow because of a problem in an interface at a
lower protocol layer
•
AdministrativelyDown — Traffic cannot flow because of manual administrative
intervention
•
Number of multilink interface down transitions—Number of interfaces that have
changed to a down state
•
Time since last status change—Time since the interface last changed its state
•
In bytes — Number of inbound bytes received on the interface
•
In frames—Number of inbound frames received on the interface
•
In errors — Number of inbound errors received on the interface
•
In discards — Number of inbound packets discarded
•
In unknown protos — Number of packets received on the interface with unknown
protocols
•
Out bytes — Number of outbound bytes transmitted on the interface
•
Out frames—Number of outbound frames transmitted on the interface
•
Out errors — Number of outbound errors transmitted on the interface
•
Out discards — Number of outbound packets discarded
•
Example
host1# show frame-relay multilinkInterface
Multilink Frame relay interface 6/2:2, status is down
Number of multilink interface down transitions is 0
Time since last status change 2 days, 23 hours
In bytes: 0 Out bytes: 0
In frames: 0 Out frames: 0
In errors: 0 Out errors: 0
In discards: 0 Out discards: 0
In unknown protos: 0
•
See show frame-relay multilinkInterface.
show frame-relay pvc
•
Use to display statistics about PVCs for Frame Relay interfaces.
•
Specify a DLCI number or an interface type and location.
•
Use the optional delta keyword to specify that baselined statistics are to be shown.
Copyright © 2010, Juniper Networks, Inc. 146
JunosE 11.2.x Link Layer Configuration Guide