Switching Concepts, Cabling & Interface Issues

CCNA 200-301 · Network Fundamentals

By Abu Anns · Last updated 20 November 2026Exam version: 200-301 v1.1 (current until 2 Feb 2027)

Switching is the foundation skill of the CCNA: if you cannot explain what a switch does with a frame, VLANs, spanning tree, and EtherChannel will all feel mysterious, because each of them is switching with extra rules. The good news is that the core behaviour is simple, and the exam tests it the same way every time — by asking what a switch does when the destination is known, unknown, or a broadcast, and by asking you to diagnose the small physical problems that break links.

How a switch learns and forwards

A switch forwards Ethernet frames using a MAC address table (also called the CAM table). When a frame arrives, the switch reads its source MAC address and records which port that address lives on — this is MAC learning. Entries do not last forever: each one has an aging timer (300 seconds by default on Cisco switches), and if no frame arrives from that address before the timer expires, the entry is removed. This MAC aging is what lets the table stay correct when devices move or are replaced.

With the source learned, the switch looks up the destination MAC address. If the destination is in the table, the switch forwards the frame out of that one port only — this is frame switching (unicast forwarding), and it is what makes a switch better than a hub: each conversation gets its own dedicated path instead of everyone hearing everything. If the destination is not in the table, the switch floods the frame out of all ports except the one it arrived on. Flooding is normal and necessary — it is how the switch finds a device it has not learned yet. The reply from that device teaches the switch its location, so the next frame goes directly. Broadcast frames (destination MAC ff:ff:ff:ff:ff:ff) and unknown multicast frames are also flooded, by design.

Two consequences matter for the exam. First, a switch forwards broadcasts, so all devices in a VLAN share one broadcast domain — only a router breaks that up. Second, a switch starts with an empty MAC table when it boots, so its first frames are flooded; a question that asks what a switch does with a frame to an unknown destination always has the same answer: flood it. You can inspect the table with show mac address-table and clear it with clear mac address-table dynamic.

Cabling and physical interfaces

Copper cabling (twisted pair, such as Cat5e/Cat6/Cat6a) is the standard for short runs: up to 100 metres for Ethernet, inexpensive, and able to carry PoE. Multimode fiber uses a wider core that carries light over shorter distances — typically up to a few hundred metres — and is common inside buildings and campuses. Single-mode fiber uses a narrow core with a single path of light, which travels much further (kilometres to tens of kilometres) and is used for long-distance and service-provider links. The exam's comparison is straightforward: copper is cheap and short, multimode is medium distance, single-mode is long distance. Fiber also has a practical advantage the exam likes: it is immune to electromagnetic interference, so it is the right choice near heavy electrical equipment.

Connections can be point-to-point — two devices directly linked, the normal case for a switch-to-switch or switch-to-router link — or shared media, where several devices share one collision domain, as with a hub or old coaxial Ethernet. Modern switched networks are point-to-point everywhere, which is why collisions are largely a historical topic — but the exam still tests them, because recognising a collision problem is part of diagnosing interface issues.

Interface and cable issues

When a link misbehaves, show interfaces is your first command, and the exam expects you to read its output. Collisions happen when two devices transmit at the same time on shared media; in a modern full-duplex switched network you should see essentially none, so a rising collision count points to a hub in the path or a duplex problem. A duplex mismatch — one side set to full duplex and the other to half duplex — is a classic exam scenario: the half-duplex side sees collisions and late collisions, the link appears to work but performs terribly, and the fix is to match the settings (usually by leaving both sides on autonegotiation). A speed mismatch is simpler and harsher: the link usually does not come up at all, or comes up and immediately drops, because the two sides cannot agree on a signalling rate.

Errors in the interface counters tell their own stories. CRC errors and input errors often point to a damaged cable, a bad connector, or electrical interference. Runts (frames smaller than 64 bytes) and giants (frames larger than the maximum) suggest a faulty network interface card or a duplex problem. A steadily increasing error count on one interface, while the neighbour's counters stay clean, usually means the problem is the cable or the local port — swap the cable first, because it is the cheapest fix and the most common fault.

One more distinction the exam tests: the difference between a port being administratively down (shut down with the shutdown command — show interfaces reports "administratively down") and a port that is up at Layer 1 but down at Layer 2. If the status is up but the line protocol is down, the physical link works but something above it — encapsulation, keepalives, or a duplex problem — is failing. Reading that first line of show interfaces output is a small skill that answers a surprising number of exam questions.

Putting it together: reading show interfaces output

When a question shows you show interfaces output, read it in a fixed order. First, the status line: up/up means the link is healthy at Layers 1 and 2; administratively down means someone shut the port down; up with the line protocol down means a Layer 2 problem. Second, the speed and duplex lines: confirm they match the neighbour, because a mismatch is the single most common cause of a link that is up but slow. Third, the error counters: CRC errors and input errors point at the cable or the physical layer, while collisions and late collisions point at a duplex problem. Fourth, the five-minute input and output rates, which tell you whether the link is actually carrying traffic or merely up. Practise this reading order in Packet Tracer until it is automatic: build a link, break it deliberately (set a duplex mismatch, shut a port down, unplug a cable), and read the output each time. The exam rewards candidates who can move from symptom to cause in one step, and that skill comes from seeing the counters change, not from memorising their definitions.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A switch receives a unicast frame whose destination MAC address is not in its MAC address table. What does the switch do with the frame?

Report an error

Q2.A switch learns a MAC address from the source address of an incoming frame. After how long is that entry removed if no further frames arrive from that address?

Report an error

Q3.An engineer needs to connect two buildings 8 kilometres apart with a single link. Which media type is the correct choice?

Report an error

Q4.A link between a switch and a server is up but extremely slow. show interfaces shows a large and growing number of late collisions on the switch port. What is the most likely cause?

Report an error

Q5.Which command displays the contents of a switch's MAC address table?

Report an error

Q6.A broadcast frame arrives at a switch. How does the switch handle it?

Report an error

Q7.An interface shows 'up, line protocol is down' in show interfaces output. What does this indicate?

Report an error

Q8.Why is fiber-optic cabling preferred over copper in an industrial area with heavy electrical machinery?

Report an error

Q9.Two switches are connected by a single Ethernet cable, with no other devices on the link. What type of connection is this?

Report an error