Reference record for OID 1.3.6.1.4.1.65268.1.2.1.1.2.17

Parent
1.3.6.1.4.1.65268.1.2.1.1.2 (gbnPlatformOAMSystem)
Node code
17
Node name
writeConfig
Numeric OID
1.3.6.1.4.1.65268.1.2.1.1.2.17
URN notation
urn:oid:1.3.6.1.4.1.65268.1.2.1.1.2.17
ASN.1 notation

{1 3 6 1 4 1 65268 1 2 1 1 2 17}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) generic(65268) dataCom(1) gbn(2) gbnPlatform(1) gbnPlatformOAM(1) gbnPlatformOAMSystem(2) writeConfig(17)}
OID-IRI notation
  • /1/3/6/1/4/1/65268/1/2/1/1/2/17
  • /ISO/Identified-Organization/6/1/4/1/65268/1/2/1/1/2/17
  • /ISO/3/6/1/4/1/65268/1/2/1/1/2/17
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/identified-organization/dod/internet/private/enterprises/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/identified-organization/dod/internet/private/vendor-objects/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/org/dod/internet/private/enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/org/dod/internet/private/enterprises/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/org/dod/internet/private/ldap-enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/org/dod/internet/private/vendor-objects/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-identified-organization/dod/internet/private/enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-identified-organization/dod/internet/private/enterprises/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-organization/dod/internet/private/enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-organization/dod/internet/private/enterprises/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig
  • /iso/iso-organization/dod/internet/private/vendor-objects/generic/dataCom/gbn/gbnPlatform/gbnPlatformOAM/gbnPlatformOAMSystem/writeConfig

Descriptions

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

When set to 'save(2)', config file is saved to NVM (Nonvolatile Memory). NVM save operations may be slow (e.g., erasing/writing Flash device). Consequently, all or many updates should be made before saving to NVM. Note that the SNMP set to 'save(2)' returns immediately to the caller. Gets on this object then return 'saveInProgress(3)' until the save operation completes, at which time 'noop(1)' is returned if the save operation is succeeded, otherwise 'saveFailed(4)' is returned. Consequently, a get operation always returns 'noop(1)', 'saveInProgress(3)' or 'saveFailed(4) depending on the current state and the result of the save operation. The agent returns 'badValue' for SNMPv1 or 'inconsistentValue' for SNMPv2c/v3 for a set to 'Save(2)' while the current get state is 'saveInProgress(3)'. Attempts to set this object to 'saveInProgress(3)' or 'saveFailed(4)' returns 'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3.

Source records

writeConfig

Status in source: current.

