Frame Broadcast Configuration
This area completes the FR agreement advantage for this book. Earlier, Affiliate 6,
“IP Forwarding (Routing),” covered issues with mapping Layer 3 addresses to FR DLCIs,
and Affiliate 9, “OSPF,” covered issues with application OSPF over FR. This area covers the
basic agreement and operational commands, forth with FR burden compression and FR
LFI options.
Frame Broadcast Agreement Basics
Two of the best important capacity apropos Anatomy Broadcast agreement are the affiliation of
DLCIs with the actual interface or subinterface, and the mapping of L3 addresses to those DLCIs.
Interesting, both appearance can be configured application the aforementioned two commands—the frame-relay
map and frame-relay interface-dlci commands. Affiliate 6 already covered the capacity of
mapping L3 addresses to DLCIs application InARP and changeless mapping. (If you accept not advised those
518 Affiliate 15: Anatomy Relay
details back starting this chapter, it is apparently a acceptable time to do so.) This area focuses more
on the affiliation of DLCIs with a accurate subinterface.
Although a router can apprentice anniversary DLCI on the admission articulation via LMI Cachet messages, these messages
do not betoken with which subinterface anniversary DLCI should be used. To configure Anatomy Broadcast using
subinterfaces, the DLCIs charge be associated with the subinterface. Any DLCIs abstruse with LMI
that are not associated with a subinterface are affected to be acclimated by the concrete interface.
The added accepted adjustment to accomplish this affiliation is to use the frame-relay interface-dlci
subinterface subcommand. On point-to-point subinterfaces, alone a distinct frame-relay interfacedlci
command is allowed, admitting multipoint interfaces abutment assorted commands. The
alternative adjustment is to use the frame-relay map command. This command still maps Layer 3
addresses to DLCIs, but additionally implies an affiliation of the configured DLCI with the subinterface
under which the command is issued. And agnate to frame-relay interface-dlci commands, only
one frame-relay map command is accustomed per point-to-point subinterface, per Layer 3 protocol.
On multipoint subinterfaces, assorted commands are accustomed per Layer 3 protocol.
Example 15-1 depicts a advanced array of Anatomy Broadcast agreement options, application frame-relay
interface-dlci commands, and the accompanying appearance commands. Based on Figure 15-4, this example
implements the afterward requirements:
■ R1 uses a multipoint subinterface to affix to R2 and R3.
■ R1 uses a point-to-point subinterface to affix to R4.
■ The VC amid R1 and R4 uses IETF encapsulation.
Figure 15-4 Sample FR Network for Agreement Examples
Network 10.0.0.0
2.2/24
3.3/24
23.1/30
R1/2/3 –
Subnet 10.1.123.0/24,
Multipoint Subinterfaces
R1/4
Subnet 10.1.14.0/24,
4.4/24 Point-to-Point Subinterfaces
14.4/24
14.1/24
.3
.2
.1
R2
R3
FR
IETF
Encapsulation
R1
R4
fa0/0
fa0/0
fa0/0
Frame Broadcast Agreement 519
Example 15-1 Basic Anatomy Broadcast Agreement Example
! R1 agreement begins the example. Subint .14 shows the IETF advantage acclimated on
! the frame-relay interface-dlci command. Subint .123 has two DLCIs associated
! with it, for the VCs to R2 and R3.
interface Serial0/0/0
encapsulation frame-relay
!
interface Serial0/0/0.14 point-to-point
ip abode 10.1.14.1 255.255.255.0
frame-relay interface-dlci 104 IETF
!
interface Serial0/0/0.123 multipoint
ip abode 10.1.123.1 255.255.255.0
frame-relay interface-dlci 102
frame-relay interface-dlci 103
! R2 agreement comes next. R2 assigns the DLCI for the VC to R1 and R3 to the
! .123 subinterface. Agenda the routers’ subint numbers do not accept to match.
interface Serial0/0/0
encapsulation frame-relay
!
interface Serial0/0/0.123 multipoint
ip abode 10.1.123.2 255.255.255.0
frame-relay interface-dlci 101
frame-relay interface-dlci 103
! R3 agreement follows the aforementioned conventions as does R2’s and is not shown.
! R4’s agreement follows next, with the encapsulation frame-relay ietf command
! ambience the encapsulation for all the VCs on interface s0/0/0. Additionally agenda that
! the abundance of LMI enquiries was afflicted from the absence (10) to 8 with the
! keepalive 8 command.
interface Serial0/0/0
encapsulation frame-relay IETF
keepalive 8
!
interface Serial0/0/0.1 point-to-point
ip abode 10.1.14.4 255.255.255.0
frame-relay interface-dlci 101
! The appearance frame-relay pvc command shows statistics and cachet per VC. The next
! command (on R1) filters the achievement to aloof accommodate the curve with PVC status.
R1# appearance frame-relay pvc | incl PVC STATUS
DLCI = 100, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/0
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0.123
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0.123
DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0.14
DLCI = 105, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 106, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/0
DLCI = 107, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 108, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
DLCI = 109, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/0
continues
520 Affiliate 15: Anatomy Relay
DLCI = 110, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/0
! The abutting command lists stats for a distinct VC on R1, with DLCI 102, which is the
! VC to R2. Agenda the counters for FECN, BECN, and DE, as able-bodied as the in and out
! bit ante aloof for this VC.
R1# appearance frame-relay pvc 102
PVC Statistics for interface Serial0/0/0 (Frame Broadcast DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0.123
input pkts 41 achievement pkts 54 in bytes 4615
out bytes 5491 alone pkts 0 in pkts alone 0
out pkts alone 0 out bytes alone 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 27 out bcast bytes 1587
5 minute ascribe amount 0 bits/sec, 0 packets/sec
5 minute achievement amount 0 bits/sec, 0 packets/sec
pvc actualize time 00:29:37, aftermost time pvc cachet afflicted 00:13:47
! The afterward achievement confirms that R1’s articulation is application the Cisco LMI standard. Full
! LMI Cachet letters action about every minute, with the Aftermost Full Cachet message
! listed last. Agenda that the router sends Cachet Enquiries to the switch, with the
! about-face sending Cachet messages; those counters should accession together.
R1# appearance frame-relay lmi
LMI Statistics for interface Serial0/0/0 (Frame Broadcast DTE) LMI TYPE = CISCO
Invalid Unnumbered advice 0 Invalid Prot Disc 0
Invalid copy Call Ref 0 Invalid Msg Blazon 0
Invalid Cachet Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Cachet Enq. Beatific 183 Num Cachet msgs Rcvd 183
Num Update Cachet Rcvd 0 Num Cachet Timeouts 0
Last Full Cachet Req 00:00:35 Aftermost Full Cachet Rcvd 00:00:35
! The appearance interface command lists several capacity as well, including the interval
! for LMI letters (keepalive), LMI stats, LMI DLCI (1023), and stats for the FR
! advertisement queue. The advertisement chain holds FR broadcasts that charge be replicated
! and beatific over this VC, for example, OSPF LSAs.
R1# appearance int s 0/0/0
Serial0/0/0 is up, band agreement is up
! curve bare for brevity
Encapsulation FRAME-RELAY, loopback not set
Keepalive set (10 sec)
LMI enq beatific 185, LMI carbon recvd 185, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI carbon beatific 0, LMI upd beatific 0
LMI DLCI 1023 LMI blazon is CISCO anatomy broadcast DTE
FR SVC disabled, LAPF accompaniment down
Broadcast chain 0/64, broadcasts sent/dropped 274/0, interface broadcasts 228
! Curve bare for brevity
! R3 is application ANSI LMI, which uses DLCI 0, as accepted next.
Example 15-1 Basic Anatomy Broadcast Agreement Archetype (Continued)
R3# sh anatomy lmi | accommodate LMI TYPE
LMI Statistics for interface Serial0/0/0 (Frame Broadcast DTE) LMI TYPE = ANSI
R3# sh int s 0/0/0 | accommodate LMI DLCI
LMI DLCI 0 LMI blazon is ANSI Annex D anatomy broadcast DTE
At the end of Archetype 15-1, agenda that R3 is application the ANSI LMI type. R3 could accept configured
the LMI blazon statically application the frame-relay lmi-type {ansi | cisco | q933a} command, under
the concrete interface. However, R3 bare the command, causing R3 to booty the absence action
of autosensing the LMI type.