Status in source: mandatory.
Names: commonCheckCode
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"commonCheckCode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This object reports the Check Code for the transponder's configuration. The check code is generated from objects which are stored in non-volatile memory as well as those objects which reports the transponder's physical configuration, including monitored devices. The algorithm used to generate the Check Code is vendor specific. Upon a restart of the transponder, the current value of the check code is compared against the value previous to the restart to determine if a hmsColdStart or a hmsWarmStart trap is to be generated. This requires that the value of the object be maintained in non-volatile memory for the comparison operation after a restart. When a value is written to this object, the check code is recalculated, and the new value is returned in the GetResponse returned for the SetRequest. Since this optimization is NOT SNMP compliant, the transponder MAY respond in the SNMP compliant manner. Since this object description may impact an SNMP manager, it is recommended that the value be subsequently retrieved with a GetRequest, to guarantee that the desired value has been obtained. In this case (on-demand recalculation), the hmsColdStart or hmsWarmStart traps are NOT generated. The value for this object is maintained in non-volatile memory.\"",
"::=",
"{",
"commonAdminGroup",
"10",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This object reports the Check Code for the transponder's configuration. The check code is generated from objects which are stored in non-volatile memory as well as those objects which reports the transponder's physical configuration, including monitored devices. The algorithm used to generate the Check Code is vendor specific. Upon a restart of the transponder, the current value of the check code is compared against the value previous to the restart to determine if a hmsColdStart or a hmsWarmStart trap is to be generated. This requires that the value of the object be maintained in non-volatile memory for the comparison operation after a restart. When a value is written to this object, the check code is recalculated, and the new value is returned in the GetResponse returned for the SetRequest. Since this optimization is NOT SNMP compliant, the transponder MAY respond in the SNMP compliant manner. Since this object description may impact an SNMP manager, it is recommended that the value be subsequently retrieved with a GetRequest, to guarantee that the desired value has been obtained. In this case (on-demand recalculation), the hmsColdStart or hmsWarmStart traps are NOT generated. The value for this object is maintained in non-volatile memory."
],
null,
null,
null,
null
]
}