The Bryant Advantage Ultimate CCNA Lab Workbook

Chris Bryant, CCIE #12933 - www.thebryantadvantage.com Back To Index

Frame Relay Lab

A hub-and-spoke Frame Relay network will now be configured, with R1 serving as the hub and R2 and R3 as the spokes. Do not open the interfaces in this lab until you're told to. :) First, configure Frame Relay on R1s Serial0 interface with encapsulation frame-relay, and disable dynamic mapping with no frame-relay inversearp.
R1#conf t R1(config)#interface serial0 R1(config-if)#encapsulation frame-relay R1(config-if)#no frame-relay inverse-arp

Configure two Permanent Virtual Circuits (PVC) on R1 with two frame map statements, mapping DLCI 122 to R2 and DLCI 123 to R3. Ensure that broadcasts will be sent over these virtual circuits with the broadcast keyword. Run show frame map after doing so.
R1#conf t R1(config)#interface serial0 R1(config-if)#frame map ip 172.12.123.2 122 broadcast R1(config-if)#frame map ip 172.12.123.3 123 broadcast R1(config-if)#int s0 R1(config-if)#no shut 03:05:51: %LINK-3-UPDOWN: Interface Serial0, changed state to up 03:05:52: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up

R1#show frame Serial0 (up): Serial0 (up):

map ip 172.12.123.2 dlci 122(0x7A,0x1CA0), static, broadcast, CISCO, status defined, inactive ip 172.12.123.3 dlci 123(0x7B,0x1CB0), static, broadcast, CISCO, status defined, inactive

The mappings are inactive because frame relay has not yet been configured on the remote routers R2 and R3. With show frame map, if you see the PVC is inactive, theres a problem on the other end. If you see deleted, theres a problem on the local end. (A local problem is generally one of two things - a problem with the mapping or the interface is still shut.) R2s serial0.123 interface was configured as multipoint. Configure S0 and S0.123 as follows:
R2#conf t R2(config)#interface serial0 R2(config-if)#encapsulation frame-relay R2(config-if)#no frame inverse-arp R2(config-if)#interface s0.123 multipoint R2(config-subif)#frame map ip 172.12.123.1 221 broadcast R2(config-subif)#frame map ip 172.12.123.3 221 R2(config-subif)#int s0 R2(config-if)#no shut 03:06:56: %LINK-3-UPDOWN: Interface Serial0, changed state to up 03:06:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up

A subinterface can be either multipoint or point-to-point. When using a multipoint interface on a frame relay network, frame map statements are used just as they are on a physical interface. Enabling frame relay and disabling or enabling Inverse ARPis still done on the physical interface. Note that the frame map statement for 172.12.123.3 does not include a broadcast statement. Routers do not forward broadcasts, so R1 would not forward a broadcast from R2 to R3. That gives you the option of leaving the broadcast keyword out, but real-world networks generally user broadcast on all their frame map statements. The reason we'll leave it off here is to emphasize that pings will still go through without that option.
Run show frame map on R2.
R2#show frame map Serial0.123 (up): ip 172.12.123.1 dlci 221(0xDD,0x34D0), static, broadcast, CISCO, status defined, active Serial0.123 (up): ip 172.12.123.3 dlci 221(0xDD,0x34D0), static, CISCO, status defined, active

On R3, we'll configure a point-to-point interface to give you some handson practice with this interface type. The command for frame relay is a little different in this situation.

R3#conf t R3(config)#interface serial0 R3(config-if)#encapsulation frame-relay R3(config-if)#no frame-relay inverse-arp R3(config-if)#interface serial 0.31 point-to-point R3(config-subif)#frame-relay interface-dlci 321 R3(config-subif)#int s0 R3(config-if)#no shut 03:06:52: %LINK-3-UPDOWN: Interface Serial0, changed state to up 03:06:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up

