peer allow-cluster-loop
Function
The peer allow-cluster-loop command sets the number of times that the local cluster ID is allowed to be included in the cluster_list of a received route.
The undo peer allow-cluster-loop command cancels the configuration.
By default, the local cluster ID cannot be included in the cluster_list of a received route.
Format
peer { group-name | ipv4-address } allow-cluster-loop [ number ]
undo peer { group-name | ipv4-address } allow-cluster-loop
Parameters
| Parameter | Description | Value |
|---|---|---|
| group-name | Specifies the name of a peer group. | The name is a string of 1 to 47 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| ipv4-address | Specifies the IPv4 address of a peer. | - |
| number | Specifies the number of times that the local cluster ID is allowed to be included in the cluster_list of a received route. | The value is an integer ranging from 1 to 10. The default value is 1. |
Usage Guidelines
A router reflector (RR) generally checks the cluster_list in a received route. If the RR finds that its own cluster ID is included in the cluster_list carried in the received route, the RR discards this route and does not reflect this route to its clients.
After the peer allow-cluster-loop command is configured on a level-2 RR, you must configure a routing policy on the level-2 RR to forcibly select routes advertised by PEs. If no routing policy is configured, VPN-target routes flap, which also causes the flapping of VPNv4 routes.
Example
# Set the number of times that the local cluster ID is allowed to be included in the cluster_list of a received route to 2.
<sysname> system-view
[sysname] bgp 100
[sysname-bgp] peer 1.1.1.2 as-number 200
[sysname-bgp] ipv4-family vpn-target
[sysname-bgp-af-vpn-target] peer 1.1.1.2 enable
[sysname-bgp-af-vpn-target] peer 1.1.1.2 allow-cluster-loop 2