Success rate is 100 percent (5/5), round-trip min/avg/max = 100/101/108 ms
Let’s test R2’s reachability, we already know that it needs a frame-relay map or else it will not be able to ping its own IP address, let’s configure one and test:
On R2
R2(config)#Int S0/0
R2(config-if)#Frame-relay map ip 10.1.1.2 201
To test the configuration:
On R2
R2#Ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/100/108 ms Let’s see if R2 can ping the other spokes:
On R2
R2#Ping 10.1.1.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds:
...
Success rate is 0 percent (0/5)
R2#Ping 10.1.1.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.4, timeout is 2 seconds:
...
Success rate is 0 percent (0/5)
Do we have frame-relay mappings for these destinations? Let’s check:
On R2
R2#Show frame-relay map
Serial0/0 (up): ip 10.1.1.2 dlci 201(0xC9,0x3090), static, CISCO, status defined, active
Serial0/0 (up): ip 10.1.1.1 dlci 201(0xC9,0x3090), static, broadcast,
CISCO, status defined, active
NOTE: There are two frame-relay mappings, one for 10.1.1.2 and the second one is for 10.1.1.1 IP addresses. Let’s add two more frame-relay mappings, one for 10.1.1.3 and the second one for 10.1.1.4:
On R2
R2(config)#Int S0/0
R2(config-if)#Frame-relay map ip 10.1.1.3 201 R2(config-if)#Frame-relay map ip 10.1.1.4 201
There are two points that you need to remember:
a. The destination IP address must be in the routing table with a valid next hop.
b. There must be a frame-relay mapping for that destination.
To test the configuration:
On R2
R2#Ping 10.1.1.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds:
...
Success rate is 0 percent (0/5)
Let’s turn on the “Debug Frame-relay packet” and ping again and see the result:
On R2
R2#Deb frame pack
Frame Relay packet debugging is on R2#Ping 10.1.1.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds:
Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 104.
Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 104.
Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 104.
Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 104.
Serial0/0(o): dlci 201(0x3091), pkt type 0x800(IP), datagramsize 104.
Success rate is 0 percent (0/5)
It seems like the local router (R2) is sending the packets out, let’s enable the same debugging on R3 and see the result:
On R2
R2#Ping 10.1.1.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds:
...
Success rate is 0 percent (0/5)
On R3
Serial0/0(i): dlci 301(0x48D1), pkt type 0x800, datagramsize 104 Serial0/0:Encaps failed--no map entry link 7(IP)
It looks like R3 is missing frame-relay map back to R2. Let’s configure a frame-relay map on R3 for R2 and test again:
On R3
R3(config)#Int S0/0
R3(config-if)#Frame-relay map ip 10.1.1.2 301
To verify the configuration:
On R2
R2#Ping 10.1.1.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 100/100/100 ms Perfect…..Let’s do the same on R4.
On R4
R4(config)#Int S0/0
R4(config-if)#Frame-relay map ip 10.1.1.2 401
To verify the configuration:
On R2
R2#Ping 10.1.1.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/100/108 ms
When configuring the frame-relay mapping from one spoke to another spoke, the “Broadcast”
keyword should not be used, if this keyword is used, the hub router will receive redundant routing traffic. This can be verified by running RIPv2 and performing a “Debug ip rip” command on the hub router.
Task 3
Configure the routers such that the LMI status inquiries are sent every 5 seconds and Full Status LMI requests are sent every 3 cycles instead of 6.
By default, frame-relay routers generate LMI Status inquiries every 10 seconds, and a full status inquiry every 6th cycle (Every 60 seconds). The interval for status inquiries can be changed using the
“Keepalive” command, whereas, the “Frame-relay lmi-n391dte” command can be used to change the interval for the complete status inquiries.
NOTE: The output of the following debug command reveals the status inquiries and full status inquiries:
On R1
R1#Debug frame lmi
Serial0/0(out): StEnq, myseq 125, yourseen 124, DTE up datagramstart = 0x3F401ED4, datagramsize = 14
FR encap = 0x00010308
00 75 95 01 01 01 03 02 7D 7C
Serial0/0(in): Status, myseq 125, pak size 14 RT IE 1, length 1, type 1
KA IE 3, length 2, yourseq 125, myseq 125
Serial0/0(out): StEnq, myseq 126, yourseen 125, DTE up datagramstart = 0x3F6B0294, datagramsize = 14
FR encap = 0x00010308
407: 00 75 95 01 01 01 03 02 7E 7D
Serial0/0(in): Status, myseq 126, pak size 14 RT IE 1, length 1, type 1
KA IE 3, length 2, yourseq 126, myseq 126
Serial0/0(out): StEnq, myseq 127, yourseen 126, DTE up datagramstart = 0x3F400C14, datagramsize = 14
FR encap = 0x00010308
00 75 95 01 01 01 03 02 7F 7E
Serial0/0(in): Status, myseq 127, pak size 14 RT IE 1, length 1, type 1
KA IE 3, length 2, yourseq 127, myseq 127
Serial0/0(out): StEnq, myseq 128, yourseen 127, DTE up datagramstart = 0x3F6AF394, datagramsize = 14
FR encap = 0x00010308
00 75 95 01 01 01 03 02 80 7F
Serial0/0(in): Status, myseq 128, pak size 14 RT IE 1, length 1, type 1
KA IE 3, length 2, yourseq 128, myseq 128
Serial0/0(out): StEnq, myseq 129, yourseen 128, DTE up datagramstart = 0x3F644ED4, datagramsize = 14
FR encap = 0x00010308
00 75 95 01 01 01 03 02 81 80
Serial0/0(in): Status, myseq 129, pak size 14 RT IE 1, length 1, type 1
KA IE 3, length 2, yourseq 129, myseq 129
Serial0/0(out): StEnq, myseq 130, yourseen 129, DTE up datagramstart = 0x3F6B03D4, datagramsize = 14
FR encap = 0x00010308
00 75 95 01 01 00 03 02 82 81
Serial0/0(in): Status, myseq 130, pak size 59 RT IE 1, length 1, type 0
KA IE 3, length 2, yourseq 130, myseq 130
PVC IE 0x7 , length 0x3 , dlci 102, status 0x2 PVC IE 0x7 , length 0x3 , dlci 103, status 0x2 PVC IE 0x7 , length 0x3 , dlci 104, status 0x2 PVC IE 0x7 , length 0x3 , dlci 105, status 0x0 PVC IE 0x7 , length 0x3 , dlci 106, status 0x0
Note the status inquiries are sent every 10 seconds, these messages are “type 1s”, whereas, the complete status inquiries are generated by the local router every 6th cycle, these message are “type 0” messages, and when the frame-relay switch receives these messages it responds with all the DLCIs that are configured for that given router.