Reference record for OID 1.3.6.1.4.1.52642.2.3.1.1.4.1

Parent
1.3.6.1.4.1.52642.2.3.1.1.4 (fsSysClockProtocolGroup)
Node code
1
Node name
fsSysClockProtocol
Numeric OID
1.3.6.1.4.1.52642.2.3.1.1.4.1
URN notation
urn:oid:1.3.6.1.4.1.52642.2.3.1.1.4.1
ASN.1 notation

{1 3 6 1 4 1 52642 2 3 1 1 4 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsnetworks(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmslocal(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProtocol(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsCommon(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) transmission(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsnetworks(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) nmslocal(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsProtocol(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsCommon(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) transmission(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsnetworks(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) nmslocal(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsProtocol(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsCommon(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) transmission(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) fsnetworks(2) fsSystemMan(3) fsSystemManMIBObjects(1) fsSysClock(1) fsSysClockProtocolGroup(4) fsSysClockProtocol(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/2/3/1/1/4/1
  • /ISO/Identified-Organization/6/1/4/1/52642/2/3/1/1/4/1
  • /ISO/3/6/1/4/1/52642/2/3/1/1/4/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsnetworks/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmslocal/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProtocol/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsCommon/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fs/transmission/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsnetworks/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmslocal/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsProtocol/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsCommon/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/nms/transmission/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsnetworks/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/nmslocal/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsProtocol/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsCommon/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/transmission/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • /iso/identified-organization/dod/internet/private/enterprise/FS/fsnetworks/fsSystemMan/fsSystemManMIBObjects/fsSysClock/fsSysClockProtocolGroup/fsSysClockProtocol
  • Additional combinations skipped.

Descriptions

fsSysClockProtocol — FS.COM official Documentation Hub native MIB packages

Writing none(1) to this object indicates to use the local system time. When the value is set to none(1), fsSysClockProtocolSrcMdc and fsSysClockProtocolSrcContext cannot be written and the value will be set to invalid. Change system time will be performed through the node of fsSysLocalClock and fsSysSummerTime. Writing ntp(2) to this object indicates to use NTP time source. NTP means Network Time Protocol. To get the system time through NTP, NTP must be configured successfully. NTP time source can be obtained from non-default MDC and non-default context. When ntp(2) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing ptp(3) to this object indicates to use PTP time source. PTP means Precision Time Protocol. To get clock time through PTP, PTP must be configured successfully. PTP time source can be obtained from non-default MDC but cannot be obtained from non-default context. When ptp(3) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing interface(4) to this object indicates to get time source from interface. To get clock time through interface, interface must be configured successfully. When interface(4) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing gnss(5) to this object indicates to get time source from Global Natvigtion Satelite System(GNSS).GNSS time source can be obtained from non-default MDC and non-default context. When gnss(5) is set, the system time can't be changed manually. Support for this keyword depends on the device model. All MDCs on the device share the same time source and use the same system time. The shared time source can be one of the following items: Local system time - the time signal that is generated by the local crystal oscillator Remote time source - the time signal that is obtained by the specified MDC from another device on the network.

Source records

fsSysClockProtocol

Status in source: current.

Names: fsSysClockProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsSysClockProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "none",
    "(",
    "1",
    ")",
    ",",
    "ntp",
    "(",
    "2",
    ")",
    ",",
    "ptp",
    "(",
    "3",
    ")",
    ",",
    "interface",
    "(",
    "4",
    ")",
    ",",
    "gnss",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Writing none(1) to this object indicates to use the local system time. When the value is set to none(1), fsSysClockProtocolSrcMdc and fsSysClockProtocolSrcContext cannot be written and the value will be set to invalid. Change system time will be performed through the node of fsSysLocalClock and fsSysSummerTime. Writing ntp(2) to this object indicates to use NTP time source. NTP means Network Time Protocol. To get the system time through NTP, NTP must be configured successfully. NTP time source can be obtained from non-default MDC and non-default context. When ntp(2) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing ptp(3) to this object indicates to use PTP time source. PTP means Precision Time Protocol. To get clock time through PTP, PTP must be configured successfully. PTP time source can be obtained from non-default MDC but cannot be obtained from non-default context. When ptp(3) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing interface(4) to this object indicates to get time source from interface. To get clock time through interface, interface must be configured successfully. When interface(4) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing gnss(5) to this object indicates to get time source from Global Natvigtion Satelite System(GNSS).GNSS time source can be obtained from non-default MDC and non-default context. When gnss(5) is set, the system time can't be changed manually. Support for this keyword depends on the device model. All MDCs on the device share the same time source and use the same system time. The shared time source can be one of the following items: Local system time - the time signal that is generated by the local crystal oscillator Remote time source - the time signal that is obtained by the specified MDC from another device on the network.\"",
    "::=",
    "{",
    "fsSysClockProtocolGroup",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "none",
            1
          ],
          [
            "ntp",
            2
          ],
          [
            "ptp",
            3
          ],
          [
            "interface",
            4
          ],
          [
            "gnss",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Writing none(1) to this object indicates to use the local system time. When the value is set to none(1), fsSysClockProtocolSrcMdc and fsSysClockProtocolSrcContext cannot be written and the value will be set to invalid. Change system time will be performed through the node of fsSysLocalClock and fsSysSummerTime. Writing ntp(2) to this object indicates to use NTP time source. NTP means Network Time Protocol. To get the system time through NTP, NTP must be configured successfully. NTP time source can be obtained from non-default MDC and non-default context. When ntp(2) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing ptp(3) to this object indicates to use PTP time source. PTP means Precision Time Protocol. To get clock time through PTP, PTP must be configured successfully. PTP time source can be obtained from non-default MDC but cannot be obtained from non-default context. When ptp(3) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing interface(4) to this object indicates to get time source from interface. To get clock time through interface, interface must be configured successfully. When interface(4) is set, the system time can't be changed manually. Support for this keyword depends on the device model. Writing gnss(5) to this object indicates to get time source from Global Natvigtion Satelite System(GNSS).GNSS time source can be obtained from non-default MDC and non-default context. When gnss(5) is set, the system time can't be changed manually. Support for this keyword depends on the device model. All MDCs on the device share the same time source and use the same system time. The shared time source can be one of the following items: Local system time - the time signal that is generated by the local crystal oscillator Remote time source - the time signal that is obtained by the specified MDC from another device on the network."
    ],
    null,
    null,
    null,
    null
  ]
}
  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: ies3220-8t4f-switch-snmp-mib-files.zip

    Module: FS-SYS-MAN-MIB

    Published definition
    fsSysClockProtocol OBJECT-TYPE
        SYNTAX INTEGER
            {
            none(1),
            ntp(2),
            ptp(3),
            interface(4),
            gnss(5)
             }
        MAX-ACCESS read-write
        STATUS current
        DESCRIPTION
            "Writing none(1) to this object indicates to use the local system time.
            When the value is set to none(1), fsSysClockProtocolSrcMdc and
            fsSysClockProtocolSrcContext cannot be written and the value will be
            set to invalid.  Change system time will be performed through the node
            of fsSysLocalClock and fsSysSummerTime.
            Writing ntp(2) to this object indicates to use NTP time source.
            NTP means Network Time Protocol.  To get the system time through NTP,
            NTP must be configured successfully.  NTP time source can be obtained
            from non-default MDC and non-default context.
            When ntp(2) is set, the system time can't be changed manually.
            Support for this keyword depends on the device model.
    
            Writing ptp(3) to this object indicates to use PTP time source.
            PTP means Precision Time Protocol.  To get clock time through PTP, PTP
            must be configured successfully.  PTP time source can be obtained from
            non-default MDC but cannot be obtained from non-default context.
            When ptp(3) is set, the system time can't be changed manually.
            Support for this keyword depends on the device model.
    
            Writing interface(4) to this object indicates to get time source from interface.
            To get clock time through interface, interface must be configured successfully.
            When interface(4) is set, the system time can't be changed manually.
            Support for this keyword depends on the device model.
    
            Writing gnss(5) to this object indicates to get time source from Global
            Natvigtion Satelite System(GNSS).GNSS time source can be obtained from
            non-default MDC and non-default context. When gnss(5) is set, the system time
            can't be changed manually.
            Support for this keyword depends on the device model.
    
            All MDCs on the device share the same time source and use the same system time.
            The shared time source can be one of the following items:
            Local system time - the time signal that is generated by the local
            crystal oscillator
            Remote time source - the time signal that is obtained by the specified MDC
            from another device on the network."
        ::= { fsSysClockProtocolGroup 1 }
    Module imports
    {'SNMPv2-TC': ['DateAndTime', 'DisplayString', 'RowStatus', 'TruthValue'], 'FS-OID-MIB': ['fsCommon'], 'SNMPv2-SMI': ['Integer32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'TimeTicks', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'SNMP-TARGET-MIB': ['SnmpTagList', 'SnmpTagValue']}

    Related source files and packages:

    • IES5120-28TF Switch SNMP MIB FilesIES5120-28TF Switch SNMP MIB Files; Models: IES5120-28TF; Catalog updated: 2026-02-27 15:56:52; File: mall/resource/ies5120-28tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:14:36 GMT; 2.6 MiB
    • IES3220-8T4F Switch SNMP MIB FilesIES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:08:16 GMT; 2.6 MiB
    • IES5120-48T4S Switch SNMP MIB FilesIES5120-48T4S Switch SNMP MIB Files; Models: IES5120-48T4S; Catalog updated: 2026-02-27 16:10:26; File: mall/resource/ies5120-48t4s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:16:11 GMT; 2.6 MiB
    Show all 10 related files and packages
    • TSN3220-10S Switch SNMP MIB FilesTSN3220-10S Switch SNMP MIB Files; Models: TSN3220-10S; Catalog updated: 2026-01-08 09:53:00; File: mall/resource/tsn3220-10s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:10:41 GMT; 2.6 MiB
    • IES5120-28TS-P Switch SNMP MIB FilesIES5120-28TS-P Switch SNMP MIB Files; Models: IES5120-28TS-P; Catalog updated: 2026-02-27 16:09:52; File: mall/resource/ies5120-28ts-p-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:40 GMT; 2.6 MiB
    • IES5220-30TS-3ES Switch SNMP MIB FilesIES5220-30TS-3ES Switch SNMP MIB Files; Models: IES5220-30TS-3ES; Catalog updated: 2025-08-19 16:17:18; File: mall/resource/ies5220-30ts-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:17:18 GMT; 2.6 MiB
    • IES5220-6S-3ES Switch SNMP MIB FilesIES5220-6S-3ES Switch SNMP MIB Files; Models: IES5220-6S-3ES; Catalog updated: 2026-02-27 16:11:15; File: mall/resource/ies5220-6s-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:32:47 GMT; 2.6 MiB
    • IES3220-8T4F-U Switch SNMP MIB FilesIES3220-8T4F-U Switch SNMP MIB Files; Models: IES3220-8T4F-U; Catalog updated: 2025-12-03 14:47:49; File: mall/resource/ies3220-8t4f-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:09:07 GMT; 2.6 MiB
    • IES5120-28TS Switch SNMP MIB FilesIES5120-28TS Switch SNMP MIB Files; Models: IES5120-28TS; Catalog updated: 2026-02-27 15:57:39; File: mall/resource/ies5120-28ts-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:08 GMT; 2.6 MiB
    • TSN3220-10S-U Switch SNMP MIB FilesTSN3220-10S-U Switch SNMP MIB Files; Models: TSN3220-10S-U; Catalog updated: 2025-12-16 18:11:48; File: mall/resource/tsn3220-10s-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:13:57 GMT; 2.6 MiB

    Source location: FS-SYS-MAN-MIB::fsSysClockProtocol.
    Source version and references

    Same file in tsn3220-10s-u-switch-snmp-mib-files.zip.

    Same file in tsn3220-10s-switch-snmp-mib-files.zip.

    Same file in ies5220-6s-3es-switch-snmp-mib-files.zip.

    Same file in ies5220-30ts-3es-switch-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:15.736921+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.2.3.1.1.4.2 fsSysClockProtocolSrcMdc00
1.3.6.1.4.1.52642.2.3.1.1.4.3 fsSysClockProtocolSrcContext00