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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 3.2. IPX Encapsulation Schemes<br />

Media Type Encapsulation Scheme Frame Type<br />

E<strong>the</strong>rnet Novell 802.3 RAW<br />

ARPA DEC E<strong>the</strong>rnet v2<br />

802.3 IEEE 802.3 Standard<br />

SNAP E<strong>the</strong>rnet SNAP<br />

Token Ring IEEE 802.5 (802.2 LLC) IEEE 802.5 Standard<br />

SNAP IEEE 802.5 SNAP<br />

FDDI SNAP FDDI SNAP<br />

SAP FDDI 802.2 LLC<br />

Novell ANSI FDDI RAW<br />

Serial IPXWAN PPP<br />

IPXWAN HDLC<br />

Characteristics of different IPX encapsulation schemes include <strong>the</strong> following:<br />

• Novell RAW uses <strong>the</strong> standard pro<strong>to</strong>col frame without 802.2 logical link<br />

control.<br />

• E<strong>the</strong>rnet version 2 is <strong>the</strong> standard pre-IEEE 3COM/DEC E<strong>the</strong>rnet version 2<br />

standard frame specification.<br />

• SNAP uses <strong>the</strong> 802.2 LLC frame format and <strong>the</strong> pro<strong>to</strong>col type field.<br />

• IEEE 802.* uses <strong>the</strong> IEEE 802.x standard frame format.<br />

• IPXWAN is a WAN-specific pro<strong>to</strong>col used for IPX routing (and transporting)<br />

communication between routers connected over dedicated serial lines.<br />

For compatibility and, as it turns out, increased flexibility, IPX can support multiple<br />

<strong>network</strong> segments using different encapsulation schemes over <strong>the</strong> same physical<br />

(Layer 1) medium. If no router is in place, none of <strong>the</strong> <strong>network</strong>s can exchange data<br />

between one ano<strong>the</strong>r. This is because each <strong>network</strong> is using a specific frame type.<br />

Only end-nodes that are configured <strong>to</strong> process <strong>the</strong> same frame type can exchange<br />

information.<br />

NOTE<br />

This same result occurs when AppleTalk Phase 1 E<strong>the</strong>rnet and Phase 2 E<strong>the</strong>rnet are<br />

used on <strong>the</strong> same media. Because <strong>the</strong> frame types are different, <strong>the</strong>y can only be<br />

unders<strong>to</strong>od by like end-nodes (Phase 1 or Phase 2) but are unable <strong>to</strong><br />

cross-communicate.

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

Saved successfully!

Ooh no, something went wrong!