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.

it is possible <strong>to</strong> exchange packets between <strong>the</strong> DCLIs, by default only unicast<br />

packets are sent. FR does not natively support broadcast and multicast<br />

transmissions. Therefore, in order for <strong>the</strong> messages <strong>to</strong> be properly relayed, <strong>the</strong><br />

multipoint router must send a unicast copy of <strong>the</strong>se packets <strong>to</strong> each endpoint. To<br />

enable broadcast simulation, add <strong>the</strong> [broadcast] keyword <strong>to</strong> <strong>the</strong> end of <strong>the</strong><br />

or interface configuration<br />

command.<br />

NOTE<br />

With multipoint grouping, a collection of FR endpoints function as if <strong>the</strong>y are<br />

connected over a local shared transport. The FR provider provisions <strong>the</strong> multipoint<br />

group (up <strong>to</strong> 32 nodes) by associating all <strong>the</strong> endpoint members'local DCLIs <strong>to</strong> a<br />

multipoint group. Each endpoint is assigned an address reflecting a common<br />

<strong>network</strong> address (<strong>the</strong> same IP subnet or equivalent) with <strong>the</strong> DCLI functioning in<br />

effect as a MAC address. From a conceptual perspective, <strong>the</strong> endpoints function as<br />

DTE peers connected <strong>to</strong> a common virtual DCE.<br />

NOTE<br />

Not all Layer 3 pro<strong>to</strong>cols can operate over a point-<strong>to</strong>-multipoint <strong>to</strong>pology. The<br />

reason for this is that not all pro<strong>to</strong>cols will permit datagrams <strong>to</strong> be relayed out of <strong>the</strong><br />

same interface from which <strong>the</strong>y are received. In addition, <strong>the</strong> multipoint<br />

sub-interface designation also enables "split-horizon" (disabled by IOS when<br />

frame-relay encapsulation is selected) on any IP routing pro<strong>to</strong>col.<br />

Point-<strong>to</strong>-Point VC Topology<br />

Typically, multi-VC FR implementations (partial and full mesh) are configured using<br />

partially or fully meshed point-<strong>to</strong>-point sub-interfaces. Although quite effective,<br />

<strong>the</strong>y are costly in comparison <strong>to</strong> multipoint implementations because each link<br />

requires its own PVC. In addition <strong>to</strong> cost, <strong>the</strong> actual configuration is fairly complex,<br />

requiring that some real thought be paid <strong>to</strong> addressing <strong>the</strong> various point-<strong>to</strong>-point<br />

PVC sub-interfaces. Good documentation is a big help when debugging problems<br />

(so be sure <strong>to</strong> write some). Figure 9.5 illustrates a fully meshed FR <strong>to</strong>pology using<br />

point-<strong>to</strong>-point PVC. Following <strong>the</strong> illustration are interface configuration examples<br />

from two of <strong>the</strong> routers (batman and robin).

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

Saved successfully!

Ooh no, something went wrong!