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

Reminder

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

upgrade
Knowledge Base

FAQ-Whether Routes on the NE40E80E Public Network Can Be Iterated to the Tunnel

Publication Date:  2012-07-27  |   Views:  2  |   Downloads:  0  |   Author:  SU1001891224  |   Document ID:  EKB0000409530

Contents

Issue Description

 Q:
Whether routes on the NE40E80E public network can be iterated to the tunnel.
Version: V300R002 
 

Alarm Information

 Null 

Handling Process

 A:
Yes.
By default, non-label routes can only be iterated to the egress and next hop and cannot be iterated to the tunnel. You can run the route recursive-lookup tunnel command to enable non-label routes on the public network to inherit the tunnel ID of IGP or the static route and realize MPLS forwarding.
The route recursive-lookup tunnel command is used to enable non-label routes on the public network to be iterated to the tunnel and only valid to the non-label routes on the public network that require iteration. The IP-prefix list can be used to accurately specify the non-label routes that require the iteration. You can use the undo form of this command to recover the default configuration (non-label routes are only iterated to the egress and next hop).
The route recursive-lookup tunnel [ ip-prefix ip-prefix-name ] command enables non-label routes on the public network to be iterated to the LSP tunnel and perform MPLS forwarding. 
 

Root Cause

 Null 

Suggestions

 Null