AT-INSTALL-MIB: View SNMP OID List / Download MIB

VENDOR: ALLIED TELESIS


 Home MIB: AT-INSTALL-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, AT-SMI-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 install 1.3.6.1.4.1.207.8.4.4.4.49
This MIB file contains definitions of managed objects for the INSTALL module.
       installTrap 1.3.6.1.4.1.207.8.4.4.4.49.0
           configFileExistTrap 1.3.6.1.4.1.207.8.4.4.4.49.0.1
This trap is generated when the boot file is detected as missing
       installTable 1.3.6.1.4.1.207.8.4.4.4.49.1 no-access
The list of install configurations for the router.
           installEntry 1.3.6.1.4.1.207.8.4.4.4.49.1.1 no-access
An entry in the list of install configurations.
               instIndex 1.3.6.1.4.1.207.8.4.4.4.49.1.1.1 integer read-only
The index for the install table. There are four install configurations defined in the router, default, preferred, temporary and current. The router will attempt to use these in the order temporary, preferred, default when it boots. An install that is undefined will be skipped, an install which points to a file which is not present will be skipped. When the temporary install is used, the information is deleted. The current configuration shows what the router currently has installed. Enumeration: 'default': 3, 'current': 4, 'temporary': 1, 'preferred': 2.
               instRelDevice 1.3.6.1.4.1.207.8.4.4.4.49.1.1.2 integer read-only
The device for the release in the install. If the device is flash the file for the release is given in instRelName. Devices none(1) or flash(3) are invalid for the default(3) release. Enumeration: 'none': 1, 'flash': 3, 'eprom': 2.
               instRelName 1.3.6.1.4.1.207.8.4.4.4.49.1.1.3 displaystring read-only
The file name for the release in the install, if the instRelDevice is flash(3). If the instRelDevice is none(1) or eprom(2), this object should be a null string.
               instRelMajor 1.3.6.1.4.1.207.8.4.4.4.49.1.1.4 integer read-only
The major release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is a.
               instRelMinor 1.3.6.1.4.1.207.8.4.4.4.49.1.1.5 integer read-only
The minor release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is b.
               instPatDevice 1.3.6.1.4.1.207.8.4.4.4.49.1.1.6 integer read-only
The device for the patch in the install. The file for the patch is given in instPatName unless the device is none(1). Enumeration: 'none': 1, 'flash': 3, 'nvs': 4.
               instPatName 1.3.6.1.4.1.207.8.4.4.4.49.1.1.7 displaystring read-only
The file name for the patch in the install.
               instRelInterim 1.3.6.1.4.1.207.8.4.4.4.49.1.1.8 integer read-only
The interim release number for this install. This information is obtained by the router when the other elements in the row are set and is thus not directly set by management. If the release number is a.b.c, the major release number is c. If the release number is a.b, the interim release number is 0.
               instRelExists 1.3.6.1.4.1.207.8.4.4.4.49.1.1.9 integer read-only
Indicates if the release file exists or not. true(1) means it exists, false(2) means it doesn't. Enumeration: 'false': 2, 'true': 1.
               instPatExists 1.3.6.1.4.1.207.8.4.4.4.49.1.1.10 integer read-only
Indicates if the patch file exists or not. true(1) means it exists, false(2) means it doesn't Enumeration: 'false': 2, 'true': 1.
       installHistoryTable 1.3.6.1.4.1.207.8.4.4.4.49.2 no-access
The table of descriptions of events in the install history of the router.
           installHistoryEntry 1.3.6.1.4.1.207.8.4.4.4.49.2.1 no-access
A single line describing part of the install history of the router.
               instHistIndex 1.3.6.1.4.1.207.8.4.4.4.49.2.1.1 integer read-only
The index of this event in the install history. Indices run from 1 to the maximum number. The maximum number is not available as a managed object so this table will have to be traversed in order to find out how large it is.
               instHistLine 1.3.6.1.4.1.207.8.4.4.4.49.2.1.2 displaystring read-only
A line of text describing a single event in the install history of the router.
       configFile 1.3.6.1.4.1.207.8.4.4.4.49.3 displaystring read-write
The name of the file that the router will configure from at boot. The format of the name is the same as that for fileName described above. If the configuration file name is a zero length string, then there is no configuration file defined in the router.
       licenceTable 1.3.6.1.4.1.207.8.4.4.4.49.4 no-access
The list of release licences in the router.
           licenceEntry 1.3.6.1.4.1.207.8.4.4.4.49.4.1 no-access
An entry in the list of release licences.
               licenceIndex 1.3.6.1.4.1.207.8.4.4.4.49.4.1.1 integer read-only
A unique licence index. Licence indices are recalculated every time the router reboots to reflect the current licences on the router. As licences are added, new indices are allocated to the new licences.
               licenceStatus 1.3.6.1.4.1.207.8.4.4.4.49.4.1.2 integer read-write
The status of the file. When read, this object will always return a value of ok(1), since the object will not exist if the value is deleting(2). Write the value deleting(2) to this object to delete the file. Enumeration: 'deleting': 2, 'ok': 1.
               licenceRelease 1.3.6.1.4.1.207.8.4.4.4.49.4.1.3 displaystring read-write
The file name for the release whose licence this is.
               licenceMajor 1.3.6.1.4.1.207.8.4.4.4.49.4.1.4 integer read-write
The major release number for the release whose licence this is.
               licenceMinor 1.3.6.1.4.1.207.8.4.4.4.49.4.1.5 integer read-write
The minor release number for the release whose licence this is.
               licencePassword 1.3.6.1.4.1.207.8.4.4.4.49.4.1.6 displaystringunsized read-write
The password for this release. The password is a string of hex digits.
               licenceExpiry 1.3.6.1.4.1.207.8.4.4.4.49.4.1.7 displaystring read-only
A human-readable string that gives the expiry date of this licence.
               licenceInterim 1.3.6.1.4.1.207.8.4.4.4.49.4.1.8 integer read-write
The interim release number for the release whose licence this is.
       createConfigFile 1.3.6.1.4.1.207.8.4.4.4.49.5 displaystring read-write
The name of a file to create containing the current router configuration. A read from this variable will return the same as the variable configFile. Thus to save the current configuration in the current configuration file, read createConfigFile first, then write the result back to createConfigFile. If this variable is written with the name of an existing file, the file will be replaced with the current configuration.
       configFileExist 1.3.6.1.4.1.207.8.4.4.4.49.6 integer read-only
Indicates if the boot configuration file exists or not. true(1) means it exists, false(2) means it doesn't Enumeration: 'false': 2, 'true': 1.
       currentConfigFile 1.3.6.1.4.1.207.8.4.4.4.49.7 displaystring read-only
The name of the file that the router is currently configured with. The format of the name is the same as that for fileName described above. If the current configuration file name is a zero length string, then there is no current configuration file defined in the router.