Point-to-point Serial interfaces on a frame relay network do not use dynamic or static mappings. A point-to-point interface has only one possible destination the other end of the point-to-point connection. With only one possible destination, no mapping is necessary. Instead, the command frame-relay interface-dlci indicates the single DLCI that will be used by this interface.
R3#show frame map Serial0.31 (up): point-to-point dlci, dlci 321(0x141,0x5010), broadcast status defined, active

From each router, ping the other two routers Serial interfaces on the frame relay network. All pings will be successful. Run show frame lmi and show frame map on each router as well. Notice that the LMI counters are incrementing, and the frame map commands show all maps as active. (Only R1 is shown here, but send pings and run your show commands on all three routers.)
R1#ping 172.12.123.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.12.123.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 68/68/68 ms R1#ping 172.12.123.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.12.123.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 68/68/68 ms R1#show frame lmi LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO Invalid Unnumbered info 0 Invalid Prot Disc 0 Invalid dummy Call Ref 0 Invalid Msg Type 0 Invalid Status 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 Status Enq. Sent 121 Num Status msgs Rcvd 123 Num Update Status Rcvd 0 Num Status Timeouts 0

On R1, change the frame LMI type to ANSI with the frame-relay lmi-type command. After about 30 seconds, the line will go down.
R1#conf t R1(config)#interface serial0 R1(config-if)#frame-relay lmi-type ansi 00:46:40: %SYS-5-CONFIG_I: Configured from console by console

R1# 00:47:12: %FR-5-DLCICHANGE: Interface Serial0 INACTIVE 00:47:12: %FR-5-DLCICHANGE: Interface Serial0 INACTIVE 00:47:12: %FR-5-DLCICHANGE: Interface Serial0 DELETED 00:47:12: %FR-5-DLCICHANGE: Interface Serial0 DELETED 00:47:13: %LINEPROTO-5-UPDOWN: Line protocol on state to down

DLCI 122 state changed to DLCI 123 state changed to DLCI 122 state changed to DLCI 123 state changed to Interface Serial0, changed

The LMI mismatch leads to the line going down and the DLCIs going inactive. Run show frame lmi on R1. Wait a few seconds, then run it again, then again. Notice that the timeouts are incrementing. Once the total number of timeouts reached 3, the line protocol came down.
R1#show frame lmi LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI Invalid Unnumbered info 0 Invalid Prot Disc 0 Invalid dummy Call Ref 0 Invalid Msg Type 0 Invalid Status Message 0 Invalid Lock Shift 0 Invalid Information ID 0Invalid Report IE Len 0 Invalid Report Request 0 Invalid Keep IE Len 0 Num Status Enq. Sent 256 Num Status msgs Rcvd 240 Num Update Status Rcvd 0 Num Status Timeouts 16

The router is receiving LMI status messages, but when the LMI type was changed, the Status Timeouts began to accrue. This command gives an indication that there is a problem with the LMIs. The LMIs are the heartbeat of frame relay; without the right LMIs, the frame connection dies. Run debug frame lmi on R1.
R1#debug frame lmi Frame Relay LMI debugging is on Displaying all Frame Relay LMI data 00:52:12: Serial0(out): StEnq, myseq 31, yourseen 0, DTE down 00:52:12: datagramstart = 0xE0183C, datagramsize = 14 00:52:12: FR encap = 0x00010308 00:52:12: 00 75 95 01 01 00 03 02 1F 00 00:52:12: 00:52:22: Serial0(out): StEnq, myseq 32, yourseen 0, DTE down 00:52:22: datagramstart = 0xE0183C, datagramsize = 14 00:52:22: FR encap = 0x00010308 00:52:22: 00 75 95 01 01 00 03 02 20 00 00:52:22: 00:52:32: Serial0(out): StEnq, myseq 33, yourseen 0, DTE down 00:52:32: datagramstart = 0xE0183C, datagramsize = 14 00:52:32: FR encap = 0x00010308 00:52:32: 00 75 95 01 01 00 03 02 21 00

