static (Origin Validation for BGP)
Syntax static {
record destination {
maximum-length prefix-length {
origin-autonomous-system as-number {
validation-state (invalid | valid);
}
}
}
}
Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation],
[edit logical-systems logical-system-name routing-options validation],
[edit routing-instances instance-name routing-options validation],
[edit routing-options validation]
Release Information Statement introduced in Junos OS Release 12.2.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Description Configure a static route validation (RV) record.
RV records are received from the cache server using the protocol defined in Internet draft
draft-ietf-sidr-rpki-rtr-19, The RPKI/Router Protocol, and can also be configured statically,
as shown here.
Static records are useful for overwriting the information received from an RPKI cache
server.
An RV record matches any route whose prefix matches the RV prefix record, whose prefix
length does not exceed the maximum-length given in the RV record, and whose origin AS
equals the origin-autonomous-system number given in the RV record.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege
Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Use Case and Benefit of Origin Validation
• Understanding Origin Validation for BGP
• Example: Configuring Origin Validation for BGP
1733Copyright © 2017, Juniper Networks, Inc.
Chapter 41: Configuration Statements
To Next Page
Loading...
Need help?
General
