genOpIndex - gen Operation Index - LOAD-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Avaya device in your network.

genOpIndex

gen Operation Index
1.3.6.1.4.1.52.4.53.1.2.1.2

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. ::= { genOpEntry 2 } SYNTAX INTEGER { idle(1), beginOperation(2), waitingIp(3), runningIp(4), copyingLocal(5), readingConfiguration(6), executing(7) } MAX-ACCESS read-write STATUS current DESCRIPTION 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) DEFVAL {idle} ::= { genOpEntry 3 } SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION 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.

Back to LOAD-MIB MIB page.

IPHost Network monitor allows you to monitor genOpIndex on Avaya device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Avaya IP phones right now.

Easy monitoring of genOpIndex with IPHost tools

MIBs list