OID reference

rcNtp

1.3.6.1.4.1.8886.6.1.44

Description

This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware. Below is a brief overview of NTP system architecture and implementation mode…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.8886.6.1 (iscomSwitch)
Node code
44
Node name
rcNtp
Numeric OID
1.3.6.1.4.1.8886.6.1.44
URN notation
urn:oid:1.3.6.1.4.1.8886.6.1.44
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

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

rcNtp   MODULE-IDENTITY
        LAST-UPDATED    "200902090000Z"
        ORGANIZATION    "Raisecom Technology Co., Ltd."
        CONTACT-INFO
                "Raisecom Science & Technology Co., ltd.
                 E-mail: support@raisecom.com"
        DESCRIPTION   "This MIB module defines a MIB which provides
                mechanisms to monitor an NTP server.

                The MIB is derived from the Technical Report
                #Management of the NTP with SNMP# TR No. 98-09
                authored by A.S. Sethi and Dave Mills in the
                University of Delaware.

                Below is a brief overview of NTP system architecture
                and implementation model. This will help understand
                the objects defined below and their relationships.

                NTP Intro:
                The Network Time Protocol (NTP) Version 3, is used to
                synchronize timekeeping among a set of distributed
                time servers and clients.  The service model is based
                on a returnable-time design which depends only on
                measured clock offsets, but does not require reliable
                message delivery.  The synchronization subnet uses a
                self-organizing, hierarchical master-slave
                configuration, with synchronization paths determined
                by a minimum-weight spanning tree.  While multiple
                masters (primary servers) may exist, there is no
                requirement for an election protocol.

                System Archiecture:
                In the NTP model a number of primary reference
                sources, synchronized by wire or radio to national
                standards, are connected to widely accessible
                resources, such as backbone gateways, and operated as
                primary time servers.  The purpose of NTP is to convey
                timekeeping information from these servers to other
                time servers via the Internet and also to cross-check
                clocks and mitigate errors due to equipment or
                propagation failures.  Some number of local-net hosts
                or gateways, acting as secondary time servers, run NTP
                with one or more of the primary servers.  In order to
                reduce the protocol overhead, the secondary servers
                distribute time via NTP to the remaining local-net
                hosts.  In the interest of reliability, selected hosts
                can be equipped with less accurate but less expensive
                radio clocks and used for backup in case of failure of
                the primary and/or secondary servers or communication
                paths between them.

                NTP is designed to produce three products: clock
                offset, round-trip delay and dispersion, all of which
                are relative to a selected reference clock.  Clock
                offset represents the amount to adjust the local clock
                to bring it into correspondence with the reference
                clock.  Roundtrip delay provides the capability to
                launch a message to arrive at the reference clock at a
                specified time.  Dispersion represents the maximum
                error of the local clock relative to the reference
                clock.  Since most host time servers will synchronize
                via another peer time server, there are two components
                in each of these three products, those determined by
                the peer relative to the primary reference source of
                standard time and those measured by the host relative
                to the peer.  Each of these components are maintained
                separately in the protocol in order to facilitate
                error control and management of the subnet itself.  
                They provide not only precision measurements of offset
                and delay, but also definitive maximum error bounds,
                so that the user interface can determine not only the
                time, but the quality of the time as well.

                Implementation Model:
                In what may be the most common client/server model a
                client sends an NTP message to one or more servers and
                processes the replies as received.  The server
                interchanges addresses and ports, overwrites certain
                fields in the message, recalculates the checksum and
                returns the message immediately.  Information included
                in the NTP message allows the client to determine the
                server time with respect to local time and adjust the
                local clock accordingly.  In addition, the message
                includes information to calculate the expected
                timekeeping accuracy and reliability, as well as
                select the best from possibly several servers.

                While the client/server model may suffice for use on
                local nets involving a public server and perhaps many
                workstation clients, the full generality of NTP
                requires distributed participation of a number of
                client/servers or peers arranged in a dynamically
                reconfigurable, hierarchically distributed
                configuration.  It also requires sophisticated
                algorithms for association management, data
                manipulation and local-clock control.

                Glossary:
                1. Host: Refers to an instantiation of the NTP
                        protocol on a local processor.
                2. Peer: Refers to an instantiation of the NTP
                        protocol on a remote processor connected by
                        a network path from the local host."
        REVISION     "200902090000Z"
        DESCRIPTION
            "version 1.0"
        ::= { iscomSwitch 44 }

Meaning

