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.

► Init: Communication with the neighbor has started, but bidirectional<br />

communication has not been established. Specifically, a hello packet was<br />

received from the neighbor, but the local router was not listed in the<br />

neighbor's hello packet.<br />

► 2-way: Bidirectional communication between the two routers has been<br />

established. Adjacencies can be formed. Neighbors are eligible to be elected<br />

as designated routers.<br />

► ExStart: The neighbors are starting to form an adjacency.<br />

► Exchange: The two neighbors are exchanging their topology databases.<br />

► Loading: The two neighbors are synchronizing their topology databases.<br />

► Full: The two neighbors are fully adjacent <strong>and</strong> their databases are<br />

synchronized.<br />

Network events cause a neighbor’s OSPF state to change. For example, when a<br />

router receives a hello packet from a neighboring device, the OSPF neighbor<br />

state changes from Down to Init. When bidirectional communication has been<br />

established, the neighbor state changes from Init to 2-Way. RFC 2328 contains a<br />

complete description of the events causing a state change.<br />

OSPF virtual links <strong>and</strong> transit areas<br />

Virtual links are used when a network does not support the st<strong>and</strong>ard OSPF<br />

network topology. This topology defines a backbone area that directly connects<br />

to each additional OSPF area. The virtual link addresses two conditions:<br />

► It can logically connect the backbone area when it is not contiguous.<br />

► It can connect an area to the backbone when a direct connection does not<br />

exist.<br />

A virtual link is established between two ABRs sharing a common non-backbone<br />

area. The link is treated as a point-to-point link. The common area is known as a<br />

transit area. Figure 5-18 on page 208 illustrates the interaction between virtual<br />

links <strong>and</strong> transit areas when used to connect an area to the backbone.<br />

Chapter 5. Routing protocols 207

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

Saved successfully!

Ooh no, something went wrong!