R3303-HP HSR6800 Routers MPLS Command Reference

336
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.
Usage guidelines
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 and the
tunnel encapsulation type must be GRE or MPLS TE.
The value range for the tunnel-number argument is 0 to 20479.
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 device, so that the device 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 ra f f ic d e st i n e d fo r 1.1.1.1 c a n n ot b e t ra n s m i t te 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 (BGP-VPNv4 subaddress family
view/BGP-L2VPN address family view/BGP-VPLS address
family view)
Use reflect between-clients to enable route reflection between clients.
Use undo reflect between-clients to disable the function.
Syntax
reflect between-clients
undo reflect between-clients
Default
Route reflection between clients is enabled.
Views
BGP-VPNv4 subaddress family view, BGP-L2VPN address family view, BGP-VPLS address family view
Default command level
2: System level
Usage guidelines
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.