Router Components

Internal Configuration
Components
• RAM/DRAM: RAM content is lost when
you power down or restart.
• Stores:
• routing tables
• ARP cache
• fast-switching cache
• packet buffering
• packet hold queues
• temporary and/or running memory for the router’s
configuration file (running-config)
 RAM for Working Storage
• RAM is the working storage area for the
router.

• When the router is turned on, a bootstrap

program is executed from ROM. This
program performs some tests, then loads the
Cisco IOS software into memory.
Stores:
• routing tables
• ARP cache
• fast-switching cache
• packet buffering
• packet hold queues
• temporary and/or running memory for the
router’s configuration file (running-config)
NVRAM - Nonvolatile RAM
• Stores:
• backup configuration file (startup-config)

• NVRAM content is retained when you

power down or restart.
Flash - Erasable, reprogrammable ROM
• Stores:
• operating system image and microcode
• Having Flash memory allows you to update
software without removing and replacing
chips on the processor.
• Flash content is retained when you power
down or restart.
• Flash memory can store multiple versions
of IOS software
ROM
• Contains:
• power-on diagnostics
• a bootstrap program
• operating system software.

• To perform software upgrades, remove and

replace pluggable chips on the CPU.
Interfaces
• Network connections through which
packets enter and exit the router.

Interfaces are:
• on the motherboard
• on separate interface modules.
Router Setup and Startup
Overview of System Startup
• When a Cisco router powers up, it performs
a power-up self-test.
• During this self-test, the router executes
diagnostics from ROM on all hardware
modules.
• These diagnostics verify the basic operation
of the CPU, memory, and network
interface ports.
After the power-up self test on the router, the
following events occur as the router
initializes:
Step 1 - The generic bootstrap loader, in
ROM, executes on the CPU card.
• A bootstrap is a simple, preset operation to
load instructions that in turn cause other
instructions to be loaded into memory, or
cause entry into other configuration modes.
Step 2 - The operating system (Cisco IOS)
can be found in one of several places.
• The location is disclosed in the boot field of
the configuration register. (later)
• If the boot field indicates a Flash, or
network load, boot system commands in
the configuration file indicate the exact
location of the image.

• Default is Flash.
Step 3 - The operating system image is
loaded.
• Then, when it is loaded and operational, the
operating system locates the hardware and
software components and lists the results on
the console terminal.

• Loaded into RAM.

Step 4 - The configuration file saved in
NVRAM is loaded into main memory and
executed one line at a time.
• These configuration commands start routing
processes, supply addresses for interfaces,
set media characteristics, and so on.

• startup-config becomes running-config

Step 5 - If no valid configuration file exists
in NVRAM, the operating system executes
a question-driven initial configuration
routine referred to as the system
configuration dialog, also called the setup
dialog.
• Setup is not intended as the mode for entering
complex protocol features in the router.
• You should use setup to bring up a minimal
configuration, then use various configuration-
mode commands, rather than setup, for most
router configuration tasks.
Router Configuration
 clock rate vs. clockrate
• clock rate, not clockrate
• however, both will work
• config files show clockrate
 Router Status Commands
show version - Displays the configuration of
the system hardware, the software version,
the names and sources of configuration
files, and the boot images.
(Extra)
• IOS version, System Image, Firmware
• Uptime, Restarted time/date
• CPU, Flash, RAM (2500: Processor / I/O -
Packet Buffering)
• Interfaces, Configuration Register
 Cisco Discovery Protocol
Overview
• Cisco Discovery Protocol (CDP) provides a
single proprietary command that enables
network administrators to access a summary
of what the configurations look like on
other directly connected routers.
• CDP runs over a data link layer connecting
lower physical media and upper-network-
layer protocols.
• CDP starts up automatically.
• CDP can then automatically discover
neighboring Cisco devices running CDP.
• Discovered devices extend beyond those
having TCP/IP. CDP discovers directly
connected Cisco devices regardless of
which Layer 3 and 4 protocol suite they run.
CDP Configuration Example
Mkting# show cdp interface
• Although CDP runs by default, you must
explicitly enable it on the device’s interface
using the command cdp enable. For
example, the graphic shows the cdp enable
• Default values for timers set the frequency
between:
• CDP updates: timer default 60 seconds
• for aging CDP: hold-down timer default
180 seconds

• If the device receives a more recent update

or if this holdtime value expires, the device
must discard the CDP entry.
Correction: show cdp entry routerB
 Showing CDP Entries for a
Device
• Notice that output from this command
includes all the Layer 3 addresses present
in the neighbor router B—an administrator
can see the IP addresses of the targeted
CDP neighbor (Router B) with the single
command entry on router A.
• Mkting# show cdp entry gateway
 Showing CDP Neighbor
Entries
Mkting# Show cdp neighbor
• Values include the following:
• Device identifiers - For example, the router’s
configured host name and domain name (if any).
• Address list - At least one protocol for SNMP, up to
one address for each protocol supported.
• Port identifier - Such as Ethernet 0, Ethernet 1,
Serial 0, etc.
• Capabilities list - If, for example, the device acts as
a source route bridge as well as a router.
• Version - Information such as that provided by the
local command show version.
• Platform - The device’s hardware platform: for
example, Cisco 7000.
 Showing CDP Neighbors
• Use the command show cdp neighbors to
display the CDP updates received on the
local router. Notice that for each local port,
the display shows the following:
Displays
• Neighbor device ID: hostname
• Local Interface: Local port type and number.
Interface of your router on which you are connected to
this neighbor.
• Holdtime: Decremental holdtime value in seconds
• Capability: Neighbor’s device capability code
• Platform: Hardware platform of the neighbor
• Port ID: Neighbor’s remote port type and number.
Interface of the remote router on which it is connected
to your router. Remote router’s interface.