Status in source: current.
Names: checkTcpIpStackForSuccessfulBoot
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"checkTcpIpStackForSuccessfulBoot",
"OBJECT-TYPE",
"SYNTAX",
"MxEnableState",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Enable the check of TCP/IP stack before declaring the boot successful. This variable affects the behavior of the unit when it reboots and a TCP/IP flood occurs. The flood prevents the TCP/IP stack from initializing properly, and the unit eventually reboots again. After three unsuccessful reboots, the unit falls into rescue mode. When checkTcpIpStackForSuccessfulBoot is enabled, the TCP/IP stack must initialize properly to consider the reboot a success. In a flood scenario, the unit may end up in the rescue mode. When checkTcpIpStackForSuccessfulBoot is disabled, during a TCP/IP flood, even if the TCP/IP stack fails to initialize, the reboot is considered successful, and thus, the unit never goes into rescue mode in this scenario.\"",
"DEFVAL",
"{",
"enable",
"}",
"::=",
"{",
"bootBehaviorMIBObjects",
"1",
"}"
],
"syntax_tree": [
[
"row",
"MxEnableState"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Enable the check of TCP/IP stack before declaring the boot successful. This variable affects the behavior of the unit when it reboots and a TCP/IP flood occurs. The flood prevents the TCP/IP stack from initializing properly, and the unit eventually reboots again. After three unsuccessful reboots, the unit falls into rescue mode. When checkTcpIpStackForSuccessfulBoot is enabled, the TCP/IP stack must initialize properly to consider the reboot a success. In a flood scenario, the unit may end up in the rescue mode. When checkTcpIpStackForSuccessfulBoot is disabled, during a TCP/IP flood, even if the TCP/IP stack fails to initialize, the reboot is considered successful, and thus, the unit never goes into rescue mode in this scenario."
],
null,
null,
null,
[
"DEFVAL",
"enable"
]
]
}