05.01.2013 Views

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

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.

494 Chapter 10 � Wide Area <strong>Network</strong>ing Protocols<br />

Subinterfaces<br />

Routers receive LMI information on a frame-encapsulated interface and<br />

update the virtual circuit status to one of three different states:<br />

Active state Everything is up and routers can exchange information.<br />

Inactive state The router’s interface is up and working with a connection<br />

to the switching office, but the remote router is not working.<br />

Deleted state This means that no LMI information is being received<br />

on the interface from the switch. It could be a mapping problem or a line<br />

failure.<br />

You can have multiple virtual circuits on a single serial interface and yet treat<br />

each as a separate interface. These are known as subinterfaces. Think of a<br />

subinterface as a hardware interface defined by the IOS software. An advantage<br />

gained through using subinterfaces is the ability to assign different <strong>Network</strong><br />

layer characteristics to each subinterface and virtual circuit, such as IP<br />

routing on one virtual circuit and IPX on another.<br />

Partial Meshed <strong>Network</strong>s<br />

You can use subinterfaces to mitigate partial meshed Frame Relay networks<br />

and split horizon protocols. For example, say you were running the IP protocol<br />

on a LAN network. If, on the same physical network, Router A can talk<br />

to Router B, and Router B to Router C, you can usually assume that Router<br />

A can talk to Router C. Though this is true with a LAN, it’s not true with a<br />

Frame Relay network, unless Router A has a PVC to Router C.<br />

In Figure 10.5, <strong>Network</strong> 1 is configured with five locations. To be able to<br />

make this network function, you would have to create a meshed network as<br />

shown in <strong>Network</strong> 2. However, even though <strong>Network</strong> 2’s example works,<br />

it’s an expensive solution—configuring subinterfaces as shown in the <strong>Network</strong><br />

3 solution is much more cost-effective.<br />

In <strong>Network</strong> 3, configuring subinterfaces actually works to subdivide the<br />

Frame Relay network into smaller subnetworks—each with its own network<br />

number. So locations A, B, and C connect to a fully meshed network, while<br />

locations C and D, and D and E, are connected via point-to-point connections.<br />

Locations C and D connect to two subinterfaces and forward packets.<br />

Subinterfaces also solve the problem with routing protocols that use split<br />

horizon. As you may recall, split horizon protocols do not advertise routes

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

Saved successfully!

Ooh no, something went wrong!