OID reference

backupCnfgPath

1.3.6.1.4.1.207.8.4.4.4.500.3.4.1

Description

The full path of the backup configuration file to be used the next time the device restarts, if the boot configuration file cannot be accessed. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup configuration path was last set). Only one set operation can be executed …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.500.3.4 (backupConfig)
Node code
1
Node name
backupCnfgPath
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.500.3.4.1
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.500.3.4.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 207 8 4 4 4 500 3 4 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) setup(500) deviceConfiguration(3) backupConfig(4) backupCnfgPath(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/500/3/4/1
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/500/3/4/1
  • /ISO/3/6/1/4/1/207/8/4/4/4/500/3/4/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/setup/deviceConfiguration/backupConfig/backupCnfgPath
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
Status in MIB
current

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.

backupCnfgPath OBJECT-TYPE
            SYNTAX DisplayString
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "The full path of the backup configuration file to be used the
                next time the device restarts, if the boot configuration file
                cannot be accessed. There is no guarantee that the file
                referenced exists (i.e. it may have been deleted since the
                backup configuration path was last set).

                Only one set operation can be executed at a time across all
                SNMP users, and an operation may not be started unless the
                current value of backupCnfgSetStatus is 'idle'. The path must
                not contain whitespace characters.

                Immediately upon setting this object, the system will attempt
                to set the new backup configuration path, and the process will
                continue on the device until it has completed or a failure
                occurs. The current status of the operation can be determined
                by reading backupCnfgSetStatus, and the result of the last
                completed operation is indicated by backupCnfgLastSetResult.

                This object can be set with an empty string in order to clear
                the current backup configuration. Otherwise, the path should be
                of the form 'flash:/filename.cfg' or 'card:/filename.cfg'.

                There are several requirements that must be met in order to set
                a backup configuration file successfully:
                - The file must exist.
                - The file must be in the flash (on the active master in a
                  stacked environment) or card filesystems.
                - The file must have a .cfg suffix.
                - In a stacked environment, there must be enough disk space
                  available to store the configuration file on each stack
                  member."
            ::= { backupConfig 1 }

Meaning

Descriptions

1 unique

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

The full path of the backup configuration file to be used the next time the device restarts, if the boot configuration file cannot be accessed. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup configuration path was last set). Only one set operation can be executed at a time across all SNMP users, and an operation may not be started unless the current value of backupCnfgSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup configuration path, and the process will continue on the device until it has completed or a failure occurs. The current status of the operation can be determined by reading backupCnfgSetStatus, and the result of the last completed operation is indicated by backupCnfgLastSetResult. This object can be set with an empty string in order to clear the current backup configuration. Otherwise, the path should be of the form 'flash:/filename.cfg' or 'card:/filename.cfg'. There are several requirements that must be met in order to set a backup configuration file successfully: - The file must exist. - The file must be in the flash (on the active master in a stacked environment) or card filesystems. - The file must have a .cfg suffix. - In a stacked environment, there must be enough disk space available to store the configuration file on each stack member.

Sources for this description

Multiple manufacturers; see the original MIB 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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

backupCnfgPath · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: backupCnfgPath

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "backupCnfgPath",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The full path of the backup configuration file to be used the next time the device restarts, if the boot configuration file cannot be accessed. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup configuration path was last set). Only one set operation can be executed at a time across all SNMP users, and an operation may not be started unless the current value of backupCnfgSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup configuration path, and the process will continue on the device until it has completed or a failure occurs. The current status of the operation can be determined by reading backupCnfgSetStatus, and the result of the last completed operation is indicated by backupCnfgLastSetResult. This object can be set with an empty string in order to clear the current backup configuration. Otherwise, the path should be of the form 'flash:/filename.cfg' or 'card:/filename.cfg'. There are several requirements that must be met in order to set a backup configuration file successfully: - The file must exist. - The file must be in the flash (on the active master in a stacked environment) or card filesystems. - The file must have a .cfg suffix. - In a stacked environment, there must be enough disk space available to store the configuration file on each stack member.\"",
    "::=",
    "{",
    "backupConfig",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The full path of the backup configuration file to be used the next time the device restarts, if the boot configuration file cannot be accessed. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup configuration path was last set). Only one set operation can be executed at a time across all SNMP users, and an operation may not be started unless the current value of backupCnfgSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup configuration path, and the process will continue on the device until it has completed or a failure occurs. The current status of the operation can be determined by reading backupCnfgSetStatus, and the result of the last completed operation is indicated by backupCnfgLastSetResult. This object can be set with an empty string in order to clear the current backup configuration. Otherwise, the path should be of the form 'flash:/filename.cfg' or 'card:/filename.cfg'. There are several requirements that must be met in order to set a backup configuration file successfully: - The file must exist. - The file must be in the flash (on the active master in a stacked environment) or card filesystems. - The file must have a .cfg suffix. - In a stacked environment, there must be enough disk space available to store the configuration file on each stack member."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.207)

Scott Holley

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.207.8.4.4.4.500.3.4.2 backupCnfgExists00
1.3.6.1.4.1.207.8.4.4.4.500.3.4.3 backupCnfgSetStatus00
1.3.6.1.4.1.207.8.4.4.4.500.3.4.4 backupCnfgLastSetResult00