AT-SETUP-MIB :: backupCnfgPath

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › AT-SETUP-MIB › backupCnfgPath

backupCnfgPath

Module: AT-SETUP-MIB

OID (symbolic): AT-SETUP-MIB::backupCnfgPath

OID (numeric): 1.3.6.1.4.1.207.8.4.4.4.500.3.4.1

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

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.

What is backupCnfgPath?

This read-write text specifies the backup configuration to use if boot config fails. Setting designates the fallback config. Setting "flash:/backup.cfg" uses that as fallback.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.207.8.4.4.4.500.3.4.1
snmpwalk -v2c -c public <target> AT-SETUP-MIB::backupCnfgPath

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.207.8.4.4.4.500.3.4.1.1
snmpget -v2c -c public <target> AT-SETUP-MIB::backupCnfgPath.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.207.8.4.4.4.500.3.4.1.1 s <value>

Start monitoring Allied Telesis managed switches and routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AT-SETUP-MIB::backupCnfgPath OID value, configure state conditions and alerts, and monitor any Allied Telesis managed switches and routers from a single console.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.207alliedTelesynAT-RG600-MIB
1.3.6.1.4.1.207.8mibObjectAT-RG600-MIB
1.3.6.1.4.1.207.8.4brouterMibAT-SMI-MIB
1.3.6.1.4.1.207.8.4.4atRouterAT-SMI-MIB
1.3.6.1.4.1.207.8.4.4.4modulesAT-SMI-MIB
Numeric OIDNameModule
1.3.6.1.4.1.207.8.4.4.4.500setupAT-SETUP-MIB
1.3.6.1.4.1.207.8.4.4.4.500.3deviceConfigurationAT-SETUP-MIB
1.3.6.1.4.1.207.8.4.4.4.500.3.4backupConfigAT-SETUP-MIB
1.3.6.1.4.1.207.8.4.4.4.500.3.4.1backupCnfgPathAT-SETUP-MIB