330
By default, no preferred tunnel exists.
In a tunneling policy, you can configure up to 64 preferred tunnels.
The tunnel interfaces specified for the preferred tunnels can have the same destination address. The tunnel
encapsulation type must be MPLS TE.
Syntax
preferred-path number interface tunnel tunnel-number [ disable-fallback ]
undo preferred-path number
View
Tunneling policy view
Default level
2: System view
Parameters
number: Specifies the number of the preferred tunnel, ranging from 0 to 63. A smaller number means a
higher priority.
interface tunnel tunnel-number: Specifies a tunnel interface for the preferred tunnel. tunnel-number
represents the tunnel interface number, which ranges from 0 to 127.
disable-fallback: With this keyword specified, the tunneling policy does not select other paths when this
preferred tunnel is matched (the tunnel’s destination address and encapsulation type are both matched)
but is unavailable.
Examples
# Tunnel interfaces Tunnel 0, Tunnel 2, and Tunnel 3 have the same destination address 1.1.1.1. Configure
a tunneling policy po1 for the switch, so that the switch selects tunnels for traffic destined for 1.1.1.1 in this
order: Tunnel 0, Tunnel 2, Tunnel 3. If all three tunnels are unavailable, tunnel selection is stopped and
t r a f f i c d e s t i n e d f o r 1.1.1.1 c a n n o t b e t r a n s m i t t e d. Fo r traffic going to other destinations, the device selects
tunnels by type, and only one CR-LSP tunnel can be selected.
<Sysname> system-view
[Sysname] tunnel-policy po1
[Sysname-tunnel-policy-po1] preferred-path 0 interface tunnel 0
[Sysname-tunnel-policy-po1] preferred-path 2 interface tunnel 2
[Sysname-tunnel-policy-po1] preferred-path 3 interface tunnel 3 disable-fallback
[Sysname-tunnel-policy-po1] tunnel select-seq cr-lsp load-balance-number 1
reflect between-clients
Description
Use the reflect between-clients command to enable route reflection between clients.
Use the undo reflect between-clients command to disable the function.
By default, route reflection between clients is enabled.
If fully meshed interconnections exist between the clients, route reflection is not required. Otherwise, an RR
is required for routes to be reflected from one client to every other client.
To Next Page
Loading...
Need help?
General
