Learning by Doing: CISCO Certified Network ... - SCN Research

traffic
vofr
Frame-Relay protocol statistics
Show frame-relay VoFR statistics
router#debug frame-relay ?
detailed
Detailed Debug: Only for Lab use
dlsw
Frame Relay dlsw
end-to-end Frame-relay end-to-end VC information
events
Important Frame Relay packet events
foresight Frame Relay router ForeSight support
fragment Frame Relay fragment
hpr
Frame Relay APPN HPR
ip
Frame Relay Internet Protocol
l3cc
Frame Relay Layer 3 Call Control
l3ie
Frame Relay IE parsing/construction
lapf Frame Relay SVC Layer 2
llc2
Frame Relay llc2
lmi
LMI packet exchanges with service provider
nli
Network Layer interface
packet
Frame Relay packets
ppp
PPP over Frame Relay
rsrb
Frame Relay rsrb
verbose
Frame Relay
2. Next let’s use some of those more common commands to see “good” traffic,
packets and statistics on a frame relay connection between two routers (one
dlci #16 the other dlci#18). As always we like to start with an overall
“snapshot” of our connection. We use show frame pvc to show our permanent
virtual circuit statistics (layer 2):
router#sh frame pvc
PVC Statistics for interface Serial0/1 (Frame Relay DTE)
DLCI = 18, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE,
INTERFACE = Serial0/1
input pkts 18 output pkts 23 in bytes 1758
out bytes 2114 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 1 out bcast bytes 30
pvc create time 00:05:19, last time pvc status changed 00:00:30
router#
Which dlci is this router connected to? If you said 18 then you were incorrect.
The frame status we see is for the other one. If we have more than one dlci in our
406