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.

When <strong>the</strong> route table is flushed, <strong>the</strong> router will recreate <strong>the</strong> table starting with its<br />

directly attached interfaces. If a dynamic pro<strong>to</strong>col is in use, <strong>the</strong> flush will trigger an<br />

update immediately. Static route entries that are loaded from <strong>the</strong> configuration file<br />

at boot will also be res<strong>to</strong>red shortly after <strong>the</strong> table has been flushed. Be aware that<br />

while <strong>the</strong> router rebuilds its route table, connectivity will be lost. The connectivity<br />

outage will vary in length from a few seconds <strong>to</strong> several minutes, depending on <strong>the</strong><br />

size of <strong>network</strong> and <strong>the</strong> routing table.<br />

The privileged EXEC command clears <strong>the</strong> router's ARP table. If a<br />

situation requires <strong>the</strong> entire IP route table <strong>to</strong> be cleared, it is not a bad idea <strong>to</strong> clear<br />

<strong>the</strong> ARP table as well, preferably before you flush <strong>the</strong> IP route table. This way, you<br />

will ensure that <strong>the</strong> router has accurate ARP entries for its adjacent neighbors before<br />

<strong>the</strong> route table is cleared. The ARP table will reconstruct itself quickly, since it is only<br />

dependent on connectivity with nodes that are directly accessible <strong>to</strong> its connected<br />

interfaces.<br />

Because dynamic pro<strong>to</strong>cols refresh route entries au<strong>to</strong>matically, only <strong>the</strong> most<br />

drastic situations will require <strong>the</strong> entire route table <strong>to</strong> be flushed. In most cases,<br />

only a single failed route is <strong>the</strong> problem, such as a dynamic route in a hold-down<br />

state (waiting <strong>to</strong> expire) or a static route that points <strong>to</strong> a nonexistent gateway. To<br />

remove an invalid dynamic route from <strong>the</strong> routing table, use . It is also possible <strong>to</strong> clear a single ARP table entry with . Removal of an invalid static route must be done from global<br />

configuration EXEC mode. After you're in configuration mode, place a in front<br />

of <strong>the</strong> same command string you would use <strong>to</strong> create <strong>the</strong> route:<br />

Router#config t<br />

Enter configuration commands, one per line. End with CNTL/Z.<br />

Router(config)#no ip route 192.160.0.4 255.255.255.252 172.16.0.6 20<br />

Router(config)#^Z<br />

Router#<br />

After <strong>the</strong> static route is removed from <strong>the</strong> configuration, <strong>the</strong> IOS will purge it from<br />

<strong>the</strong> IP routing table.<br />

NOTE

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

Saved successfully!

Ooh no, something went wrong!