OID reference

hwNTPPeerPMode

1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.32

Description

This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be s…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1 (hwNTPPeerEntry)
Node code
32
Node name
hwNTPPeerPMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.32
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.32
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 5 25 22 2 1 1 1 32}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) huaweiMgmt(5) huaweiDatacomm(25) hwNTP(22) hwNTPPeerMIB(2) hwNTPPeerMIBObjects(1) hwNTPPeerTable(1) hwNTPPeerEntry(1) hwNTPPeerPMode(32)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/5/25/22/2/1/1/1/32
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/5/25/22/2/1/1/1/32
  • /ISO/3/6/1/4/1/43/45/1/5/25/22/2/1/1/1/32
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/huaweiMgmt/huaweiDatacomm/hwNTP/hwNTPPeerMIB/hwNTPPeerMIBObjects/hwNTPPeerTable/hwNTPPeerEntry/hwNTPPeerPMode
  • Additional combinations skipped.

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

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.

In A3COM-HUAWEI-NTP-MIB, the row index consists of these components in order:

  1. hwNTPPeerRemAdr (IpAddress): four numeric subidentifiers, one per IPv4 address octet.
  2. hwNTPPeerHMode (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.32.<hwNTPPeerRemAdr: four octets>.<hwNTPPeerHMode>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.32

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

hwNTPPeerPMode · current

hwNTPPeerPMode OBJECT-TYPE
        SYNTAX INTEGER
            {
                unspecified (0),
                symmetricActive (1),
                symmetricPassive (2),
                client (3),
                server(4),
                broadcast (5),
                reservedControl (6),
                reservedPrivate (7),
                broadcastclient (8),
                multicastclient (9)
            }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "This is an integer indicating the association mode,
            with values coded as follows,
            0, unspecified
            1, symmetric active - A host operating in this mode
                    sends periodic messages regardless of the
                    reach ability 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
                    reach ability 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
                    reach ability 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
            8, broadcastclient
            9, multicastclient
            When creating a new peer association, if no value
            is specified for this object, it defaults to
            'symmetricActive'."
        ::= { hwNTPPeerEntry 32 }

hwNTPPeerPMode · current

hwNTPPeerPMode OBJECT-TYPE
        SYNTAX INTEGER
            {
                unspecified (0),
                symmetricActive (1),
                symmetricPassive (2),
                client (3),
                server(4),
                broadcast (5),
                reservedControl (6),
                reservedPrivate (7),
                broadcastclient (8),
                multicastclient (9)
            }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
            "This is an integer indicating the association mode,
            with values coded as follows,
            0, unspecified
            1, symmetric active - A host operating in this mode
                    sends periodic messages regardless of the
                    reach ability 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
                    reach ability 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
                    reach ability 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
            8, broadcastclient
            9, multicastclient
            When creating a new peer association, if no value
            is specified for this object, it defaults to
            'symmetricActive'."
        ::= { hwNTPPeerEntry 32 }

Meaning

Descriptions

1 unique

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

This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability 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 reach ability 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 reach ability 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 8, broadcastclient 9, multicastclient When creating a new peer association, if no value is specified for this object, it defaults to 'symmetricActive'.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

hwNTPPeerPMode · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: hwNTPPeerPMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hwNTPPeerPMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "unspecified",
    "(",
    "0",
    ")",
    ",",
    "symmetricActive",
    "(",
    "1",
    ")",
    ",",
    "symmetricPassive",
    "(",
    "2",
    ")",
    ",",
    "client",
    "(",
    "3",
    ")",
    ",",
    "server",
    "(",
    "4",
    ")",
    ",",
    "broadcast",
    "(",
    "5",
    ")",
    ",",
    "reservedControl",
    "(",
    "6",
    ")",
    ",",
    "reservedPrivate",
    "(",
    "7",
    ")",
    ",",
    "broadcastclient",
    "(",
    "8",
    ")",
    ",",
    "multicastclient",
    "(",
    "9",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability 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 reach ability 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 reach ability 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 8, broadcastclient 9, multicastclient When creating a new peer association, if no value is specified for this object, it defaults to 'symmetricActive'.\"",
    "::=",
    "{",
    "hwNTPPeerEntry",
    "32",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unspecified",
            0
          ],
          [
            "symmetricActive",
            1
          ],
          [
            "symmetricPassive",
            2
          ],
          [
            "client",
            3
          ],
          [
            "server",
            4
          ],
          [
            "broadcast",
            5
          ],
          [
            "reservedControl",
            6
          ],
          [
            "reservedPrivate",
            7
          ],
          [
            "broadcastclient",
            8
          ],
          [
            "multicastclient",
            9
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability 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 reach ability 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 reach ability 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 8, broadcastclient 9, multicastclient When creating a new peer association, if no value is specified for this object, it defaults to 'symmetricActive'."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (35)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.1 hwNTPPeerConfig00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.2 hwNTPPeerAuthenable00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.3 hwNTPPeerAuthentic00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.4 hwNTPPeerRemAdr00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.5 hwNTPPeerRemPort00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.6 hwNTPPeerLocAdr00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.7 hwNTPPeerLocPort00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.8 hwNTPPeerLeap00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.9 hwNTPPeerHMode00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.10 hwNTPPeerStratum00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.11 hwNTPPeerPPoll00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.12 hwNTPPeerHPoll00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.13 hwNTPPeerPrecision00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.14 hwNTPPeerRootDelay00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.15 hwNTPPeerRootDispersion00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.16 hwNTPPeerRefId00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.17 hwNTPPeerRefTime00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.18 hwNTPPeerOrg00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.19 hwNTPPeerRec00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.20 hwNTPPeerXmt00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.21 hwNTPPeerReach00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.22 hwNTPPeerValid00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.23 hwNTPPeerTimer00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.24 hwNTPPeerDelay00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.25 hwNTPPeerOffset00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.26 hwNTPPeerJitter00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.27 hwNTPPeerDispersion00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.28 hwNTPPeerKeyId00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.29 hwNTPPeerFiltDelay00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.30 hwNTPPeerFiltOffset00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.31 hwNTPPeerFiltError00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.33 hwNTPPeerReceived00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.34 hwNTPPeerSent00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.35 hwNTPPeerFlash00
1.3.6.1.4.1.43.45.1.5.25.22.2.1.1.1.36 hwNTPPeerRowStatus00