What "requirement" is not met? The task is referring only to outbound advertisement/filtering from Cat1.
The task specifies that Cat2 should not receive certain routes from Cat1, and that Cat3 should not receive certain routes from Cat1. NOWHERE in the task does it say that Cat2 and Cat3 can't learn about the other routes from each other. NOWHERE does it say that Cat2 can't directly use Cat1 as the next hop for the AS 3550 routes learned from Cat3 or vice versa. Why do you think that forcing traffic to bounce off the other switch is the "correct" next hop? Marvin Greenlee, CCIE #12237 (R&S, SP, Sec) Senior Technical Instructor - IPexpert, Inc. Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: [EMAIL PROTECTED] Progress or excuses, which one are you making? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louis S Sent: Monday, July 07, 2008 4:14 PM To: osl Subject: [OSL | CCIE_RS] Vol 2 Section 3 task 4.2 BGP route manipulation Shouldn't "next-hop-self" be configured on CAT2 and Cat3 This is the only way to get the BGP to show the correct next-hop see below: Cat2(config-router)#sib BGP table version is 7, local router ID is 110.99.102.102 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *>i172.16.1.0/24 110.99.103.103 0 100 0 3550 i *> 172.16.2.0/24 110.99.101.101 0 0 3550 i *>i172.16.3.0/24 110.99.103.103 0 100 0 3550 i *> 172.16.4.0/24 110.99.101.101 0 0 3550 i Without it, and this is what the PG does, all the next hops would says 110.99.101.101 which technically does not meet the requirement!
