ccnp route packet tracer labs

ccnp route packet tracer labs

Both R1 and R2 inject 100.0.1.0 and 100.0.2.0 into BGP using network . We look R5 are BGP table: http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/31sga/configuration/guide/pvlans.html Same interface mode ( access , trunk ) ? OpenConfirm In the example, the static route associated with the next hop does not have this attribute, so it is not matched. The medium to root has the least overhead, so the uplink port is RP . SW3 is different. Since the bandwidth of the interface connected to root is only 10M , the interface connecting SW2 wins as RP . Finally choose DP . I won't go into details. After these subnet routes are passed to AS200 , R4 and R5 do route summarization, and the summary routes are passed to AS100 . At this time, if R1 wants to go to the 172.16.1.0 and 2.0 subnets, it may be to go to one side, either to R2 or R3 . This is of course not the optimal implementation. We hope to see R1 go to 1.0 subnet and go to R2. , go 2.0 subnets go R3 , then the idea is to achieve in R2 and R3 deployment BGP deaggregation , the R2 to AS100 injected Criteria breakdown 172.16.1.0/24 ,ccnp route packet tracer labs, R3 injection 172.16.2.