Pete To clarify - if I just adjust the local preference on the receiving router, that should do it?
But if I didn't have an admin control of the receiving router I would do it on the advertising router by requesting a community. Just sanity checking... On Fri, May 23, 2008 at 4:53 PM, Pete Templin <[EMAIL PROTECTED]> wrote: > Gary Roberton wrote: > > Router A BGP table entry is shown here; >> >> * 90.0.0.0 <http://90.0.0.0> 10.40.1.6 <http://10.40.1.6> >> 50 0 64604 1000 i >> >> *> 10.40.1.2 <http://10.40.1.2> >> 0 64603 1000 i >> >> > Paths come from different neighbor ASes, so MED doesn't apply unless you > override default behavior. > > On most newer IOSes, oldest path wins, so everything's working as expected. > > You should tweak a different knob to achieve the desired results. Origin > code comes to mind as an easy twiddle. Or, have the remote routers send a > community to request a particular local preference (as someone else > suggested) - you'll need a community-list and a route-map to catch this. Or > just write a route-map to adjust local-pref or weight upon local receipt of > the prefix. > > pt > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
