Book Image

CCNA Routing and Switching 200-125 Certification Guide

By : Lazaro (Laz) Diaz
Book Image

CCNA Routing and Switching 200-125 Certification Guide

By: Lazaro (Laz) Diaz

Overview of this book

Cisco Certified Network Associate (CCNA) Routing and Switching is one of the most important qualifications for keeping your networking skills up to date. CCNA Routing and Switching 200-125 Certification Guide covers topics included in the latest CCNA exam, along with review and practice questions. This guide introduces you to the structure of IPv4 and IPv6 addresses and examines in detail the creation of IP networks and sub-networks and how to assign addresses in the network. You will then move on to understanding how to configure, verify, and troubleshoot layer 2 and layer 3 protocols. In addition to this, you will discover the functionality, configuration, and troubleshooting of DHCPv4. Combined with router and router simulation practice, this certification guide will help you cover everything you need to know in order to pass the CCNA Routing and Switching 200-125 exam. By the end of this book, you will explore security best practices, as well as get familiar with the protocols that a network administrator can use to monitor the network.
Table of Contents (24 chapters)
4
Subnetting in IPv4
21
Mock Test Questions
22
Assessments

The Network Time Protocol or NTP

In a network, it is extremely important that all devices that participate in it be in sync with one another.

By this I mean, their clocks should all be the same down to the second, heck, to a millisecond if you ask me; if they aren't, you could run into trouble. Just think about DC replication, DNS replication, intersite or intrasite replication, and the list does not stop there. And that's just Microsoft. The routers and switches that you are using must be in sync with one another as well, or updates will come in late or not at all. This in turn will hurt all your Microsoft devices as well.

Something else to think about is troubleshooting. You must have a timestamp when things go wrong, so you can have documentation as to when it all went bonkers, or if you are doing an update to your hardware or software, we should all be in sync so...