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.

Configuring Redundant Pairs<br />

Configuring Redundant Pairs is supported only on plat<strong>for</strong>m e<br />

<strong>Networks</strong> that employ switches that do not support Spanning Tree (STP)—<strong>for</strong> example, networks with<br />

Digital Subscriber Line Access Mutiplexers (DSLAM)—cannot have redundant links between switches<br />

because <strong>the</strong>y create switching loops (Figure 115). The Redundant Pairs feature enables you to create<br />

redundant links in networks that do not use STP by configuring backup interfaces <strong>for</strong> <strong>the</strong> interfaces on<br />

ei<strong>the</strong>r side of <strong>the</strong> primary link.<br />

Note: For details on STP, see Chapter 19, Spanning Tree Protocol, on page 385.<br />

Assign a backup interface to an interface using <strong>the</strong> command switchport backup. The backup interface<br />

remains in down state until <strong>the</strong> primary fails, at which point it transitions to up state. If <strong>the</strong> primary<br />

interface fails, and later comes up, it becomes <strong>the</strong> backup interface <strong>for</strong> <strong>the</strong> redundant pair. <strong>FTOS</strong> supports<br />

Gigabit and 10-Gigabit interfaces as backup interfaces.<br />

You must apply all o<strong>the</strong>r configurations to each interface in <strong>the</strong> redundant pair such that <strong>the</strong>ir<br />

configurations are identical, so that transition to <strong>the</strong> backup interface in <strong>the</strong> event of a failure is transparent<br />

to rest of <strong>the</strong> network.<br />

Figure 115 Configuring Redundant Layer 2 Pairs without Spanning Tree<br />

<strong>Force10</strong>(conf-if-gi-3/41)#switchport<br />

<strong>Force10</strong>(conf-if-gi-3/41)#switchport backup gi 3/42<br />

<strong>Force10</strong>(conf-if-gi-3/41)#no shutdown<br />

<strong>Force10</strong>(conf-if-gi-3/42)#switchport<br />

<strong>Force10</strong>(conf-if-gi-3/42)#no shutdown<br />

Redundant links create a switching loop.<br />

Without STP broadcast storms occurs.<br />

Use backup interfaces to create redundant<br />

links in networks without STP<br />

R3 R4<br />

3/41 4/31<br />

Backup Link<br />

<strong>Force10</strong>(conf-if-gi-4/31)#switchport<br />

<strong>Force10</strong>(conf-if-gi-4/31)#no shutdown<br />

<strong>Force10</strong>(conf-if-gi-4/32)#switchport<br />

<strong>Force10</strong>(conf-if-gi-4/32)#no shutdown<br />

Important Points about Configuring Redundant Pairs<br />

• You may not configure any interface to be a backup <strong>for</strong> more than one interface, no interface can have<br />

more than one backup, and a backup interface may not have a backup interface.<br />

• Nei<strong>the</strong>r <strong>the</strong> active nor <strong>the</strong> backup interface may be a member of a LAG.<br />

• The active and standby do not have to be of <strong>the</strong> same type (1G, 10G, etc).<br />

3/42<br />

• You may not enable any Layer 2 protocol on any interface of a redundant pair or to ports connected to<br />

<strong>the</strong>m.<br />

206 Layer 2<br />

4/32<br />

fnC0067mp

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

Saved successfully!

Ooh no, something went wrong!