This document is the SNMP MIB module for the Nokia SROS implementation
of origin validation for rpki session.
Copyright 2003-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
This SNMP MIB module (Specification) embodies Nokia's proprietary
intellectual property. Nokia retains all title and ownership in the
Specification, including any revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied 'as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
tmnxRpkiNotifySession notification is generated when a rpki
session either comes up or goes down. Possible reasons for this to
happen is listed below:
(a) a session goes down due to hold-timer expiry.
(b) a session goes down due to failure of the TCP connection.
(c) a session goes down due to session ID mismatch.
(d) a session goes down due to sent or received Error Report PDU
containing fatal error code
(e) a session comes up (established state)
[EFFECT] This may remove the routes learned from a particular
rpki server if session goes down. Or start learning routes
from a rpki session which was newly established.
[RECOVERY] There is no recovery required for this notification.
tmnxRpkiStaleTimerExpiry
.1.3.6.1.4.1.6527.3.1.3.96.0.2
is notification is generated when a stale timer expires. The
stale timer expires due to the following reasons:
1) The peer goes down, and never comes up within the stale timer
interval
2) Peer goes down and comes back up and refreshes the databases. The
stale timer is expired to remove unrefreshed entries in the database.
3) The peer goes down and comes back again and again goes down before
refreshing any entries. Here again the stale timer is expired due to
unstable connection.
4) The RPKI server sends a Cache Reset in response to a Serial Query
instead of doing an incremental update.
[EFFECT] This may remove the routes learned from a particular
rpki server if session goes down. Or start learning routes
from a rpki session which was newly established.
[RECOVERY] There is no recovery required for this notification.