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>

Reminder

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

upgrade

FAQ-The Configuration When NE40 Configures Policy Route and Designates Next-hop as Sub-interface

Publication Date:  2012-07-27 Views:  46 Downloads:  0
Issue Description
Q:
NE40 configures policy route and the next-hop is designated as sub-interface, it prompts fault.
flow-action a redir ip 10.10.10.1 Atm1/0/0.1
The interface is sub-interface or on mainboard 
Alarm Information
Null
Handling Process
A:
If it is required to send packet to next-hop 10.10.10.1, local device uses sub-interface to connect with opposite device, next-hop egress must be designated when defining flow and action. Configure next-hop egress as sub-interface, it prompts fault. As long as next-hop address is correct, next-hop egress is designated as master-interface.
Under system-view:
rule-map  r-CNC ip 161.236.11.128 0.0.0.127 any     
//define flow based on source address//         
flow-action f-CNC redirect ip 10.10.10.1  Atm1/0/0
//define action: forcibly designate next-hop address and egress// 
eacl CNC r-CNC f-CNC 
//bind flow and action//
At inbound interface import eacl:
  access-group eacl CNC  
Root Cause
Null
Suggestions
Null

END