CloudEngine S16700 V600R023C00 Command Reference
EVPN Configuration Commands
- advertise bgp l2vpn-family evpn lowest-priority enable
- advertise l2vpn evpn
- advertise l2vpn evpn (BGP-VPN instance IPv4 address family view/BGP-VPN instance IPv6 address family view)
- advertise route-reoriginate evpn disable
- bestroute add-path (BGP-EVPN address family view)
- dampening (BGP-EVPN address family view)
- detect loop-times
- detect loop-times (EVPN-MAC-DUP view)
- display bgp evpn all routing-table dampening parameter
- display bgp evpn all routing-table statistics
- display bgp evpn group
- display bgp evpn peer
- display bgp evpn peer verbose
- display bgp evpn routing-table (peer)
- display bgp evpn routing-table (prefix condition)
- display bgp evpn routing-table dampened
- display bgp evpn routing-table flap-info
- display bgp evpn routing-table(prefix)
- display bgp evpn update-peer-group
- display bgp evpn vpn-instance routing-table
- display bgp evpn vpn-instance routing-table (prefix)
- display bgp evpn vpn-instance routing-table (verbose)
- display evpn mac-duplication
- display evpn vpn-instance
- display evpn vpn-instance mac-duplication
- display evpn vpn-instance mac-duplication history
- evpn
- evpn ( bd-evpn-instance view )
- evpn-overlay enable
- evpn-route-origin igp
- export route-policy (EVPN instance view)
- export route-policy evpn
- filter-policy
- import route-policy (EVPN instance view)
- import route-policy evpn
- irb asymmetric (BGP-VPN instance IPv4 address family view)
- irb asymmetric (BGP-VPN instance IPv6 address family view)
- l2vpn-family evpn
- l2vpn-family evpn (bgp-instance-af-evpn-extend view)
- l3-reoriginate different-split-group
- local mac-only-route no-generate
- mac-duplication (EVPN instance view)
- mac-duplication (Global EVPN configuration view)
- mac-ip route generate-mac
- mac-route no-advertise
- nexthop recursive-lookup default-route (BGP-EVPN address family view)
- nexthop recursive-lookup default-route (bgp-muli-instance-af-evpn view)
- nexthop recursive-lookup delay (BGP-EVPN address family view)
- nexthop recursive-lookup restrain disable (EVPN instance view)
- nexthop recursive-lookup restrain disable (Global EVPN configuration view)
- peer advertise (BGP-EVPN address family view)
- peer advertise (BGP-EVPN address family view) (group)
- peer advertise (BGP-EVPN address family view) (IPv6)
- peer advertise add-path (BGP-EVPN address family view)
- peer advertise add-path (BGP-EVPN address family view) (group)
- peer advertise add-path (bgp-muli-instance-af-evpn view)
- peer advertise route-reoriginated (BGP-EVPN address family view)
- peer advertise route-reoriginated (BGP-EVPN address family view) (group)
- peer advertise-community (BGP-EVPN address family view)
- peer advertise-community (BGP-EVPN address family view) (group)
- peer advertise-community (bgp-muli-instance-af-evpn view)
- peer advertise-large-community
- peer advertise-large-community (BGP-EVPN address family view)
- peer advertise-large-community (BGP-EVPN address family view) (group)
- peer allow-as-loop (BGP-EVPN address family view) (group)
- peer allow-as-loop (BGP-EVPN address family view) (IPv6)
- peer allow-as-loop (BGP-EVPN address family view)(IPv4)
- peer attribute-id (BGP-EVPN address family view)
- peer attribute-id (BGP-EVPN address family view) (IPv6)
- peer capability-advertise add-path (BGP-EVPN address family view)
- peer capability-advertise add-path (BGP-EVPN address family view) (group)
- peer capability-advertise add-path (bgp-muli-instance-af-evpn view)
- peer enable (BGP-EVPN address family view) (group)
- peer enable (BGP-EVPN address family view) (IPv4)
- peer enable (BGP-EVPN address family view) (IPv6)
- peer graceful-restart static-timer (BGP-EVPN address family view)
- peer graceful-restart static-timer (BGP-EVPN address family view)(IPv6)
- peer group (BGP-EVPN address family view) (IPv6)
- peer group (BGP-EVPN address family view)(IPv4)
- peer high-priority (BGP-EVPN address family view)
- peer high-priority (BGP-EVPN address family view) (group)
- peer high-priority (BGP-EVPN address family view) (ipv6)
- peer import reoriginate (BGP-EVPN address family view)
- peer import reoriginate (BGP-EVPN address family view) (group)
- peer mac-limit (BGP-EVPN address family view)
- peer mac-limit (BGP-EVPN address family view) (group)
- peer mac-limit (BGP-EVPN address family view) (ipv6)
- peer next-hop-invariable (BGP-EVPN address family view)
- peer next-hop-invariable (BGP-EVPN address family view) (group)
- peer next-hop-invariable (BGP-EVPN address family view) (IPv6)
- peer peer-as-check (BGP-EVPN address family view)(IPv6)
- peer peer-as-check(BGP-EVPN address family view)
- peer peer-as-check(BGP-EVPN address family view)(group)
- peer preferred-value (BGP-EVPN address family view) (group)
- peer preferred-value (BGP-EVPN address family view)(IPv4)
- peer reflect-client (BGP-EVPN address family view) (group)
- peer reflect-client (BGP-EVPN address family view) (IPv6)
- peer reflect-client (BGP-EVPN address family view)(IPv4)
- peer route-limit (BGP-EVPN address family view)
- peer route-limit (BGP-EVPN address family view) (group)
- peer route-policy export (BGP-EVPN address family view)
- peer route-policy export (BGP-EVPN address family view) (group)
- peer route-policy export (BGP-EVPN address family view) (IPv6)
- peer route-policy import (BGP-EVPN address family view) (group)
- peer route-policy import (BGP-EVPN address family view) (IPv6)
- peer route-policy import (BGP-EVPN address family view)(IPv4)
- peer route-update-interval (BGP-EVPN address family view)
- peer route-update-interval (BGP-EVPN address family view) (group)
- peer route-update-interval(bgp-muli-instance-af-evpn view)
- peer split-group (BGP-EVPN address family view)
- peer split-group (BGP-EVPN address family view) (group)
- peer transit-med-to-ebgp
- peer transit-med-to-ebgp (group)
- peer transit-med-to-ebgp(BGP-EVPN address family view) (IPv6)
- policy vpn-target (BGP-EVPN address family view)
- reflect between-clients (BGP-EVPN address family view)
- reflect change-path-attribute (BGP-EVPN address family view)
- reflect same-split-group
- reflector cluster-id (BGP-EVPN address family view)
- refresh bgp evpn
- refresh bgp evpn (IPv6)
- reset bgp evpn
- reset bgp evpn (IPv6)
- reset bgp evpn dampening
- reset bgp evpn flap-info
- reset evpn mac-duplication
- reset evpn vpn-instance mac-duplication
- retry-cycle
- retry-cycle(EVPN-MAC-DUP view)
- slow-peer absolute-detection (BGP-EVPN address family view)
- slow-peer detection (BGP-EVPN address family view)
- vpn-target (EVPN instance view)
- vpn-target evpn (VPN instance IPv4 address family view)
- vpn-target evpn (VPN instance IPv6 address family view)
- vpn-target evpn (VPN instance view)
- peer advertise encap-type
- peer advertise encap-type (group)
- reset bgp slow-delete sid evpn
- segment-routing ipv6 best-effort evpn
- segment-routing ipv6 locator evpn
- inclusive-route pmsi-compatible
- peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)
- peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)(group)
- peer srv6-label-compatible(BGP-EVPN address family view)
- peer srv6-label-compatible(BGP-EVPN address family view)(group)
advertise bgp l2vpn-family evpn lowest-priority enable
Function
The advertise bgp l2vpn-family evpn lowest-priority enable command enables BGP to set the priorities of BGP routes to be advertised to the lowest.
The undo advertise bgp l2vpn-family evpn lowest-priority enable command restores the default configuration.
By default, BGP is disabled from setting the priorities of BGP routes to be advertised to the lowest.
Format
advertise bgp l2vpn-family evpn lowest-priority enable
undo advertise bgp l2vpn-family evpn lowest-priority enable
Usage Guidelines
Usage Scenario
You can run the advertise bgp l2vpn-family evpn lowest-priority enable command to enable BGP on the device to forcibly set the priorities of BGP routes to be advertised to the lowest (changing the MED to the maximum value and the Local_Pref to the minimum value). This configuration ensures that service traffic can be switched to the other device.
Precautions
The advertise bgp l2vpn-family evpn lowest-priority enable command takes effect for all routes in the EVPN address families.
If at least one of the advertise bgp l2vpn-family evpn lowest-priority enable and advertise lowest-priority all-address-family peer-up commands is run, BGP can set the priorities of routes (to be advertised) in the preceding address families to the lowest when BGP peers in these address families go up from down. After the advertise bgp l2vpn-family evpn lowest-priority enable command is run, modifying the MED and Local_Pref attributes of BGP routes to be advertised through an export routing policy does not take effect.advertise l2vpn evpn
Function
The advertise l2vpn evpn command enables a VPN instance to advertise EVPN IP prefix routes.
The undo advertise l2vpn evpn command restores the default configuration.
By default, a VPN instance is disabled from advertising EVPN IP prefix routes.
Format
advertise l2vpn evpn [ import-route-multipath ]
undo advertise l2vpn evpn [ import-route-multipath ]
Parameters
Parameter | Description | Value |
---|---|---|
import-route-multipath |
Advertises all routes with the same destination address in a VPN instance as EVPN IP prefix routes. |
- |
Views
BGP-VPN instance IPv4 address family view,BGP-VPN instance IPv6 address family view,BGP multi-instance VPN instance IPv6 address family view
Usage Guidelines
Usage Scenario
If EVPN IP prefix routes are used to advertise IP routes between devices, you need to enable the VPN instance to advertise EVPN IP prefix routes so that the local VPN instance can advertise IP routes to the peer device through BGP EVPN peer relationships.
If import-route-multipath is not specified in the advertise l2vpn evpn command, the VPN instance advertises only the optimal route among the routes with the same destination address when advertising EVPN IP prefix routes. In load balancing scenarios, the import-route-multipath parameter must be specified in the advertise l2vpn evpn command so that all routes with the same destination address are advertised as EVPN IP prefix routes. By default, the locally leaked routes of a VPN instance are not advertised as EVPN IP prefix routes. To solve the problem of mutual access between VPN instances, run the advertise l2vpn evpn command with the include-local-cross-route parameter specified, the locally leaked routes collected by the VPN instance can be advertised as EVPN IP prefix routes and then sent to the remote device through BGP EVPN peer relationships.Example
<HUAWEI> system-view [HUAWEI] ip vpn-instance vpna [HUAWEI-vpn-instance-vpna] route-distinguisher 1:1 [HUAWEI-vpn-instance-vpna-af-ipv4] quit [HUAWEI-vpn-instance-vpna] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv4-family vpn-instance vpna [HUAWEI-bgp-vpna] advertise l2vpn evpn
advertise l2vpn evpn (BGP-VPN instance IPv4 address family view/BGP-VPN instance IPv6 address family view)
Function
The advertise l2vpn evpn command enables a VPN instance to advertise EVPN IP prefix routes.
The undo advertise l2vpn evpn command restores the default configuration.
By default, a VPN instance is disabled from advertising EVPN IP prefix routes.
Format
advertise l2vpn evpn { best-route | valid-routes } [ import-route-multipath ]
undo advertise l2vpn evpn { best-route | valid-routes } [ import-route-multipath ]
Parameters
Parameter | Description | Value |
---|---|---|
best-route |
Advertises only optimal routes in a VPN instance as EVPN IP prefix routes. |
- |
valid-routes |
Advertises only valid routes in a VPN instance as EVPN IP prefix routes. |
- |
import-route-multipath |
Advertises all routes with the same destination address in a VPN instance as EVPN IP prefix routes. |
- |
Views
BGP-VPN instance IPv4 address family view,BGP-VPN instance IPv6 address family view,BGP multi-instance VPN instance IPv6 address family view
Usage Guidelines
Usage Scenario
If EVPN IP prefix routes are used to advertise IP routes between devices, you need to enable the VPN instance to advertise EVPN IP prefix routes so that the local VPN instance can advertise IP routes to the peer device through BGP EVPN peer relationships.
By default, the device advertises external routes in the VPN instance routing table, including invalid routes and non-optimal routes, as EVPN IP prefix routes. To prevent invalid routes from being advertised, you can specify valid-routes. If you want to advertise only the optimal VPN routes as EVPN IP prefix routes, specify best-route. If the advertise l2vpn evpn command does not contain the import-route-multipath parameter when it is run, the VPN instance advertises only optimal locally imported routes as EVPN IP prefix routes. In load-balancing scenarios, the import-route-multipath parameter must be specified in the advertise l2vpn evpn command, so that the VPN instance advertises all locally imported routes with the same destination address as EVPN IP prefix routes.Example
<HUAWEI> system-view [HUAWEI] ip vpn-instance vpna [HUAWEI-vpn-instance-vpna] route-distinguisher 1:1 [HUAWEI-vpn-instance-vpna-af-ipv4] quit [HUAWEI-vpn-instance-vpna] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv4-family vpn-instance vpna [HUAWEI-bgp-vpna] advertise l2vpn evpn valid-routes
advertise route-reoriginate evpn disable
Function
The advertise route-reoriginate evpn disable command disables a device from re-originating EVPN routes in a specified VPN instance as VPN or EVPN routes or re-originating VPN routes in a specified VPN instance as EVPN routes.
The undo advertise route-reoriginate evpn disable command restores the default configuration.
By default, the function to re-originate EVPN routes in a specified VPN instance as EVPN or VPN routes or to re-originate VPN routes in a specified VPN instance as EVPN routes is disabled.
Usage Guidelines
A device can be configured to re-originate IP prefix routes and IRB routes received from an EVPN peer and then advertise them to a VPN or EVPN peer. A device can also be configured to re-originate routes received from a VPN peer and then advertise them to an EVPN peer. You can run the advertise route-reoriginate evpn disable command to disable the function to re-originate EVPN routes as EVPN or VPN routes or to re-originate VPN routes as EVPN routes in a specified VPN instance.
Example
<HUAWEI> system-view [HUAWEI] ip vpn-instance vpna [HUAWEI-vpn-instance-vpna] ipv4-family [HUAWEI-vpn-instance-vpn-af-ipv4] quit [HUAWEI-vpn-instance-vpna] ipv6-family [HUAWEI-vpn-instance-vpn-af-ipv6] quit [HUAWEI-vpn-instance-vpna] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv4-family vpn-instance vpna [HUAWEI-bgp-vpna] advertise route-reoriginate evpn disable [HUAWEI-bgp-vpna] quit [HUAWEI-bgp] ipv6-family vpn-instance vpna [HUAWEI-bgp-6-vpna] advertise route-reoriginate evpn disable
bestroute add-path (BGP-EVPN address family view)
Function
The bestroute add-path command enables BGP Add-Path and configures the number of routes that the device can select.
The undo bestroute add-path command restores the default configuration.
By default, BGP Add-Path is not enabled.
Format
bestroute add-path path-number path-number
undo bestroute add-path [ path-number path-number ]
Parameters
Parameter | Description | Value |
---|---|---|
path-number path-number |
Specifies the number of routes that the device can select. |
The value is an integer ranging from 2 to 64. |
Usage Guidelines
Usage Scenario
In a scenario with an RR and clients, if the RR has multiple routes to the same destination (with the same prefix), the RR selects an optimal route from these routes and then sends only the optimal route to its clients. Therefore, the clients have only one route to the destination. If a link along this route fails, route convergence takes a long time, which cannot meet the requirements for high reliability. To address this issue, deploy the BGP Add-Path feature on the RR. With BGP Add-Path, the RR can send two or more routes with the same prefix to a specified peer. These routes can back up each other or load-balance traffic, which ensures high reliability in data transmission.
Prerequisites
Run the evpn-overlay enable command to enable EVPN as the VXLAN control plane.
Follow-up Procedure
Run the peer capability-advertise add-path send command to enable the device to advertise Add-Path routes to a specified peer.
Run the peer advertise add-path command to specify the number of routes to be advertised to a peer.Precautions
The bestroute add-path command can be configured and takes effect on any device, but it is mainly configured on an RR. After this command is run, BGP can select multiple routes.
The selected Add-Path routes may not work in load balancing mode. They can work in load balancing mode only when they meet load balancing conditions. If the optimal route is a labeled route, only labeled routes are selected as Add-Path routes. If the optimal route is a common route, only common routes are selected as Add-Path routes. To enable the device to accept the Add-Path routes received from the specified peer, you need to run the peer capability-advertise add-path receive command on the device. BGP Add-Path advertises multiple routes with the same prefix. Therefore, in specific scenarios, two devices may select each other as the next hop, causing a traffic loop. Avoid such scenarios when deploying BGP Add-Path. The bestroute add-path and deterministic-med commands are mutually exclusive. Do not run them together.dampening (BGP-EVPN address family view)
Function
The dampening command enables EVPN route dampening or modifies EVPN route damping parameters.
The undo dampening command disables EVPN route dampening.
By default, BGP route flapping suppression is disabled.
Format
dampening [ half-life-reach reuse suppress ceiling | [ route-policy route-policy-name ] ] * [ update-standard ]
dampening ibgp [ half-life-reach reuse suppress ceiling | [ route-policy route-policy-name ] ] * [ update-standard ]
undo dampening
undo dampening ibgp
Parameters
Parameter | Description | Value |
---|---|---|
half-life-reach |
Specifies the half life of a reachable route. |
The value is an integer ranging from 1 to 45, in minutes. The default value is 15. |
reuse |
Specifies a Reuse value. If the penalty value of a route falls below the Reuse value, the route is reused. |
The value is an integer ranging from 1 to 20000. The default value is 750. |
suppress |
Specifies a Suppress value. If the penalty value of a route exceeds the Suppress value, the route is dampened. |
The value is an integer ranging from 1 to 20000 and must be greater than the value of reuse. The default value is 2000. |
ceiling |
Specifies a penalty ceiling. |
The value is an integer ranging from 1001 to 20000. The configured value must be greater than that of suppress. The default value is 16000. |
route-policy route-policy-name |
Specifies the name of a route-policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
update-standard |
Enables BGP to add the standard penalty value to the route carried in each received Update message (excluding Withdraw message). |
- |
ibgp |
Enables IBGP route flap damping. |
- |
Usage Guidelines
Usage Scenario
If a policy is configured for route dampening, routes are preferentially matched against the dampening parameters defined by route-policy in the command.
The four parameters of the command are mutually dependent. If you configure one of the parameters, the other parameters also need to be configured in the command. EVPN dampening measures route stability using a penalty value. The greater the penalty value, the less stable a route. Each time route flapping occurs (the device receives a Withdraw), EVPN adds a penalty value to the route carried in the message. If a route changes from active to inactive, the penalty value increases by 1000. If the penalty value of a route exceeds the Suppress value, the route is dampened. The device does not add the route to the IP routing table or advertise any Update message to other EVPN peers. EVPN removes the best flag of the route. If the route is carried in an Update message, EVPN adds a d flag to the route; if the route is carried in a Withdraw message, EVPN adds an h flag to the route. If a route carries both a d flag and an h flag, the route is considered a deleted one. After the penalty value reaches the penalty ceiling, it does not increase any more. The penalty value of a dampened route reduces by half after a half-life period. If the route is carried in an Update message and its penalty value decreases to the Reuse value, the route becomes reusable, and EVPN removes the d flag from it, adds it to the IP routing table if it is an optimal route, and advertises an Update message carrying the route to EVPN peers. If the route is carried in a Withdraw message and its penalty value decreases to 0, EVPN deletes this route from the EVPN routing table. After EVPN route dampening is configured, any parameter in the command can be used to dampen flapping routes. You can adjust the parameters as required. To increase the dampening time of flapping routes, perform any of the following operations (to reduce the dampening time, perform otherwise):- Increase ceiling.
- Increase half-life-reach.
- Reduce reuse.
Prerequisites
Run the evpn-overlay enable command to enable EVPN as the VXLAN control plane.
Configuration Impact
If the dampening command is run more than once, the latest configuration overrides the previous one.
After the dampening command is run, the system dampens unstable routes. Specifically, the system does not add unstable routes to the EVPN routing table or advertise them to other EVPN peers.Precautions
When configuring EVPN route flapping suppression, pay attention to the following points:
- The reuse, suppress, and ceiling thresholds increase in sequence.
- According to the formula MaxSuppressTime = half-life-reach x 60 x (ln(ceiling/reuse)/ln(2)), if the value of MaxSuppressTime is less than 1, the suppression cannot be performed. Therefore, to ensure that the value of MaxSuppressTime is greater than or equal to 1, the value of ceiling/reuse must be large enough. When route-policy route-policy-nameis configured, the following items can be specified: IPv4 ACL, AS_Path filter, AS_Path length filter, community filter, route cost, IPv6 route destination address, VPN target extended community filter, outbound interface, MPLS label, Large-community filter, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on routing information, next-hop address prefix list based on IPv6 routing information, route priority, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, and route dampening parameters. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level messages.
detect loop-times
Function
The detect loop-times command sets loop detection parameters for MAC duplication suppression.
The undo detect loop-times command restores the default configuration.
By default, the loop detection period for MAC duplication suppression is 180s, and the threshold for MAC entry flaps is 5 within a detection period.
Format
detect loop-times loop-times detect-cycle detect-cycle-time
undo detect loop-times detect-cycle
undo detect loop-times loop-times detect-cycle detect-cycle-time
Parameters
Parameter | Description | Value |
---|---|---|
loop-times |
Specifies the maximum number of times MAC entry flapping is allowed in a detection period. |
The value is an integer ranging from 3 to 10. |
detect-cycle detect-cycle-time |
Specifies a detection period. |
The value is an integer ranging from 60 to 900, in seconds. The value must be a multiple of 10. |
Usage Guidelines
Usage Scenario
On an EVPN VXLAN, two PEs may interconnect through both network-side and access-side links. If this is the case, BUM traffic loops and MAC route flapping both occur, preventing devices from working properly. In this case, MAC duplication suppression on the devices works. By default, the system checks the number of times a MAC address entry flaps within a detection period (180s by default). If the number of times a MAC address entry flaps exceeds the upper threshold (5 by default), the system considers MAC route flapping to be occurring on the network and consequently suppresses the flapping MAC routes. The suppressed MAC routes cannot be sent to a remote PE through a BGP EVPN peer relationship. To modify the detection period or the threshold for MAC entry flapping, run the detect loop-times command.
Configuration Impact
If the detect loop-times command is run in both EVPN instance view and global EVPN configuration view, the configuration in the EVPN instance view takes precedence.
Precautions
This command takes effect does not take effect for MAC/IP routes but takes effect only for MAC routes.
detect loop-times (EVPN-MAC-DUP view)
Function
The detect loop-times command sets loop detection parameters for MAC duplication suppression.
The undo detect loop-times command restores the default configuration.
By default, the loop detection period for MAC duplication suppression is 180s, and the threshold for MAC entry flaps is 5 within a detection period.
Format
detect loop-times loop-times detect-cycle detect-cycle-time
undo detect loop-times detect-cycle
undo detect loop-times loop-times detect-cycle detect-cycle-time
Parameters
Parameter | Description | Value |
---|---|---|
loop-times |
Specifies the maximum number of times MAC entry flapping is allowed in a detection period. |
The value is an integer ranging from 3 to 10. |
detect-cycle detect-cycle-time |
Specifies a detection period. |
The value is an integer ranging from 60 to 900, in seconds. The value must be a multiple of 10. |
Usage Guidelines
Usage Scenario
On an EVPN VXLAN network, two PEs may interconnect through both network-side and access-side links. If this is the case, BUM traffic loops and MAC route flapping both occur, preventing devices from working properly. In this case, MAC duplication suppression on the devices works. By default, the system checks the number of times a MAC address entry flaps within a detection period (180s by default). If the number of times a MAC address entry flaps exceeds the upper threshold (5 by default), the system considers MAC route flapping to be occurring on the network and consequently suppresses the flapping MAC routes. The suppressed MAC routes cannot be sent to a remote PE through a BGP EVPN peer relationship. To modify the detection period or the threshold for MAC address entry flapping, run the detect loop-times command.
Configuration Impact
If the detect loop-times command is run in both EVPN instance view and global EVPN configuration view, the configuration in the EVPN instance view takes precedence.
Precautions
This command takes effect does not take effect for MAC/IP routes but takes effect only for MAC routes.
display bgp evpn all routing-table dampening parameter
Function
The display bgp evpn all routing-table dampening parameter command displays configured BGP EVPN route dampening parameters.
Format
display bgp evpn all routing-table dampening parameter
display bgp instance instance-name evpn all routing-table dampening parameter
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Specifies a BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
To view BGP EVPN route dampening parameters, run the display bgp evpn all routing-table dampening parameter command.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table dampening parameter
EBGP:
Maximum Suppress Time(in second) : 3973
Ceiling Value : 16000
Reuse Value : 750
HalfLife Time(in second) : 900
Suppress-Limit : 2000
IBGP:
Maximum Suppress Time(in second) : 3973
Ceiling Value : 16000
Reuse Value : 750
HalfLife Time(in second) : 900
Suppress-Limit : 2000
<HUAWEI> display bgp instance aaa evpn all routing-table dampening parameter
EBGP:
Maximum Suppress Time(in second) : 3973
Ceiling Value : 16000
Reuse Value : 750
HalfLife Time(in second) : 900
Suppress-Limit : 2000
IBGP:
Maximum Suppress Time(in second) : 3973
Ceiling Value : 16000
Reuse Value : 750
HalfLife Time(in second) : 900
Suppress-Limit : 2000
Item | Description |
---|---|
Maximum Suppress Time(in second) | Maximum route suppression time, in seconds. |
Ceiling Value | Penalty ceiling. |
Reuse Value | Threshold for the routes to be unsuppressed. |
HalfLife Time(in second) | Half life of a reachable route, in seconds. |
Suppress-Limit | Threshold for the routes to be suppressed. |
EBGP | EBGP route dampening parameters. |
IBGP | IBGP route dampening parameters. |
display bgp evpn all routing-table statistics
Function
The display bgp evpn all routing-table statistics command displays statistics information about all of BGP EVPN routes.
Format
display bgp evpn all routing-table statistics
display bgp [ instance instance-name ] evpn all routing-table statistics
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Displays statistics information about EVPN routes of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
To check statistics information about BGP EVPN routes of all instances for maintenance, run the display bgp evpn all routing-table statistics command.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table statistics
Total number of routes from all PE: 2
Number of A-D Routes: 2
Number of Mac Routes: 0
Number of Inclusive Multicast Routes: 0
Number of ES Routes: 0
Number of Ip Prefix Routes: 0
Number of ARP Routes: 0
Item | Description |
---|---|
Total number of routes from all PE | Number of EVPN routes received from all PEs. |
Number of A-D Routes | Number of Ethernet auto-discovery routes. |
Number of Mac Routes | Number of MAC advertisement routes. |
Number of Inclusive Multicast Routes | Number of inclusive multicast routes. |
Number of ES Routes | Number of Ethernet segment routes. |
Number of Ip Prefix Routes | Number of IP prefix routes. |
Number of ARP Routes | Number of arp routes. |
display bgp evpn group
Format
display bgp evpn group [ group-name ]
display bgp [ instance instance-name ] evpn group [ group-name ]
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. |
instance instance-name |
Displays information about EVPN peer group of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Configuring BGP EVPN peer groups simplifies BGP EVPN network configuration and improves route advertisement efficiency.
The display bgp evpn group command displays BGP EVPN peer group information, including peers in the peer group and configuration information about the BGP EVPN peer group. The display bgp evpn group command is used in the following scenarios:- Verify the configuration after a peer group is configured using the group command.
- Verify the configuration after a peer is added to a peer group using the peer group command.
- Verify the configuration after a peer is deleted from a peer group using the undo peer group command.
- Verify the configuration after modifying the configuration of a peer group.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn group
Group in BGP-EVPN:
BGP peer-group: gp1
Remote AS: 100
Authentication type configured: None
Type : internal
PeerSession Members:
10.2.2.9
Peer Members:
10.2.2.9
Item | Description |
---|---|
BGP peer-group | Name of a BGP peer group. |
Remote AS | Number of the AS where a peer group resides. |
Authentication type configured | BGP authentication type:
|
Type | Type of a peer group:
|
PeerSession Members | BGP peers with which sessions have been established. |
Peer Members | Peer information. |
display bgp evpn peer
Function
The display bgp evpn slow-peer command displays information about slow BGP EVPN peers.
The display bgp evpn peer command displays information about BGP EVPN peers.
Format
display bgp [ instance instance-name ] evpn peer
display bgp [ instance instance-name ] evpn slow-peer
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Displays the information about BGP EVPN peers of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters without spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
To check the following information about BGP EVPN peers, run the display bgp evpn peer command:
- Status of connections between BGP EVPN peers
- Configuration information about BGP EVPN peers
- Whether BGP EVPN peers are successfully configured using the peer enable command
- Whether BGP EVPN peers are successfully deleted using the undo peer enable command To check information about slow BGP EVPN peers, run the display bgp evpn slow-peer command. The information includes the time when a peer began to be identified as a slow peer, the time when a peer last exited from the slow peer state, the number of times a peer has been identified as a slow peer, and the remaining time for a peer to exit from the slow peer state.
Precautions
When dynamic BGP EVPN peer relationships are being established or disconnected, statistics about the BGP EVPN peers may be inconsistent with the actual number of BGP EVPN peers. Therefore, you are advised to query statistics after the BGP EVPN peer status is stable.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn slow-peer
Total number of peers : 2
Switchback detection timer: Remaining 3581 Second(s)
Peer LastSlowEndTime SlowStartTime SlowCount
10.1.1.1 2016-04-10 20:41:33+00:00 2016-04-12 00:02:33+00:00 3
10.2.2.1 2016-04-11 23:02:40+00:00 2016-04-12 00:02:40+00:00 5
<HUAWEI> display bgp evpn peer
BGP local router ID : 10.3.3.3
Local AS number : 100
Total number of peers : 3
Peers in established state : 3
Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
10.1.1.1 4 100 4456 3196 0 0045h29m Established 5
10.2.2.2 4 100 4447 3202 0 0045h29m Established 5
10.4.4.4 4 100 4452 3206 0 0045h29m Established 4
Item | Description |
---|---|
Total number of peers | Number of peers. |
Switchback detection timer | Remaining time for a peer to exit from the slow peer state. |
Peer | Peer IP address. |
LastSlowEndTime | Time when a peer last exited from the slow peer state. |
SlowStartTime | Time when a peer began to be identified as a slow peer. |
SlowCount | Number of times a peer has been identified as a slow peer. |
BGP local router ID | Local BGP EVPN router ID. |
Local AS number | Local AS number. |
AS | Autonomous system number. |
Peers in established state | Number of peers in the Established state. |
V | BGP version. |
MsgRcvd | BGP version of a peer. |
MsgSent | Number of messages sent. |
OutQ | Number of messages waiting to be sent to a specified peer. |
Up/Down | Duration of the BGP session staying in the current state.
|
State | Current BGP EVPN status:
After BGP EVPN receives a start event, BGP EVPN initiates a TCP connection to a peer, starts the ConnectRetry timer, and listens to the TCP messages from the peer. BGP EVPN then enters the Connect state.
If the TCP connection is successfully established, BGP EVPN stops the ConnectRetry timer and sends an Open message to the peer. BGP EVPN then enters the Opensent state. If the TCP connection fails to be established, BGP EVPN resets the ConnectRetry timer and listens to the TCP connection initiated by the peer. BGP EVPN then enters the Active state. If the ConnectRetry timer expires, BGP EVPN restarts the ConnectRetry timer and attempts to establish a TCP connection with the peer again. At this time, BGP EVPN remains in the Connect state.
If the TCP connection is successfully established, BGP EVPN resets the ConnectRetry timer and sends an Open message to the peer. BGP EVPN then enters the Opensent state. If the ConnectRetry timer expires, BGP EVPN restarts the ConnectRetry timer and enters the Connect state. If BGP EVPN attempts to establish a TCP connection with an unknown IP address but fails, BGP EVPN resets the ConnectRetry timer and remains in the Active state.
If BGP EVPN receives a correct Open message, BGP EVPN enters the OpenConfirm state. If BGP EVPN receives an incorrect Open message, BGP EVPN sends a Notification message to the peer and enters the Idle state. If BGP EVPN receives a TCP connection teardown message, BGP EVPN resets the ConnectRetry timer and listens to the TCP connection initiated by the peer. BGP EVPN then enters the Active state.
If BGP EVPN receives a Notification or TCP connection teardown message, BGP EVPN enters the Idle state. If BGP EVPN receives a Keepalive message, BGP EVPN enters the Established state.
If BGP EVPN receives an Update or Keepalive message, BGP EVPN remains in the Established state. If BGP EVPN receives a Notification message, BGP EVPN enters the Idle state.
|
PrefRcv | Number of route prefixes sent from the peer. |
display bgp evpn peer verbose
Function
The display bgp evpn peer verbose command displays detailed information about BGP EVPN peers.
Format
display bgp evpn peer [ ipv4-address ] verbose
display bgp [ instance instance-name ] evpn peer [ ipv4-address ] verbose
display bgp evpn peer ipv6-address verbose
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Displays the information about BGP EVPN peers of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
ipv6-address |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
ipv4-address |
Specifies the IPv4 address of a BGP EVPN peer. |
The value is in dotted decimal notation. |
Usage Guidelines
To check the following detailed information about BGP EVPN peers, run the display bgp evpn peer verbose command:
- Status of connections between BGP EVPN peers
- Configuration information about BGP EVPN peers
- Whether BGP EVPN peers are successfully configured using the peer enable command
- Whether BGP EVPN peers are successfully deleted using the undo peer enable command
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn peer 10.3.3.3 verbose
BGP Peer is 10.3.3.3, remote AS 100
Type: IBGP link
BGP version 4, Remote router ID 192.168.63.130
Update-group ID: 1
BGP current state: Established, Up for 06h58m12s
BGP current event: KATimerExpired
BGP last state: OpenConfirm
BGP Peer Up count: 1
Received total routes: 1
Received active routes total: 1
Advertised total routes: 1
Port: Local - 179 Remote - 65085
Configured: Connect-retry Time: 32 sec
Configured: Min Hold Time: 0 sec
Configured: Active Hold Time: 180 sec Keepalive Time:60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time:60 sec
Peer optional capabilities:
Peer supports bgp multi-protocol extension
Peer supports bgp route refresh capability
Peer supports bgp add-path capability
EVPN address-family: both
Negotiated bgp add-path capability
EVPN address-family: both
Peer supports bgp 4-byte-as capability
Address family IPv4 Unicast: advertised and received
Address family L2VPN EVPN: advertised and received
Received:
Total messages 486
Update messages 6
Open messages 1
KeepAlive messages 479
Notification messages 0
Refresh messages 0
Sent :
Total messages 486
Update messages 3
Open messages 1
KeepAlive messages 482
Notification messages 0
Refresh messages 0
Authentication type configured: None
Last keepalive received: 2018-06-13 16:34:10+00:00
Last keepalive sent : 2018-06-13 16:34:33+00:00
Last update received : 2018-06-13 09:36:49+00:00
Last update sent : 2018-06-13 09:36:27+00:00
No refresh received since peer has been configured
No refresh sent since peer has been configured
Minimum route advertisement interval is 15 seconds
Optional capabilities:
Route refresh capability has been enabled
4-byte-as capability has been enabled
Connect-interface has been configured
Peer Preferred Value: 0
Split group configured:
Peer limit state: true
Pipe limit percent: 10
Pipe limit count: 3
Pipe last limit time: 2020-11-21 08:48:36
Routing policy configured:
No routing policy is configured
Item | Description |
---|---|
BGP Peer is 10.3.3.3 | BGP peer address (10.3.3.3). |
BGP version | BGP version. |
BGP current state | Current state of BGP:
Upon receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry timer with the initial value, and waits for a TCP message from the remote BGP peer. BGP then enters the Connect state.
|
BGP current event | Current BGP event. |
BGP last state | State of last BGP stage, The possible states are Idle, Connect, Active, OpenSent, OpenConfirm, Established, and No neg. |
BGP Peer Up count | Number of times the BGP peer alternates between Up and Down. |
Peer optional capabilities | Optional capabilities of the peer. |
Peer Preferred Value | PrefVal of the peer. |
Peer limit state | Suppression status of the pipe for receiving packets from peers:
|
remote AS | AS number of the BGP peer. |
Remote router ID | Router ID of a peer. |
Update-group ID | ID of the Update group to which a peer belongs. |
Received total routes | Number of received route prefixes. |
Received active routes total | Number of active route prefixes received. |
Received : Active Hold Time | Hold time of the peer. |
Received | Number of packets received from a neighbor:
|
Advertised total routes | Number of route prefixes sent. |
Keepalive Time | Interval for sending Keepalive packets to the peer. |
Negotiated: Active Hold Time | Hold time negotiated by BGP peers. |
4-byte-as capability has been enabled | 4-byte-As is enabled. |
Sent | Number of packets sent to neighbors:
|
Authentication type configured | Authentication type. |
Last keepalive received | Last time when a Keepalive message is received. |
Last keepalive sent | Time when a Keepalive message was last sent. |
Last update received | Time when an Update message is last received. |
Last update sent | Last time when an Update message is sent. |
No refresh received since peer has been configured | No Route-Refresh messages are received from the peer after the peer relationship is established. |
No refresh sent since peer has been configured | No Route-Refresh messages are sent to the peer after the peer relationship is established. |
No routing policy is configured | No routing policy is configured. |
Minimum route advertisement interval is 15 seconds | Minimum interval at which routes are advertised:
|
Optional capabilities | Optional capabilities of the peer. |
Route refresh capability has been enabled | Route-refresh enabled. |
Connect-interface has been configured | Source interface used to send BGP messages. |
Split group configured | Whether a split horizon group is configured. |
Routing policy configured | Whether a routing policy has been configured. |
Pipe limit percent | Rate limit percentage of the pipe for receiving neighbor packets. |
Pipe limit count | Number of times rate limiting is performed on the pipe for receiving neighbor packets. |
Pipe last limit time | Last time when the rate of the pipe for receiving neighbor packets was limited. |
Type | BGP link type, which can only be IBGP link currently. |
Port | Port number.:
|
Configured | Locally configured timer:
|
display bgp evpn routing-table (peer)
Format
display bgp evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ] { inclusive-route | mac-route | prefix-route }
display bgp evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route }
display bgp evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ]
display bgp evpn all routing-table extcommunity { rt extcommunity } &<1-33>
display bgp evpn all routing-table extcommunity { rt extcommunity } &<1-33> match-any
display bgp evpn all routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33>
display bgp evpn all routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33> match-any
display bgp instance instance-name evpn all routing-table extcommunity { rt extcommunity } &<1-33>
display bgp instance instance-name evpn all routing-table extcommunity { rt extcommunity } &<1-33> match-any
display bgp instance instance-name evpn all routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33>
display bgp instance instance-name evpn all routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33> match-any
display bgp evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33>
display bgp evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33> match-any
display bgp instance instance-name evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33>
display bgp instance instance-name evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route } extcommunity { rt extcommunity } &<1-33> match-any
display bgp instance instance-name evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ] { inclusive-route | mac-route | prefix-route }
display bgp instance instance-name evpn { route-distinguisher route-distinguisher } routing-table { inclusive-route | mac-route | prefix-route }
display bgp instance instance-name evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ]
display bgp evpn all routing-table peer ipv6-address { advertised-routes | received-routes } { inclusive-route | mac-route | prefix-route }
display bgp evpn all routing-table peer ipv6-address { advertised-routes | received-routes }
Parameters
Parameter | Description | Value |
---|---|---|
peer ip-address |
Specifies a peer IP address. |
The value is in dotted decimal notation. |
advertised-routes |
Specifies the routes to be advertised to a specified peer. |
- |
received-routes |
Displays the routes received from the specified peer. |
- |
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix-route |
Displays information about prefix routes. |
- |
all |
Displays EVPN routes of all EVPN instances. |
- |
route-distinguisher route-distinguisher |
Displays information about BGP EVPN routes with a specified RD. |
An RD can be in any of the following formats:
|
extcommunity |
Displays the routes with the specified extended community attribute. |
- |
rt extcommunity |
Specifies the extended community attribute of the VPN-Target type. |
The options are as follows:
as-number specifies the AS number. The value is an integer that ranges from 0 to 65535. 4as-number is a 4-byte AS number, which can be:
ipv4-address is an IPv4 address in dotted decimal notation. nn is an integer. For as-number and 4as-number, the value ranges from 0 to 4294967295. For ipv4-address, the value ranges from 0 to 65535. |
match-any |
Displays information about the routes that match any of the specified extended community attributes. |
- |
instance instance-name |
Displays the routes of a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the string must be enclosed in double quotation marks (" "). |
ipv6-address |
Specifies the peer IPv6 address. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
Usage Guidelines
To check information about EVPN routes, including active and inactive routes, run the display bgp evpn routing-table command.
Information about specified EVPN routes can be displayed by specifying different parameters.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table peer 10.1.1.1 advertised-routes prefix-route
Local AS number : 100
BGP Local router ID is 10.2.2.2
Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
EVPN address family:
Number of Ip Prefix Routes: 1
Route Distinguisher: 1:1
Network(EthTagId/IpPrefix/IpPrefixLen) NextHop
*> 0:10.22.22.22:32 10.2.2.2
<HUAWEI> display bgp instance p1 evpn all routing-table Local AS number : 100 BGP Local router ID is 10.1.1.1 Status codes: * - valid, > - best, d - damped, x - best external, a - add path, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete EVPN address family: Number of A-D Routes: 1 Route Distinguisher: 1:1 Network(ESI/EthTagId) NextHop *> 0010.1010.1010.1010.1010:0 127.0.0.1 EVPN-Instance c1: Number of A-D Routes: 1 Network(ESI/EthTagId) NextHop *> 0010.1010.1010.1010.1010:0 127.0.0.1 EVPN address family: Number of Inclusive Multicast Routes: 1 Route Distinguisher: 1:1 Network(EthTagId/IpAddrLen/OriginalIp) NextHop *> 0:32:10.1.1.1 127.0.0.1 EVPN-Instance c1: Number of Inclusive Multicast Routes: 1 Network(EthTagId/IpAddrLen/OriginalIp) NextHop *> 0:32:10.1.1.1 127.0.0.1 EVPN address family: Number of ES Routes: 1 Route Distinguisher: 10.1.1.1:0 Network(ESI/IpAddrLen/OriginalIp) NextHop *> 0010.1010.1010.1010.1010:32:10.1.1.1 127.0.0.1 EVPN-Instance c1: Number of ES Routes: 1 Network(ESI/IpAddrLen/OriginalIp) NextHop *> 0010.1010.1010.1010.1010:32:10.1.1.1 127.0.0.1 <HUAWEI> display bgp instance p1 evpn all routing-table statistics Total number of routes from all PE: 6 Number of A-D Routes: 2 Number of Mac Routes: 0 Number of Inclusive Multicast Routes: 2 Number of ES Routes: 2 <HUAWEI> display bgp instance p1 evpn all routing-table es-route Local AS number : 100 BGP Local router ID is 10.1.1.1 Status codes: * - valid, > - best, d - damped, x - best external, a - add path, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete EVPN address family: Number of ES Routes: 3 Route Distinguisher: 10.1.1.1:0 Network(ESI/IpAddrLen/OriginalIp) NextHop *> 0010.1010.1010.1010.1010:32:10.1.1.1 127.0.0.1 Route Distinguisher: 10.2.2.2:0 Network(ESI/IpAddrLen/OriginalIp) NextHop *>i 0010.1010.1010.1010.1010:32:10.2.2.2 10.2.2.2 Route Distinguisher: 10.3.3.3:0 Network(ESI/IpAddrLen/OriginalIp) NextHop *>i 0010.1010.1010.1010.1010:32:10.3.3.3 10.3.3.3 EVPN-Instance c1: Number of ES Routes: 3 Network(ESI/IpAddrLen/OriginalIp) NextHop *> 0010.1010.1010.1010.1010:32:10.1.1.1 127.0.0.1 *> 0010.1010.1010.1010.1010:32:10.2.2.2 10.2.2.2 *> 0010.1010.1010.1010.1010:32:10.3.3.3 10.3.3.3 <HUAWEI> display bgp instance p1 evpn all routing-table ad-route Local AS number : 100 BGP Local router ID is 10.1.1.1 Status codes: * - valid, > - best, d - damped, x - best external, a - add path, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete EVPN address family: Number of A-D Routes: 6 Route Distinguisher: 1:1 Network(ESI/EthTagId) NextHop *> 0010.1010.1010.1010.1010:0 127.0.0.1 Route Distinguisher: 2:2 Network(ESI/EthTagId) NextHop *>i 0010.1010.1010.1010.1010:0 10.2.2.2 Route Distinguisher: 3:3 Network(ESI/EthTagId) NextHop *>i 0010.1010.1010.1010.1010:0 10.3.3.3 Route Distinguisher: 10.1.1.1:0 Network(ESI/EthTagId) NextHop *> 0010.1010.1010.1010.1010:4294967295 127.0.0.1 Route Distinguisher: 10.2.2.2:0 Network(ESI/EthTagId) NextHop *>i 0010.1010.1010.1010.1010:4294967295 10.2.2.2 Route Distinguisher: 10.3.3.3:0 Network(ESI/EthTagId) NextHop *>i 0010.1010.1010.1010.1010:4294967295 10.3.3.3 EVPN-Instance c1: Number of A-D Routes: 5 Network(ESI/EthTagId) NextHop *> 0010.1010.1010.1010.1010:0 127.0.0.1 * i 10.2.2.2 * i 10.3.3.3 *>i 0010.1010.1010.1010.1010:4294967295 10.2.2.2 * i 10.3.3.3
Item | Description |
---|---|
Local AS number | Local AS number. |
BGP Local router ID | Router ID of the local device. |
BGP routing table entry information of | Routing entry information. |
best | Optimal route. |
EVPN address family | EVPN address family. |
Number of A-D Routes | Number of A-D routes. |
Number of Inclusive Multicast Routes | Number of inclusive multicast routes. |
Number of ES Routes | Number of ES routes. |
Number of Mac Routes | Number of MAC routes. |
Number of Ip Prefix Routes | Number of IP prefix routes. |
Route Duration | Duration for route advertisement. |
Route Distinguisher | RD of a route. |
NextHop | Next hop information about routes. |
EVPN-Instance | EVPN instance name. |
Total routes of Route Distinguisher | Total number of EVPN routes with a specified RD. |
Total number of routes from all PE | Total number of routes. |
From | IP address of the device that sends the route. |
Original nexthop | Original next hop IP address. |
Qos information | Qos information. |
Ext-Community | BGP EVPN extended community attribute. |
origin | Origin attribute of a BGP route. |
valid | Valid route. |
local | Local route. |
pre | The priority of the route. |
Advertised to such 1 peers | Peers to which routes are advertised. |
Direct Out-interface | Directly connected interface. |
Effective nexthop | Actual next hop of the IP prefix route. |
Advertised nexthop | Next hop to which the IP prefix route is re-iterated after being sent. |
Sent path-id | ID of the transmit path. |
Label information (Received/Applied) | Label information (received label/advertised label). |
Tunnel Type | Tunnel type. |
Router's MAC | MAC address received from an EVPN peer. |
GW IP Address | Gateway IP address. |
MED | MED value of a route. |
Ethernet Tag ID | Configured VLAN ID. The current value is always 0. |
IP Prefix/Len | IP prefix address and its length. |
ESI | ID of an Ethernet link network segment. |
localpref | Local preference. |
Network | Network information of the route. |
display bgp evpn routing-table (prefix condition)
Format
display bgp evpn all routing-table { inclusive-route | mac-route | prefix-route } prefix { community-list | ext-community | large-community | cluster-list | advertised-peer | as-path }
display bgp [ instance instance-name ] evpn all routing-table { inclusive-route | mac-route | prefix-route } prefix { community-list | ext-community | large-community | cluster-list | advertised-peer | as-path }
Parameters
Parameter | Description | Value |
---|---|---|
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix-route |
Displays information about prefix routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
An EVPN route prefix has the following formats: IP prefix route. The value is in the format of L:X.X.X.X:M or L:[X:X::X:X]:M, where:
|
community-list |
Displays the community list of BGP EVPN routes. |
- |
ext-community |
Displays the extended community list of BGP EVPN routes. |
- |
large-community |
Displays the extended community attribute of BGP EVPN routes. |
- |
cluster-list |
Displays the cluster list of BGP EVPN routes. |
- |
advertised-peer |
Displays the advertised peer list of BGP EVPN routes. |
- |
as-path |
Displays the AS_Path attribute of BGP EVPN routes. |
- |
all |
Displays information about EVPN routes of all EVPN instances. |
- |
instance instance-name |
Displays information about EVPN routes of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the string must be enclosed in double quotation marks (" "). |
Usage Guidelines
To check information about EVPN routes, including active and inactive routes, run the display bgp evpn routing-table command.
Information about specified EVPN routes can be displayed by specifying different parameters.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table inclusive-route 0:32:10.5.5.5 large-community
Routes of Route Distinguisher(1:1):
BGP routing table entry information of 0:32:10.5.5.5:
Imported route.
From: ::
Large-Community: <1:1:1>
Item | Description |
---|---|
Routes of Route Distinguisher | Routing information for the specified RD. |
BGP routing table entry information of | Routing entry information. |
Imported route | The routes imported. |
From | IP address of the device that advertised routes. |
Large-Community | Specifies the extended community attribute of BGP EVPN routes. |
display bgp evpn routing-table dampened
Format
display bgp evpn { all | route-distinguisher route-distinguisher } routing-table statistics dampened
display bgp evpn { all | route-distinguisher route-distinguisher } routing-table [ mac-route | prefix-route ] dampened
display bgp instance instance-name evpn { all | route-distinguisher route-distinguisher } routing-table statistics dampened
display bgp instance instance-name evpn { all | route-distinguisher route-distinguisher } routing-table [ mac-route | prefix-route ] dampened
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays EVPN routes of all EVPN instances. |
- |
route-distinguisher route-distinguisher |
Displays information about EVPN routes with the specified RD. |
An RD can be in either of the following formats:
|
statistics |
Displays statistics about BGP EVPN routes. |
- |
mac-route |
Number of MAC advertisement routes. |
- |
prefix-route |
Displays information about IP prefix routes. |
- |
instance instance-name |
Displays information about EVPN routes of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
To view the information about BGP EVPN dampened routes, run the display bgp evpn all routing-table dampened command with specified parameters.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table dampened
BGP Local router ID is 10.1.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
EVPN address family:
Number of Ip Prefix Routes: 2
Route Distinguisher: 1:1
Network(EthTagId/IpPrefix/IpPrefixLen) From Reuse Path/Ogn
di 0:10.1.1.1:32 10.2.2.2 01:03:18 200?
di 0:2.1.1.1:32 10.2.2.2 01:03:18 200?
Item | Description |
---|---|
BGP Local router ID | Router ID of the local device. |
Status codes | Status code. |
Number of Ip Prefix Routes | Number of IP prefix routes. |
Route Distinguisher | RD of a route. |
From | IP address of the peer that receives the routes. |
Reuse | Reused value. |
Path/Ogn | AS_Path and Origin attributes. |
Network | Network information of the route. |
display bgp evpn routing-table flap-info
Function
The display bgp evpn routing-table flap-info command displays statistics about BGP EVPN route flapping.
Format
display bgp evpn { all | route-distinguisher route-distinguisher } routing-table flap-info [ mac-route | prefix-route ]
display bgp instance instance-name evpn { all | route-distinguisher route-distinguisher } routing-table flap-info [ mac-route | prefix-route ]
Parameters
Parameter | Description | Value |
---|---|---|
all |
Displays information about EVPN routes of all EVPN instances. |
- |
route-distinguisher route-distinguisher |
Displays information about EVPN routes with the specified RD. |
An RD can be in either of the following formats:
|
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix-route |
Displays information about prefix routes. |
- |
instance instance-name |
Displays information about EVPN routes of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
To view statistics about BGP EVPN route flapping, run the display bgp evpn all routing-table flap-info command.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table flap-info
BGP Local router ID is 10.1.1.1
Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V - valid, I - invalid, N - not-found
EVPN address family:
Number of Mac Routes: 2
Route Distinguisher: 1:1
Network(EthTagId/MacAddrLen/MacAddr/IpAddrLen/IpAddr) From Flaps Duration Reuse Path/Ogn
di 0:48:0002-0002-0002:0:0.0.0.0 10.2.2.2 4 00:10:22 00:28:40 600i
di 0:48:38ba-a703-7902:0:0.0.0.0 10.2.2.2 4 00:10:10 00:28:46 600i
Item | Description |
---|---|
BGP Local router ID | Router ID of the local BGP device. |
Number of Mac Routes | Number of MAC Routes. |
Route Distinguisher | The route distinguisher. |
From | IP address of the peer from which a route is learned. |
Flaps | Total number of times of route flapping. |
Duration | Flapping duration. |
Reuse | Reuse value. |
Path/Ogn | AS_Path number and the Origin attribute. |
Network | The network information of the route. |
display bgp evpn routing-table(prefix)
Format
display bgp evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ] { inclusive-route | mac-route | prefix-route } prefix
display bgp evpn route-distinguisher route-distinguisher routing-table { inclusive-route | mac-route | prefix-route } prefix
display bgp [ instance instance-name ] evpn all routing-table [ peer ip-address { advertised-routes | received-routes } ] { inclusive-route | mac-route | prefix-route } prefix
display bgp [ instance instance-name ] evpn route-distinguisher route-distinguisher routing-table { inclusive-route | mac-route | prefix-route } prefix
display bgp evpn all routing-table peer ipv6-address { advertised-routes | received-routes } { inclusive-route | mac-route | prefix-route } prefix
Parameters
Parameter | Description | Value |
---|---|---|
peer |
Specifies the EVPN peer. |
- |
ip-address |
Specifies a peer IPv4 address. |
The value is in dotted decimal notation. |
advertised-routes |
Displays the routes advertised to the peer. |
- |
received-routes |
Displays the routes received by the peer. |
- |
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix-route |
Displays information about prefix routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
An EVPN route prefix has the following formats: Inclusive multicast route. The value is in the format of M:L:X.X.X.X, where:
MAC advertisement route. The value is in the format of E:M:H-H-H:L:X.X.X.X or E:M:H-H-H:L: [X:X::X:X], where:
IP prefix route. The value is in the format of L:X.X.X.X:M or L:[X:X::X:X]:M, where:
|
all |
Displays information about EVPN routes of all EVPN instances. |
- |
route-distinguisher route-distinguisher |
Displays information about EVPN routes with the specified RD. |
An RD can be in any of the following formats:
|
instance instance-name |
Displays information about EVPN routes of a specified BGP instance. |
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the string must be enclosed in double quotation marks (" "). |
ipv6-address |
Specifies a peer IPv6 address. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn all routing-table ad-route 0000.1111.2222.3333.4444:0 BGP local router ID : 172.16.1.1 Local AS number : 100 Total routes of Route Distinguisher(3:3): 1 BGP routing table entry information of 0000.1111.2222.3333.4444:0: Label information (Received/Applied): 48066/NULL From: 10.1.1.1 (10.1.1.1) Route Duration: 0d01h15m42s Relay IP Nexthop: 192.168.1.1 Relay IP Out-Interface: 10GE1/0/1 Relay Tunnel Out-Interface: 10GE1/0/1 Original nexthop: 10.1.1.1 Qos information : 0x0 Ext-Community: RT <1 : 1>, RT <3 : 3>, SoO <2.2.2.1 : 0> AS-path Nil, origin incomplete, localpref 100, pref-val 0, valid, internal, best, select, pre 255, IGP cost 1 Route Type: 1 (Ethernet Auto-Discovery (A-D) route) ESI: 0000.1111.2222.3333.4444, Ethernet Tag ID: 0 Not advertised to any peer yet EVPN-Instance evpnb: Number of A-D Routes: 1 BGP routing table entry information of 0000.1111.2222.3333.4444:0: Route Distinguisher: 3:3 Remote-Cross route Label information (Received/Applied): 48066/NULL From: 10.1.1.1 (10.1.1.1) Route Duration: 0d01h15m43s Relay Tunnel Out-Interface: 10GE1/0/1 Original nexthop: 10.1.1.1 Qos information : 0x0 Ext-Community: RT <1 : 1>, RT <3 : 3>, SoO <10.1.1.1 : 0> AS-path Nil, origin incomplete, localpref 100, pref-val 0, valid, internal, best, select, pre 255, IGP cost 1 Route Type: 1 (Ethernet Auto-Discovery (A-D) route) ESI: 0000.1111.2222.3333.4444, Ethernet Tag ID: 0 Not advertised to any peer yet
<HUAWEI> display bgp evpn all routing-table es-route 0000.1111.2222.3333.4444
BGP local router ID : 2.2.2.1
Local AS number : 100
Total routes of Route Distinguisher(2.2.2.1:0): 1
BGP routing table entry information of 0000.1111.2222.3333.4444:32:2.2.2.1:
From: 0.0.0.0 (0.0.0.0)
Route Duration: 1d02h09m05s
Direct Out-interface: NULL0
Original nexthop: 127.0.0.1
Qos information : 0x0
Ext-Community: SoO <2.2.2.1 : 0>, RT <0011-1122-2233>, DF Election <0 : 0 : 0>
AS-path Nil, origin incomplete, pref-val 0, valid, local, best, select, pre 255
Route Type: 4 (Ethernet Segment Route)
ESI: 0000.1111.2222.3333.4444, Originating IP:2.2.2.1/32
Advertised to such 1 peers:
1.1.1.1
EVPN-Instance evpnb:
Number of ES Routes: 1
BGP routing table entry information of 0000.1111.2222.3333.4444:32:2.2.2.1:
Route Distinguisher: 2.2.2.1:0
Local-Cross route
Route Duration: 1d02h09m06s
Relay IP Nexthop: 0.0.0.0
Relay IP Out-Interface: NULL0
Original nexthop: 127.0.0.1
Qos information : 0x0
Ext-Community: SoO <2.2.2.1 : 0>, RT <0011-1122-2233>, DF Election <0 : 0 : 0>
AS-path Nil, origin incomplete, pref-val 0, valid, local, best, select, pre 255
Route Type: 4 (Ethernet Segment Route)
ESI: 0000.1111.2222.3333.4444, Originating IP:2.2.2.1/32
Not advertised to any peer yet
<HUAWEI> display bgp evpn all routing-table inclusive-route 0:32:1.1.1.1
BGP local router ID : 1.1.1.1
Local AS number : 100
Total routes of Route Distinguisher(3:3): 1
BGP routing table entry information of 0:32:1.1.1.1:
From: 0.0.0.0 (0.0.0.0)
Route Duration: 0d00h00m10s
Direct Out-interface: NULL0
Original nexthop: 127.0.0.1
Qos information : 0x0
Ext-Community: RT <1 : 1>, RT <3 : 3>, SoO <1.1.1.1 : 0>
AS-path Nil, origin incomplete, pref-val 0, valid, local, best, select, pre 255
PMSI: Flags 0, Ingress Replication, Label 0:0:0(0), Tunnel Identifier:1.1.1.1
Route Type: 3 (Inclusive Multicast Route)
Ethernet Tag ID: 0, Originator IP:1.1.1.1/32
Advertised to such 1 peers:
2.2.2.1
EVPN-Instance evpnb:
Number of Inclusive Multicast Routes: 1
BGP routing table entry information of 0:32:1.1.1.1:
Route Distinguisher: 3:3
From: 0.0.0.0 (0.0.0.0)
Route Duration: 1d02h03m11s
Relay IP Nexthop: 0.0.0.0
Relay IP Out-Interface: NULL0
Original nexthop: 127.0.0.1
Qos information : 0x0
AS-path Nil, origin incomplete, pref-val 0, valid, local, best, select, pre 255
PMSI: Flags 0, Ingress Replication, Label 0:0:0(0), Tunnel Identifier:1.1.1.1
Route Type: 3 (Inclusive Multicast Route)
Ethernet Tag ID: 0, Originator IP:1.1.1.1/32
Not advertised to any peer yet
<HUAWEI> display bgp evpn all routing-table
Local AS number : 100
BGP Local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
EVPN address family:
Number of A-D Routes: 1
Route Distinguisher: 1:1
Network(ESI/EthTagId) NextHop
*> 0010.1010.1010.1010.1010:0 127.0.0.1
EVPN-Instance c1:
Number of A-D Routes: 1
Network(ESI/EthTagId) NextHop
*> 0010.1010.1010.1010.1010:0 127.0.0.1
EVPN address family:
Number of Inclusive Multicast Routes: 1
Route Distinguisher: 1:1
Network(EthTagId/IpAddrLen/OriginalIp) NextHop
*> 0:32:1.1.1.1 127.0.0.1
EVPN-Instance c1:
Number of Inclusive Multicast Routes: 1
Network(EthTagId/IpAddrLen/OriginalIp) NextHop
*> 0:32:1.1.1.1 127.0.0.1
EVPN address family:
Number of ES Routes: 1
Route Distinguisher: 1.1.1.1:0
Network(ESI/IpAddrLen/OriginalIp) NextHop
*> 0010.1010.1010.1010.1010:32:1.1.1.1 127.0.0.1
EVPN-Instance c1:
Number of ES Routes: 1
Network(ESI/IpAddrLen/OriginalIp) NextHop
*> 0010.1010.1010.1010.1010:32:1.1.1.1 127.0.0.1
<HUAWEI> display bgp evpn all routing-table prefix-route 0:10.1.1.0:24
BGP local router ID : 10.0.12.2
Local AS number : 100
Total routes of Route Distinguisher(1:1): 1
BGP routing table entry information of 0:10.1.1.0:24:
Label information (Received/Applied): 1/NULL
From: 0.0.0.0 (0.0.0.0)
Route Duration: 0d00h15m16s
Direct Out-interface: LoopBack10
Original nexthop: 10.56.21.29
Effective nexthop: 192.168.1.1
Qos information : 0
Ext-Community: RT <1 : 1>, Tunnel Type <VxLan>, Router's MAC <00e0-fc12-3456>
AS-path Nil, origin igp, MED 0, pref-val 0, valid, local, best, select, pre 255
Received path-id: 0
Route Type: 5 (Ip Prefix Route)
Ethernet Tag ID: 0, IP Prefix/Len: 10.1.1.0/24, ESI: 0000.0000.0000.0000.0000, GW IP Address: 0.0.0.0
Advertised to such 1 peers:
10.1.1.1
Item | Description |
---|---|
BGP Local router ID | Router ID of the local device. |
BGP routing table entry information of | Routing entry information. |
local | Local route. |
Local AS number | Local AS number. |
Total routes of Route Distinguisher | Total number of EVPN routes with a specified RD. |
Route Distinguisher | RD of the EVPN routes. |
Route Duration | Duration for route advertisement. |
Route Type | EVPN route type:
|
Label information (Received/Applied) | Label information (received label/advertised label). |
Label 0:0:0(0) | MPLS label value. 0:0:0 is a fixed value and is not used currently. (0) indicates the label value of BUM traffic. |
Relay IP Nexthop | IP recursive next hop. |
Relay Tunnel Out-Interface | Outbound interface of the recursive tunnel. |
Tunnel Type | Tunnel type. |
Tunnel Identifier | Tunnel ID, which is the source address of the current node. |
Original nexthop | Original next hop IP address. |
Qos Information | QoS information. |
SoO | SoO extended community attribute. |
AS-path | AS_Path attribute (Nil indicates that the attribute value is null.). |
origin | Origin attribute of a BGP route. |
origin incomplete | Other attribute. |
pref-val | Preferred value. |
pre | The priority of the route. |
IGP cost | IGP cost. |
Ethernet Tag ID | Configured VLAN ID. The current value is always 0. |
Not advertised to any peer yet | Route that is not advertised to any EVPN peer. |
EVPN-Instance | EVPN instance name. |
Number of A-D Routes | Number of Ethernet auto-discovery routes. |
Number of Inclusive Multicast Routes | Number of inclusive multicast routes. |
Number of ES Routes | Number of Ethernet segment routes. |
Remote-Cross route | Route received from a peer and leaked into an EVPN instance. |
best | Optimal route. |
EVPN address family | EVPN address family. |
NextHop | Next hop address. |
MED | MED value of route. |
GW IP Address | Gateway IP address. |
Direct Out-interface | Directly connected interface. |
DF Election | Extended community attribute of DF election. |
Originating IP | IP address of the device that has originated routes. |
Advertised to such 1 peers | Peers to which routes are advertised. |
Local-Cross route | Locally leaked routes. |
Flags 0 | Whether the current node is a leaf node. Currently, the value can only be 0. |
Ingress Replication | BUM traffic is forwarded in ingress replication mode. |
Originator | IP address of the device that has originated routes. |
Effective nexthop | Actual next hop of the IP prefix route. |
Router's MAC | MAC address received from an EVPN peer. |
Received path-id | ID of the receive path. |
Network | Reachable address. |
ESI | ID of an Ethernet link network segment. |
EthTagId | VLAN ID. |
IpAddrLen | Mask length. |
OriginalIp | Source IP address. |
From | IP address of the device that sends the route. |
Ext-Community | BGP EVPN extended community attribute. |
valid | Valid route. |
select | Local AS number. |
PMSI | Provider Multicast Service Interface (PMSI) tunnel information. |
display bgp evpn update-peer-group
Function
The display bgp evpn update-peer-group command displays information about update peer-groups of BGP EVPN routes.
Format
display bgp evpn update-peer-group [ index update-group-index ]
display bgp [ instance instance-name ] evpn update-peer-group [ index update-group-index ]
Parameters
Parameter | Description | Value |
---|---|---|
index update-group-index |
Specifies the index of an update peer-group. |
The value is an integer ranging from 0 to 65535. |
instance instance-name |
Specifies the name of a BGP instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
This command is used to view information about the update peer-group in the BGP-EVPN address family.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn update-peer-group
The EVPN instance's update peer group number : 1
Keep buffer update peer group number : 0
BGP Version : 4
Group ID : 1
Group Type : internal
Addr Family : EVPN AdvMinTimeVal : 0
Total Peers : 1
Leader Peer : 10.44.44.88
Item | Description |
---|---|
The EVPN instance's update peer group number | Number of update peer-groups in the EVPN instance. |
Keep buffer update peer group number | Number of update peer-groups stored in the buffer. |
BGP Version | BGP version. |
Group ID | ID of an update peer-group. |
Group Type | Type of an update peer-group:
|
Addr Family | Address family. |
AdvMinTimeVal | Minimum interval at which Update messages with the same route prefix are sent. |
Total Peers | Total number of peers in an update peer-group. |
Leader Peer | Representative of an update peer-group. |
display bgp evpn vpn-instance routing-table
Function
The display bgp evpn vpn-instance routing-table command displays information about BGP-EVPN routes.
Format
display bgp evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route }
display bgp evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } extcommunity { rt strExtCommunity } &<1-33>
display bgp evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } extcommunity { rt strExtCommunity } &<1-33> match-any
display bgp instance bgpName evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } extcommunity { rt strExtCommunity } &<1-33>
display bgp instance bgpName evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } extcommunity { rt strExtCommunity } &<1-33> match-any
display bgp instance bgpName evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route }
Parameters
Parameter | Description | Value |
---|---|---|
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
vpn-instance evpn-name-value |
Displays information about EVPN routes of a specified EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters without spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
extcommunity |
Displays the routes with the specified extended community attribute. |
- |
rt strExtCommunity |
Specifies the extended community attribute of the VPN-Target type. |
The options are as follows:
as-number specifies the AS number. The value is an integer that ranges from 0 to 65535. 4as-number is a 4-byte AS number, which can be:
ipv4-address is an IPv4 address in dotted decimal notation. nn is an integer. For as-number and 4as-number, the value ranges from 0 to 4294967295. For ipv4-address, the value ranges from 0 to 65535. |
match-any |
Displays information about the routes that match any of the specified extended community attributes. |
- |
instance bgpName |
Displays the routes of a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters without spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
To check information about all active and inactive BGP-EVPN routes, run the display bgp mvpn routing-table command. You can specify different parameters to check specific routing information.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn vpn-instance e1 routing-table mac-route extcommunity rt 1:1
BGP Local router ID is 10.1.1.1
Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
EVPN-Instance e1:
Number of Mac Routes: 1
Network(EthTagId/MacAddrLen/MacAddr/IpAddrLen/IpAddr) NextHop Extcommunity
*>i 0:48:00e0-fc12-3456:0:0.0.0.0 2001:DB8:1::144 RT <1 : 1>, SoO <10.1.1.144 : 0>, Mac Mobility <flag:1 seq:0 res:0>
Item | Description |
---|---|
BGP Local router ID | Router ID of the local device. |
EVPN-Instance | EVPN instance name. |
Number of Mac Routes | Number of MAC routes. |
Mac Mobility | Extended community attribute for MAC address migration. |
NextHop | Next hop information about routes. |
Extcommunity | Extended community attribute. |
SoO | SoO extended community attribute. |
Network | Network information of the route. |
EthTagId | VLAN ID. |
MacAddrLen | MAC address length. |
MacAddr | MAC address. |
IpAddrLen | Length of the IP address mask. |
IpAddr | IPv4 address. |
display bgp evpn vpn-instance routing-table (prefix)
Function
The display bgp evpn vpn-instance routing-table command displays information about BGP-EVPN routes.
Format
display bgp evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } prefix { community-list | ext-community | large-community | cluster-list }
display bgp [ instance bgpName ] evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } prefix { community-list | ext-community | large-community | cluster-list }
Parameters
Parameter | Description | Value |
---|---|---|
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
An EVPN route prefix has the following formats: Ethernet auto-discovery route. The value is in the format of xxxx.xxxx.xxxx.xxxx.xxxx:M, where:
Ethernet segment route. The value is in the format of xxxx.xxxx.xxxx.xxxx.xxxx, xxxx.xxxx.xxxx.xxxx.xxxx:M:X.X.X.X.X, or xxxx.xxxx.xxxx.xxxx.xxxx:M:[X:X::X:X], where x is a hexadecimal integer ranging from 0 to F. The value equals the ESI configured for the device originating this route.
Inclusive multicast route. The value is in the format of M:L:X.X.X.X, where:
MAC advertisement route. The value is in the format of E:M:H-H-H:L:X.X.X.X or E:M:H-H-H:L: [X:X::X:X], where:
IP prefix route. The value is in the format of L:X.X.X.X:M or L:[X:X::X:X]:M, where:
|
community-list |
Displays the community list of BGP EVPN routes. |
- |
ext-community |
Displays the extended community list of BGP EVPN routes. |
- |
large-community |
Displays the extended community attribute of BGP EVPN routes. |
- |
cluster-list |
Displays the cluster list of EVN BGP routes. |
- |
vpn-instance evpn-name-value |
Displays information about EVPN routes of a specified EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
instance bgpName |
Displays the routes of a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
To check information about all active and inactive BGP-EVPN routes, run the display bgp mvpn routing-table command. You can specify different parameters to check specific routing information.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn vpn-instance e1 routing-table mac-route 0:48:00e0-fc12-3456:0:0.0.0.0 ext-community
Routes of evpn-instance e1:
BGP routing table entry information of 0:48:00e0-fc12-3456:0:0.0.0.0:
From: 2001:DB8:1::141
Remote-Cross route
Ext-Community: RT <1 : 1>, SoO <10.1.1.144 : 0>, Mac Mobility <flag:1 seq:0 res:0>
Item | Description |
---|---|
evpn-instance | EVPN instance name. |
BGP routing table entry information of | Routing entry information. |
Remote-Cross route | Route received from a peer and leaked into an EVPN instance. |
SoO | SoO extended community attribute. |
Mac Mobility | Extended community attribute for MAC address migration. |
From | IP address of the device that sends the route. |
Local-Cross route | Locally leaked routes. |
Ext-Community | BGP EVPN extended community attribute. |
display bgp evpn vpn-instance routing-table (verbose)
Function
The display bgp evpn vpn-instance routing-table command displays information about BGP-EVPN routes.
Format
display bgp evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } prefix
display bgp [ instance bgpName ] evpn vpn-instance evpn-name-value routing-table { inclusive-route | mac-route } prefix
Parameters
Parameter | Description | Value |
---|---|---|
inclusive-route |
Displays information about inclusive multicast routes. |
- |
mac-route |
Displays information about MAC advertisement routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
An EVPN route prefix has the following formats: Inclusive multicast route. The value is in the format of M:L:X.X.X.X, where:
MAC advertisement route. The value is in the format of E:M:H-H-H:L:X.X.X.X or E:M:H-H-H:L: [X:X::X:X], where:
IP prefix route. The value is in the format of L:X.X.X.X:M or L:[X:X::X:X]:M, where:
|
vpn-instance evpn-name-value |
Displays information about EVPN routes of a specified EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters without spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
instance bgpName |
Displays the routes of a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters without spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
You can specify different parameters in this command to view information about routes as required.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display bgp evpn vpn-instance e1 routing-table mac-route 0:48:00e0-fc12-3456:0:0.0.0.0 BGP local router ID : 10.1.1.43 Local AS number : 100 EVPN-Instance e1: Number of Mac Routes: 1 BGP routing table entry information of 0:48:00e0-fc12-3456:0:0.0.0.0: Route Distinguisher: 1:1 Remote-Cross route Label information (Received/Applied): 3/NULL From: 2001:db8:1::1 (10.1.1.141) Route Duration: 0d00h03m39s Relay IP Nexthop: FE80::AA49:4DFF:FE84:32F6 Relay IP Out-Interface: 10GE1/0/1 Relay Tunnel Out-Interface: Original nexthop: 2001:DB8:1::2 Qos information : 0x0 Ext-Community: RT <1 : 1>, SoO <10.1.1.144 : 0>, Mac Mobility <flag:1 seq:0 res:0> Prefix-sid: 2001:DB8:2::1 AS-path Nil, origin igp, localpref 100, pref-val 0, valid, internal, best, select, pre 255, IGP cost 20 Originator: 10.1.1.144 Cluster list: 10.1.1.141 Route Type: 2 (MAC Advertisement Route) Ethernet Tag ID: 0, MAC Address/Len: 00e0-fc12-3456/48, IP Address/Len: 0.0.0.0/0, ESI:0000.0144.0144.0144.0144 Not advertised to any peer yet
Item | Description |
---|---|
BGP local router ID | Router ID of the local device. |
BGP routing table entry information of | Routing entry information. |
local | Local route. |
Local AS number | Local AS number. |
EVPN-Instance | EVPN instance name. |
Number of Mac Routes | Number of MAC advertisement routes. |
Mac Mobility | Extended community attribute for MAC address migration. |
Route Distinguisher | RD of the EVPN routes. |
Route Duration | Duration for route advertisement. |
Route Type | EVPN route type:
|
Remote-Cross route | Route received from a peer and leaked into an EVPN instance. |
Label information (Received/Applied) | Label information (received label/advertised label). |
Relay IP Nexthop | IP recursive next hop. |
Relay Tunnel Out-Interface | Outbound interface of the recursive tunnel. |
Relay IP Out-Interface | Outbound interface obtained during the recursion. |
IP Address/Len | IP address and length in a host route. |
Original nexthop | Original next hop IP address. |
Qos information | QoS information. |
SoO | SoO extended community attribute. |
AS-path | AS_Path attribute (Nil indicates that the attribute value is null.). |
origin | Origin attribute of a BGP route. |
pref-val | Preferred value. |
pre | The priority of the route. |
IGP cost | IGP cost. |
Cluster list | Cluster list. |
Ethernet Tag ID | Configured VLAN ID. The current value is always 0. |
MAC Address/Len | MAC address and length in a MAC route. |
Not advertised to any peer yet | Route that is not advertised to any EVPN peer. |
ESI | ID of an Ethernet link network segment. |
From | IP address of the device that sends the route. |
Ext-Community | BGP EVPN extended community attribute. |
valid | Valid route. |
best | Optimal route. |
select | Local AS number. |
Originator | IP address of the device that has originated routes. |
Community | Community attribute. |
Prefix-sid | Prefix SID. |
display evpn mac-duplication
Function
The display evpn mac-duplication command displays information about MAC duplication suppression in all EVPN instances.
The display evpn mac-duplication statistics command displays statistics about MAC duplication suppression of all EVIs.
Parameters
Parameter | Description | Value |
---|---|---|
statistics |
Enables the function to collect statistics about MAC address suppression of all EVPN instances. |
- |
Usage Guidelines
After configuring MAC duplication suppression, run the display evpn mac-duplication command to check information about MAC duplication suppression in all EVPN instances, including parameters related to MAC duplication suppression and information about suppressed MAC routes. You can run the display evpn mac-duplication statistics command to view statistics about MAC duplication suppression of all EVPN instances.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display evpn mac-duplication
Status codes: s - suppressed
VPN-Instance Name and ID : 1, 1
Detect loop-times : 3
Detect cycle(s) : 600
Retry cycle(s) : 540
Black Hole : Disabled
Mac-address BdTag/VlanId BdId MTimes SuppressTime LastSource
s 00e0-fc12-3456 0 1 3 2022-01-21 06:12:09 Eth-Trunk10.1
Status codes: s - suppressed
VPN-Instance Name and ID : 2, 2
Detect loop-times : 3
Detect cycle(s) : 600
Retry cycle(s) : 540
Black Hole : Disabled
<HUAWEI> display evpn mac-duplication statistics
Total number of suppressed mac-address : 8
----------------------------------------
EVPN-Instance Name Suppressed Number
----------------------------------------
1 3
3 1
4 1
5 2
6 1
Item | Description |
---|---|
Status codes | Status code. |
VPN-Instance Name and ID | EVPN instance name and ID. |
Detect loop-times | Threshold for the number of times a MAC route flaps. |
Detect cycle(s) | Detection period. |
Retry cycle(s) | Hold-off time to unsuppress MAC duplication. |
Black Hole | Whether blackhole MAC route is enabled. |
Mac-address | MAC address of the blackhole MAC route. |
BdTag/VlanId | BD ID or VLAN ID. |
BdId | BD ID. |
MTimes | Number of MAC duplication suppression times. |
SuppressTime | Date and time when MAC duplication was suppressed. |
LastSource | Source port. |
Total number of suppressed mac-address | Total number of MAC addresses suppressed in all EVPN instances. |
EVPN-Instance Name | Name of the EVPN instance. |
Suppressed Number | Number of times that suppression is performed. |
display evpn vpn-instance
Format
display evpn vpn-instance [ name vpn-instance-name ]
display evpn vpn-instance [ name vpn-instance-name ] verbose
Parameters
Parameter | Description | Value |
---|---|---|
name vpn-instance-name |
Specifies the name of an EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
verbose |
Displays detailed information. |
- |
Usage Guidelines
To check EVPN instance information, run the display evpn vpn-instance command.
If vpn-instance-name is not specified, the display evpn vpn-instance command displays a summary of all configured EVPN instances.Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display evpn vpn-instance name 1 verbose
VPN-Instance Name and ID : 1, 5120
Address family evpn
Route Distinguisher :
Label Policy : label per instance
Per-Instance Label : NULL(unicast),NULL(bum),NULL(bypass)
Item | Description |
---|---|
VPN-Instance Name and ID | Name and ID of the EVPN instance. The ID is allocated by the system for indexing. |
Address family evpn | EVPN instance address family. |
Route Distinguisher | EVPN instance RD. |
Label Policy | Label policy of the EVPN instance:
|
Per-Instance Label | Label shared by all private network routes in the EVPN instance. |
display evpn vpn-instance mac-duplication
Function
The display evpn vpn-instance mac-duplication command displays information about suppression on MAC route flapping.
Format
display evpn vpn-instance name vpn-instance-name mac-duplication [ bridge-domain bd-id ] [ mac-address mac-address ]
Parameters
Parameter | Description | Value |
---|---|---|
bridge-domain bd-id |
Displays a BD ID. |
The value is an integer ranging from 1 to 16777215. |
mac-address mac-address |
Displays a MAC address. |
The value is a 12-digit hexadecimal number, in the format of H-H-H. Each H is 4 digits. If an H contains fewer than 4 digits, the left-most digits are padded with zeros. For example, e0 is displayed as 00e0. |
name vpn-instance-name |
Displays the name of an EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. This value should be the same as BD ID. |
Usage Guidelines
To view information about MAC duplication suppression, run the display evpn vpn-instance mac-duplication command. The command output displays parameters related to MAC duplication suppression and information about the suppressed MAC routes.Note: For specifying specific MAC queries, BD needs to be specified for BD EVPN.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display evpn vpn-instance name evpna mac-duplication
Status codes: s - suppressed
VPN-Instance Name and ID : evpna, 5
Detect loop-times : 5
Detect cycle(s) : 180
Retry cycle(s) : 540
Black Hole : Disabled
Mac-address BdTag/VlanId BdId MTimes SuppressTime LastSource
s 00e0-fc55-01c9 0 100 3 2020-04-08 14:47:16 PW<peerip:1.1.1.1 vcid:100 vctype:vlan>
<HUAWEI> display evpn vpn-instance name 100 mac-duplication
Status codes: s - suppressed
VPN-Instance Name and ID : 100, 5
Detect loop-times : 5
Detect cycle(s) : 180
Retry cycle(s) : 540
Black Hole : Enabled
Mac-address BdTag/VlanId BdId MTimes SuppressTime LastSource
s 00e0-fc55-01c9 0 100 3 2020-04-08 14:47:16 2001:DB8::1
Item | Description |
---|---|
Status codes | Status code. |
VPN-Instance Name and ID | EVPN instance name and ID. |
Detect loop-times | Threshold for the number of times a MAC route flaps. |
Detect cycle(s) | Detection period. |
Retry cycle(s) | Hold-off time to unsuppress MAC duplication. |
Black Hole | Whether blackhole MAC route is enabled. |
Mac-address | MAC address of the blackhole MAC route. |
BdId | BD ID. |
MTimes | Number of MAC duplication suppression times. |
SuppressTime | Date and time when MAC duplication was suppressed. |
LastSource | Source port. |
BdTag | BD ID. |
peerip | Peer IP Address of PW. |
vcid | VC ID. |
vctype | Encapsulation type of a PW. |
display evpn vpn-instance mac-duplication history
Function
The display evpn vpn-instance mac-duplication history command displays historical records of MAC route flapping.
Parameters
Parameter | Description | Value |
---|---|---|
name evpnName |
Specifies the name of an EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
After MAC duplication suppression is configured, you can run the display evpn vpn-instance mac-duplication history command to view historical records about MAC duplication suppression, including parameters related to MAC duplication suppression and information about MAC duplication routes.
Example
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display evpn vpn-instance name bdevpn1 mac-duplication history
VPN-Instance Name and ID : bdevpn1, 3
Detect loop-times : 5
Detect cycle(s) : 300
Retry cycle(s) : 300
Black Hole : Disabled
Mac-address BdTag/VlanId BdId MTimes TimeStamp CurrentLearn LastLearn
00e0-fc12-3456 0 1 5 2022-08-23 12:18:41 Eth-Trunk1.1 2.2.2.2
Item | Description |
---|---|
VPN-Instance Name and ID | EVPN instance name and ID. |
Detect loop-times | Threshold for the number of times a MAC route flaps. |
Detect cycle(s) | Detection period. |
Retry cycle(s) | Hold-off time to unsuppress MAC duplication. |
Black Hole | Whether blackhole MAC route is enabled. |
Mac-address | MAC address that flaps. |
BdTag/VlanId | BD ID/VLAN ID. |
BdId | BD ID. |
MTimes | Number of MAC duplication suppression times. |
TimeStamp | Time when the last migration occurs. |
CurrentLearn | Location of the learned MAC address. |
LastLearn | Location of the MAC address that is learned last time. |
evpn
Function
The evpn command creates and displays the global EVPN configuration view. In this view, you can configure global EVPN parameters and run related commands.
The undo evpn command deletes the global EVPN configuration view.
By default, the global EVPN configuration view is not created.
evpn ( bd-evpn-instance view )
Function
The evpn command creates an EVPN instance for a VXLAN.
The undo evpn command deletes an EVPN instance of a VXLAN.
By default, no EVPN instance is created for VXLANs.
Usage Guidelines
Usage Scenario
The created EVPN instance can store EVPN routes sent from peer VTEPs.
Prerequisites
The following tasks have been performed:
- EVPN has been configured to serve as the VXLAN control plane using the evpn-overlay enable command.
- A VNI has been created using the vxlan vni command and associated with a broadcast domain (BD).
Configuration Impact
If you run undo evpn command to delete an EVPN instance, all configurations in the EVPN instance are deleted.
evpn-overlay enable
Function
The evpn-overlay enable command enables EVPN.
The undo evpn-overlay enable command disables EVPN.
By default, EVPN is disabled.
evpn-route-origin igp
Function
The evpn-route-origin igp command enables the origin-igp function for EVPN routes.
The undo evpn-route-origin igp command disables the origin-igp function for EVPN routes.
By default, the origin-igp function is enabled for EVPN routes, and the origin attribute carried by generated EVPN routes is igp.
Usage Guidelines
According to BGP, the origin attribute carried by a route indicates the origin of the route, which can be IGP, EGP, or incomplete. The command can be used to control whether the origin attribute carried by the routes (including Type 1, Type 2, Type 3, and Type 4 routes) generated by EVPN is igp or incomplete. By default, this function is enabled, that is, the origin attribute is igp.
After the upgrade, the undo evpn-route-origin igp command is added to keep the origin attribute of generated routes as imcomplete.export route-policy (EVPN instance view)
Function
The export route-policy command associates an EVPN instance with an export routing policy.
The undo export route-policy command disassociates an EVPN instance with an export routing policy.
By default, an EVPN instance is not associated with any export routing policy.
Parameters
Parameter | Description | Value |
---|---|---|
policy-name |
Specifies the name of a routing policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
By default, an EVPN instance adds all VPN targets in the export VPN target list to EVPN routes to be advertised to its peers. To control route export more precisely, run the export route-policy command to associate the EVPN instance with an export routing policy and set attributes for eligible routes.
Prerequisites
An RD has been configured for the EVPN instance using the route-distinguisher command.
If the export route-policy to be associated with a VPN instance IPv4 address family does not exist, configure the export route-policy first.Configuration Impact
If the command is run more than once, the latest configuration overrides the previous one.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] route-policy rp2 permit node 10 [HUAWEI-route-policy] apply community 10:1 [HUAWEI-route-policy] quit [HUAWEI] bridge-domain 100 [HUAWEI-bd100] vxlan vni 200 [HUAWEI-bd100] evpn [HUAWEI-bd100-evpn] route-distinguisher 100:1 [HUAWEI-bd100-evpn] export route-policy rp2
export route-policy evpn
Function
The export route-policy evpn command associates the VPN instance IPv4/IPv6 address family of a VPN instance with an export routing policy to filter routes to be advertised to the EVPN.
The undo export route-policy evpn command disassociates the VPN instance IPv4/IPv6 address family of a VPN instance with an export routing policy.
By default, the VPN instance IPv4/IPv6 address family of a VPN instance is not associated with any export routing policy.
Parameters
Parameter | Description | Value |
---|---|---|
policy-name |
Specifies the name of a routing policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
By default, the VPN IPv4/IPv6 address family of a VPN instance adds all VPN targets in the export VPN target list to routes to be advertised to the EVPN. To control route export more precisely, run the export route-policy evpn command to associate the VPN IPv4/IPv6 address family with an export routing policy and set attributes for eligible routes.
Prerequisites
An RD has been configured for the VPN instance IPv4/IPv6 address family using the route-distinguisher command.
Configuration Impact
The current VPN instance address family can be associated with only one import route-policy. If this command is run more than once, the latest configuration overrides the previous one.
The export route-policy command does not affect the export route-policy configured using the export route-policy command.Precautions
If the specified routing policy does not exist, run the route-policy command to create the routing policy.
Example
<HUAWEI> system-view [HUAWEI] route-policy policy-2 permit node 10 [HUAWEI-route-policy] quit [HUAWEI] ip vpn-instance vrf1 [HUAWEI-vpn-instance-vrf1] ipv4-family [HUAWEI-vpn-instance-vrf1-af-ipv4] route-distinguisher 100:1 [HUAWEI-vpn-instance-vrf1-af-ipv4] export route-policy policy-2 evpn
filter-policy
Function
The filter-policy command configures a device to filter received MAC routes. MAC duplication suppression is not performed for MAC addresses in the filter policy.
The undo filter-policy command disables a device from filtering received MAC routes.
By default, the advertised or received MAC routes are not filtered.
Format
filter-policy { acl-number | acl-name acl-name-value }
undo filter-policy { acl-number | acl-name acl-name-value }
Parameters
Parameter | Description | Value |
---|---|---|
acl-number |
Specifies the number of a basic ACL. |
The value is an integer in the range from 4000 to 4999. |
acl-name acl-name-value |
Specifies the name of a named basic ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value starts with a letter or digit but cannot contain only digits. The ACL type must be link. |
Usage Guidelines
Usage Scenario
The filter-policy command is used to configure a MAC address whitelist. MAC duplication is not suppressed for MAC addresses in the whitelist.
When configured filtering conditions are used for a named ACL, only the configurations specified by source and time-range take effect.Prerequisites
An ACL has been configured to set filtering rules.
Configuration Impact
If the filter-policy command is run more than once for the same EVPN instance, the latest configuration overrides the previous one.
import route-policy (EVPN instance view)
Function
The import route-policy command associates an EVPN instance with an import routing policy.
The undo import route-policy command disassociates an EVPN instance with an import routing policy.
By default, an EVPN instance is not associated with any import routing policy.
Parameters
Parameter | Description | Value |
---|---|---|
policy-name |
Specifies the name of a routing policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
By default, an EVPN instance matches the export VPN targets of received routes against its import VPN targets to determine whether to import these routes. To control route import more precisely, run the import route-policy command to associate the EVPN instance with an import routing policy and set attributes for eligible routes.
Prerequisites
An RD has been configured for the EVPN instance using the route-distinguisher command.
If the specified route-policy does not exist, run the route-policy command to create one.Configuration Impact
If the command is run more than once, the latest configuration overrides the previous one.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] route-policy rp1 permit node 10 [HUAWEI-route-policy] apply community 10:1 [HUAWEI-route-policy] quit [HUAWEI] bridge-domain 100 [HUAWEI-bd100] vxlan vni 200 [HUAWEI-bd100] evpn [HUAWEI-bd100-evpn] route-distinguisher 100:1 [HUAWEI-bd100-evpn] import route-policy rp1
import route-policy evpn
Function
The import route-policy evpn command associates the VPN instance IPv4/IPv6 address family of a VPN instance with an import routing policy to filter routes imported from the EVPN.
The undo import route-policy evpn command dissociates the VPN instance IPv4/IPv6 address family of a VPN instance with an import routing policy.
By default, the VPN instance IPv4/IPv6 address family of a VPN instance is not associated with any import routing policy.
Parameters
Parameter | Description | Value |
---|---|---|
policy-name |
Specifies the name of a routing policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
By default, the VPN instance IPv4/IPv6 address family of a VPN instance matches the export VPN targets of received routes against its import VPN targets to determine whether to import these routes. To control route import more precisely, run the import route-policy evpn command to associate the VPN IPv4/IPv6 address family with an import routing policy and set attributes for eligible routes.
Prerequisites
An RD has been configured for the VPN instance IPv4/IPv6 address family using the route-distinguisher command.
If the associated route-policy does not exist, run the route-policy command to configure the route-policy.Configuration Impact
The current VPN instance IPv4/IPv6 address family can be associated with only one import route-policy. If this command is run more than once, the latest configuration overrides the previous one.
The import route-policy command does not affect the import route-policy configured using the import route-policy command.Example
<HUAWEI> system-view [HUAWEI] route-policy policy-1 permit node 10 [HUAWEI-route-policy] quit [HUAWEI] ip vpn-instance vrf1 [HUAWEI-vpn-instance-vrf1] ipv4-family [HUAWEI-vpn-instance-vrf1-af-ipv4] route-distinguisher 100:1 [HUAWEI-vpn-instance-vrf1-af-ipv4] import route-policy policy-1 evpn
irb asymmetric (BGP-VPN instance IPv4 address family view)
Function
The irb asymmetric command enables the asymmetric mode for IRB routes.
The undo irb asymmetric command restores the default configuration.
By default, the asymmetric mode is disabled for IRB routes.
Format
irb asymmetric [ route-policy route-policy-name ]
undo irb asymmetric [ route-policy route-policy-name ]
Parameters
Parameter | Description | Value |
---|---|---|
route-policy route-policy-name |
Specifies the name of a route-policy. After this parameter is specified, the asymmetric IRB function takes effect only for the routes to which the route-policy applies. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
By default, a device generates an IP prefix route based on the IP address in an IRB route that it has received from a BGP EVPN peer. IP prefix routes can be used for Layer 3 traffic forwarding. If Layer 2 forwarding is required, run the irb asymmetric command to enable the asymmetric mode for IRB routes. Specifically, after this configuration is performed, the device does not generate IP prefix routes after receiving IRB routes.
irb asymmetric (BGP-VPN instance IPv6 address family view)
Function
The irb asymmetric command enables the asymmetric mode for IRBv6 routes.
The undo irb asymmetric command restores the default configuration.
By default, the asymmetric mode is disabled for IRBv6 routes.
Format
irb asymmetric [ route-policy route-policy-name ]
undo irb asymmetric [ route-policy route-policy-name ]
Parameters
Parameter | Description | Value |
---|---|---|
route-policy route-policy-name |
Specifies the name of a route-policy. After this parameter is specified, the asymmetric IRB function takes effect only for the routes to which the route-policy applies. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Views
BGP-VPN instance IPv6 address family view,BGP multi-instance VPN instance IPv6 address family view
Usage Guidelines
By default, a device generates an IP prefix route based on the IP address in an IRBv6 route that it has received from a BGP EVPN peer. IP prefix routes can be used for Layer 3 traffic forwarding. If Layer 2 forwarding is required, run the irb asymmetric command to enable the asymmetric mode for IRBv6 routes. Specifically, after this configuration is performed, the device does not generate IP prefix routes after receiving IRBv6 routes.
Example
<HUAWEI> system-view [HUAWEI] ip vpn-instance vpna [HUAWEI-vpn-instance-vpna] ipv6-family [HUAWEI-vpn-instance-vpna-af-ipv6] route-distinguisher 2:2 [HUAWEI-vpn-instance-vpna-af-ipv6] quit [HUAWEI-vpn-instance-vpna] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv6-family vpn-instance vpna [HUAWEI-bgp-6-vpna] irb asymmetric
l2vpn-family evpn
Function
The l2vpn-family evpn command enables the BGP-EVPN address family and displays the BGP-EVPN address family view.
The undo l2vpn-family evpn command deletes the BGP-EVPN address family view.
By default, the BGP-EVPN address family is disabled.
l2vpn-family evpn (bgp-instance-af-evpn-extend view)
Function
The l2vpn-family evpn command enables the BGP-EVPN address family and displays the BGP-EVPN address family view.
The undo l2vpn-family evpn command deletes the BGP-EVPN address family view.
By default, the BGP-EVPN address family is disabled.
l3-reoriginate different-split-group
Function
The l3-reoriginate different-split-group command enables the current device to advertise Layer 3 regenerated routes only to devices in different split horizon groups.
The undo l3-reoriginate different-split-group command restores the default configuration.
By default, re-originate L3 routes are advertised without being restricted by an SHG.
Usage Guidelines
Usage Scenario
In a scenario where Segment VXLAN is used to implement DC interconnection, if both route reflectors and route regenerating are configured on Border Leaf nodes, the Border Leaf nodes regenerate Layer 3 routes received from peers in the DC, Border Leaf nodes advertise regenerated Layer 3 routes to all BGP EVPN peers (including devices in the data center) and reflect routes to all clients. As a result, devices in the data center receive redundant regenerated routes. To prevent this problem, you can specify devices in the data center as a split horizon group and run the l3-reoriginate different-split-group command to enable the Border Leaf node to advertise regenerated routes only to devices in different split horizon groups. In this way, devices in the data center and Border Leaf nodes are in the same split horizon group. Therefore, the Border Leaf node does not advertise re-established routes to them but reflects routes.
Precautions
If no split horizon group is configured for a BGP EVPN peer, the BGP EVPN peer belongs to the default split horizon group. This command is still valid for the default split horizon group.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 split-group aa [HUAWEI-bgp-af-evpn] quit [HUAWEI-bgp] quit [HUAWEI] evpn [HUAWEI-evpn] l3-reoriginate different-split-group
local mac-only-route no-generate
Function
The local mac-only-route no-generate command disables the device from generating EVPN MAC routes when both MAC address entries and ARP/ND entries contain local MAC addresses.
The undo local mac-only-route no-generate command restores the default configuration.
By default, EVPN MAC routes are generated when both MAC address entries and ARP/ND entries contain local MAC addresses.
Usage Guidelines
If a MAC address entry and an ARP/ND entry on the local gateway both contain the local MAC address in EVPN scenarios, the gateway generates both an EVPN MAC/IP route and an EVPN MAC route by default. To optimize memory utilization, perform this step so that the gateway generates only a MAC/IP route. To ensure normal Layer 2 traffic forwarding, also run the mac-ip route generate-mac command on the peer gateway to enable the function to generate MAC address entries based on MAC/IP routes.
Example
<HUAWEI> system-view Enter system view, return user view with return command. [HUAWEI] bridge-domain 100 [HUAWEI-bd100] vxlan vni 100 [HUAWEI-bd100] evpn [HUAWEI-bd100-evpn] local mac-only-route no-generate
mac-duplication (EVPN instance view)
Function
The mac-duplication command displays the EVPN-MAC-duplication view.
By default, the EVPN-MAC-duplication view is not displayed.
Usage Guidelines
Usage Scenario
To modify the configuration of MAC duplication suppression, run the mac-duplication command to enter the EVPN-MAC-duplication view first. Then, run the detect loop-times command to modify the parameter settings of the function.
Precautions
To ensure that MAC duplication suppression works as expected, you are advised to run the mac-address learning disable command on NVE interfaces.
mac-duplication (Global EVPN configuration view)
Function
The mac-duplication command displays the EVPN-MAC-duplication view.
By default, the EVPN-MAC-duplication view is not displayed.
mac-ip route generate-mac
Function
The mac-ip route generate-mac command enables the function to generate MAC entries based on MAC/IP routes.
The undo mac-ip route generate-mac command disables the function.
By default, the function to generate MAC entries based on MAC/IP routes is not enabled.
Usage Guidelines
Usage Scenario
In EVPN VXLAN scenarios, if the remote gateway is configured not to advertise MAC routes (mac-route no-advertise) or is configured not to generate MAC routes (local mac-only-route no-generate), the local gateway cannot generate MAC entries by default. To guide Layer 2 traffic forwarding, run the mac-ip route generate-mac command on the local gateway to enable MAC address entry generation based on MAC/IP routes.
Precautions
After the mac-ip route generate-mac command is run, if the remote gateway advertises both MAC/IP routes and MAC routes, the local gateway generates MAC entries based on only MAC routes.
mac-route no-advertise
Function
The mac-route no-advertise command disables local MAC routes from being advertised.
The undo mac-route no-advertise command cancels the configuration.
By default, local MAC routes can be advertised.
Usage Guidelines
Usage Scenario
In VXLAN Layer 3 gateway scenarios where Layer 2 unicast traffic forwarding is not involved, to disable local MAC routes from being advertised, run the mac-route no-advertise command. This configuration prevents an EVPN peer gateway from receiving MAC routes, therefore saving memory resources.
Precautions
The mac-route no-advertise command disables MAC routes learned within BDs from being advertised based on VXLAN Network Identifiers (VNIs).
nexthop recursive-lookup default-route (BGP-EVPN address family view)
Function
By default, the function to send packets over a default route when the recursive next-hop IP address is unavailable is not enabled.
Usage Guidelines
Usage Scenario
In an EVPN over VXLAN scenario, a PE device at one end may fail to establish a VXLAN tunnel because the next hop of the Layer 3 prefix route is unreachable due to incorrect configurations or faults. As a result, services are interrupted. To prevent this problem, run the nexthop recursive-lookup default-route command on the PE and configure the remote PE to send a default route to the local PE. When the next hop of a specific route on the local PE is unreachable, the local PE can iterate the default route to establish a VXLAN tunnel for forwarding, ensuring normal service running.
nexthop recursive-lookup default-route (bgp-muli-instance-af-evpn view)
Function
By default, the function to send packets over a default route when the recursive next-hop IP address is unavailable is not enabled.
Usage Guidelines
In an EVPN over VXLAN scenario, a PE device at one end may fail to establish a VXLAN tunnel because the next hop of the Layer 3 prefix route is unreachable due to incorrect configurations or faults. As a result, services are interrupted. To prevent this problem, run the nexthop recursive-lookup default-route command on the PE and configure the remote PE to send a default route to the local PE. When the next hop of a specific route on the local PE is unreachable, the local PE can iterate the default route to establish a VXLAN tunnel for forwarding, ensuring normal service running.
nexthop recursive-lookup delay (BGP-EVPN address family view)
Function
The nexthop recursive-lookup delay command configures a delay in responding to changes in the next hop recursion result.
The undo nexthop recursive-lookup delay command restores the default configuration.
The nexthop recursive-lookup non-critical-event delay command configures a delay in responding to non-urgent next-hop recursion changes.
The undo nexthop recursive-lookup non-critical-event delay command restores the default configuration.
By default, the delay in responding to non-critical next hop recursion changes is 10s, and the device does not delay responding to critical next hop recursion changes.
Format
nexthop recursive-lookup delay [ delay-time ]
nexthop recursive-lookup non-critical-event delay [ nonCrit-delay-time ]
undo nexthop recursive-lookup delay
undo nexthop recursive-lookup non-critical-event delay
Parameters
Parameter | Description | Value |
---|---|---|
delay-time |
Specifies the delay in responding to recursion changes. |
The value is an integer that ranges from 1 to 100, in seconds. The default value is 5 seconds. |
nonCrit-delay-time |
Indicates the delay in responding to non-critical recursion changes. |
The value is an integer ranging from 0 to 100, in seconds. The default value is 10. |
Usage Guidelines
Usage Scenario
If the recursion result of BGP routes changes frequently, you can run the nexthop recursive-lookup delay command to configure BGP to respond to the recursion result change after a specified period of time. This can reduce unnecessary route re-selection and re-advertisement, but affects network convergence. Recursion result changes are classified into two types:
- Urgent recursion result change: When the recursion result of the next hop changes, the reachability also changes. For example, if a fault occurs on the network, BGP routes cannot find the next hop route or tunnel to which BGP routes can recurse. As a result, traffic is interrupted.
- Non-urgent recursion result change: The recursion result of the next hop changes, but the reachability does not change. For example, the interface or type of the tunnel to which the next hop of a BGP route recurses changes. That is, the tunnel to which the next hop of a BGP route recurses changes from tunnel A to tunnel B, but traffic is not interrupted. Only the tunnel to which the next hop of a BGP route recurses changes.
Configuration Impact
The rules for configuring a delay in response to next hop recursion changes and configuring a dedicated delay in response to non-critical recursion changes are as follows:
- nexthop recursive-lookup delay //Configure the device to delay for 5s in response to critical recursion changes and delay for 10s in response to non-critical recursion changes.
- nexthop recursive-lookup non-critical-event delay //Configure the device not to delay the responses to critical recursion changes but to delay for 10s in response to non-critical recursion changes.
- nexthop recursive-lookup delay 3 //Configure the device to delay for 3s in response to critical recursion changes and delay for 10s in response to non-critical recursion changes.
- nexthop recursive-lookup non-critical-event delay 6 //Configure the device not to delay the responses to critical recursion changes but to delay for 6s in response to non-critical recursion changes.
- nexthop recursive-lookup delay nexthop recursive-lookup non-critical-event delay 0 //Configure the device to delay for 5s in response to both critical and non-critical recursion changes.
- nexthop recursive-lookup delay nexthop recursive-lookup non-critical-event delay //Configure the device to delay for 5s in response to critical recursion changes and delay for 10s in response to non-critical recursion changes.
- nexthop recursive-lookup delay 3 nexthop recursive-lookup non-critical-event delay //Configure the device to delay for 3s in response to critical recursion changes and delay for 10s in response to non-critical recursion changes.
- nexthop recursive-lookup delay 3 nexthop recursive-lookup non-critical-event delay 6 //Configure the device to delay for 3s in response to critical recursion changes and delay for 6s in response to non-critical recursion changes.
- nexthop recursive-lookup delay nexthop recursive-lookup non-critical-event delay 6 //Configure the device to delay for 5s in response to critical recursion changes and delay for 6s in response to non-critical recursion changes.
Precautions
Delayed response to BGP next hop recursion changes applies only to scenarios where multiple links exist between the downstream device and the same destination. If there is only one link between the downstream device and the destination, configuring delayed response to BGP next hop recursion changes may cause heavier traffic loss when the link fails because link switching is impossible.
After the nexthop recursive-lookup delay command is run, if the delay in response to non-critical recursion changes is set to 0 using the nexthop recursive-lookup non-critical-event delay command, the actual delay in response to non-critical recursion changes is the same as the delay in response to next hop recursion changes specified in the nexthop recursive-lookup delay command.nexthop recursive-lookup restrain disable (EVPN instance view)
Function
The nexthop recursive-lookup restrain disable command disables EVPN instance recursion suppression in case of next hop flapping.
The undo nexthop recursive-lookup restrain disable command enables EVPN instance recursion suppression in case of next hop flapping.
By default, EVPN instance recursion suppression in case of next hop flapping is enabled.
Usage Guidelines
Usage Scenario
If a large number of EVPN routes recurse to the same next hop that flaps frequently, the system will be busy processing changes of these routes, which consumes excessive system resources and leads to high CPU usage. To address this problem, configure EVPN recursion suppression in case of next hop flapping. If you do not care about whether the system is busy processing route selection and advertisement and the possible high CPU usage, run the nexthop recursive-lookup restrain disable command to disable EVPN recursion suppression in case of next hop flapping.
Precautions
The nexthop recursive-lookup restrain disable command can be run in the Global EVPN configuration view and EVPN instance view. Running this command in the Global EVPN configuration view disables the function in all EVPN instances. Running this command in a specified EVPN instance disables the function only in the specified EVPN instance. For an EVPN instance, EVPN recursion suppression in case of next hop flapping can take effect only when this function is enabled in both the Global EVPN configuration view and the EVPN instance view.
nexthop recursive-lookup restrain disable (Global EVPN configuration view)
Function
The nexthop recursive-lookup restrain disable command disables EVPN global recursion suppression in case of next hop flapping.
The undo nexthop recursive-lookup restrain disable command enables EVPN global recursion suppression in case of next hop flapping.
By default, EVPN global recursion suppression in case of next hop flapping is enabled.
Usage Guidelines
Usage Scenario
If a large number of EVPN routes recurse to the same next hop that flaps frequently, the system will be busy processing changes of these routes, which consumes excessive system resources and leads to high CPU usage. To address this problem, configure EVPN recursion suppression in case of next hop flapping. If you do not care about whether the system is busy processing route selection and advertisement and the possible high CPU usage, run the nexthop recursive-lookup restrain disable command to disable EVPN recursion suppression in case of next hop flapping.
Precautions
The nexthop recursive-lookup restrain disable command can be run in the Global EVPN configuration view and EVPN instance view. Running this command in the Global EVPN configuration view disables the function in all EVPN instances. Running this command in a specified EVPN instance disables the function only in the specified EVPN instance. For an EVPN instance, EVPN recursion suppression in case of next hop flapping can take effect only when this function is enabled in both the Global EVPN configuration view and the EVPN instance view.
peer advertise (BGP-EVPN address family view)
Function
The peer advertise command enables a device to advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
The undo peer advertise command restores the default configuration.
By default, a device does not advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
Format
peer ipv4-address advertise { irb | arp }
peer ipv4-address advertise { irbv6 | nd }
undo peer ipv4-address advertise { irb | arp }
undo peer ipv4-address advertise { irbv6 | nd }
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a BGP EVPN peer. |
The value is in dotted decimal notation. |
irb |
Configures a device to advertise IRB routes to its BGP EVPN peers. |
- |
arp |
Configures a device to advertise ARP routes to its BGP EVPN peers. |
- |
irbv6 |
Configures a device to advertise IRBv6 routes to its BGP EVPN peers. |
- |
nd |
Configures a device to advertise ND routes to its BGP EVPN peers. |
- |
Usage Guidelines
Usage Scenario
To allow a device to advertise ARP or IRB routes to its BGP EVPN peers, run the peer advertise command. This command allows VTEPs to establish VXLAN tunnels and implements ARP broadcast suppression on networks. If you specify irb, VTEPs can also transmit host routes.
If you specify nd or irbv6, the local device can advertise ND or IRBv6 routes to a BGP EVPN peer. After receiving the routes, the BGP EVPN peer generates a proxy table locally. After the BGP EVPN peer receives NS packets, it searches the local proxy table. If an entry is hit, the VXLAN gateway directly performs proxy ND or multicast-to-unicast processing.Precautions
You cannot specify both arp and irb in the same BGP-EVPN address family view.
You cannot specify both nd and irbv6 in the same BGP-EVPN address family view.peer advertise (BGP-EVPN address family view) (group)
Function
The peer advertise command enables a device to advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
The undo peer advertise command restores the default configuration.
By default, a device does not advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
Format
peer group-name advertise { irb | arp }
peer group-name advertise { irbv6 | nd }
undo peer group-name advertise { irb | arp }
undo peer group-name advertise { irbv6 | nd }
Parameters
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a BGP EVPN 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. |
irb |
Configures a device to advertise IRB routes to its BGP EVPN peers. |
- |
arp |
Configures a device to advertise ARP routes to its BGP EVPN peers. |
- |
irbv6 |
Configures a device to advertise IRBv6 routes to its BGP EVPN peers. |
- |
nd |
Configures a device to advertise ND routes to its BGP EVPN peers. |
- |
Usage Guidelines
Usage Scenario
To allow a device to advertise ARP or IRB routes to its BGP EVPN peers, run the peer advertise command. This command allows VTEPs to establish VXLAN tunnels and implements ARP broadcast suppression on networks. If you specify irb, VTEPs can also transmit host routes.
If you specify nd or irbv6, the local device can advertise ND or IRBv6 routes to a BGP EVPN peer. After receiving the routes, the BGP EVPN peer generates a proxy table locally. After the BGP EVPN peer receives NS packets, it searches the local proxy table. If an entry is hit, the VXLAN gateway directly performs proxy ND or multicast-to-unicast processing.Precautions
You cannot specify both arp and irb in the same BGP-EVPN address family view.
You cannot specify both nd and irbv6 in the same BGP-EVPN address family view.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.10.1.1 as-number 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 10.10.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 advertise arp
peer advertise (BGP-EVPN address family view) (IPv6)
Function
The peer advertise command enables a device to advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
The undo peer advertise command restores the default configuration.
By default, a device does not advertise ND, IRBv6, ARP or IRB routes to a BGP EVPN peer.
Format
peer peerIpv6Addr advertise { irb | arp }
peer peerIpv6Addr advertise { irbv6 | nd }
undo peer peerIpv6Addr advertise { irb | arp }
undo peer peerIpv6Addr advertise { irbv6 | nd }
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
irb |
Configures a device to advertise IRB routes to its BGP EVPN peers. |
- |
arp |
Configures a device to advertise ARP routes to its BGP EVPN peers. |
- |
irbv6 |
Configures a device to advertise IRBv6 routes to its BGP EVPN peers. |
- |
nd |
Configures a device to advertise ND routes to its BGP EVPN peers. |
- |
Usage Guidelines
Usage Scenario
To enable a device to advertise ARP or IRB routes to its BGP EVPN peers, run the peer advertise command. This command allows VTEPs to establish VXLAN tunnels and implements ARP broadcast suppression on networks. If you specify irb, VTEPs can also transmit host routes.
If you specify nd or irbv6, the local device can advertise ND or IRBv6 routes to a BGP EVPN peer. After receiving the routes, the BGP EVPN peer generates a proxy table locally. After the BGP EVPN peer receives NS packets, it searches the local proxy table. If corresponding IPv6 host information is found, it performs proxy ND or converts the multicast message to a unicast message for forwarding.peer advertise add-path (BGP-EVPN address family view)
Function
The peer advertise add-path command configures the maximum number of routes that the device can send to a specified BGP peer.
The undo peer advertise add-path command restores the default configurations.
By default, the device sends only the optimal route to a peer.
Format
peer ipv4-address advertise add-path path-number path-number
undo peer ipv4-address advertise add-path
peer ipv6-address advertise add-path path-number path-number
undo peer ipv6-address advertise add-path
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
The value is in dotted decimal notation. |
path-number path-number |
Specifies the maximum number of routes that the device can send. |
The value is an integer ranging from 2 to 64. |
ipv6-address |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
After BGP Add-Path is configured on an RR, the RR needs to send routes to a specified peer. To configure the maximum number of routes that the RR can send to the peer, run the peer advertise add-path command. The actual number of routes that the RR can send to the peer is the smaller one of the value configured using the peer advertise add-path command and the actual number of routes selected by the RR. If the maximum number of routes that the RR can send to the peer is less than the actual number of routes selected by the RR, the RR selects the optimal and Add-Path routes based on the BGP route selection rules.
Prerequisites
The following operations have been performed:
- BGP Add-Path has been enabled and the maximum number of routes that an RR can select has been configured using the bestroute add-path command.
- The RR has been enabled to send Add-Path routes to a specified peer using the peer capability-advertise add-path send command.
Precautions
- To enable the RR to receive Add-Path routes from a specified BGP peer, run the peer capability-advertise add-path receive command to enable the RR to receive Add-Path routes from the specified BGP peer.
- The RR can send Add-Path routes to its BGP peers, and Add-Path routes are advertised based on BGP route advertisement rules.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.1 advertise add-path path-number 3
peer advertise add-path (BGP-EVPN address family view) (group)
Function
The peer advertise add-path command configures the maximum number of routes that the device can send to a specified peer.
The undo peer advertise add-path command restores the default configurations.
By default, the device sends only the optimal route to a peer.
Format
peer group-name advertise add-path path-number path-number
undo peer group-name advertise add-path
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. |
path-number path-number |
Specifies the maximum number of routes that the device can send. |
The value is an integer ranging from 2 to 64. |
Usage Guidelines
Usage Scenario
After BGP Add-Path is configured on an RR, the RR needs to send routes to a specified peer. To configure the maximum number of routes that the RR can send to the peer, run the peer advertise add-path command. The actual number of routes that the RR can send to the peer is the smaller one of the value configured using the peer advertise add-path command and the actual number of routes selected by the RR. If the maximum number of routes that the RR can send to the peer is less than the actual number of routes selected by the RR, the RR selects the optimal and Add-Path routes based on the BGP route selection rules.
Prerequisites
The following operations have been performed:
- BGP Add-Path has been enabled and the maximum number of routes that an RR can select has been configured using the bestroute add-path command.
- The RR has been enabled to send Add-Path routes to a specified peer using the peer capability-advertise add-path send command.
Precautions
- To enable a device to receive Add-Path routes from a specified BGP peer, run the peer capability-advertise add-path receive command on the device.
- A device can send Add-Path routes to its BGP peers, and Add-Path routes are advertised based on BGP route advertisement rules.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 2.2.2.2 enable [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer 2.2.2.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 advertise add-path path-number 3
peer advertise add-path (bgp-muli-instance-af-evpn view)
Function
The peer advertise add-path command configures the maximum number of routes that the device can send to a specified peer.
The undo peer advertise add-path command restores the default configurations.
By default, the device sends only the optimal route to a BGP peer.
Format
peer peerIpv4Addr advertise add-path path-number number
undo peer peerIpv4Addr advertise add-path
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
path-number number |
Specifies the maximum number of routes that the device can send. |
The value is an integer ranging from 2 to 64. |
Usage Guidelines
Usage Scenario
After BGP Add-Path is configured on an RR, the RR needs to send routes to a specified BGP peer. To configure the maximum number of routes that the RR can send to the peer, run the peer advertise add-path command. The actual number of routes that the RR can send to the peer is the smaller one of the value configured using the peer advertise add-path command and the actual number of routes selected by the RR. If the maximum number of routes that the RR can send to the peer is less than the actual number of routes selected by the RR, the RR selects the optimal and Add-Path routes based on the BGP route selection rules.
Prerequisites
The following operations have been performed:
- BGP Add-Path has been enabled and the maximum number of routes that an RR can select has been configured using the bestroute add-path command.
- The RR has been enabled to send Add-Path routes to a specified IBGP peer using the peer capability-advertise add-path send command.
Precautions
- To enable a device to receive Add-Path routes from a specified BGP peer, run the peer capability-advertise add-path receive command on the device.
- A device advertises Add-Path routes to its BGP peers based on BGP route advertisement rules.
Example
<HUAWEI> system-view Enter system view, return user view with return command. [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 instance a [HUAWEI-bgp-instance-a] peer 10.1.1.1 as-number 100 [HUAWEI-bgp-instance-a] l2vpn-family evpn [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 advertise add-path path-number 3
peer advertise route-reoriginated (BGP-EVPN address family view)
Function
The peer advertise route-reoriginated command configures a device to send the routes that are regenerated in the EVPN or VPNv4/v6 address family to a BGP EVPN peer.
The undo peer advertise route-reoriginated command restores the default configuration.
By default, a device does not send the routes that are regenerated in the EVPN or VPNv4/v6 address family to a BGP EVPN peer.
Format
peer peerIpv4Addr advertise route-reoriginated evpn { mac-ip | mac }
peer peerIpv4Addr advertise route-reoriginated evpn ip
peer peerIpv4Addr advertise route-reoriginated evpn { mac-ipv6 | ipv6 }
undo peer peerIpv4Addr advertise route-reoriginated evpn { mac-ip | mac }
undo peer peerIpv4Addr advertise route-reoriginated evpn ip
undo peer peerIpv4Addr advertise route-reoriginated evpn { mac-ipv6 | ipv6 }
peer peerIpv6Addr advertise route-reoriginated evpn ip
peer peerIpv6Addr advertise route-reoriginated evpn ipv6
undo peer peerIpv6Addr advertise route-reoriginated evpn ipv6
undo peer peerIpv6Addr advertise route-reoriginated evpn ip
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
evpn |
Re-encapsulates the received EVPN routes. |
- |
mac-ip |
Re-encapsulates the IRB or ARP routes in received EVPN routes. |
- |
mac |
Re-encapsulates MAC routes in received EVPN routes. |
- |
mac-ipv6 |
Re-encapsulates the IRBv6 or ND routes in received EVPN routes. |
- |
ipv6 |
Re-encapsulates received IPv6 prefix routes. |
- |
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The format is X:X:X:X:X:X:X:X. |
ip |
Re-encapsulates received prefix routes. |
- |
Usage Guidelines
Usage Scenario
Data Center Interconnect (DCI) is an umbrella term for various solutions used to interconnect data centers. In a DCI solution, a DCI-PE re-originates received EVPN routes before sending them to peers.
After a DCI-PE receives EVPN routes with the VXLAN encapsulation attribute from a data center, the DCI-PE re-originates these EVPN routes and advertises them with the SRv6 encapsulation attribute to its BGP EVPN peers on the DCI backbone network.
You can query the BGP EVPN routing table to check whether a re-originated EVPN route carries the reoriginated flag.
Prerequisites
Route information exchange has been enabled between the local device and a specified peer using the peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2.2.2.2 enable [HUAWEI-bgp-af-evpn] peer 2.2.2.2 advertise route-reoriginated evpn mac
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:DB8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 advertise route-reoriginated evpn ipv6
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 advertise route-reoriginated evpn mac-ip
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:DB8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 advertise route-reoriginated evpn ip
peer advertise route-reoriginated (BGP-EVPN address family view) (group)
Function
The peer advertise route-reoriginated command configures a device to send the routes that are regenerated in the EVPN or VPNv4/v6 address family to a BGP EVPN peer group.
The undo peer advertise route-reoriginated command restores the default configuration.
By default, a device does not send the routes that are regenerated in the EVPN or VPNv4/v6 address family to a BGP EVPN peer group.
Format
peer peerGroupName advertise route-reoriginated evpn { mac-ip | mac }
peer peerGroupName advertise route-reoriginated evpn ip
peer peerGroupName advertise route-reoriginated evpn { mac-ipv6 | ipv6 }
undo peer peerGroupName advertise route-reoriginated evpn { mac-ip | mac }
undo peer peerGroupName advertise route-reoriginated evpn ip
undo peer peerGroupName advertise route-reoriginated evpn { mac-ipv6 | ipv6 }
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
evpn |
Re-encapsulates received EVPN routes. |
- |
mac-ip |
Re-encapsulates the IRB or ARP routes in received EVPN routes. |
- |
mac |
Re-encapsulates MAC routes in received EVPN routes. |
- |
ip |
Re-encapsulates received prefix routes. |
- |
mac-ipv6 |
Re-encapsulates the IRBv6 or ND routes in received EVPN routes. |
- |
ipv6 |
Re-encapsulates received IPv6 prefix routes. |
- |
Usage Guidelines
Usage Scenario
DCI is an umbrella term covering multiple DC interconnection solutions. In the DCI solution, a DCI-PE re-encapsulates received EVPN or VPNv4/v6 routes and then sends these routes to its peers.
- After a DCI-PE receives EVPN routes with the VXLAN encapsulation attribute from a DC, the DCI-PE re-originates these EVPN routes and advertises them with the MPLS encapsulation attribute to its BGP EVPN peers on the DCI backbone network.
- After a DCI-PE receives EVPN, VPNv4, or VPNv6 routes with the MPLS encapsulation attribute from BGP EVPN, VPNv4, or VPNv6 peers on the DCI backbone network, the DCI-PE re-originates these routes and advertises them with the VXLAN encapsulation attribute to the DC side.
Prerequisites
Route information exchange has been enabled between the local device and a specified peer group using the peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 advertise route-reoriginated evpn mac-ip
peer advertise-community (BGP-EVPN address family view)
Function
The peer advertise-community command configures a device to advertise community attributes to a peer.
The undo peer advertise-community command cancels the configuration.
By default, a device advertises no community attribute to its peer
Format
peer peerIpv4Addr advertise-community
undo peer peerIpv4Addr advertise-community
peer peerIpv6Addr advertise-community
undo peer peerIpv6Addr advertise-community
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
The value is in dotted decimal notation. |
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
The peer advertise-community command is used to configure a device to advertise a community attribute to its peer.
Prerequisites
Enable the peer in current view using peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 advertise-community
peer advertise-community (BGP-EVPN address family view) (group)
Function
The peer advertise-community command configures a device to advertise the community attribute to a peer group.
The undo peer advertise-community command restores the default configuration.
By default, a device advertises no community attribute to its peer group.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
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. |
Usage Guidelines
Usage Scenario
The peer advertise-community command is used to configure a device to advertise a community attribute to its peer group. If a device advertises a community attribute to its peer group, all the members of the peer group will inherit the configuration. This simplifies the application of routing policies and facilitates route maintenance and management.
Prerequisites
Enable the peer group in current view using peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer 2.2.2.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 advertise-community
peer advertise-community (bgp-muli-instance-af-evpn view)
Function
The peer advertise-community command configures a device to advertise community attributes to a peer.
The undo peer advertise-community command cancels the configuration.
By default, a device advertises no community attribute to its peer
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
To determine whether to advertise the community attribute to a peer, run the peer advertise-community command.
Prerequisites
Enable the peer in current view using peer enable command.
Example
<HUAWEI> system-view Enter system view, return user view with return command. [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 instance a [HUAWEI-bgp-instance-a] peer 10.1.1.1 as-number 100 [HUAWEI-bgp-instance-a] l2vpn-family evpn [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 advertise-community
peer advertise-large-community
Function
The peer advertise-large-community command enables a device to advertise the Large-Community attribute to a peer.
The undo peer advertise-large-community command cancels the configuration.
By default, a device does not advertise the Large-Community attribute to its peer.
Format
peer peerIpv6Addr advertise-large-community [ disable ]
undo peer peerIpv6Addr advertise-large-community [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
disable |
Disables a device from advertising the Large-Community attribute to a peer. |
- |
Usage Guidelines
Usage Scenario
To enable a device to advertise the Large-Community attribute to its BGP peer, run the peer advertise-large-community command.
Prerequisites
A route-policy has been used to define the large-community attribute.
Example
<HUAWEI> system-view [HUAWEI] ip ipv6-prefix 1 permit 2001:db8::2 96 [HUAWEI] route-policy RP permit node 10 [HUAWEI-route-policy] if-match ipv6-prefix 1 [HUAWEI-route-policy] apply large-community 35551:100:65552 additive [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8::2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8::2 enable [HUAWEI-bgp-af-evpn] peer 2001:db8::2 advertise-large-community
peer advertise-large-community (BGP-EVPN address family view)
Function
The peer advertise-large-community command enables the function to advertise routes carrying the large-community attribute to a BGP EVPN peer.
The undo peer advertise-large-community command disables the function to advertise routes carrying the large-community attribute to a BGP EVPN peer.
By default, a device does not advertise routes carrying the large-community attribute to a BGP EVPN peer.
Format
peer peerIpv4Addr advertise-large-community [ disable ]
undo peer peerIpv4Addr advertise-large-community [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
disable |
Disables the Large-Community attribute from being advertised to a BGP peer. |
- |
Usage Guidelines
Usage Scenario
To enable the function to advertise routes carrying the large-community attribute to the BGP EVPN peer, run the peer advertise-large-community command.
Prerequisites
A route-policy has been used to define the large-community attribute.
Example
<HUAWEI> system-view [HUAWEI] ip ip-prefix 1 permit 10.1.1.0 24 [HUAWEI] route-policy RP permit node 10 [HUAWEI-route-policy] if-match ip-prefix 1 [HUAWEI-route-policy] apply large-community 35551:100:65552 additive [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.2 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.2 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 route-policy RP export [HUAWEI-bgp-af-evpn] peer 10.1.1.2 advertise-large-community
peer advertise-large-community (BGP-EVPN address family view) (group)
Function
The peer advertise-large-community command enables the function to advertise routes carrying the large-community attribute to a BGP EVPN peer group.
The undo peer advertise-large-community command disables the function to advertise routes carrying the large-community attribute to a BGP EVPN peer group.
By default, a device does not advertise routes carrying the large-community attribute to a BGP EVPN peer group.
Format
peer peerGroupName advertise-large-community
undo peer peerGroupName advertise-large-community
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
Usage Guidelines
Usage Scenario
To enable a device to advertise the Large-Community attribute to a BGP EVPN peer group, run the peer advertise-large-community command. If the Large-Community attribute is advertised to a BGP EVPN peer group, all BGP EVPN peers in the peer group inherit the Large-Community attribute configuration. This simplifies routing policy application and facilitates route maintenance and management.
Prerequisites
A route-policy has been used to define the large-community attribute.
Example
<HUAWEI> system-view [HUAWEI] route-policy RP permit node 10 [HUAWEI-route-policy] apply large-community 35551:100:65552 additive [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer gp1 route-policy RP export [HUAWEI-bgp-af-evpn] peer gp1 advertise-large-community
peer allow-as-loop (BGP-EVPN address family view) (group)
Function
The peer allow-as-loop command sets the number of local AS number repetitions.
The undo peer allow-as-loop command cancels the configuration.
By default, the local AS number cannot be repeated.
Parameters
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a BGP EVPN 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. |
number |
Specifies the number of local AS number repetitions. |
The value is an integer ranging from 1 to 10. The default value is 1. |
Usage Guidelines
Usage Scenario
Generally, BGP uses AS numbers to detect routing loops. The AS numbers in the AS_Path of each received route are matched against the local AS number configured using the bgp command and the fake AS number configured using the peer fake-as command. The largest number of times any of the configured AS numbers is repeated is considered as the maximum number. In Hub-Spoke networking, if EBGP runs between the PE and CE at the Hub site, the routing information advertised by the Hub-PE to the Hub-CE carries the AS number of the local AS. When the Hub-PE receives a route update message from the Hub-CE, the route update message carries the AS number of the local AS. As a result, the Hub-PE cannot receive the route update message.
To ensure correct route transmission in Hub-Spoke networking, configure the BGP peers through which the VPN routes are advertised from the Hub-CE to the Spoke-CE to allow routes with the AS number repeated once in the AS_Path attribute to pass through.Prerequisites
The specified peer group has been enabled in the BGP-EVPN address family view.
Configuration Impact
If the peer allow-as-loop command is run for a peer group multiple times, the latest configuration overrides the previous one.
Precautions
The peer allow-as-loop command does not take effect for IBGP peers or BGP peers in a sub-confederation. The device checks whether the routes received from EBGP peers or EBGP peers in the confederation contain the local AS number. The minimum number of repetitions is 2, and the value 1 is not displayed.
Running the peer allow-as-loop command may cause routing loops. Therefore, exercise caution when running this command and specify the number of AS number repetitions as required.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp external [HUAWEI-bgp] peer 10.1.1.9 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.9 enable [HUAWEI-bgp-af-evpn] peer gp enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 group gp [HUAWEI-bgp-af-evpn] peer gp allow-as-loop 2
peer allow-as-loop (BGP-EVPN address family view) (IPv6)
Function
The peer allow-as-loop command sets the number of local AS number repetitions.
The undo peer allow-as-loop command cancels the configuration.
By default, the local AS number cannot be repeated.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
num |
Maximum number of times the local AS number can be included in the AS_Path of each received route. |
The value is an integer in the range from 1 to 10. The default value is 1. |
Usage Guidelines
Usage Scenario
Generally, BGP uses AS numbers to detect routing loops. The local AS number configured using the bgp command and the fake AS number configured using the peer fake-as command are compared with the AS_Path carried in the received route. The number of loops is the largest. In Hub and Spoke networking, if EBGP runs between the PE and CE of the Hub, the routing information advertised by the Hub-PE to the Hub-CE carries the AS number of the Hub-CE. When the Hub-PE receives the routing update from the Hub-CE, the routing update carries the AS number of the Hub-PE. In this case, the Hub-PE cannot receive the routing update.
To ensure correct route transmission in the Hub and Spoke networking, configure the BGP peers on the path from the Hub-CE to the Spoke-CE to allow the routes with the same AS number in the AS_Path attribute to pass.Prerequisites
BGP peers have been enabled in the BGP-EVPN address family view.
Configuration Impact
If the peer command is run more than once for the same peer, the latest configuration overrides the previous one.
Precautions
The peer allow-as-loop command does not take effect for IBGP peers or BGP peers in a sub-confederation. The device checks whether the routes received from EBGP peers or EBGP peers in the confederation contain the local AS number. The minimum number of repetitions is 2, and the value 1 is not displayed.
Running the peer allow-as-loop command may cause routing loops. Therefore, exercise caution when running this command and specify the number of AS number repetitions as required.Example
<HUAWEI> system-view [HUAWEI] bgp 200 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 allow-as-loop 2
peer allow-as-loop (BGP-EVPN address family view)(IPv4)
Function
The peer allow-as-loop command sets the number of local AS number repetitions.
The undo peer allow-as-loop command cancels the configuration.
By default, the local AS number cannot be repeated.
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
number |
Specifies the number of local AS number repetitions. |
The value is an integer ranging from 1 to 10. The default value is 1. |
Usage Guidelines
Usage Scenario
BGP uses AS numbers to detect routing loops. The AS numbers in the AS_Path of each received route are matched against the local AS number configured using the bgp command and the fake AS number configured using the peer fake-as command. The largest number of times any of the configured AS numbers is repeated is considered as the maximum number. In the Hub and Spoke networking, if EBGP runs between a Hub-PE and a Hub-CE on a Hub site, the route sent from the Hub-PE to the Hub-CE carries the AS number of the Hub-PE. If the Hub-CE sends a routing update to the Hub-PE, the Hub-PE will deny it because the routing update contains the AS number of the Hub-PE.
To ensure proper route transmission in the Hub and Spoke networking, configure all the BGP peers on the path, along which the Hub-CE advertises private network routes to the Spoke-CE, to accept the routes in which the AS number repeats once.Prerequisites
The specified peer has been enabled in the BGP-EVPN address family view.
Configuration Impact
If the peer allow-as-loop command is run for a peer multiple times, the latest configuration overrides the previous one.
Precautions
The peer allow-as-loop command does not take effect for IBGP peers or BGP peers in a sub-confederation. The device checks whether the routes received from EBGP peers or EBGP peers in the confederation contain the local AS number. The minimum number of repetitions is 2, and the value 1 is not displayed.
Running the peer allow-as-loop command may cause routing loops. Therefore, exercise caution when running this command and specify the number of AS number repetitions as required.peer attribute-id (BGP-EVPN address family view)
Function
The peer attribute-id command configures the mode of processing a specified path attribute or an incorrect path attribute.
The undo peer attribute-id command restores the default setting.
By default, BGP path attributes are processed according to a standard protocol.
Format
peer peerIpv4Addr path-attribute-treat attribute-id { id [ to id2 ] } &<1-255> { discard | withdraw | treat-as-unknown }
peer peerIpv4Addr treat-with-error attribute-id id accept-zero-value
undo peer peerIpv4Addr path-attribute-treat attribute-id { id [ to id2 ] } &<1-255> [ discard | withdraw | treat-as-unknown ]
undo peer peerIpv4Addr treat-with-error attribute-id id [ accept-zero-value ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
path-attribute-treat |
Processes path attribute packets. |
- |
attribute-id id |
Specifies an attribute ID. |
The value is an integer, which can be as follows: 0: Reserved 5: LOCAL_PREF 6: ATOMIC_AGGREGATE 7: AGGREGATOR 9: ORIGINATORID 10: CLUSTER_LIST 11: DPA 12: ADVERTISER 13: RCID_PATH / CLUSTER_ID 16: Extended Communities 17: AS4_PATH 18: AS4_AGGREGATOR 19: SAFI Specific Attribute (SSA) 20: Connector Attribute 21: AS_PATHLIMIT 22: PMSI_TUNNEL 23: Tunnel Encapsulation Attribute 24: Traffic Engineering 25: IPv6 Address Specific Extended Community 26: AIGP 27: PE Distinguisher Labels 28: ELC 29: LS_TYPE 30: REMOTE_NEXTHOP 32: LARGE_COMMUNITY 40: PREFIX_SID 128: ATTR_SET 129: WIDE_COMMUNITY 255: Reserved for development 31, 33-39, 41-127, 130-254: Unassigned |
to id2 |
Specifies an end attribute ID. |
The value is an integer, which can be as follows: 0: Reserved 5: LOCAL_PREF 6: ATOMIC_AGGREGATE 7: AGGREGATOR 9: ORIGINATORID 10: CLUSTER_LIST 11: DPA 12: ADVERTISER 13: RCID_PATH / CLUSTER_ID 16: Extended Communities 17: AS4_PATH 18: AS4_AGGREGATOR 19: SAFI Specific Attribute (SSA) 20: Connector Attribute 21: AS_PATHLIMIT 22: PMSI_TUNNEL 23: Tunnel Encapsulation Attribute 24: Traffic Engineering 25: IPv6 Address Specific Extended Community 26: AIGP 27: PE Distinguisher Labels 28: ELC 29: LS_TYPE 30: REMOTE_NEXTHOP 32: LARGE_COMMUNITY 40: PREFIX_SID 128: ATTR_SET 129: WIDE_COMMUNITY 255: Reserved for development 31, 33-39, 41-127, 130-254: Unassigned |
discard |
Discards messages carrying specified attributes. |
- |
withdraw |
Withdraws the routes with the specified attribute. |
- |
treat-as-unknown |
Processes the specified attributes as unknown attributes. If a specified attribute is optional transitive, the BGP device accepts this attribute and advertises it to other peers; if the specified attribute is of any other type, the BGP device discards this attribute. |
- |
treat-with-error |
Processes packets with incorrect path attributes. |
- |
accept-zero-value |
Indicates to accept the path attributes with a value of 0. |
- |
Usage Guidelines
Usage Scenario
BGP Update messages contain various path attributes. If the local device receives any Update message with an incorrect format, BGP session flapping may occur. To enhance reliability, you can run this command to configure a processing mode for specified BGP path attributes.
The path-attribute-treat command is used to specify a processing mode for path attributes. The processing modes are as follows:- discard: discarding messages carrying specified attributes.
- withdraw: withdrawing routes with specified attributes.
- treat-as-unknown: Processing specified attributes as unknown attributes
treat-with-error is used to specify the processing mode of incorrect path attributes. The processing mode is as follows:
- accept-zero-value: accepting the path attribute with the value of 0.
Precautions
Running this command may cause path attributes to be discarded or routes to be withdrawn. Therefore, exercise caution when running this command.
This function takes effect immediately for the routes received after this command is executed. However, it does not take effect immediately for the routes received before this command is run; to make it take effect immediately, you need to run the refresh bgp command. Currently, attribute-id id in the treat-with-error command supports only the Originator_ID attribute.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.9 path-attribute-treat attribute-id 19 to 21 discard
peer attribute-id (BGP-EVPN address family view) (IPv6)
Function
The peer attribute-id command configures the mode of processing a specified path attribute or an incorrect path attribute.
The undo peer attribute-id command restores the default setting.
By default, BGP path attributes are processed according to a standard protocol.
Format
peer peerIpv6Addr path-attribute-treat attribute-id { id [ to id2 ] } &<1-255> { discard | withdraw | treat-as-unknown }
peer peerIpv6Addr treat-with-error attribute-id id accept-zero-value
undo peer peerIpv6Addr path-attribute-treat attribute-id { id [ to id2 ] } &<1-255> [ discard | withdraw | treat-as-unknown ]
undo peer peerIpv6Addr treat-with-error attribute-id id [ accept-zero-value ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies an IPv6 peer address. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
path-attribute-treat |
Processes path attribute packets. |
- |
attribute-id id |
Specifies an attribute ID. |
The value is an integer, which can be as follows: 0: Reserved 5: LOCAL_PREF 6: ATOMIC_AGGREGATE 7: AGGREGATOR 9: ORIGINATORID 10: CLUSTER_LIST 11: DPA 12: ADVERTISER 13: RCID_PATH / CLUSTER_ID 16: Extended Communities 17: AS4_PATH 18: AS4_AGGREGATOR 19: SAFI Specific Attribute (SSA) 20: Connector Attribute 21: AS_PATHLIMIT 22: PMSI_TUNNEL 23: Tunnel Encapsulation Attribute 24: Traffic Engineering 25: IPv6 Address Specific Extended Community 26: AIGP 27: PE Distinguisher Labels 28: ELC 29: LS_TYPE 30: REMOTE_NEXTHOP 32: LARGE_COMMUNITY 40: PREFIX_SID 128: ATTR_SET 129: WIDE_COMMUNITY 255: Reserved for development 31, 33-39, 41-127, 130-254: Unassigned |
to id2 |
Specifies an end attribute ID. |
The value is an integer, which can be as follows: 0: Reserved 5: LOCAL_PREF 6: ATOMIC_AGGREGATE 7: AGGREGATOR 9: ORIGINATORID 10: CLUSTER_LIST 11: DPA 12: ADVERTISER 13: RCID_PATH / CLUSTER_ID 16: Extended Communities 17: AS4_PATH 18: AS4_AGGREGATOR 19: SAFI Specific Attribute (SSA) 20: Connector Attribute 21: AS_PATHLIMIT 22: PMSI_TUNNEL 23: Tunnel Encapsulation Attribute 24: Traffic Engineering 25: IPv6 Address Specific Extended Community 26: AIGP 27: PE Distinguisher Labels 28: ELC 29: LS_TYPE 30: REMOTE_NEXTHOP 32: LARGE_COMMUNITY 40: PREFIX_SID 128: ATTR_SET 129: WIDE_COMMUNITY 255: Reserved for development 31, 33-39, 41-127, 130-254: Unassigned |
discard |
Discards messages carrying specified attributes. |
- |
withdraw |
Withdraws the routes with the specified attribute. |
- |
treat-as-unknown |
Processes the specified attributes as unknown attributes. If a specified attribute is optional transitive, the BGP device accepts this attribute and advertises it to other peers; if the specified attribute is of any other type, the BGP device discards this attribute. |
- |
treat-with-error |
Processes packets with incorrect path attributes. |
- |
accept-zero-value |
Indicates to accept the path attributes with a value of 0. |
- |
Usage Guidelines
Usage Scenario
BGP Update messages contain various path attributes. If the local device receives any Update message with an incorrect format, BGP session flapping may occur. To enhance reliability, you can run this command to configure a processing mode for specified BGP path attributes.
The path-attribute-treat command is used to specify a processing mode for path attributes. The processing modes are as follows:- discard: discarding messages carrying specified attributes.
- withdraw: withdrawing routes with specified attributes.
- treat-as-unknown: Processing specified attributes as unknown attributes
treat-with-error is used to specify the processing mode of incorrect path attributes. The processing mode is as follows:
- accept-zero-value: accepting the path attribute with the value of 0.
Precautions
Running this command may cause path attributes to be discarded or routes to be withdrawn. Therefore, exercise caution when running this command.
This function takes effect immediately for the routes received after this command is executed. However, it does not take effect immediately for the routes received before this command is run; to make it take effect immediately, you need to run the refresh bgp command. Currently, attribute-id id in the treat-with-error command supports only the Originator_ID attribute.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 path-attribute-treat attribute-id 19 to 21 discard
peer capability-advertise add-path (BGP-EVPN address family view)
Function
The peer capability-advertise add-path command enables a device to send Add-Path routes to or receive Add-Path routes from a specified peer.
The undo peer capability-advertise add-path command restores the default configuration.
By default, a device is disabled from sending Add-Path routes to or receiving Add-Path routes from a specified peer.
Format
peer ipv4-address capability-advertise add-path { both | receive | send }
undo peer ipv4-address capability-advertise add-path { both | receive | send }
peer ipv6-address capability-advertise add-path { both | receive | send }
undo peer ipv6-address capability-advertise add-path { both | receive | send }
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
The value is in dotted decimal notation. |
both |
Enables the RR to receive Add-Path routes from and send Add-Path routes to a specified IBGP peer. |
- |
receive |
Enables the RR to receive Add-Path routes from a specified IBGP peer. |
- |
send |
Enables the RR to send Add-Path routes to a specified IBGP peer. |
- |
ipv6-address |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
This command is used to configure BGP Add-Path. After BGP Add-Path is configured, a device can advertise two or more routes with the same prefix to a BGP peer. These routes can back up each other or load-balance traffic, thereby ensuring data transmission reliability.
When deploying BGP Add-Path, run the peer capability-advertise add-path command to enable the device to advertise Add-Path routes to a specified BGP peer or receive Add-Path routes from a specified BGP peer. In addition, you need to run the peer advertise add-path command to configure the number of routes that the device can advertise to a specified peer.Prerequisites
Enable the peer in current view using peer enable command.
Precautions
If the peer capability-advertise add-path command is run for a specified peer and the peer advertise best-external command is run for a specified peer group, the peer cannot inherit the function of the peer advertise best-external command configured for the peer group when the peer is added to the peer group.
Enabling or disabling Add-Path will disconnect and then re-establish the peer session. This operation will cause temporary network interruption. Therefore, exercise caution when performing this operation.peer capability-advertise add-path (BGP-EVPN address family view) (group)
Function
The peer capability-advertise add-path command enables a device to send Add-Path routes to or receive Add-Path routes from a BGP EVPN peer group.
The undo peer capability-advertise add-path command restores the default configuration.
By default, a device is disabled from sending Add-Path routes to or receiving Add-Path routes from a BGP EVPN peer group.
Format
peer peerGroupName capability-advertise add-path { both | receive | send }
undo peer peerGroupName capability-advertise add-path { both | receive | send }
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
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. |
both |
Enables the RR to receive Add-Path routes from and send Add-Path routes to a specified IBGP peer. |
- |
receive |
Enables the RR to receive Add-Path routes from a specified IBGP peer. |
- |
send |
Enables the RR to send Add-Path routes to a specified IBGP peer. |
- |
Usage Guidelines
Usage Scenario
This command is used to configure BGP Add-Path. After BGP Add-Path is configured, a device can advertise two or more routes with the same prefix to a BGP peer. These routes can back up each other or load-balance traffic, thereby ensuring data transmission reliability.
When deploying BGP Add-Path, run the peer capability-advertise add-path command to enable the device to advertise Add-Path routes to a specified BGP peer or receive Add-Path routes from a specified BGP peer. In addition, you need to run the peer advertise add-path command to configure the number of routes that the device can advertise to a specified peer.Prerequisites
Enable the peer group in current view using peer enable command.
Precautions
If you enable or disable the Add-Path function, the BGP peer relationship will be re-established, which can lead to a temporary network interruption. Therefore, exercise caution when running the related commands.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer 2.2.2.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 capability-advertise add-path receive
peer capability-advertise add-path (bgp-muli-instance-af-evpn view)
Function
The peer capability-advertise add-path command enables a device to send Add-Path routes to or receive Add-Path routes from a specified peer.
The undo peer capability-advertise add-path command restores the default configuration.
By default, a device is disabled from sending Add-Path routes to or receiving Add-Path routes from a specified peer.
Format
peer ipv4-address capability-advertise add-path { both | receive | send }
undo peer ipv4-address capability-advertise add-path { both | receive | send }
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
The value is in dotted decimal notation. |
both |
Enables the RR to receive Add-Path routes from and send Add-Path routes to a specified IBGP peer. |
- |
receive |
Enables the RR to receive Add-Path routes from a specified IBGP peer. |
- |
send |
Enables the RR to send Add-Path routes to a specified IBGP peer. |
- |
Usage Guidelines
Usage Scenario
This command is used to configure BGP Add-Path. After BGP Add-Path is configured, a device can advertise two or more routes with the same prefix to a BGP peer. These routes can back up each other or load-balance traffic, thereby ensuring data transmission reliability.
When deploying BGP Add-Path, run the peer capability-advertise add-path command to enable the device to advertise Add-Path routes to a specified BGP peer or receive Add-Path routes from a specified BGP peer. In addition, you need to run the peer advertise add-path command to configure the number of routes that the device can advertise to a specified peer.Prerequisites
Enable the peer in current view using peer enable command.
Precautions
If you enable or disable the Add-Path function, the BGP peer relationship will be re-established, which can lead to a temporary network interruption. Therefore, exercise caution when running the related commands.
Example
<HUAWEI> system-view Enter system view, return user view with return command. [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 instance a [HUAWEI-bgp-instance-a] peer 10.1.1.1 as-number 100 [HUAWEI-bgp-instance-a] l2vpn-family evpn [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-instance-a-af-evpn] peer 10.1.1.1 capability-advertise add-path receive
peer enable (BGP-EVPN address family view) (group)
Function
The peer enable command enables a BGP device to exchange routes with a specified peer group in the address family view.
The undo peer enable command disables a BGP device from exchanging routes with a specified peer group.
By default, only the peer group in the BGP IPv4 unicast address family view is automatically enabled.
Parameters
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a BGP EVPN 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. |
Usage Guidelines
Usage Scenario
By default, only peer groups in the BGP-IPv4 unicast address family are automatically enabled to exchange routing information. In other words, after the peer as-number command is run in the BGP view, the system automatically configures the peer enable command. In other address family views, however, this function must be manually enabled.
Configuration Impact
Enabling or disabling a BGP peer group in an address family, for example, running the peer enable command or the undo peer enable command in a VPNv4 address family, causes teardown and re-establishment of the BGP connection of the peer group in other address families.
Precautions
If the device has established peer relationships with a peer group in another address family, running the peer enable command may disconnect and re-establish all peer relationships with the peer group, causing route flapping. Therefore, exercise caution when running this command.
By default, the routes that are learned from IBGP peers in the EVPN address family and leaked into BGP VPN instances are advertised to IBGP peers in the VPN instances, which may cause routing loops. Therefore, you are advised to configure loop prevention mechanisms such as SoO to prevent loops. By default, the routes learned from IBGP peers in the BGP-VPN instance IPv4 address family or BGP-VPN instance IPv6 address family and reported to EVPN are advertised to EVPN IBGP peers.peer enable (BGP-EVPN address family view) (IPv4)
Function
The peer enable command enables a BGP device to exchange routes with a specified peer in the address family view.
The undo peer enable command disables a BGP device from exchanging routes with a specified peer.
By default, only the peer in the BGP IPv4 unicast address family view is automatically enabled.
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
By default, only peer groups in the BGP-IPv4 unicast address family are automatically enabled to exchange routing information. In other words, after the peer as-number command is run in the BGP view, the system automatically configures the peer enable command. In other address family views, however, this function must be manually enabled.
Configuration Impact
Enabling or disabling a BGP peer in an address family, for example, running the peer enable command or the undo peer enable command in a VPNv4 address family, causes teardown and re-establishment of the BGP connection of the peer in other address families.
Precautions
If the device has established peer relationships with a peer in other address families, running the peer enable command may disconnect and re-establish all peer relationships with the peer, causing route flapping. Therefore, exercise caution when running this command.
By default, the routes that are learned from IBGP peers in the EVPN address family and leaked into BGP VPN instances are advertised to IBGP peers in the VPN instances, which may cause routing loops. Therefore, you are advised to configure loop prevention mechanisms such as SoO to prevent loops. By default, the routes learned from IBGP peers in the BGP-VPN instance IPv4 address family or BGP-VPN instance IPv6 address family and reported to EVPN are advertised to EVPN IBGP peers.peer enable (BGP-EVPN address family view) (IPv6)
Function
The peer enable command enables a BGP device to exchange routes with a specified peer in the address family view.
The undo peer enable command disables a BGP device from exchanging routes with a specified peer.
By default, only the peer in the BGP IPv4 unicast address family view is automatically enabled.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
By default, only peer groups in the BGP-IPv4 unicast address family are automatically enabled to exchange routing information. In other words, after the peer as-number command is run in the BGP view, the system automatically configures the peer enable command. In other address family views, however, this function must be manually enabled.
Configuration Impact
Enabling or disabling a BGP peer in an address family, for example, running the peer enable command or the undo peer enable command in a VPNv6 address family, causes teardown and re-establishment of the BGP connection of the peer in other address families.
Precautions
If the device has established peer relationships with a peer in other address families, running the peer enable command may disconnect and re-establish all peer relationships with the peer, causing route flapping. Therefore, exercise caution when running this command.
By default, the routes that are learned from IBGP peers in the EVPN address family and leaked into BGP VPN instances are advertised to IBGP peers in the VPN instances, which may cause routing loops. Therefore, you are advised to configure loop prevention mechanisms such as SoO to prevent loops. By default, the routes learned from IBGP peers in the BGP-VPN instance IPv4 address family or BGP-VPN instance IPv6 address family and reported to EVPN are advertised to EVPN IBGP peers.peer graceful-restart static-timer (BGP-EVPN address family view)
Function
The peer graceful-restart static-timer command sets the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established.
The undo peer graceful-restart static-timer command deletes the configuration.
By default, the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established is 150s.
Format
peer ipv4-address graceful-restart static-timer restart-time
undo peer ipv4-address graceful-restart static-timer restart-time
undo peer ipv4-address graceful-restart static-timer
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
restart-time |
Specifies the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established. |
The value is an integer ranging from 3600 to 2147483647, in seconds. |
Usage Guidelines
Usage Scenario
By default, the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established is 150s. Even if you run the graceful-restart timer restart time command in the BGP view, the maximum wait time can be changed to 3600s at most. If some BGP EVPN sessions take more than 3600s to re-establish due to poor network conditions, you can run the peer graceful-restart static-timer command to set a proper wait time for a specified peer.
Configuration Impact
If the graceful-restart timer restart command is run in the BGP view and the peer graceful-restart static-timer command is run in any of its views, the latter command takes precedence over the former command.
Precautions
GR has been enabled using the graceful-restart command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] graceful-restart [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 graceful-restart static-timer 5000
peer graceful-restart static-timer (BGP-EVPN address family view)(IPv6)
Function
The peer graceful-restart static-timer command sets the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established.
The undo peer graceful-restart static-timer command deletes the configuration.
By default, the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established is 150s.
Format
peer peerIpv6Addr graceful-restart static-timer restart-time
undo peer peerIpv6Addr graceful-restart static-timer restart-time
undo peer peerIpv6Addr graceful-restart static-timer
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
restart-time |
Specifies the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established. |
The value is an integer ranging from 3600 to 2147483647, in seconds. |
Usage Guidelines
Usage Scenario
By default, the maximum duration from the time the local device finds that the peer device is restarted to the time a BGP EVPN session is re-established is 150s. Even if you run the graceful-restart timer restart time command in the BGP view, the maximum wait time can be changed to 3600s at most. If some BGP EVPN sessions take more than 3600s to re-establish due to poor network conditions, you can run the peer graceful-restart static-timer command to set a proper wait time for a specified peer.
Configuration Impact
If the graceful-restart timer restart command is run in the BGP view and the peer graceful-restart static-timer command is run in any of its views, the latter command takes precedence over the former command.
Precautions
GR has been enabled using the graceful-restart command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] graceful-restart [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 graceful-restart static-timer 5000
peer group (BGP-EVPN address family view) (IPv6)
Function
The peer group command adds a peer to a peer group.
The undo peer group command removes a peer from a peer group but retains all the configurations of the peer.
By default, a peer is not added to any peer group.
Parameters
Parameter | Description | Value |
---|---|---|
ipv6-address |
Specifies the IPv6 address of a peer. |
The format is X:X:X:X:X:X:X:X. |
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. |
Usage Guidelines
Usage Scenario
On a large-scale BGP network, there are a large number of peers and many of them have the same routing policies. To configure these peers, you have to repeatedly use some commands. In such a case, configuring peer groups can simplify configurations. If you intend to perform the same configuration on several peers, create and configure a peer group. Then, add the peers to the peer group. The peers will inherit the configurations of the peer group.
Precautions
You can add peers of different AS numbers into the same peer group. If a peer has an AS number, the peer keeps its own AS number after being added to a peer group. If a peer has no AS number and a peer group has an AS number, the peer inherits the AS number of the peer group after being added to the peer group.
Peers in the same peer group can have different import and export routing policies configured. The undo peer group command has the same function as the undo peer and undo peer enable commands.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] group test1 internal [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer test1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 group test1
peer group (BGP-EVPN address family view)(IPv4)
Function
The peer group command adds a peer to a peer group.
The undo peer group command removes a peer from a peer group but retains all the configurations of the peer.
By default, a peer is not added to any peer group.
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
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. |
Usage Guidelines
Usage Scenario
On a large-scale BGP network, there are a large number of peers and many of them have the same routing policies. To configure these peers, you have to repeatedly use some commands. In such a case, configuring peer groups can simplify configurations. If you intend to perform the same configuration on several peers, create and configure a peer group. Then, add the peers to the peer group. The peers will inherit the configurations of the peer group.
Precautions
You can add peers of different AS numbers into the same peer group. If a peer has an AS number, the peer keeps its own AS number after being added to a peer group. If a peer has no AS number and a peer group has an AS number, the peer inherits the AS number of the peer group after being added to the peer group.
Peers in the same peer group can have different import and export routing policies configured. The undo peer group command has the same function as the undo peer and undo peer enable commands.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.1 as-number 100 [HUAWEI-bgp] group group1 internal [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer group1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.1 group group1
peer high-priority (BGP-EVPN address family view)
Function
The peer high-priority command enables a device to preferentially select routes based on their priorities in the EVPN address family.
The undo peer high-priority command disables a device from preferentially selecting routes based on their priorities in the EVPN address family.
By default, routes are preferentially selected based on BGP route selection rules in the EVPN address family.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 address for a BGP EVPN peer. |
The value is in dotted decimal notation. |
disable |
Disables a device from preferentially selecting routes based on their high priority in the EVPN address family. |
- |
Usage Guidelines
Usage Scenario
The EVPN address family supports the coexistence of IPv4 and IPv6 peers. A device may learn routes with the same prefix from IPv4 and IPv6 peers. To control the route priority, run the route-priority command. This function takes effect only locally and is not transmitted through packets.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 high-priority
peer high-priority (BGP-EVPN address family view) (group)
Function
The peer high-priority command enables a device to preferentially select routes based on their priorities in the EVPN address family.
The undo peer high-priority command disables a device from preferentially selecting routes based on their priorities in the EVPN address family.
By default, routes are preferentially selected based on BGP route selection rules in the EVPN address family.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
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. |
Usage Guidelines
Usage Scenario
The EVPN address family supports the coexistence of IPv4 and IPv6 peers. A device may learn routes with the same prefix from IPv4 and IPv6 peers. To control the route priority, run the route-priority command. This function takes effect only locally and is not transmitted through packets.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.1 as-number 100 [HUAWEI-bgp] group g1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer g1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.1 group g1 [HUAWEI-bgp-af-evpn] peer g1 high-priority
peer high-priority (BGP-EVPN address family view) (ipv6)
Function
The peer high-priority command enables a device to preferentially select routes based on their priorities in the EVPN address family.
The undo peer high-priority command disables a device from preferentially selecting routes based on their priorities in the EVPN address family.
By default, routes are preferentially selected based on BGP route selection rules in the EVPN address family.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies an IPv6 address for a BGP EVPN peer. |
The address is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
disable |
Disables a device from preferentially selecting routes based on their high priority in the EVPN address family. |
- |
Usage Guidelines
Usage Scenario
The EVPN address family supports the coexistence of IPv4 and IPv6 peers. A device may learn routes with the same prefix from IPv4 and IPv6 peers. To control the route priority, run the route-priority command. This function takes effect only locally and is not transmitted through packets.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:DB8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 high-priority
peer import reoriginate (BGP-EVPN address family view)
Function
The peer import reoriginate command enables a device to add a regeneration flag to the routes received from BGP EVPN peers.
The undo peer import reoriginate command restores the default configuration.
By default, a device does not add a regeneration flag to the routes received from BGP EVPN peers.
Format
peer peerIpv4Addr import reoriginate
undo peer peerIpv4Addr import reoriginate
peer peerIpv6Addr import reoriginate
undo peer peerIpv6Addr import reoriginate
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a BGP EVPN peer. |
The value is in dotted decimal notation. |
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. This parameter applies only to the BGP-EVPN address family view. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
Data Center Interconnect (DCI) refers to the definition of various solutions for interconnecting data centers. In a DCI solution, a DCI-PE re-originates received EVPN routes before sending them to peers. By default, the function of re-originating labeled routes is disabled. That is, a DCI-PE does not re-encapsulate the routes received from peers. To enable a DCI-PE to re-encapsulate EVPN routes, run the peer import reoriginate command to enable the function of re-originating labeled routes.
You can query the BGP VPN routing table to check whether a route carries the REGEN capability flag in its attributes. If the route carries this flag, it can be re-originated and re-advertised to the BGP public network.Prerequisites
The device has been enabled to exchange routing information with the specified peer using the peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 import reoriginate
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 import reoriginate
peer import reoriginate (BGP-EVPN address family view) (group)
Function
The peer import reoriginate command enables a device to add a regeneration flag to the routes received from BGP EVPN peer group.
The undo peer import reoriginate command restores the default configuration.
By default, a device does not add a regeneration flag to the routes received from BGP EVPN peers.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
Usage Guidelines
Usage Scenario
In the data center interconnect (DCI) solution, DCI-PE adds the regeneration flag to the received EVPN routes before sending the routes to the peer. By default, the function to add the regeneration flag to the routes received from the peer is disabled. Specifically, DCI-PE does not re-encapsulate the routes received from the peer. Therefore, to allow DCI-PE to re-encapsulate the EVPN routes, run the peer import reoriginate command to enable the function to add the regeneration flag to the routes received from the peer.
Prerequisites
The peer enable command has been run to enable the device to exchange routing information with a specified peer group.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 import reoriginate
peer mac-limit (BGP-EVPN address family view)
Function
The peer mac-limit command configures the maximum number of MAC advertisement routes allowed to be received from a peer.
The undo peer mac-limit command restores the default configuration.
By default, the number of MAC advertisement routes allowed to be received from a peer is not limited.
Format
peer ipv4-address mac-limit number [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
undo peer ipv4-address mac-limit
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a peer. |
The value is in dotted decimal notation. |
number |
Specifies the maximum number of MAC advertisement routes allowed to be received from a peer. |
The value is an integer ranging from 1 to 4294967295. |
percentage |
Specifies a percentage of MAC advertisement routes for the device to generate an alarm. If the number of MAC advertisement routes received from a peer exceeds (number*percentage)/100, the device generates an alarm. |
The value is an integer ranging from 1 to 100. The default value is 75. |
alert-only |
Indicates that an alarm will be generated and additional routes will be denied if the maximum number of routes allowed have been received. This parameter is recommended to prevent a peer disconnection when the number of routes received by the device exceeds the maximum limit. |
- |
idle-forever |
Indicates that a connection that is interrupted after the maximum number of routes allowed have been received cannot be automatically re-established. |
- |
idle-timeout times |
Specifies a timer for re-establishing a connection if the connection is interrupted after the maximum number of routes allowed have been received. Before the timer expires, the system does not re-establish a connection. |
The value is an integer ranging from 1 to 1200, in minutes. |
Usage Guidelines
Usage Scenario
If an EVPN instance may import many invalid MAC advertisement routes from peers and these routes occupy a large proportion of the total number of MAC advertisement routes, run the peer mac-limit command to configure the maximum number of MAC advertisement routes allowed to be received from each peer. If the number of received MAC advertisement routes exceeds the specified maximum number, the system displays an alarm, instructing users to check the validity of the MAC advertisement routes received in the EVPN instance.
Configuration Impact
After this command is run, excess route prefixes of the EVPN instance may be discarded.
If the undo peer mac-limit command is run after the received MAC advertisement routes exceed the specified maximum number, the system receives route prefixes from PEs again to construct the BGP EVPN routing table. If a peer relationship between two devices is in the Established state, the following situations occur:- If the number of routes received by the device exceeds the maximum limit after you run the peer mac-limit command for the first time or run the command to reduce the maximum limit: If you specified alert-only in the command, the device does not disconnect its BGP peer. The received routes are not removed, and no additional routes will be accepted. If you specified idle-forever in the command, the device disconnects its BGP peer. To re-establish the connection, run the reset bgp command. If you specified idle-timeout in the command, the device disconnects its BGP peer and re-establishes its BGP peer relationship automatically after the timeout timer expires. To re-establish the connection before the timeout timer expires, run the reset bgp command.
- If the upper limit set on the device is increased to be greater than the number of received routes, the device sends Refresh packets to receive routes again. If the device does not support the route-refresh capability, the device needs to re-establish the connection with its peer.
- If the upper limit set on the device is reduced but is still greater than the number of received routes, only configuration parameters need to be modified. Assume that none of alert-only, idle-forever, and idle-timeout is configured. If the number of routes exceeds the upper limit, an alarm is generated and recorded in the log. Then, the peer relationship is disconnected. The devices try to re-establish the peer relationship after 30 seconds.
Precautions
The peer mac-limit and peer route-limit commands are mutually exclusive.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2.2.2.2 enable [HUAWEI-bgp-af-evpn] peer 2.2.2.2 mac-limit 1000 alert-only
peer mac-limit (BGP-EVPN address family view) (group)
Function
The peer mac-limit command configures the maximum number of MAC advertisement routes allowed to be received from a peer group.
The undo peer mac-limit command restores the default configuration.
By default, the number of MAC advertisement routes allowed to be received from a peer group is not limited.
Format
peer group-name mac-limit number [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
undo peer group-name mac-limit
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. |
number |
Specifies the maximum number of MAC advertisement routes allowed to be received from a peer. |
The value is an integer that ranges from 1 to 4294967295. |
percentage |
Specifies a percentage of MAC advertisement routes for the device to generate an alarm. If the number of MAC advertisement routes received from a peer exceeds (number*percentage)/100, the device generates an alarm. |
The value is an integer ranging from 1 to 100. The default value is 75. |
alert-only |
Indicates that an alarm will be generated and additional routes will be denied if the maximum number of routes allowed have been received. This parameter is recommended to prevent a peer disconnection when the number of routes received by the device exceeds the maximum limit. |
- |
idle-forever |
Indicates that a connection that is interrupted after the maximum number of routes allowed have been received cannot be automatically re-established. |
- |
idle-timeout times |
Specifies a timer for re-establishing a connection if the connection is interrupted after the maximum number of routes allowed have been received. Before the timer expires, the system does not re-establish a connection. |
The value is an integer ranging from 1 to 1200, in minutes. |
Usage Guidelines
Usage Scenario
If an EVPN instance may import many invalid MAC advertisement routes from peers and these routes occupy a large proportion of the total number of MAC advertisement routes, run the peer mac-limit command to configure the maximum number of MAC advertisement routes allowed to be received from each peer. If the number of received MAC advertisement routes exceeds the specified maximum number, the system displays an alarm, instructing users to check the validity of the MAC advertisement routes received in the EVPN instance.
Configuration Impact
After this command is run, excess route prefixes of the EVPN instance may be discarded.
If the undo peer mac-limit command is run after the received MAC advertisement routes exceed the specified maximum number, the system receives route prefixes from PEs again to construct the BGP EVPN routing table. If a peer relationship between two devices is in the Established state, the following situations occur:- If the number of routes received by the device exceeds the maximum limit after you run the peer mac-limit command for the first time or run the command to reduce the maximum limit: If you specified alert-only in the command, the device does not disconnect its BGP peer. The received routes are not removed, and no additional routes will be accepted. If you specified idle-forever in the command, the device disconnects its BGP peer. To re-establish the connection, run the reset bgp command. If you specified idle-timeout in the command, the device disconnects its BGP peer and re-establishes its BGP peer relationship automatically after the timeout timer expires. To re-establish the connection before the timeout timer expires, run the reset bgp command.
- If the upper limit set on the device is increased to be greater than the number of received routes, the device sends Refresh packets to receive routes again. If the device does not support the route-refresh capability, the device needs to re-establish the connection with its peer.
- If the upper limit set on the device is reduced but is still greater than the number of received routes, only configuration parameters need to be modified. Assume that none of alert-only, idle-forever, and idle-timeout is configured. If the number of routes exceeds the upper limit, an alarm is generated and recorded in the log. Then, the peer relationship is disconnected. The devices try to re-establish the peer relationship after 30 seconds.
Precautions
The peer mac-limit and peer route-limit commands are mutually exclusive.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2.2.2.2 as-number 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 2.2.2.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 mac-limit 1000 alert-only
peer mac-limit (BGP-EVPN address family view) (ipv6)
Function
The peer mac-limit command configures the maximum number of MAC advertisement routes allowed to be received from a peer.
The undo peer mac-limit command restores the default configuration.
By default, the number of MAC advertisement routes allowed to be received from a peer is not limited.
Format
peer peerIpv6Addr mac-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
undo peer peerIpv6Addr mac-limit
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
limit |
Specifies the maximum number of MAC advertisement routes allowed to be received from a peer. |
The value is an integer ranging from 1 to 4294967295. |
percentage |
Specifies a percentage of MAC advertisement routes for the device to generate an alarm. If the number of MAC advertisement routes received from a peer exceeds (number*percentage)/100, the device generates an alarm. |
The value is an integer ranging from 1 to 100. The default value is 75. |
alert-only |
Indicates that an alarm will be generated and additional routes will be denied if the maximum number of routes allowed have been received. This parameter is recommended to prevent a peer disconnection when the number of routes received by the device exceeds the maximum limit. |
- |
idle-forever |
Indicates that a connection that is interrupted after the maximum number of routes allowed have been received cannot be automatically re-established. |
- |
idle-timeout times |
Specifies a timer for re-establishing a connection if the connection is interrupted after the maximum number of routes allowed have been received. Before the timer expires, the system does not re-establish a connection. |
The value is an integer ranging from 1 to 1200, in minutes. |
Usage Guidelines
Usage Scenario
If an EVPN instance may import many invalid MAC advertisement routes from peers and these routes occupy a large proportion of the total number of MAC advertisement routes, run the peer mac-limit command to configure the maximum number of MAC advertisement routes allowed to be received from each peer. If the number of received MAC advertisement routes exceeds the specified maximum number, the system displays an alarm, instructing users to check the validity of the MAC advertisement routes received in the EVPN instance.
Configuration Impact
After this command is run, excess route prefixes of the EVPN instance may be discarded.
If the undo peer mac-limit command is run after the received MAC advertisement routes exceed the specified maximum number, the system receives route prefixes from PEs again to construct the BGP EVPN routing table. If a peer relationship between two devices is in the Established state, the following situations occur:- If the number of routes received by the device exceeds the maximum limit after you run the peer mac-limit command for the first time or run the command to reduce the maximum limit: If you specified alert-only in the command, the device does not disconnect its BGP peer. The received routes are not removed, and no additional routes will be accepted. If you specified idle-forever in the command, the device disconnects its BGP peer. To re-establish the connection, run the reset bgp command. If you specified idle-timeout in the command, the device disconnects its BGP peer and re-establishes its BGP peer relationship automatically after the timeout timer expires. To re-establish the connection before the timeout timer expires, run the reset bgp command.
- If the upper limit set on the device is increased to be greater than the number of received routes, the device sends Refresh packets to receive routes again. If the device does not support the route-refresh capability, the device needs to re-establish the connection with its peer.
- If the upper limit set on the device is reduced but is still greater than the number of received routes, only configuration parameters need to be modified. Assume that none of alert-only, idle-forever, and idle-timeout is configured. If the number of routes exceeds the upper limit, an alarm is generated and recorded in the log. Then, the peer relationship is disconnected. The devices try to re-establish the peer relationship after 30 seconds.
Precautions
The peer mac-limit and peer route-limit commands are mutually exclusive.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:DB8:2::2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:DB8:2::2 enable [HUAWEI-bgp-af-evpn] peer 2001:DB8:2::2 mac-limit 1000 alert-only
peer next-hop-invariable (BGP-EVPN address family view)
Function
The peer next-hop-invariable command enables a BGP EVPN speaker to keep the next hops of routes unchanged when the speaker advertises these routes to EBGP EVPN peers and to apply the original next hops of locally imported routes when the speaker advertises these routes to IBGP EVPN peers.
The undo peer next-hop-invariable command restores the default configuration.
By default, the function of keeping the next hops of routes unchanged is not enabled.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
By default:
- A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish EBGP EVPN peer relationships before advertising these routes to EBGP EVPN peers.
- A BGP EVPN speaker changes the next hops of routes imported from EBGP EVPN to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers.
- An RR does not change the next hops of routes imported from IBGP EVPN when advertising these routes to IBGP EVPN peers.
- A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers. In an inter-AS scenario where an EVPN Route Reflector (RR) is used, the peer next-hop-invariable command needs to be run on the RR to prevent the RR from modifying the Next_Hops of routes before advertising the routes to EBGP peers. This ensures that the remote PE recurses routes to the LSP destined for the local PE during traffic transmission. In an EVPN VXLAN scenario, the peer next-hop-invariable command must be run if a device needs to advertise routes received from an EBGP EVPN peer to IBGP EVPN peers or advertise routes to EBGP EVPN peers.
Prerequisites
The specified peer has been enabled in the BGP-EVPN address family view.
Precautions
If both the peer next-hop-invariable and peer next-hop-local commands are run, the latest configuration overrides the previous one.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.9 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.9 next-hop-invariable
peer next-hop-invariable (BGP-EVPN address family view) (group)
Function
The peer next-hop-invariable command enables a BGP EVPN speaker to keep the next hops of routes unchanged when the speaker advertises these routes to EBGP EVPN peers and to apply the original next hops of locally imported routes when the speaker advertises these routes to IBGP EVPN peers.
The undo peer next-hop-invariable command restores the default configuration.
By default, the function of keeping the next hops of routes unchanged is not enabled.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
Usage Guidelines
Usage Scenario
By default:
- A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish EBGP EVPN peer relationships before advertising these routes to EBGP EVPN peers.
- A BGP EVPN speaker changes the next hops of routes imported from EBGP EVPN to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers.
- An RR does not change the next hops of routes imported from IBGP EVPN when advertising these routes to IBGP EVPN peers.
- A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers. In an EVPN VXLAN scenario, the peer next-hop-invariable command must be run if a device needs to advertise routes received from an EBGP EVPN peer to IBGP EVPN peers or advertise routes to EBGP EVPN peers.
Prerequisites
The specified peer group has been enabled in the BGP-EVPN address family view.
Precautions
If both the peer next-hop-invariable and peer next-hop-local commands are run, the latest configuration overrides the previous one.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.1 as-number 200 [HUAWEI-bgp] group dcn external [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer dcn enable [HUAWEI-bgp-af-evpn] peer 10.1.1.1 group dcn [HUAWEI-bgp-af-evpn] peer dcn next-hop-invariable
peer next-hop-invariable (BGP-EVPN address family view) (IPv6)
Function
The peer next-hop-invariable command enables a BGP EVPN speaker to keep the next hops of routes unchanged when the speaker advertises these routes to EBGP EVPN peers and to apply the original next hops of locally imported routes when the speaker advertises these routes to IBGP EVPN peers.
The undo peer next-hop-invariable command restores the default configuration.
By default, the function of keeping the next hops of routes unchanged is not enabled.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
By default:
A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish EBGP EVPN peer relationships before advertising these routes to EBGP EVPN peers. A BGP EVPN speaker changes the next hops of routes imported from EBGP EVPN to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers. An RR does not change the next hops of routes imported from IBGP EVPN when advertising these routes to IBGP EVPN peers. A BGP EVPN speaker changes the next hops of routes to the interface that it uses to establish IBGP EVPN peer relationships before advertising these routes to IBGP EVPN peers.In an inter-AS scenario where an EVPN Route Reflector (RR) is used, the peer next-hop-invariable command needs to be run on the RR to prevent the RR from modifying the Next_Hops of routes before advertising the routes to EBGP peers. This ensures that the remote PE recurses routes to the LSP destined for the local PE during traffic transmission.
In a VXLAN scenario, when an EBGP EVPN peer relationship is established between VTEPs, to ensure that EVPN routes can be correctly sent, run the peer next-hop-invariable command on the VTEPs.Prerequisites
The specified peer has been enabled in the BGP-EVPN address family view.
Precautions
If both the peer next-hop-invariable and peer next-hop-local commands are run, the latest configuration overrides the previous one.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 next-hop-invariable
peer peer-as-check (BGP-EVPN address family view)(IPv6)
Function
The peer peer-as-check command prevents the routes received from an EBGP peer from being broadcast to other peers with the same AS number as the EBGP peer.
The undo peer peer-as-check command cancels the configuration.
By default, the routes received from an EBGP peer are broadcast to other EBGP peers in the same AS.
Format
peer peerIpv6Addr peer-as-check
peer peerIpv6Addr peer-as-check disable
undo peer peerIpv6Addr peer-as-check
undo peer peerIpv6Addr peer-as-check disable
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
disable |
Disables the function. |
- |
Usage Guidelines
Usage Scenario
By default, after receiving a route from an EBGP peer (for example, in AS 200), the local device (for example, in AS 100) advertises the route to all EBGP peers in AS 200. After the peer peer-as-check command is run on a device, the device does not advertise routes received from an EBGP peer to other EBGP peers in the same AS as this EBGP peer. This reduces BGP memory and CPU consumption and speeds up route convergence in case of route flapping.
Configuration Impact
After this command is run, the number of BGP update peer-groups on the device is affected. If the AS numbers of BGP peers configured with this function are different, these BGP peers cannot be added to the same BGP update peer-group.
Precautions
This command applies only to EBGP peers.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 peer-as-check
peer peer-as-check(BGP-EVPN address family view)
Function
The peer peer-as-check command prevents the routes received from an EBGP peer from being broadcast to other peers with the same AS number as the EBGP peer.
The undo peer peer-as-check command cancels the configuration.
By default, the routes received from an EBGP peer are broadcast to other EBGP peers in the same AS.
Format
peer peerIpv4Addr peer-as-check
peer peerIpv4Addr peer-as-check disable
undo peer peerIpv4Addr peer-as-check
undo peer peerIpv4Addr peer-as-check disable
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
disable |
Disables the function. |
- |
Usage Guidelines
Usage Scenario
By default, after receiving a route from an EBGP peer (for example, in AS 200), the local device (for example, in AS 100) advertises the route to all EBGP peers in AS 200. After the peer peer-as-check command is run on a device, the device does not advertise routes received from an EBGP peer to other EBGP peers in the same AS as this EBGP peer. This reduces BGP memory and CPU consumption and speeds up route convergence in case of route flapping.
Prerequisites
Run the evpn-overlay enable command to enable EVPN as the VXLAN control plane.
Configuration Impact
After this command is run, the number of BGP update peer-groups on the device is affected. If the AS numbers of BGP peers configured with this function are different, these BGP peers cannot be added to the same BGP update peer-group.
Precautions
This command applies only to EBGP peers.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.1 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.1 peer-as-check
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 instance a [HUAWEI-bgp-instance-a] peer 10.1.1.1 enable [HUAWEI-bgp-instance-a] l2vpn-family evpn [HUAWEI-bgp-instance-a-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-instance-a-evpn] peer 10.1.1.1 peer-as-check
peer peer-as-check(BGP-EVPN address family view)(group)
Function
The peer peer-as-check command prevents the routes received from an EBGP peer from being broadcast to other peers with the same AS number as the EBGP peer.
The undo peer peer-as-check command cancels the configuration.
By default, the routes received from an EBGP peer are broadcast to other EBGP peers in the same AS.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP peer group. |
The value is a string of 1 to 47 case-sensitive characters and cannot contain spaces. If the character string is quoted by double quotation marks, the character string can contain spaces. |
Usage Guidelines
Usage Scenario
By default, after receiving a route from an EBGP peer (for example, AS 200), the local device (for example, AS 100) advertises the route to all EBGP peers in AS 200. After the peer peer-as-check command is run on a device, the device does not advertise routes received from an EBGP peer to other EBGP peers in the same AS as this EBGP peer. This reduces BGP memory and CPU consumption and speeds up route convergence in case of route flapping.
Prerequisites
Run the evpn-overlay enable command to enable EVPN as the VXLAN control plane.
Configuration Impact
After this command is run, the number of BGP update peer-groups on the device is affected. If the AS numbers of BGP peers configured with this function are different, these BGP peers cannot be added to the same BGP update peer-group.
Precautions
This command applies only to EBGP peers.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 instance a [HUAWEI-bgp-instance-a] group a external [HUAWEI-bgp-instance-a] l2vpn-family evpn [HUAWEI-bgp-instance-a-evpn] peer a enable [HUAWEI-bgp-instance-a-evpn] peer a peer-as-check
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] group a external [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer a enable [HUAWEI-bgp-af-evpn] peer a peer-as-check
peer preferred-value (BGP-EVPN address family view) (group)
Function
The peer preferred-value command sets a preferred value for the routes that a BGP device learns from its peer group.
The undo peer preferred-value command deletes the preferred value set for the routes that a BGP device learns from its peer group.
By default, the preferred value of the routes learned from other BGP peer groups is 0.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
preferredvalue |
Specifies the preferred value for routes. |
The value is an integer ranging from 0 to 65535. |
Usage Guidelines
Usage Scenario
After a preferred value is configured for a peer group, all the routes learned from the peer group have the preferred value. If multiple routes with the same prefix are available, the route with the largest preferred value is preferred.
Prerequisites
A BGP peer group must be configured before the preferred value is assigned to the peer group. If you run this command for a peer group that does not exist, the system displays a message indicating that the peer group does not exist.
Configuration Impact
If a preferred value is set for the routes that a BGP device learns from a peer group, all members of the peer group inherit the configuration.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] peer 1.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 preferred-value 50
peer preferred-value (BGP-EVPN address family view)(IPv4)
Function
The peer preferred-value command sets a preferred value for the routes that a BGP device learns from its peer.
The undo peer preferred-value command deletes the preferred value set for the routes that a BGP device learns from its peer.
By default, the preferred value of a route learned from a BGP peer is 0.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
preferredvalue |
Specifies the preferred value of the routes that a BGP device learns from its peer. |
The value is an integer ranging from 0 to 65535. |
Usage Guidelines
Usage Scenario
After a preferred value is configured for a peer, all the routes learned from the peer have the preferred value. If multiple routes with the same prefix are available, the route with the largest preferred value is preferred.
Prerequisites
A BGP peer has been configured. If the peer preferred-value command is used but no BGP peer exists, a message is displayed, indicating that the peer does not exist.
Configuration Impact
If a preferred value is set for the routes that a device learns from a peer group, all members of the peer group inherit the configuration.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.2 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.2 preferred-value 50
peer reflect-client (BGP-EVPN address family view) (group)
Function
The peer reflect-client command configures the local router as the route reflector and the peer group as the client of the route reflector.
The undo peer reflect-client command cancels the configuration.
By default, the route reflector and its client are not configured.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
Usage Guidelines
Usage Scenario
Full-meshed connections need to be established between IBGP peers to ensure the connectivity between the IBGP peers. If there are n devices in an AS, n x (n – 1)/2 IBGP connections need to be established. When there are a lot of IBGP peers, network resources and CPU resources are greatly consumed. To solve this problem, route reflection is used.
In an AS, one device functions as an RR, and the other devices function as clients. The clients establish IBGP connections with the RR. The RR and its clients form a cluster. The RR reflects routes among the clients, and therefore the clients do not need to establish any BGP connection. Assume that an AS has n devices. If one of the devices functions as an RR, and other devices function as clients, the number of IBGP connections to be established is n-1. This means that network and CPU resource consumption is greatly reduced. An RR is easy to configure, because it needs to be configured only on the device that functions as a reflector and clients do not need to know that they are clients.Configuration Impact
If the peer reflect-client command is run multiple times in the same view, the latest configuration overwrites the previous one.
The device where the peer reflect-client command is run serves as the RR and a specified peer group serves as the client of the RR.Precautions
The peer reflect-client command applies only to IBGP peer groups.
The RR information configured in an address family is valid only in this address family and cannot be inherited by other address families. Therefore, you are advised to configure RR information in a specific address family. If this command is run on a specified peer and the peer advertise best-external command is run in a specified peer group, the peer cannot inherit the function of the peer advertise best-external command when the peer is added to the peer group.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] peer 1.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 reflect-client
peer reflect-client (BGP-EVPN address family view) (IPv6)
Function
The peer reflect-client command configures the local router as the route reflector and the peer or peer group as the client of the route reflector.
The undo peer reflect-client command cancels the configuration.
By default, the route reflector and its client are not configured.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
Full-meshed connections need to be established between IBGP peers to ensure the connectivity between the IBGP peers. If there are n devices in an AS, n x (n – 1)/2 IBGP connections need to be established. When there are a lot of IBGP peers, network resources and CPU resources are greatly consumed. To solve this problem, route reflection is used.
In an AS, one device functions as an RR, and the other devices function as clients. The clients establish IBGP connections with the RR. The RR and its clients form a cluster. The RR reflects routes among the clients, and therefore the clients do not need to establish any BGP connection. Assume that an AS has n devices. If one of the devices functions as an RR, and other devices function as clients, the number of IBGP connections to be established is n-1. This means that network and CPU resource consumption is greatly reduced. An RR is easy to configure, because it needs to be configured only on the device that functions as a reflector and clients do not need to know that they are clients.Configuration Impact
If the peer reflect-client command is run multiple times in the same view, the latest configuration overwrites the previous one.
The device where the peer reflect-client command is run serves as the RR and a specified peer serves as the client of the RR.Precautions
The peer reflect-client command applies only to IBGP peers.
The RR information configured in an address family is valid only in this address family and cannot be inherited by other address families. Therefore, you are advised to configure RR information in a specific address family. If this command is run on a specified peer and the peer advertise best-external command is run in a specified peer group, the peer cannot inherit the function of the peer advertise best-external command when the peer is added to the peer group.peer reflect-client (BGP-EVPN address family view)(IPv4)
Function
The peer reflect-client command configures the local router as the route reflector and the peer as the client of the route reflector.
The undo peer reflect-client command cancels the configuration.
By default, the route reflector and its client are not configured.
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
Full-meshed connections need to be established between IBGP peers to ensure the connectivity between the IBGP peers. If there are n devices in an AS, n x (n – 1)/2 IBGP connections need to be established. When there are a lot of IBGP peers, network resources and CPU resources are greatly consumed. To solve this problem, route reflection is used.
In an AS, one device functions as an RR, and the other devices function as clients. The clients establish IBGP connections with the RR. The RR and its clients form a cluster. The RR reflects routes among the clients, and therefore the clients do not need to establish any BGP connection. Assume that an AS has n devices. If one of the devices functions as an RR, and other devices function as clients, the number of IBGP connections to be established is n-1. This means that network and CPU resource consumption is greatly reduced. An RR is easy to configure, because it needs to be configured only on the device that functions as a reflector and clients do not need to know that they are clients.Configuration Impact
If the peer reflect-client command is run multiple times in the same view, the latest configuration overwrites the previous one.
The device where the peer reflect-client command is run serves as the RR and a specified peer serves as the client of the RR.Precautions
The peer reflect-client command applies only to IBGP peers.
The RR information configured in an address family is valid only in this address family and cannot be inherited by other address families. Therefore, you are advised to configure RR information in a specific address family. If this command is run on a specified peer and the peer advertise best-external command is run in a specified peer group, the peer cannot inherit the function of the peer advertise best-external command when the peer is added to the peer group.peer route-limit (BGP-EVPN address family view)
Function
The peer route-limit command sets the maximum number of routes that can be received from a peer.
The undo peer route-limit command restores the default setting.
By default, there is no limit on the number of routes that can be received from a peer.
Format
peer peerIpv4Addr route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
peer peerIpv6Addr route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
undo peer peerIpv4Addr route-limit
undo peer peerIpv6Addr route-limit
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
limit |
Specifies the maximum number of routes that can be accepted from a peer. |
The value is an integer ranging from 1 to 4294967295. |
percentage |
Specifies the proportion threshold of the number of received routes to limit.
|
The value is an integer ranging from 1 to 100. The default value is 75. |
alert-only |
Enables the device to send a threshold alarm or limit-exceeding alarm and stop accepting excess routes if accept-prefix is not specified and the percentage of the number of received routes to the maximum number of routes that can be accepted reaches 100%. In this case, the peer relationship is not disconnected. |
- |
idle-forever |
If the percentage of the number of received routes to the maximum number of routes that can be received is greater than percentage, the device reports an alarm. After the number of received routes exceeds the threshold, the peer relationship is disconnected and will not be automatically re-established. |
- |
idle-timeout times |
Enables the device to send an alarm if the proportion of the number of received routes to limit reaches percentage. After the number of received routes exceeds the limit, the connection is interrupted, and the device does not automatically re-establish the connection until the timer expires. |
The value is an integer ranging from 1 to 1200, in minutes. |
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
The peer route-limit command is used to set the maximum number of routes that a BGP device is allowed to receive from its peer. This provides a mechanism for controlling the routes received from peers in addition to distribution lists, filtering lists, and route mappings.
Configuration Impact
If the peer route-limit command is run for a peer group, the peers of the peer group inherit the configuration.
When the peer relationship between peers is Established:- If the peer route-limit command is run for the first time or the upper limit is reduced and the number of routes received by the device exceeds the upper limit:
- If alert-only is specified in the command, the peer relationship is not interrupted and the received routes are not withdrawn, and for the new routes that are received, the system performs limit-exceeding processing.
- If idle-forever is specified in the command, the local device terminates the connection with its peer. To reestablish the connection, run the reset bgp command.
- If idle-timeout is specified in the command, the local device terminates the connection with its peer and starts the timer for automatic connection re-establishment. To re-establish the connection before the timer expires, you can run the reset bgp command.
- If the upper limit is increased to a value greater than the number of received routes, the device sends Refresh messages to receive routes again. If the device does not support the route-refresh capability, the device reestablishes the connection.
- If the upper limit is reduced but is still greater than the number of received routes, the device only changes the configuration parameter. If alert-only, idle-forever, or idle-timeout is not configured and the percentage of the number of received routes to the maximum number of routes that can be accepted is greater than the specified percentage, the device sends a threshold alarm. When the number of received routes exceeds the limit, the peer relationship is interrupted. After 30 seconds, the system automatically attempts to reestablish the peer relationship.
- If the upper limit remains unchanged, the device only changes the configuration parameter.
- If accept-prefix is specified, the device continues to accept excess routes in the alert-only scenario, and all received routes are valid. If accept-prefix is not specified in the alert-only scenario, the device only sends the threshold alarm or limit-exceeding alarm and does not accept excess routes. In this case, the peer relationship is not disconnected.
Precautions
If a specified peer has this capability and the peer relationship is interrupted because the number of routes exceeds the upper limit, the same peer relationship in all address families is affected, and the peer relationship is re-established.
Adding, modifying, or deleting the peer route-limit configuration of a BGP peer may cause the BGP peer to learn a large number of routes. The peer route-limit and peer mac-limit commands are mutually exclusive.peer route-limit (BGP-EVPN address family view) (group)
Function
The peer route-limit command sets the maximum number of routes that can be received from a peer group.
The undo peer route-limit command restores the default setting.
By default, there is no limit on the number of routes that can be received from a peer group.
Format
peer peerGroupName route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout times ]
undo peer peerGroupName route-limit
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
limit |
Specifies the maximum number of routes that can be accepted from a peer. |
The value is an integer ranging from 1 to 4294967295. |
percentage |
Specifies the proportion threshold of the number of received routes to limit.
|
The value is an integer ranging from 1 to 100. The default value is 75. |
alert-only |
Enables the device to send a threshold alarm or limit-exceeding alarm and stop accepting excess routes if accept-prefix is not specified and the percentage of the number of received routes to the maximum number of routes that can be accepted reaches 100%. In this case, the peer relationship is not disconnected. |
- |
idle-forever |
If the percentage of the number of received routes to the maximum number of routes that can be received is greater than percentage, the device reports an alarm. After the number of received routes exceeds the threshold, the peer relationship is disconnected and will not be automatically re-established. |
- |
idle-timeout times |
Enables the device to send an alarm if the proportion of the number of received routes to limit reaches percentage. After the number of received routes exceeds the limit, the connection is interrupted, and the device does not automatically re-establish the connection until the timer expires. |
The value is an integer ranging from 1 to 1200, in minutes. |
Usage Guidelines
Usage Scenario
The peer route-limit command is used to set the maximum number of routes that a BGP device is allowed to receive from its peer group. This provides a mechanism for controlling the routes received from peer group in addition to distribution lists, filtering lists, and route mappings.
Configuration Impact
If the peer route-limit command is run for a peer group, the peers of the peer group inherit the configuration.
When the peer relationship between peers is Established:- If the peer route-limit command is run for the first time or the upper limit is reduced and the number of routes received by the device exceeds the upper limit:
- If alert-only is specified in the command, the peer relationship is not interrupted and the received routes are not withdrawn, and for the new routes that are received, the system performs limit-exceeding processing.
- If idle-forever is specified in the command, the local device terminates the connection with its peer. To reestablish the connection, run the reset bgp command.
- If idle-timeout is specified in the command, the local device terminates the connection with its peer and starts the timer for automatic connection re-establishment. To re-establish the connection before the timer expires, you can run the reset bgp command.
- If the upper limit is increased to a value greater than the number of received routes, the device sends Refresh messages to receive routes again. If the device does not support the route-refresh capability, the device reestablishes the connection.
- If the upper limit is reduced but is still greater than the number of received routes, the device only changes the configuration parameter. If alert-only, idle-forever, or idle-timeout is not configured and the percentage of the number of received routes to the maximum number of routes that can be accepted is greater than the specified percentage, the device sends a threshold alarm. When the number of received routes exceeds the limit, the peer relationship is interrupted. After 30 seconds, the system automatically attempts to reestablish the peer relationship.
- If the upper limit remains unchanged, the device only changes the configuration parameter.
- If accept-prefix is specified, the device continues to accept excess routes in the alert-only scenario, and all received routes are valid. If accept-prefix is not specified in the alert-only scenario, the device only sends the threshold alarm or limit-exceeding alarm and does not accept excess routes. In this case, the peer relationship is not disconnected.
Precautions
If a specified peer has this capability and the peer relationship is interrupted because the number of routes exceeds the upper limit, the same peer relationship in all address families is affected, and the peer relationship is re-established.
Adding, modifying, or deleting the peer route-limit configuration of a BGP peer may cause the BGP peer to learn a large number of routes. The peer route-limit and peer mac-limit commands are mutually exclusive.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] peer 1.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 route-limit 10000
peer route-policy export (BGP-EVPN address family view)
Function
The peer route-policy export command specifies a route-policy for filtering routes to be advertised to a peer.
The undo peer route-policy export command deletes a specified route-policy.
By default, no route-policy is configured for filtering routes to be advertised to a peer.
Format
peer peerIpv4Addr route-policy route-policy-name export
undo peer peerIpv4Addr route-policy route-policy-name export
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
route-policy-name |
Specifies the name of a route-policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy export command is used to apply a Route-Policy to a peer group so that the routes advertised to peer group can be controlled. To be specific, only the necessary routes are advertised to the peer group. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If a routing policy needs to be specified in the command, run the route-policy command to create the routing policy first.
Configuration Impact
If both a peer group and a peer are configured with a route-policy, the configuration on the peer takes precedence. If a peer group is configured with a route-policy but peers in the group are not configured with their own ones, the peers inherit the configuration of the peer group. If the route-policy configuration of a peer group is the same as that of a peer in the group, the configuration is displayed in the configuration file only for the peer group.
Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.
When route-policy route-policy-nameis configured, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter. The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 route-policy test-policy export
peer route-policy export (BGP-EVPN address family view) (group)
Function
The peer route-policy export command specifies a route-policy for filtering routes to be advertised to a peer group.
The undo peer route-policy export command deletes a specified route-policy.
By default, no route-policy is configured for filtering routes to be advertised to a peer group.
Format
peer peerGroupName route-policy route-policy-name export
undo peer peerGroupName route-policy route-policy-name export
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
route-policy-name |
Specifies the name of a route-policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy export command is used to apply a Route-Policy to a peer group so that the routes advertised to peer group can be controlled. To be specific, only the necessary routes are advertised to the peer group. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If a routing policy needs to be specified in the command, run the route-policy command to create the routing policy first.
Configuration Impact
If both a peer group and a peer are configured with a route-policy, the configuration on the peer takes precedence. If a peer group is configured with a route-policy but peers in the group are not configured with their own ones, the peers inherit the configuration of the peer group. If the route-policy configuration of a peer group is the same as that of a peer in the group, the configuration is displayed in the configuration file only for the peer group.
Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.
When route-policy route-policy-nameis configured, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter. The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] peer 10.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 route-policy test-policy export
peer route-policy export (BGP-EVPN address family view) (IPv6)
Function
The peer route-policy export command specifies a route-policy for filtering routes to be advertised to a peer.
The undo peer route-policy export command deletes a specified route-policy.
By default, no route-policy is configured for the routes to be advertised to a specified peer.
Format
peer peerIpv6Addr route-policy route-policy-name export
undo peer peerIpv6Addr route-policy route-policy-name export
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
route-policy-name |
Specifies the name of a routing policy. |
The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy export command is used to apply a Route-Policy to a peer group so that the routes advertised to peer group can be controlled. To be specific, only the necessary routes are advertised to the peer group. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If a routing policy needs to be specified in the command, run the route-policy command to create the routing policy first.
Configuration Impact
If both a peer group and a peer are configured with a route-policy, the configuration on the peer takes precedence. If a peer group is configured with a route-policy but peers in the group are not configured with their own ones, the peers inherit the configuration of the peer group. If the route-policy configuration of a peer group is the same as that of a peer in the group, the configuration is displayed in the configuration file only for the peer group.
Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.
When route-policy route-policy-nameis configured, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter. The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 route-policy test-policy export
peer route-policy import (BGP-EVPN address family view) (group)
Function
The peer route-policy import command specifies a route-policy for filtering routes received from a peer group.
The undo peer route-policy import command deletes a specified route-policy.
By default, no route-policy is configured for filtering routes received from a peer group.
Format
peer peerGroupName route-policy route-policy-name import
undo peer peerGroupName route-policy route-policy-name import
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN peer group. |
The value is a string of 1 to 47 case-sensitive characters, spaces not supported. The character string can contain spaces if it is enclosed with double quotation marks ("). |
route-policy-name |
Specifies the name of a route-policy. |
The value is a string of 1 to 200 case-sensitive characters. It cannot contain spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy import command is used to apply a Route-Policy to a peer group so that the routes received from a peer group can be controlled. To be specific, only the necessary routes are received from the peer group. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If the command specifies a route-policy that does not exist, use the route-policy command to create the route-policy.
Configuration Impact
If a route-policy is configured for a peer group, all the peers in the peer group inherit the configuration.
If both this command and the peer route-filter command are run, the latest configuration overrides the previous one. If a BGP peer relationship is established, then an import policy is bound to the peer or the import policy bound to the peer is modified, and the device does not support the Refresh capability, the peer relationship is re-established because the import policy addition or modification causes the peer to resend Refresh messages.Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.
When route-policy route-policy-nameis configured in the BGP multi-instance EVPN address family view, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, ACL for the next hop address of a route, ACL for the next hop address of an IPv6 route, next hop address prefix list of routing information, next hop address prefix list of IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter.
The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority coloring extended community, gateway IP address, gateway IPv6 address, BGP route local preference, next-hop address (IPv4), next-hop address (IPv6), BGP route source, BGP route preferred value, QoS parameters, and EVPN route VN-ID attributes.When route-policy route-policy-nameis configured in the BGP-EVPN address family view, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter.
The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, BGP route preferred value, QoS parameters, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 internal [HUAWEI-bgp] peer 1.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 route-policy test-policy import
peer route-policy import (BGP-EVPN address family view) (IPv6)
Function
The peer route-policy import command specifies a route-policy for filtering routes received from a peer.
The undo peer route-policy import command deletes a specified route-policy.
By default, no route-policy is configured for filtering routes received from a peer.
Format
peer peerIpv6Addr route-policy route-policy-name import
undo peer peerIpv6Addr route-policy route-policy-name import
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The format is X:X:X:X:X:X:X:X. |
route-policy-name |
Specifies the name of a route-policy. |
The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy import command is used to apply a Route-Policy to a peer so that the routes received from the peer can be controlled. To be specific, only the necessary routes are received from the peer. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If a routing policy needs to be specified in the command, run the route-policy command to create the routing policy first.
Configuration Impact
If a BGP peer relationship is established, then an import policy is bound to the peer or the import policy bound to the peer is modified, and the device does not support the Refresh capability, the peer relationship is re-established because the import policy addition or modification causes the peer to resend Refresh messages.
Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.<br /> When route-policy route-policy-nameis configured in the BGP-EVPN address family view, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter.
The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, BGP route preferred value, QoS parameters, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 route-policy test-policy import
peer route-policy import (BGP-EVPN address family view)(IPv4)
Function
The peer route-policy import command specifies a route-policy for filtering routes received from a peer.
The undo peer route-policy import command deletes a specified route-policy.
By default, no route-policy is configured for filtering routes received from a peer.
Format
peer peerIpv4Addr route-policy route-policy-name import
undo peer peerIpv4Addr route-policy route-policy-name import
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
route-policy-name |
Specifies the name of a route-policy. |
The value is a string of 1 to 200 case-sensitive characters. It cannot contain spaces. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
After a route-policy is created, the peer route-policy import command is used to apply a Route-Policy to a peer so that the routes received from the peer can be controlled. To be specific, only the necessary routes are received from the peer. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
Prerequisites
If a routing policy needs to be specified in the command, run the route-policy command to create the routing policy first.
Configuration Impact
If a BGP peer relationship is established, then an import policy is bound to the peer or the import policy bound to the peer is modified, and the device does not support the Refresh capability, the peer relationship is re-established because the import policy addition or modification causes the peer to resend Refresh messages.
Precautions
After the peer route-policy import command is run, only the routes that match the route-policy are received. Replacing or modifying the route-policy may cause a large number of routes to match the route-policy and be received.
When route-policy route-policy-nameis configured in the BGP multi-instance EVPN address family view, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, ACL for the next hop address of a route, ACL for the next hop address of an IPv6 route, next hop address prefix list of routing information, next hop address prefix list of IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter.
The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority coloring extended community, gateway IP address, gateway IPv6 address, BGP route local preference, next-hop address (IPv4), next-hop address (IPv6), BGP route source, BGP route preferred value, QoS parameters, and EVPN route VN-ID attributes.When route-policy route-policy-nameis configured in the BGP-EVPN address family view, the following items can be matched: IPv4 ACL, AS_Path filter, AS_Path length, community filter, route cost, IPv6 route destination address, VPN target extended community filter, priority-based coloring extended community filter, SoO extended community filter, outbound interface, MPLS label, Large-community filter, MAC address list, next-hop address ACL of routing information, next-hop address ACL of IPv6 routing information, next-hop address prefix list based on IP routing information, next-hop address prefix list based on IPv6 routing information, destination address prefix list of IP routing information, destination address prefix list of IPv6 routing information, route modulo, routing protocol type, RD attribute filter, route source IP address ACL, route source IPv6 address ACL, route source IP address prefix list, route source IPv6 address prefix list, route type, route tag, and encapsulation extended community filter.
The following attributes can be set: BGP Large-community, AS_Path, BGP community, BGP route MED, BGP route VPN target extended community, BGP route coloring extended community, BGP route SoO extended community, EVPN route priority-based coloring extended community, route gateway IP address, route gateway IPv6 address, BGP route local preference, route next-hop address (IPv4), route next-hop address (IPv6), BGP route source, BGP route preferred value, QoS parameters, and EVPN route VN-ID attributes. If the referenced policy contains unsupported attribute matching or behavior setting, unexpected results may occur. For some attribute matching behaviors, the device may display warning-level information.Example
<HUAWEI> system-view [HUAWEI] route-policy test-policy permit node 10 [HUAWEI-route-policy] quit [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 route-policy test-policy import
peer route-update-interval (BGP-EVPN address family view)
Function
The peer route-update-interval command sets the interval for sending Update messages with the same route prefix to a peer.
The undo peer route-update-interval command restores the default configuration.
By default, the interval at which routing updates are sent to IBGP peers is 15s, and the interval at which routing updates are sent to EBGP peers is 30s.
Format
peer peerIpv4Addr route-update-interval interval
undo peer peerIpv4Addr route-update-interval
peer peerIpv6Addr route-update-interval interval
undo peer peerIpv6Addr route-update-interval
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
interval |
Specifies the minimum interval at which BGP routing updates are sent. |
The value is an integer that ranges from 0 to 600, in seconds. The value 0 indicates that the device immediately sends a BGP Update message to notify the peer of the route change. |
peerIpv6Addr |
Specifies the IPv6 address of a BGP EVPN peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
When routes change, the device sends routing updates to notify its peers. If a route changes frequently, the peer route-update-interval command can be used to adjust the interval at which Update packets are sent for changes of this route. This frees the device from sending Update packets for every route change.
Implementation Procedure
If the peer route-update-interval command is used but no peer exists, a message is displayed, indicating that the peer does not exist.
Precautions
After the peer route-update-interval command is run, all routes in the current BGP routing table are sent to peers.
- If the interval between two new route additions is longer than the interval configured using the peer route-update-interval command, the device immediately sends an Update message to notify its peers, regardless of the interval configured using the peer route-update-interval command.
- If the interval between two new route additions is shorter than the interval configured using the peer route-update-interval command, the device sends an Update message to notify its peers after the configured interval expires. If a route is withdrawn because the export policy denies the route, the device sends a Withdraw message to notify its peers after the configured interval expires.
- In other cases, if a route is withdrawn, the device immediately sends a Withdraw message to notify its peers, regardless of the interval set using the peer route-update-interval command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.2 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 route-update-interval 10
peer route-update-interval (BGP-EVPN address family view) (group)
Function
The peer route-update-interval command sets the interval for sending Update messages with the same route prefix to a peer group.
The undo peer route-update-interval command restores the default configuration.
By default, the interval at which routing updates are sent to IBGP peers is 15s, and the interval at which routing updates are sent to EBGP peers is 30s.
Format
peer peerGroupName route-update-interval interval
undo peer peerGroupName route-update-interval
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of a BGP EVPN 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. |
interval |
Specifies the minimum interval at which BGP routing updates are sent. |
The value is an integer ranging from 0 to 600, in seconds. The value 0 indicates that the device immediately sends BGP Update messages to notify its peers of route changes. |
Usage Guidelines
Usage Scenario
When routes change, the device sends routing updates to notify its peers. If a route changes frequently, the peer route-update-interval command can be used to adjust the interval at which Update packets are sent for changes of this route. This frees the device from sending Update packets for every route change.
Implementation Procedure
If the peer route-update-interval command is used but no peer exists, a message is displayed, indicating that the peer does not exist.
Precautions
After the peer route-update-interval command is run, all routes in the current BGP routing table are sent to peers.
- If the interval between two new route additions is longer than the interval configured using the peer route-update-interval command, the device immediately sends an Update message to notify its peers, regardless of the interval configured using the peer route-update-interval command.
- If the interval between two new route additions is shorter than the interval configured using the peer route-update-interval command, the device sends an Update message to notify its peers after the configured interval expires. If a route is withdrawn because the export policy denies the route, the device sends a Withdraw message to notify its peers after the configured interval expires.
- In other cases, if a route is withdrawn, the device immediately sends a Withdraw message to notify its peers, regardless of the interval set using the peer route-update-interval command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] peer 10.1.1.2 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 route-update-interval 10
peer route-update-interval(bgp-muli-instance-af-evpn view)
Function
The peer route-update-interval command sets the interval for sending Update messages with the same route prefix to a peer.
The undo peer route-update-interval command restores the default configuration.
By default, the interval at which route update messages are sent to IBGP peers is 15s, and the interval at which route update messages are sent to EBGP peers is 30s.
Format
peer peerIpv4Addr route-update-interval interval
undo peer peerIpv4Addr route-update-interval
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
interval |
Specifies the minimum interval at which routing updates are sent. |
The value is an integer ranging from 0 to 600, in seconds. The value 0 indicates that the device immediately sends BGP Update messages to notify its peers of route changes. |
Usage Guidelines
Usage Scenario
When routes change, the device sends routing updates to notify its peers. If a route changes frequently, the peer route-update-interval command can be used to adjust the interval at which Update packets are sent for changes of this route. This frees the device from sending Update packets for every route change.
Precautions
After the peer route-update-interval command is run, all routes in the current BGP routing table are sent to peers.
- If the interval between two new route additions is longer than the interval configured using the peer route-update-interval command, the device immediately sends an Update message to notify its peers, regardless of the interval configured using the peer route-update-interval command.
- If the interval between two new route additions is shorter than the interval configured using the peer route-update-interval command, the device sends an Update message to notify its peers after the configured interval expires. If a route is withdrawn because the export policy denies the route, the device sends a Withdraw message to notify its peers after the configured interval expires.
- In other cases, if a route is withdrawn, the device immediately sends a Withdraw message to notify its peers, regardless of the interval set using the peer route-update-interval command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 instance aa [HUAWEI-bgp-instance-aa] peer 10.1.1.1 as-number 100 [HUAWEI-bgp-instance-aa] l2vpn-family evpn [HUAWEI-bgp-instance-aa-af-evpn] peer 10.1.1.1 enable [HUAWEI-bgp-instance-aa-af-evpn] peer 10.1.1.1 route-update-interval 10
peer split-group (BGP-EVPN address family view)
Function
The peer split-group command configures a split horizon group (SHG) to which BGP EVPN peers belong.
The undo peer split-group command restores the default configuration.
By default, no SHG is configured for BGP EVPN peers.
Format
peer ipv4-address split-group split-group-name
undo peer ipv4-address split-group split-group-name
Parameters
Parameter | Description | Value |
---|---|---|
ipv4-address |
Specifies the IPv4 address of a BGP EVPN peer. |
The value is in dotted decimal notation. |
split-group split-group-name |
Specifies the name of the SHG to which BGP EVPN peers belong. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
Usage Scenario
In a scenario where segment VXLAN is used to implement Layer 2 interworking between DCs, a VXLAN tunnel is established in BGP EVPN mode between the DCs. To prevent forwarding BUM traffic from causing loops, run the peer split-group command on the transit leaf nodes (edge devices interconnecting the DCs) to configure an SHG to which the BGP EVPN peers (transit leaf nodes) belong. After the configuration is complete, devices within a DC belong to the default SHG, and transit leaf nodes between DCs belong to the specified SHG. In this manner, when a transit leaf node receives BUM traffic, it does not forward traffic to a device belonging to the same SHG, therefore preventing loops.
Prerequisites
BGP EVPN peers have been enabled to exchange route information using the peer enable command.
peer split-group (BGP-EVPN address family view) (group)
Function
The peer split-group command configures a split horizon group (SHG) to which a BGP EVPN peer group belong.
The undo peer split-group command restores the default configuration.
By default, no SHG is configured for a BGP EVPN peer group.
Format
peer group-name split-group split-group-name
undo peer group-name split-group split-group-name
Parameters
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a BGP EVPN 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. |
split-group split-group-name |
Specifies the name of the SHG to which BGP EVPN peers (or peer groups) belong. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
Usage Scenario
In a scenario where segment VXLAN is used to implement Layer 2 interworking between DCs, a VXLAN tunnel is established in BGP EVPN mode between the DCs. To prevent forwarding BUM traffic from causing loops, run the peer split-group command on the transit leaf nodes (edge devices interconnecting the DCs) to configure an SHG to which the BGP EVPN peers (transit leaf nodes) belong. After the configuration is complete, devices within a DC belong to the default SHG, and transit leaf nodes between DCs belong to the specified SHG. In this manner, when a transit leaf node receives BUM traffic, it does not forward traffic to a device belonging to the same SHG, therefore preventing loops.
Prerequisites
BGP EVPN peer groups have been enabled to exchange route information using the peer enable command.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] peer 10.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 split-group aa
peer transit-med-to-ebgp
Function
The peer transit-med-to-ebgp command enables a device to transmit MED attributes to an EBGP EVPN peer.
The undo peer transit-med-to-ebgp command disables a device from transmitting MED attributes to an EBGP EVPN peer.
The peer transit-med-to-ebgp disable command disables a device from transmitting MED attributes to a specified EBGP EVPN peer in an EBGP EVPN peer group.
The undo peer transit-med-to-ebgp disable command enables a device to transmit MED attributes to a specified EBGP EVPN peer in an EBGP EVPN peer group.
By default, a device does not forcibly transmit MED attributes to an EBGP EVPN peer.
Format
peer peerIpv4Addr transit-med-to-ebgp [ disable ]
undo peer peerIpv4Addr transit-med-to-ebgp [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv4Addr |
Specifies the IPv4 address of a peer. |
It is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
The MED attribute is optional non-transitive. When an EBGP EVPN peer relationship is established between devices in two data centers in different BGP ASs, the devices do not transmit the MED attributes of EVPN routes to each other by default. The MED attribute needs to be transmitted to an EBGP EVPN peer in a scenario, for example, after you change a cost value to switch service flows between the active and standby gateways within a data center. You can run the peer transit-med-to-ebgp command to configure the local gateway to transmit the MED attributes of the received EVPN routes to the peer EBGP EVPN peer.
Precautions
MED attributes can be transmitted within an AS by default. Therefore, if you set an intra-AS peer address in this command, this command does not make sense.
Example
[HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.2 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.2 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 transit-med-to-ebgp
peer transit-med-to-ebgp (group)
Function
The peer transit-med-to-ebgp command enables a device to transmit MED attributes to an EBGP peer group.
The undo peer transit-med-to-ebgp command disables a device from transmitting MED attributes to an EBGP peer group.
By default, a device does not forcibly transmit MED attributes to an EBGP peer group.
Parameters
Parameter | Description | Value |
---|---|---|
peerGroupName |
Specifies the name of an EBGP EVPN peer group. |
The name is a string of 1 to 47 case-sensitive characters. The name does not contain spaces. If spaces are used, the string must start and end with double quotation marks ("). |
Usage Guidelines
Usage Scenario
The MED attribute is optional non-transitive. When an EBGP EVPN peer relationship is established between devices in two data centers in different BGP ASs, the devices do not transmit the MED attributes of EVPN routes to each other by default. The MED attribute needs to be transmitted to an EBGP EVPN peer in a scenario, for example, after you change a cost value to switch service flows between the active and standby gateways within a data center. You can run the peer transit-med-to-ebgp command to configure the local gateway to transmit the MED attributes of the received EVPN routes to the peer EBGP EVPN peer.
Precautions
MED attributes can be transmitted within an AS by default. Therefore, if you set an intra-AS peer address in this command, this command does not make sense.
Example
[HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 external [HUAWEI-bgp] peer gp1 as-number 200 [HUAWEI-bgp] peer 10.1.1.2 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.2 enable [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.2 group gp1 [HUAWEI-bgp-af-evpn] peer gp1 transit-med-to-ebgp
peer transit-med-to-ebgp(BGP-EVPN address family view) (IPv6)
Function
The peer transit-med-to-ebgp command enables a device to advertise the MED attribute to its EBGP-EVPN peers.
The undo peer transit-med-to-ebgp command cancels the existing configuration.
The peer transit-med-to-ebgp disable command disables a device from advertising the MED attribute to a specified peer in an EBGP-EVPN peer group.
The undo peer transit-med-to-ebgp disable command cancels the existing configuration.
By default, the MED attribute is not forcibly advertised to any EBGP EVPN peer.
Format
peer peerIpv6Addr transit-med-to-ebgp [ disable ]
undo peer peerIpv6Addr transit-med-to-ebgp [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format X:X:X:X:X:X:X:X. |
Usage Guidelines
Usage Scenario
The MED attribute is an optional non-transitive attribute. When EBGP EVPN peers are established between devices in two data centers in different BGP ASs, the MED attributes of EVPN routes are not transmitted between the EBGP EVPN peers by default. If a DC has active and standby gateways and the cost needs to be changed to trigger an active/standby switchover of service flows, you can configure peer transit-med-to-ebgp to enable the local gateway to advertise the MED attribute of received EVPN routes to the peer.
Precautions
By default, the MED attribute can be transmitted in an AS. Therefore, if the peer ip-address command is run to specify the address of a peer as an AS address, the command does not take effect.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:DB8:1::1 as-number 200 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:DB8:1::1 transit-med-to-ebgp
policy vpn-target (BGP-EVPN address family view)
Function
The policy vpn-target command configures a device to implement VPN target-based filtering for received routes.
The undo policy vpn-target command cancels VPN target-based filtering.
By default, VPN target-based filtering is enabled for VPN routes.
Usage Guidelines
Usage Scenario
After the undo policy vpn-target command is run on a device, the device does not compare the export RT of a VPN route with the import RT of the local VPN instance. In the inter-AS VPN Option B scenario, if the undo policy vpn-target command is not run, ensure that a VPN instance is created on the RR and the import RT of the local VPN instance matches the export RT of received VPN routes; otherwise, received VPN routes may be discarded.
Configuration Impact
After the policy vpn-target command is run on a device, the device accepts a VPN route if one export RT attribute contained in the VPN route matches the import IT of the local VPN instance, and then adds the VPN route to the VPN routing tables of the VPN instances of which the import RT matches the export RT of the VPN route.
Precautions
In an EVPN L3VPN scenario, either of the following commands needs to be configured:
- BGP-VPN instance address family view: segment-routing ipv6 best-effort evpn
- VPN instance view: vxlan vni
reflect between-clients (BGP-EVPN address family view)
Function
The reflect between-clients command enables route reflection among clients.
The undo reflect between-clients command disables route reflection among clients. If the clients of an RR are fully meshed, you can disable route reflection between the clients to reduce the cost.
By default, route reflection among clients through the RR is enabled.
Usage Guidelines
Usage Scenario
On some networks, if the clients of an RR establish full-mesh connections with each other, they can directly exchange routing information. Route reflection among clients through the RR is unnecessary. The undo reflect between-clients command can be used to prohibit the clients from reflecting routes to each other to reduce costs.
Prerequisites
An RR has been configured.
Precautions
The reflect between-clients command is run only on RRs.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 reflect-client [HUAWEI-bgp-af-evpn] undo reflect between-clients
reflect change-path-attribute (BGP-EVPN address family view)
Function
The reflect change-path-attribute command enables an RR to modify path attributes of BGP routes through an export policy.
The undo reflect change-path-attribute command disables an RR from modifying path attributes of BGP routes through an export policy.
By default, an RR is disabled from modifying path attributes of BGP routes through an export policy.
Usage Guidelines
Usage Scenario
According to standard protocols, RRs are disabled from modifying path attributes through an export policy; otherwise, routing loops may occur. Therefore, by default, an export policy cannot be configured on an RR to modify path attributes.
To enable an RR to modify path attributes of BGP routes through an export policy, run the reflect change-path-attribute command. The attributes that can be modified are as follows:- The apply as-path command modifies the AS_Path attribute of BGP routes.
- The apply comm-filter delete command deletes a community attribute from BGP routes.
- The apply community command modifies a community attribute of BGP routes.
- The apply cost command modifies the MED of BGP routes.
- The apply ip-address next-hop command modifies the next hop of BGP routes.
- The apply ipv6 next-hop command modifies the next hop of BGP4+ routes.
- The apply local-preference command modifies the Local_Pref of BGP routes.
- The apply origin command modifies the origin attribute of BGP routes.
- The apply extcommunity command modifies the VPN-Target extcommunity attribute of BGP routes.
- The apply extcommunity soo command modifies the SoO extcommunity attribute of BGP routes. If the undo reflect change-path-attribute command is run, the preceding configurations on the RR do not take effect.
Precautions
If an export policy is configured on the current RR, the configuration does not take effect before the reflect change-path-attribute command is run. After the reflect change-path-attribute command is run, these configurations may take effect, which may affect BGP route selection. Therefore, exercise caution when running the reflect change-path-attribute command.
Description: After the reflect change-path-attribute command is run on an RR, the peer route-policy export command takes precedence over the peer next-hop-invariable and peer next-hop-local commands.reflect same-split-group
Function
The reflect same-split-group command enables a device to reflect routes only to devices in the same split horizon group.
The undo reflect same-split-group command restores the default configuration.
By default, route reflection are advertised without being restricted by an SHG.
Usage Guidelines
Usage Scenario
In a scenario where Segment VXLAN is used to implement DC interconnection, if the route reflector function is configured on a Border Leaf node, the Border Leaf node reflects the received route to the Border Leaf node in the peer DC after receiving the route from the client in the DC, however, it does not have a route to the internal device of the local data center. Therefore, the received reflected route is invalid. To prevent this problem, you can specify devices in the data center as a split horizon group on the Border Leaf node and run the reflect same-split-group command to enable the Border Leaf node to reflect routes only to devices in the same split horizon group. In this case, the Border Leaf node in the peer DC and the local Border Leaf node are in different split horizon groups. Therefore, the Border Leaf node does not reflect routes to them.
Precautions
This command must be used together with a split horizon group. If no split horizon group is configured, the function is unavailable, but the configuration can be delivered separately. If a split horizon group is configured independently, route reflection is not affected.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 10.1.1.9 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 10.1.1.9 enable [HUAWEI-bgp-af-evpn] peer 10.1.1.9 split-group aa [HUAWEI-bgp-af-evpn] quit [HUAWEI-bgp] quit [HUAWEI] evpn [HUAWEI-evpn] reflect same-split-group
reflector cluster-id (BGP-EVPN address family view)
Function
The reflector cluster-id command sets a cluster ID for an RR.
The undo reflector cluster-id command deletes the cluster ID configured for an RR.
By default, each RR uses its router ID as the cluster ID.
Parameters
Parameter | Description | Value |
---|---|---|
cluster-id-value |
Specifies the cluster ID of an RR. |
The value is an integer ranging from 1 to 4294967295. |
cluster-id-ipv4 |
Specifies the IPv4 address of an RR. |
The value is in dotted decimal notation. |
Usage Guidelines
Usage Scenario
Sometimes, more than one RR needs to be configured in a cluster to improve network reliability and prevent a single point of failure (SPOF). If a cluster has more than one RR, the reflector cluster-id command needs to be used to set the same cluster ID for the RRs. This helps to identify the cluster and avoid routing loops.
Configuring an RR allows IBGP peers to advertise routes learned in the local AS to each other. The Cluster_List attribute is introduced to avoid loops within an AS. The Cluster_List is composed of a series of Cluster_IDs, and records all the RRs through which a route passes.Configuration Impact
If the reflector cluster-id command is run several times, the latest configuration overrides the previous one.
Precautions
To ensure that a client can learn the routes reflected by an RR, the Cluster ID configured on the RR must be different from the Cluster ID of the client (By default, the client uses its Router ID as the cluster ID). If the Cluster ID is the same as the Cluster ID of the client, the client discards received routes.
Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] peer 1.1.1.1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 1.1.1.1 enable [HUAWEI-bgp-af-evpn] peer 1.1.1.1 reflect-client [HUAWEI-bgp-af-evpn] reflector cluster-id 50
refresh bgp evpn
Format
refresh bgp [ instance instance-name ] evpn { all | peer-address | group group-name } { import | export }
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Specifies a BGP multi-instance name. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
all |
Softly resets all BGP EVPN connections. |
- |
peer-address |
Specifies a BGP EVPN peer IP address. |
The value is in dotted decimal notation. |
group group-name |
Specifies the name of a peer group. |
The value is a string of 1 to 47 case-sensitive characters, spaces not supported. The character string can contain spaces if it is enclosed with double quotation marks ("). |
import |
Triggers an inbound soft reset. |
- |
export |
Triggers an inbound soft reset. |
- |
Usage Guidelines
Usage Scenario
If the peer supports route-refresh, you can run the refresh bgp evpn command to soft reset the BGP EVPN connection. BGP EVPN soft reset can refresh the EVPN routing table and apply new filtering policies without tearing down the BGP connection.
Prerequisites
The route-refresh function has been enabled for BGP EVPN peers.
Precautions
Assume that a device supports route-refresh and is configured with the peer keep-all-routes command. After the refresh bgp command is run on the device, the device does not refresh its routing table.
refresh bgp evpn (IPv6)
Parameters
Parameter | Description | Value |
---|---|---|
peer-address |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
import |
Triggers an inbound soft reset. |
- |
export |
Triggers an inbound soft reset. |
- |
Usage Guidelines
Usage Scenario
If the peer supports route-refresh, you can run the refresh bgp evpn command to soft reset the BGP EVPN connection. BGP EVPN soft reset can refresh the EVPN routing table and apply new filtering policies without tearing down the BGP connection.
Prerequisites
Configuring BGP soft reset requires that the peers support the route-refresh capability.
Precautions
Assume that a device supports route-refresh and is configured with the peer keep-all-routes command. After the refresh bgp command is run on the device, the device does not refresh its routing table.
reset bgp evpn
Format
reset bgp [ instance instance-name ] evpn { all | as-number | ipv4-address | group group-name }
reset bgp evpn [ ipv4-address ] slow-peer
reset bgp instance instance-name evpn [ ipv4-address ] slow-peer
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Specifies a BGP multi-instance name. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
all |
Resets all BGP EVPN connections. |
- |
as-number |
Specifies a 2-byte AS number (number<1-65535>) or a 4-byte AS number (number<1-65535>.number<0-65535>). |
For an integral AS number, the value is an integer ranging from 1 to 4294967295. For an AS number in dotted notation, the value is in the format of x.y, where x and y are integers ranging from 1 to 65535 and from 0 to 65535, respectively. |
ipv4-address |
Resets connections with a specified BGP EVPN peer. |
The value is in dotted decimal notation. |
group group-name |
Resets BGP connections with the specified peer group. |
The value is a string of 1 to 47 case-sensitive characters, spaces not supported. The character string can contain spaces if it is enclosed with double quotation marks ("). |
slow-peer |
Restores a slow peer connection to a normal peer connection. |
- |
Usage Guidelines
Usage Scenario
If you want to have the new configuration take effect immediately after the BGP EVPN configuration changes, run the reset bgp evpn command.
To reset all BGP EVPN connections, run the reset bgp evpn all command.Configuration Impact
This command resets all TCP connections established between BGP EVPN peers and therefore results in the re-establishment of BGP EVPN peer relationships. Exercise caution when running this command.
reset bgp evpn (IPv6)
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies a BGP EVPN peer IPv6 address. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
slow-peer |
Slow peer. |
- |
Usage Guidelines
Usage Scenario
To reset the BGP EVPN connection of a peer, run the reset bgp evpn command.
Configuration Impact
This command resets all TCP connections established between BGP EVPN IPv6 peers and therefore results in the re-establishment of BGP EVPN IPv6 peer relationships. Exercise caution when running this command.
reset bgp evpn dampening
Function
The reset bgp evpn dampening command clears BGP EVPN route dampening information and releases suppressed routes.
Format
reset bgp instance instance-name evpn dampening
reset bgp instance instance-name evpn dampening { mac-route | prefix-route } prefix
reset bgp evpn dampening
reset bgp evpn dampening { mac-route | prefix-route } prefix
Parameters
Parameter | Description | Value |
---|---|---|
instance instance-name |
Clears route dampening information about a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters without any spaces. The character string can contain spaces if it is enclosed with double quotation marks ("). |
mac-route |
Indicates MAC advertisement routes. |
- |
prefix-route |
Indicates IP prefix routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
EVPN route prefixes are classified into the following types: MAC advertisement route, in the format of E:M:H-H-H:L:X.X.X.X or E:M:H-H-H:L: [X:X::X:X]:
IP prefix route, in the format of L:X.X.X.X:M or L:[X:X::X:X]:M:
|
Usage Guidelines
Usage Scenario
Route dampening can address route instability. In most cases, BGP EVPN is used on complex networks where routes change frequently. To prevent the adverse impact of continuous route flapping, BGP EVPN uses route dampening to suppress unstable routes.
The reset bgp evpn dampening command clears dampening information about specified BGP EVPN routes on the public network and releases specified suppressed routes. If no parameter is specified, dampening information about all BGP EVPN routes on the public network is cleared and all suppressed routes are released.Prerequisites
If you do not know which routes are suppressed, you can run the display bgp evpn all routing-table dampened command to view the suppressed routes.
Configuration Impact
After the reset bgp dampening command is run, suppressed routes are released. If the status of some routes still changes frequently, route flapping may occur. Routing flapping consumes a large number of bandwidth and CPU resources.
reset bgp evpn flap-info
Format
reset bgp instance instance-name evpn flap-info
reset bgp instance instance-name evpn flap-info { mac-route | prefix-route } prefix
reset bgp evpn flap-info
reset bgp evpn flap-info { mac-route | prefix-route } prefix
reset bgp instance instance-name evpn ip-address flap-info
reset bgp evpn { ip-address | ipv6-address } flap-info
Parameters
Parameter | Description | Value |
---|---|---|
ip-address |
Specifies an IPv4 peer address. |
The value is in dotted decimal notation. |
ipv6-address |
Specifies the IPv6 address of a peer. |
The value is a 32-bit hexadecimal string in format X:X:X:X:X:X:X:X. |
instance instance-name |
Clears route dampening information about a specified BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters. If spaces are used, the string must be enclosed in double quotation marks (" "). |
mac-route |
Indicates MAC advertisement routes. |
- |
prefix-route |
Indicates IP prefix routes. |
- |
prefix |
Specifies the prefix of an EVPN route. |
An EVPN route prefix has the following formats: MAC advertisement route. The value is in the format of E:M:H-H-H:L:X.X.X.X or E:M:H-H-H:L: [X:X::X:X], where:
IP Prefix route. The value is in the format of L:X.X.X.X:M or L:[X:X::X:X]:M, where:
|
Usage Guidelines
Usage Scenario
The process of adding a route to and then deleting the route from a routing table is called route flapping.
When route flapping occurs, the routing protocol sends Update packets to neighbors. The neighbors that receive the Update packets need to recalculate routes and modify their routing tables. Frequent route flapping consumes extensive bandwidth and CPU resources and can even affect network operations. To clear flapping statistics about BGP EVPN routes on the public network, run the reset bgp evpn flap-info command. The command output helps you monitor route changes and locate network problems.Prerequisites
Run the display bgp evpn all routing-table flap-info command to view statistics about BGP-EVPN route flapping. The command output shows specific flapping routes.
Configuration Impact
After the reset bgp evpn flap-info command is run, route flapping statistics are cleared and cannot be displayed.
Follow-up Procedure
After clearing route flapping statistics, run the display bgp evpn all routing-table flap-info command again to check BGP-EVPN route flapping statistics for fault locating.
reset evpn mac-duplication
Function
The reset evpn mac-duplication command clears MAC route suppression status of all EVPN instances.
Usage Guidelines
If you are sure that MAC routes of all EVPN instances will no longer flap and want to restore the MAC routes immediately instead of waiting for the suppression recovery time to expire, run the clear mac-route dampening command to clear the suppression status of MAC routes of all EVPN instances.
reset evpn vpn-instance mac-duplication
Function
The reset evpn vpn-instance mac-duplication command clears the suppression state of MAC routes.
Format
reset evpn vpn-instance vpn-instance-name mac-duplication [ bridge-domain bd-id ] [ mac-address mac-address ]
Parameters
Parameter | Description | Value |
---|---|---|
vpn-instance-name |
Specifies the name of an EVPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. The name must be the same as the BD ID. |
bridge-domain bd-id |
Specifies a BD in which the suppression state of MAC routes is to be cleared. |
The value is an integer ranging from 1 to 16777215. |
mac-address mac-address |
Specifies a MAC route whose suppression state is to be cleared. |
The value is a 12-digit hexadecimal number, in the format of H-H-H. Each H is 4 digits. If an H contains fewer than 4 digits, the left-most digits are padded with zeros. For example, e0 is displayed as 00e0. |
Usage Guidelines
When a MAC route to a specific MAC address or MAC routes in a specific BD have stopped flapping and you want to restore them before the configured hold-off timer expires, run the reset evpn vpn-instance mac-duplication command. This allows you to manually clear the suppression state of the MAC routes.
retry-cycle
Function
The retry-cycle command sets a hold-off time to unsuppress MAC duplication.
The undo retry-cycle command restores the default configuration.
By default, MAC duplication is unsuppressed after 540 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
retry-times |
Specifies a hold-off time to unsuppress MAC duplication suppression. |
The value is an integer ranging from 120 to 3600, in seconds. The value must be a multiple of 10. |
Usage Guidelines
Usage Scenario
On an EVPN VXLAN, two PEs may interconnect through both network-side and access-side links. If this is the case, BUM traffic loops and MAC route flapping both occur, preventing devices from working properly. In this case, MAC duplication suppression on the devices works. By default, the system checks the number of times a MAC address entry flaps within a detection period. If the number of times a MAC address entry flaps exceeds the upper threshold, the system considers MAC route flapping to be occurring on the network and consequently suppresses the flapping MAC routes. The suppressed MAC routes cannot be sent to a remote PE through a BGP EVPN peer relationship. Then, the system starts a hold-off timer to unsuppress MAC duplication. After the timer expires, MAC routes are automatically unsuppressed. To modify the hold-off time, run the retry-cycle command.
Configuration Impact
If the retry-cycle command is run in both EVPN instance view and global EVPN configuration view, the configuration in the EVPN instance view takes precedence.
Precautions
This command takes effect does not take effect for MAC/IP routes but takes effect only for MAC routes.
retry-cycle(EVPN-MAC-DUP view)
Function
The retry-cycle command sets a hold-off time to unsuppress MAC duplication.
The undo retry-cycle command restores the default configuration.
By default, MAC duplication is unsuppressed after 540 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
retry-times |
Specifies a hold-off time to unsuppress MAC duplication suppression. |
The value is an integer ranging from 120 to 3600, in seconds. The value must be a multiple of 10. |
Usage Guidelines
Usage Scenario
On an EVPN VXLAN, two PEs may interconnect through both network-side and access-side links. If this is the case, BUM traffic loops and MAC route flapping both occur, preventing devices from working properly. In this case, MAC duplication suppression on the devices works. By default, the system checks the number of times a MAC address entry flaps within a detection period. If the number of times a MAC address entry flaps exceeds the upper threshold, the system considers MAC route flapping to be occurring on the network and consequently suppresses the flapping MAC routes. The suppressed MAC routes cannot be sent to a remote PE through a BGP EVPN peer relationship. Then, the system starts a hold-off timer to unsuppress MAC duplication. After the timer expires, MAC routes are automatically unsuppressed. To modify the hold-off time, run the retry-cycle command.
Configuration Impact
If the retry-cycle command is run in both EVPN instance view and global EVPN configuration view, the configuration in the EVPN instance view takes precedence.
Precautions
This command takes effect does not take effect for MAC/IP routes but takes effect only for MAC routes.
slow-peer absolute-detection (BGP-EVPN address family view)
Function
The slow-peer absolute-detection threshold command configures an absolute threshold for slow peer detection.
The undo slow-peer absolute-detection threshold command restores the absolute threshold of slow peer detection.
The slow-peer absolute-detection disable command disables slow peer detection in absolute mode.
The undo slow-peer absolute-detection disable command enables slow peer detection in absolute mode.
By default, slow peer detection in absolute mode is enabled. The absolute threshold for slow peer detection is 60 seconds.
Format
slow-peer absolute-detection threshold threshold
slow-peer absolute-detection disable
undo slow-peer absolute-detection threshold threshold
undo slow-peer absolute-detection disable
Parameters
Parameter | Description | Value |
---|---|---|
threshold |
Specifies an absolute threshold for slow peer detection. |
The value is an integer that ranges from 3 to 3600. The default value is 60. |
Usage Guidelines
After slow peer detection is enabled, the local device calculates the difference between the time taken to send Update messages to each BGP peer and the shortest time taken to send Update messages to a BGP peer in the group. If the difference between the time taken to send Update messages to BGP peer 1 and the shortest time is greater than the specified threshold, the local device considers BGP peer 1 as a slow peer and removes it from the update peer-group. The removal of the slow peer prevents this slow peer from affecting update message advertisement to other peers in the group. If Update messages fail to be advertised, the traditional slow peer detection function cannot be used to detect slow peers. To address this problem, configure an absolute threshold for slow peer detection. If the delay in sending Update messages to a peer is greater than the absolute threshold, the peer is considered a slow peer.
To configure an absolute threshold for slow peer detection, run the slow-peer absolute-detection threshold command.slow-peer detection (BGP-EVPN address family view)
Function
The slow-peer detection threshold command configures a threshold for slow peer detection.
The undo slow-peer detection threshold command restores the absolute threshold of slow peer detection.
The slow-peer detection disable command disables slow peer detection.
The undo slow-peer detection disable command enables slow peer detection.
By default, slow peer detection is enabled, and the slow peer detection threshold is 300s.
Format
slow-peer detection threshold threshold-value
slow-peer detection disable
undo slow-peer detection [ threshold threshold-value ]
undo slow-peer detection disable
Parameters
Parameter | Description | Value |
---|---|---|
threshold-value |
Specifies a slow peer detection threshold. If the difference between the time taken to send packets to BGP peer 1 and the shortest time taken to send packets to BGP peer 2 is greater than the threshold, BGP peer 1 is considered as a slow peer. |
The value is an integer ranging from 120 to 3600, in seconds. The default value is 300. |
Usage Guidelines
Usage Scenario
An update peer-group may contain multiple peers. If the local device advertises routes to one peer slowly due to network congestion, the speed at which the local device advertises routes to other peers in the update peer-group is affected. To prevent this problem, slow peer detection is enabled by default.
After slow peer detection is enabled, the local device calculates the difference between the time taken to send messages to each peer in the update peer-group and the shortest time taken to send messages to each peer in the group. If the difference between the time taken to send messages to a peer and the shortest time is greater than the threshold specified for slow peer detection, the local device considers this peer as a slow peer and removes it from the update peer-group, which prevents this slow peer from affecting route advertisement to other peers in the group.Configuration Impact
If the command is run more than once, the latest configuration overrides the previous one.
vpn-target (EVPN instance view)
Function
The vpn-target command configures VPN targets for a BD EVPN instance.
The undo vpn-target command deletes the VPN targets of a BD EVPN instance.
By default, no VPN target is configured for BD EVPN instances.
Format
vpn-target { vrfRt } &<1-8> [ vrfRtType ]
vpn-target auto [ vrfRtType ]
undo vpn-target { vrfRt } &<1-8> [ vrfRtType ]
undo vpn-target all
undo vpn-target auto [ vrfRtType ]
Parameters
Parameter | Description | Value |
---|---|---|
vrfRt |
Specifies a VPN target to be configured for a BD EVPN instance. |
The format of a VPN target can be as follows:
|
vrfRtType |
Adds a VPN target to both the import or export VPN target lists of a BD EVPN instance. |
The value can be both, export-extcommunity, and import-extcommunity. If none is specified, the configured VPN target is added to both the import and export VPN target lists by default. |
auto |
Specifies the VPN target that is automatically generated. |
- |
all |
Deletes all VPN targets of the EVPN instance address family in the BD view. |
- |
Usage Guidelines
Usage Scenario
When a local PE advertises EVPN routes to peer PEs, the EVPN routes carry all the export VPN targets of the local EVPN instance. A peer PE installs a received EVPN route to its EVPN routing table only when the route's export VPN target is identical with the import VPN target in the PE's EVPN instance. To configure VPN targets for a BD EVPN instance, run the vpn-target command.
NOTE: A maximum of eight VPN targets can be specified in the vpn-target command. If you want to configure more VPN targets in an EVPN instance, run the vpn-target command more than once.Prerequisites
An RD has been configured for the BD EVPN instance using the route-distinguisher command.
Configuration Impact
If the vpn-target command is not run, a PE does not install received EVPN routes into its EVPN routing table.
If all the VPN targets of an EVPN instance are deleted using the undo vpn-target command, all routes learned by the EVPN instance from other VPN instances will be deleted.vpn-target evpn (VPN instance IPv4 address family view)
Function
The vpn-target evpn command configures the VPN target extended community attribute for EVPN routes in the VPN instance IPv4 address family.
The undo vpn-target evpn command deletes the VPN target extended community attribute of EVPN routes in the VPN instance IPv4 address family.
By default, no VPN target extended community list is configured for EVPN routes in the VPN instance IPv4 address family.
Format
vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target all evpn
Parameters
Parameter | Description | Value |
---|---|---|
vpn-target |
Specifies a VPN target to be configured for a VPN instance IPv4 address family. |
The format of a VPN target can be as follows:
|
vrfRtType |
Adds a VPN target to the VPN target list of a VPN instance IPv4 address family. |
The value is an enumerated type:
|
all |
Deletes all the VPN targets of a VPN instance IPv4 address family. |
- |
Usage Guidelines
Usage Scenario
When advertising EVPN IP prefix routes to other PE peers, the local PE must carry all VPN targets in the export VPN target list configured for EVPN routes in the local VPN instance IPv4 address family. If the VPN targets carried in received IRB routes or IP prefix routes overlap with those in the import VPN targets list of EVPN routes in the local VPN instance IPv4 address family, only the IRB route or IP prefix route can be added to the routing table of the local VPN instance IPv4 address family.
Prerequisites
A route distinguisher (RD) has been configured using the route-distinguisher command.
The vpn-target evpn command can be used only after the evpn-overlay enable command is run.Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] ip vpn-instance vrf1 [HUAWEI-vpn-instance-vrf1] ipv4-family [HUAWEI-vpn-instance-vrf1-af-ipv4] route-distinguisher 100:1 [HUAWEI-vpn-instance-vrf1-af-ipv4] vpn-target 3:3 export-extcommunity evpn [HUAWEI-vpn-instance-vrf1-af-ipv4] vpn-target 4:4 import-extcommunity evpn
vpn-target evpn (VPN instance IPv6 address family view)
Function
The vpn-target evpn command configures the VPN target extended community attribute for EVPN routes in the VPN instance IPv6 address family.
The undo vpn-target evpn command deletes the VPN target extended community attribute of EVPN routes in the VPN instance IPv6 address family.
By default, no VPN target extended community list is configured for EVPN routes in the VPN instance IPv6 address family.
Format
vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target all evpn
Parameters
Parameter | Description | Value |
---|---|---|
vpn-target |
Specifies the VPN target to be added to the VPN target list of a VPN instance IPv6 address family. |
The three formats of a VPN target are as follows:
|
vrfRtType |
Adds a VPN target to the VPN target list of a VPN instance IPv6 address family. |
The value is an enumerated type:
|
all |
Delete all the VPN targets of a VPN instance IPv6 address family. |
- |
Usage Guidelines
Usage Scenario
When advertising EVPN IPv6 prefix routes to other PE peers, the local PE must carry all VPN targets in the export VPN target list configured for EVPN routes in the local VPN instance IPv6 address family. If the VPN targets carried in received IRBv6 routes or IPv6 prefix routes overlap with those in the import VPN targets list of EVPN routes in the local VPN instance IPv6 address family, only the IRBv6 route or IPv6 prefix route can be added to the routing table of the local VPN instance IPv6 address family.
Prerequisites
The ipv6-family command has been run in the VPN instance view to enable the IPv6 address family, and the route-distinguisher command has been run in the VPN instance view to set an RD for the VPN instance IPv6 address family.
Configuration Impact
If the vpn-target evpn command is not used, a PE does not install received IRBv6 routes or IPv6 prefix routes into the routing table of its VPN instance IPv6 address family.
After the undo vpn-target evpn command is run, all routes learned through IRBv6 routes or IPv6 prefix routes in the VPN instance address family are deleted.Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] ip vpn-instance vrf1 [HUAWEI-vpn-instance-vrf1] ipv6-family [HUAWEI-vpn-instance-vrf1-af-ipv6] route-distinguisher 100:1 [HUAWEI-vpn-instance-vrf1-af-ipv6] vpn-target 5:5 evpn
vpn-target evpn (VPN instance view)
Function
The vpn-target evpn command configures the VPN target extended community attribute for EVPN routes in the VPN instance.
The undo vpn-target evpn command deletes the VPN target extended community attribute of EVPN routes in the VPN instance.
By default, no VPN target extended community list is configured for EVPN routes in the VPN instance.
Format
vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target { vpn-target } &<1-8> [ vrfRtType ] evpn
undo vpn-target all evpn
Parameters
Parameter | Description | Value |
---|---|---|
vpn-target |
Specifies a VPN target to be configured for a VPN instance. |
The format of a VPN target can be as follows:
|
vrfRtType |
Adds a VPN target to the VPN target list of a VPN instance. |
The value is an enumerated type:
|
all |
Deletes all the VPN targets of a VPN instance. |
- |
Usage Guidelines
When advertising EVPN IP prefix routes to other PE peers, the local PE must carry all VPN targets in the export VPN target list configured for EVPN routes in the local VPN instance. If the VPN targets carried in received IRB routes or IP prefix routes overlap with those in the import VPN targets list of EVPN routes in the local VPN instance, only the IRB route or IP prefix route can be added to the routing table of the local VPN instance.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] ip vpn-instance vrf1 [HUAWEI-vpn-instance-vrf1] route-distinguisher 100:1 [HUAWEI-vpn-instance-vrf1-af-ipv4] quit [HUAWEI-vpn-instance-vrf1] vpn-target 3:3 export-extcommunity evpn [HUAWEI-vpn-instance-vrf1] vpn-target 4:4 import-extcommunity evpn
peer advertise encap-type
Function
The peer advertise encap-type command configures the encapsulation attribute carried in EVPN routes to be advertised to peers.
The undo peer advertise encap-type command restores the default configuration.
By default, a device advertises EVPN routes that carry the VXLAN encapsulation attribute to its peers.
Format
peer ipv6-address advertise encap-type srv6 [ advertise-srv6-locator ]
undo peer ipv6-address advertise encap-type srv6 [ advertise-srv6-locator ]
Parameters
Parameter | Description | Value |
---|---|---|
ipv6-address |
Specifies the IPv6 address of a peer. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
srv6 |
Specifies EVPN routes carrying the SRv6 encapsulation attribute. |
- |
advertise-srv6-locator |
Enables EVPN routes to use the SRv6 SID Structure Sub-Sub-TLV to carry locator length information. |
- |
Usage Guidelines
Usage Scenario
By default, BGP EVPN peers advertise only VXLAN-encapsulated EVPN routes to each other. However, in an EVPN over SRv6 scenario, BGP EVPN peers need to advertise SRv6-encapsulated EVPN routes to each other. To enable BGP EVPN peers to advertise SRv6-encapsulated EVPN routes to each other, run the peer advertise encap-type srv6 command.
In an EVPN over SRv6 BE scenario, BFD is used to detect locator reachability. If the primary path fails, BFD goes Down, triggering auto FRR (VPN FRR) to perform path switching. After locator routes are summarized by the P between PEs, the remote PE can learn only the summarized locator routes of the local PE. BFD, however, depends on the peer IPv6 address (also the local locator address) bound to the BFD session. As a result, BFD fails, and auto FRR (VPN FRR) switching cannot be triggered. To solve this problem, you can configure the advertise-srv6-locator parameter on the local PE so that the local PE carries locator length information when advertising BGP routes to the remote PE. The remote PE calculates the local locator based on the SRv6 SID and locator length information carried in the routes. If the peer IPv6 address bound to the BFD session matches the IPv6 address of the local locator, BFD takes effect. When the primary path fails, auto FRR (VPN FRR) is triggered for path switching.Precautions
If a BGP EVPN peer is in a peer group, running the undo peer advertise encap-type command applies the encapsulation attributes of the peer group to the peer, and running the undo peer advertise encap-type command again restores the default encapsulation attributes of the peer.
An SRv6 license must have been loaded before SRv6 parameters are configured.Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 advertise encap-type srv6
peer advertise encap-type (group)
Function
The peer advertise encap-type command configures the encapsulation attribute carried by EVPN routes advertised to peer group.
The undo peer advertise encap-type command restores the default configuration.
By default, a device advertises EVPN routes that carry the VXLAN encapsulation attribute to the peer group.
Format
peer group-name advertise encap-type srv6 [ advertise-srv6-locator ]
undo peer group-name advertise encap-type srv6 [ advertise-srv6-locator ]
Parameters
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a peer group. |
The value is a string of 1 to 47 case-sensitive characters and cannot contain spaces. If the character string is quoted by double quotation marks, the character string can contain spaces. |
srv6 |
Specifies EVPN routes carrying the SRv6 encapsulation attribute. |
- |
advertise-srv6-locator |
Enables EVPN routes to use the SRv6 SID Structure Sub-Sub-TLV to carry locator length information. |
- |
Usage Guidelines
Usage Scenario
By default, BGP EVPN peers advertise only VXLAN-encapsulated EVPN routes to each other. However, in an EVPN over SRv6 scenario, BGP EVPN peers need to advertise SRv6-encapsulated EVPN routes to each other. To enable BGP EVPN peers to advertise SRv6-encapsulated EVPN routes to each other, run the peer advertise encap-type srv6 command.
In an EVPN over SRv6 BE scenario, BFD is used to detect locator reachability. If the primary path fails, BFD goes Down, triggering auto FRR (VPN FRR) to perform path switching. After locator routes are summarized by the P between PEs, the remote PE can learn only the summarized locator routes of the local PE. BFD, however, depends on the peer IPv6 address (also the local locator address) bound to the BFD session. As a result, BFD fails, and auto FRR (VPN FRR) switching cannot be triggered. To solve this problem, you can configure the advertise-srv6-locator parameter on the local PE so that the local PE carries locator length information when advertising BGP routes to the remote PE. The remote PE calculates the local locator based on the SRv6 SID and locator length information carried in the routes. If the peer IPv6 address bound to the BFD session matches the IPv6 address of the local locator, BFD takes effect. When the primary path fails, auto FRR (VPN FRR) is triggered for path switching.Example
<HUAWEI> system-view [HUAWEI] bgp 100 [HUAWEI-bgp] group gp1 [HUAWEI-bgp] peer 2001:db8:1::1 group gp1 [HUAWEI-bgp] peer 2001:db8:2::2 group gp1 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer gp1 enable [HUAWEI-bgp-af-evpn] peer gp1 advertise encap-type srv6
reset bgp slow-delete sid evpn
Function
The reset bgp slow-delete sid evpn command deletes a BGP-EVPN SID in the delayed deletion state.
Parameters
Parameter | Description | Value |
---|---|---|
ipv4 |
Deletes the SID of an EVPN L3VPNv4 route in the delayed deletion state. |
- |
ipv6 |
Deletes the SID of an EVPN L3VPNv6 route in the delayed deletion state. |
- |
vpn |
Deletes the SID of an L3EVPN instance in the delayed deletion state. |
- |
segment-routing ipv6 best-effort evpn
Function
The segment-routing ipv6 best-effort evpn command enables SRv6 EVPN L3VPN, enables a device to recurse routes based on the SID attribute carried in EVPN routes.
The undo segment-routing ipv6 best-effort evpn command disables SRv6 EVPN L3VPN, disables a device from recursing routes based on the SID attribute carried in EVPN routes.
By default, SRv6 EVPN L3VPN is not enabled, route recursion based on the SID attribute carried in EVPN routes is not enabled.
Usage Guidelines
Usage Scenario
To enable route recursion over an SRv6 BE tunnel based on the SID attribute in EVPN routes, run the segment-routing ipv6 best-effort evpn command.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] ip vpn-instance vpn1 [HUAWEI-vpn-instance-vpn1] ipv4-family [HUAWEI-vpn-instance-vpn1-af-ipv4] route-distinguisher 100:1 [HUAWEI-vpn-instance-vpn1-af-ipv4] vpn-target 100:1 both [HUAWEI-vpn-instance-vpn1-af-ipv4] quit [HUAWEI-vpn-instance-vpn1] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv4-family vpn-instance vpn1 [HUAWEI-bgp-vpn1] segment-routing ipv6 best-effort evpn
segment-routing ipv6 locator evpn
Function
The segment-routing ipv6 locator evpn command adds the SID attribute to the VPN routes to be sent through EVPN.
The undo segment-routing ipv6 locator evpn command restores the default configuration.
By default, the SID attribute is not added to the VPN routes to be sent through EVPN.
Format
segment-routing ipv6 locator locator-name evpn
undo segment-routing ipv6 locator locator-name evpn
Parameters
Parameter | Description | Value |
---|---|---|
locator-name |
Specifies the name of a node route segment. |
The value is a string of 1 to 31 characters. |
Usage Guidelines
Usage Scenario
In an EVPN L3VPN scenario, if service traffic needs to be carried over an SRv6 tunnel, the segment-routing ipv6 locator evpn command can be run to add the SID attribute to the EVPN routes to be sent. Upon receipt of EVPN routes from a BGP EVPN peer, the local device can recurse routes over an SRv6 tunnel based on the SID attribute carried in routes.
Example
<HUAWEI> system-view [HUAWEI] segment-routing ipv6 [HUAWEI-segment-routing-ipv6] locator as ipv6-prefix 2001:DB8:100:: 64 static 32 [HUAWEI-segment-routing-ipv6-locator] quit [HUAWEI-segment-routing-ipv6] quit [HUAWEI] evpn-overlay enable [HUAWEI] ip vpn-instance vpn1 [HUAWEI-vpn-instance-vpn1] ipv4-family [HUAWEI-vpn-instance-vpn1-af-ipv4] route-distinguisher 100:1 [HUAWEI-vpn-instance-vpn1-af-ipv4] quit [HUAWEI-vpn-instance-vpn1] quit [HUAWEI] bgp 100 [HUAWEI-bgp] ipv4-family vpn-instance vpn1 [HUAWEI-bgp-vpn1] segment-routing ipv6 locator as evpn
inclusive-route pmsi-compatible
Function
The inclusive-route pmsi-compatible command enables compatibility with the PMSI attribute for inclusive routes.
The undo inclusive-route pmsi-compatible command restores the default configuration.
By default, compatibility with the PMSI attribute of inclusive routes is disabled.
Usage Guidelines
Usage Scenario
When the most significant bit of the Tunnel Type field in the PMSI Tunnel Attribute of a received inclusive route is 1 (composite tunnel bit) and the least significant seven bits are 0x06 (Ingress Replication), all routes contained in the packet are withdrawn according to related standards. After the inclusive-route pmsi-compatible command is run, these routes are not withdrawn.
peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)
Function
The peer srv6-label-compatible inclusive-route command enables SRv6 label compatibility for inclusive routes, so that the device sends inclusive routes in the standard format (with the MPLS label carried in the PMSI attribute set to 0).
The undo peer srv6-label-compatible inclusive-route command restores the default configuration.
By default, the MPLS label value in the PMSI attribute is set to 3 when inclusive routes are sent to SRv6 peers.
Format
peer peerIpv6Addr srv6-label-compatible inclusive-route [ disable ]
undo peer peerIpv6Addr srv6-label-compatible inclusive-route [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is in the format X:X:X:X:X:X:X:X. |
srv6-label-compatible |
Indicates compatibility with SRv6 labels. |
- |
inclusive-route |
Inclusive multicast routes. |
- |
disable |
Disables the function. |
- |
Usage Guidelines
Usage Scenario
In a non-transposition scenario, when sending an inclusive route to an SRv6 peer, the device does not set the MPLS label value in the PMSI attribute to 0 according to related standards. To enable a Huawei device to communicate with a non-Huawei device, run this command to change the MPLS label value in the PMSI attribute of inclusive routes to 0.
Example
<HUAWEI> system-view [HUAWEI] evpn-overlay enable [HUAWEI] bgp 100 [HUAWEI-bgp] peer 2001:db8:1::1 as-number 100 [HUAWEI-bgp] l2vpn-family evpn [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 enable [HUAWEI-bgp-af-evpn] peer 2001:db8:1::1 srv6-label-compatible inclusive-route
peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)(group)
Function
The peer srv6-label-compatible inclusive-route command enables SRv6 label compatibility for a peer group so that the device sends inclusive routes in the standard format (with the MPLS label carried in the PMSI attribute set to 0).
The undo peer srv6-label-compatible inclusive-route command disables SRv6 label compatibility for a peer group.
By default, the MPLS label value in the PMSI attribute is set to 3 when inclusive routes are sent to SRv6 peers.
Format
peer groupName srv6-label-compatible inclusive-route
undo peer groupName srv6-label-compatible inclusive-route
Parameters
Parameter | Description | Value |
---|---|---|
groupName |
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. |
Usage Guidelines
Usage Scenario
In a non-transposition scenario, when sending an inclusive route to an SRv6 peer, the device does not set the MPLS label value in the PMSI attribute to 0 according to related standards. To enable a Huawei device to communicate with a non-Huawei device, run this command to change the MPLS label value in the PMSI attribute of inclusive routes to 0.
peer srv6-label-compatible(BGP-EVPN address family view)
Function
The peer srv6-label-compatible command enables SRv6 label compatibility for a peer group, enabling the device to send IRB and ES-AD routes in standard formats, with the MPLS Layer 3 labels of IRB routes and the ESI labels of ES-AD routes set to 3 (Implicit NULL).
The undo peer srv6-label-compatible command disables SRv6 label compatibility for a peer group.
By default, a device sets the MPLS Layer 3 labels of IRB routes to be the same as the L3VPN instance label and the ESI labels of ES-AD routes to be the same as the ESI MPLS label when sending IRB and ES-AD routes to SRv6 peers.
Format
peer peerIpv6Addr srv6-label-compatible [ disable ]
undo peer peerIpv6Addr srv6-label-compatible [ disable ]
Parameters
Parameter | Description | Value |
---|---|---|
peerIpv6Addr |
Specifies the IPv6 address of a peer. |
The value is in the format X:X:X:X:X:X:X:X. |
disable |
Disables the function. |
- |
Usage Guidelines
Usage Scenario
In a non-transposition scenario, when ES-AD and IRB routes are sent to SRv6 peers, the ESI labels and MPLS Layer 3 labels are not set to 3 according to related standards. To enable a Huawei device to communicate with a non-Huawei device, run this command to configure the Huawei device to change the ESIs carried in ES-AD routes and MPLS Layer 3 labels carried in IRB routes.
peer srv6-label-compatible(BGP-EVPN address family view)(group)
Function
The peer srv6-label-compatible command enables SRv6 label compatibility for a peer group, enabling the device to send IRB and ES-AD routes in standard formats, with the MPLS Layer 3 labels of IRB routes and the ESI labels of ES-AD routes set to 3 (Implicit NULL).
The undo peer srv6-label-compatible command disables SRv6 label compatibility for a peer group.
By default, a device sets the MPLS Layer 3 labels of IRB routes to be the same as the L3VPN instance label and the ESI labels of ES-AD routes to be the same as the ESI MPLS label when sending IRB and ES-AD routes to SRv6 peers.
Parameters
Parameter | Description | Value |
---|---|---|
groupName |
Specifies the name of a peer group. |
The value is a string of 1 to 47 case-sensitive characters, spaces not supported. The character string can contain spaces if it is enclosed with double quotation marks ("). |
Usage Guidelines
Usage Scenario
In a non-transposition scenario, when ES-AD and IRB routes are sent to SRv6 peers, the ESI labels and MPLS Layer 3 labels are not set to 3 according to related standards. To enable a Huawei device to communicate with a non-Huawei device, run this command to configure the Huawei device to change the ESIs carried in ES-AD routes and MPLS Layer 3 labels carried in IRB routes.
- advertise bgp l2vpn-family evpn lowest-priority enable
- advertise l2vpn evpn
- advertise l2vpn evpn (BGP-VPN instance IPv4 address family view/BGP-VPN instance IPv6 address family view)
- advertise route-reoriginate evpn disable
- bestroute add-path (BGP-EVPN address family view)
- dampening (BGP-EVPN address family view)
- detect loop-times
- detect loop-times (EVPN-MAC-DUP view)
- display bgp evpn all routing-table dampening parameter
- display bgp evpn all routing-table statistics
- display bgp evpn group
- display bgp evpn peer
- display bgp evpn peer verbose
- display bgp evpn routing-table (peer)
- display bgp evpn routing-table (prefix condition)
- display bgp evpn routing-table dampened
- display bgp evpn routing-table flap-info
- display bgp evpn routing-table(prefix)
- display bgp evpn update-peer-group
- display bgp evpn vpn-instance routing-table
- display bgp evpn vpn-instance routing-table (prefix)
- display bgp evpn vpn-instance routing-table (verbose)
- display evpn mac-duplication
- display evpn vpn-instance
- display evpn vpn-instance mac-duplication
- display evpn vpn-instance mac-duplication history
- evpn
- evpn ( bd-evpn-instance view )
- evpn-overlay enable
- evpn-route-origin igp
- export route-policy (EVPN instance view)
- export route-policy evpn
- filter-policy
- import route-policy (EVPN instance view)
- import route-policy evpn
- irb asymmetric (BGP-VPN instance IPv4 address family view)
- irb asymmetric (BGP-VPN instance IPv6 address family view)
- l2vpn-family evpn
- l2vpn-family evpn (bgp-instance-af-evpn-extend view)
- l3-reoriginate different-split-group
- local mac-only-route no-generate
- mac-duplication (EVPN instance view)
- mac-duplication (Global EVPN configuration view)
- mac-ip route generate-mac
- mac-route no-advertise
- nexthop recursive-lookup default-route (BGP-EVPN address family view)
- nexthop recursive-lookup default-route (bgp-muli-instance-af-evpn view)
- nexthop recursive-lookup delay (BGP-EVPN address family view)
- nexthop recursive-lookup restrain disable (EVPN instance view)
- nexthop recursive-lookup restrain disable (Global EVPN configuration view)
- peer advertise (BGP-EVPN address family view)
- peer advertise (BGP-EVPN address family view) (group)
- peer advertise (BGP-EVPN address family view) (IPv6)
- peer advertise add-path (BGP-EVPN address family view)
- peer advertise add-path (BGP-EVPN address family view) (group)
- peer advertise add-path (bgp-muli-instance-af-evpn view)
- peer advertise route-reoriginated (BGP-EVPN address family view)
- peer advertise route-reoriginated (BGP-EVPN address family view) (group)
- peer advertise-community (BGP-EVPN address family view)
- peer advertise-community (BGP-EVPN address family view) (group)
- peer advertise-community (bgp-muli-instance-af-evpn view)
- peer advertise-large-community
- peer advertise-large-community (BGP-EVPN address family view)
- peer advertise-large-community (BGP-EVPN address family view) (group)
- peer allow-as-loop (BGP-EVPN address family view) (group)
- peer allow-as-loop (BGP-EVPN address family view) (IPv6)
- peer allow-as-loop (BGP-EVPN address family view)(IPv4)
- peer attribute-id (BGP-EVPN address family view)
- peer attribute-id (BGP-EVPN address family view) (IPv6)
- peer capability-advertise add-path (BGP-EVPN address family view)
- peer capability-advertise add-path (BGP-EVPN address family view) (group)
- peer capability-advertise add-path (bgp-muli-instance-af-evpn view)
- peer enable (BGP-EVPN address family view) (group)
- peer enable (BGP-EVPN address family view) (IPv4)
- peer enable (BGP-EVPN address family view) (IPv6)
- peer graceful-restart static-timer (BGP-EVPN address family view)
- peer graceful-restart static-timer (BGP-EVPN address family view)(IPv6)
- peer group (BGP-EVPN address family view) (IPv6)
- peer group (BGP-EVPN address family view)(IPv4)
- peer high-priority (BGP-EVPN address family view)
- peer high-priority (BGP-EVPN address family view) (group)
- peer high-priority (BGP-EVPN address family view) (ipv6)
- peer import reoriginate (BGP-EVPN address family view)
- peer import reoriginate (BGP-EVPN address family view) (group)
- peer mac-limit (BGP-EVPN address family view)
- peer mac-limit (BGP-EVPN address family view) (group)
- peer mac-limit (BGP-EVPN address family view) (ipv6)
- peer next-hop-invariable (BGP-EVPN address family view)
- peer next-hop-invariable (BGP-EVPN address family view) (group)
- peer next-hop-invariable (BGP-EVPN address family view) (IPv6)
- peer peer-as-check (BGP-EVPN address family view)(IPv6)
- peer peer-as-check(BGP-EVPN address family view)
- peer peer-as-check(BGP-EVPN address family view)(group)
- peer preferred-value (BGP-EVPN address family view) (group)
- peer preferred-value (BGP-EVPN address family view)(IPv4)
- peer reflect-client (BGP-EVPN address family view) (group)
- peer reflect-client (BGP-EVPN address family view) (IPv6)
- peer reflect-client (BGP-EVPN address family view)(IPv4)
- peer route-limit (BGP-EVPN address family view)
- peer route-limit (BGP-EVPN address family view) (group)
- peer route-policy export (BGP-EVPN address family view)
- peer route-policy export (BGP-EVPN address family view) (group)
- peer route-policy export (BGP-EVPN address family view) (IPv6)
- peer route-policy import (BGP-EVPN address family view) (group)
- peer route-policy import (BGP-EVPN address family view) (IPv6)
- peer route-policy import (BGP-EVPN address family view)(IPv4)
- peer route-update-interval (BGP-EVPN address family view)
- peer route-update-interval (BGP-EVPN address family view) (group)
- peer route-update-interval(bgp-muli-instance-af-evpn view)
- peer split-group (BGP-EVPN address family view)
- peer split-group (BGP-EVPN address family view) (group)
- peer transit-med-to-ebgp
- peer transit-med-to-ebgp (group)
- peer transit-med-to-ebgp(BGP-EVPN address family view) (IPv6)
- policy vpn-target (BGP-EVPN address family view)
- reflect between-clients (BGP-EVPN address family view)
- reflect change-path-attribute (BGP-EVPN address family view)
- reflect same-split-group
- reflector cluster-id (BGP-EVPN address family view)
- refresh bgp evpn
- refresh bgp evpn (IPv6)
- reset bgp evpn
- reset bgp evpn (IPv6)
- reset bgp evpn dampening
- reset bgp evpn flap-info
- reset evpn mac-duplication
- reset evpn vpn-instance mac-duplication
- retry-cycle
- retry-cycle(EVPN-MAC-DUP view)
- slow-peer absolute-detection (BGP-EVPN address family view)
- slow-peer detection (BGP-EVPN address family view)
- vpn-target (EVPN instance view)
- vpn-target evpn (VPN instance IPv4 address family view)
- vpn-target evpn (VPN instance IPv6 address family view)
- vpn-target evpn (VPN instance view)
- peer advertise encap-type
- peer advertise encap-type (group)
- reset bgp slow-delete sid evpn
- segment-routing ipv6 best-effort evpn
- segment-routing ipv6 locator evpn
- inclusive-route pmsi-compatible
- peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)
- peer srv6-label-compatible inclusive-route(BGP-EVPN address family view)(group)
- peer srv6-label-compatible(BGP-EVPN address family view)
- peer srv6-label-compatible(BGP-EVPN address family view)(group)