LOAD-MIB :: genOpIndex

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOAD-MIB › genOpIndex

genOpIndex

Module: LOAD-MIB

OID (symbolic): LOAD-MIB::genOpIndex

OID (numeric): 1.3.6.1.4.1.1751.2.53.1.2.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: 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.

What is genOpIndex?

Selects which type of file operation this row represents, such as uploadConfig(1), downloadSoftware(5), or eraseFile(9); walking this table shows every operation type the module supports, and setting the companion genOp* objects then triggers that specific operation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.53.1.2.1.2
snmpwalk -v2c -c public <target> LOAD-MIB::genOpIndex

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.53.1.2.1.2.1
snmpget -v2c -c public <target> LOAD-MIB::genOpIndex.1

Start monitoring Lucent Technologies telecommunications network element (firmware download/upload jobs) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LOAD-MIB::genOpIndex OID value, configure state conditions and alerts, and monitor any Lucent Technologies telecommunications network element (firmware download/upload jobs) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1751lucentACMIB
1.3.6.1.4.1.1751.2mibsACMIB
Numeric OIDNameModule
1.3.6.1.4.1.1751.2.53loadLOAD-MIB
1.3.6.1.4.1.1751.2.53.1genOperationsLOAD-MIB
1.3.6.1.4.1.1751.2.53.1.2genOpTableLOAD-MIB
1.3.6.1.4.1.1751.2.53.1.2.1genOpEntryLOAD-MIB
1.3.6.1.4.1.1751.2.53.1.2.1.2genOpIndexLOAD-MIB