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 you configure process restart, the coredump
portion of failover is still executed.
The processes that you can restart fall under three categories:
•
Interface-related processes
— , RADIUS, CLI, and SSH, and so on.
•
Protocol tasks
— OSPF, RIP, and ACL, and so on. Process restart is not currently available for protocol
tasks; the failover procedure is executed immediately after software exception.
•
Line card processes
— IPC, Event Log Agent, Line Card Manager, and so on. Process restart is not
currently available for line card processes; the failover procedure is executed immediately after
software exception.
Enabling Process Restartability
The restart time varies by process.
In general, interface-related processes are hitless and can be restarted in seconds; if a restart is
successful, traffic is not interrupted. Protocol tasks and line card processes are not hitless and take longer
to restart. You can select which process may attempt to restart and the number of consecutive restart
attempts before failover, but by default, every process fails over.
• Enable process restartability for a process or task.
CONFIGURATION mode
process restartable [
process
] [try
number
] [timestamp
hours
]
• Display the processes and tasks configured for restart.
EXEC Privilege
When a process restarts, FTOS displays a message similar to the following message.
[9/18 23:22:21] TME-(tme): Starting to restart the failed process tacplus
[9/18 23:22:41] TME-(tme): Finishing restarting the failed process tacplus
You can specify the timestamp in hour(s) so that if the number of attempts to restart exceeds the
maximum allowed within this timestamp, Restart mode is changed into Failover mode from that moment
forward. This means that the next time the crashed process does NOT restart but failover to the standby
RPM if it is on a dual RPM environment and rebooted if it is on a single RPM.
High Availability (HA)
407
Содержание S4820T
Страница 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Страница 282: ...Dell 282 Control Plane Policing CoPP ...
Страница 569: ...Figure 62 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 569 ...
Страница 572: ...Figure 64 Inspecting a LAG Port on BRAVO Using the show interface Command 572 Link Aggregation Control Protocol LACP ...
Страница 573: ...Figure 65 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 573 ...
Страница 617: ...mac address table static multicast mac address vlan vlan id output range interface Microsoft Network Load Balancing 617 ...
Страница 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Страница 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Страница 624: ...Figure 83 Configuring PIM in Multiple Routing Domains 624 Multicast Source Discovery Protocol MSDP ...
Страница 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Страница 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Страница 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Страница 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Страница 979: ...6 Member not present 7 Member not present Stacking 979 ...
Страница 981: ...storm control Storm Control 981 ...
Страница 999: ... Te 1 1 0 INCON Root Rootguard Te 1 2 0 LIS Loopguard Te 1 3 0 EDS Shut Bpduguard Spanning Tree Protocol STP 999 ...
Страница 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...