This chapter covers the following exam topics:

1.0 Network Fundamentals

1.6 Configure and verify IPv4 addressing and subnetting
3.0 IP Connectivity
3.3 Configure and verify IPv4 and IPv6 static routing
3.3.a Default route
3.3.b Network route
3.3.c Host route
3.3.d Floating static
The first three chapters in this part of the book took you from a starting point of understanding
IP addressing and subnetting to the details of implementing IP addressing, routing
between connected subnets, and configuring static routes. All those steps include the idea
of configuring a command and seeing a route show up in the IP routing table on that same
router.
This chapter turns our attention to routing from end-to-end across an entire enterprise network.
How do you troubleshoot an IPv4 network? How do you verify correct operation,
identify root causes, and fix those for various IP routing features? How do you do that in
the presence of an IP addressing and subnetting plan, requiring you to apply all that subnetting
math from Part IV of this book and the basic address/mask and static route configuration
from the other chapters here in Part V? This chapter answers some of those questions.
In particular, this chapter focuses on two tools and how to use them: ping and traceroute.
Both tools test the IPv4 data plane; that is, the ability of each networking device to route or
forward IPv4 packets. This chapter devotes a major section each to ping and traceroute. The
chapter then ends with a short discussion of two other router tools that can also be useful
for troubleshooting: Telnet and Secure Shell (SSH).
“Do I Know This Already?” Quiz
I put DIKTA quizzes in most of the chapters as a tool to help you decide how to approach
reading a chapter. However, this chapter does not have a DIKTA quiz because I think you
should read it regardless of your prior knowledge. As with all chapters in this book, this
chapter introduces new concepts, but it also acts as a tool to review and deepen your understanding
of IP routing. I hope you enjoy the perspectives on using ping and traceroute in this