Policy-based routing didn’t come into effect for configuration problem

Publication Date:  2012-11-15 Views:  347 Downloads:  0
Issue Description

The demand is the network segment whose source IP is 192.168.10.0 go netcom line, other default go telecom, after configured the policy-based routing found the flow still out from telecom interface.
Alarm Information
None.
Handling Process
Removed the default parameter in the policy-based routing, it is normal.
apply ip-address next-hop 1.1.1.1------It is normal after changed
In the strategy routing to cancel the default parameters after normal

Apply IP address next hop 1.1.1.1 - - - - - - - - after the change of normal
Root Cause
Check the policy-based routing
acl number 2010
rule 5 permit source 192.168.10.0 0.0.0.255
ip route-static 0.0.0.0 0.0.0.0 1.1.1.1 netcom
ip route-static 0.0.0.0 0.0.0.0 2.2.2.2 telecom
policy-based-route huawei permit node 1
  if-match acl 2010
  apply ip-address default next-hop 1.1.1.1-----this place should not have the “default”
Add default parameters means: first check the routing table, if it doesn’t match then enable the policy-based routing; USG received the 192.168.10.0 message which wants to access to the external network, first check their own routing table found there is a default route out to external network, so it will not match the policy-based routing, therefore the policy-based not becomes effective.
Suggestions
If there is no special demand suggest using fixed format “apply ip-address next-hop IP” configure, don't add additional parameters.

END