background image
Frame Relay Configuration 557
Point-to-point subinterfaces were used in this configuration because the network is not fully
meshed. The frame-relay interface-dlci command is needed when using subinterfaces. This is
because the status messages come into the physical interface stating that a VC with a particular
DLCI is up; the IOS then needs to associate that VC with a subinterface.
The subinterface numbers in the example configuration happen to match on either end of the
VCs. For example, subinterface 2 was used in Atlanta for the PVC to Nashville; Nashville also
uses subinterface 2. There is no requirement that the subinterface numbers be the same.
Example 8-13 shows the output from the most popular IOS Frame Relay EXEC commands for
monitoring Frame Relay, as issued on router Atlanta.
interface ethernet 0
ip address 140.1.13.3 255.255.255.0
ipx network 13
Example 8-12
Boston Configuration
ipx routing 0200.dddd.dddd
!
interface serial0
encapsulation frame-relay
!
interface serial 0.3 point-to-point
ip address 140.1.3.4 255.255.255.0
ipx network 3
frame-relay interface-dlci 51
!
interface ethernet 0
ip address 140.1.14.4 255.255.255.0
ipx network 14
Example 8-13
Output from EXEC Commands on Atlanta
Atlanta#show frame-relay pvc
PVC Statistics for interface Serial0 (Frame Relay DTE)
DLCI = 52, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.1
input pkts 843 output pkts 876 in bytes 122723
out bytes 134431 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 876 out bcast bytes 134431
pvc create time 05:20:10, last time pvc status changed 05:19:31
--More--
DLCI = 53, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.2
input pkts 0 output pkts 875 in bytes 0
out bytes 142417 dropped pkts 0 in FECN pkts 0
Example 8-11
Nashville Configuration (Continued)
continues
ch08.fm Page 557 Monday, March 20, 2000 5:17 PM