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.

NAT's Shortcomings<br />

Although NAT is useful, it is not without shortcomings, <strong>the</strong> largest of which is <strong>the</strong><br />

fact that NAT is CPU intensive. If you are planning <strong>to</strong> deploy NAT on any sizable scale<br />

(a pool of 128 addresses or more), you will want <strong>to</strong> use a 36×0 series or higher<br />

router <strong>to</strong> minimize any user-perceivable performance decrease. In terms of actual<br />

deployment, if possible do not run NAT on your gateway router. In most cases, <strong>the</strong><br />

gateway router is performing security filtering and o<strong>the</strong>r CPU-intensive tasks.<br />

Adding <strong>the</strong> additional NAT processing will only decrease <strong>the</strong> gateway's performance.<br />

Use a separate router <strong>to</strong> provide NAT services, and it will dedicate that router's CPU<br />

<strong>to</strong> a single task and make NAT/performance-related troubleshooting easier and<br />

much less intrusive. It also provides you with <strong>the</strong> capability <strong>to</strong> do some additional<br />

filtering (which is needed if you use NAT as part of a router-based firewall solution).<br />

Not all IP-based applications behave well with NAT, particularly those that are<br />

dependent on hostname/IP address verification and third-party au<strong>the</strong>ntication,<br />

such as Kerberos and AFS. NAT also has trouble with certain ISO load sharing and<br />

queuing schemes, depending on <strong>the</strong> IOS version <strong>the</strong> router is using (11.0 releases<br />

are prone <strong>to</strong> this problem). Most IP applications behave just fine, however, though<br />

it is always wise <strong>to</strong> test all your application requirements before you deploy.<br />

Cisco Tunneling<br />

The tunnel interface is a virtual point-<strong>to</strong>-point link tied <strong>to</strong> a physical source interface.<br />

That is <strong>to</strong> say, <strong>the</strong>re is a virtual interface that corresponds <strong>to</strong> a logical interface, and<br />

between two interfaces of this type, traffic is wrapped and delivered across a<br />

public/private inter<strong>network</strong> as if it were a point-<strong>to</strong>-point link. The tunnel interface<br />

has three components:<br />

• The passenger pro<strong>to</strong>col—The <strong>network</strong> pro<strong>to</strong>col you are sending over <strong>the</strong><br />

tunnel, such as AppleTalk, IP, and so on.<br />

• The carrier pro<strong>to</strong>col—The pro<strong>to</strong>col that encapsulates <strong>the</strong> data. Generic Route<br />

Encapsulation (GRE) is <strong>the</strong> most commonly used pro<strong>to</strong>col and is needed if<br />

multiple pro<strong>to</strong>cols are being handled. Cisco also supports Cayman (for<br />

AppleTalk over IP), EON (for CLNP over IP), and NOS.<br />

• The transport pro<strong>to</strong>col—This is IP (Internet Pro<strong>to</strong>col), which handles <strong>the</strong><br />

delivery of <strong>the</strong> data between <strong>the</strong> physical links tied <strong>to</strong> <strong>the</strong> tunnels.<br />

The disadvantage of tunneling is performance. The encapsulation and<br />

de-encapsulation of <strong>the</strong> LAN pro<strong>to</strong>cols is time consuming, and processor and<br />

memory intensive. With Cisco IOS 11.1, GRE tunneling is supported on all Cisco<br />

1600 and IP routers. Tunneling's greatest advantage is that it allows multipro<strong>to</strong>col<br />

virtual private <strong>network</strong>s <strong>to</strong> be connected with a single access pro<strong>to</strong>col, which (if

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

Saved successfully!

Ooh no, something went wrong!