Task 3.3: Troubleshooting DMVPN will be broken at a later stage (task 6.1) when we're asked to configure CoPP on R2. The criteria for successful task 3.3 are: R1# ping 22.22.22.22 !!!! R4# ping 22.22.22.22 !!!! However in 6.1 we're told to block all pings to R2 sourced from non-RFC1918 space. This violates the above criteria because those pings are sourced from the tunnel end-points (172.1.0.x).
The Lab Debrief section doesn't mention that conflict, hence, I suppose, this is just a bug. Bad if something similar surfaces in a real lab: the evaluation scripts would fail the task 3.3 when doing pings - if the CoPP is not tuned, but if it is - this might be seen as a violation of task 6.1. Besides, the solution provided by Yusuf to 6.1 uses 2 access-lists, and I did it with a single acl; again - the scripts will fail the task. On almost every task evaluation Yusuf says: "The highlighted portions are of the utmost importance. The grading for this question is strongly based on these highlighted items. Any incorrect or mismatched item will result in a null score for this question." For both of the above tasks the conflicting items are highlighted... I wonder if somebody have an idea about to what extend the automated lab evaluation is used? There are tasks that will not be tested by real traffic or situation, rather a correct syntax is checked. I also confirm that the FPM filter (task 8.3 of lab_1) does not work for traffic destined to the router itself, at least in 12.4(24)T1. _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
