CCENT Study Guide
Chapter 7
Managing a Cisco Internetwork
Chapter 7 Objectives
• The CCENT Topics Covered in this chapter include:
• 2.0 LAN Switching Technologies
• 2.6 Configure and verify Layer 2 protocols.
• 2.6.a Cisco Discovery Protocol
• 2.6.b LLDP
• 4.0 Infrastructure Services
• 4.1 Describe DNS lookup operation.
• 4.2 Troubleshoot client connectivity issues involving DNS.
• 4.3 Configure and verify DHCP on a router (excluding static
• reservations).
• 4.3.a Server
• 4.3.b Relay
• 4.3.c Client
• 4.3.d TFTP, DNS, and gateway options
• 4.4 Troubleshoot client- and router-based DHCP connectivity
• issues.
• 4.5 Configure and verify NTP operating in client/server mode.
• 5.0 Infrastructure Management
• 5.1 Configure and verify device-monitoring using syslog
• 5.2 Configure and verify device management.
• 5.2.a Backup and restore device configuration.
• 5.2.b Using Cisco Discovery Protocol and LLDP for device
• Discovery
• 5.2.d Logging
• 5.2.e Timezone
• 5.2.f Loopback 2
Table 7.1: Cisco router
components
Bootstrap Stored in the microcode of the ROM, the ROM (read-only memory) Used to start and maintain the router.
bootstrap is used to bring a router up Holds the POST and the bootstrap
during initialization. It boots the router program as well as the mini-IOS.
up and then loads the IOS.
POST (power-on self-test) Also stored in the microcode of the Flash memory Stores the Cisco IOS by default. Flash
ROM, the POST is used to check the basic memory is not erased when the router
functionality of the router hardware and is reloaded. It is EEPROM (electronically
determines which interfaces are present. erasable programmable read-only
ROM monitor Again, stored in the microcode of the memory) created by Intel.
ROM, the ROM monitor is used for
manufacturing, testing, and
troubleshooting. NVRAM (nonvolatile RAM) Used to hold the router and switch
Mini-IOS Called the RXBOOT or bootloader by configuration. NVRAM is not erased
Cisco, the mini-IOS is a small IOS in ROM when the router or switch is reloaded.
that can be used to bring up an interface Does not store an IOS. The configuration
and load a Cisco IOS into flash memory. register is stored in NVRAM.
The mini-IOS can also perform a few
other maintenance operations.
RAM (random access memory) Used to hold packet buffers, ARP cache, Configuration register Used to control how the router boots
routing tables, and also the software and up. This value can be found as the last
data structures that allow the router to line of the show version command
function. Running-config is stored in output and by default is set to 0x2102,
RAM, and most routers expand the IOS which tells the router to load the IOS
from flash into RAM upon boot. from flash memory as well as to load
the configuration from NVRAM.
Verifying the Current
Configuration
To verify the configuration in DRAM, use the show running-config
command (sh run for short) like this:
Router#show running-config
Building configuration...
Current configuration : 855 bytes
!
version 15.0
The current configuration information indicates that the router is
running version 15.0 of the IOS.
Copying the Current
Configuration to NVRAM
By copying running-config to NVRAM as a backup, as shown in the
following output, you ensure that your running-config will always
be reloaded if the router gets rebooted. Starting in the 12.0 IOS,
you’ll be prompted for the filename you want to use:
Router#copy running-config startup-config
Destination filename [startup-config]?[enter]
Building configuration...
[OK]
Copying the Configuration to
a TFTP Server
Once the file is copied to NVRAM, you can make a second backup to
a TFTP server by using the copy running-config tftp command, or
copy run tftp for short. I’m going to set the hostname to Todd before
I run this command:
Todd#copy running-config tftp
Address or name of remote host []? [Link]
Destination filename [todd-confg]?
!!
776 bytes copied in 0.800 secs (970 bytes/sec)
If you have a hostname already configured, the command will
automatically use the hostname plus the extension -confg as the
name of the file.
Restoring the Cisco
Configuration
If you did copy the configuration to a TFTP server as a second backup, you
can restore the configuration using the copy tftp running-config command
(copy tftp run for short), or the copy tftp startup-config command (copy tftp
start for short), as shown in the output below. Just so you know, the old
command we used to use for this is config net:
Todd#copy tftp running-config
Address or name of remote host []?[Link]
Source filename []?todd-confg
Destination filename[running-config]?[enter]
Accessing t[Link]
Loading todd-confg from [Link] (via FastEthernet0/0):
!!
[OK - 776 bytes]
776 bytes copied in 9.212 secs (84 bytes/sec)
Todd#
*Mar 7 [Link].071: %SYS-5-CONFIG_I: Configured from
t[Link] by console
Okay, here we can see that the configuration file is an ASCII text file, meaning
that before you copy the configuration stored on a TFTP server back to a
router, you can make changes to the file with any text editor.
Erasing the Configuration
To delete the startup-config file on a Cisco router or switch, use the command
erase startup-config, like this:
Todd#erase startup-config
Erasing the nvram filesystem will remove all configuration files!
Continue? [confirm][enter]
[OK]
Erase of nvram: complete
*Mar 7 [Link].407: %SYS-7-NV_BLOCK_INIT: Initialized the
geometry of nvram
Todd#reload
System configuration has been modified. Save? [yes/no]:n
Proceed with reload? [confirm][enter]
*Mar 7 [Link].059: %SYS-5-RELOAD: Reload requested by console.
Reload Reason: Reload Command.
This command deletes the contents of NVRAM on the switch and router. If you
type reload while in privileged mode and say no to saving changes, the switch
or router will reload and come up into setup mode.
Configuring DHCP
Here are your configuration steps:
1. Exclude the addresses you want to reserve. The reason you do this
step first is because as soon as you set a network ID, the DHCP
service will start responding to client requests.
2. Create your pool for each LAN using a unique name.
3. Choose the network ID and subnet mask for the DHCP pool that
the server will use to provide addresses to hosts.
4. Add the address used for the default gateway of the subnet.
5. Provide the DNS server address(es).
6. If you don’t want to use the default lease time of 24 hours, you
need to set the lease time in days, hours, and minutes.
Figure 7.1: DHCP Configuration
example on a switch
Here’s how we’ll configure DHCP using the
[Link]/24 network ID:
Switch(config)#ip dhcp excluded-address
[Link] [Link]
Switch(config)#ip dhcp pool Sales_Wireless
Switch(dhcp-config)#network [Link]
[Link]
Switch(dhcp-config)#default-router [Link]
Switch(dhcp-config)#dns-server [Link]
Switch(dhcp-config)#lease 3 12 15
First, you can see that I reserved 10 addresses in the
range for the router, servers, and printers, etc. I then
created the pool named Sales Wireless, added the default
gateway and DNS server, and set the lease to 3 days, 12
hours, and 15 minutes (which isn’t really significant
because I just set it that way for demonstration
purposes).
DHCP Relay
But what happens if we need to provide an IP address from a DHCP server to a host that’s
not in our broadcast domain, or if we want to receive a DHCP address for a client from a
remote server?
So we know that because the hosts off the router don’t have access
to a DHCP server, the router will simply drop their client request
broadcast messages by default. To solve this problem, we can
configure the F0/0 interface of the router to accept the DHCP client
requests and forward them to the DHCP server like this:
Router#config t
Router(config)#interface fa0/0
Router(config-if)#ip helper-address [Link]
Figure 7.3: Sending console
messages to a syslog server
A syslog server saves copies of console messages and can time-
stamp them so you can view them at a later time. This is actually
rather easy to do. Here would be your configuration on the SF
router:
SF(config)#logging host [Link]
SF(config)#service timestamps log datetime msec
Network Time Protocol (NTP)
To make sure all devices are synchronized with the same time
information, we’ll configure our devices to receive the accurate time
information from a centralized server
SF(config)#ntp server [Link] version 4
Documenting a network
topology using CDP
IP Address IP Address
Router Router
Int S0/0 Int
Fa0/0 .1
.1
Fa0/1 .1
.1 S0/1
Int Int
Router Router
IP Address IP Address
Network topology
documented
2501 2514
S0/0
Fa0/0 .1
.1
Fa0/1 Lab_A .1
.1 S0/1
2621 2620
[Link]/24 [Link]/24
Written Labs and Review
Questions
– Read through the Exam Essentials section
together in class.
– Open your books and go through all the
written labs and the review questions.
– Review the answers in class.
16