OID reference

tmnxRpkiStaleTimerExpiry

1.3.6.1.4.1.6527.3.1.3.96.0.2

Description

[CAUSE] This 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 backup and refreshes the databases. The stale timer is expired to remove unrefreshed entries in …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.3.96.0 (tmnxRpkiNotifications)
Node code
2
Node name
tmnxRpkiStaleTimerExpiry
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.6527.3.1.3.96.0.2
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.3.96.0.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 3 96 0 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRNotifyPrefix(3) tmnxRpkiNotifyPrefix(96) tmnxRpkiNotifications(0) tmnxRpkiStaleTimerExpiry(2)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/3/96/0/2
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/3/96/0/2
  • /ISO/3/6/1/4/1/6527/3/1/3/96/0/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRNotifyPrefix/tmnxRpkiNotifyPrefix/tmnxRpkiNotifications/tmnxRpkiStaleTimerExpiry

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

tmnxRpkiStaleTimerExpiry · current

tmnxRpkiStaleTimerExpiry  NOTIFICATION-TYPE
    OBJECTS {
              tmnxRpkiPeerAddrType,
              tmnxRpkiPeerAddr
            }
    STATUS        current
    DESCRIPTION
        "[CAUSE] This 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 backup 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.
         [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."
    ::= { tmnxRpkiNotifications 2 }

tmnxRpkiStaleTimerExpiry · current

tmnxRpkiStaleTimerExpiry         NOTIFICATION-TYPE
    OBJECTS     {
        tmnxRpkiPeerAddrType,
        tmnxRpkiPeerAddr
    }
    STATUS      current
    DESCRIPTION
        "[CAUSE] This 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."
    ::= { tmnxRpkiNotifications 2 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

[CAUSE] This 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 backup 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. [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.

Sources for this description

Netdisco MIB archive copies

See 1 matching source record

Description 2

[CAUSE] This 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.

Sources for this description

Nokia networking MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Netdisco MIB archive copies1 record · 1 source

Description 1

tmnxRpkiStaleTimerExpiry · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: tmnxRpkiStaleTimerExpiry

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "tmnxRpkiStaleTimerExpiry",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "tmnxRpkiPeerAddrType",
    ",",
    "tmnxRpkiPeerAddr",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] This 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 backup 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. [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.\"",
    "::=",
    "{",
    "tmnxRpkiNotifications",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "tmnxRpkiPeerAddrType",
        "tmnxRpkiPeerAddr"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] This 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 backup 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. [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."
    ],
    null
  ]
}
Records for description 2Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

tmnxRpkiStaleTimerExpiry · currentNokia networking MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: tmnxRpkiStaleTimerExpiry

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "tmnxRpkiStaleTimerExpiry",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "tmnxRpkiPeerAddrType",
    ",",
    "tmnxRpkiPeerAddr",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"[CAUSE] This 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.\"",
    "::=",
    "{",
    "tmnxRpkiNotifications",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "tmnxRpkiPeerAddrType",
        "tmnxRpkiPeerAddr"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "[CAUSE] This 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."
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Marcelo Mourier

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Jason Sterne

Siblings (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.3.96.0.1 tmnxRpkiNotifySession00