All MIBs › LBMSH-MIB › slLoadStatus
slLoadStatus
Module: LBMSH-MIB
OID (symbolic): LBMSH-MIB::slLoadStatus
OID (numeric): 1.3.6.1.4.1.43.10.3.1.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The status of the last system load operation requested for this device. If the value of this object is in the range 1 to 18 inclusive, the download failed, and the value is an error code indicating the reason why. Codes 1 to 7 are a direct mapping from the TFTP error codes defined in RFC-783. The other error codes have the following meanings:- noResponse(8) load server failed to respond; noResource(9) the download could not be started because of a lack of resources; recLenMismatch(10) the record length differs from that implied by the value of the record length field; invalidRecType(11) the record type is not recognised; checksumError(12) record checksum error; wrongDevice(13) the device type in the file is incorrect; wrongHardwareVersion(14) the software image is not suitable for this version of the hardware; noFileHeader(15) the first record in the file was not a file header; byteCountError(16) the byte count reported in the file trailer record differed from the number of bytes actually received; invalidProgAddress(17) the load file contained a load address which was outside the valid range of memory; eraseFailed(18) unable to erase the program memory; progFailed(19) hardware error programming the memory. The meanings of the remaining values are as follows:- loadPending(20) a load has been requested but has not yet begun; loadActive(21) the device is currently being downloaded; success(22) the device has been downloaded successfully.
What is slLoadStatus?
Result of the last software load for this device: errors 1 to 18 mean the download failed (1 to 7 are TFTP errors such as fileNotFound or accessViolation, others include noResponse, checksumError, wrongHardwareVersion, eraseFailed and progFailed), while loadPending(20), loadActive(21) and success(22) report progress. Poll it after an upgrade to confirm success(22).
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.10.3.1.1.3 snmpwalk -v2c -c public <target> LBMSH-MIB::slLoadStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.43.10.3.1.1.3.1 snmpget -v2c -c public <target> LBMSH-MIB::slLoadStatus.1
Start monitoring 3Com LANBuilder MSH modular stackable hub with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LBMSH-MIB::slLoadStatus OID value, configure state conditions and alerts, and monitor any 3Com LANBuilder MSH modular stackable hub from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.43 | a3Com | A3COM-AUDL-R1-MIB |
| 1.3.6.1.4.1.43.10 | generic | A3Com-products-MIB |
| 1.3.6.1.4.1.43.10.3 | sysLoader | A3COM0004-GENERIC |
| 1.3.6.1.4.1.43.10.3.1 | loadableDeviceTable | LBHUB-BOOM-MIB |
| 1.3.6.1.4.1.43.10.3.1.1 | loadableDeviceEntry | LBHUB-BOOM-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.43.10.3.1.1.3 | slLoadStatus | LBMSH-MIB |