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.

internal/Internet access router where <strong>the</strong> internal <strong>network</strong> and <strong>the</strong> multiple Internet<br />

links are all homed in<strong>to</strong> <strong>the</strong> same router. This approach does have some drawbacks.<br />

The first is <strong>the</strong> fact that <strong>the</strong>re is no hardware redundancy; if <strong>the</strong> internal gateway<br />

fails, you are completely down. To overcome this and still maintain a single gateway<br />

for end-stations and servers, use HSRP (or VIRP) with two gateway routers. The<br />

second drawback has <strong>to</strong> do with security. Internet gateways are managed by you<br />

and in part by your ISP. It is usually not a good idea <strong>to</strong> have your ISP accessing your<br />

internal <strong>network</strong> gateway router.<br />

After <strong>the</strong> connectivity has been established between <strong>the</strong> internal gateway router<br />

and <strong>the</strong> Internet gateway routers, you want <strong>to</strong> establish a local BGP process on your<br />

gateway router. This is started using <strong>the</strong> global configuration EXEC command<br />

. If you are planning <strong>to</strong> use BGP <strong>to</strong> provide reachability<br />

information over <strong>the</strong> Internet, you will need a registered AS number from an<br />

Internet Addressing Authority (IAA), such as <strong>the</strong> American Registry for Internet<br />

Numbers (ARIN). For unannounced BGP (for internal use only), any number<br />

between 32768 and 64511 will do. For this example, we are going <strong>to</strong> announce<br />

<strong>network</strong>s 12.14.116.0 /22 and 192.168.180 /22.<br />

Before we start configuring our BGP process, we first need <strong>to</strong> establish routes <strong>to</strong> our<br />

remote-AS BGP neighbors. In most cases, you will peer with <strong>the</strong> router on <strong>the</strong> o<strong>the</strong>r<br />

end of your Internet link. In this case, <strong>the</strong> routers are (ATT) 12.127.40.65 and (PSI)<br />

192.144.36.1. We can accomplish peering with static routes:<br />

ASBR-Master#config t<br />

ASBR-Master(config)#ip route 12.127.40.64 255.255.255.252 12.14.116.3<br />

ASBR-Master(config)#ip route 192.174.36.0 255.255.255.252 12.14.116.2<br />

Now, let's enable our BGP process. The process ID is <strong>the</strong> AS number, which, in this<br />

case, is 789. The process ID is used for communication with o<strong>the</strong>r BGP processes. If<br />

you are planning <strong>to</strong> run BGP on more than one internal router, be sure that <strong>the</strong> same<br />

AS is used:<br />

ASBR-Master(config)#router bgp 789<br />

ASBR-Master(config-router)#<br />

After <strong>the</strong> process starts, we add <strong>the</strong> <strong>network</strong>s we want announced. Like OSPF, BGP<br />

uses netmasks as part of <strong>the</strong> <strong>network</strong> number announcements. This means that you<br />

can announce parts of <strong>network</strong>s as VLSM subnets, as CIDR address ranges, or as

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

Saved successfully!

Ooh no, something went wrong!