LOAD-MIB

All MIBs › LOAD-MIB

Organization: Lucent Technologies Inc.

Last Updated: 2000-09-13

Category: Vendor: Lucent/Ascend

Description: MIB from Lucent Technologies exposing system load metrics and resource utilization objects for its telecommunications 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 LOAD-MIB?

LOAD-MIB is a Lucent Technologies private enterprise MIB governing common file download/upload operations used to transfer firmware, configuration, or software images to and from Lucent network elements. It exposes a generic operation table (genOpTable) recording the state, direction (source/destination), and network parameters of transfer jobs, including the target server's IP address, login credentials, and transfer protocol. Although framed as a "load" MIB, its core purpose is operational: monitoring the running state of file-transfer jobs (genOpRunningState) and the number of concurrent sessions (genLoadNumberOfSession), useful for detecting stalled or failed firmware/config upgrades - effectively a software job-status monitor rather than a CPU/memory load gauge. It does not show explicit imports from standard MIB-II or Entity MIB conventions, functioning largely as a self-contained enterprise-specific control/status MIB under the Lucent enterprise OID branch. It is typically deployed by Lucent equipment provisioning/management systems that push firmware or configuration files to network elements and need to confirm each transfer job completed successfully. Engineers can download the LOAD-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in LOAD-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

Lucent Technologies telecommunications network element

Monitoring Examples

An operator kicking off a firmware upgrade would poll genOpTable/genOpEntry rows keyed by genOpIndex to watch genOpRunningState transition from in-progress to complete or failed, while genOpServerIP and genOpProtocolType confirm which server and protocol the job used. genOpSourceIndex and genOpDestIndex identify which module and file are being transferred, and genLoadNumberOfSession shows how many such jobs are concurrently active, revealing whether a batch upgrade has stalled if the session count doesn't decrease as expected.

What Can Be Monitored

download/upload job running state
active transfer session count
source and destination module indices
target server IP address
transfer protocol type
job/operation status

Imported Objects

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString
RowStatus

How to Use in IPNetwork Monitor

Example using genLoadNumberOfSession OID:

