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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Although static routing is not an ideal <strong>to</strong>tal solution for IP route announcement in<br />

large <strong>network</strong>s, it is a very effective solution for small (single gateway) <strong>network</strong>s<br />

and provides needed gateway and route redirection services. Static routes are also<br />

essential <strong>to</strong> announcing <strong>network</strong>s where <strong>the</strong> access links are unstable or temporary<br />

(as with dial-up connections).<br />

Static routes are set in <strong>the</strong> Cisco IOS using <strong>the</strong> configuration EXEC<br />

command. As noted in <strong>the</strong> previous section, static routes are set in <strong>the</strong> router's<br />

configuration file. The IOS's handling of static routes is different than, say, a UNIX<br />

or NT workstation that has static entries in its startup configuration file. With <strong>the</strong><br />

IOS, static route entries are managed as an IP routing process, so <strong>the</strong>y are reloaded<br />

after routing table flush. Static routes entered on an end-station would typically<br />

need <strong>to</strong> be re-entered or reloaded (by rebooting <strong>the</strong> system) after <strong>the</strong> routing table<br />

has been flushed.<br />

Configuring Default Routing<br />

If <strong>the</strong> IP <strong>network</strong> is closed (<strong>network</strong> reachability is limited <strong>to</strong> explicitly announced<br />

<strong>network</strong>s defined in <strong>the</strong> routing table), a default route is not needed. A typical<br />

example is a closed or private <strong>network</strong> where <strong>the</strong>re is no Internet access or where<br />

access is provided through a proxy server or firewall. In closed <strong>network</strong><br />

architectures, typically, traffic destined for unannounced <strong>network</strong>s is discarded and<br />

<strong>the</strong> user is notified with an ICMP message. To disable ICMP notifications and ICMP<br />

redirection attempts, <strong>the</strong> and commands<br />

can be set on <strong>the</strong> router's connected interfaces. These options also provide an<br />

additional level of <strong>network</strong> security by limiting <strong>the</strong> capability of IP traffic <strong>to</strong> be<br />

redirected across a path that may insecure.<br />

In most situations, however, a default route is needed. The most common one is<br />

where a single point Internet connection exists or where it is undesirable <strong>to</strong><br />

exchange routing information but reachability information is required.<br />

In Chapter 7, we first used <strong>the</strong> command <strong>to</strong> set <strong>the</strong> default route on <strong>the</strong><br />

Concord and Ridgefield routers. In this case, we are setting <strong>the</strong> default route for<br />

asbr-a2 <strong>to</strong> forward all traffic that has no explicit route out asbr-a1's dedicated<br />

Internet link through Fast E<strong>the</strong>rnet 0/0 (refer <strong>to</strong> Figure 10.1). If <strong>the</strong> link fails, it<br />

should forward all of <strong>the</strong> traffic out interface s2/0 <strong>to</strong> asbr-b2. Notice on <strong>the</strong> route<br />

entry for 192.168.0.6, we've added a number for administrative distance of 20:<br />

asbr-a1#config t<br />

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

asbr-a1(config)#ip route 0.0.0.0 0.0.0.0 192.168.0.6 20<br />

asbr-a1(config)#ip route 0.0.0.0 0.0.0.0 192.168.191.20

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

Saved successfully!

Ooh no, something went wrong!