Forcing AirCards to be less preferred in core

[jmattbullen]

I currently have a design issue with the addition of an ATT aircard being available for our remote sites.  This connection comes in on a separate ATT vrf but it comes into our ATT router which as you can see gets preferred by EIGRP when bgp gets redistributed into it.  I want the ATT aircard bgp routes to be the least preferred when coming into EIGRP.  My strategy so far for this has been to somehow mark the BGP routes coming in from the aircard network so that when I redistribute into EIGRP I can lower the bandwidth to 80000 and thus would be the least preferred.  I've tried the following:

!Setting tags, this does not work.  After more research looks like you can only tag when doing the redistribute command

#####

route-map ATTAirCards permit

set tag 200

router bgp x

neighbor 2.2.2.2 route-map ATTAirCards in

####

! I then got rid of the ATTAirCards route-map and tried a match of the outgoing interface in the route-map that gets directly reference by the redistribution.  This only works though if the next hop in the routing table is an interface not an IP.

route-map BGP->EIGRP permit 10

match interface Tunnel5

set metric 8000 100 255 1 1 1500

! lastly I have brought back the ATTAirCards route-map and have tried using communities.  It is adding the community but the metric is not changing in EIGRP

route-map ATTAirCards permit 10

set community 999

ip community standard AttAirCardComunity permit 999

route-map BGP->EIGRP  permit 10

match community AttAirCardCommunity

set metric 80000 100 255 1 1500

Usually, when things seem complicated there is a simple solution so I'm open to ideas.

[jmattbullen]

I guess I could do ibgp between the VZB and ATT routers and on the bgp neighbors using aircards apply a lower local pref.  Since redistribution only redistributes routes that are in the routing table the ATT router would have better BGP metrics for either the eBGP routes coming from the ATT cloud or if the store has a primary verizon connection the ATT router would receive a better route from the VZB router.  I'd like to avoid that if possible though.  I like idea of the ATT router only knowing about ATT routes and so forth.

[jmattbullen]

ugh, sometimes this job sucks.  I spent most of the day on this trying this or that and always the route in the eigrp topology table would match the bandwidth that is in the catch-all at the bottom of the route-map.  The fix for this was simply to change the metric in the set command from 80000 to 75000 then back.  now it's working fine with the configuration above using communities.  Does anyone know why I had to do that?  I did clear bgp relationship with the test neighbor when I was testing but I did not clear the EIGRP process because I'm playing around in production.

ip community-list AttAirCardCommunity permit 50

route-map BGP->EIGRP permit 10
description match community 50(AttAirCards).  Set metric to least preferred
match community AttAirCardCommunity
set metric 80000 100 255 1 1500

route-map BGP->EIGRP permit 50
description default match for ATT.  HQ prefers ATT for most sites
set metric 150000 100 255 1 1500