Status in source: current.
Names: ostModcfgTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ostModcfgTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"OstModcfgEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This table enables the chassis master's management entity to read and save the slave's configuration file or to write the saved slave's configuration file to the slave. The write operation does not activate the configuration at the slave, only updates the slave's ini file. Steps to use entries in this table: 1) Wait for ostModcfgReady value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and ostModcfgReady objects (in same SNMP PDU). b. Check if value for ostModcfgReady 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 ostModcfgReady 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 ostModcfgReady 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 ostModcfgOpAction to get(1) or put (2) value to initiate command operation. 5) Check the value of ostModcfgLastStatus to find out if the operation was successfully completed. 6) Change the ostModcfgReady value back to true to allow other management entities to use the table.\"",
"::=",
"{",
"ostModcfg",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"OstModcfgEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This table enables the chassis master's management entity to read and save the slave's configuration file or to write the saved slave's configuration file to the slave. The write operation does not activate the configuration at the slave, only updates the slave's ini file. Steps to use entries in this table: 1) Wait for ostModcfgReady value to be true. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and ostModcfgReady objects (in same SNMP PDU). b. Check if value for ostModcfgReady 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 ostModcfgReady 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 ostModcfgReady 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 ostModcfgOpAction to get(1) or put (2) value to initiate command operation. 5) Check the value of ostModcfgLastStatus to find out if the operation was successfully completed. 6) Change the ostModcfgReady value back to true to allow other management entities to use the table."
],
null,
null,
null,
null
]
}