task 4.13 loop prevention

Checking in the archives, it seems this step is unneccesary, but still a good exercise.  It seems that if the administrative distance was not already set higher for external ospf routes and tagging was being used to prevent looping for R3 and R6 loopbacks, then the SG is still overly complex.  The tags are preserved throughout the routing domain and the retagging just seems redundant and confusing.  I was able to achieve the same results tagging from RIP to EIGRP and then deny those tagged routes when redistibuting from OSPF into EIGRP on both R2 and R4.

Anyone else come to the same conclusion?


Sign In or Register to comment.