So by that, my question is do you have 6" or 9" plumbing throughout your
house? ;)
Scott
On 10/22/10 2:13 PM, Narbik Kocharians wrote:
> I am trying to prove that studying labs that have 50 NINJA or 007 tasks is
> NOT what gets you in the lab or prepares you for the lab, the lab focuses on
> easy stuff, you won't see tasks like:
>
> Redistribute on the appropriate router(s) such that my bathroom flushes 3
> times every 985 ms, and with each flush it should use 2.3 liters of water.
>
> These tasks are NOT teaching you anything, these tasks tell you how creative
> the author can be.
>
> On Fri, Oct 22, 2010 at 12:09 PM, Tom Solski <tom.solski_at_gmail.com> wrote:
>
>> OK, I did lab it up. R2 and R3 exchange default routes and because of
>> split horizon one of the routers will not send 0/0 to R1. Disabling
>> split horizon on R2 and R3 will not help either. The solution is to
>> prevent R2 and R3 to exchange default routes, but it took me *more
>> than 5 minutes* to realize that the solutions is within R2-R3 and R1
>> has nothing to do with it.
>>
>> So how do you find out ? Do you just KNOW that by looking at the
>> diagram, start with debug ...
>>
>>
>> On Fri, Oct 22, 2010 at 2:25 PM, Narbik Kocharians <narbikk_at_gmail.com>
>> wrote:
>>> *One of the students told me that he did not see the second puzzle, so i
>> am
>> > posting my original post for the second one.*
>>> The reason I asked to Unicast was so one student will not see the answer
>>> from another student, this forces some people to lab the scenario and
>> think.
>>>
>>> *Now that I have your attention*, here are some solutions to the problem,
>> I
>>> am sure there are more ways, and please feel free to add to the list.
>>>
>>> 1. Filter all RIPs updates coming from R2 on R3 fa0/0 interface with
>>> access-list/prefix-list/route-map and vice versa.
>>> 2. Filter the default route from R2 on R3 and vice versa.
>>> 3. Instead of filtering, you could also use the distance command and set
>> it
>>> to 255.
>>> 4. Filter default from R2 on R3, and R3 to R2 using an "Offset-list in".
>>> 5. Configure passive-interface on the F0/0 interfaces of R2 and R3, and
>> then
>>> on Both routers configure a "Neighbor R1".
>>> 6. Configure the ports that R2 and R3 are connected as "swi Protect".
>>> 7. Configure Private Vlan; configuring the F0/0 interface of R2 and R3 in
>>> Isolated, and the F0/0 interface of R1 in primary.
>>> 8. Mac ACLs or an IP access-list and a Vlan Access-map that denies the
>> two
>>> routers from communicating.
>>> 9. Configuring an MQC that matches on the destination-address MAC and
>> drops
>>> that traffic in the policy-map that's assigned to the F0/0 interface of
>> R2
>>> and Vice versa.
>>> 10. Dropping the traffic by filtering the MAC on the switchports.
>>> 11. Put R2 and R3 in different subnets and do a "no validate-update
>> source"
>>> on R1.
>>>
>>>
>>> *Now could you imagine the following scenario*: you are in a CCIE lab,
>> and
>>> you just finished the troubleshooting section, so you feel like Mike
>> Tyson
>>> because you did well, but the first question in the configuration section
>> is
>>> the following:
>>>
>>> R1 is running RIPv2.
>>> R6 is also running RIPv2.
>>> There are bunch of routers between R1 and R6 running OSPF or whatever
>>> routing protocol that turns you on.
>>>
>>> I want R6 to get all R1 s RIP routes.
>>>
>>> Do not use redistribution, AToM, IPnIP or GRE tunnels to accomplish this.
>>> Come up with 2 solutions. Common unicast me the solution..
>>>
>>>
>>> There is a reason I am doing this, trust me .
>>>
>>> --
>>> Narbik Kocharians
>>> CCSI#30832, CCIE# 12410 (R&S, SP, Security)
>>> www.MicronicsTraining.com <http://www.micronicstraining.com/>
>>> Sr. Technical Instructor
>>> YES! We take Cisco Learning Credits!
>>> Training And Remote Racks available
>>>
>>>
>> > Blogs and organic groups at http://www.ccie.net
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Fri Oct 22 2010 - 19:33:31 ART
This archive was generated by hypermail 2.2.0 : Mon Nov 01 2010 - 06:42:06 ART