CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte100
CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte100
CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte100
1.1.a Routers
This chapter begins a series of chapters that focus on specific Cisco router
features. It begins by discussing Cisco routers: hardware, operating system,
interfaces, and other components that comprise a router. This first section
helps give you concrete examples of interfaces and devices before getting
into the many concept and topology drawings to come.
Take the quiz (either here or use the PTP software) if you want to use the
score to help you decide how much time to spend on this chapter. The letter
answers are listed at the bottom of the page following the quiz. Appendix C,
found both at the end of the book as well as on the companion website,
includes both the answers and explanations. You can also find both answers
and explanations in the PTP testing software.
Table 16-1 “Do I Know This Already?” Foundation Topics Section-to-Question Mapping
1. Which operating systems run on Cisco enterprise routers and use a CLI
that works much like the CLI on Cisco LAN switches? (Choose two answers.)
1. CatOS
2. IOS
3. Windows
4. IOS XE
2. Which action would you expect to be true of a router CLI interaction that
is not true when configuring a LAN switch that performs only Layer 2
switching functions?
1. Moving from global to physical interface configuration mode
2. Configuring an IP address in physical interface configuration mode
3. Configuring a 10/100/1000 port’s settings related to speed and
autonegotiation
4. Configuring a console password
1. show running-config
2. show protocols type number
3. show ip interface brief
4. show interfaces
6. Which of the following is different on the Cisco switch CLI for a Layer 2
switch as compared with the Cisco router CLI?
1 B, D
2B
3 A, C
4B
5C
6B
Foundation Topics
This section examines some of the details of router installation and cabling,
first from the enterprise perspective and then from the perspective of
connecting a typical small office/home office (SOHO) to an ISP using high-
speed Internet.
Ethernet LAN: Simple straight lines with one or more LAN switches implied
but not shown.
Ethernet WAN: Shown as a straight line, often with a cloud over it, with
some kind of Ethernet interface identifier shown by the router (in this case,
G0/1/0 and G0/0/0, which refers to GigabitEthernet interfaces).
Serial WAN: A line with a crooked part in the middle (a “lightning bolt”)
represents a typical point-to-point serial link as introduced in Chapter 3.
In comparison, Figure 16-2 shows the same network, with more detail about
the physical cabling but with IP details removed. Focusing on the LANs, all
the lines connected to the LAN switches could be the standard UTP cabling
with RJ-45 connectors.
Next, consider the hardware on the ends of the serial link between the two
routers. In a real serial link that runs through a service provider, the link
terminates at a channel service unit/data service unit (CSU/DSU). The
CSU/DSU can either sit outside the router as a separate device (as shown on
the left at Router R1) or integrated into the router’s serial interface hardware
(as shown on the right).
As for cabling, the service provider will run the cable into the enterprise’s
wiring closet and often put an RJ-48 connector (same size as an RJ-45
connector) on the end of the cable. That cable should connect to the
CSU/DSU. With an internal CSU/DSU (as with Router R2 in Figure 16-2), the
router serial port has an RJ-48 port to which the serial cable should connect.
With an external CSU/DSU, the CSU/DSU must be connected to the router’s
serial card via a short serial cable.
All routers have the usual components found in a computer: a CPU, RAM,
permanent memory (usually flash memory), and other electronics. They also
run an operating system (OS), which goes by the name IOS. The original
Cisco routers used IOS; even today, some current router products use IOS.
However, Cisco has created other enterprise-class router product families
that use a different variation of IOS named IOS XE.
Cisco created IOS XE in the 2000s to improve the IOS software architecture.
Those improvements may not be evident to the casual observer, but to name
a few, IOS XE reduces unplanned and planned downtime, better protects
against cyberattacks, and aids network automation. For instance, IOS XE
devices can support upgrading the OS while continuing to forward frames
and packets, while IOS cannot.
Thankfully, IOS XE uses the same familiar CLI as IOS. Both use the same
commands, for the most part, the same command syntax, navigation and
modes, and so on. If you learned the CLI using an IOS router, you might not
even notice when using a router that runs IOS XE later.
Because the differences between IOS and IOS XE do not matter in most
cases in this book, the book uses the term IOS almost exclusively to refer to
the router OS. When differences in IOS versus IOS XE matter, the text will
note the differences.
Figure 16-3 shows a Cisco 4321 ISR, with some of the more important
features highlighted. The top part of the figure shows a full view of the back
of the router. This model comes with two built-in Gigabit Ethernet interfaces
and two modular slots that allow you to add small cards called Network
Interface Modules (NIMs). The bottom of the figure shows one sample NIM
(a NIM that provides two serial interfaces). The router has other items as
well, including both an RJ-45 and USB console port.