OID reference

tmnxNtpPeersMode

1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9

Description

The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric pa…

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
9
Node name
tmnxNtpPeersMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9
URN notation
urn:oid:1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9
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 9}

  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
  • {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) tmnxNtpPeersMode(9)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/3/1/2/38/3/2/1/9
  • /ISO/Identified-Organization/6/1/4/1/6527/3/1/2/38/3/2/1/9
  • /ISO/3/6/1/4/1/6527/3/1/2/38/3/2/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/org/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/org/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/org/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/timetraProducts/tmnxSRMIB/tmnxSRObjs/tmnxNtpObjs/tmnxNtpPeers/tmnxNtpPeersVarTable/tmnxNtpPeersVarEntry/tmnxNtpPeersMode

SNMP properties

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

Enumerated values

ValueName
0unspecified
1symmetricActive
2symmetricPassive
3client
4server
5broadcast
6reservedControl
7reservedPrivate
8broadcastclient

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.9

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

tmnxNtpPeersMode · current

tmnxNtpPeersMode                 OBJECT-TYPE
    SYNTAX      INTEGER {
        unspecified      (0),
        symmetricActive  (1),
        symmetricPassive (2),
        client           (3),
        server           (4),
        broadcast        (5),
        reservedControl  (6),
        reservedPrivate  (7),
        broadcastclient  (8)
    }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of tmnxNtpPeersMode indicates the association mode, with
         values coded as follows:

         0, unspecified
         1, symmetric active - The host sends periodic messages regardless
                 of the reachability state or stratum of this peer and so
                 announces its willingness to synchronize and be synchronized
                 by the peer.
         2, symmetric passive - This association type is created upon receipt
                 of a message from a peer operating in the symmetric active
                 mode and lasts as long as the peer is reachable and operating
                 at a stratum level less than or equal to the host.  Else the
                 association is dissolved.  Such an association always lasts
                 until at least one message has been sent in reply.  A host in
                 this mode announces its willingness to synchronize and be
                 synchronized by the peer.
         3, client - Periodic messages are sent regardless of the reachability
                 state or stratum of the peer.  A host in this mode announces
                 its willingness to be synchronized by but not to synchronize
                 the peer.
         4, server - This association is created upon receipt of a client
                 request message and exists only in order to reply to that
                 request, after which the association is dissolved.  A host
                 in this mode announces its willingness to synchronize,
                 but not to be synchronized by the peer.
         5, broadcast - Periodic messages are sent regardless of the
                 reachability state or stratum of the peers.  A host in this
                 mode announces its willingness to synchronize all of the
                 peers but not to be synchronized by any of them.
         6, reserved for NTP control messages
         7, reserved for private use
         8, broadcastclient - Messages are sent only in response to messages
                 received from a broadcast server. A host in this mode is
                 willing to be synchronized by any broadcast server."
    REFERENCE
        "D.L. Mills, 'Network Time Protocol (Version 3)',
         RFC-1305, March 1992, Section 3.3"
    ::= { tmnxNtpPeersVarEntry 9 }

tmnxNtpPeersMode · current

tmnxNtpPeersMode OBJECT-TYPE
    SYNTAX      INTEGER {
                    unspecified (0),
                    symmetricActive (1),
                    symmetricPassive (2),
                    client (3),
                    server (4),
                    broadcast (5),
                    reservedControl (6),
                    reservedPrivate (7),
                    broadcastclient (8)
                }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The value of tmnxNtpPeersMode indicates the association mode,
        with values coded as follows:

        0, unspecified
        1, symmetric active - The host sends periodic messages regardless
                of the reachability state or stratum of this peer and so
                announces its willingness to synchronize and be synchronized
                by the peer.
        2, symmetric passive - This association type is created upon receipt
                of a message from a peer operating in the symmetric active
                mode and lasts as long as the peer is reachable and operating
                at a stratum level less than or equal to the host.  Else the
                association is dissolved.  Such an association always lasts
                until at least one message has been sent in reply.  A host in
                this mode announces its willingness to synchronize and be
                synchronized by the peer.
        3, client - Periodic messages are sent regardless of the reachability
                state or stratum of the peer.  A host in this mode announces
                its willingness to be synchronized by but not to synchronize
                the peer.
        4, server - This association is created upon receipt of a client
                request message and exists only in order to reply to that
                request, after which the association is dissolved.  A host
                in this mode announces its willingness to synchronize,
                but not to be synchronized by the peer.
        5, broadcast - Periodic messages are sent regardless of the
                reachability state or stratum of the peers.  A host in this
                mode announces its willingness to synchronize all of the
                peers but not to be synchronized by any of them.
        6, reserved for NTP control messages
        7, reserved for private use
        8, broadcastclient - Messages are sent only in response to messages
                received from a broadcast server. A host in this mode is
                willing to be synchronized by any broadcast server.
        "
    REFERENCE
        "D.L. Mills, 'Network Time Protocol (Version 3)',
        RFC-1305, March 1992, Section 3.3"
    ::= { tmnxNtpPeersVarEntry 9 }

