Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

session (Origin Validation for BGP)

 

Syntax

Hierarchy Level

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 TCP session with a resource public key infrastructure (RPKI) cache server. The router-to-cache transport protocol is carried using a TCP session to a configurable port. Caches are organized in groups. The Junos OS implementation supports up to 63 sessions per group and both IPv4 and IPv6 address families.

The maximum number of sessions in a group is two, by default, and is configurable. If the number of sessions in a group exceeds the max-sessions value, the connections are established in order by preference value. A numerically higher preference results in a higher probability for session establishment. The order of session establishment is random among sessions with equal preferences.

Options

server-ip-address Specify the IP address of the RPKI cache server.
hold-time seconds Specify the length of time in seconds that the session between the routing device and the RPKI cache server is to be considered operational without any activity. After the hold time expires, the session is dropped.

Receiving any protocol data unit (PDU) from the cache server resets the hold timer. The hold time must be configured to be at least twice the value configured on the refresh-time statement. If the hold time expires, the session is considered to be down. This, in turn, triggers a session restart event. During a session restart, the routing device attempts to start a session with the cache server that has the numerically highest preference value.

Range: 10 through 3600 seconds

Default: 600 seconds

local-address local-ip-address Configure a local IP address of the session to be used for the outgoing connection to the RPKI cache server. If the local cache server has inbound firewall filtering, it might be necessary to specify a local IP address to use for this session.
port port-number Configure an alternative TCP port number to be used for the outgoing connection to the cache server. The well-known resource public key infrastructure (RPKI) port is TCP port 2222. For a given deployment, an RPKI cache server might listen on some other TCP port number. If so, configure the alternative port number with this statement.

Default: 2222

preference number Configure the preference number for the RPKI cache server. Each cache server has a static preference. Higher preferences are preferred. During a session start or restart, the device attempts to start a session with the cache server that has the numerically highest preference. The device connects to multiple cache servers in preference order.

Range: 1 through 255

Default: 100

record-lifetime seconds Configure the amount of time that route validation (RV) records learned from an RPKI cache server remain valid after the session to the cache server goes down. RV records expire if the session to the cache server goes down and remains down for the time configured.

Range: 60 (one minute) through 604800 (one week)

Default: 3600 seconds (one hour)

refresh-time seconds Configure a liveliness check interval for a configured resource public key infrastructure (RPKI) cache server. After every period of time configured on the refresh-time statement (in seconds), a serial query protocol data unit (PDU) with the last known serial number is transmitted. The value configured on the refresh-time statement cannot be longer than half of the value configured on the hold-time statement.

Range: 1 through 1800 seconds

Default: 300 seconds

The remaining statement is 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.