Chapter 8: Router and switch interfaces
The chapter introduces its terminology for ports and interfaces before turning to interface configuration and operation.
After this chapter you will be able to
- Port and interface terminology. Distinguish the book’s usual use of port for a physical connector and interface for its software configuration, while explaining that the terms are often used interchangeably.
- Interface descriptions and purpose. Explain what an interface description is, how to configure one, and why keeping descriptions current is useful.
- Interface description display commands. Distinguish the commands for viewing interface descriptions on routers and switches, including where descriptions appear in switch status output.
- Interface speed and compatibility. Explain what interface speed measures and why an interface may operate below its maximum supported speed.
- Automatic and manual speed selection. Distinguish default autonegotiation from manual speed configuration, including when manual configuration may be appropriate and how the speed command expresses either choice.
- Half and full duplex. Distinguish half duplex from full duplex by whether an interface can send and receive at the same time, and give the section’s wireless and switched Ethernet examples.
- Hubs switches and collisions. Explain why hub-connected hosts share a collision domain and require half duplex, whereas switch-connected hosts have separate collision domains and can use full duplex.
- Duplex configuration and status. Describe how to set an interface’s duplex and interpret the section’s `show interfaces status` duplex values.
- Shared operational mode selection. Explain how two autonegotiating neighbors select their operational speed and duplex.
- One-sided autonegotiation behavior. Trace how an autonegotiation-enabled interface selects speed and duplex when its neighbor is manually configured, and describe the possible mismatches.
- Interface error counters. Explain that Cisco IOS increments interface counters when sending or receiving errors occur, and that show interfaces displays them. Distinguish input errors from output errors and explain what the CRC counter records.
- Collision counter interpretation. Distinguish ordinary collisions from late collisions and explain when their counts are expected or concerning.
- Speed mismatch symptoms. Explain what causes a speed mismatch and what happens to the connected interfaces when one occurs.
- Duplex mismatch symptoms and causes. Explain how a duplex mismatch arises and why an affected link can still appear operational despite reduced performance.
- False collisions and error counters. Trace how a duplex mismatch produces apparent collisions and corrupted frames, and describe the counters expected on each end.
What it builds on
- Global configuration mode (chapter 5) · Using IOS configuration commands.
- IOS configuration files (chapter 5) · Assumes the idea of viewing an IOS configuration file.
- Frame flooding and forwarding (chapter 6) · Switch forwarding and flooding provide the contrast with a hub repeating bits.
- Frame Check Sequence (chapter 6) · The Ethernet Frame Check Sequence
Section by section
Introduction
The chapter introduces its terminology for ports and interfaces before turning to interface configuration and operation.
- Port and interface terminology: Distinguish the book’s usual use of port for a physical connector and interface for its software configuration, while explaining that the terms are often used interchangeably.
Why it matters: This distinction helps you follow the book’s wording without treating the terms as rigidly separate.
Key terms: port, interface
8.1 Configuring interfaces
8.1.1 Interface descriptions
This section explains how to name interfaces with descriptions, configure several interfaces at once, and view descriptions in IOS.
- Interface descriptions and purpose: Explain what an interface description is, how to configure one, and why keeping descriptions current is useful.
Why it matters: Clear, current descriptions help you recognize an interface’s purpose when you revisit a configuration. - Interface range selection: Describe how interface range selects multiple interfaces for configuration, including how to include interfaces of different types.
Why it matters: Selecting interfaces together saves repeated configuration commands. - Interface description display commands: Distinguish the commands for viewing interface descriptions on routers and switches, including where descriptions appear in switch status output.
Why it matters: Choosing the right display command lets you find descriptions on either device type.
Key terms: interface description, description, interface range, type, slot, port, show interfaces description, show interfaces status, Status, Protocol
8.1.2 Interface speed
Explains interface speed, how Cisco IOS selects or configures it, and how to check a speed setting in the running configuration.
- Interface speed and compatibility: Explain what interface speed measures and why an interface may operate below its maximum supported speed.
Why it matters: This explains why a link might run below an interface’s highest supported speed. - Automatic and manual speed selection: Distinguish default autonegotiation from manual speed configuration, including when manual configuration may be appropriate and how the speed command expresses either choice.
Why it matters: The distinction helps you choose whether to leave the default in place or set an interface speed explicitly. - Speed configuration visibility: Describe how to view an interface’s active configuration and why an explicit speed auto command may not appear there.
Why it matters: An absent speed auto line does not by itself mean autonegotiation is off.
Key terms: interface speed, bits per second, 10/100 interfaces, 10/100/1000 interfaces, autonegotiation, speed {speed | auto}, speed auto, show running-config interface interface-name, default setting
8.1.3 Interface duplex
This section explains half- and full-duplex communication, why hubs and switches differ in their collision behavior, how CSMA/CD handles shared Ethernet, and how to configure and check interface duplex.
- Half and full duplex: Distinguish half duplex from full duplex by whether an interface can send and receive at the same time, and give the section’s wireless and switched Ethernet examples.
Why it matters: Duplex determines whether a device must take turns communicating or can send and receive simultaneously. - Hubs switches and collisions: Explain why hub-connected hosts share a collision domain and require half duplex, whereas switch-connected hosts have separate collision domains and can use full duplex.
Why it matters: The hub–switch contrast explains why collisions belong to shared Ethernet media rather than normal switched links. - Shared medium collision handling: Trace how CSMA/CD helps half-duplex devices on a shared medium avoid and respond to collisions.
Why it matters: CSMA/CD explains how devices manage access when they must share a collision domain. - Duplex configuration and status: Describe how to set an interface’s duplex and interpret the section’s `show interfaces status` duplex values.
Why it matters: The status display lets you distinguish a negotiated duplex setting from one configured manually.
Key terms: duplex, half duplex, full duplex, Ethernet hub, collision, collision domain, shared medium, point-to-point connections, CSMA/CD, carrier-sense
8.2 Autonegotiation
Explains how interfaces select speed and duplex through autonegotiation, what happens when only one end uses it, and when manual settings may be appropriate.
- Shared operational mode selection: Explain how two autonegotiating neighbors select their operational speed and duplex.
Why it matters: This lets you predict the settings a link will use when both ends autonegotiate. - One-sided autonegotiation behavior: Trace how an autonegotiation-enabled interface selects speed and duplex when its neighbor is manually configured, and describe the possible mismatches.
Why it matters: Knowing these fallback rules helps explain why a link can have mismatched settings when only one end autonegotiates. - Autonegotiation configuration tradeoffs: Justify why autonegotiation is generally left enabled for end devices and why some engineers manually configure infrastructure links.
Why it matters: The tradeoff helps you decide whether manual interface settings are worth the effort and error risk.
Key terms: autonegotiation, operational mode, speed, full duplex, half duplex, speed mismatch, duplex mismatch, manual configuration, end devices, network infrastructure devices
8.3 Interface errors
The section explains how to read selected Cisco IOS interface error counters and distinguish expected collisions from signs of network problems.
- Interface error counters: Explain that Cisco IOS increments interface counters when sending or receiving errors occur, and that show interfaces displays them. Distinguish input errors from output errors and explain what the CRC counter records.
Why it matters: These counters give you a starting point for identifying what is going wrong on an interface. - Runt and giant frames: Distinguish runts from giants by their size limits and describe the possible cause given for each.
Why it matters: The frame size tells you whether to consider collisions or an MTU mismatch. - Collision counter interpretation: Distinguish ordinary collisions from late collisions and explain when their counts are expected or concerning.
Why it matters: The timing and setting of a collision help distinguish normal hub behavior from a likely interface problem.
Key terms: show interfaces, input errors, output errors, CRC, FCS, runts, giants, MTU, padding, collisions
8.3.1 Speed mismatches
Explains how a speed mismatch between connected interfaces affects their status and communication.
- Speed mismatch symptoms: Explain what causes a speed mismatch and what happens to the connected interfaces when one occurs.
Why it matters: Recognizing down/down on both ends helps you identify a possible speed mismatch when troubleshooting a link.
Key terms: speed mismatch, down/down, show ip interface brief
8.3.2 Duplex mismatches
Explains why a duplex mismatch can leave a link operational but slow, and how interface error counters reveal it.
- Duplex mismatch symptoms and causes: Explain how a duplex mismatch arises and why an affected link can still appear operational despite reduced performance.
Why it matters: An up/up interface does not rule out a duplex problem. - False collisions and error counters: Trace how a duplex mismatch produces apparent collisions and corrupted frames, and describe the counters expected on each end.
Why it matters: The counters help identify a duplex mismatch even while the link continues forwarding traffic.
Key terms: duplex mismatch, up/up, autonegotiation, full duplex, half duplex, show interfaces, collisions, late collision counters, jamming signal, CSMA/CD
8.4 Summary
Concepts explained in this chapter
- autonegotiationAutonegotiation is a link establishment technique in which connected interfaces automatically agree on compatible communication parameters such as speed and duplex.
- duplexDuplex is an interface transmission setting that specifies whether an Ethernet interface operates in full-duplex or half-duplex mode.
- full duplexFull duplex is a communication mode in which an interface can transmit and receive simultaneously without collisions on the link.
- half duplexHalf duplex is a communication mode in which an interface cannot transmit and receive simultaneously and must wait for the medium to become available.
- csma/cdCSMA/CD is the Ethernet medium-access method in which devices detect carrier activity, transmit when the medium is available, and handle collisions.
- hubA hub is a network device that repeats incoming signals to multiple connected ports, causing attached devices to share a transmission medium.
- collision domainA collision domain is a network segment in which simultaneous transmissions can interfere and cause collisions.
- duplex mismatchA duplex mismatch is a link condition in which two connected interfaces use different duplex settings or incompatible autonegotiation behavior.
- speed mismatchA speed mismatch is a condition in which two connected network interfaces are configured to communicate at different transmission speeds.
- interface descriptiondescription is a Cisco IOS interface-configuration command that assigns descriptive text to an interface.
- interface rangeinterface range is a Cisco IOS interface-configuration command that selects multiple interfaces for simultaneous configuration.
- shutdownshutdown is a Cisco IOS interface configuration command that administratively disables an interface.
- network interfaceA network interface is a connection point through which a device communicates with other devices in a network.
- physical layerThe Physical Layer is a networking model layer that defines the transmission of raw signals and bits over a physical medium.
- port numberA port number is a transport-layer identifier ranging from 0 to 65535 that directs network data to a particular application process on a host.
- network switchA Layer 2 switch is a switch that forwards frames within a local network without performing network-layer routing.
- no shutdown commandThe Cisco IOS no shutdown command removes the shutdown state from an interface and enables it.
- show interfaces statusshow interfaces status is a Cisco IOS switch command that displays interface status, descriptions, speed, and duplex information.
- jamming signalA jamming signal is a deliberately transmitted signal that announces a detected Ethernet collision and disrupts ongoing transmissions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.