391Parametersnumber: Specifies the number of the preferred tunnel, in the range of 0 to 63. A smaller number meansa higher priority.interface tunnel tunnel-number: Specifies a tunnel interface for the preferred tunnel. The tunnel-numberargument represents the tunnel interface number. The value range for the tunnel-number argument is from0 to 255.disable-fallback: With this keyword specified, the tunneling policy does not select other paths when thispreferred tunnel is matched (the tunnel's destination address and encapsulation type are both matched)but is unavailable.Usage guidelinesIn 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 thetunnel encapsulation type must be MPLS TE.Examples# Tunnel interfaces Tunnel 0, Tunnel 2, and Tunnel 3 have the same destination address 1.1.1.1. Configurea tunneling policy po1 for the device, so that the device selects tunnels for traffic destined for 1.1.1.1 in thisorder: Tunnel 0, Tunnel 2, Tunnel 3. If all three tunnels are unavailable, tunnel selection is stopped andtraffic destined for 1.1.1.1 cannot be transmitted. For traffic going to other destinations, the device selectstunnels by type and only one CR-LSP tunnel can be selected. 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 1reflect between-clients (BGP-VPNv6 subaddress family view)Use reflect between-clients to enable route reflection between clients.Use undo reflect between-clients to disable the function.Syntaxreflect between-clientsundo reflect between-clientsDefaultRoute reflection between clients is enabled.ViewsBGP-VPNv6 subaddress family viewDefault command level2: System levelUsage guidelinesIf fully meshed interconnections exist between the clients, route reflection is not required. Otherwise, anRR is required for routes to be reflected from one client to every other client.
