Process Restartability - Dell Force10 S4810P Configuration Manual

High-density, 1ru 48-port 10gbe switch
Hide thumbs Also See for Force10 S4810P:
Table of Contents

Advertisement

SECONDARY IMAGE FILE =
DEFAULT IMAGE FILE =
LOCAL CONFIG FILE =
PRIMARY HOST CONFIG FILE =
SECONDARY HOST CONFIG FILE =
PRIMARY NETWORK CONFIG FILE =
SECONDARY NETWORK CONFIG FILE =
CURRENT IMAGE FILE =
CURRENT CONFIG FILE 1 =
CURRENT CONFIG FILE 2 =
CONFIG LOAD PREFERENCE =
BOOT INTERFACE GATEWAY IP ADDRESS =
FTOS#

Process Restartability

Process Restartability is an extension to the FTOS high availability system component that enables
application processes and system protocol tasks to be restarted. This extension increases system reliability
and uptime by attempting to restart the crashed process on primary RPM before executing the failover
procedure as a last resort.
Currently, if a software exception occurs, FTOS executes a failover procedure. In a single-RPM system,
the system generates a coredump and reboots; in a dual-RPM system, the system generates a coredump and
fails over to the standby RPM.
With a system reload, the system must read and apply the entire startup-config file, which might take some
time if the startup-config is large. Restarting a process saves time because only a portion of the
configuration related to the crashed process is read and re-applied.
For a dual-RPMs system, restarting a process also precludes launching the failover process on the primary
and standby RPMs. Recovery is attempted first locally on the primary RPM, which involves less CPU
overhead, increasing the systems availability for other activities.
However, in both single and dual-RPM systems, even when Process Restart is configured, the coredump
portion of failover is still executed.
The processes that can be restarted fall under three categories:
Interface-related processes—TACACS+, RADIUS, CLI, and SSH, etc.
Protocol tasks—OSPF, RIP, and ACL, etc. Process Restart is not currently available for protocol
tasks; the failover procedure is executed immediately upon software exception.
Line card processes—IPC, Event Log Agent, Line Card Manager, etc. Process Restart is not currently
available for line card processes; the failover procedure is executed immediately upon software
exception.
flash://FTOS-EF-7.7.1.0.bin
flash://FTOS-EF-7.6.1.0.bin
variable does not exist
variable does not exist
variable does not exist
variable does not exist
variable does not exist
flash://FTOS-EF-7.7.1.0.bin
flash://startup-config
variable does not exist
local first
variable does not exist
High Availability | 457

Advertisement

Table of Contents
loading

Table of Contents