09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

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.

Configuring Dynamic IGP and EGP IP Routing<br />

Pro<strong>to</strong>cols<br />

All dynamic IP routing pro<strong>to</strong>cols are configured as IOS subprocesses, much <strong>the</strong><br />

same way a router interface is configured. The <br />

global configuration command enables <strong>the</strong> process:<br />

asbr-a1#config t<br />

asbr-a1(configure)#router ospf 89<br />

asbr-a1(config-router)#<strong>network</strong> 172.16.0.0 0.0.255.255 area 0.0.0.0<br />

asbr-a1(config-router)#<br />

After a process is enabled, it does not become active until a statement that corresponds <strong>to</strong> a configured router interface is added <strong>to</strong><br />

<strong>the</strong> subprocess.<br />

After <strong>the</strong> process is configured, you need <strong>to</strong> add each directly connected <strong>network</strong><br />

that you wish <strong>the</strong> pro<strong>to</strong>col <strong>to</strong> announce. If <strong>the</strong> <strong>network</strong> is not added<strong>to</strong> <strong>the</strong> process,<br />

it will not be announced by <strong>the</strong> pro<strong>to</strong>col. Occasionally, you might want <strong>to</strong> receive,<br />

but not send, <strong>network</strong> announcements on an interface (and you still want <strong>the</strong><br />

<strong>network</strong> announced by <strong>the</strong> routing process). This is common when a routing<br />

pro<strong>to</strong>col is used <strong>to</strong> manage a "private" <strong>network</strong> that is attached <strong>to</strong> an Internet<br />

gateway, which is also using a routing pro<strong>to</strong>col. In situations like this, <strong>the</strong> interface<br />

can be run in passive mode using <strong>the</strong> routing configuration subprocess command<br />

:<br />

asbr-a1#config t<br />

asbr-a1(configure)#router ospf 89<br />

asbr-a1(config-router)# passive-interface s1<br />

After <strong>the</strong> interface is in passive mode, it will only receive routing announcements.<br />

When a router interface has been configured <strong>to</strong> operate in passive mode, it will only<br />

accept routing announcements. This option is useful when you only want <strong>the</strong> router<br />

<strong>to</strong> obtain reachability information, but not announce. Initially, this might seem odd,<br />

this is a common practice in situations where data services are being provided by an<br />

outside <strong>network</strong> (for example, Internet Gateway or News Service feed). In <strong>the</strong>se<br />

situations, <strong>the</strong> provider will use a static route <strong>to</strong> reach your gateway, but o<strong>the</strong>rwise,

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

Saved successfully!

Ooh no, something went wrong!