No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


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

Publication Date:  2012-11-15 Views:  708 Downloads:  0

Issue Description

The demand is the network segment whose source IP is go netcom line, other default go telecom, after configured the policy-based routing found the flow still out from telecom interface.

Alarm Information


Handling Process

Removed the default parameter in the policy-based routing, it is normal.
apply ip-address next-hop is normal after changed
In the strategy routing to cancel the default parameters after normal

Apply IP address next hop - - - - - - - - after the change of normal

Root Cause

Check the policy-based routing
acl number 2010
rule 5 permit source
ip route-static netcom
ip route-static telecom
policy-based-route huawei permit node 1
  if-match acl 2010
  apply ip-address default next-hop 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 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.


If there is no special demand suggest using fixed format “apply ip-address next-hop IP” configure, don't add additional parameters.