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.

For many users, <strong>the</strong> usefulness of BGP is questionable. BGP, althoughconsidered a<br />

routing pro<strong>to</strong>col, could be more aptly described as a <strong>network</strong> reachability pro<strong>to</strong>col.<br />

Its focus is not on announcing how <strong>to</strong> reach a destination, but ra<strong>the</strong>r on how <strong>to</strong> get<br />

somewhere that can reach <strong>the</strong> destination. With this goal in mind, let's review <strong>the</strong><br />

three types of routing BGP is used for:<br />

• Inter-au<strong>to</strong>nomous system routing—A collection (two or more) routers from<br />

different au<strong>to</strong>nomous systems exchange BGP information with <strong>the</strong> goal of<br />

maintaining a complete reachability table for <strong>the</strong> entire intra<strong>network</strong>.<br />

• Intra-au<strong>to</strong>nomous system routing—Used by peer-routers connected <strong>to</strong> <strong>the</strong><br />

same au<strong>to</strong>nomous system <strong>to</strong> exchange external AS information.<br />

• Pass-through au<strong>to</strong>nomous system routing—Used <strong>to</strong> exchange BGP<br />

reachability information between a collection of routers belonging <strong>to</strong> <strong>the</strong><br />

same or different ASs across an uninvolved third-party AS. In this case, <strong>the</strong><br />

ASs exchanging reachability information are dependent on <strong>the</strong> third-party<br />

AS's IGP pro<strong>to</strong>col <strong>to</strong> transport <strong>the</strong> BGP traffic.<br />

As stated earlier, almost all applications of BGP occur within <strong>the</strong> context of <strong>the</strong> public<br />

Internet. Most private enterprise <strong>network</strong>s do not have <strong>the</strong>se types of requirements,<br />

and those that do can safely accomplish <strong>the</strong>ir goals with OSPF or EIGRP. However,<br />

with businesses'growing dependency on <strong>the</strong> Internet and <strong>the</strong> hyper-growth of many<br />

corporate intranets, <strong>the</strong> usefulness of BGP is finally reaching <strong>the</strong> private <strong>network</strong>. It<br />

is particularly applicable <strong>to</strong> environments where access <strong>to</strong> multiple private/public<br />

<strong>network</strong>s links is required. Because BGP was designed <strong>to</strong> manage <strong>the</strong> Internet, it is<br />

powerful, and as you can imagine, can be quite complex <strong>to</strong> configure. With this in<br />

mind, we will look at some basic inter-au<strong>to</strong>nomous and intra-au<strong>to</strong>nomous BGP<br />

configurations.<br />

Inter-Au<strong>to</strong>nomous BGP<br />

For most BGP applications, <strong>the</strong> goal is <strong>to</strong> provide <strong>network</strong>-reachability information<br />

for your local <strong>network</strong> between two or more ISP gateways. In this situation, your<br />

goal is not <strong>to</strong> configure a large BGP routing policy. All you want is <strong>to</strong> have Internet<br />

access redundancy. An easy way <strong>to</strong> achieve this goal is <strong>to</strong> use ships in <strong>the</strong> night (SIN)<br />

routing. SIN routing exists where a router is running multiple dynamic pro<strong>to</strong>cols,<br />

without redistributing <strong>the</strong>m in<strong>to</strong> one ano<strong>the</strong>r. The effect is that only <strong>the</strong> SIN router<br />

processes a complete internal and external <strong>network</strong> routing table. The o<strong>the</strong>r internal<br />

<strong>network</strong> routers use <strong>the</strong> SIN router as <strong>the</strong> default gateway, so <strong>the</strong>y blindly forward<br />

all of <strong>the</strong>ir external traffic <strong>to</strong> <strong>the</strong> SIN router, which <strong>the</strong>n uses its full routing table <strong>to</strong><br />

decide <strong>the</strong> best next hop. When configuring BGP for <strong>the</strong> SIN routing context, you<br />

want <strong>to</strong> set up <strong>the</strong> BGP process on your internal <strong>network</strong>'s gateway router instead of<br />

configuring BGP on each of your Internet access gateways.<br />

Figure 10.6 illustrates a SIN routing router <strong>to</strong>pology configuration example.

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

Saved successfully!

Ooh no, something went wrong!