Names: writeConfig

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "writeConfig",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "noop",
    "(",
    "1",
    ")",
    ",",
    "save",
    "(",
    "2",
    ")",
    ",",
    "saveInProgress",
    "(",
    "3",
    ")",
    ",",
    "saveFailed",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"When set to 'save(2)', config file is saved to NVM (Nonvolatile Memory). NVM save operations may be slow (e.g., erasing/writing Flash device). Consequently, all or many updates should be made before saving to NVM. Note that the SNMP set to 'save(2)' returns immediately to the caller. Gets on this object then return 'saveInProgress(3)' until the save operation completes, at which time 'noop(1)' is returned if the save operation is succeeded, otherwise 'saveFailed(4)' is returned. Consequently, a get operation always returns 'noop(1)', 'saveInProgress(3)' or 'saveFailed(4) depending on the current state and the result of the save operation. The agent returns 'badValue' for SNMPv1 or 'inconsistentValue' for SNMPv2c/v3 for a set to 'Save(2)' while the current get state is 'saveInProgress(3)'. Attempts to set this object to 'saveInProgress(3)' or 'saveFailed(4)' returns 'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3.\"",
    "::=",
    "{",
    "gbnPlatformOAMSystem",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "noop",
            1
          ],
          [
            "save",
            2
          ],
          [
            "saveInProgress",
            3
          ],
          [
            "saveFailed",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "When set to 'save(2)', config file is saved to NVM (Nonvolatile Memory). NVM save operations may be slow (e.g., erasing/writing Flash device). Consequently, all or many updates should be made before saving to NVM. Note that the SNMP set to 'save(2)' returns immediately to the caller. Gets on this object then return 'saveInProgress(3)' until the save operation completes, at which time 'noop(1)' is returned if the save operation is succeeded, otherwise 'saveFailed(4)' is returned. Consequently, a get operation always returns 'noop(1)', 'saveInProgress(3)' or 'saveFailed(4) depending on the current state and the result of the save operation. The agent returns 'badValue' for SNMPv1 or 'inconsistentValue' for SNMPv2c/v3 for a set to 'Save(2)' while the current get state is 'saveInProgress(3)'. Attempts to set this object to 'saveInProgress(3)' or 'saveFailed(4)' returns 'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: GBNPlatformOAM-MIB

    Vendor MIB copy from the LibreNMS archive.

    Module: GBNPlatformOAM-MIB

    Published definition
    writeConfig OBJECT-TYPE
            SYNTAX INTEGER {
                   noop(1),             -- no operation
                   save(2),             -- save all configuration parameters to NVM
                   saveInProgress(3),   -- read-only: NVM save in progress
                   saveFailed(4)        -- read-only: NVM save failed
            }
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "When set to 'save(2)', config file is saved to NVM (Nonvolatile 
                 Memory).  NVM save operations may be slow (e.g., erasing/writing 
                 Flash device).
                
                 Consequently, all or many updates should be made before
                 saving to NVM.  Note that the SNMP set to 'save(2)' returns
                 immediately to the caller.  Gets on this object then return
                 'saveInProgress(3)' until the save operation completes, at
                 which time 'noop(1)' is returned if the save operation is
                 succeeded, otherwise 'saveFailed(4)' is returned.  Consequently, 
                 a get operation always returns 'noop(1)', 'saveInProgress(3)' 
                 or 'saveFailed(4) depending on the current state and the result 
                 of the save operation.
                 
                 The agent returns 'badValue' for SNMPv1 or 'inconsistentValue'
                 for SNMPv2c/v3 for a set to 'Save(2)' while the current get
                 state is 'saveInProgress(3)'.
                 
                 Attempts to set this object to 'saveInProgress(3)' or 'saveFailed(4)' 
                 returns 'badValue' for SNMPv1 or 'wrongValue' for SNMPv2c/v3."
            ::= { gbnPlatformOAMSystem 17 }
    Module imports
    {'SNMPv2-TC': ['DisplayString', 'MacAddress', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'IpAddress', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'Q-BRIDGE-MIB': ['PortList', 'dot1qStaticMulticastEntry'], 'GENERIC-MASTER-MIB': ['gbnPlatform'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

    Related source files and packages:


    Source location: GBNPlatformOAM-MIB::writeConfig.
    Source version and references

    Downloaded: 2026-10-24T02:14:16.964281+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.65268)

SHENZHEN FOCUSCOM TECHNOLOGIES CO.,LTD

Siblings (32)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.65268.1.2.1.1.2.1 softwarePlate00
1.3.6.1.4.1.65268.1.2.1.1.2.2 softwareVersion00
1.3.6.1.4.1.65268.1.2.1.1.2.3 softwareCompiledTimeE00
1.3.6.1.4.1.65268.1.2.1.1.2.4 softwareCompiledTimeC00
1.3.6.1.4.1.65268.1.2.1.1.2.5 cpuDescription00
1.3.6.1.4.1.65268.1.2.1.1.2.6 sdramDescription00
1.3.6.1.4.1.65268.1.2.1.1.2.7 flashDescription00
1.3.6.1.4.1.65268.1.2.1.1.2.8 hardwareVersion00
1.3.6.1.4.1.65268.1.2.1.1.2.9 bootromVersion00
1.3.6.1.4.1.65268.1.2.1.1.2.10 hostName00
1.3.6.1.4.1.65268.1.2.1.1.2.11 cpuIdle00
1.3.6.1.4.1.65268.1.2.1.1.2.12 memorySize00
1.3.6.1.4.1.65268.1.2.1.1.2.13 memoryIdle00
1.3.6.1.4.1.65268.1.2.1.1.2.14 systemClock44
1.3.6.1.4.1.65268.1.2.1.1.2.15 productName00
1.3.6.1.4.1.65268.1.2.1.1.2.16 systemReset00
1.3.6.1.4.1.65268.1.2.1.1.2.19 prodSerialNo00
1.3.6.1.4.1.65268.1.2.1.1.2.20 cpuBusyStatus00
1.3.6.1.4.1.65268.1.2.1.1.2.21 cpuBusyAlarmEnable00
1.3.6.1.4.1.65268.1.2.1.1.2.22 cpuBusyThreshold00
1.3.6.1.4.1.65268.1.2.1.1.2.23 cpuUnbusyThreshold00
1.3.6.1.4.1.65268.1.2.1.1.2.24 cpuStatusTrap22
1.3.6.1.4.1.65268.1.2.1.1.2.25 cpuUtilization00
1.3.6.1.4.1.65268.1.2.1.1.2.26 memoryUtilization00
1.3.6.1.4.1.65268.1.2.1.1.2.27 dramAlarmEnable00
1.3.6.1.4.1.65268.1.2.1.1.2.28 dramAlarmThreshold00
1.3.6.1.4.1.65268.1.2.1.1.2.29 dramAlarmLowThreshold00
1.3.6.1.4.1.65268.1.2.1.1.2.30 dramStatus00
1.3.6.1.4.1.65268.1.2.1.1.2.31 dramUtilization00
1.3.6.1.4.1.65268.1.2.1.1.2.32 dramStatusTrap22
1.3.6.1.4.1.65268.1.2.1.1.2.33 cpuTemperature00
1.3.6.1.4.1.65268.1.2.1.1.2.34 boardTemperature00