Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual page 181

Copyright © 2010, Juniper Networks, Inc.
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 sub-interface down transitions—Number of times a subinterface came
down because of error conditions
Time since last status change—Time since the last status change on the subinterface
In bytes—Number of inbound bytes received on the subinterface
Out bytes—Number of outbound bytes transmitted on the subinterface
In frames—Number of inbound frames received on the interface
Out frames—Number of outbound frames transmitted on the interface
In errors—Number of inbound errors received on the subinterface
Out errors—Number of outbound errors transmitted on the subinterface
In discards—Number of inbound packets discarded
Out discards—Number of outbound packets discarded
In unknown protos—Number of packets received on the subinterface with unknown
protocols
Example 1
host1#show frame-relay subinterface brief
Frame relay sub-interface mlframe-relayTEST.1, status is up
Frame relay sub-interface mlframe-relayTEST.2, status is up
Example 2
host1#show frame-relay subinterface mlframe-relay TEST
Frame relay sub-interface mlframe-relayTEST.1, status is up
Number of sub-interface down transitions is 0
Time since last status change 00:07:49
In bytes: 512
In frames: 16
In errors: 0
In discards: 16
In unknown protos: 0
Frame relay sub-interface mlframe-relayTEST.2, status is up
Number of sub-interface down transitions is 0
Time since last status change 00:07:50
Chapter 3: Configuring Multilink Frame Relay
Out bytes: 0
Out frames: 0
Out errors: 0
Out discards: 0
149