20.01.2013 Views

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

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.

192 Switching Basics <strong>and</strong> Intermediate Routing <strong>CCNA</strong> 3 <strong>Labs</strong> <strong>and</strong> <strong>Study</strong> <strong>Guide</strong><br />

Field C Type of Service (TOS) or Differentiated Service<br />

This 8-bit field can be broken down into two parts: Precedence <strong>and</strong> TOS. The first 3 bits specify the<br />

Precedence value (e.g. routine-0, priority-1, immediate-2, etc.); 4th bit specifies minimal delay; 5th bit<br />

specifies maximize throughput; 6th bit specifies maximize reliability; 7th bit specifies minimize monetary<br />

costs; 8th bit is currently unused. Although this field is not commonly used <strong>and</strong> is usually set to all zeros,<br />

the Precedence bits are occasionally used for QoS applications.<br />

Field D Total Length<br />

This field is a 16-bit number specifying the total length of the packet (header + data) in bytes; can be up to<br />

65,535 bytes. By subtracting the header length for this value, you can determine the size of the payload.<br />

Field E Identifier<br />

This field is used to identify the fragments of one datagram from those of another. The originating protocol<br />

module of an Internet datagram sets the Identifier field to a value that must be unique for that sourcedestination<br />

pair <strong>and</strong> protocol for the time the datagram will be active in the Internet system. The originating<br />

protocol module of a complete datagram sets the MF bit to 0 <strong>and</strong> the Fragment Offset field to 0.<br />

Field F Flags<br />

These 3 bits indicate whether the packet can be fragmented <strong>and</strong> whether it has more fragments coming.<br />

The 3 bits are as follows:<br />

■ 1st bit: Reserved (unused)<br />

■ 2nd bit: Fragment? 1=no, 0=yes<br />

■ 3rd bit: More Fragments Coming? 0=no, 1=yes<br />

Field G Fragment Offset<br />

This is a byte count from the beginning of the original packet so that the destination knows where to place<br />

this particular fragment when reconstructing the packet. If a router’s interface is set to a maximum transmission<br />

unit that is smaller than the sent packet, then it will be fragmented by the router. However, if the<br />

Do Not Fragment bit is set in the Flag field, then the packet will be dropped <strong>and</strong> an ICMP message will be<br />

sent to the source.<br />

Field H Time to Live<br />

This 8-bit field helps prevent routing loops. This field is set with a certain number when the packet is first<br />

encapsulated at the source. Each router along the path from the source to the destination decrements this<br />

field. If this field reaches 0 before the packet reaches the destination, then the packet is dropped <strong>and</strong> an<br />

ICMP messages is sent to the source. The trace utility uses this field to trace a route to a specified destination.<br />

Field I Protocols<br />

Also called Service Access Point (SAP), the Protocol field identifies the upper-layer protocol that the data<br />

packet is destined for. A few of the values of this field are shown in the following table:

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

Saved successfully!

Ooh no, something went wrong!