Dell Force10 E600i FTOS Version 8.4.1.5 Configuration Guide for ExaScale - Page 379

Table 21-3. Support for RPM Redundancy by FTOS Version Failover Type Failover Behavior Hot Failover Only the failed RPM reboots. All line cards and SFMs remain online. All application tasks are spawned on the secondary RPM before failover. The running configuration is synchronized at runtime so it does not need to be reapplied during failover. Platform c e s RPM synchronization Data between the two RPMs is synchronized immediately after bootup. Once the two RPMs have done an initial full synchronization (block sync), thereafter FTOS only updates changed data (incremental sync). The data that is synchronized consists of configuration data, operational data, state and status, and statistics depending on the FTOS version. Failover Type Warm Failover Synchronized Data some NVRAM information, startup-configuration, line card configurations, user-access configurations Platform ec s Hot Failover some NVRAM information, startup-config, line card configurations, user-access configurations, running-config, SFM and datapath states, run-time event log and configuration, interface state ec s RPM redundancy configuration tasks Select a Primary RPM The RPM in slot 0 is the primary RPM by default. Manually select the primary RPM using the command redundancy primary from CONFIGURATION mode. View which RPM is the primary using the command show running-config redundancy from EXEC Privilege mode, as shown in the example below. FTOS#show running-config redundancy ! redundancy auto-failover-limit count 3 period 60 redundancy auto-synchronize full redundancy primary rpm0 FTOS# High Availability | 379