OID reference

tmnxNtpPeersStatus

1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18

Description

The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop,…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.3.1.2.38.3.2.1 (tmnxNtpPeersVarEntry)
Node code
18
Node name
tmnxNtpPeersStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 3 1 2 38 3 2 1 18}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) timetraProducts(3) tmnxSRMIB(1) tmnxSRObjs(2) tmnxNtpObjs(38) tmnxNtpPeers(3) tmnxNtpPeersVarTable(2) tmnxNtpPeersVarEntry(1) tmnxNtpPeersStatus(18)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/2/38/3/2/1/18
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/2/38/3/2/1/18
  • /ISO/3/6/1/4/1/6527/3/1/2/38/3/2/1/18
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersStatus

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current

Enumerated values

ValueName
0reject
1inaccurate
2excess
3outlyer
4candidate
5selected
6syspeer
7ppspeer

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: tmnxNtpPeersVarAssocId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

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

Show 2 published definitions

tmnxNtpPeersStatus · current

tmnxNtpPeersStatus               OBJECT-TYPE
    SYNTAX      INTEGER {
        reject     (0),
        inaccurate (1),
        excess     (2),
        outlyer    (3),
        candidate  (4),
        selected   (5),
        syspeer    (6),
        ppspeer    (7)
    }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of tmnxNtpPeersStatus indicates the status of the peer, with
         values coded as follows:

         0, reject - The peer is rejected and will not be used for
                 synchronization. Rejection reasons could be the peer is
                 unreachable, the peer is synchronized to this local server
                 so synchronizing with it would create a sync loop, or the
                 synchronization distance is too large.
         1, inaccurate - The peer is not maintaining an accurate clock. This
                 peer will not be used for synchronization.
         2, excess - The peer's synchronization distance is greater than ten
                 other peers. This peer will not be used for synchronization.
         3, outlyer - The peer is discarded as an outlyer. This peer will not
                 be used for synchronization.
         4, candidate - The peer is accepted as a possible source of
                 synchronization.
         5, selected - The peer is an acceptable source of synchronization,
                 but it's synchronization distance is greater than six other
                 peers.
         6, syspeer - The peer is chosen as the source of synchronization.
         7, ppspeer - The peer is chosen as the source of synchronization, but
                 the actual synchronization is occurring from a
                 pulse-per-second (PPS) signal."
    ::= { tmnxNtpPeersVarEntry 18 }

tmnxNtpPeersStatus · current

tmnxNtpPeersStatus    OBJECT-TYPE
    SYNTAX      INTEGER {
                    reject (0),
                    inaccurate (1),
                    excess (2),
                    outlyer (3),
                    candidate (4),
                    selected (5),
                    syspeer (6),
                    ppspeer (7)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of tmnxNtpPeersStatus indicates the status of the peer,
        with values coded as follows:

        0, reject - The peer is rejected and will not be used for
                synchronization. Rejection reasons could be the peer is
                unreachable, the peer is synchronized to this local server
                so synchronizing with it would create a sync loop, or the
                synchronization distance is too large.
        1, inaccurate - The peer is not maintaining an accurate clock. This
                peer will not be used for synchronization.
        2, excess - The peer's synchronization distance is greater than ten
                other peers. This peer will not be used for synchronization.
        3, outlyer - The peer is discarded as an outlyer. This peer will not
                be used for synchronization.
        4, candidate - The peer is accepted as a possible source of
                synchronization.
        5, selected - The peer is an acceptable source of synchronization,
                but it's synchronization distance is greater than six other
                peers.
        6, syspeer - The peer is chosen as the source of synchronization.
        7, ppspeer - The peer is chosen as the source of synchronization, but
                the actual synchronization is occurring from a
                pulse-per-second (PPS) signal.
        "
    ::= { tmnxNtpPeersVarEntry 18 }

Meaning

Descriptions

1 unique

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

The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal.

Sources for this description

Netdisco MIB archive copiesNokia networking MIB copies (LibreNMS/Observium Community)

See 2 matching source records

Evidence

Source records

2 records

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

Records for description 1Netdisco MIB archive copies, Nokia networking MIB copies (LibreNMS/Observium Community)2 records · 2 sources

Description 1

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

Status in source: current.

Names: tmnxNtpPeersStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxNtpPeersStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "reject",
    "(",
    "0",
    ")",
    ",",
    "inaccurate",
    "(",
    "1",
    ")",
    ",",
    "excess",
    "(",
    "2",
    ")",
    ",",
    "outlyer",
    "(",
    "3",
    ")",
    ",",
    "candidate",
    "(",
    "4",
    ")",
    ",",
    "selected",
    "(",
    "5",
    ")",
    ",",
    "syspeer",
    "(",
    "6",
    ")",
    ",",
    "ppspeer",
    "(",
    "7",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal.\"",
    "::=",
    "{",
    "tmnxNtpPeersVarEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "reject",
            0
          ],
          [
            "inaccurate",
            1
          ],
          [
            "excess",
            2
          ],
          [
            "outlyer",
            3
          ],
          [
            "candidate",
            4
          ],
          [
            "selected",
            5
          ],
          [
            "syspeer",
            6
          ],
          [
            "ppspeer",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal."
    ],
    null,
    null,
    null,
    null
  ]
}
tmnxNtpPeersStatus · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: tmnxNtpPeersStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxNtpPeersStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "reject",
    "(",
    "0",
    ")",
    ",",
    "inaccurate",
    "(",
    "1",
    ")",
    ",",
    "excess",
    "(",
    "2",
    ")",
    ",",
    "outlyer",
    "(",
    "3",
    ")",
    ",",
    "candidate",
    "(",
    "4",
    ")",
    ",",
    "selected",
    "(",
    "5",
    ")",
    ",",
    "syspeer",
    "(",
    "6",
    ")",
    ",",
    "ppspeer",
    "(",
    "7",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal. \"",
    "::=",
    "{",
    "tmnxNtpPeersVarEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "reject",
            0
          ],
          [
            "inaccurate",
            1
          ],
          [
            "excess",
            2
          ],
          [
            "outlyer",
            3
          ],
          [
            "candidate",
            4
          ],
          [
            "selected",
            5
          ],
          [
            "syspeer",
            6
          ],
          [
            "ppspeer",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows: 0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal."
    ],
    null,
    null,
    null,
    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 (19)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.1 tmnxNtpPeersVarAssocId00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.2 tmnxNtpPeersConfigured00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.3 tmnxNtpPeersPeerAddrType00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.4 tmnxNtpPeersPeerAddress00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.5 tmnxNtpPeersPeerPort00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.6 tmnxNtpPeersHostAddrType00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.7 tmnxNtpPeersHostAddress00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.8 tmnxNtpPeersHostPort00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9 tmnxNtpPeersMode00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.10 tmnxNtpPeersStratum00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.11 tmnxNtpPeersPeerPoll00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.12 tmnxNtpPeersHostPoll00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.13 tmnxNtpPeersRefId00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.14 tmnxNtpPeersReceiveTime00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.15 tmnxNtpPeersReach00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.16 tmnxNtpPeersOffset00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.17 tmnxNtpPeersPrefPeer00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.19 tmnxNtpPeersStatusFlags00
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.20 tmnxNtpPeersPeerVRtrID00