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.

• Preamble (7 bytes)—Every device on <strong>the</strong> E<strong>the</strong>rnet segment looks at all <strong>the</strong><br />

traffic transmitted. The preamble consists of 7 (1010101) or 8 bytes<br />

(10101010). The preamble tells all <strong>the</strong> devices on <strong>the</strong> <strong>network</strong> <strong>to</strong><br />

synchronize <strong>the</strong>mselves <strong>to</strong> <strong>the</strong> incoming frame.<br />

• Start of Frame Delimiter (SFD) (1 byte)—This is a continuation of <strong>the</strong><br />

preamble. The first 6 bits are in <strong>the</strong> binary order (101010), <strong>the</strong> last 2 bits are<br />

(11) so <strong>the</strong> SFD has a binary signature of (10101011). This breaks <strong>the</strong> sync<br />

and alerts <strong>the</strong> devices that frame data is following. The preamble and <strong>the</strong><br />

start of frame delimiter are dropped by <strong>the</strong> E<strong>the</strong>rnet controller, and when<br />

transmitting, it adds <strong>the</strong> correct frames for <strong>the</strong> E<strong>the</strong>rnet format in use. The<br />

preamble and SFD are not included in <strong>the</strong> calculation of <strong>the</strong> minimum and<br />

maximum frame size.<br />

• Destination address (6 bytes)—This tells <strong>the</strong> <strong>network</strong> where <strong>the</strong> data is being<br />

sent. There are slight differences between <strong>the</strong> E<strong>the</strong>rnet and IEEE 802.3<br />

frame. The destination field also indicates if data is destined for a single<br />

station (unicast), a group of stations (multicast), or all <strong>the</strong> stations on <strong>the</strong><br />

<strong>network</strong> (broadcast). The address itself can be ei<strong>the</strong>r locally or universally<br />

assigned.<br />

• Source address (6 bytes)—This address tells <strong>the</strong> <strong>network</strong> where <strong>the</strong> data<br />

was sent. Like <strong>the</strong> destination address, it can be locally or universally<br />

assigned. Locally administered addresses are 2 bytes long. The addresses<br />

are loaded on<strong>to</strong> flash memory on <strong>the</strong> E<strong>the</strong>rnet card. Locally administered<br />

addresses are generally found in mainframe environments. In most<br />

workstation environments, universal addresses are used. Universal<br />

addresses are "burned" in<strong>to</strong> <strong>the</strong> card. Because each E<strong>the</strong>rnet card must have<br />

its own unique address, organizational unique identifiers (OUI) are assigned<br />

<strong>to</strong> every NIC manufacturer. The NIC identifier is <strong>the</strong> first 3 bytes of <strong>the</strong><br />

address. The last 3 bytes of <strong>the</strong> address are uniquely assigned by <strong>the</strong><br />

manufacturer.<br />

• VLAN tag (4 bytes)—This is only used on 802.3 frames that are handled by<br />

802.1q VLAN-enabled <strong>network</strong> switches (multiport bridges). The tag is used<br />

<strong>to</strong> identify a packet with a specific VLAN. When <strong>the</strong> packet leaves <strong>the</strong> switch,<br />

<strong>the</strong> tag is removed.<br />

• Type (2 bytes)—The type field is only used with <strong>the</strong> E<strong>the</strong>rnet II frame type.<br />

It identifies <strong>the</strong> higher level pro<strong>to</strong>col contained in <strong>the</strong> data field.<br />

• Length (2 bytes)—This provides information on <strong>the</strong> size of <strong>the</strong> frame. The<br />

minimum size of an E<strong>the</strong>rnet frame is 64 bytes.<br />

• Data (46 <strong>to</strong> 1,500 bytes)—The PDU contains <strong>the</strong> upper layer pro<strong>to</strong>col<br />

information and <strong>the</strong> actual data. The minimum size is 46 bytes, which<br />

consists of a LLC PDU header of 4 bytes + 42 bytes of data or padding, and<br />

<strong>the</strong> maximum is 1,500 bytes. The PDU construction is <strong>the</strong> responsibility of<br />

<strong>the</strong> LLC interface. 802.2 (covered at <strong>the</strong> beginning of <strong>the</strong> chapter) is <strong>the</strong><br />

standard LLC interface used <strong>to</strong> construct <strong>the</strong> PDU.

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

Saved successfully!

Ooh no, something went wrong!