25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

if R3 needs to communicate with a device in AS 3. R3 passes the traffic to R2.<br />

However, because R2 does not have any routes to AS 3 networks, the traffic is<br />

dropped.<br />

If R3 advertises the 10.0.0.0/8 network to AS 4, the problem continues. If AS 4<br />

needs to communicate with a device in AS 3, the packets are forwarded from R5<br />

to R3. R3 forwards the packets to R2 where they are discarded.<br />

EBGP<br />

BGP<br />

R4<br />

10.0.0.0/8<br />

AS 3<br />

BGP<br />

R1<br />

Figure 5-26 BGP synchronization<br />

AS 1<br />

R2<br />

This situation is addressed by the synchronization rule of BGP. The rule states<br />

that a transit AS will not advertise a route before all routers within the AS have<br />

learned about the route. In this example, R3 will not advertise the existence of<br />

the networks in AS 3 until R2 has built a proper routing table.<br />

IBGP<br />

There are three methods to implement the synchronization rule:<br />

► Enable BGP on all devices within the transit AS. In this solution, R2 has an<br />

IBGP session with both R1 <strong>and</strong> R3. R2 learns of the 10.0.0.0/8 network at the<br />

same time it is advertised to R3. At that time, R3 announces the routes to its<br />

peer in AS 4.<br />

BGP<br />

R3<br />

BGP<br />

R5<br />

AS 4<br />

EBGP<br />

Chapter 5. Routing protocols 227

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

Saved successfully!

Ooh no, something went wrong!