Week 5 · Lesson 8

Ethernet Frames

This is the canonical lesson on the Ethernet frame. Learn every field and its exact size in octets, the minimum and maximum frame lengths, and the values that appear in the EtherType field. These numbers are tested directly, so treat them as memorisation targets, not background reading.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Learning objectives
Part 1

The standard: IEEE 802.3

Ethernet is standardised as IEEE 802.3. Two frame formats live under that umbrella, and exam questions use both:

Everything that follows describes the Ethernet II frame, which is what you will meet in practice and on the exam.

In this lesson · select a part to jump

Part 2

The Ethernet II fields

Here are the fields in order, with their sizes in octets (bytes). Memorise this table cold.

FieldSize (octets)Purpose
Preamble7Bit-synchronisation pattern (alternating 1/0) so the receiver can lock onto the signal.
Start Frame Delimiter (SFD)1Ends the sync pattern and marks the start of the frame (value 10101011).
Destination MAC address6Layer 2 address of the receiving device (or a broadcast/multicast address).
Source MAC address6Layer 2 address of the sending device.
Type / Length2EtherType identifies the upper-layer protocol (Ethernet II); or the payload length (IEEE 802.3).
Payload (Data)46–1500The encapsulated data — the PDU from the Network layer (for example, an IPv4 packet).
Frame Check Sequence (FCS)4CRC-based error-detection value computed over the frame.
Connection to encapsulation The Ethernet header (Destination + Source + Type/Length) and the FCS trailer are exactly the “Ethernet header + FCS trailer” added in the encapsulation lesson (Week 1, Lesson 18 and Week 3, Lesson 5). The payload here is the IP packet handed down from Layer 3.
Reference table · select a row

Key ideas & exam traps · select one

Part 3

Preamble and Start Frame Delimiter

The first 8 octets are not really part of the message; they are there so the two ends of the link agree on where the frame begins at the bit level. The Preamble is 7 octets of the pattern 10101010, giving the receiver time to synchronise its clock. The Start Frame Delimiter (SFD) is 1 octet, 10101011; the final two bits differ from the preamble pattern and announce “the frame starts now”.

Exam tip — the 8 sync bytes The Preamble (7) + SFD (1) = 8 octets of synchronisation. They are not counted in the 64-byte minimum or the 1518-byte maximum, because those sizes are measured from the Destination Address through the FCS. A common trap is to add the preamble into the minimum and answer 72.
Part 4

Destination and Source addresses

Both the Destination and Source addresses are 6 octets (48 bits) — the MAC addresses you will study in lesson 09. The Destination comes first, because a receiving station wants to check whether the frame is for it as early as possible. A destination of FF:FF:FF:FF:FF:FF is the broadcast address and is received by every station on the local segment.

Part 5

Type vs Length: Ethernet II and 802.3

The 2-octet field after the source address is the crux of the Ethernet II vs IEEE 802.3 difference. It is interpreted by its numeric value:

AspectEthernet II (DIX)IEEE 802.3 (LLC/SNAP)
Field after SourceType (EtherType)Length
Protocol identificationDirectly by EtherTypeBy LLC (and SNAP) inside the payload
Typical use todayAll common LAN trafficLegacy; some control protocols

The canonical EtherType values you must know:

EtherTypeProtocol
0x0800IPv4
0x86DDIPv6
0x0806ARP (Address Resolution Protocol)
0x8100IEEE 802.1Q VLAN tag (indicates a tagged frame)
Exam tip — the three must-know values 0x0800 = IPv4, 0x86DD = IPv6, 0x0806 = ARP. If a question shows a frame carrying an IPv4 packet, the Type field reads 0x0800. If it carries an IPv6 packet, 0x86DD.
Part 6

Payload and FCS

The Payload (Data) field carries the encapsulated protocol data unit, from 46 to 1500 octets. If the actual data is shorter than 46 octets, the sender pads it with zeros so the frame still reaches the 64-octet minimum. The Frame Check Sequence (FCS) is the final 4 octets: a CRC computed by the sender and verified by the receiver. A frame whose FCS does not match is discarded silently — Ethernet does not retransmit at Layer 2 (see Lesson 5).

Part 7

Minimum, maximum, VLAN, and jumbo

Know these numbers and the reasoning behind them:

Part 8

The frame, field by field

The diagram shows the octet sizes of each field. Note how the 8 synchronisation octets sit outside the measured frame.

 Octets:    7        1         6          6           2        46..1500        4
         +--------+--------+----------+----------+-----------+-------------+-------+
  Field: |Preamble|  SFD   |  Dest    |  Source  | Type /    |   Payload   |  FCS  |
         |        |        |  MAC     |  MAC     | Length    |   (Data)    |       |
         +--------+--------+----------+----------+-----------+-------------+-------+
          \_______ 8 octet sync ______/
          (NOT part of the 64-byte minimum)

          |<----------- MIN 64 octets .. MAX 1518 octets (DA -> FCS) ----------->|

  EtherType values:  0x0800 = IPv4   0x86DD = IPv6   0x0806 = ARP   0x8100 = 802.1Q tag
  

Read it left to right: the receiver synchronises on the preamble and SFD, checks the destination MAC, learns the source MAC, reads the Type to know what is inside, consumes the payload, and finally verifies the FCS. The 802.1Q VLAN tag, when present, is a 4-octet addition between Source and Type/Length.

Part 9

Worked 64-byte breakdown

Why is the minimum frame exactly 64 octets? Add the smallest legal field sizes from the Destination address through the FCS:

  Destination MAC .......  6
  Source MAC ............  6
  Type / Length .........  2
  Minimum payload ....... 46
  FCS ...................  4
                         ----
  Minimum frame ......... 64  octets

  Inversely, the minimum payload is whatever is needed to reach 64:
     64 - (6 + 6 + 2 + 4) = 64 - 18 = 46 octets

  Maximum frame:
     6 + 6 + 2 + 1500 + 4 = 1518 octets
  With an 802.1Q VLAN tag (4 extra octets):
     1518 + 4 = 1522 octets

  On the wire, add the 8 sync octets:
     64 + 8 = 72 octets transmitted for a minimum-size frame
  

The MTU is the payload ceiling, 1500 octets (see Lesson 7); the whole frame adds 18 octets of header and trailer to that payload, giving the 1518 maximum.

Part 10

Runts and giants

FrameSizeMeaning and action
RuntShorter than 64 octets (DA–FCS)Usually a collision fragment or a truncation error. The receiving NIC discards it.
Normal64–1518 octets (1522 with VLAN)A valid Ethernet frame.
GiantLonger than the maximum for the linkFrames above 1518 (or above an agreed jumbo MTU) are invalid and dropped.
Memory hooks Runt = too small (the “runt of the litter”), below 64. A runt is almost always a collision fragment. Giant = too big, above the maximum. Remember 6-6-2-46-4 = 64 and 6-6-2-1500-4 = 1518; add 4 for a VLAN tag to get 1522.
Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 11 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.