The myseq value continues remains at 0. Between debug seen that LMI messages are accepted another indicator of

to increase, but the yourseen value frame lmi and show frame lmi, it can be being received from the DCE, but not an LMI mismatch.

Leave that debug command on, and change the LMI default back to Cisco. (You must know all three LMI types before taking the CCNA exams!)

R1#debug frame lmi Frame Relay LMI debugging is on Displaying all Frame Relay LMI data

R1#conf t R1(config)#interface serial0 R1(config-if)#frame-relay lmi-type cisco 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:22: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:32: 00:56:42: 00:56:42: 00:56:42: 00:56:42: 00:56:42: 00:56:42: 00:56:42: 00:56:43: 00:57:22: 00:57:22: Serial0(out): StEnq, myseq 1, yourseen 0, DTE down datagramstart = 0xE0183C, datagramsize = 13 FR encap = 0xFCF10309 00 75 01 01 00 03 02 01 00 Serial0(in): Status, myseq 1 RT IE 1, length 1, type 0 KA IE 3, length 2, yourseq 1 , myseq 1 PVC IE 0x7 , length 0x6 , dlci 122, status 0x2 , bw 0 PVC IE 0x7 , length 0x6 , dlci 123, status 0x2 , bw 0 Serial0(out): StEnq, myseq 2, yourseen 1, DTE down datagramstart = 0xE0183C, datagramsize = 13 FR encap = 0xFCF10309 00 75 01 01 01 03 02 02 01 Serial0(in): Status, myseq 2 RT IE 1, length 1, type 0 KA IE 3, length 2, yourseq 2 , myseq 2 PVC IE 0x7 , length 0x6 , dlci 122, status 0x2 , bw 0 PVC IE 0x7 , length 0x6 , dlci 123, status 0x2 , bw 0 Serial0(out): StEnq, myseq 3, yourseen 2, DTE up datagramstart = 0xE0183C, datagramsize = 13 FR encap = 0xFCF10309 00 75 01 01 01 03 02 03 02 Serial0(in): Status, myseq 3 RT IE 1, length 1, type 1 KA IE 3, length 2, yourseq 3 , myseq 3 %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up %FR-5-DLCICHANGE: Interface Serial0 - DLCI 122 state changed to ACTIVE %FR-5-DLCICHANGE: Interface Serial0 - DLCI 123 state changed to ACTIVE

The incoming myseq packets are now being accepted, and the outgoing messages see the yourseen value begin to accrue. The DTE end of the connection goes up, the line protocol goes up soon after that, and finally the previously deleted DLCIs are again active. Use IOS Help to see what the LMI options are.
R1#conf t Enter configuration commands, one per line. End with CNTL/Z. R1(config)#int serial 0 R1(config-if)#frame lmi-type ? cisco ansi q933a

Run show frame pvc on R1. Note the status for each DLCI, and the uptime.
R1#show frame pvc PVC Statistics for interface Serial0 (Frame Relay DTE) Active Inactive Deleted Static Local 2 0 0 0 Switched0 00 0 Unused0 0 0 0 DLCI = 122, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0 input pkts 5 output pkts 5 in bytes 520 out bytes 520 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 0 out bcast bytes 0

 pvc create time 00:49:19, last time pvc status changed 00:01:15 DLCI = 123, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0 input pkts 17 output pkts 5 in bytes 4024 out bytes 520 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 0 out bcast bytes 0 pvc create time 00:49:12, last time pvc status changed 00:01:17

Before you take your CCNA exams, be very familiar with what each of these commands show you, and what the letters FECN, BECN, and DE mean: FECN: Congestion was experienced in the direction in which this packet was traveling. BECN: Congestion was experienced in the opposite direction in which this packet was traveling. DE: Packet was marked discard eligible, meaning it may be discarded if network congestion occurs. Back To Index
Copyright 2011 The Bryant Advantage. All Rights Reserved.