|
Posted by Charlie Root on February 22, 2006, 10:44 am
If you were Registered and logged in, you could reply and use other advanced thread options > Hi ILya,
>
> Thanks for your reponse.
>
> Charlie Root wrote:
>>>I want the outbound traffic which ip source address is 11.12.13.14 to be
>>>able to reach all networks depending on the neighbor local-pref
>>>parameters. ( This solution currently work )
>>>
>>
>> don't need a policy map for this, just let it fall through to the
>> routing-based forwarding (= don't do anything specific about this
>> address).
>>
>>
>>>I want the outbound traffic which ip source address is 11.12.13.15 to not
>>>be able to go through "Transit 2" and "Peer with A".
>>>
>>
>> you can use 'verify-availability' as described in "Policy Based Routing
>> with the Multiple Tracking Options Feature Configuration Example"
>
> I dont want to verify the availability of a particular link.
> I just want to create some specific routing policy for some address of my
> network through my ebgp routes.
>
the problem with this is that only route with best metric (local-pref) will
make it into the routing table (bgp table itself is not used for forwarding
decisions, it only installs best path into the routing table).
the only solution comes to my mind is to use VRF for each of this addresses
and for each of your peer links, then define policy which routes are
exchanged between VRFs. But I wouldn't do it - you surely will end up with
at least double increase in memory requirements (to keep at least two copies
of the routing table). I haven't tried this yet (but actually curious to try
it in the lab when I have time), so can't be sure what other caveats are
there and if it going to work at all.
Kind regards,
iLya
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map