Descriptions

1 unique

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

This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware. Below is a brief overview of NTP system architecture and implementation model. This will help understand the objects defined below and their relationships. NTP Intro: The Network Time Protocol (NTP) Version 3, is used to synchronize timekeeping among a set of distributed time servers and clients. The service model is based on a returnable-time design which depends only on measured clock offsets, but does not require reliable message delivery. The synchronization subnet uses a self-organizing, hierarchical master-slave configuration, with synchronization paths determined by a minimum-weight spanning tree. While multiple masters (primary servers) may exist, there is no requirement for an election protocol. System Archiecture: In the NTP model a number of primary reference sources, synchronized by wire or radio to national standards, are connected to widely accessible resources, such as backbone gateways, and operated as primary time servers. The purpose of NTP is to convey timekeeping information from these servers to other time servers via the Internet and also to cross-check clocks and mitigate errors due to equipment or propagation failures. Some number of local-net hosts or gateways, acting as secondary time servers, run NTP with one or more of the primary servers. In order to reduce the protocol overhead, the secondary servers distribute time via NTP to the remaining local-net hosts. In the interest of reliability, selected hosts can be equipped with less accurate but less expensive radio clocks and used for backup in case of failure of the primary and/or secondary servers or communication paths between them. NTP is designed to produce three products: clock offset, round-trip delay and dispersion, all of which are relative to a selected reference clock. Clock offset represents the amount to adjust the local clock to bring it into correspondence with the reference clock. Roundtrip delay provides the capability to launch a message to arrive at the reference clock at a specified time. Dispersion represents the maximum error of the local clock relative to the reference clock. Since most host time servers will synchronize via another peer time server, there are two components in each of these three products, those determined by the peer relative to the primary reference source of standard time and those measured by the host relative to the peer. Each of these components are maintained separately in the protocol in order to facilitate error control and management of the subnet itself. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the user interface can determine not only the time, but the quality of the time as well. Implementation Model: In what may be the most common client/server model a client sends an NTP message to one or more servers and processes the replies as received. The server interchanges addresses and ports, overwrites certain fields in the message, recalculates the checksum and returns the message immediately. Information included in the NTP message allows the client to determine the server time with respect to local time and adjust the local clock accordingly. In addition, the message includes information to calculate the expected timekeeping accuracy and reliability, as well as select the best from possibly several servers. While the client/server model may suffice for use on local nets involving a public server and perhaps many workstation clients, the full generality of NTP requires distributed participation of a number of client/servers or peers arranged in a dynamically reconfigurable, hierarchically distributed configuration. It also requires sophisticated algorithms for association management, data manipulation and local-clock control. Glossary: 1. Host: Refers to an instantiation of the NTP protocol on a local processor. 2. Peer: Refers to an instantiation of the NTP protocol on a remote processor connected by a network path from the local host.

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

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

Status in source: unspecified.

