Agree with Jason. Note : the devices been cleared and the entire pod was revert before loading any configs.
Regards ... amer On Sun, Oct 24, 2010 at 1:43 AM, Jason Maynard <[email protected]>wrote: > I have seen that from time to time (not sure what labs) but I think it > forces you do some troubleshooting right off the hop. The only time that I > get a little frustrated by it is when I want to get into a specific > technology and I have to do some troubleshooting first. It does enhance the > learning experience (especially from a troubleshooting perspective) but > perhaps should be documented. > > > > This may also be a result of not clearing the devices before starting. > > > > One Feature I would like to see is the ability to load labs based on > sections. This will allow you to focus on specific technologies without > having to build up the configuration to the point of where you want to > focus. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Di Bias, Steve > *Sent:* October-23-10 6:20 PM > *To:* Amer Mustafa; [email protected] > *Subject:* Re: [OSL | CCIE_RS] Workbook 1 LAB 18. > > > > Can you be more specific? Why were they “down”? There was no DLCI’s > configured? The wrong DLCI’s were configured? The wrong LMI type? > > > > I just looked at the initials configs for VOL1 LAB18 and everything is > configured just fine > > > > *R2* > > > > interface Serial0/1/0 > > no ip address > > encapsulation frame-relay > > no arp frame-relay > > no frame-relay inverse-arp > > frame-relay lmi-type cisco > > no shutdown > > ! > > interface Serial0/1/0.24 point-to-point > > ip address 150.50.24.2 255.255.255.252 > > frame-relay interface-dlci 204 > > ! > > interface Serial0/1/0.25 point-to-point > > ip address 150.50.25.2 255.255.255.252 > > frame-relay interface-dlci 205 > > ! > > interface Serial0/1/0.26 point-to-point > > ip address 150.50.26.2 255.255.255.252 > > frame-relay interface-dlci 206 > > > > *R4* > > > > interface Serial0/0/0 > > no ip address > > encapsulation frame-relay > > no arp frame-relay > > no frame-relay inverse-arp > > frame-relay lmi-type cisco > > no shutdown > > ! > > interface Serial0/0/0.24 point-to-point > > ip address 150.50.24.1 255.255.255.252 > > frame-relay interface-dlci 402 > > > > *R5* > > > > interface Serial0/1/0 > > no ip address > > encapsulation frame-relay > > no arp frame-relay > > no frame-relay inverse-arp > > frame-relay lmi-type cisco > > no shutdown > > ! > > interface Serial0/1/0.25 point-to-point > > ip address 150.50.25.1 255.255.255.252 > > frame-relay interface-dlci 502 > > > > *R6* > > > > interface Serial0/1/0 > > no ip address > > encapsulation frame-relay > > serial restart-delay 0 > > no arp frame-relay > > no frame-relay inverse-arp > > frame-relay lmi-type cisco > > no shutdown > > ! > > interface Serial0/1/0.26 point-to-point > > ip address 150.50.26.1 255.255.255.252 > > frame-relay interface-dlci 602 > > > > > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Amer Mustafa > *Sent:* Saturday, October 23, 2010 3:10 PM > *To:* [email protected] > *Subject:* [OSL | CCIE_RS] Workbook 1 LAB 18. > > > > *Workbook 1 LAB 18.* > > > > *The inital configs of the routers are with FR proper config, which leads > that the FR links are down. i had to configure ( Frame-relay interface DLCI > ) on all the routers. just would like to know if this is not avilable in the > initial configs on purpose ? becuase its not mentioned in the lab to check > FR links or verify them.* > > > > > > *thanks * > > *amer* > > > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
