22.10.2013 Views

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RPM synchronization<br />

Data between the two RPMs is synchronized immediately after bootup. Once the two RPMs have done an<br />

initial full synchronization (block sync), thereafter FTOS only updates changed data (incremental sync).<br />

The data that is synchronized consists of configuration data, operational data, state and status, and statistics<br />

depending on the FTOS version.<br />

Failover Type Synchronized Data Platform<br />

Warm Failover some NVRAM information, startup-configuration, line card configurations,<br />

user-access configurations<br />

Hot Failover some NVRAM information, startup-config, line card configurations, user-access<br />

configurations, running-config, SFM and datapath states, run-time event log<br />

and configuration, interface state<br />

RPM redundancy configuration tasks<br />

Selecting a Primary RPM<br />

The RPM in slot 0 is the primary RPM by default. Manually select the primary RPM using the command<br />

redundancy primary from CONFIGURATION mode. View which RPM is the primary using the<br />

command show running-config redundancy from EXEC Privilege mode, as shown in Figure 185.<br />

Figure 185<br />

Selecting a Primary RPM<br />

<strong>Force10</strong>#show running-config redundancy<br />

!<br />

redundancy auto-failover-limit count 3 period 60<br />

redundancy auto-synchronize full<br />

redundancy primary rpm0<br />

<strong>Force10</strong>#<br />

Forcing an RPM failover<br />

Trigger an RPM failover between RPMs using the command redundancy force-failover rpm from EXEC<br />

Privilege mode. Use this feature when:<br />

• you are replacing an RPM, and<br />

• you are performing a warm upgrade<br />

Figure 186 Using the redundancy force-failover rpm Command to Copy Software between RPMs<br />

<strong>Force10</strong>#redundancy force-failover rpm<br />

Peer RPM's SW version is different but HA compatible.<br />

Failover can be done by warm or hitless upgrade.<br />

All linecards will be reset during warm upgrade.<br />

Specify hitless upgrade or warm upgrade [confirm hitless/warm]:hitless<br />

Proceed with warm upgrade [confirm yes/no]:<br />

ecs<br />

ecs<br />

FTOS Configuration Guide, version <strong>7.8.1.0</strong> 317

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!