This would have you pinging! r1(config-if)#encapsulation frame-relay mfR ? <0-2147483647> MFR interface number
r1(config-if)#encapsulation frame-relay mfR HTHs On Jun 23, 2010, at 2:11 PM, virtualtech wrote: > Team > > I used my rack time today to continue to work on Vol 1 Lab 6. Below are the > issues I ran into: > > Some of the DSG show results do not match up to what you actually see when > using the proctorlabs. When I make my next pass on this lab I will list those > differences. They are mostly cosmetic but could throw someone expecting their > results to match the DSG. > > I ran into the same issue listed in my email below that I ran into yesterday > on Vol1 Lab 6 Task 6.4 I used the workaround I listed in my email below and > it worked. You only need to shut the physical interface s0/1/0 since it shuts > the sub interface down automatically. Then do a clear frame-relay inarp on R2 > and then you can complete the commands for Vol1 Lab 6 Task 6.5. > > I also ran into another issue on Vol1 Lab 6 Task 6.14. After entering the > commands on R6 and R9 the DSG says you should be able to ping 150.100.69.6 > from R9. This does not work I ran a debug IP packet to see if I could figure > out why the ping fails and the results are below. > > R9#debug ip packet > IP packet debugging is on > R9#ping 150.100.69.6 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 150.100.69.6, timeout is 2 seconds: > > Jun 23 15:55:12.571: IP: s=0.0.0.0 (local), d=150.100.69.6, len 100, > unroutable. > Jun 23 15:55:14.571: IP: s=0.0.0.0 (local), d=150.100.69.6, len 100, > unroutable. > Jun 23 15:55:16.571: IP: s=0.0.0.0 (local), d=150.100.69.6, len 100, > unroutable. > Jun 23 15:55:18.571: IP: s=0.0.0.0 (local), d=150.100.69.6, len 100, > unroutable. > Jun 23 15:55:20.571: IP: s=0.0.0.0 (local), d=150.100.69.6, len 100, > unroutable. > Success rate is 0 percent (0/5) > > All of the other show command results looked good for Lab 6 Task 6.14 except > for the above ping failing. Any idea’s why this fails? > > I continued on through the lab following the DSG. I got to Lab 6 Task 6.17 > and I ran into the same issue I listed in my previous email yesterday. I > basically see one failure on R2 so at this point I assume that the one > failure is not an issue since whenever I run sh frame end keep I do not see > any more failures but the one and the time since the last error increases > plus EEK is up. On R4 I do not show any failures. > > R2#sh frame end keep > End-to-end Keepalive Statistics for Interface Serial0/1/0 (Frame Relay DTE) > > DLCI = 204, DLCI USAGE = LOCAL, VC STATUS = ACTIVE (EEK UP) > SEND SIDE STATISTICS > Send Sequence Number: 59, Receive Sequence Number: 60 > Configured Event Window: 3, Configured Error Threshold: 2 > Total Observed Events: 64, Total Observed Errors: 2 > Monitored Events: 3, Monitored Errors: 0 > Successive Successes: 3, End-to-end VC Status: UP > RECEIVE SIDE STATISTICS > Send Sequence Number: 60, Receive Sequence Number: 59 > Configured Event Window: 3, Configured Error Threshold: 2 > Total Observed Events: 62, Total Observed Errors: 0 > Monitored Events: 3, Monitored Errors: 0 > Successive Successes: 3, End-to-end VC Status: UP > Failures Since Started: 1, Last Failure: 00:10:09 > > Hopefully someone from IP Expert can run through this lab and verify > everything and then update the DSG so we can avoid these issues in the > future. I am attaching the configs for my rack so IP Expert can review them. > > Thanks > > > From: virtualtech [mailto:[email protected]] > Sent: Tuesday, June 22, 2010 4:24 PM > To: 'virtualtech'; 'Adrian Brayton' > Cc: '[email protected]' > Subject: RE: [OSL | CCIE_RS] Volume 1 Lab 6 Task 6.4 > > Team > > I continued ahead to task 6.5 in the DSG and when I tried to enter those > commands I got the message %PVC already assigned to interface Serial0/1/0. At > this point I shut down int s0/1/0 and s0/1/0.1 on R2 and then did a clear > frame-relay inarp on R2. Then I was able to complete the commands for task > 6.5 and no shut int s0/1/0 and s0/1/0.1 on R2. > > This also seems to fix the issue I was having in task 6.4. I was able to see > the 402 and 412 DLCI and ping 150.100.24.2 from R4. > > So at this point I believe the DSG needs to be checked and then updated with > the correct commands so no one else runs into these issues. Can one of the IP > Expert instructors please run through this lab and confirm everything and > then get it updated? > > Please note that I was not able to complete my frame relay lab today due to > the time it took to troubleshoot and document these issues. I have tried to > complete this lab and I have run into errors using both the video solution > and the DSG. > > I will use my scheduled rack time in the morning to try and complete this lab > with the DSG and document any other errors I find. > > Task 6.5 - Commands > __________ > > R4 > _ _ _ _ > conf t > int s0/0/0 > encap frame ietf > end > wr > > R2 > _ _ _ _ > > conf t > int s0/1/0.1 > frame-relay interface-dlci 204 ietf > end > wr > > > R4#ping 150.100.24.2 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 150.100.24.2, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms > R4#sh frame map > Serial0/0/0 (up): ip 150.100.24.2 dlci 402(0x192,0x6420), dynamic, > broadcast, > IETF, status defined, active > Serial0/0/0 (up): ip 150.100.100.2 dlci 412(0x19C,0x64C0), dynamic, > broadcast, > IETF, status defined, active > R4#sh frame map > Serial0/0/0 (up): ip 150.100.24.2 dlci 402(0x192,0x6420), dynamic, > broadcast, > IETF, status defined, active > Serial0/0/0 (up): ip 150.100.100.2 dlci 412(0x19C,0x64C0), dynamic, > broadcast, > IETF, status defined, active > > > Thanks > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.829 / Virus Database: 271.1.1/2955 - Release Date: 06/22/10 > 02:36:00 > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.829 / Virus Database: 271.1.1/2955 - Release Date: 06/22/10 > 02:36:00 > > > <configs 6-23-10.rtf>_______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
