Chapter 3 | Topology |
Status of the SCE 1000AfterAbnormal Boot
This parameter determines whether the SCE 1000 returns to normal operational state after a reboot caused by fatal error or abnormal shutdown. In general, it is desirable that the SCE 1000 resume operation, and as promptly as possible. However, in a redundant topology, a recovered SCE 1000 may remain
The two options for this parameter are:
•Operational — The status of the SCE 1000 after abnormal boot is operational. The platform automatically resumes functioning in the defined operational link bypass mode.
•Not Operational — The status of the SCE 1000 after abnormal boot is not operational. The platform remains in the defined failure link bypass mode.
This option is to be used only in a redundant topology where a second, operational platform exists.
Note Default value = Operational for all
Must be explicitly configured for redundant topologies.
Table | Topology Configuration Summary Table |
| ||
|
|
|
|
|
Description |
| Connection | Admin status after | |
|
| mode | bypass mode | abnormal boot |
Link connection via external | Bypass | Operational | ||
switch with |
|
|
| |
|
|
|
| |
|
|
| ||
Inline | Bypass | Operational | ||
and control, not redundant |
|
|
| |
Inline | Bypass | Operational | ||
only, not redundant |
|
|
| |
|
|
|
| |
Inline | Cutoff | Operational[1] | ||
and control, redundant |
|
|
| |
|
|
|
| |
Inline | Cutoff | Operational[1] | ||
only, redundant |
|
|
|
|
|
|
|
|
|
*Italicized values represent automatically applied defaults that are applied based on previously defined parameters. These values can be changed only via specific CLI commands.
[1]: In a redundant topology, it is also possible to configure admin status after abnormal boot to be Not operational. In this case, though, the SCE 1000 would have to be manually reloaded in order to resume full functionality.
Cisco SCE 1000 2xGBE Installation and Configuration Guide
| ||
|
|
|