02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 256 System Messages Indicating <strong>the</strong> Standby RPM is Online<br />

When you boot <strong>the</strong> system with two RPMs installed, you can configure one to be <strong>the</strong> primary RPM or<br />

allow <strong>the</strong> system to select <strong>the</strong> primary. If you have not entered <strong>the</strong> redundancy primary command, <strong>the</strong><br />

RPM in slot R0 defaults to <strong>the</strong> primary RPM. You can trigger an RPM failover through <strong>the</strong> command line,<br />

or it can occur because of one of <strong>the</strong> following reasons:<br />

• The heartbeat (similar to a keepalive message) between <strong>the</strong> two RPMs is lost.<br />

• The primary RPM experiences a problem (<strong>for</strong> example, a task crashed).<br />

• The primary RPM is removed.<br />

Security Considerations<br />

After a failover, <strong>the</strong> new primary RPM (RPM1) prompts you <strong>for</strong> a username and password if<br />

au<strong>the</strong>ntication methods was configured and that data was synchronized.<br />

The Standby RPM does not use au<strong>the</strong>ntication methods involving client/server protocols, such as RADIUS<br />

or TACACS+.<br />

RPM Failover Example<br />

Below are <strong>the</strong> steps, actions, and results of a typical data synchronization between RPMs in an RPM<br />

failover.<br />

Step Action Result<br />

1 system boots with 2<br />

RPMs<br />

2<br />

3<br />

4<br />

%RPM-2-MSG:CP0 %POLLMGR-2-ALT_RPM_STATE: Alternate RPM is present<br />

%IRC-6-IRC_COMMUP: Link to peer RPM is up<br />

%RAM-6-RAM_TASK: RPM1 is in Standby State.<br />

<strong>Force10</strong>(standby)><br />

stable system, traffic<br />

running<br />

failover (ei<strong>the</strong>r<br />

user-requested or<br />

triggered by an event<br />

in <strong>the</strong> system)<br />

RPM1 is up and<br />

traffic is flowing<br />

The system brings up <strong>the</strong> primary RPM first.<br />

If <strong>the</strong> redundancy primary command is not configured, <strong>the</strong> software<br />

automatically makes <strong>the</strong> RPM in slot 0 <strong>the</strong> primary RPM.<br />

The software per<strong>for</strong>ms incremental data synchronizations between <strong>the</strong> primary<br />

RPM and <strong>the</strong> Standby RPM when data changes on <strong>the</strong> primary RPM.<br />

The Standby RPM (RPM1):<br />

• notifies all tasks about <strong>the</strong> RPM failover<br />

• transitions <strong>the</strong> tasks to <strong>the</strong> active state<br />

• reboots RPM0<br />

If user-requested, <strong>the</strong> software prompts you to save <strong>the</strong> running configuration<br />

to <strong>the</strong> startup configuration. The process takes approximately 25 seconds.<br />

RPM0 is now <strong>the</strong> Standby RPM and monitors RPM1.<br />

372 High Availability

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

Saved successfully!

Ooh no, something went wrong!