protect lsp-tunnel for-all-instance peer-ip
Function
The protect lsp-tunnel for-all-instance peer-ip command configures a public and VPN protection tunnel template in hot backup scenarios.
The undo protect lsp-tunnel peer-ip command deletes a specified public and VPN protection tunnel template.
By default, no public and VPN protection tunnel template is created.
This command is supported only on the NetEngine 8000 F1A.
Usage Guidelines
Usage Scenario
In RUI scenarios, previously, the protection tunnels must be configured for the public network and each VPN separately, and MBGP must run between devices when VPN protection tunnels are configured. To simplify tunnel configuration in RUI scenarios, run the protect lsp-tunnel for-all-instance peer-ip command to configure a public and VPN protection tunnel template. Then a public protection tunnel is automatically created, and a VPN protection tunnel is triggered by user login, without needing to configure MBGP.
Prerequisites
MPLS LSPs have been configured between the master and slave devices for public protection tunnels, and VPNs have been configured between master and slave devices for VPN protection tunnels.
Configuration Impact
Network-to-user traffic forwarding is affected. Run the display remote-backup-service command to check the tunnel status. If the Tunnel-state field displays Up, the tunnel is working properly.
Precautions
This command is supported only on the admin VS.
The protect tnl-policy policy-name peer-ip ip-address and protect ip-vpn-instance vpn-instance-name peer-ip ip-address command are used to specify a tunnel for a private network and a tunnel for a VPN, respectively. These two commands can be used together with the protect lsp- tunnel for-all-instance peer-ip command. The protect lsp-tunnel for-all-instance peer- **ip ** command has a higher priority. Specifically, when these commands are configured at the same time, the configuration of the protect lsp- tunnel for-all-instance peer-ip command takes effect in priority.