Cisco Router Configuration Commands
Cisco Router Configuration Commands
Cisco Router Configuration Commands
Set the clock rate for a router with a DCE cable to 64K Router(config-if)clock rate 64000
Static route the remote network is 172.16.1.0, with a mask of 255.255.255.0, Router(config)#ip route 172.16.1.0
the next hop is 172.16.2.1, at a cost of 5 hops 255.255.255.0 172.16.2.1 5
Shows all logs that the router has in its memory show log
View type of serial cable on s0 show controllers 0 (note the space between the 's' and the
'0')
Display access lists, this includes the number of displayed show access-lists
matches
Check the router can see the ISDN switch show isdn status
Upgrade the router IOS from a TFTP server copy tftp flash
1. Connect PC Ethernet port and Cisco router Ethernet port by using:
Cross-over UTP cable (cable with pin 1 connected to pin 6 and pin 2 connected to pin 6,
both on RJ45 connector) or by using:
HUB and two straight UTP cables.
2. Power on the router and look at the massages appearing on the screen, while the router is booting
Part 1
BASIC COMMANDS
show version
show ip interface brief (or show interface)
1. Router name:
2. Router type:
3. IOS version:
4. Memory amount:
5. Flash ROM amount:
6. Number and types of interfaces:
Part 2
Part 3
Set up a new IP address, mask and Default Gateway on each WG PC
Each WG should decide which IP addresses will be used (from each subnet) for PC to router
connection and for router to router connection .
Start -> Settings -> Control panel -> Network -> TCP/IP Ethernet… -> Properties -> IP address and
Gateway
Part 4
Displaying the configurations
Exit the privilege mode (CTRL-Z), you are back in Privileged mode!
Specify virtual terminal lines you would like to configure (line vty 0 4)
Exit the privilege mode (CTRL-Z), you are back in Privileged mode!
Select the ip address and subnet mask (ip address your_IP_address mask )
Exit the privilege mode (CTRL-Z), you are back in Privileged mode!
Part 5
Establishing router to router connectivity:
Configuring the Serial interface:
Select the ip address and subnet mask (ip address your_IP_address mask )
Find out which Serial interface got connected DCE and which DTE CISCO cable
On Serial Interface with DCE cable enable line CLOCK by entering the command:
Exit the privilege mode (CTRL-Z), you are back in Privileged mode!
Provide routers with info where other (not directly connected) subnets are by configuring static routes on each
router:
· <subnet> is the subnet used for router-to-PC connection on the neighbor router
Part 6 (optional)
Connect your network to other WG network (by Ethernet or Serial connection):
· Check connectivity (ping) from your PC to all other PC’s (in others WG)
· Check reachibility (traceroute) from your PC to all other PS’s (in others WG)
There are several methods available for configuring Cisco routers. It can be done over the network from a TFTP
server. It can be done through the menu interface provided at bootup, and it can be done from the menu interface
provided by using the command setup. This tutorial does not cover these methods. It covers configuration from
the IOS command-line interface only. Useful for anyone new to Cisco routers, and those studying for CCNA.
Note that this tutorial does not cover physically connecting the router to the networks it will be routing for. It
covers operating system configuration only.
The main reason for using the command-line interface instead of a menu driven interface is speed. Once you have
invested the time to learn the command-line commands, you can perform many operations much more quickly
than by using a menu. This is basically true of all command-line vs. menu interfaces. What makes it especially
efficient to learn the command-line interface of the Cisco IOS is that it is standard across all Cisco routers. Also,
some questions on the CCNA exam require you to know command-line commands.
Initially you will probably configure your router from a terminal. If the router is already configured and at least
one port is configured with an IP address, and it has a physical connection to the network, you might be able to
telnet to the router and configure it across the network. If it is not already configured, then you will have to
directly connect to it with a terminal and a serial cable. With any Windows box you can use Hyperterminal to
easily connect to the router. Plug a serial cable into a serial (COM) port on the PC and the other end into the
console port on the Cisco router. Start Hyperterminal, tell it which COM port to use and click OK. Set the speed of
the connection to 9600 baud and click OK. If the router is not on, turn it on.
If you wish to configure the router from a Linux box, either Seyon or Minicom should work. At least one of
them, and maybe both, will come with your Linux distribution.
Often you will need to hit the Enter key to see the prompt from the router. If it is unconfigured it will look like
this:
Router>
If it has been previously configured with a hostname, it will look like this:
hostname of router>
If you have just turned on the router, after it boots it will ask you if you wish to begin initial configuration. Say
no. If you say yes, it will put you in the menu interface. Say no.
2.1 Modes
The Cisco IOS command-line interface is organized around the idea of modes. You move in and out of several
different modes while configuring a router, and which mode you are in determines what commands you can use.
Each mode has a set of commands available in that mode, and some of these commands are only available in that
mode. In any mode, typing a question mark will display a list of the commands available in that mode.
Router>?
When you first connect to the router and provide the password (if necessary), you enter EXEC mode, the first
mode in which you can issue commands from the command-line. From here you can use such unprivileged
commands as ping, telnet, and rlogin. You can also use some of the show commands to obtain information
about the system. In unprivileged mode you use commands like, show version to display the version of the IOS
the router is running. Typing show ? will diplay all the show commands available in the mode you are presently
in.
Router>show ?
You must enter privileged mode to configure the router. You do this by using the command enable. Privileged
mode will usually be password protected unless the router is unconfigured. You have the option of not password
protecting privileged mode, but it is HIGHLY recommended that you do. When you issue the command enable
and provide the password, you will enter privileged mode.
To help the user keep track of what mode they are in, the command-line prompt changes each time you enter a
different mode. When you switch from unprivileged mode to privileged mode, the prompt changes from:
Router>
to
Router#
This would probably not be a big deal if there were just two modes. There are, in fact, numerous modes, and this
feature is probably indispensable. Pay close attention to the prompt at all times.
Within privileged mode there are many sub-modes. In this document I do not closely follow Cisco terminology
for this hierarchy of modes. I think that my explanation is clearer, frankly. Cisco describes two modes,
unprivileged and privileged, and then a hierarchy of commands used in privileged mode. I reason that it is much
clearer to understand if you just consider there to be many sub-modes of privileged mode, which I will also call
parent mode. Once you enter privileged mode (parent mode) the prompt ends with a pound sign (#). There are
numerous modes you can enter only after entering privileged mode. Each of these modes has a prompt of the
form:
Router(arguments)#
They still all end with the pound sign. They are subsumed within privileged mode. Many of these modes have
sub-modes of their own. Once you enter priliged mode, you have access to all the configuration information and
options the IOS provides, either directly from the parent mode, or from one of its submodes.
If you have just turned on the router, it will be completely unconfigured. If it is already configured, you may want
to view its current configuration. Even if it has not been previously configured, you should familiarize yourself
with the show commands before beginning to configure the router. Enter privileged mode by issuing the
command enable, then issue several show commands to see what they display. Remember, the command show ?
will display all the showcommands aavailable in the current mode. Definately try out the following commands:
Router#show interfaces
Router#show ip protocols
Router#show ipv6 protocols
Router#show ip route
Router#show ipv6 route
Router#show ip arp
Router#show ipv6 neighbors
When you enter privileged mode by using the command enable, you are in the top-level mode of privileged
mode, also known in this document as "parent mode." It is in this top-level or parent mode that you can display
most of the information about the router. As you now know, you do this with the show commands. Here you can
learn the configuration of interfaces and whether they are up or down. You can display what IP protocols are in
use, such as dynamic routing protocols. You can view the route and ARP tables, and these are just a few of the
more important options.
As you configure the router, you will enter various sub-modes to set options, then return to the parent mode to
display the results of your commands. You also return to the parent mode to enter other sub-modes. To return to
the parent mode, you hit ctrl-z. This puts any commands you have just issued into affect, and returns you to
parent mode.
To configure any feature of the router, you must enter configuration mode. This is the first sub-mode of the parent
mode. In the parent mode, you issue the command config.
Router#config
Router(config)#
As demonstrated above, the prompt changes to indicate the mode that you are now in.
In connfiguration mode you can set options that apply system-wide, also refered to as "global configurations." For
instance, it is a good idea to name your router so that you can easily identify it. You do this in configuration mode
with the hostname command.
Router(config)#hostname ExampleName
ExampleName(config)#
As demonstrated above, when you set the name of the host with the hostname command, the prompt immediately
changes by replacing Router with ExampleName. (Note: It is a good idea to name your routers with an organized
naming scheme.)
Another useful command issued from config mode is the command to designate the DNS server to be used by the
router:
This is also where you set the password for privileged mode.
Until you hit ctrl-Z (or type exit until you reach parent mode) your command has not been put into affect. You
can enter config mode, issue several different commands, then hit ctrl-Z to activate them all. Each time you hit
ctrl-Z you return to parent mode and the prompt:
ExampleName#
Here you use show commands to verify the results of the commands you issued in config mode. To verify the
results of the ip name-server command, issue the command show host.
Cisco interface naming is straightforward. Individual interfaces are referred to by this convention:
"Media type" refers to the type of media that the port is an interface for, such as Ethernet, Token Ring, FDDI,
serial, etc. Slot numbers are only applicable for routers that provide slots into which you can install modules.
These modules contain several ports for a given media. The 7200 series is an example. These modules are even
hot-swapable. You can remove a module from a slot and replace it with a different module, without interrupting
service provided by the other modules installed in the router. These slots are numbered on the router.
Port number refers to the port in reference to the other ports in that module. Numbering is left-to-right, and all
numbering starts at 0, not at one.
For example, a Cisco 7206 is a 7200 series router with six slots. To refer to an interface that is the third port of an
Ethernet module installed in the sixth slot, it would be interface ethernet 6/2. Therefor, to display the
configuration of that interface you use the command:
ExampleName#show interface ethernet 6/2
If your router does not have slots, like a 1600, then the interface name consists only of:
For example:
ExampleName#config
ExampleName(config)#interface serial 1/1
ExampleName(config-if)#ip address 192.168.155.2 255.255.255.0
ExampleName(config-if)#ipv6 address fe80::230:1bff:fe80:b8ea/64
ExampleName(config-if)#ipv6 enable
ExampleName(config-if)#no shutdown
ExampleName(config-if)#ctrl-Z
ExampleName#
Note the no shutdown command. An interface may be correctly configured and physically connected, yet be
"administratively down." In this state it will not function. The command for causing an interface to be
administratively down is shutdown.
In the Cisco IOS, the way to reverse or delete the results of any command is to simply put no infront of it. For
instance, if we wanted to unassign the IP address we had assigned to interface serial 1/1:
Configuring most interfaces for LAN connections might consist only of assigning a network layer address and
making sure the interface is not administratively shutdown. It is usually not necessary to stipulate data-link layer
encapsulation. Note that it is often necessary to stipulate the appropriate data-link layer encapsulation for WAN
connections, such as frame-relay and ATM. Serial interfaces default to using HDLC. A discussion of data-link
protocols is outside the scope of this document. You will need to look up the IOS command encapsulation for
more details.
IP routing is automatically enabled on Cisco routers. If it has been previously disabled on your router, you turn it
back on in config mode with the command ip routing.
ExampleName(config)#ip routing
ExampleName(config)#ctrl-Z
ExampleName(config)#ipv6 unicast-routing
ExampleName(config)#ctrl-Z
There are two main ways a router knows where to send packets. The administrator can assign static routes, or the
router can learn routes by employing a dynamic routing protocol.
Static routes are generally used in very simple networks or in particular cases that necessitate their use. To create
a static route, the administrator tells the router operating system that any network traffic destined for a specified
network layer address should be forwarded to a similiarly specified network layer address. In the Cisco IOS this is
done with the ip route and ipv6 route commands.
ExampleName#config
ExampleName(config)#ip route 172.16.0.0 255.255.255.0 192.168.150.1
ExampleName(config)#ctrl-Z
ExampleName#show ip route
ExampleName#config
ExampleName(config)#ipv6 route fe80::230:1bff:fe80::/64 fe80::230:1bff:fe80::1
ExampleName(config)#ctrl-Z
ExampleName#show ipv6 route
Two things to be said about this example. First, the packet destination address must include the subnet mask for
that destination network. Second, the address it is to be forwarded to is the specified addres of the next router
along the path to the destination. This is the most common way of setting up a static route, and the only one this
document covers. Be aware, however, that there are other methods.
Dynamic routing protocols, running on connected routers, enable those routers to share routing information. This
enables routers to learn the routes available to them. The advantage of this method is that routers are able to
adjust to changes in network topologies. If a route is physically removed, or a neighbor router goes down, the
routing protocol searches for a new route. Routing protocols can even dynamically choose between possible
routes based on variables such as network congestion or network reliability.
There are many different routing protocols, and they all use different variables, known as "metrics," to decide
upon appropriate routes. Unfortunately, a router needs to be running the same routing protocols as its neighbors.
Many routers can, however, run mutliple protocols. Also, many protocols are designed to be able to pass routing
information to other routing protocols. This is called "redistribution."
Routing protocols are a complex topic and this document contains only this superficial description of them. There
is much to learn about them, and there are many sources of information about them available. An excelent source
of information on this topic is Cisco's website, http://www.cisco.com.
This is a seperate section because IPv6 is new to most people, and they will be looking specifically for
information about configuring IPv6. Examples of configuring IPv6 are included throughout the document,
however, alongside IPv4. That is a more accurate reflection of how you will work with IPv6 on a day-to-day
basis. Once the newness of IPv6 passes, it will be one more piece in the familiar puzzle.
The important concept to understand when configuring IPv6 is that IPv4 and IPv6 exist in parrallel. One is not a
replacement for the other, at least not in the way it is treated by the operating system. A term for this is dual
stack. An interface can have an IPv4 address and no IPv6 address. Or an IPv6 address and no IPv4 address. Or
both an IPv4 address and an IPv6 address. Examples:
IPv4 only
!
interface FastEthernet0/0
ip address 192.168.1.138 255.255.255.0
!
IPv6 only
!
interface FastEthernet0/0
ipv6 address fe80::230:1bff:fe80::/64
ipv6 enable
!
!
interface FastEthernet0/0
ip address 192.168.1.138 255.255.255.0
ipv6 address fe80::230:1bff:fe80::/64
ipv6 enable
!
Notice that there are seperate but similiar commands for IPv4 and IPv6. To assign an IPv4 address,
There are some bigger differences between IPv4 and IPv6 IOS commands. For example, the IPv6 equivilant of
show ip arp, is show ipv6 neighbors.
Once you have configured routing on the router, and you have configured individual interfaces, your router
should be capable of routing traffic. Give it a few moments to talk to its neighbors, then issue the commands show
ip route and show ip arp. There should now be entries in these tables learned from the routing protocol.
If you turned the router off right now, and turned it on again, you would have to start configuration over again.
Your running configuration is not saved to any perminent storage media. You can see this configuration with
the command show running-config.
ExampleName#show running-config
You do want to save your successful running configuration. Issue the command copy running-config
startup-config.
Your configuration is now saved to non-volatile RAM (NVRAM). Issue the command show startup-config.
ExampleName#show startup-config
Now any time you need to return your router to that configuration, issue the command copy startup-config
running-config.
1. Router>enable
2. Router#config
3. Router(config)#hostname N115-7206
4. N115-7206(config)#interface serial 1/1
5. N115-7206(config-if)ip address 192.168.155.2 255.255.255.0
6. N115-7206(config-if)ipv6 address fe80::230:1bff:fe80:b8ea/64
7. N115-7206(config-if)ipv6 enable
8. N115-7206(config-if)no shutdown
9. N115-7206(config-if)ctrl-z
10. N115-7206#show interface serial 1/1
11. N115-7206#config
12. N115-7206(config)#interface ethernet 2/3
13. N115-7206(config-if)#ip address 192.168.150.90 255.255.255.0
14. N115-7206(config-if)#no shutdown
15. N115-7206(config-if)#ctrl-z
16. N115-7206#show interface ethernet 2/3
17. N115-7206#config
18. N115-7206(config)#ip name-server 172.16.0.10
19. N115-7206(config)#ctrl-z
20. N115-7206#ping archie.au
21. N115-7206#config
22. N115-7206(config)#enable secret password
23. N115-7206(config)#ctrl-z
24. N115-7206#copy running-config startup-config
25. N115-7206#exit
Inevitably, there will be problems. Usually, it will come in the form of a user notifying you that they can not
reach a certain destination, or any destinattion at all. You will need to be able to check how the router is
attempting to route traffic, and you must be able to track down the point of failure.
You are already familiar with the show commands, both specific commands and how to learn what other show
commands are available. Some of the most basic, most useful commands you will use for troubleshooting are:
Router#show interfaces
Router#show ip protocols
Router#show ipv6 protocols
Router#show ip route
Router#show ipv6 route
Router#show ip arp
Router#show ipv6 neighbors
It is very possible that the point of failure is not in your router configuration, or at your router at all. If you
examine your router's configuration and operation and everything looks good, the problem might be be farther up
the line. In fact, it may be the line itself, or it could be another router, which may or may not be under your
administration.
One extremely useful and simple diagnostic tool is the ping command. Ping is an implementation of the IP
Message Control Protocol (ICMP). Ping sends an ICMP echo request to a destination IP address. If the
destination machine receives the request, it responds with an ICMP echo response. This is a very simple exchange
that consists of:
Yes, I am.
ExampleName#ping xx.xx.xx.xx
If the ping test is successful, you know that the destination you are having difficulty reaching is alive and
physically reachable.
If there are routers between your router and the destination you are having difficulty reaching, the problem might
be at one of the other routers. Even if you ping a router and it responds, it might have other interfaces that are
down, its routing table may be corrupted, or any number of other problems may exist.
To see where packets that leave your router for a particular destination go, and how far, use the trace command.
ExampleName#trace xx.xx.xx.xx
It may take a few minutes for this utility to finish, so give it some time. It will display a list of all the hops it
makes on the way to the destination.
There are several debug commands provided by the IOS. These commands are not covered here. Refer to the
Cisco website for more information.
Do not overlook the possibility that the point of failure is a hardware or physical connection failure. Any number
of things can go wrong, from board failures to cut cables to power failures. This document will not describew
troubleshooting these problems, except for these simple things.
Check to see that the router is turned on. Also make sure that no cables are loose or damaged. Finally, make sure
cables are plugged into the correct ports. Beyond this simple advice you will need to check other sources.
If the point of failure is farther up the line, the prolem might lie with equipment not under your administration.
Your only option might be to contact the equipment's administrator, notify them of your problem, and ask them
for help. It is in your interest to be courtious and respectful. The other administrator has their own problems, their
own workload and their own priorities. Their agenda might even directly conflict with yours, such as their
intention to change dynamic routing protocols, etc. You must work with them, even if the situation is frustrating.
Alienating someone with the power to block important routes to your network is not a good idea.