Select a Lucent Technologies telecommunications network element (firmware download/upload jobs) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type genLoadNumberOfSession into the Find box to locate it in the OID tree, then select it and click OK. The number of operational sessions in progress in this system. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
lucent	1.3.6.1.4.1.1751
products	1.3.6.1.4.1.1751.1
mibs	1.3.6.1.4.1.1751.2
load	1.3.6.1.4.1.1751.2.53			Lucent Common Download / Upload Private MIB
genOperations	1.3.6.1.4.1.1751.2.53.1
I32 genLoadNumberOfSessionEx	1.3.6.1.4.1.1751.2.53.1.1	Integer32	read-only	The number of operational sessions in progress in this system
genOpTable	1.3.6.1.4.1.1751.2.53.1.2		not-accessible	Table of configuration attributes which define the operational functions and the results on a per module basis. This group provides the mechanism by which available operations are initiated, monitored and reported.
genOpEntry	1.3.6.1.4.1.1751.2.53.1.2.1		not-accessible	An entry in the table, containing data about a single modules operations.
INT genOpModuleId	1.3.6.1.4.1.1751.2.53.1.2.1.1	INTEGER	read-only	Index which identifies the module inside the chassis for which this entry contains information. Equals the number of the slot by which the group is accessed or the stackable index.
INT genOpIndex	1.3.6.1.4.1.1751.2.53.1.2.1.2	INTEGER	read-only	Index to identify the operation supported by this row entry. Each operation type that is supported by this module should be represented by a unique row in this MIB Table. A walk of this MIB table should reveal all the operations that are supported by the device. The operations supported are: uploadConfig -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpServerIP' should be set to the server to which the config will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are uploading. The 'genOpFileName' should be set to the name and path of the config file on the TFTP server. downloadConfig -- The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpServerIP' should be set to the server from which the config will be copied. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to 0 (to indicate source of server). The 'genOpFileName' should be set to the name and path of the config file on the TFTP server. report -- uploadSoftware -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpServerIP' should be set to the server to which the config file will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are uploading. The 'genOpFileName' should be set to the name and path of the image file on the TFTP server. downloadSoftware -- The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are downloading to (if one does not exist, you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpServerIP' should be set to the server from which the config file will be copied. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpSourceIndex' should be set to 0 (to indicate source of server). The 'genOpFileName' should be set to the name and path of the image file on the TFTP server. localConfigFileCopy -- (using a 'genOpType' of 'localPeerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are copying from. The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL. localSWFileCopy -- (using a 'genOpType' of 'localPeerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are copying from. The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL. localConfigFileCopy -- (using a 'genOpType' of 'localServerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the config file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable') or ZERO (0) if copying to a localServer. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the config file you are copying from or ZERO (0) if copying from a localServer. The 'genOpServerIP' should be set to the address of the local server. The 'genOpProtocolType' should be set to 'localServerTransport'. localSWFileCopy -- (using a 'genOpType' of 'localServerTransport') The 'genOpDestIndex' should be set to the 'genAppFileId' of the software file you are copying to (if one does not exist you'll need to RowCreate it in the 'genAppFileTable'). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the software file you are copying from. The 'genOpServerIP' should be set to the address of the local server. The 'genOpProtocolType' should be set to 'localServerTransport'. uploadLogfile -- The 'genOpDestIndex' should be set to 0 (to indicate destination of server). The 'genOpSourceIndex' should be set to the 'genAppFileId' of the log file you are copying from. The 'genOpServerIP' should be set to the server to which the config will be saved. The 'genOpProtocolType' should be set to the IP protocol used to transport the file. The 'genOpFileName' should be set to the name and path of the log file on the TFTP server. eraseFile -- The 'genOpDestIndex' Is not applicable for this command. The 'genOpSourceIndex' should be set to the 'genAppFileId' of the file you wish to erase. The 'genOpServerIP' should be set to 0. The 'genOpProtocolType' should be set to 0. The 'genOpFileName' should be set to NULL. show -- Reporting information to the CLI. syncStandbyAgent(11) -- copy configuration AND software image files to the (non-active) standby agent in a P550/P880. The 'genOpDestIndex' should be set to 1 The 'genOpSourceIndex' should be set to 1 The 'genOpServerIP' should be set to NULL. The 'genOpProtocolType' should be set to 'localPeerTransport'. The 'genOpFileName' should be set to NULL.
INT genOpRunningState	1.3.6.1.4.1.1751.2.53.1.2.1.3	INTEGER	read-write	Identifies the operation to perform and the state of that operation. This field acts as both the trigger to initiate the operation (via the beginOperation) and the status field of the operation itself (i.e. waiting-ip, running-ip, etc.). It is expected that all dependent MIB objects will be set before the trigger is set to beginOperation. The operations completion is triggered by the return to the idle state. idle(1), - Operation not in progress beginOperation(2), - Trigger by NMS to start the operation waitingIp(3), - Communication phase; waiting for response runningIp(4), - Communication phase; transferring data copyingLocal(5), - Local operation readingConfiguration(6), - Parsing / Executing configuration file executing(7) - Executing Command (such as erasing a file or reporting)
I32 genOpSourceIndex	1.3.6.1.4.1.1751.2.53.1.2.1.4	Integer32	read-write	The index value (taken from the genAppFileTable) of the source of the operation. NOTE: A value of zero (0) here indicates that the Server (specified below) is the source.
I32 genOpDestIndex	1.3.6.1.4.1.1751.2.53.1.2.1.5	Integer32	read-write	The index value (taken from the genAppFileTable) of the destination of the operation. NOTE: A value of zero (0) here indicates that the Server (specified below) is the Destination.
IP genOpServerIP	1.3.6.1.4.1.1751.2.53.1.2.1.6	IpAddress	read-write	The IP Address of the server from/to which the file has to be Download/Upload. NOTE: In the case of localPeerTransport this value should be NULL.
STR genOpUserName	1.3.6.1.4.1.1751.2.53.1.2.1.7	DisplayString	read-write	Contains the username to be used if the protocol specified in genOpProtocolType requires one. The default value will be the empty string
OCT genOpPassword	1.3.6.1.4.1.1751.2.53.1.2.1.8	OCTET STRING	read-write	Contains the password to be used if the protocol specified in genOpProtocolType requires one. The default value will be the empty string
INT genOpProtocolType	1.3.6.1.4.1.1751.2.53.1.2.1.9	INTEGER	read-write	Identifies the protocol between the management station and the device for Download/Upload of the file.
STR genOpFileName	1.3.6.1.4.1.1751.2.53.1.2.1.10	DisplayString	read-write	The location (including the FULL path) of the file in the server. NOTE: In the case of localPeerTransport this value should be NULL.
STR genOpRunningStateDisplay	1.3.6.1.4.1.1751.2.53.1.2.1.11	DisplayString	read-only	The state of the operation for Display on the terminal during operation process.
INT genOpLastFailureIndex	1.3.6.1.4.1.1751.2.53.1.2.1.12	INTEGER	read-only	While a download is in progress this will always be 'no-error'. After a download is complete this indicates the success or failure of the download. If it is anything other than 'no-error' then 'genOpLastFailureDisplay' will contain a textual description of the error. Error codes from 100 upwards are errors returned from a TFTP server. errors below this are locally generated. Configuration files may return errors after download as a result of reading a config file into the system. confFileGenErr - General (unknown error) confFileParseError - Reading of config file resulted in parsing errors. confFileExecError - Reading of config file resulted in execution errors.
STR genOpLastFailureDisplay	1.3.6.1.4.1.1751.2.53.1.2.1.13	DisplayString	read-only	Contains the last error, Null if there is no error.
STR genOpLastWarningDisplay	1.3.6.1.4.1.1751.2.53.1.2.1.14	DisplayString	read-only	Last warning which didn't stop the operation (not fatal error).
I32 genOpErrorLogIndex	1.3.6.1.4.1.1751.2.53.1.2.1.15	Integer32	read-write	The Index in the 'genAppFileTable' under which an error log has been created. In the case of file that produce errors this file should contain a log of errors that occurred. (This item should be zero if it does not exist)
INT genOpResetSupported	1.3.6.1.4.1.1751.2.53.1.2.1.16	INTEGER	read-only	Indicates if a reset (after operation completion) is supported by this Module.
INT genOpEnableReset	1.3.6.1.4.1.1751.2.53.1.2.1.17	INTEGER	read-write	Whether to do a reset after the operation completed successfully.
I32 genOpNextBootImageIndex	1.3.6.1.4.1.1751.2.53.1.2.1.18	Integer32	read-write	The row in the 'genAppFileTable' of the default Application that the device will boot from when a standard reboot is performed.
I32 genOpLastBootImageIndex	1.3.6.1.4.1.1751.2.53.1.2.1.19	Integer32	read-only	The Index in the 'genAppFileTable' of the default Application that the device was last booted from.
INT genOpFileSystemType	1.3.6.1.4.1.1751.2.53.1.2.1.20	INTEGER	read-only	Indicates what type of file system is supported by this module. A value of 'static' indicates that rows in the 'genAppFileTable' are not removable nor can new entries be created. A value of 'dynamic' indicates that entries in the 'genAppFileTable' are both removable and can be created.
INT genOpReportSpecificFlags	1.3.6.1.4.1.1751.2.53.1.2.1.21	INTEGER	read-write	Contain modifiers to the Report operation. fullReport - Full configuration report partialReport - A report without the information stored in the OSPF database notSupported - For operations other than report, this MIB has no meaning and can return not Supported or not be supported.
I32 genOpOctetsReceived	1.3.6.1.4.1.1751.2.53.1.2.1.22	Integer32	read-only	While a download is in progress this indicates the number of bytes transferred so far.
genApplications	1.3.6.1.4.1.1751.2.53.2
genAppFileTable	1.3.6.1.4.1.1751.2.53.2.1		not-accessible	Table of Application (FILE) entries. Each row uniquely defines an application in the system. Applications can be defined as any entity that can be read or written from or to the system. This includes software images, boot code, configuration files, prom code, etc.
genAppFileEntry	1.3.6.1.4.1.1751.2.53.2.1.1		not-accessible	An entry in the table, containing data about a single application / config file.
INT genAppFileId	1.3.6.1.4.1.1751.2.53.2.1.1.1	INTEGER	read-only	Index which uniquely identifies the application. NOTE: This index CANNOT BE ZERO (0) since the index of zero is reserved as an indication of network server location in the genOpSourceIndex and genOpDestIndex above.
STR genAppFileName	1.3.6.1.4.1.1751.2.53.2.1.1.2	DisplayString	read-create	The name of the application.
INT genAppFileType	1.3.6.1.4.1.1751.2.53.2.1.1.3	INTEGER	read-create	The type (class) of the application. This class serves to catagorize the many application files in the system into some fixed types: runningConfiguration -- This entry represents a virtual file in the system. Use of this entry in the genOpTable should serve to cause the system to generate it's configuration or to force the system to read a new config into it's configuration. startupConfiguration -- This entry represents a real file that is used at start-up to configure the device. defaultConfiguration -- This entry represents a file which contains the default configuration of the device. report -- ?? genConfigFile -- This entry represents a file which contains configuration information (similar to the 'startupConfiguration' above but is not automatically read by the device. This entry is used to represent 'alternate', 'backup' or 'experimental' configurations that the user may which to store on the device. nvramFile -- This entry represents a file that is contain in the nvram files system that does not fit any of the other pre-defined types. swRuntimeImage -- This entry represents a software images that contains operational code that is currently being used to run the device. swBootImage -- This entry represents a software image that contain operational code that is used to initally boot the device. swComponent -- This entry represents a file that is stored as an 'alternate', 'backup' or 'experimental' version of operational code. other -- other swWebImage -- The Image file of the embedded Web application (java application, etc).
STR genAppFileDescription	1.3.6.1.4.1.1751.2.53.2.1.1.4	DisplayString	read-create	A description of the application.
I32 genAppFileSize	1.3.6.1.4.1.1751.2.53.2.1.1.5	Integer32	read-create	The size (expressed as the number of bytes) of the application.
OCT genAppFileVersionNumber	1.3.6.1.4.1.1751.2.53.2.1.1.6	OCTET STRING	read-only	The current version of the application. If this files does not carry a version this field should be NULL.
INT genAppFileLocation	1.3.6.1.4.1.1751.2.53.2.1.1.7	INTEGER	read-create	The physical location of the application.
STR genAppFileDateStamp	1.3.6.1.4.1.1751.2.53.2.1.1.8	DisplayString	read-only	The time stamp is the Real Time if supported otherwise sysUpTime. The convention for this field is as follows: Real Time: Entry is prefixed with an 'R' character and time is formatted using the convention for date-and-time (rfc1903) DISPLAY-HINT 'R-2d-1d-1d,1d:1d:1d.1d,1a1d:1d' field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: R-1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SysUpTime: Entry is prefixed with an 'S' character and time is formatted using a portion of that date-and-time convention DISPLAY-HINT 'S-1d-1d,1d:1d:1d.1d' field octets contents range ----- ------ -------- ----- 1 3 month 1..12 2 4 day 1..31 3 5 hour 0..23 4 6 minutes 0..59 5 7 seconds 0..60 6 8 deci-seconds 0..9 For example, S-5-26,13:30:15.0 Represents a file that has existed in the system for 5 months, 26 days, 13 hours, 30 minutes, 15 seconds exactly. This value will be reset after a reboot of the system.
ROW genAppFileRowStatus	1.3.6.1.4.1.1751.2.53.2.1.1.9	RowStatus	read-create	The status of this entry in the table. Note the available states: active(1), -- Fully configured and active. notInService(2) -- NOT SUPPORTED. notReady(3), -- Entry NOT FULLY configured. createAndGo(4), -- Used to add new Applications in the system. createAndWait(5) -- Used to add new Applications in the system. destroy(6) -- Used to delete Applications in the system.

RFC description

Lucent Technologies MIB providing system load metrics and resource utilization objects for Lucent telecommunications equipment.

Start monitoring Lucent Technologies telecommunications network element (firmware download/upload jobs) 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.

Download LOAD-MIB