OID reference

rcNtpPeersMode

1.3.6.1.4.1.8886.6.1.44.1.2.1.1.8

Description

The association mode of the NTP server, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized b…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.8886.6.1.44.1.2.1.1 (rcNtpPeersVarEntry)
Node code
8
Node name
rcNtpPeersMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.8
URN notation
urn:oid:1.3.6.1.4.1.8886.6.1.44.1.2.1.1.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 8886 6 1 44 1 2 1 1 8}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raisecom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) raiseCom(8886) iscomSeries(6) iscomSwitch(1) rcNtp(44) rcNtpMIBObjects(1) rcNtpPeers(2) rcNtpPeersVarTable(1) rcNtpPeersVarEntry(1) rcNtpPeersMode(8)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/8886/6/1/44/1/2/1/1/8
  • /ISO/Identified-Organization/6/1/4/1/8886/6/1/44/1/2/1/1/8
  • /ISO/3/6/1/4/1/8886/6/1/44/1/2/1/1/8
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprises/raisecom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/enterprises/raiseCom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raisecom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/raiseCom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/raisecom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/raiseCom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/org/dod/internet/private/enterprise/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/org/dod/internet/private/enterprise/raisecom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/org/dod/internet/private/enterprise/raiseCom/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • /iso/org/dod/internet/private/enterprises/8886/iscomSeries/iscomSwitch/rcNtp/rcNtpMIBObjects/rcNtpPeers/rcNtpPeersVarTable/rcNtpPeersVarEntry/rcNtpPeersMode
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

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

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: rcNtpPeersAssocId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8886.6.1.44.1.2.1.1.8

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.

The displayed source records contain one distinct definition. Compare its source records.

rcNtpPeersMode OBJECT-TYPE
        SYNTAX      INTEGER { unspecified (0), symmetricActive (1),
                              symmetricPassive (2), client (3),
                              server(4), broadcast (5),
                              reservedControl (6),
                              reservedPrivate (7) }
        MAX-ACCESS  read-create
        STATUS      current
        DESCRIPTION                "The association mode of the NTP server, with values
                coded as follows,
                0, unspecified
                1, symmetric active - A host operating in this mode
                        sends periodic messages regardless of the
                        reachability state or stratum of its peer.  By
                        operating in this mode the host announces its
                        willingness to synchronize and be synchronized
                        by the peer
                2, symmetric passive - This type of association is
                        ordinarily created upon arrival of a message
                        from a peer operating in the symmetric active
                        mode and persists only as long as the peer is
                        reachable and operating at a stratum level
                        less than or equal to the host; otherwise, the
                        association is dissolved.  However, the
                        association will always persist until at least
                        one message has been sent in reply.  By
                        operating in this mode the host announces its
                        willingness to synchronize and be synchronized
                        by the peer
                3, client -  A host operating in this mode sends
                        periodic messages regardless of the
                        reachability state or stratum of its peer.  By
                        operating in this mode the host, usually a LAN
                        workstation, announces its willingness to be
                        synchronized by, but not to synchronize the peer
                4, server - This type of association is ordinarily
                        created upon arrival of a client request message
                        and exists only in order to reply to that
                        request, after which the association is
                        dissolved.  By operating in this mode the host,
                        usually a LAN time server, announces its
                        willingness to synchronize, but not to be
                        synchronized by the peer
                5, broadcast - A host operating in this mode sends
                        periodic messages regardless of the
                        reachability state or stratum of the peers.
                        By operating in this mode the host, usually a
                        LAN time server operating on a high-speed
                        broadcast medium, 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.

                When creating a new peer association, if no value
                is specified for this object, it defaults to
                symmetricActive(1)."
        REFERENCE
                "D.L. Mills, 'Network Time Protocol (Version 3)',
                RFC-1305, March 1992, Section 3.3"
        ::= { rcNtpPeersVarEntry 8 }

Meaning

Descriptions

1 unique

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

The association mode of the NTP server, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, 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. When creating a new peer association, if no value is specified for this object, it defaults to symmetricActive(1).

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

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

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

rcNtpPeersMode · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: rcNtpPeersMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rcNtpPeersMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unspecified",
    "(",
    "0",
    ")",
    ",",
    "symmetricActive",
    "(",
    "1",
    ")",
    ",",
    "symmetricPassive",
    "(",
    "2",
    ")",
    ",",
    "client",
    "(",
    "3",
    ")",
    ",",
    "server",
    "(",
    "4",
    ")",
    ",",
    "broadcast",
    "(",
    "5",
    ")",
    ",",
    "reservedControl",
    "(",
    "6",
    ")",
    ",",
    "reservedPrivate",
    "(",
    "7",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The association mode of the NTP server, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, 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. When creating a new peer association, if no value is specified for this object, it defaults to symmetricActive(1).\"",
    "REFERENCE",
    "\"D.L. Mills, 'Network Time Protocol (Version 3)', RFC-1305, March 1992, Section 3.3\"",
    "::=",
    "{",
    "rcNtpPeersVarEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unspecified",
            0
          ],
          [
            "symmetricActive",
            1
          ],
          [
            "symmetricPassive",
            2
          ],
          [
            "client",
            3
          ],
          [
            "server",
            4
          ],
          [
            "broadcast",
            5
          ],
          [
            "reservedControl",
            6
          ],
          [
            "reservedPrivate",
            7
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The association mode of the NTP server, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reachability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, 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. When creating a new peer association, if no value is specified for this object, it defaults to symmetricActive(1)."
    ],
    [
      "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.8886)

Gao Lei

Siblings (27)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.1 rcNtpPeersAssocId00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.2 rcNtpPeersConfigured00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.3 rcNtpPeersPeerAddress00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.4 rcNtpPeersPeerPort00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.5 rcNtpPeersHostAddress00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.6 rcNtpPeersHostPort00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.7 rcNtpPeersLeap00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.9 rcNtpPeersStratum00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.10 rcNtpPeersPeerPoll00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.11 rcNtpPeersHostPoll00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.12 rcNtpPeersPrecision00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.13 rcNtpPeersRootDelay00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.14 rcNtpPeersRootDispersion00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.15 rcNtpPeersRefId00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.16 rcNtpPeersRefTime00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.17 rcNtpPeersOrgTime00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.18 rcNtpPeersReceiveTime00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.19 rcNtpPeersTransmitTime00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.20 rcNtpPeersUpdateTime00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.21 rcNtpPeersReach00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.22 rcNtpPeersTimer00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.23 rcNtpPeersOffset00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.24 rcNtpPeersDelay00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.25 rcNtpPeersDispersion00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.26 rcNtpPeersFilterValidEntries00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.27 rcNtpPeersEntryStatus00
1.3.6.1.4.1.8886.6.1.44.1.2.1.1.28 rcNtpPeersVersion00