I have a specific static routes that require advertising into EIGRP and eventually into BGP for remote offices. My goal is to cut down on the configuration updates required for updating not only the static routes for new additions, but the route-map ACL for EIGRP, and the policy-route ACL to the next hop.
I've learned that route tags may be an option for routing traffic with less configuration. Basically I can tag a static route with a number, (such as 20). Then I can create a route-map that matches on tag 20, and sets tag 20 and configure this within EIGRP to match and advertise that tag again. On the receiving router I should be able to perform this same step for BGP in a similar manner (EIGRP-to-BGP route-map that retags), however, I still have a policy route that doesn't quite fit with this tagging method (ACL has a source/destination - whereas a prefix list does not).
My goal here is to create specific static routes with tags, and have those tags carry through and advertise properly (including a policy route-map or equivalent ) without me having to update 3 other ACLs everytime. Policy-map doesn't play well with the redistribution - any one come up with other ideas for something similar?