Whether the image file should be loaded in image1 or image2 in flash.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.1411.102.102.18.3.2
Whether the image file should be loaded in image1 or image2 in flash.
Identification
{1 3 6 1 4 1 1411 102 102 18 3 2}
| Value | Name |
|---|---|
| 2 | image1 |
| 3 | image2 |
| 4 | boot |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.1411.102.102.18.3.2.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
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.
agTftpImage OBJECT-TYPE
SYNTAX INTEGER {
image1(2),
image2(3),
boot(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Whether the image file should be loaded in image1 or image2 in flash."
::= { imageConfigTransfer 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Whether the image file should be loaded in image1 or image2 in flash.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: agTftpImage
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"agTftpImage",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"image1",
"(",
"2",
")",
",",
"image2",
"(",
"3",
")",
",",
"boot",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Whether the image file should be loaded in image1 or image2 in flash.\"",
"::=",
"{",
"imageConfigTransfer",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"image1",
2
],
[
"image2",
3
],
[
"boot",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Whether the image file should be loaded in image1 or image2 in flash."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: EX2500-BASE-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'DisplayString', 'PhysAddress', 'MacAddress', 'RowStatus', 'TimeInterval', 'TimeStamp'], 'BRIDGE-MIB': ['BridgeId', 'dot1dTp', 'dot1dTpPort', 'dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'TimeTicks', 'IpAddress', 'mib-2'], 'RFC1213-MIB': ['sysName', 'sysLocation', 'sysContact', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpMessageProcessingModel', 'SnmpSecurityModel', 'SnmpSecurityLevel'], 'SNMP-USER-BASED-SM-MIB': ['usmNoAuthProtocol', 'usmNoPrivProtocol']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1411.102.102.18.3.1 | agTftpServer | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.18.3.3 | agTftpImageFileName | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.18.3.4 | agTftpCfgFileName | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.18.3.5 | agTftpAction | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.18.3.6 | agTftpLastActionStatus | 0 | 0 |