Configuring Non-labeled Public Network Routes to Be Iterated to LSPs
By default, non-labeled public network routes can be iterated to outgoing interfaces and next hops, but cannot be iterated to tunnels. After this feature is configured, non-labeled public network routes can be iterated to LSPs.
Pre-configuration Tasks
Before configuring non-labeled public network routes to be iterated to LSPs, complete the following tasks:
-
Configure a local LDP session. For details, see Configuring Basic Functions of MPLS LDP.
-
Configure an IP prefix list if non-labeled public network routes to be iterated to LSPs need to be limited.
Procedure
- Run system-view
The system view is displayed.
- Run route recursive-lookup tunnel [ ip-prefix ip-prefix-name ] [ tunnel-policy policy-name ]
The non-label public network route is allowed to be iterated to the LSP to forward through MPLS.
By default, the non-label public network route can be iterated only to the outbound interface and the next hop but not the LSP tunnel.
If ip-prefix ip-prefix-name is not set, all static routes and non-labeled public BGP routes will be preferentially iterated to LSP tunnels.
- Run commit
The configuration is committed.