Names: rcNtp

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "rcNtp",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303930323039303030305a22"
    ],
    "ORGANIZATION",
    "\"Raisecom Technology Co., Ltd.\"",
    "CONTACT-INFO",
    "\"Raisecom Science & Technology Co., ltd. E-mail: support@raisecom.com\"",
    "DESCRIPTION",
    "\"This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware. Below is a brief overview of NTP system architecture and implementation model. This will help understand the objects defined below and their relationships. NTP Intro: The Network Time Protocol (NTP) Version 3, is used to synchronize timekeeping among a set of distributed time servers and clients. The service model is based on a returnable-time design which depends only on measured clock offsets, but does not require reliable message delivery. The synchronization subnet uses a self-organizing, hierarchical master-slave configuration, with synchronization paths determined by a minimum-weight spanning tree. While multiple masters (primary servers) may exist, there is no requirement for an election protocol. System Archiecture: In the NTP model a number of primary reference sources, synchronized by wire or radio to national standards, are connected to widely accessible resources, such as backbone gateways, and operated as primary time servers. The purpose of NTP is to convey timekeeping information from these servers to other time servers via the Internet and also to cross-check clocks and mitigate errors due to equipment or propagation failures. Some number of local-net hosts or gateways, acting as secondary time servers, run NTP with one or more of the primary servers. In order to reduce the protocol overhead, the secondary servers distribute time via NTP to the remaining local-net hosts. In the interest of reliability, selected hosts can be equipped with less accurate but less expensive radio clocks and used for backup in case of failure of the primary and/or secondary servers or communication paths between them. NTP is designed to produce three products: clock offset, round-trip delay and dispersion, all of which are relative to a selected reference clock. Clock offset represents the amount to adjust the local clock to bring it into correspondence with the reference clock. Roundtrip delay provides the capability to launch a message to arrive at the reference clock at a specified time. Dispersion represents the maximum error of the local clock relative to the reference clock. Since most host time servers will synchronize via another peer time server, there are two components in each of these three products, those determined by the peer relative to the primary reference source of standard time and those measured by the host relative to the peer. Each of these components are maintained separately in the protocol in order to facilitate error control and management of the subnet itself. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the user interface can determine not only the time, but the quality of the time as well. Implementation Model: In what may be the most common client/server model a client sends an NTP message to one or more servers and processes the replies as received. The server interchanges addresses and ports, overwrites certain fields in the message, recalculates the checksum and returns the message immediately. Information included in the NTP message allows the client to determine the server time with respect to local time and adjust the local clock accordingly. In addition, the message includes information to calculate the expected timekeeping accuracy and reliability, as well as select the best from possibly several servers. While the client/server model may suffice for use on local nets involving a public server and perhaps many workstation clients, the full generality of NTP requires distributed participation of a number of client/servers or peers arranged in a dynamically reconfigurable, hierarchically distributed configuration. It also requires sophisticated algorithms for association management, data manipulation and local-clock control. Glossary: 1. Host: Refers to an instantiation of the NTP protocol on a local processor. 2. Peer: Refers to an instantiation of the NTP protocol on a remote processor connected by a network path from the local host.\"",
    "REVISION",
    [
      "literal",
      "223230303930323039303030305a22"
    ],
    "DESCRIPTION",
    "\"version 1.0\"",
    "::=",
    "{",
    "iscomSwitch",
    "44",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200902090000Z"
    ],
    [
      "ORGANIZATION",
      "Raisecom Technology Co., Ltd."
    ],
    [
      "CONTACT-INFO",
      "Raisecom Science & Technology Co., ltd. E-mail: support@raisecom.com"
    ],
    [
      "DESCRIPTION",
      "This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware. Below is a brief overview of NTP system architecture and implementation model. This will help understand the objects defined below and their relationships. NTP Intro: The Network Time Protocol (NTP) Version 3, is used to synchronize timekeeping among a set of distributed time servers and clients. The service model is based on a returnable-time design which depends only on measured clock offsets, but does not require reliable message delivery. The synchronization subnet uses a self-organizing, hierarchical master-slave configuration, with synchronization paths determined by a minimum-weight spanning tree. While multiple masters (primary servers) may exist, there is no requirement for an election protocol. System Archiecture: In the NTP model a number of primary reference sources, synchronized by wire or radio to national standards, are connected to widely accessible resources, such as backbone gateways, and operated as primary time servers. The purpose of NTP is to convey timekeeping information from these servers to other time servers via the Internet and also to cross-check clocks and mitigate errors due to equipment or propagation failures. Some number of local-net hosts or gateways, acting as secondary time servers, run NTP with one or more of the primary servers. In order to reduce the protocol overhead, the secondary servers distribute time via NTP to the remaining local-net hosts. In the interest of reliability, selected hosts can be equipped with less accurate but less expensive radio clocks and used for backup in case of failure of the primary and/or secondary servers or communication paths between them. NTP is designed to produce three products: clock offset, round-trip delay and dispersion, all of which are relative to a selected reference clock. Clock offset represents the amount to adjust the local clock to bring it into correspondence with the reference clock. Roundtrip delay provides the capability to launch a message to arrive at the reference clock at a specified time. Dispersion represents the maximum error of the local clock relative to the reference clock. Since most host time servers will synchronize via another peer time server, there are two components in each of these three products, those determined by the peer relative to the primary reference source of standard time and those measured by the host relative to the peer. Each of these components are maintained separately in the protocol in order to facilitate error control and management of the subnet itself. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the user interface can determine not only the time, but the quality of the time as well. Implementation Model: In what may be the most common client/server model a client sends an NTP message to one or more servers and processes the replies as received. The server interchanges addresses and ports, overwrites certain fields in the message, recalculates the checksum and returns the message immediately. Information included in the NTP message allows the client to determine the server time with respect to local time and adjust the local clock accordingly. In addition, the message includes information to calculate the expected timekeeping accuracy and reliability, as well as select the best from possibly several servers. While the client/server model may suffice for use on local nets involving a public server and perhaps many workstation clients, the full generality of NTP requires distributed participation of a number of client/servers or peers arranged in a dynamically reconfigurable, hierarchically distributed configuration. It also requires sophisticated algorithms for association management, data manipulation and local-clock control. Glossary: 1. Host: Refers to an instantiation of the NTP protocol on a local processor. 2. Peer: Refers to an instantiation of the NTP protocol on a remote processor connected by a network path from the local host."
    ],
    [
      "Revisions",
      [
        [
          "200902090000Z",
          [
            "DESCRIPTION",
            "version 1.0"
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.8886)

Gao Lei

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.44.1 rcNtpMIBObjects353

Siblings (63)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.8886.6.1.1 rcSystem8170
1.3.6.1.4.1.8886.6.1.2 rcRateLimit535
1.3.6.1.4.1.8886.6.1.3 rcMacConfig427
1.3.6.1.4.1.8886.6.1.4 rcPortMirror631
1.3.6.1.4.1.8886.6.1.6 rcLinkAggregation, rcTrunk718
1.3.6.1.4.1.8886.6.1.7 rcPortStatistics327
1.3.6.1.4.1.8886.6.1.8 rcSntp28
1.3.6.1.4.1.8886.6.1.9 rcRstp216
1.3.6.1.4.1.8886.6.1.10 rcSnmp29
1.3.6.1.4.1.8886.6.1.11 rcIgmpSnoop919
1.3.6.1.4.1.8886.6.1.12 rcDhcpServer141
1.3.6.1.4.1.8886.6.1.13 rcDhcpRelay123
1.3.6.1.4.1.8886.6.1.14 rcFilter124
1.3.6.1.4.1.8886.6.1.15 rcL3Filter17
1.3.6.1.4.1.8886.6.1.16 rcL3489
1.3.6.1.4.1.8886.6.1.17 rcRip319
1.3.6.1.4.1.8886.6.1.19 rcVlan550
1.3.6.1.4.1.8886.6.1.20 rcIfExtend15
1.3.6.1.4.1.8886.6.1.21 rcMvr273
1.3.6.1.4.1.8886.6.1.22 rmonMib585
1.3.6.1.4.1.8886.6.1.23 rcDhcpSnooping140
1.3.6.1.4.1.8886.6.1.24 rcMstp991
1.3.6.1.4.1.8886.6.1.25 rcDhcpClient124
1.3.6.1.4.1.8886.6.1.26 rcCfm25249
1.3.6.1.4.1.8886.6.1.27 rcDot1x17
1.3.6.1.4.1.8886.6.1.28 rcAutoConfig2224
1.3.6.1.4.1.8886.6.1.29 rcIpDhcpServer366
1.3.6.1.4.1.8886.6.1.30 rcIpDhcpRelay341
1.3.6.1.4.1.8886.6.1.32 rcDot1ag3168
1.3.6.1.4.1.8886.6.1.33 rcLinkStateTrack234
1.3.6.1.4.1.8886.6.1.35 rcRelay421
1.3.6.1.4.1.8886.6.1.36 rcSla8217
1.3.6.1.4.1.8886.6.1.37 rcIpSourceGuard717
1.3.6.1.4.1.8886.6.1.38 rcDai130
1.3.6.1.4.1.8886.6.1.39 rcEthRing250
1.3.6.1.4.1.8886.6.1.40 rcPortBackup216
1.3.6.1.4.1.8886.6.1.41 rcDhcpOption142
1.3.6.1.4.1.8886.6.1.42 rcQinQ2145
1.3.6.1.4.1.8886.6.1.43 rcVlanCfg133
1.3.6.1.4.1.8886.6.1.45 rcExtLoopback212
1.3.6.1.4.1.8886.6.1.47 rcPPPoEAgent518
1.3.6.1.4.1.8886.6.1.49 rcPortsecurity436
1.3.6.1.4.1.8886.6.1.50 rcLbDetect538
1.3.6.1.4.1.8886.6.1.51 rcPoe325
1.3.6.1.4.1.8886.6.1.52 rcRrcp2102
1.3.6.1.4.1.8886.6.1.53 rcErps355
1.3.6.1.4.1.8886.6.1.54 rcElps254
1.3.6.1.4.1.8886.6.1.55 rcCcp149
1.3.6.1.4.1.8886.6.1.57 rcLldp2125
1.3.6.1.4.1.8886.6.1.60 raisecomWred, rcCpuPro115