show validation session

Session

IP address of the RPKI cache server. You configure the session and all of its elements with the session statement.

State

State of the connection between the routing device and the cache server.

• Up—The session is up and the validation route payload (VRP) database is synchronized with the RPKI cache server.

• Down—The session is down, In other words, the client router cannot communicate effectively with this RPKI cache server because:

  • TCP is down

  • The RPKI cache server is unresponsive. In other words, the RPKI cache server does not send PDUs for a while

• Connect—The connection is not established and the client router retries connecting to the RPKI cache server.

• Ex-Full—The client router requests an immediate full update from the RPKI cache server by sending a “Reset Query”. This state indicates that the router is in the process of receiving cache response PDUs on this session from the cache server with validation records relevant to the query. The “End of Data” PDU indicates the end of responses from the server. When the router receives this PDU, the session moves to the Up state.

• Ex-Incr—The client router requests an incremental update from the RPKI cache server by sending a “Serial Query”. This state indicates that the router is in the process of receiving cache response PDUs on this session from the cache server with validation records relevant to this query. The “End of Data” PDU indicates end of responses from the server. When the router receives this PDU, the session moves to the Up state.

Flaps

Number of attempts to establish a session.

Uptime

Length of time that the session has remained established.

#IPv4/IPv6 records

Number of IPv4 and IPv6 route validation records.

Session index

Every session has an index number.

Group

Name of the group to which the session belongs.

Preference

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

The default preference is 100. The preference is configurable with the preference statement.

Port

TCP port number for the outgoing connection with the cache server. The well-known RPKI port is TCP port 2222. For a given deployment, an RPKI cache server might listen on some other TCP port number. If so, you can configure the alternative port number with the port statement.

Refresh time

Liveliness check interval for an RPKI cache server. Everyrefresh-time (seconds), a serial query protocol data unit (PDU) with the last known serial number is transmitted. The hold-time must be at least 2 x the refresh-time.

Hold time

Length of time in seconds that the session between the routing device and the cache server is considered operational without any activity. After the hold time expires, the session is dropped.

Receiving any PDU from the cache server resets the hold timer. The hold-time is 600 seconds, by default, and must be least 2 x the refresh-time. 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.

Record Life time

Amount of time that route validation (RV) records learned from a cache server are valid. RV records expire if the session to the cache server goes down and remains down for the record-lifetime (seconds).

Serial (Full Update)

Number of full serial updates.

Serial (Incremental Update)

Number of incremental serial updates.

Session flaps

Number of attempts to establish a session.

Session uptime

Length of time that the session has remained established.

Last PDU received

Time when the most recent PDU was received.

IPv4 prefix count

Number of IPv4 sessions.

IPv6 prefix count

Number of IPv6 sessions.

Authentication key-chain

Configured TCP keychain