RPKI-ROUTER-MIB

        This MIB module contains management objects to
support monitoring of the Resource Public Key
Infrastructure (RPKI) protocol on routers.
        
Copyright (c) 2013 IETF Trust and the persons
identified as authors of the code.  All rights
reserved.
        
Redistribution and use in source and binary
forms, with or without modification, is
permitted pursuant to, and subject to the
license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF
Trust's Legal Provisions Relating to IETF
Documents
(http://trustee.ietf.org/license-info).
        
This version of this MIB module is part of
RFC 6945; see the RFC itself for full legal
notices.
    
Source file
RPKI-ROUTER-MIB
Last revised
Identity
rpkiRtrMIB
Base OID
1.3.6.1.2.1.218
Imported Objects
INET-ADDRESS-MIB InetAddress InetAddressPrefixLength InetAddressType InetAutonomousSystemNumber InetPortNumber
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TimeStamp
SYSAPPL-MIB LongUtf8String
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'RPKI-ROUTER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RPKI-ROUTER-MIB::rpkiRtrMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RPKI-ROUTER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RPKI-ROUTER-MIB::rpkiRtrMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
.1.3.6.1.2.1.218
.1.3.6.1.2.1.218.0
.1.3.6.1.2.1.218.1
.1.3.6.1.2.1.218.1.1
.1.3.6.1.2.1.218.1.2
.1.3.6.1.2.1.218.1.2.1
.1.3.6.1.2.1.218.1.2.1.1
.1.3.6.1.2.1.218.1.2.1.10
.1.3.6.1.2.1.218.1.2.1.11
.1.3.6.1.2.1.218.1.2.1.12
.1.3.6.1.2.1.218.1.2.1.13
.1.3.6.1.2.1.218.1.2.1.14
.1.3.6.1.2.1.218.1.2.1.15
.1.3.6.1.2.1.218.1.2.1.16
.1.3.6.1.2.1.218.1.2.1.17
.1.3.6.1.2.1.218.1.2.1.18
.1.3.6.1.2.1.218.1.2.1.19
.1.3.6.1.2.1.218.1.2.1.2
Unsigned32
.1.3.6.1.2.1.218.1.2.1.20
secondsUnsigned32
.1.3.6.1.2.1.218.1.2.1.21
.1.3.6.1.2.1.218.1.2.1.22
Unsigned32
.1.3.6.1.2.1.218.1.2.1.23
Unsigned32
.1.3.6.1.2.1.218.1.2.1.3
.1.3.6.1.2.1.218.1.2.1.4
.1.3.6.1.2.1.218.1.2.1.5
Unsigned32
.1.3.6.1.2.1.218.1.2.1.6
.1.3.6.1.2.1.218.1.2.1.7
.1.3.6.1.2.1.218.1.2.1.8
Enumeration
.1.3.6.1.2.1.218.1.2.1.9
.1.3.6.1.2.1.218.1.3
.1.3.6.1.2.1.218.1.3.1
.1.3.6.1.2.1.218.1.3.1.1
.1.3.6.1.2.1.218.1.3.1.2
.1.3.6.1.2.1.218.1.3.1.3
.1.3.6.1.2.1.218.1.3.1.4
.1.3.6.1.2.1.218.1.3.1.5
.1.3.6.1.2.1.218.1.3.1.6
.1.3.6.1.2.1.218.1.3.1.7
.1.3.6.1.2.1.218.1.3.1.8
.1.3.6.1.2.1.218.1.4
.1.3.6.1.2.1.218.1.4.1
.1.3.6.1.2.1.218.1.4.1.1
.1.3.6.1.2.1.218.1.4.1.2
.1.3.6.1.2.1.218.1.4.1.3
.1.3.6.1.2.1.218.1.4.1.4
Unsigned32
.1.3.6.1.2.1.218.1.4.1.5
Unsigned32
.1.3.6.1.2.1.218.1.4.1.6
.1.3.6.1.2.1.218.2
.1.3.6.1.2.1.218.2.1
.1.3.6.1.2.1.218.2.2
Dependencies (5) 5 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. INET-ADDRESS-MIBrfc
  4. SNMPv2-CONFrfc
  5. SYSAPPL-MIBrfc
  6. RPKI-ROUTER-MIBrfcselected
Type Definitions (1)
Enumeration
ssh(1)
tls(2)
tcpMD5(3)
tcpAO(4)
tcp(5)
ipsec(6)
other(7)
Conformance Groups (4)
The collection of objects to monitor the RPKI peer
connections.
.1.3.6.1.2.1.218.2.2.1
The collection of objects that may help in
debugging the communication between RPKI
clients and cache servers.
.1.3.6.1.2.1.218.2.2.2
The collection of objects that represent
the prefix(es) and their validated Origin
ASes.
.1.3.6.1.2.1.218.2.2.3
The set of notifications to alert an NMS of change
in connections to RPKI cache servers.
.1.3.6.1.2.1.218.2.2.4
Compliance Statements (1)

OID .1.3.6.1.2.1.218.2.1.1
The compliance statement for the rpkiRtrMIB module. There
are only read-only objects in this MIB module, so the
'ReadOnly' in the name of this compliance statement is there
only for clarity and truth in advertising.

There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but for
which there are compliance requirements. Those requirements
and similar requirements for related objects are expressed

below, in pseudo-OBJECT clause form, in this description:

-- OBJECT rpkiRtrCacheServerRemoteAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2), dns(16) }
-- DESCRIPTION
-- The MIB requires support for the IPv4, IPv6, and DNS
-- InetAddressTypes for this object.

-- OBJECT rpkiRtrCacheServerLocalAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2), dns(16) }
-- DESCRIPTION
-- The MIB requires support for the IPv4, IPv6, and DNS
-- InetAddressTypes for this object.

-- OBJECT rpkiRtrPrefixOriginAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- The MIB requires support for the IPv4, and IPv6
-- InetAddressTypes for this object.
Required groups
mandatory rpkiRtrCacheServerGroup
mandatory rpkiRtrPrefixOriginGroup
mandatory rpkiRtrNotificationsGroup
optional rpkiRtrCacheServerErrorsGroup Implementation of this group is optional and
would be useful for debugging.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.2.1.218.0.1
This notification signals a change in the status
of an rpkiRtrCacheServerConnection.

The management agent MUST throttle the generation of
consecutive rpkiRtrCacheServerConnectionStateChange
notifications such that there is at least a 5 second
gap between them.

If more than one notification has occurred locally
during that time, the most recent notification is

sent at the end of the 5 second gap and the others
are discarded.
.1.3.6.1.2.1.218.0.2
This notification signals that an RPKI cache
server connection is about to go stale.
It is suggested that this notification is
generated when the value of the
rpkiRtrCacheServerTimeToRefresh attribute
goes below 60 seconds.

The SNMP agent MUST throttle the generation of
consecutive rpkiRtrCacheServerConnectionToGoStale
notifications such that there is at least a
5 second gap between them.