Meaning

Descriptions

1 unique

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

The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server.

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

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

Status in source: current.

Names: tmnxNtpPeersMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxNtpPeersMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unspecified",
    "(",
    "0",
    ")",
    ",",
    "symmetricActive",
    "(",
    "1",
    ")",
    ",",
    "symmetricPassive",
    "(",
    "2",
    ")",
    ",",
    "client",
    "(",
    "3",
    ")",
    ",",
    "server",
    "(",
    "4",
    ")",
    ",",
    "broadcast",
    "(",
    "5",
    ")",
    ",",
    "reservedControl",
    "(",
    "6",
    ")",
    ",",
    "reservedPrivate",
    "(",
    "7",
    ")",
    ",",
    "broadcastclient",
    "(",
    "8",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server.\"",
    "REFERENCE",
    "\"D.L. Mills, 'Network Time Protocol (Version 3)', RFC-1305, March 1992, Section 3.3\"",
    "::=",
    "{",
    "tmnxNtpPeersVarEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unspecified",
            0
          ],
          [
            "symmetricActive",
            1
          ],
          [
            "symmetricPassive",
            2
          ],
          [
            "client",
            3
          ],
          [
            "server",
            4
          ],
          [
            "broadcast",
            5
          ],
          [
            "reservedControl",
            6
          ],
          [
            "reservedPrivate",
            7
          ],
          [
            "broadcastclient",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server."
    ],
    [
      "REFERENCE",
      "D.L. Mills, 'Network Time Protocol (Version 3)', RFC-1305, March 1992, Section 3.3"
    ],
    null,
    null,
    null
  ]
}
tmnxNtpPeersMode · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: tmnxNtpPeersMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tmnxNtpPeersMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unspecified",
    "(",
    "0",
    ")",
    ",",
    "symmetricActive",
    "(",
    "1",
    ")",
    ",",
    "symmetricPassive",
    "(",
    "2",
    ")",
    ",",
    "client",
    "(",
    "3",
    ")",
    ",",
    "server",
    "(",
    "4",
    ")",
    ",",
    "broadcast",
    "(",
    "5",
    ")",
    ",",
    "reservedControl",
    "(",
    "6",
    ")",
    ",",
    "reservedPrivate",
    "(",
    "7",
    ")",
    ",",
    "broadcastclient",
    "(",
    "8",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server. \"",
    "REFERENCE",
    "\"D.L. Mills, 'Network Time Protocol (Version 3)', RFC-1305, March 1992, Section 3.3\"",
    "::=",
    "{",
    "tmnxNtpPeersVarEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unspecified",
            0
          ],
          [
            "symmetricActive",
            1
          ],
          [
            "symmetricPassive",
            2
          ],
          [
            "client",
            3
          ],
          [
            "server",
            4
          ],
          [
            "broadcast",
            5
          ],
          [
            "reservedControl",
            6
          ],
          [
            "reservedPrivate",
            7
          ],
          [
            "broadcastclient",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows: 0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server."
    ],
    [
      "REFERENCE",
      "D.L. Mills, 'Network Time Protocol (Version 3)', RFC-1305, March 1992, Section 3.3"
    ],
    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.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.18 tmnxNtpPeersStatus00
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