OID reference

backupPath

1.3.6.1.4.1.207.8.4.4.4.500.2.3.2

Description

The full path of the release file to be used as a backup in the event of the main release file failing to boot. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup path was last set). Only one set operation can be executed at a time across all SNMP users, and an operat…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.500.2.3 (backupFirmware)
Node code
2
Node name
backupPath
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.500.2.3.2
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.500.2.3.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • {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) firmware(2) backupFirmware(3) backupPath(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/500/2/3/2
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/500/2/3/2
  • /ISO/3/6/1/4/1/207/8/4/4/4/500/2/3/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/setup/firmware/backupFirmware/backupPath
  • 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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

backupPath · current

backupPath OBJECT-TYPE
            SYNTAX DisplayString
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "The full path of the release file to be used as a backup in
                the event of the main release file failing to boot. There is no
                guarantee that the file referenced exists (i.e. it may have
                been deleted since the backup 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 backupSetStatus is 'idle'. The path must not
                contain whitespace characters.

                Immediately upon setting this object, the system will attempt
                to set the new backup 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
                backupSetStatus, and the result of the last completed operation
                is indicated by backupLastSetResult.

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

                There are several requirements that must be met in order to set
                a backup release file successfully:
                - The file must exist.
                - The file must be in the root of flash (on the active master
                  in a stacked environment) or card.
                - The file must not be the same as the currently set backup
                  release.
                - The file must have a .rel suffix.
                - The file must be a valid release file.
                - In a stacked environment, there must be enough disk space
                  available to store the release file on each stack member.
                - The device must have a current release license for the
                  specified release."
            ::= { backupFirmware 2 }

backupPath · current

backupPath OBJECT-TYPE
			SYNTAX DisplayString
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
				"The full path of the release to use a backup. There is no guarantee that 
				the file referenced exists in the flash (ie, may have been subsequently 
				deleted).
				
				This object can be set with an empty string in order to clear the current
				backup firmware. Otherwise, the path should be in the form:
				flash:/release.rel.
				
				There are several requirements that must be met in order to set this 
				object:
				- File must exist
				- File must be in the root of the flash
				- File must not be the same one that is set as the next boot release
				- File must have a .rel suffix
				- File must pass several internal checks to ensure it really is a 
				  release file"
			::= { backupFirmware 2 }

Meaning

Descriptions

2 unique

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

Description 1

The full path of the release file to be used as a backup in the event of the main release file failing to boot. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup 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 backupSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup 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 backupSetStatus, and the result of the last completed operation is indicated by backupLastSetResult. This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be of the form 'flash:/filename.rel' or 'card:/filename.rel'. There are several requirements that must be met in order to set a backup release file successfully: - The file must exist. - The file must be in the root of flash (on the active master in a stacked environment) or card. - The file must not be the same as the currently set backup release. - The file must have a .rel suffix. - The file must be a valid release file. - In a stacked environment, there must be enough disk space available to store the release file on each stack member. - The device must have a current release license for the specified release.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Description 2

The full path of the release to use a backup. There is no guarantee that the file referenced exists in the flash (ie, may have been subsequently deleted). This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be in the form: flash:/release.rel. There are several requirements that must be met in order to set this object: - File must exist - File must be in the root of the flash - File must not be the same one that is set as the next boot release - File must have a .rel suffix - File must pass several internal checks to ensure it really is a release file

Sources for this description

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

See 1 matching source record

Evidence

Source records

2 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

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

Status in source: current.

Names: backupPath

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "backupPath",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The full path of the release file to be used as a backup in the event of the main release file failing to boot. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup 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 backupSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup 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 backupSetStatus, and the result of the last completed operation is indicated by backupLastSetResult. This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be of the form 'flash:/filename.rel' or 'card:/filename.rel'. There are several requirements that must be met in order to set a backup release file successfully: - The file must exist. - The file must be in the root of flash (on the active master in a stacked environment) or card. - The file must not be the same as the currently set backup release. - The file must have a .rel suffix. - The file must be a valid release file. - In a stacked environment, there must be enough disk space available to store the release file on each stack member. - The device must have a current release license for the specified release.\"",
    "::=",
    "{",
    "backupFirmware",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The full path of the release file to be used as a backup in the event of the main release file failing to boot. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the backup 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 backupSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new backup 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 backupSetStatus, and the result of the last completed operation is indicated by backupLastSetResult. This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be of the form 'flash:/filename.rel' or 'card:/filename.rel'. There are several requirements that must be met in order to set a backup release file successfully: - The file must exist. - The file must be in the root of flash (on the active master in a stacked environment) or card. - The file must not be the same as the currently set backup release. - The file must have a .rel suffix. - The file must be a valid release file. - In a stacked environment, there must be enough disk space available to store the release file on each stack member. - The device must have a current release license for the specified release."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

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

Status in source: current.

Names: backupPath

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "backupPath",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The full path of the release to use a backup. There is no guarantee that the file referenced exists in the flash (ie, may have been subsequently deleted). This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be in the form: flash:/release.rel. There are several requirements that must be met in order to set this object: - File must exist - File must be in the root of the flash - File must not be the same one that is set as the next boot release - File must have a .rel suffix - File must pass several internal checks to ensure it really is a release file\"",
    "::=",
    "{",
    "backupFirmware",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The full path of the release to use a backup. There is no guarantee that the file referenced exists in the flash (ie, may have been subsequently deleted). This object can be set with an empty string in order to clear the current backup firmware. Otherwise, the path should be in the form: flash:/release.rel. There are several requirements that must be met in order to set this object: - File must exist - File must be in the root of the flash - File must not be the same one that is set as the next boot release - File must have a .rel suffix - File must pass several internal checks to ensure it really is a release file"
    ],
    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.2.3.1 backupVersion00
1.3.6.1.4.1.207.8.4.4.4.500.2.3.3 backupSetStatus00
1.3.6.1.4.1.207.8.4.4.4.500.2.3.4 backupLastSetResult00