peer origin-validation export (BGP view)(group)

Format

peer peerGroupName origin-validation export [ include-not-found [ external ] ]

undo peer peerGroupName origin-validation export [ include-not-found [ external ] ]

Parameters

Parameter	Description	Value
peerGroupName	Specifies the name of a peer group.	The value is a string of 1 to 47 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
include-not-found	Configures the device to send routes with the ROA validation result as Valid or Not Found to the EBGP peer.	-
external	Configures the device to send the routes with the ROA validation result as Valid or Not Found (the Not Found routes are received other ASs) to the EBGP peer.	-

Parameter

Description

Value

peerGroupName

Specifies the name of a peer group.

The value is a string of 1 to 47 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

include-not-found

Configures the device to send routes with the ROA validation result as Valid or Not Found to the EBGP peer.

-

external

Configures the device to send the routes with the ROA validation result as Valid or Not Found (the Not Found routes are received other ASs) to the EBGP peer.

-

Views

BGP view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
bgp	write

Usage Guidelines

Usage Scenario

After a device sets up a session with an RPKI server and saves the ROA data downloaded from the server, you can run the peer origin-validation export command to enable an EBGP peer group to perform ROA validation on the routes to be advertised to an EBGP peer; if a route has a match in the ROA database and the information about the source AS is consistent with that in the database, the validation result is Valid. If the information about the source AS is inconsistent, the validation result is Invalid. If the route has no match in the ROA database, the validation result is Not Found. By default, only the routes whose validation result is Valid are advertised. To advertise the routes with the validation results being Valid or Not Found, configure include-not-found. To advertise the routes with the validation results being Valid or Not Found (the Not Found routes are received other ASs), configure include-not-found external.

Example

# Configure an EBGP peer group to perform the ROA validation on the routes to be sent to an EBGP peer.

<HUAWEI> system-view
[~HUAWEI] bgp 100
[*HUAWEI-bgp] group test external
[*HUAWEI-bgp] peer test origin-validation export