Policy Based Routing
-
matiasniosi
-
matiasniosi
agungaryo wrote:hi matiasniosi ,
CMIIW , I just trying to help your case .
yups,if we use static routing it would be globally used for all your customer .
I don't know for 6850 Omniswitch solution but if you consider to use 7750 SR ,
for classifying your customer ( I guess you mean source address based ) you can use "IP Filter "
and for backup routing (3 ISP) you can use "redirect-policy" ( technically you should insert it in "action" part of "ip filter" and you can use PING or URL or SNMP test to perform backup )
so,I guess "IP Filter " + "Redirect Policy" should solve your issue
regards
agung aryo
Thank you Agung,
so it's not possible to implement redirect-policy on a 6850? I looked at the documentation to see if it is possible to use ping as a policy condition but couldn´t find it. Is this right?
Thanks.
-
cedric1
-
agungaryo
matiasniosi wrote:Thank you Agung,
so it's not possible to implement redirect-policy on a 6850? I looked at the documentation to see if it is possible to use ping as a policy condition but couldn´t find it. Is this right?
Thanks.
I don't know exactly but as far as I've known , 6850 can't do redirect policy for redundancy ,but 6850 can do PBR as cedric said .
CMIIW.even you use cisco I guess you have to use "event manager" ,not only pbr .
regard
agung aryo
-
matiasniosi
Maybe I can solve my issue by using BGP prepending (adding mi AS number multiple times in the as-path when advertized to certain ISPs). Is this possible in a 6850 (prepending for some routes in one ISP and not in a second one)?
This way I can divide my public IP range in subnets and give them different treatment setting the local preference (for outbound traffic) and prepending (for inbound traffic).
The thing is that I think that local prefence is global and won't let me set it depending on the source address for outbound traffic.
Maybe I should give all my internalclients the same redundancy setting and forget about my problem...
Thanks to all!!
This way I can divide my public IP range in subnets and give them different treatment setting the local preference (for outbound traffic) and prepending (for inbound traffic).
The thing is that I think that local prefence is global and won't let me set it depending on the source address for outbound traffic.
Maybe I should give all my internalclients the same redundancy setting and forget about my problem...
Thanks to all!!
-
cedric1
Hello
I'have a meeting with alcatel tomorrow and I have some Product Ehancement Request.
I will add this into :
Need to add in a static route gateway tracking via icmp
if unreachable, gateway should go out of routing table and use next best static route (based of metric value)
this need to be enable in PBR too. Gateway in a policy based routing need to be checked via icmp. In the same case we need to be able to add
a backup gateway in a pbr rule.
I'have a meeting with alcatel tomorrow and I have some Product Ehancement Request.
I will add this into :
Need to add in a static route gateway tracking via icmp
if unreachable, gateway should go out of routing table and use next best static route (based of metric value)
this need to be enable in PBR too. Gateway in a policy based routing need to be checked via icmp. In the same case we need to be able to add
a backup gateway in a pbr rule.
-
matiasniosi
cedric1 wrote:Hello
I'have a meeting with alcatel tomorrow and I have some Product Ehancement Request.
I will add this into :
Need to add in a static route gateway tracking via icmp
if unreachable, gateway should go out of routing table and use next best static route (based of metric value)
this need to be enable in PBR too. Gateway in a policy based routing need to be checked via icmp. In the same case we need to be able to add
a backup gateway in a pbr rule.
That would solve all my problems. Thanks again!
-
cedric1
-
cedric1
******** per ********
I have open a PER for this :
Content of PER
Description of Enhancement Required:
Description:
Our customer encounter this type of pb :
We use actually static routing and PBR routing solution in our network.
Problem is that the switch is not able to detect that a gateway is going down.
Gateway is not BFD enable.
So we need to have an option in a static route and PBR gateway : track-ip
This track-ip need to be done by and option via icmp or via arp.
If we get an arp or icmp reply => gateway is reachable an is up in routing table
If we get no arp or icmp reply => gateway is no reachable an is not available in active routing table.
So we can still see this route in show ip router database in inactive route part.
This should be the same in PBR (policy based routing) gateway.
So for example: have 2 gateways in PBR rule, with track-ip option via icmp or arp.
If one is going down, next best gateway is used.
Content of PER
Description of Enhancement Required:
Description:
Our customer encounter this type of pb :
We use actually static routing and PBR routing solution in our network.
Problem is that the switch is not able to detect that a gateway is going down.
Gateway is not BFD enable.
So we need to have an option in a static route and PBR gateway : track-ip
This track-ip need to be done by and option via icmp or via arp.
If we get an arp or icmp reply => gateway is reachable an is up in routing table
If we get no arp or icmp reply => gateway is no reachable an is not available in active routing table.
So we can still see this route in show ip router database in inactive route part.
This should be the same in PBR (policy based routing) gateway.
So for example: have 2 gateways in PBR rule, with track-ip option via icmp or arp.
If one is going down, next best gateway is used.

