Status in source: current.
Names: ostFwupdTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ostFwupdTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"OstFwupdEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This table enables the chassis master's management entity to update the firmware of a slave module via the backplane using the FTP protocol. The backplane must be enabled between the master and slave module to work correctly. The slave module will reboot itself upon completion of the update. Steps to use entries in this table: 1) Wait for ostFwupdgReady value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and ostFwupdgReady objects (in same SNMP PDU). b. Check if value for ostFwupdgReady is true. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change ostFwupdgReady value from true to false to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and ostFwupdgReady objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the slave slot if differ from slot 2. 4) Set ostFwupdAction to write(1) value to initiate command operation. 5) Check the value of ostFwupdLastStatus to find out if the operation was successfully completed. 6) Change the ostFwupdgReady value back to true to allow other management entities to use the table.\"",
"::=",
"{",
"ostFwupd",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"OstFwupdEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This table enables the chassis master's management entity to update the firmware of a slave module via the backplane using the FTP protocol. The backplane must be enabled between the master and slave module to work correctly. The slave module will reboot itself upon completion of the update. Steps to use entries in this table: 1) Wait for ostFwupdgReady value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and ostFwupdgReady objects (in same SNMP PDU). b. Check if value for ostFwupdgReady is true. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change ostFwupdgReady value from true to false to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and ostFwupdgReady objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the slave slot if differ from slot 2. 4) Set ostFwupdAction to write(1) value to initiate command operation. 5) Check the value of ostFwupdLastStatus to find out if the operation was successfully completed. 6) Change the ostFwupdgReady value back to true to allow other management entities to use the table."
],
null,
null,
null,
null
]
}