profithaa.blogg.se

Eigrp to bgp redistribution timers
Eigrp to bgp redistribution timers












Origin incomplete, localpref 100, valid, external Origin incomplete, localpref 200, valid, external At this point, the 10.200.1.0/24 subnet was not accessible.īut you also see that this did not happen to the 10.100.1.0/24 subnet and that subnet was accessible. In this example, you can see that the 10.200.1.0/24 NY subnet became a locally originated route because of the redistribution. Redistribute bgp 65000 metric 100000 120 route-map BGP>EIGRP Redistribute bgp 65000 metric 100000 10 route-map BGP>EIGRP Use TAGs to prevent EIGRP from going into BGP when redistributing. Now when the Primary Path came back up, Router A did not take the same prefix as the best one because the same prefix was already in the BGP table originated by itself (Router A – redistributed from EIGRP) with a weight of 32768. Router A received the prefix from EIGRP and because the same prefix was not received from PE1 (Primary Path) because of their shutdown of the peer, Router A took the EIGRP prefix as the best one and redistributed it into BGP. It redistributed that prefix into EIGRP like it’s supposed to.

eigrp to bgp redistribution timers eigrp to bgp redistribution timers eigrp to bgp redistribution timers

Router B receives the 10.xx.0.0/24 prefixes from PE2 (Secondary Path).














Eigrp to bgp redistribution timers