18.10.2013 Views

FTOS Command Reference for the S-Series - Force10 Networks

FTOS Command Reference for the S-Series - Force10 Networks

FTOS Command Reference for the S-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.

passive-interface<br />

Parameters<br />

<strong>Command</strong> Modes ROUTER OSPF<br />

<strong>Command</strong><br />

History<br />

Usage<br />

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

default Enter <strong>the</strong> keyword default to make all OSPF interfaces (current and future)<br />

passive.<br />

interface Enter <strong>the</strong> following keywords and slot/port or number in<strong>for</strong>mation:<br />

• For a Gigabit E<strong>the</strong>rnet interface, enter <strong>the</strong> keyword GigabitE<strong>the</strong>rnet<br />

followed by <strong>the</strong> slot/port in<strong>for</strong>mation.<br />

• For Port Channel groups, enter <strong>the</strong> keyword port-channel followed by a<br />

number:<br />

C-<strong>Series</strong> and S-<strong>Series</strong> Range: 1-128<br />

E-<strong>Series</strong> Range: 1-32 <strong>for</strong> E<strong>the</strong>rScale, 1-255 <strong>for</strong> TeraScale<br />

• For a SONET interface, enter <strong>the</strong> keyword sonet followed by <strong>the</strong> slot/port<br />

in<strong>for</strong>mation.<br />

• For a 10-Gigabit E<strong>the</strong>rnet interface, enter <strong>the</strong> keyword<br />

TenGigabitE<strong>the</strong>rnet followed by <strong>the</strong> slot/port in<strong>for</strong>mation.<br />

• For a VLAN, enter <strong>the</strong> keyword vlan followed by a number from 1 to 4094.<br />

Version 7.6.1.0 Introduced on S-<strong>Series</strong><br />

Version 7.5.1.0 Introduced on C-<strong>Series</strong><br />

Version 7.4.1.0 Modified to include <strong>the</strong> default keyword.<br />

pre-Version 6.1.1.1 Introduced on E-<strong>Series</strong><br />

Although <strong>the</strong> passive interface will nei<strong>the</strong>r send nor receive routing updates, <strong>the</strong> network on<br />

that interface will still be included in OSPF updates sent via o<strong>the</strong>r interfaces.<br />

The default keyword sets all interfaces as passive. You can <strong>the</strong>n configure individual<br />

interfaces, where adjacencies are desired, using <strong>the</strong> no passive-interface interface<br />

command. The no <strong>for</strong>m of this command is inserted into <strong>the</strong> configuration <strong>for</strong> individual<br />

interfaces when <strong>the</strong> no passive-interface interface command is issued while<br />

passive-interface default is configured.<br />

This command behavior has changed as follows:<br />

passive-interface interface<br />

• The previous no passive-interface interface is removed from <strong>the</strong> running<br />

configuration.<br />

• The ABR status <strong>for</strong> <strong>the</strong> router is updated.<br />

• Save passive-interface interface into <strong>the</strong> running configuration.<br />

passive-interface default<br />

• All present and future OSPF interface are marked as passive.<br />

• Any adjacency are explicitly terminated from all OSPF interfaces.<br />

• All previous passive-interface interface commands are removed from <strong>the</strong> running<br />

configuration.<br />

• All previous no passive-interface interface commands are removed from <strong>the</strong> running<br />

configuration.<br />

no passive-interface interface<br />

512 OSPF

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

Saved successfully!

Ooh no, something went wrong!