All MIBs › AT-SETUP-MIB
Organization: Allied Telesis, Inc.
Last Updated: 2013-10-14
Category: Device Management, Vendor: Allied Telesis
Description: Manages initial device setup parameters including hostname, IP configuration, and access credentials on Allied Telesis equipment.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is AT-SETUP-MIB?
AT-SETUP-MIB is an Allied Telesis enterprise MIB covering initial device setup and software/configuration-file management, including parameters like hostname, IP configuration, and access credentials used when bringing a switch or router online. It exposes configuration-oriented objects for installing and managing software and configuration files rather than ongoing performance counters. Its monitoring value is mainly around software/configuration status — confirming the device has the correct configuration file loaded/active and that basic setup parameters (network identity, management access) are correctly applied, foundational to confirming a device came up correctly after provisioning or a config push. No specific external MIB dependency is indicated in the source, though it complements standard system MIBs (SNMPv2-MIB) for full device identification. It's used during initial provisioning and ongoing configuration-file management of Allied Telesis switches and routers. Engineers can download the AT-SETUP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in AT-SETUP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Allied Telesis switch/router
Monitoring Examples
No specific table/object names were included in the available metadata for this module, so a concrete polling example can't be grounded in real identifiers; in general terms, an operator would use this module's setup objects to confirm the active configuration file and basic network parameters (hostname, IP address) on a newly provisioned Allied Telesis device match the intended baseline before it's put into production.
What Can Be Monitored
- active configuration file
- hostname/IP setup parameters
- software installation status
This MIB depends on
Related MIBs
Imported Objects
From AT-SMI-MIB
| modules | OBJECT-IDENTITY |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| setup | 1.3.6.1.4.1.207.8.4.4.4.500 | The AT Setup MIB for managing the software installation and configuration files. | ||
| I32 restartDevice | 1.3.6.1.4.1.207.8.4.4.4.500.1 | Integer32 | read-write | This object forces a standalone unit or stack of devices to restart immediately when set with a value of 1. For a chassis switch, this object causes the whole chassis to restart immediately. Reading the object will always return zero. NOTE: This object has been replaced by the restartStkMemberDevice object. |
| firmware | 1.3.6.1.4.1.207.8.4.4.4.500.2 | |||
| currentFirmware | 1.3.6.1.4.1.207.8.4.4.4.500.2.1 | |||
| STR currSoftVersion | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.1 | DisplayString | read-only | The major.minor.interim version of the firmware that the device is currently running. Will return 0 if the version cannot be determined. |
| STR currSoftName | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.2 | DisplayString | read-only | The name of the firmware that the device is currently running. |
| STR currSoftSaveAs | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.3 | DisplayString | read-write | Set with a filename to save the currently running software to the root of flash. Only one save operation can be executed at a time across all SNMP users, and the filename must not contain whitespace characters. Immediately upon executing the set action, the actual firmware save operation will be started and continue on the device until it has completed or a failure occurs. Subsequent reads of the object will return one of several results: saving x A saving operation is currently in progress. Another save cannot be started while the object is returning this value. x success The last save operation was successfully completed. x failure: [error] The last save operation failed, due to the descriptive message attached. The most common failure is lack of disk space. idle There is no save operation in progress and a new one may be started. Upon reading a success or failure message, the message will be cleared and the next read will result in an 'idle' message. A new save operation can now be executed. NOTE: This object has been replaced by objects currSoftSaveToFile, currSoftSaveStatus and currSoftLastSaveResult. |
| STR currSoftSaveToFile | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.4 | DisplayString | read-write | Set with a URL (e.g. 'flash:/filename.rel' or 'card:/filename.rel') to save the currently running software to the root of flash or SD card. Only one save operation can be executed at a time across all SNMP users, and an operation may not be started unless the current value of currSoftSaveStatus is 'idle'. The URL must not contain whitespace characters. Immediately upon executing the set action, the actual firmware save operation will be started and continue on the device until it has completed or a failure occurs. The current status of the operation can be determined by reading currSoftSaveStatus, and the result of the last completed operation is indicated by currSoftLastSaveResult. When read, this object will return the URL of the last firmware save operation that was attempted. |
| SYS currSoftSaveStatus | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.5 | SystemFileOperationType | read-only | Returns the status of any current operation to store the running software to a release file. The following values may be returned: 1 (idle) There is no release file save operation in progress. 2 (success) The last release file save operation completed successfully. 3 (failure) The last release file save operation failed. 4 (saving) A release file save operation is currently in progress. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading currSoftLastSaveResult. |
| STR currSoftLastSaveResult | 1.3.6.1.4.1.207.8.4.4.4.500.2.1.6 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to save the running firmware to a release file. |
| nextBootFirmware | 1.3.6.1.4.1.207.8.4.4.4.500.2.2 | |||
| STR nextBootVersion | 1.3.6.1.4.1.207.8.4.4.4.500.2.2.1 | DisplayString | read-only | The major.minor.interim version of the firmware that the device is currently set to boot from. Will return 0 if the version cannot be determined. |
| STR nextBootPath | 1.3.6.1.4.1.207.8.4.4.4.500.2.2.2 | DisplayString | read-write | The full path of the release to be used the next time the device restarts. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the boot 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 nextBootSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new boot 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 nextBootSetStatus, and the result of the last completed operation is indicated by nextBootLastSetResult. This object can be set with an empty string in order to clear the current boot 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 boot 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. |
| SYS nextBootSetStatus | 1.3.6.1.4.1.207.8.4.4.4.500.2.2.3 | SystemFileOperationType | read-only | Returns the status of any current operation to set the next boot release file. The following values may be returned: 1 (idle) There is no boot release setting operation in progress. 2 (success) The last boot release setting operation completed successfully. 3 (failure) The last boot release setting operation failed. 5 (syncing) A boot release setting operation is currently in progress and the file is being syncronised across the stack or system. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading nextBootLastSetResult. |
| STR nextBootLastSetResult | 1.3.6.1.4.1.207.8.4.4.4.500.2.2.4 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to set the boot release filename. |
| backupFirmware | 1.3.6.1.4.1.207.8.4.4.4.500.2.3 | |||
| STR backupVersion | 1.3.6.1.4.1.207.8.4.4.4.500.2.3.1 | DisplayString | read-only | The major.minor.interim version of the firmware that the device will boot from as a backup. This will return 0 if the version cannot be determined. |
| STR backupPath | 1.3.6.1.4.1.207.8.4.4.4.500.2.3.2 | DisplayString | read-write | 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. |
| SYS backupSetStatus | 1.3.6.1.4.1.207.8.4.4.4.500.2.3.3 | SystemFileOperationType | read-only | Returns the status of any current operation to set the backup boot release file. The following values may be returned: 1 (idle) There is no backup boot release setting operation in progress. 2 (success) The last backup boot release setting operation completed successfully. 3 (failure) The last backup boot release setting operation failed. 5 (syncing) A backup boot release setting operation is currently in progress and the file is being syncronised across the stack or system. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading backupLastSetResult. |
| STR backupLastSetResult | 1.3.6.1.4.1.207.8.4.4.4.500.2.3.4 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to set the backup boot release filename. |
| deviceConfiguration | 1.3.6.1.4.1.207.8.4.4.4.500.3 | |||
| runningConfig | 1.3.6.1.4.1.207.8.4.4.4.500.3.1 | |||
| STR runCnfgSaveAs | 1.3.6.1.4.1.207.8.4.4.4.500.3.1.1 | DisplayString | read-write | Set with a URL to save the running configuration to the flash or card filesystem using that filename (e.g. 'flash:/myconfig.cfg' or 'card:/myconfig.cfg'). 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 runCnfgSaveAsStatus is 'idle'. The URL must not contain whitespace characters. Immediately upon setting this object, the system will attempt to save the running configuration, 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 runCnfgSaveAsStatus, and the result of the last completed operation is indicated by runCnfgLastSaveResult. When read, this object will return the URL of the last configuration save operation that was attempted. |
| SYS runCnfgSaveAsStatus | 1.3.6.1.4.1.207.8.4.4.4.500.3.1.2 | SystemFileOperationType | read-only | Returns the status of any current operation to save the running configuration. The following values may be returned: 1 (idle) There is no config file save operation in progress. 2 (success) The last config file save operation completed successfully. 3 (failure) The last config file save operation failed. 4 (saving) A config file save operation is currently in progress. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading runCnfgLastSaveResult. |
| STR runCnfgLastSaveResult | 1.3.6.1.4.1.207.8.4.4.4.500.3.1.3 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to save the running configuration. |
| nextBootConfig | 1.3.6.1.4.1.207.8.4.4.4.500.3.2 | |||
| STR bootCnfgPath | 1.3.6.1.4.1.207.8.4.4.4.500.3.2.1 | DisplayString | read-write | The full path of the configuration file to be used the next time the device restarts. There is no guarantee that the file referenced exists (i.e. it may have been deleted since the 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 bootCnfgSetStatus is 'idle'. The path must not contain whitespace characters. Immediately upon setting this object, the system will attempt to set the new 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 bootCnfgSetStatus, and the result of the last completed operation is indicated by bootCnfgLastSetResult. This object can be set with an empty string in order to clear the current boot 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 boot 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. |
| T/F bootCnfgExists | 1.3.6.1.4.1.207.8.4.4.4.500.3.2.2 | TruthValue | read-only | This object will return TRUE if the currently defined boot configuration file exists, or FALSE otherwise. |
| SYS bootCnfgSetStatus | 1.3.6.1.4.1.207.8.4.4.4.500.3.2.3 | SystemFileOperationType | read-only | Returns the status of any current operation to set the next boot configuration file. The following values may be returned: 1 (idle) There is no boot configuration setting operation in progress. 2 (success) The last boot configuration setting operation completed successfully. 3 (failure) The last boot configuration setting operation failed. 5 (syncing) A boot configuration setting operation is currently in progress and the file is being syncronised across the stack or system. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading bootCnfgLastSetResult. |
| STR bootCnfgLastSetResult | 1.3.6.1.4.1.207.8.4.4.4.500.3.2.4 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to set the boot configuration filename. |
| defaultConfig | 1.3.6.1.4.1.207.8.4.4.4.500.3.3 | |||
| STR dfltCnfgPath | 1.3.6.1.4.1.207.8.4.4.4.500.3.3.1 | DisplayString | read-only | The full path of the configuration file to be used upon device restart, if no user-defined boot or backup configuration files can be found. There is no guarantee that the file referenced exists (i.e. it may have been deleted). This object is not settable - the default configuration file is always 'flash:/default.cfg' |
| T/F dfltCnfgExists | 1.3.6.1.4.1.207.8.4.4.4.500.3.3.2 | TruthValue | read-only | This object will return TRUE if the currently defined default configuration file exists, or FALSE otherwise. |
| backupConfig | 1.3.6.1.4.1.207.8.4.4.4.500.3.4 | |||
| STR backupCnfgPath | 1.3.6.1.4.1.207.8.4.4.4.500.3.4.1 | DisplayString | read-write | 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. |
| T/F backupCnfgExists | 1.3.6.1.4.1.207.8.4.4.4.500.3.4.2 | TruthValue | read-only | This object will return TRUE if the currently defined backup configuration file exists, or FALSE otherwise. |
| SYS backupCnfgSetStatus | 1.3.6.1.4.1.207.8.4.4.4.500.3.4.3 | SystemFileOperationType | read-only | Returns the status of any current operation to set the next backup boot configuration file. The following values may be returned: 1 (idle) There is no backup boot configuration setting operation in progress. 2 (success) The last backup boot configuration setting operation completed successfully. 3 (failure) The last backup boot configuration setting operation failed. 5 (syncing) A backup boot configuration setting operation is currently in progress and the file is being syncronised across the stack or system. When a read of this object returns a value of 'success' or 'failure', it will immediately be reset to 'idle' and a new operation may be initiated if desired. A detailed description of the last completed operation may be determined by reading backupCnfgLastSetResult. |
| STR backupCnfgLastSetResult | 1.3.6.1.4.1.207.8.4.4.4.500.3.4.4 | DisplayString | read-only | Gives an indication of the result of the last completed SNMP operation to set the backup boot configuration filename. |
| I32 restartStkMemberDevice | 1.3.6.1.4.1.207.8.4.4.4.500.4 | Integer32 | read-write | This object causes a specified device to restart immediately. The restart is initiated by setting its value to the device's stack member ID. For a chassis switch, this object causes the specified card to restart immediately. Setting its value to zero will cause all devices in the stack (or a standalone device) to restart. Reading the object will always return zero. |
| serviceConfig | 1.3.6.1.4.1.207.8.4.4.4.500.5 | |||
| T/F srvcTelnetEnable | 1.3.6.1.4.1.207.8.4.4.4.500.5.1 | TruthValue | read-write | This object represents the state of the telnet server of a device. A management application can find out the telnet server is either enabled or disabled by reading this object. To either enable or disable the telnet server, a management application can SET this object with value 'enable(1)' or 'disable(2)' respectively. |
| T/F srvcSshEnable | 1.3.6.1.4.1.207.8.4.4.4.500.5.2 | TruthValue | read-write | This object represents the state of the ssh server of a device. A management application can find out the ssh server is either enabled or disabled by reading this object. To either enable or disable the ssh server, a management application can SET this object with value 'enable(1)' or 'disable(2)' respectively. |
| guiConfig | 1.3.6.1.4.1.207.8.4.4.4.500.6 | |||
| guiAppletConfig | 1.3.6.1.4.1.207.8.4.4.4.500.6.1 | |||
| STR guiAppletSysSwVer | 1.3.6.1.4.1.207.8.4.4.4.500.6.1.1 | DisplayString | read-only | This object represents the system software release that the currently selected GUI applet was designed to run on. The system will automatically search for GUI applet files residing in the root directory of flash, and will select the latest available one that is applicable to the currently running system software. This will be the applet that is uploaded to a user's web browser when they initiate use of the GUI. |
| STR guiAppletSwVer | 1.3.6.1.4.1.207.8.4.4.4.500.6.1.2 | DisplayString | read-only | This object represents the software version of the currently selected GUI applet. The system will automatically search for GUI applet files residing in the root directory of flash, and will select the latest available one that is applicable to the currently running system software. This will be the applet that is uploaded to a user's web browser when they initiate use of the GUI. |
RFC description
Allied Telesis vendor-private MIB for system setup and configuration of AT network devices.
Start monitoring Allied Telesis managed switches and routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.