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

Routing Information Protocol (RIP)

Let's get down and dirty with RIP. This protocol has three versions: RIPv1, RIPv2, and RIPng. Version 1 of this protocol is not used anymore, but you should know that RIPv1 is a class-full routing protocol, which means you need to use the same mask across your network and the same class of address. It also will not receive any updates from RIPv2 unless you specifically go into the interface and tell it to, but, again, it is not used any more. Oh, and the updates are sent as broadcast.

RIPv2 is a classless routing protocol that allows you to have different classes of addresses and different masks that would meet the needs of the network, allowing you not to waste IP addresses. This is possible due to the command no auto-summary. It does send periodic updates, but now it's using the multicast address 224.0.0.9, which is a lot easier...