On 7 Aug 2011, at 15:24, marc abel wrote: >>> -the acl specifies deny host Fe80::6 host FF02::9 and is applied on R5 >>> how is that supposed to block routing traffic from R6? > > How does Rip send it's updates? It multicasts them to reserved > addresses. In IPv4 this is 224.0.0.9, but what is it in IPv6? FF02::9. > So your access list is blocking multicast traffic sourced from R6 to > the multicast address. Since the access list is configured on R5, R6 > will still be sending them, R5 will just ignore them.
Got it. I thought of FF02::9 as FE80::9, i.e. the actual host address of R9. > > So now R5 isn't going to get these routes at all, however R7 will. R7 > will not advertise them to R5 however because it is on the same subnet > it learned them on. If we disable split horizon on R7 then it can > advertise them back to R5. Now R5 receives them from R7 and not from > R6. Task complete. I think i get that. Need to do some more reading on basic split horizon i'm afraid. > >>> What do they mean by the statement, "depending on the link of the backbone >>> connection you may want go get clarification as to whether the backbone has >>> the same speed interface as your device." >>> >>> Why is that relevant? The backbone is connected by ethernet, i'm sure i >>> would get a duplex error mismatch if it would be set wrong. I just don't >>> see how it ties into the question. > > > Int f0/1 > speed 100 > duplex full > bandwidth 10000 > > Which speed will the interface use for QOS? Will you see that in a > duplex mismatch? > I am not sure. I suppose the bandwidth statement. No you will not see that, but i still don't realise why that is important for the QOS to function? 100% of anything is still 100%. > > > On Sun, Aug 7, 2011 at 7:50 AM, Alef <[email protected]> wrote: >> >>> Dear diary, 2 questions and then i'll leave you in peace for today :-) >>> >>> Vol2, Lab8, Task 8.2 >>> >>> -the acl specifies deny host Fe80::6 host FF02::9 and is applied on R5 >>> how is that supposed to block routing traffic from R6? >>> >>> Anyway i can imagine that would us to see now R7 in the routing table, but >>> what is up with the split horizon disabling on r7? All that allows is that >>> R7 can now send R5 and R6 routes back to them. Split horizon is still on >>> R6. How does turning it off on R7 make R7 the next-hop router. >>> >>> Bit confused here as to what that would accomplish. >>> >>> Vol2, Lab8, Task 9.2 >>> >>> What do they mean by the statement, "depending on the link of the backbone >>> connection you may want go get clarification as to whether the backbone has >>> the same speed interface as your device." >>> >>> Why is that relevant? The backbone is connected by ethernet, i'm sure i >>> would get a duplex error mismatch if it would be set wrong. I just don't >>> see how it ties into the question. >>> >>> Thanks as always, >> >> _______________________________________________ >> 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 >> _______________________________________________ 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
