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

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

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

Standby RPM<br />

The E-<strong>Series</strong> supports <strong>the</strong> Online Insertion and Removal (OIR) of primary and Standby RPMs. For<br />

detailed in<strong>for</strong>mation, refer to <strong>the</strong> Implementation In<strong>for</strong>mation <strong>for</strong> RPM Redundancy.<br />

RPM Redundancy<br />

The RPM in <strong>the</strong> E-<strong>Series</strong> is <strong>the</strong> core <strong>for</strong> routing, switching, and control operations. Routing table entries<br />

are built on <strong>the</strong> RPM and directed to <strong>the</strong> Forwarding (FIB) tables on <strong>the</strong> line cards.<br />

Each RPM contains three CPUs. System control, Layer 2 and Layer 3 functions are divided among <strong>the</strong><br />

three CPUs.<br />

With two RPMs installed and online, <strong>FTOS</strong> supports 1+1 RPM redundancy, providing an extra module <strong>for</strong><br />

failover. The primary RPM (in slot R0 by default) per<strong>for</strong>ms all routing, switching, and control operations<br />

(hardware mastership), and <strong>the</strong> Standby RPM is on-line and monitoring <strong>the</strong> primary RPM. Throughout this<br />

section <strong>the</strong> examples will assume that RPM0 is <strong>the</strong> primary RPM (slot R0) and RPM1 is <strong>the</strong> Standby RPM<br />

(slot R1).<br />

Note: If your system contains two RPMs, both RPMs must contain <strong>the</strong> same software image.<br />

With redundant RPMs, you may experience a shorter or hitless transition after an RPM failure. The<br />

Standby RPM does not need to reboot and can take over hardware mastership if necessary to return your<br />

E-<strong>Series</strong> to operational status.<br />

<strong>FTOS</strong> supports <strong>the</strong> following RPM Redundancy tasks:<br />

• Implementation In<strong>for</strong>mation on page 371 (optional)<br />

• Security Considerations on page 372 (optional)<br />

• RPM Failover Example on page 372 (optional)<br />

• RPM High Availability <strong>Configuration</strong> on page 373 (optional)<br />

Implementation In<strong>for</strong>mation<br />

You can boot <strong>the</strong> system with one RPM and later add a second RPM, which will automatically become <strong>the</strong><br />

Standby RPM. <strong>Force10</strong> <strong>Networks</strong> recommends that you insert <strong>the</strong> Standby RPM after <strong>the</strong> primary RPM is<br />

online and stable, and that you copy <strong>the</strong> running configuration to <strong>the</strong> startup config file (copy<br />

running-config startup-config command) after <strong>the</strong> Standby RPM is online. You can tell when <strong>the</strong> Standby<br />

RPM is online when amessage appears indicating this and <strong>the</strong> standby prompt appears (see Figure 256).<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 371

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

Saved successfully!

Ooh no, something went wrong!