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

Page: 162 / 774

■
Out DE pkts—Number of packets transmitted with the DE bit set
■
Dropped packets—Number of dropped packets
■
Example
host1# show frame-relay pvc
PVC information for frame relay NNI interface 3/2:1/1
DLCI 101 in sub-interface 3/2:1/1.1, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:29, last status change 01:21:29
In pkts: 0 Out pkts: 0
In bytes: 0 Out bytes: 0
In FECN pkts: 0 Out FECN pkts: 0
In BECN pkts: 0 Out BECN pkts: 0
In DE pkts: 0 Out DE pkts: 0
Dropped pkts: 0
DLCI 102 in sub-interface 3/2:1/1.2, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:28, last status change 01:21:29
In pkts: 0 Out pkts: 0
In bytes: 0 Out bytes: 0
In FECN pkts: 0 Out FECN pkts: 0
In BECN pkts: 0 Out BECN pkts: 0
In DE pkts: 0 Out DE pkts: 0
Dropped pkts: 0
DLCI 103 in sub-interface 3/2:1/1.3, status is active
Number of circuit status inactive transitions is 0
Time since creation 03:27:28, last status change 01:21:29
In pkts: 0 Out pkts: 0
In bytes: 0 Out bytes: 0
In FECN pkts: 0 Out FECN pkts: 0
In BECN pkts: 0 Out BECN pkts: 0
In DE pkts: 0 Out DE pkts: 0
Dropped pkts: 0
■
See show frame-relay pvc.
show frame-relay subinterface
■
Use to display the state of the Frame Relay subinterface.
■
The subinterface can be in one of the following states:
■
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
■
Use the optional delta keyword to specify that baselined statistics are to be
shown.
130 ■
Monitoring Frame Relay
JUNOSe 11.1.x Link Layer Configuration Guide