Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"osFailureCaptureSaveStart",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"execute",
"(",
"1",
")",
",",
"execute-nowait",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Start saving the configuration file to the specified target file and system. The file will exist if the OS Hang or OS Loader watchdog is enabled and been tripped. Using execute will cause the SNMP client to wait for the save operation to complete. Using execute-nowait will not cause the SNMP client to wait for the save to complete. Instead it will save the configuration in the background. Note 1: Both osFailureCaptureTftpServer and osFailureCaptureFileName must be set. Note 2: Depending on the target, it might take up to several seconds for the save operation to complete. Note 3: Use osFailureCaptureStatus to confirm the status of the last operation. NOTE: Value returned for the GET command is meaningless for this MIB object.\"",
"::=",
"{",
"osFailureCapture",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"execute",
1
],
[
"execute-nowait",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Start saving the configuration file to the specified target file and system. The file will exist if the OS Hang or OS Loader watchdog is enabled and been tripped. Using execute will cause the SNMP client to wait for the save operation to complete. Using execute-nowait will not cause the SNMP client to wait for the save to complete. Instead it will save the configuration in the background. Note 1: Both osFailureCaptureTftpServer and osFailureCaptureFileName must be set. Note 2: Depending on the target, it might take up to several seconds for the save operation to complete. Note 3: Use osFailureCaptureStatus to confirm the status of the last operation. NOTE: Value returned for the GET command is meaningless for this MIB object."
],
null,
null,
null,
null
]
}