MIB Viewer

iOpsIADDownloadSoftware

OBJECT-TYPE
1.3.6.1.3.1.1.1.1.12
Access
read-write
Status
current
Source
OPS-MIB
Sub-identifiers
0
Is used to download the system image file to the IAD or to obtain status about the file download: 1) The SNMP SET PDU message is used to initiate a download of the system image file to the IAD. 2) The SNMP GET, GET-NEXT, OR GET-BULK PDU messages are used to obtain status of the previously initiated download. When initiating a download of the system image file, the attributes of this object and the attributes of the 'iOpsIADSaveSoftware' object-type must be included in the same SNMP SET PDU message. 'iOpsIADSaveSoftware' is used to specify either: 1) A save of the file on the IAD. 2) A save of the file on the IAD and then perform a reboot of the IAD. The IP address of the server used to transfer the file or the status information is specified in the 'iOpsIADServerIP' object-type. The server used to download the system image file defaults to the TFTP protocol. However, this default may be changed to 'FTP' or to 'other'. It is specified in the 'iOpsIADServerType' object-type. If an alternate transfer protocol is used, it must first be specified before attempting the file download. If the IAD is unable to complete the file transfer for any reason, the values of the 'iOpsIADAdminStatus' and 'iOpsIADOperStatus' object-types must remain in the 'up' status in order for the IAD to be available to accept subsequent system image file downloads. SET PDU message: 1: Download the system image file from the server to the IAD. The system image file name is specified in the 'iOpsIADSoftwareUpgradeFileName' object-type. GET, GET-NEXT, or GET-BULK PDU message: 2: The download of the system image file is complete. 3: The download of the system image file failed. 4: The download of the system image file is in progress. 5. No status can be returned because no prior SET operation was performed.
INTEGER { downloadSoftwareFromServer(1), downloadComplete(2), downloadFailed(3), downloadInProgress(4), none(5) Definitions of Managed Objects for OPS October 2000 }