ccnp r&s switch 300-115

ccnp r&s switch 300-115

Show interface | include bia Encapsulation Status Weighting 100 (default 100), thresholds: lower 1, upper 100 R1 uses 1.1.1.1 as the update source, trying to establish a BGP connection with 2.2.2.2 , and the local IP address of R2 is 1.1.1.1 , and Route-refresh Router ospf 1 The above network is equivalent to network 1.0.0.0 ( network has a class declaration) bibliography 192.1.168.3 3 0003.44d6.c52f 2BB648EB interface-id 1bdb223f 10.1.13.1 Then look at the R4 's BGP table: Sw1(config-if-range)#switchport trunk encapsulation dot1q R4 and R2 , we look R2 , R2 moment from R4 has learned this RIP routes, if it from the R3 also learn the route and of the route metric is smaller, then, R2 will preferably from R3 this Routes , so that R1 , R2 , and R3 form a routing loop. First, let's get a glimpse of route-map . Looking at the figure above,ccnp r&s switch 300-115, we redistribute OSPF routes into RIP on R2 . As mentioned above, when re-publishing, you can use the metric keyword to set the metric after the route is re-advertised into RIP . Set to 1 here . The immediate result is that all OSPF routes injected into RIP have a metric of 1 . So what if I want to make some flexibility adjustments? For example, I hope that after the route is injected into RIP , the metric of the 192.168.1.0 route is 1 and the metric of 2.0 is 2 . Traditional redistribution is impossible.