Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010, Configuration Manual

Page: 174 / 774

■
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 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 1
host1# show frame-relay interface brief
Frame relay interface mlframe-relayTEST, status is up
■
Example 2
host1# show frame-relay interface mlframe-relay TEST
Frame relay interface mlframe-relayTEST, status is up
Number of interface down transitions is 0
Time since last status change 00:01:47
Number of configured circuits: 2
In bytes: 452 Out bytes: 198
In frames: 19 Out frames: 11
In errors: 0 Out errors: 0
In discards: 8 Out discards: 0
In unknown protos: 0
■
Example 3
host1# show frame-relay interface mlframe-relay members
Frame relay interface mlframe-relay TEST is up
142 ■
Monitoring MLFR
JUNOSe 11.1.x Link Layer Configuration Guide