I am also noticing some minor annoyances in Lab6... For example, the in the DSG, R4 is being configured with the "encapsulation frame-relay ietf" command, but in the "final configs" section that config is nowhere to be seen...
Atle On Thu, Jun 24, 2010 at 6:31 PM, virtualtech <[email protected]>wrote: > Team > > > > I have spent several days working on Frame-Relay Volume 1 Lab 6 on the > Proctor Labs rack and I have found some errors in the current version of the > Detail Solution Guide. Below is a detailed list of every error I have found > complete with the workarounds I used to resolve them. > > > > The following tasks had errors, cosmetic errors, or some part of the task > that could not be completed as written in the DSG. The tasks are 6.2, 6.4, > 6.5, 6.7, 6.8, 6.13, 6.14 and 6.17. > > > > Hopefully someone from IP Expert can confirm everything I listed here and > then make the correct changes in the DSG. Until then I hope this helps > anyone working on this lab. > > > > I am also attaching my final router configurations. I basically logged onto > Proctor Labs and loaded the initial configurations for Frame-Relay Volume 1 > Lab 6 and then went through with the DSG line by line and made the changes I > listed here when I ran into issues. So my configurations only show changes I > made as part of the Frame-Relay Volume 1 Lab 6. > > > > Thank you and good luck to everyone in their studies! > > > > > > Task 6.2 > > > > R2#sh ip int brie | exc una > > Interface IP-Address OK? Method Status > Protocol > > Serial0/1/0 150.100.100.2 YES manual up > up > > Serial0/1/0.1 150.100.24.2 YES manual up > up > > R2# > > > > The DSG shows more interfaces and it shows them as down. However mine are > up and up this does not affect anything it is cosmetic. > > > > Task 6.4 > > > > In the DSG it shows DLCI 412 and 402 being up. It also says you can ping > DLCI 402 IP 150.100.24.2 from R4. > > > > When you run the Show frame map command you will only see DLCI 422. You > will not be able to see DLCI 402 or ping its IP until you complete the steps > below: > > Note: Some of these commands are covered later in task 6.5. However they do > not cover shutting down R2's interface and clearing frame-relay arp. > > > > Note: This command is covered in Task 6.5 > > R4 > > _ _ _ _ > > conf t > > int s0/0/0 > > encap frame ietf > > end > > wr > > > > Note: This command is not covered in the tasks but you cannot add the other > R2 command in task 6.5 without it. > > R2 > > _ _ _ _ > > > > conf t > > int s0/1/0 > > shut > > end > > clear frame-relay inarp > > wr > > > > Note: This command is covered in Task 6.5 > > R2 > > _ _ _ _ > > > > conf t > > int s0/1/0.1 > > frame-relay interface-dlci 204 ietf > > end > > wr > > > > Note: Now you can no shut the interface. This command is not covered but we > need it since we shut the interface so we could clear frame relay arp and > add the other command to R2. > > R2 > > _ _ _ _ > > > > conf t > > int s0/1/0 > > no shut > > end > > wr > > > > Note: You should be able to see DLCI 402 and ping 150.100.24.2 on R4 now. > > Note: I assume DLCI 412 was a typo and the DSG meant DLCI 422. > > Note: You can try your pings and show commands from task 6.4 and 6.5 and > > If everything checks out then you can move on to task 6.6. > > > > Task 6.7 > > In the DSG the show frame map results shows DLCI 604 and DLCI 612. I only > see DLCI 624 which has the IP address shown in the DSG for DLCI 604. > > > > R6#sh frame map > > Serial0/1/0 (up): ip 150.100.24.4 dlci 624(0x270,0x9C00), dynamic, > > broadcast,, status defined, active > > > > Note: You should be able to continue to task 6.8. I believe these are typos > in the DSG. > > > > Task 6.8 > > When I try to enter the commands from the DSG I get the message %Address > already in map. > > > > > > R6#conf t > > Enter configuration commands, one per line. End with CNTL/Z. > > R6(config)#int s0/1/0 > > R6(config-if)#no frame inv > > R6(config-if)#frame map ip 150.100.100.5 602 > > R6(config-if)#frame map ip 150.100.100.2 602 broad > > %Address already in map > > R6(config-if)#frame map ip 150.100.100.6 602 > > R6(config-if)#end > > > > In order to avoid this issue and be able to enter the command in task 6.8 > you need to clear > > frame-relay inarp. I use the command below. > > > > R6 > > _ _ _ _ > > clear frame-relay inarp > > conf t > > int s0/1/0 > > no frame inv > > frame map ip 150.100.100.5 602 > > frame map ip 150.100.100.2 602 broad > > frame map ip 150.100.100.6 602 > > end > > wr > > > > R6#clear frame-relay inarp > > R6#conf t > > Enter configuration commands, one per line. End with CNTL/Z. > > R6(config)#int s0/1/0 > > R6(config-if)#no frame inv > > R6(config-if)#frame map ip 150.100.100.5 602 > > R6(config-if)#frame map ip 150.100.100.2 602 broad > > R6(config-if)#frame map ip 150.100.100.6 602 > > R6(config-if)#end > > R6#wr > > > > Note: No message %Address already in map so you are ready to go to task > 6.9. > > > > Task 6.13 > > The DSG only shows entering commands on router R6. However you need to > enter some commands on R9 for the link to come up. Below are the commands > you need to use. > > > > R6 > > _ _ _ _ > > conf t > > int mfr 1 > > encapsulation frame-relay > > int s0/2/0 > > encap frame mfr 1 > > int s0/2/1 > > encap frame mfr 1 > > end > > wr > > > > > > R9 > > _ _ _ _ > > conf t > > int mfr 1 > > int s0/2/0 > > encap frame mfr 1 > > int s0/2/1 > > encap frame mfr 1 > > end > > wr > > > > Note: In task 6.14 the DSG shows ping 150.100.69.6 from R9. This ping will > not work unless you enter the commands above. > > Note: Make sure the encapsulation frame-relay has the mfr 1 on it or you > will not be able to ping. > > Note: If you do a show run your interfaces should say encapsulation > frame-relay MFR1. If they just show encapsulation frame-relay without the > MFR1 it is not correct. Below is how they should look. > > > > interface Serial0/2/0 > > no ip address > > encapsulation frame-relay MFR1 > > clock rate 2000000 > > no arp frame-relay > > ! > > interface Serial0/2/1 > > no ip address > > encapsulation frame-relay MFR1 > > clock rate 2000000 > > no arp frame-relay > > > > Task 6.17 > > In the DSG on page 184 the commands under So Let's change things for R2 and > R4 are wrong. Below are the correct commands. > > > > R2 > > _ _ _ _ > > conf t > > int s0/1/0.1 > > frame-relay class FREEK > > end > > wr > > > > R4 > > _ _ _ _ > > conf t > > int s0/0/0 > > frame-relay interface-dlci 402 > > class FREEK > > end > > wr > > > > Note: In the DSG after these commands are entered they do a show frame end > keep on R2. In the DSG example everything is perfect. I have run through > this lab several times and I get at least one failure on R2. I believe this > is normal because I never see any other failures and the last failure time > keeps increasing on R2. Plus EEK is up and that is the goal of the task. > > > > 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: 255, Receive Sequence Number: 255 > > Configured Event Window: 3, Configured Error Threshold: 2 > > Total Observed Events: 3, Total Observed Errors: 2 > > Monitored Events: 0, Monitored Errors: 0 > > Successive Successes: 0, End-to-end VC Status: UP > > > > RECEIVE SIDE STATISTICS > > > > Send Sequence Number: 254, Receive Sequence Number: 254 > > Configured Event Window: 3, Configured Error Threshold: 2 > > Total Observed Events: 2, Total Observed Errors: 0 > > Monitored Events: 1, Monitored Errors: 0 > > Successive Successes: 1, End-to-end VC Status: UP > > > > Failures Since Started: 1, Last Failure: 00:00:07 > > > > Note: If I do a show frame end keep on R4 the results are perfect. > > > > R4#sh frame end keep > > > > End-to-end Keepalive Statistics for Interface Serial0/0/0 (Frame Relay DTE) > > > > DLCI = 402, DLCI USAGE = LOCAL, VC STATUS = ACTIVE (EEK UP) > > > > SEND SIDE STATISTICS > > > > Send Sequence Number: 3, Receive Sequence Number: 4 > > Configured Event Window: 3, Configured Error Threshold: 2 > > Total Observed Events: 6, Total Observed Errors: 0 > > Monitored Events: 3, Monitored Errors: 0 > > Successive Successes: 3, End-to-end VC Status: UP > > > > RECEIVE SIDE STATISTICS > > > > Send Sequence Number: 4, Receive Sequence Number: 3 > > Configured Event Window: 3, Configured Error Threshold: 2 > > Total Observed Events: 6, Total Observed Errors: 0 > > Monitored Events: 3, Monitored Errors: 0 > > Successive Successes: 3, End-to-end VC Status: UP > > _______________________________________________ > 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
