Buffl

Day 5 - 6 Ethernet LAN Switching

as
by abdullah S.

Common Exam Pitfalls


Pitfall 1: Confusing Source and Destination MAC Address Roles Many students incorrectly believe switches learn from the destination MAC address. This is wrong. Switches always learn by examining the SOURCE MAC address of received frames and associating it with the receiving interface. The destination MAC address is used for forwarding decisions, not learning. Remember: "Learn from SOURCE, forward to DESTINATION."

Pitfall 2: Misunderstanding Frame Flooding Students often think switches flood only unknown unicast frames. However, switches flood both unknown unicast frames AND broadcast frames. Known unicast frames are never flooded—they are forwarded only out the specific interface in the MAC address table. A helpful memory aid: "BUU floods" (Broadcast and Unknown Unicast flood).


Pitfall 3: Incorrect Frame Size Calculations The Preamble and SFD are sometimes counted and sometimes not, depending on context. For CCNA purposes, remember that the minimum frame size of 64 bytes does NOT include the Preamble and SFD. The 18-byte header/trailer count also excludes them. If you include Preamble and SFD, the total overhead is 26 bytes.


Pitfall 4: Type/Length Field Confusion The Type/Length field serves dual purposes based on its value. Values of 1500 or less indicate the payload length in bytes. Values of 1536 or greater indicate the protocol type (like IPv4 or IPv6). Students often forget this threshold and misinterpret the field's purpose.


Pitfall 5: ARP Message Direction Confusion ARP Requests are broadcast (sent to everyone), while ARP Replies are unicast (sent only to the requester). Students sometimes think both are broadcast. Similarly, ICMP Echo Requests (ping) are unicast, not broadcast. Only the ARP Request is broadcast because the requester doesn't yet know the destination's MAC address.


Pitfall 6: MAC Address Structure Students sometimes reverse the OUI and device-specific portions. Remember: the FIRST 24 bits (first half) are the OUI identifying the manufacturer. The LAST 24 bits (second half) identify the specific device.


Pitfall 7: Command Syntax Errors Cisco IOS commands have specific syntax. The command is "show mac address-table" (note: space before "address," hyphen before "table"). Older IOS versions used "show mac-address-table" with hyphens, but newer versions changed the first hyphen to a space. For clearing, it's "clear mac address-table dynamic" with various optional parameters.

Practical Examples


Example 1: Basic Switch Learning Process Consider PC1 (MAC: AA00.0001) connected to SW1 port F0/1, sending its first frame to PC2 (MAC: AA00.0002) on port F0/2. When SW1 receives the frame, it examines the source MAC address AA00.0001 and creates an entry: "AA00.0001 → F0/1" in its MAC table. Since PC2's MAC isn't in the table yet, this is an unknown unicast frame, so SW1 floods it out all ports except F0/1. When PC2 replies, SW1 learns "AA00.0002 → F0/2" and now has both entries, enabling efficient forwarding.

Example 2: ARP in Action PC1 (IP: 192.168.1.1) wants to ping PC3 (IP: 192.168.1.3). PC1 knows the destination IP but not the MAC address. It sends an ARP Request: "Who has 192.168.1.3? Tell 192.168.1.1" with destination MAC FFFF.FFFF.FFFF. All devices receive this broadcast. PC2 ignores it because the IP doesn't match. PC3 recognizes its IP and sends an ARP Reply: "192.168.1.3 is at 0C2F.B06A.3900" directly to PC1. Now PC1 can send the ping with the correct destination MAC address.


Example 3: Multi-Switch Environment PC1 connects to SW1, which connects to SW2, which connects to PC3. When PC1 sends a frame to PC3, SW1 learns PC1's MAC on its interface. SW1 floods the frame (unknown unicast) to SW2. SW2 also learns PC1's MAC, but associates it with the interface connecting to SW1, not directly to PC1. This is important: the MAC table entry shows how to REACH a device, not necessarily where it's directly connected. When PC3 replies, both switches learn PC3's MAC and can forward efficiently in both directions.


Example 4: Padding in Action You send a 36-byte ping. The minimum payload is 46 bytes, so the system automatically adds 10 bytes of padding (all zeros). In Wireshark, you would see these as hexadecimal zeros at the end of the frame. Each pair of hex digits represents one byte, so 20 hex digits = 10 bytes of padding. This ensures the frame meets the minimum 64-byte requirement.


Example 5: Why First Ping Fails When you ping 192.168.1.3 from PC1, Cisco IOS sends 5 pings. The output shows: .!!!! (one period, four exclamation marks). The first ping failed (.) because PC1 had to send an ARP Request and wait for the reply to learn the destination MAC address. During this ARP process, the first ICMP Echo Request timed out. After learning the MAC address, the remaining four pings succeeded (!).

Author

abdullah S.

Information

Last changed