peer label-route-capability (BGP multi-instance VPN instance IPv4 address family view)

Function

The peer label-route-capability command enables a BGP device to exchange labeled routes with a specified peer.

The undo peer label-route-capability command disables this function.

By default, this function is disabled.

Format

peer ipv4-address label-route-capability [ check-tunnel-reachable ]

undo peer ipv4-address label-route-capability

Parameters

Parameter	Description	Value
ipv4-address	Specifies the IPv4 address of a peer.	It is in dotted decimal notation.
check-tunnel-reachable	Checks tunnel reachability when imported routes are sent as labeled routes.	-

Parameter

Description

Value

ipv4-address

Specifies the IPv4 address of a peer.

It is in dotted decimal notation.

check-tunnel-reachable

Checks tunnel reachability when imported routes are sent as labeled routes.

Views

BGP multi-instance VPN instance IPv4 address family view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
bgp	write

Usage Guidelines

Usage Scenario

The peer label-route-capability command is applicable to the scenario where labeled IPv4 routes need to be exchanged between the local end and the specified peer.

Configuring the check-tunnel-reachable parameter can only be used to check tunnels on IPv4 public networks.

If the check-tunnel-reachable parameter is configured, BGP advertises IPv4 unicast routes to peers when routed tunnels are unreachable or advertises labeled routes to peers when routed tunnels are reachable. In VPN scenario, this eliminates the risk of establishing an MP-EBGP peer relationship between PEs over a faulty LSP because this will cause data forwarding failures.
If the check-tunnel-reachable parameter is not configured, BGP advertises labeled routes to peers whether the tunnels for imported routes are reachable or not.
NOTE:
To disable tunnel reachability checking, run the peer label-route-capability command, not the undo peer label-route-capability command.

Prerequisites

The peer as-number command has been run to create a peer.

Configuration Impact

If the peer label-route-capability command is run multiple times, the latest configuration overwrites the previous one.

Example

# Enable BGP to send the labeled routes.

<HUAWEI> system-view
[~HUAWEI] ip vpn-instance vpna
[*HUAWEI-vpn-instance-vpna] ipv4-family
[*HUAWEI-vpn-instance-vpna-af-ipv4] route-distinguisher 100:1
[*HUAWEI-vpn-instance-vpna-af-ipv4] vpn-target 111:1 both
[*HUAWEI-vpn-instance-vpna-af-ipv4] quit
[*HUAWEI-instance-vpna] quit
[*HUAWEI] bgp 100 instance a
[*HUAWEI-bgp-instance-a] ipv4-family vpn-instance vpna
[*HUAWEI-bgp-instance-a-vpna] peer 10.1.1.1 as-number 100
[*HUAWEI-bgp-instance-a-vpna] peer 10.1.1.1 label-route-capability