Hi, here are the REAL LABS, (FEW TOPICS), FOR OPEN DISCUSSION: "chek it out" ------------------------------------------------------------------------------------------------------------------------ (for querries, reply back ) : IMPLEMENT IPV4 EIGRP (2.2) -------------------- .Configure EIGRP YY between R4 and R5. .Configure EIGRP 100 as in diagram. .EIGRP updates should be advertised only out to the interfaces in the IGP topology. .Configure SW3 such that it will not receive, any EIGRP Querries. SW3 shoul also not send out information about BB3 routes to the EIGRP 100 neighbors. .Do not configure any kind of outgoing filtering to do this. .On SW3, use route-maps to tag any CLASS A network address routes sourced from the external EIGRP with tag 200. .Redistribute loopback 0 of R4 and R5 into EIGRP YY. .SW3 redistribute EIGRP 100 to OSPF summarize to the following routes into an aggregate: 198.1.1.4/30 198.2.1.0/24 198.2.3.0/24 198.2.5.0/24 SOLUTION: -------- R4: -- router eigrp YY red connected route-map LB0 network YY.YY.254.2 0.0.0.255 no auto-summary ! route-map LB0 permit 10 match interface loopback 0 ! R5: -- router eigrp YY red connected route-map LB0 network YY.YY.254.1 0.0.0.255 no auto-summary ! route-map LB0 permit 20 match interface loopback 0 ! SW3: -- router eigrp 100 network 150.3.YY.1 0.0.0.0 no auto-summary eigrp stub receive-only ! router ospf1 red eigrp 100 subnets route-map O2E summary-address 198.0.0.0 255.252.0.0 ! ip prefix-list O2E permit 0.0.0.0/1 le 32 ! route-map O2E permit 10 match ip address prefix-list O2E match route-type external set tag 200 ! route-map O2E permit 20 ------------------------------------------------------------------------------------------------------------------------- IMPLEMENTING IPV4 BGP (2.3) ---------------------- Reffering the BGP routing diagram. Configure BGP within these parameters .SW1 connects to BB1 (150.1.YY.254); and from BB1 SW1 receives 197.68.Z.0/24 networks with As PATH : 254 253 .SW2 connects to BB2 (150.2.YY.254); and from BB2 SW2 receives 197.68.Z.0/24 networks with AS PATH : 254 .SW2 should modify the AS PATH of its learned routes; adding AS253 by using a single route-map. .SW1 , SW2 , R2 , R3 are IBGP peers. (Dont use next-hop-self and route_reflector) .Use BGP command to cause R2 to prefer SW2 as the exit point for ASYY to AS 254, and R3 to prefer SW1 and the exit pointfor ASYY to AS 254. .Both R2 and R3 should still have routes to the other exit point in their BGP table. .Use ONLY the loopback 0 IP address to propagate BGP route info. .No IGP router should be advertised to AS254. SOLUTION: -------- R2: -- router bgp YY no sync no auto-summary neighbor YY.YY.3.3 remote-as YY neighbor YY.YY.3.3 update-source loopback 0 neighbor YY.YY.7.7 remote-as YY neighbor YY.YY.7.7 update-source loopback o neighbor YY.YY.8.8 remote-as YY neighbor YY.YY.8.8 update-source loopback 0 neighbor YY.YY.8.8 weight 1000 R3: -- router bgp YY no sync no auto-summary neighbor YY.YY.2.2 remote-as YY neighbor YY.YY.2.2 update-source loopback 0 neighbor YY.YY.7.7 remote-as YY neighbor YY.YY.7.7 update-source loopback 0 neighbor YY.YY.8.8 remot-as YY neighbor YY.YY.8.8 update-source loopback 0 neighbor YY.YY.7.7 weight 1000 SW1: -- router bgp YY no sync no auto-summary neighbor YY.YY.2.2 remote-as YY neighbor YY.YY.2.2 update-source loopback 0 neighbor YY.YY.3.3 remote-as YY neighbor YY.YY.3.3 update-source loopback 0 neighbor YY.YY.8.8 remote-as YY neighbor YY.YY.8.8 update-source loopback 0 neighbor 150.1.YY.254 remote-as 254 SW2: -- router bgp YY no sync no auto-summary neighbor YY.YY.2.2 remote-as YY neighbor YY.YY.2.2 update-source loopback 0 neighbor YY.YY.3.3 remote-as YY neighbor YY.YY.3.3 update-source loopback 0 neighbor YY.YY.7.7 remote-as YY neighbor YY.YY.7.7 update -source loopback 0 neighbor 150.2.YY.254 remote-as 254 neighbor 150.2.YY.254 route-map FROM_BB2 in ! route-map FROM_BB2 permit 10 set as-path prepend 253 ------------------------------------------------------------------------------------------------------
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
