Yes I have found that WB2 has more issues than WB1 or WB3. In reality though, I only use WB2 to increase speed and don't rely heavily on the DSG or agree with it sometimes. While I feel your pain, as long as you know you're doing things correctly you can look past this and keep moving forward. If you look through past emails you will see that I have brought this up in the past as well, in fact for Volume 2 Lab 10 I found the WB and DSG didn't match at all (although this may have been fixed now).
Here was my email about this back in May: While working on Volume 2 Lab 10 I noticed that the WB doesn't match the DSG. For example it's good up until Task 2.4, at this point things are not the same. Mind you, I was using "printed" WB and DSG so I downloaded the PDF's from IPexpert and they have the same issue there. In Task 2.4 the WB states: You should ensure that users can telnet to Cat1 at 192.168.100.10 and Cat2 at 192.168.100.12. Use the VTY password of "ipexpert" But in the DSG it states: You should ensure that users can telnet and configure each switch at 192.168.100.x, where x is the switch number (e.g. Cat1 = 192.168.100.11) In Task 2.5 the WB states: All switches should respond to SNMP RW requests with a community string of "ipexpert" It should also send traps to a NMS station locate at 192.168.100.253 In the DSG the question isn't even close to the same: Configure the s0/2/0 and s0/2/1 serial interfaces between R6 and R9 using the 192.168.90.0/30, with R6 having the lower IP address. The S0/2/0 and S0/2/1 serial interfaces should support Frame Relay using DLCI 69 It only does downhill from there so no point to keep going, however this completely screwed up my lab verification when going through the DSG, I think one of these needs to be updated. I haven't checked all the others, but I hope they don't have the same issue, especially since I use printed materials most of the time. Any help on getting these things corrected would be appreciated. Thanks Thank you, Steve Di Bias Network Engineer - Information Systems Valley Health System - Las Vegas Office - 702- 369-7594 Cell - 702-241-1801 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of mark salmon Sent: Monday, September 26, 2011 6:41 AM To: [email protected] Subject: [OSL | CCIE_RS] Ipexpert I am somewhat disappointed with the IPexpert labs, i am seeing too many errors that should be caught. I am working on WB 2. Lab #5 has typpgraphical errors the lab diagram did not match the description in the text, for BGP they clearly sated that the new loopback addresses (task 4.2) that states the router should advertise 192.168.100.0/23 via Ibgp. The answer have us filter those routes globally in BGP so r6 will get the /23 and not the more specific. My solution was to use a RM and block the more specific to the Ibgp peer and not to the EBGP peer. Not sure if that is an error per se, I am more concerned about the actual errors ("wrong" IP addresses) concerns me. Thoughts? "Question with boldness even the existence of a God; because, if there be one, he must more approve of the homage of reason, than that of blind-folded fear." Thomas Jefferson " Where ignorance is bliss 'tis folly to be wise" _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com 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. 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 Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
