CSC341

CSC341
Network
Management
Lab Manual I
1
Third Semester BS (CS)
Computer Science Faculty
Dear students,
The handbook helps you in practicing your practical labs in the subject
CSC341 Network Management. This is the first basic level lab manual of the
above mentioned subject and contains 26 labs of which some of them are
outside of the course outline. This lab manual is prepared for the students in
order to learn and enhance their intermediate skills in network management and
furthermore, to learn and attend the cisco routing and switching certification.
In case of any errors or guidelines you can contact the faculty though an
application.
Regards
Mr. Dilawar
Dean of CS Faculty
Jahan University
2
Topics Covered
Lab 1 -- Connecting to a Router
Lab2 Introduction to the Basic User Interface
Lab 3 Introduction to the basic Show Commands
Lab 4 Cisco Discovery Protocol
Lab 5 Extended Basics
Lab 6 Banner Message of the Day
Lab 7 Copy Command
Lab 8 Introduction to the Interface Configuration
Lab 9 Introduction to Internet Protocol
Lab 10 Address Resolution Protocol
Lab 11 Creating a Host Table
Lab 12 Static Routers
Lab 13 Routing Information Protocol
Lab 14 Troubleshooting Routing Information Protocol
Lab 15 Interior Gateway Routing Protocol
Lab 16 Connectivity Test with traceroute
Lab 17 Saving Router Configuration
Lab 18 Loading Router Configuration
Lab 19 Copying and Pasting Configuration
Lab 20 Integrated Services Digital Network
Lab 21 Introduction to Switch
Lab 22 Basic Switch Commands
Lab 23 2950 Switch Basic Native IOS
Lab 24 Spanning Tree Protocol on 2950 Switch
Lab 25 VLAN
Lab 26 VLAN Trunking Protocol
3
Lab 1: Connecting to a Router
Objective: Become familiar with the Cisco Router
Background:
Lab Equipment: Router 1 from the Router menu
Procedure:
Step 1
When the lab finished loading the router 1 window will open and the text Press enter to
start will appear.
Step 2
Click inside the router 1 window, and press the Enter key to get started. You are now
connected to router 1 and are at the user mode prompt. The prompt is broken into two
parts: the host name and the mode. Router is router 1s host name, and the >indicates
user mode.
Press enter to get started
Router>
Step 3
Next type the enable command to get to the privileged mode prompt.
Router>enable
Router#
Step 4
To return to the user mode, simply type disable. From user mode, type logout or exit to
exit the router.
Router# disable
Router>
Router> exit
Router con0 is now available
Press return to get started
Lab 2: Introduction to the Basic User Interface

Objective: Become familiar with the command-line interface (CLI), user and privileged
mode, and basic help and show commands.
Background:
Lab Equipment: Router 1 from the eRouters menu
Procedure:
Step 1
Press ENTER key to get to the router prompt.
Router>
Step 2
The interface is now in user mode. At the user mode prompt, type the command that is
used to view all the command available in user mode
1
Router>?
Step 3
Type the command used to enter privileged mode.
Router> enable
Router#
Step 4
Type the command that will allow you to view the available commands in privileged
mode.
Router#?
Step 5
Type the command that will allow you to see all of the show commands
Router# show?
Step 6
Type the command that will allow you to see the active or running, configuration.
Router# show running-config
Step 7
At the MORE prompt, press the SPACEBAR key to view the next page of information.
SPACEBAR
Step 8
Finally, type one of the commands that will log you out of the router.
Router# exit
OR Router# disable
Lab 3: Introduction to the Basic Show Commands

Objective: To become familiar with the basic show commands.
Background:
Lab Equipment: Router 1 from eRouters menu
Procedure:
Step 1
Press ENTER to get to the router prompt.
Router>
2
Step 2
Enter privileged mode.
Router> enable
Router#
Step 3
Display the active configuration in memory. The currently active configuration script
running on the router is referred to as the running-config in the routers command-line
interface (CLI). Note that privileged mode is required in order to access the running
configuration. The running configuration script is not automatically saved on a CISCO
router and will be lost in the event of power failure. The running configuration must be
manually saved with the copy command.
Router # show running-config
Step 4
Display flash memory. Flash memory is a special kind of memory that contains the
operating system image file(s) on the router. Unlike regular router memory, flash
memory continues to maintain the file image even after power is lost.
Router# show flash
Step 5
By default the routers CLI maintains in memory the last 10 commands entered. The
show history command displays simultaneously all of the past commands still in router
memory.
Router# show history
Step 6
Press the Ctrl+P key combination the retrieve the previous command you typed.
Step 7
Press the DOWN ARROW key or press the CTRL+N key combination to see the next
command in the history buffer.
Step 8
Use the show protocols command to view the status of the current layer 3 routed
protocols running on your router.
Router# show protocols
Step 9
The show version command is used to obtain critical information, such as router
platform type, operating system version, operating system last boot time and file
location, amount of memory, number of interfaces and configuration register.
Router# show version
3
Step 10
Use the show clock command to view the routers clock
Router# show clock
Step 11
The show hosts command displays a cached list of host and all of their interfaces IP
addresses
Router# show host
Step 12
Use the show user command to view a list of all users who are connected to the router
Router# show users
Step 13
The show interfaces command displays detailed information about each interface.
Router# show interfaces
Step 14
The show protocols command displays the global and interface- specific status of any
Layer 3 protocols.
Router# show protocols
Lab 4: CDP
Objective: To learn how the Cisco Discovery Protocol (CDP) functions and what is required
for Cisco devices to be discovered.
Background:
Lab Equipment: Router 1 and router 4 from eRouters menu
Procedure:
Step 1
On Router 1, enter global configuration mode.
Router> enable
Router# config t
Router (config) #
Step 2
Change the host name to R1.
Router (config) # hostname R1
R1 (config) #
4
Step 3
Connect to Router 4 and change the host name to R4.
Router>enable
Router#config t
Router (config) # hostname R4
R4 (config) #
Step 4
Return to R1 and enable the serial 0 interface. By default all interfaces are shut down
(disabled).
R1 (config) # interface serial 0
R1 (config-if)# no shutdown
Step 5
Now enable the serial 0 interface on R4.
R4 (config) # interface serial 0
R4 (config-if) # no shutdown
Step 6
Enable the Ethernet 0 interface on R1.
R1 (config) # interface Ethernet 0
R1 (config-if) # no shutdown
Step 7
CDP allows devices to share basic configuration information and will operate without
any protocol-specific information being configured. CDP, which is enabled by default
on all interfaces, is a Data Link protocol that operates at Layer 2 of the OSI model. This
is important to understand because CDP is not routable, it can only travel to directly
connected devices.
On R1, type the command that displays the status of all interfaces that are running CDP.
R1 (config-if) # exit
R1 (config) # exit
R1# show cdp interface
5
The sample output below shows that both interfaces are up and sending CDP packets:
Serial0 is up, line protocol is up
Encapsulation HDLC
Sending CDP packets every 60 seconds
Holdtime is 180 seconds
<output omitted>
R1#
Now that the router has interfaces that are broadcasting and receiving CDP updates, you
can use CDP to find out about directly connected neighbours.
Step 8
On R1, type the command that provides information about directly connected
neighbours.
R1# show cdp neighbours
Below is some sample output:
Capability Codes: R-Router, T- Trans Bridge, B-Source Router Bridge, S- Switch, H-
Host, I-IGMP, r- Repeater
Device ID Local Interface Hold time Capability Platform Port ID
R4 Serial 0 148 R 1700 Serial 0
R1#
The first device on the directly connected neighbours list for R1 is R4 via the serial 0
link. R1 is receiving CDP updates from R4; the updates tell R1 to retain the information
for a specified amount of time. At the time this command was entered, there were 148
seconds left in the hold time for R1s update. If that time expires before another update
is received. R1 information will be removed from the table. R4 is a 1000 series router as
indicated in the Platform column. The final column, PORT ID, indicates the port on
the other device form which the updates are being sent.
Step 9
On R1, type the command that provides more detailed information about directly
connected neighbours.
R1# show cdp neighbours detail
6
Below is some output:
Device ID: R4
Entry address (es):
Platform: cisco 2501, Capabilities: Router
Interface: Serial0, Port ID (outgoing port): Serial0
Hold time: 162 seconds
Version:
Cisco Internetwork Operating System Software
Software, Version 12.0 (16), RELEASE SOFTWARE (fc2)
Copyright 1989-2001 by cisco Systems, Inc.
Compiled Fri 02-Mar-01 17:34 by dchih
To show cdp neighbour detail command shows devices one at a time. It is used to
display Network layer address information. The command also displays IOS version
information. Notice that the devices are listed in order. If you wanted to find out
information about a device further down the list, you would need to scroll down using
the SPACEBAR.
Step 10
On R1, type the command to provide information about the specific devices R4.
R1# show cdp entry R4
Device ID: R4
Entry address (es):
Platform: cisco 1000, Capabilities: Router
Interface: Serial0, Port ID (outgoing port): Serial0
Hold time: 148 seconds
Version:
Software, Version 12.0 (16), RELEASE SOFTWARE (fc2)
Copyright 1986-2001 by cisco Systems, Inc.
Compiled Fri 02-Mar-01 17:34 by dchih
R1#
7
The show cdp entry command provides the same information as the show cdp
neighbour detail command, but it allows a single device to be satisfied. Also, notice
that this is one of the only case-sensitive commands that exist.
Step 11
On R1, type the command that shows how often CDP updates are being sent and how
long a recipient should retain the update.
R1# show cdp
Below is some sample outputs:
Global CDP information:
Sending a holdtime value of 180 seconds
Sending CDP v2 advertisement is enabled
On R1, adjust the number of seconds between CDP updates to 45.
R1#conf t
R1 (config) # cdp timer 45
Besides the updates interval, the hold time value may also be adjusted. This value tells
the recipient of the update how long to retain the CDP information in the update. It is
also a global parameter.
Step 12
On R1, type the command to adjust the holdtime timer to 60 seconds.
R1# conf t
R1 (config) # cdp holdtime 60
Step 13
On R1, type the command that will allow you to verify that the changes have been
made.
R1# show cdp
R1# sh cdp
Sending CDP v2 advertisement is enabled
R1#
8
Step 14
If there are no other directly connected Cisco devices on the network, or if you want to
conserve bandwidth, you can disable CDP.
On R1, type the command that disables CDP for the entire router.
R1# conf t
R1 (config) # no cdp run
At times, you may wish to disable CDP for a specific interface for security reasons, or
simply because the interface has very low bandwidth.
Step 15
On R1, type the command that turns CDP back on the entire router.
R1# conf t
R1 (config) # no cdp run
Step 16
On R1, disable CDP for only the specific interface Ethernet 0.
R1 (config) #interface Ethernet 0
R1 (config-if) # no cdp enable
Step 17
On R1, verify that Ethernet 0 is no longer sending CDP updates. (If the Ethernet 0
interface does not show up as an entry in the output, you can conclude that it is not
sending CDP upates)
Below is sample output from the command:
Serial 0 is up, line protocol is up
Encapsulation HDLC
9
Lab 5: Extended Basics
Objectives: view and configure some basic areas of the router.
Background:
Lab Equipment: Router 1 form eRouter menu
Procedure:
Step 1
Press ENTER to get to the router prompt.
Router>?
Step 2
Enter the command that is used to view all the commands available in the user mode.
Router>?
Step 3
Enter privileged mode. This is the mode that gives you complete control of the router.
Router> enable
Router#
Step 4
View the commands in the privileged mode
Router#?
Step 5
Enter the command that provides access to global configuration mode.
Router# config terminal
Router (config) #
Step 6
The routers host name is used for local identification. When you logon to the router, you
see its host name in front of the prompt (either the > or the # prompt). The host name can
be used to identify the location or function of the router. Set the routers host name to
Krang.
Router (config) # hostname Krang
Krang (config) #
Step 7
The enable password controls access to privileged mode. This is a very important
password because when it is configured only those who know the password can make
configuration changes in privileged mode. Set the enable password to boson.
Krang (config) # enable password boson
10
Step 8
Test the password. Exit the router and try to enter privileged mode. Notice that you have
to provide the password in order to enter privileged mode. Now, type the conf term
command and proceed with the instructions in the next step.
Krang (config) # exit
Krang# exit
Password:
Krang# config term
Krang (config) #
Step 9
The only problem with the enable password is that it appears in plain text in the routers
configuration file. If you need to obtain assistance in troubleshooting a problem, you
may inadvertently compromise the security of your system by revealing the password.
Set the enable secret password to cisco.
Krang (config) # enable secret cisco
Step 10
Now test this password by logging out of the router and then typing enable at the user
mode prompt. The enable secret password overrides the enable password. If you have set
both passwords, you must use the enable secret password to enable privileged mode. The
enable password is still configured but is now deactivated.
Krang (config) # exit
Krang# exit
Krang> enable
Password:
Krang#
Lab 6: Banner Message of the Day

Objective: Configure a banner Message of the Day (MOTD). The MOTD is displayed when
a user logs on to the router. The banner can also be used to display information about the
router itself or to display a security message.
Background:
Lab Equipment: Router 1 from eRouters menu.
Procedure:
11
Step 1
Connect to the router1 and enter privileged mode.
Router>
Router> enable
Router#
Step 2
Enter configuration mode.
Router# config t
Router (config) #
Step 3
Type the command to enter the banner message and press ENTER. After you type
banner motd, enter a delimiting character so the router knows when you are finished
entering text for the banner. The easiest one to use is the letter Z.
Router (config) #banner motd z
Enter the next followed by the z to finish
Step 4
Now all text that you type, until you type the letter Z; will be stored as the banner. Type
the text you do not have permission to be here. This router eats hackers for lunch! z,
and press ENTER. This will set the banner.
You do not have permission to be here. This router eats hackers for lunch! z
Step 5
To view the banner exit configuration mode, and then exit the router. Press ENTER to
display the banner.
Router (config#) exit
Router# exit
Router>exit
Press RETURN to get started.
You do not have permission to be here. This router eats hackers for lunch!
12
Lab 07: Copy Command
Objective: To become familiar with the router configuration and the copy commands
available in the Cisco IOS.
Background:
Lab Equipment: router1 from eRouters menu
Procedure:
Step 1
Connect to router1 and enter privileged mode.
Router>enable
Router#
Step 2
Display the active configuration in memory. The currently active configuration script
running on the router is referred to as running-config in the routers command- line
interface (CLI). Note that privileged mode is required to display the active configuration.
The running configuration script is not automatically saved on Cisco router and will be
lost in the event of power failure. The running configuration must be manually saved
with the copy command.
Router# show running-config
Step 3
Try to display the configuration stored in NVRAM (known as startup-config). You
have not saved the configuration, so there is not one to show.
Router# show startup-config
Step 4
Copy the current active configuration to NVRAM. The current active configuration is in
RAM; it should be saved so that the router will still boot up with the configuration in the
event of a power outage.
Router# copy running# config startup-config
Step 5
Now show the configuration stored in NVRAM.
Step 6
If you decide that you would like to continue the router from scratch, you can erase the
startup configuration and reload the router. This will enable you to completely delete all
configuration on the router so that you can start from scratch. Type the command that
will delete the configuration file in NVRAM. When prompted, confirm that you do want
to erase the NVRAM file system by pressing the Y key.
13
Router# erase startup-config
Step 7
Now type the command to reload the router and press the Y key when prompted to
confirm the reload.
Router# reload
Step 8
After the router reboots look at the startup configuration file again. Because you did not
save it before you reloaded, there is nothing there.
Router>enable
Step 9
Now, change the host name of the router to Boson.
Router# config terminal
Router (config) # hostname Boson
Boson (config) # exit
Boson#
Step 10
Save your router configuration and reload the router. Again, press the Y key when
prompted to confirm the reload.
Boson# copy run start
Boson# reload
Step 11
After the router reloads, the host name of Boson appears in the prompt. If you run the
show startup config command, nothing appears.
Boson>enable
Boson# show startup-config
14
Lab 08: Introduction to Interface Configuration
Objective: Learn to enable interfaces on a router, and learn what is required for the interface
to be up.
Background:
Procedure:
Step 1
On router1, enter global configuration.
Router> enable
Router# conf t
Router (config) #
Router (config) # hostname Router1
Step 2
Type the command to enter interface configuration mode for Ethernet 0.
Router1 (config) #interface Ethernet 0
Router1 (config-if) #
Step 3
Display all the commands available in interface configuration mode by typing ?
Step 4
The shutdown command shuts down the selected interface. You can often achieve the
opposite of a command by typing no in front of it. Execute the command on router 1
Ethernet 0 to enable the interface.
Router 1(config-if) # no shutdown
Step 5
Add a description for this interface.
Router1 (config-if) # description Ethernet interface on Router 1
Step 6
To view the interface description, exit back to privileged mode, and run the show
interface command. You should see the description under Ethernet 0.
Router1 (config-if) # end
Router1 # show interface
Step 7
Connect to router 2, and assign it a host name of Router 2.
15
Router# conf t
Router (config) # hostname router 2
Step 8
Now access the Ethernet 0 interface, and enable the interface.
Router2 (config) # interface Ethernet 0
Router 2 (config-if) # no shutdown
Step 9
Now that the interfaces on both sides of the Ethernet connection are enabled, they should
be able to see on another through CDP. Use the show cdp neighbours command on
Router2 to view all directly connected Cisco routers
Router2 (config-if) # end
Router2# show cdp neighbour
Lab 09: Introduction to Internet Protocol

Objective: Configure Routers 1, 2 and 4 with Internet Protocol (IP) address and ping
between them to test connectivity.
Background:
Lab Equipment: Router1, Router 2 and Router 4 from eRouters menu
Procedure:
Step 1
Connect to router 1 and assign it a host name of Router1.
Router>enable
Router# conf t
16
Router (config) #hostname router 1
Router1 (config) #
Step 2
Enter interface configuration mode for the Ethernet 0 interface.
Router1 (config-if) #
Step 3
Type the command that will set the IP address on the Ethernet 0 interface to 10.1.1.1
255.255.255.0 and enable the interface.
Router1 (config-if) # ip address 10.1.1.1 255.255.255.0
Router1 (config-if) # no shutdown
Step 4
Set the IP address on the serial 0 interface of Router1 to 172.16.10.1 255.255.255.0, and
enable the interface.
Router1 (config) # interface serial 0
Router1 (config-if) # no shut
Step 5
Connect to Router2 and assign it a host name of Router2.
Router> enable
Router# conf t
Router2 (config) #
Step 6
Set the IP address for the Ethernet 0 interface to 10.1.1.2.255.255.255.0, and enable the
interface.
Step 7
Connect to router4 and assign it a host name of Router4.
Router> enable
Router#conf t
17
Step 8
Configure an IP address of 172.16.10.2 255.255.255.0 on the serial 0 interface and
Router4 (config) # interface serial 0
Step 9
From router1 try to ping Router2s Ethernet interface.
Router1#ping 10.1.1.2
Step 10
Try to ping Router4s serial 0 interface.
Router1# ping 172.16.10.2
Step 11
Verify that the lines and protocols are up for all of Router1s interface.
Router1#show ip interface brief
Step 12
Display Router1s running configuration, and verify that the IP address appear.
Router1#show running-config
Step 13
Display detailed IP information about each interface on Router1.
Router1# show ip interface
Lab 10: Address Resolution Protocol

Objective: Configure router1 and 2 with IP addresses and ping between them to test
connectivity. Then view the entries stored in the Address Resolution Protocol (ARP) table.
Background:
Lab Equipment: Router 1 and router 2 from eRouters menu.
Procedure:
Step 1
Connect to router1 and type the command to view the ARP table.
Router> enable
18
Router# show arp
Step 2
Assign an IP address of 10.1.1.1 255.255.255.0 to the Ethernet 0 interface of Router1.
Router# conf terminal
Router (config) # interface Ethernet 0
Router (config-if) # ip address 10.1.1.1 255.255.255.0
Router (config-if) # no shutdown
Router (config-if) # exit
Step 3
View the ARP table again.
Router (config) # exit
Router# show arp
Step 4
Now connect to router2 and configure its Ethernet 0 interface with an IP address
10.1.1.2/24.
Router# conf terminal
Router (config) # interface Ethernet 0
Router (config-if) # ip address 10.1.1.2 255.255.255.0
Router (config-if) # no shutdown
Step 5
A connection should now exist between the router 1 and router 2 Ethernet interfaces. To
ensure that the connection is functional, ping the IP address of Router1s Ethernet 0 IP
address of Router2.
Router# ping 10.1.1.1
Step 6
View the ARP table on Router 2 and notice the entry.
Router# show arp
Step 7
Now clear the ARP table.
Router # clear arp
19
Step 8
View the ARP table one last time and notice what entries are there.
Router# show arp
Lab 11: Creating a Host Table

Objective: Become familiar with the routers host table. Host tables can be used to set names
for commonly used IP addresses which helps with troubleshooting.
Background:
Lab Equipment: router1 from eRouters menu.
Procedure:
Step 1
Connect to Router1 and set the host name to California.
Router> enable
Router# config t
Router (config) # hostname California
California (config) #
Step 2
Configure an IP address of 195.42.36.10 255.255.255.240 on the Ethernet 0 interfaces,
be sure to enable the interface.
California (config) # interface Ethernet 0
California (config-if) # ip address 195.42.36.10 255.255.255.240
California (config-if) #no shutdown
Step 3
Connect to router2 and set the host name to Tampa.
Router> enable
Router# config t
Router (config) # hostname tampa
Tampa (config) #
Step 4
Configure an IP address of 195.42.36.12 255.255.255.240 on the Ethernet 0 interface, be
sure to enable the interface.
Tampa (config) # interface Ethernet 0
Tampa (config-if) # ip address 195.42.36.12 255.255.255.240
20
Tampa (config-if) #no shutdown
Step 4
Exit interface mode. You do not have to type Californias Ethernet 0 IP address every
time you try to ping it from Tampa, so set a host table entry for California using the IP
address 195.42.36.10.
Tampa (config) # ip host California 195.42.36.10
Tampa (config#) exit
Step 5
Now you should be able to ping Californias Ethernet 0 IP address from Tampa just by
typing ping California.
Tampa# ping California
Step 6
Use the show hosts commands to verify that the entry is stored in the routers host
table.
Tampa# show hosts
Lab 12: Static Routers

Objective: Configure Router1, 2 and 4 with IP addresses, and then add static router for all
routers.
Background:
Lab Equipment: router1, router2 and router4 from eRouters menus.
Goals:
Set the host name, and bring up the interfaces.
Ping the directly connected interfaces.
Configure static routes for the topology.
Verify that you can ping all routers.
Procedure:
Step 1
Configure Router1, 2 and 4 to the specifications outlined in the table and diagram
below.
Device Router 1 Router 2 Router 4
Host Name Router 1 Router 2 Router 4
Ethernet 0 10.1.1.1/24 10.1.1.2/24
Serial 0 12.5.10.1/24 12.5.10.2/24
21
Step 2
On each router, verify that you can ping the directly connected neighbours.
Step 3
Now you need to establish static routes on each router to any location that is not directly
connected. Router1 is directly connected to both router2 and router4, so it will not need
any static routes.
On router4, enter global configuration mode, and think about what the static route
command should be. You know that you currently cannot reach router2 because it is not
directly connected. Off of router4s serial interfaces is network 12.5.10.0 which is
connected to router1. Router1 is also connected to network 10.1.1.0, which you would
also like to access. In this case, you will need a static route for network 10.1.1.0. on
router4, what command should you use to establish a static route to network 10.1.1.0?
Router4# conf term
Router4 (conf) # ip route 10.1.1.0 255.255.255.0 12.5.10.1
You established a route to network 10.1.1.0. Now, whenever a packet of information
leaves Router4 destined for network 10.1.1.0, it will first be sent to IP address 12.5.10.1
on Router1.
Step 4
Now try to ping Router1s serial 0 interface, Router1s Ethernet 0 interface and Router2s
Ethernet 0 interface.
Consider why the ping to 10.1.1.2 (Router2s Ethernet 0 interface) was unsuccessful. A
packet leaves Router4s serial 0 interface destined for 10.1.1.2. Because the destination
address is on the 10.1.1.0 network and the static route on Router4 stipulates that traffic
destined for the network should first be sent to 12.5.10.1, the packet will travel to
12.5.10.1. When the packet reaches Router1, the router send the packet out the interface
that is directly connected to the 10.1.1.0 network. Router2 picks up that packet on its
Ethernet 0 interface and attempts to send a response packet to confirm receipt. Router2
examines the source IP address of the received packet which is 12.5.10.2 (Router4s
serial 0 interface). Router2 does not have a route network 12.5.10.0, so it drops the
packet. This is why the ping was not successful.
22
Step 5
Just to make sure the static route on Router4 worked, view the routing table to see if the
static route has been added there.
Router4# show ip route
Step 6
To enable Router4 to ping 10.1.1.2, connect to Router2 and configure static route back to
Router4s network. Type the command that will set a static route on Router2 for the
network 12.5.10.0.
Router# config term
Router2 (config) # ip route 12.5.10.0 25.255.255.0 10.1.1.1
Router2 (config) # exit
Consequently, any data sent to network 12.5.10.0 will go to 10.1.1.1 first.
Step 7
Connect to Router4 again and make sure you can ping router1s serial 0 interface.
Router1s Ethernet 0 interface, and Router2s Ethernet 0 interface.
Router# ping 10.1.1.2
Step 8
Examine the routing table on Router2.
Codes: C-connected, S- static, I-IGRP, R-RIP, M-mobile, B-BGP, D- EIGRP, EX-
EIGRP external, O- OSPF, IA-OSPF inter area, E1- OSPF external type1, E2-
OSPF external type 2, E- EGP, i- IS-IS, L1 IS-IS level-1, L2 IS-IS level-2, *-
candidate default, U- per- user static route
Gateway of last resort is not set
C 10.1.1.0/24 is directly connected 10.1.1.2
S 12.5.10.0/24 [1/10] via 10.1.1.1
In the S 12.5.10.0/24[1/10] via 10.1.1.1 line of output, the S denotes the static route.
Next, the destination network and its subnet information (12.5.10.0/24) are displayed.
The [1/10] represents the administrative distance which is 1 by default, and the metric
(hop count in this case), which is 0. The word via signals the next hop address the packet
should be sent to, which in this case is 10.1.1.1.
23
Lab 13: Routing Information Protocol
Objective: Configure Router 1, 2 and 4 with IP addresses and the Routing Information
Protocol.
Background:
Lab Equipment: Router1 and Router 2 and router 4 from eRouters menu.
Goals:
Set the host name and bring up the interface.
Configure RIP.
Select the directly connected networks.
Display the routing table.
Display the RIP protocol information.
Procedure:
Step 1
Configure Router1, 2 and 4 to the specifications outlined in the table and diagram
below.
Ethernet 0 10.1.1.1/24 10.1.1.2/24
Serial 0 172.16.10.1/24 172.16.10.2/24
Step 2
On each router, verify that you can ping the directly connected neighbours.
Router2#ping 10.1.1.1
Step 2
Add RIP to router1.
Router1#
Router1# configure terminal
Router1 (config) # router rip
Router1 (config-router) #
Step 3
Add the network(s) to which Router1 is directly connected.
Router1 (config-router) # network 10.0.0.0
24
Step 4
Add RIP to Router2.
Router2#
Step 5
Step 6
Add RIP to Router 4
Router4#
Step 7
Step 8
Now, RIP should be running on all three routers. See if you can ping between routers
that are not directly connected. For instance, from Router2 you should now be able to
ping Router4s serial 0 interface.
Router2 # ping 172.16.10.2
Step 9
Connect to Router4 and ping Router2s Ethernet 0 interface.
If you can ping both devices, then you have correctly configured routing. If the pings
were not successful, trace back through the steps.
Step 10
Now, issue the command to display the routing table on Router4.
25
Step 11
Finally, display specific IP routing protocol information on Router4.
Router4# show ip protocol
Lab 14: Troubleshooting Routing Information Protocol

Objective: Configure IP addresses on Router1, 2 and 4 with Routing Information Protocol
(RIP) as the routing protocol. Then, observe routing activity using the debug ip rip command
and examine routers using the show ip route command.
Background:
Lab Equipment: Router1, router2 and router4 from eRouter menu.
Procedure:
Step 1
Configure Router1, 2 and 4 to the specifications outlined in the table below:
Ethernet 0 192.168.1.1/24 192.168.1.2/24
Serial 0 192.168.2.1/24 192.168.2.2/24
Step2
Use the proper network statements to configure RIP on all routers.
Router1# conf t
Router1 (config-router) # exit
Router1#
Router2# config t
Router2#
Router4# conf t
26
Router4#
Step 3
Use the show ip route command to confirm that the routes are being received on all
routers.
Step 4
Once the routers have received the routes, execute the debug ip rip command at the
privileged mode prompt on Router1.
Router1# debug ip rip
Observe the output on Router1s terminal screen. (The output could take up to 60
seconds to appear.)
Step 5
To turn off the debug command, use the no keyword in front of the command (i.e; no
debug ip rip)
Router1# no debug ip rip
Step 6
View the routing table entries on router2 and router4. Notice the administrative
distances and metrics for these routes.
Step 7
Make sure you can ping all devices on the network from every other device. If all pings
do not succeed, then you will need to troubleshoot the router configurations toe ensure
you configured all settings correctly.
27
Lab 15: Interior Gateway Routing Protocol

Objective: Configure Router1, 2 and 4 with IP addresses and Interior Gateway Routing
Protocol (IGRP).
Background:
Lab Equipment: Router1, router2 and router 4 from eRouter menu
Goals:
Set the host name and bring up the interfaces.
Configure IGRP.
Select the directly connected networks.
Display the routing table.
Display the IGRP protocol information.
Procedure:
Step 1
Configure router1, router2 and router4 to the specifications outlined in the table and
diagram below.
Ethernet 0 10.1.1.1/24 10.1.1.2/24
Serial 0 172.16.10.1/24 172.16.10.2/24
Step 2
After you have configured the correct IP address on each interface, verify that each
router can ping its directly connected neighbours.
Step 2
Access global configuration mode on Router1 and enter the command to configure
IGRP as the routing protocol on Router1; use the autonomous system number 100.
Router1# config terminal
Router1 (config) # router igrp 100
28
Step 3
Add network(s) to which Router1 is directly connected.
Step 4
Now, enter global configuration mode on Router2 and add IGRP. Remember to use the
same autonomous system number.
Router2 (config- router) #
Step 5
Step 6
Now, enter global configuration mode on Router1 and add IGRP. Remember to use the
same autonomous system number.
Router4 (config- router) #
Step 7
Step 8
IGRP should now be running on all three routers. See if pings are successful between
routers that are not directly connected. From router2, you should now be able to ping
router4s serial 0 interface. From router4, you should be able to ping router2s Ethernet
0 interface.
If you can ping both devices then you have correctly configured routing. If the pings
were not successful, trace back through the steps.
Step 9
Now, display the routing table on Router4.
29
Router4 # show ip route
Step 10
Finally display specific IP routing protocol information on Router4.
Router4# show ip protocol
LAB 16: Connectivity Test with traceroute

Objective: Learn how to use traceroute command. This command is used to map the IP
addresses that a packet travels through to get from one device to another.
Background:
Lab Equipment: router1, router2 and router4 from eRouter menu
Procedure:
Step 1
Configure router1, 2 and 4 to the specifications outlined on the below diagram:
Ethernet 0 192.168.1.1/24 192.168.1.2/24
Serial 0 192.168.2.1/24 192.168.2.2/24
Step 2
After you have configured the proper IP addresses, enable RIP routing across all three
routes. Make sure you use the proper network statements.
Router1# conf t
Router1#
Router2# conf t
Router2#
30
Router4# conf t
Router4#
Step 3
From router1, ping the directly connected routers and their interfaces, which are router2
Ethernet 0 and router4 serial 0.
Step 4
Because RIP routing is enabled, you should be able to ping non-directly connected
routers. Connect to router2, and ping router4s serial 0 interface.
Step 5
The global behind the traceroute command is to help you troubleshoot and determine
the path a packet is taking to reach a destination device. In this example, there are three
routers and only one path to any destination. Trace the route from Router4s serial 0
interface.
Router2# traceroute 192.168.2.2
Step 6
Observe the output from the traceroute command. It lists Router1s Ethernet 0 IP
address and then the destination IP address. This means that the packet leaves Router2s
Ethernet 0 interface and passes through Router1s Ethernet 0 interface before reaching
Router4s serial 0 interface.
Lab 17: Saving Router Configuration

Objective: Learn how to back up a routers configuration in case the configuration in case
the configuration is accidently deleted or the router fails.
Background:
Lab Equipment: Router4 from the eRouters menu and PC 1 from the eStations menu.
Procedure:
Step 1
31
Connect to router4 and change the host name to Tampa.
Router> enable
Router# conf t
Router (config) # hostname Tampa
Tampa (config) #
Step 2
Assign the IP address of 24.37.2.1 255.255.255.0 to the Ethernet 0 interface, and then
Tampa (config) # interface Ethernet 0
Tampa (config-if) # ip address 24.37.2.1 255.255.255.0
Tampa (config-if) # no shutdown
Step 3
Connect to PC 1 by selecting it from the eStation menu. Type the command that will
allow you to configure PC1s IP address and default gateway. Set the IP address to
24.37.2.252 with a subnet mask of 255.255.255.0. Set the default gateway to Tampas
Ethernet 0 IP address (24.37.2.1).
C :> winipcfg
Step 4
From PC1 , ping Tampas Ethernet 0 interface to make sure connectivity exists to the
default gateway.
C :> ping 24.37.2.1
Step 5
Connect to Tampa again, exit interface configuration mode, and then exit global
configuration mode.
Copy the running configuration to the TFTP server on PC1.
Tampa (config-if) # exit
Tampa (config) # exit
Tampa# copy running- config tftp
Step 6
When prompted for the address or name of the TFTP server, provides PC1s IP address
(24.37.2.252), press ENTER and then provide the name of the configuration file that
will be stored on PC1. Name the configuration file Tampa_config.
24.37.2.252
Tampa_config
32
After you press ENTER, the router will take a few seconds to establish the connection;
then you will see it after copy the configuration file and tell you how long it took.
Step 7
Next, connect back to PC1 and type the show tftp-configs command in order to display
the configurations that are stored on the tftp server. (Note: this command does not work
on real PCs, just in the NetSim program)
C : >show tftp-configs
If you see the configuration in the list, you have successfully completed the lab.
Note: lab 19 builds on this labs configuration. To complete lab 19. Please continue
with the instructions for lab 19 in this lab. If you load another lab from the Lab
Navigator, your changes will be lost and Lab 19 will not work properly.
Lab 18: Loading Router Configurations

Objective: become familiar with the process of loading router configurations.
Background:
Lab Equipment: router4 from eRouters menu (tampa from lab 18)
Prerequisite: you must have completed Lab 18: Saving Router Configurations in order to
complete this lab successfully.
Procedure:
Step 1
Now that the configuration is stored on the TFTP server, change the hostname of the
router. This will prove that the configuration was copied from the TFTP server. Log on
to Tampa and enter global configuration mode.
Tampa# config t
Tampa (config) #
Step 2
Change the host name to Bad_Router.
Tampa (config) # hostname Bad_Router
Step 3
Copy the configuration you stored on the TFTP server into the running_configuration
on Bad_Router.
Bad_router (config) # exit
Bad_router# copy tftp running-config
Step 4
33
When the router prompts you for a name or an IP address, enter the IP address of the
TFTP server.
Address or name of remote host []?24.37.2.252
Step 5
Enter the name of the configuration file that should be obtained from the TFTP server.
Source filename []? Tampa_config
Step 6
The router will download the configuration and load it into the running configuration.
Afterward, the host name will be restored to what it was the configuration was saved.
Tampa#
Lab 19: Copying and Pasting Configuration

Objective: learn to save, reload and paste modified configuration from within the simulator
Background:
Cisco routers use a command-line parsing routine. Each time you press a carriage return, the
router passes that command and executes the code that is required to carry out the command.
The simulator works the same way. When you are working with the simulator, you can easily
switch between devices using the menus across the top of the window. The simulator offers
some built-in saving and loading options.
Procedure:
Step 1
Set the host name of router1 to Router1
Router> enable
Step 2
Select the Save Single Device Config option from the File menu. The program will ask
for a file name; use Router1 and click Save. Save the files to a convenient location that
you will remember easily.
Step 3
After you have saved the file, exit the simulator and then start it again. Reload Stand-
Alone Lab 20 from the Lab Navigator.
Step 4
Select the Load Single Device Config (overwrite) option from the File menu. Select the
Router1.rtr file that you just saved and then click Open.
34
Step 5
The program will then open the file and execute all the commands that were previously saved
on the device. Once it is finished, you will notice that the hostname has been restored.
Step 6
Two other options under the File menu offer similar functionality: the Save Multi
Devices Configs option and the Load Multi Devices Configs option. These two options
respectively will save and load the configurations for all the devices.
Step 7
Saved files can be edited easily. Minimize the program and double-click the Roure1.rtr
file that you just saved to your computer. When the operating system asks you which
program you would like to use to open the file, select Microsoft Notepad.
Step 8
Notepad will launch with router1s running configuration displayed. You will see the
hostname command a few lines down. Change this line from the hostname Router1 to
hostname Miami. Save your changes.
Step 9
Now repeat step 04 and observe the hostname change.
Step 10
If you have created a configuration that you want to paste into the routers, the program
offers a tool to allow you to do this.
Step 11
First, make sure Router1 is open. Select the Paste Real Router Configs option from the
File menu this will open a window that will allow you to paste configuration files you
would like to have executed on Router1. In the empty text box, type the following:
Hostname Router1
Interface Ethernet 0
Ip address 1.1.1.1 255.255.255.0
No shutdown
Exit
Step 12
After you have typed the commands above, click the OK button. The router will quickly
execute the commands. Notice that the host name of the router will change back to
Router1.
Step 13
Execute the show ip interface brief command on Router1 to see that the ip address has
been set for Ethernet 0.
35
Lab 20: Integrated Service Digital Network
Objective: learn how to setup Integrated Services Digital Network (ISDN) on Cisco routers.
Background:
Lab Equipment: router1 and router2 from eRouters menu.
Procedure:
Step 1
Connect to router1 and assign it a hostname of Router1.
Router>enable
Router# conf t
Step 2
Connect to Router2 and assign it a host name of Router2.
Router> enable
Router#conf t
Router (config) # hostname Router2.
Step 3
Now, set up the connection between router1 and router 2 using the BRI ports. Assign
the BRI 0 interface of Router1 an IP address of 42.34.10.1 with a 255.255.255.0 subnet
mask, enable the interface and then exit interface configuration mode.
Router1 (config) # interface BRI0
Router1 (config-if) # exit
Router1 (config-) #
Step 4
Now connect to Router2 and assign its BRI 0 interface an IP address of 42.34.10.121
with a 255.255.255.0 subnet mask. Enable the interface, and then exit interface
configuration mode.
Router2 (config) # interface BRI0
Router2 (config-) #
36
Step 5
Return to Router1, and start to configure ISDN. First, specify the ISDN switch type that
will be used. If you use the Simulator defaults, the switch type is basic-ni. There are
two different ways to configure the type of ISDN switch type the router should use. You
can specify the command globally for all BRI interfaces on the router, or you can make
the switch type interface- specific. In this instance, enter the switch type globally on
your router.
Router1 (config) # isdn switch-type basic-ni
Step 6
Configure some specific information for this BRI interface. First, assign it the ISDN
SPID (Service Profile Identifier). Set the SPID on the BRI interface of Router1 by using
the isdn spid1 command. A SPID is a number supplied by ISP to identify the line
configuration of the BRI service. Each SPID points to line setup and configure
information on the ISPs ISDN switch. If you use the default for the ISDN switch, the
SPID for Router1 will be 32177820010100.
Router1 (config) #interface bri 0
Router1 (config-if) # isdn spid 1 32177820010100
Step 7
Now that you have configured the switch type and SPID, Layer1 connectivity should
exist. Layer1 connectivity occurs between the ISDN switch and the router. To verify
that Layer1 connectivity exists, use the show isdn status command at the privileged
mode prompt. Make sure that the Layer2 state is Multiple_Frame_Established.
Router1# show isdn status
Step 8
Now, configure the number that will need to be dialled on the ISDN switch to establish
a Layer3 connection; this is called the dialer string. Set the dialer string on Router1s
BRI 0 interface. If you are using the default configuration, use 7782001.
Router1# config t
Router1 (config) # interface bri 0
Router1 (config) # dialer string 7782001
Step 9
Because ISDN costs money when the connection is up, the connection should only be
active when it is being used. You can use dialer groups and dialer lists to accomplish
this. A dialer list either permits or denies traffic. Specify a dialer list of protocol ip
permit; consequently, all IP traffic will be permitted. To setup a dialer list, use the
dialer-list command on global configure mode.
37
Router1 (config) # dialer-list 1 protocol ip permit
Step 10
The dialer list must be associated with an interface. Add the dialer list to the ISDN BRI
0 interface by using the dialer-group 1 command.
Router1 (config-if) # dialer- group 1
Step 11
Now that you have set up ISDN on Router1, you need to perform the same steps for
Router2, but with some slight modifications. Connect to Router2 and specify the ISDN
switch type that you will be using. If you use the Simulator defaults, the switch type id
basic-ni. Specify the switch type in global configuration mode on the router.
Router2 (config) # isdn switch-type basic-ni
Step 12
Next, provide the SPID for this interface. If you use the Simulator defaults for the ISDN
switch, the SPID for Router2 will be 32177820010100.
Router2 (config-if) # isdn spid1 32177820010100
Step 13
Now that you have set up the switch type and SPID, Layer1 connectivity should be
established. To verify that Layer 1 connectivity exists, use the show isdn status
command at the privileged mode prompt. Make sure that the Layer2 state is
Multiple_Frame_Established.
Router2# shoe isdn status
Step 14
Now, configure the dialer string that you will need to dial on the ISDN switch in order
to establish a Layer 3 connection. Set the dialer string on Router2s BRI 0 interface. If
you are using the default configuration, use 7782002.
Router2# config t
Router2 (config) #interface bri 0
Router2 (config-if) #dialer string 7782002
Step 15
Configure the dialer list named protocol ip permit on Router2 to permit all IP traffic
Router2 (config) # dialer-list 1 protocol ip permit
38
Step 16
Use the dialer-group 1 command to add the dialer list to the ISDN BRI 0 interface.
Router2 (config-if) # dailer-group 1
Step 17
Now that both routers are configured for ISDN, see if you can ping the router on the
other side of the connection. From Router2, ping Router1s BRI 0 interface (IP address
42.34.10.1).
Step 18
If the ping is successful, ISDN is working. Verify this by issuing the show isdn status
command on Router2.
Router2# show isdn status
Examine the Layer3 settings; there should be one active Layer3 call. You should also
see that the SPID is valid in Layer2. This information is useful for troubleshooting.
Step 19
Finally, view the configuration changes you have made by displaying the running
configuration.
Router2# show running-config
Lab 21: Introduction to Switch

Objective: view some basic areas of Cisco Catalyst 1900 switch.
Background:
Lab Equipment: switch 1 from the eSwitches menu
Procedure:
Step 1
Connect to Switch1. You should see the user mode prompt.
>
Step 2
Enter the command to display the IOS version of the switch.
>show version
What version of the IOS is running? _______________________________________
39
What is the model number of the switch? __________________
What is the Base Ethernet Address of the switch? _______________________
Step 3
Display the interface of the switch
>show interfaces
How many of the interfaces are 10 Mbps? _____________________
How many ports are 100 Mbps Fast Ethernet? ______________________________
Step 4
Enter the command to view the MAC address table.
>show mac-address-table
How many dynamic entries have been learned? _______________
Step 5
Display the running configuration.
>show running-config
Lab 22: Introduction to Basic Switch Command

Objective: To become familiar with the basic configuration of the Cisco Catalyst 1912
switch.
Background:
Lab Equipment: Switch 1 from eSwitches menu
Procedure:
Step 1
Connect to Switch1. You should see the user mode prompt.
>
Step 2
Display the list of commands available at this prompt.
>?
Step 3
Now, enter privileged mode.
>enable
#
40
Step 4
Display the available commands in privileged mode
#?
Lab 23: 2950 Switch Basic Native IOS

Objective: Basic commands of Native IOS on 2950 and 3550.
Lab Equipment: 2950 switch
Background:
Procedure:
Configuration:
Step 1
After connecting your PC to the Console Port.
Switch con0 is now available.
Switch> (User mode)
Step 2
To Enter Into Privilege mode/Executive Mode From User Mode and Vice Versa.
Switch> enable
Switch#
Switch# disable
Switch>
Step 3
To Enter Into Global Configuration Mode
Switch# config t
Switch (config) #
Step 4
To change the host name of switch.
Switch (config) # hostname 2950-SWA
2950-SWA (config) #
Step 5
Set the message of the day banner
Swutch (config) # banner motd # HELLO & WELCOME TO CISCO WORLD#
41
Step 6
Display the version information of the switch
2950-SWA # show version
IOS C2950 Software (C2950-I5Q3L2-M), version 12.1(20) EA2, RELEASE
SOFTWARE (fc1)
Copyright 1986-2004 by cisco System, Inc.
Compiled Wed 19-May-04 05:06 by Antonio
Image text-base: 0x0003000, data-base: 0x0082D44C
ROM: bootstrap program is C2950 boot loader
2950 uptime is 7 hours, 11 minutes

System returned to ROM by power-on
System image file is flash: c2950-i5q3l2-mz.121-20.EA2.bin
Cisco WS-C2950-24 (Power PC) processor (revision L0) with 65526K/8192K bytes of
memory.
Processor broad ID CAT0805Z0CW
Last reset from warm-reset
Bridging software.
Running Layer2/3 Switching Image
Ethernet-controller 1 has 12 Fast Ethernet/IEEE 802.3 interfaces

Ethernet-controller 2 has 12 Fast Ethernet/IEEE 802.3 interfaces
Ethernet-controller 3 has 1 Gigabit Ethernet/IEEE 802.3 interface
Ethernet-controller 1 has 1 Gigabit Ethernet/IEEE 802.3 interface
24 Fast Ethernet/ IEEE 802.3 interface(s)

2 Gigabit Ethernet/IEEE 802.3 interface(s)
42
The password-recovery mechanism is enabled.
384K byte of flash-simulated non-volatile configuration memory.
Base Ethernet MAC Address: 00:0F:24:68:05:00
Motherboard assembly number: 73-5700-11
Power supply part number: 34-0966-04
Motherboard serial number: CAT08050JCX
Power supply serial number: DTH08042TFG
Model revision number: L0
Motherboard revision number: A0
Model number: WS-CAT0805Z0CW
Configuration register is 0x10F
Step 7
Show contents of Current Configuration (RAM).
2950-SWA # show running-config
Building configuration
Current configuration: 2146 bytes
!
Version 12.2
No service pad
Service timestamps debug uptime
Service timestamps log uptime
No service password-encryption
!
Hostname 2950-SWA
!
<Output Omitted>
Ip subnet-zero
!
!
Spanning-tree mode pvst
Spanning-tree extend system-id
43
!
Interface FastEthernet 0/1
Switchport mode dynamic desirable

!
<Output Omitted>
!
Interface FastEthernet0/23
Switchport mode dymanic desirable
!
!
Interface Gigabit Ethernet 0/1
!
Interface Gigabit Ethernet 0/2
!
Interface Vlan1
No ip address
Shutdown
!
Ip classless
Ip http server
!
<Output Omitted>
!
End
44
Step 8
Display the flash information
2950-SWA # dir
or
2950-SWA # show flash:
Directory of flash: /
2 -rwx 556 Mar 1 1993 00:18:07 +00:00 vlan.dat
3 -rwx 4219426 Mar 1 1993 00:44:10 +00:00 c2950-i5q312-mz.121-20.EA2.bin
4 -rwx 315 Mar 1 1993 00:45:44 +00:00 system_env_vars
5 -rwx 0 Mar 1 1993 00:45:43 +00:00 env.vars
8 drwx 192 Mar 1 1993 0:04:07 +00:00 c2950-i9q312-mz.121-14.EA1a
87 rwx 744 Mar 1 1993 0:26:17 +00:00 debug.text
15998976 bytes total (6026752 bytes free)
Step 9
To give the IP address of management domain interface of 2950
2950-SWA (config) # int vlan 1
2950-SWA (config-if) # ip address 10.0.0.10 255.0.0.0
2950-SWA (config-if) # no shutdown
Step 10
Display the Information of Management VLAN Interface.
2950-SWA # s hint vlan 1
Vlan is up, line protocol is up
Hardware is EtherSVI, address is 000f.2468.0500 (bia 000f.2468.0500)
Internet address is 10.0.0.10/8
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
Reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARP, ARP Timeout 04:00:00
45
Queuing strategy: fifo
Output queue: 0/40 (size/max)
<Output Omitted>
Step 11
Display the information of All Interfaces on the switch
2950-SWA# s hip int brief
Interface IP-Address OK Method Status Protocol

Vlan1 10.0.0.10 Yes Manual Up Down
Fast Ethernet 0/1 Unassigned Yes Unset down Down
Fast Ethernet 0/2 Unassigned Yes Unset down Down
Fast Ethernet 0/23 Unassigned Yes unset down Down
<Output Omitted>
Fast Ethernet 0/24 unassigned YES unset down Down
Gigabit Ethernet 0/1 Unassigned YES unset down Down
Gigabit Ethernet 0/2 unassigned YES unset down Down
Step 12
Set IP default network in a switched network
2590-SWA (config) # ip default-gateway 10.0.0.1
Step 13
Display the status of the interfaces on the switch
2950-SWA# show interfaces status
Port Name Status Vlan Duplex Speed Type
Fa0/2 notconnectde 1 auto auto 10/100BaseTX
<Output Omitted>
Gi0/1 notconnectde 1 auto auto unknown
Gi0/22 notconnectde 1 auto auto unknown
46
Step 14
Display the detailed information of interfaces.
2950-SWA# show interfaces
or
2950-SWA# show interfaces fast Ethernet 0/1
Fast Ethernet 0/1 is up, line protocol is up (connect)
Hardware is fast Ethernet, address is 000f.2468.0501 (bia 000f.2468.0501)

Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 100BaseTX

Input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Queuing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
<Output Omitted>
Step 15
Display the information of the mode of interfaces (switch port)
2950-SWA# show interfaces switchport
or
2950-SWA# show interfaces fast Ethernet 0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administration Mode: dynamic desirable
Operational Mode: static access
Administrative Trunking Encapsulation: dot 1q
47
Operational trunking encapsulation: native
Negotiation of trunking: on
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN:1 (default)
<output omitted>
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Appliance trust: none
Step 16
Display the detailed information of interfaces capabilities
2950-SWA# show interfacescapibilties
or
2950-SWA# show interfaces fastEthernet 0/1 capibilties
FastEthernet0/1
Model: WS-C2950-24
Type: 10/100BaseTX
Speed: 10,100, auto
Duplex: half, full, auto
Trunk encap, type: 802.1Q.1SL
Trunk mode: on, off, desirable, nonegotiate
Channel: yes
<output omitted>
Step 17
Display the information of the trunk interface (Ports)
2950-SWA# show interfaces trunk
48
Port mode encapsulation status native vlan
Fa0/23 desirable n-802.1q trunking 1
Fa0/24 desirable n-802.1q trunking 1
Port Vlans allowed on trunk

Fa0/23 1-4094
Fa0/24 1-4094
Port Vlans allowed and native in management domain

Fa0/23 1-2
Fa0/24 1-2
Port Vlans in spanning tree forwarding state and not pruned

Fa0/23 1-2
Fa0/24 2
Step 18
Setting of speed,pulex and description on interface.
2950-SWA (config) # int fastEthernet 0/1
2950-SWA (config-if) # speed 100
2950-SWA (config-if) # duplex full
2950-SWA (config) # description Fast-Ethernet-Port-1
Step 19
Configuring the multiple interfaces
2950-SWA (config) # int range fastEthernet 0/1-5
2950-SWA (config-if-range) # switchport mode access
Step 20
Display the information of CDP (Cisco Discovery Protocol)
2950-SWA# sh cdp
49
Sending CDPv2 advertisements is enable
Step 21
Display the information of CDP Enabled Interfaces
2950-SWA# sh cdp interfaces
FastEthernet 0/1 is up, line protocol is up
Encapsulation ARPA
FastEthernet 0/2 is down, line protocol is down

Encapsulation ARPA
<Output Omitted>
FastEthernet 0/23 is down, line protocol is down

Encapsulation ARPA
FastEthernet 0/24 is up, line protocol is up
Encapsulation ARPA
GigabitEthernet 0/1 is down, line protocol is down

Encapsulation ARPA
GigabitEthernet 0/2 is down, line protocol is down
50
Encapsulation ARPA
Step 22
Enabled the CDP on the switch
Switch (config) # cdp run
Step 23
Enable CDP on the interface fast ethernet 0/1
Switch (config) # interface fastethernet 0/1
Switch (config-if) # cdp enable
Step 23-A
Set he line console password on the switch
2950-SWA (config) # line console 0
2950-SWA (config-line) # password cisco
2950-SWA (config-line) # login
Step 23-B
Verification line console password on the switch
2950-SWA con0 is now available
User access verification
Password:
2950-SWA> enable
Step 23-A
Set the privileged mode password in clear text
2950-SWA (config) # enable password cisco
Step 23-B
Verifying the privileged mode password in clear text
2950-SWA # disable
2950-SWA > enable
Password:
51
2950-SWA#
Step 23-A
Set the privileged Mode Password in encrypted form
2950-SWA (config) # enable secret cisco
The enable secret you have is the same as your enable password.
This is not recommended. Re-enter the enable secret.
2950-SWA (config)# enable secret cisco1
Step 23-B
Verifying the privileged mode password in encryoted form.
2950-SWA > enable
Password:
Step 24
Set Line VTY Password on the switch
2950-SWA (config) # line vty 0 15
2950-SWA (config-line) # password cisco
2950-SWA (config-line) # login
Step 25
Display the information of dynamic trunking protocol (DTP)
2950-SWA # show dtp
Global DTP information
Sending DTP Hello packet every 30 seconds
Dynamic Trunk timeout is 300 seconds
4 interfaces using DTP
Step 26
Copy the Current Configuration Into Startup Configuration
950-SWA# copy running-config startup-config
Destination filename [startup-config]?
Building configuration
[OK]
52
Lab 24: Spanning Tree Protocol on 2950 Switch
Objective: understanding the spanning tree protocol operation in switched environment by
creating a multiple or redundant link between switches.
Background:
Lab Equipment: 2950 switch
Procedure:
The spanning tree protocol on the 2950-SWA & 2950-SWB switches.
Changing Non Root Switch into Root Switch By Decreasing the priority.
Verifying the Spanning Tree Protocol on the 2950-SWA & 2950-SWB
switches after changing priority.
Select Root Port on (Non-Root Switch) by Changing Cost of Port.
Verifying the Spanning Tree Protocol on the 2950-SWA & 2950-SWB
switches after changing Cost of Port.
Configuration:
Step 1-A
Verifying the Spanning Tree Protocol on the 2950-SWA switches
2950-SWA# show spanning-tree
or
2950-SWA # sh spanning-tree vlan1
VLAN0001
Spanning Tree enabled protocol ieee
Root ID Priority 32769

Address 0012.43a0.b840
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32769 (priority 32769 sys-id-ext1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Aging Time 15
Interface Role Sts Cost Prio.Nbr Type

Fa0/23 Desg FWD 19 128.23 P2p
Fa0/24 Desg FWD 19 128.24 P2p
53
Step 1-B
Verifying the detailed information of Spanning Tree Protocol on the 2950-
SWA switch.
2950-SWA # sh spanning-tree vlan 1 detail
VLAN0001 is executing the ieee compatible Spanning Tree Protocol.
Bridge Identifier has priority 32768, sysid 1, address 0012.43a0.b840
Configured hello time 2, max age 20, forward delay 15
We are the root of the spanning tree
Topology change flag not set, detected flag not set
Number of topology changes 1 last change occurred 00:06:50 ago
From FastEthernet 0/23
Times: hold 1, topology change 35, notification 2
Hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 23 (Fast Ethernet 0/23) of VLAN0001 is forwarding

Port path cost 19, port priority 128, port Identifier 128.23.
Designated root has priority 32769, address 0012.43a0.b840
Designated bridge has priority 32769, address 0012.43a0.b840
Designated port id is 128.23, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state:1
Link type is point to-point by default
BPDU: sent 221, received 1
Port 24 (Fast Ethernet 0/24) of VLAN001 is forwarding

Port path cost 19, port priority 128, port Identifier 128.23.
Designated root has priority 32769, address 0012.43a0.b840
54
Number of transitions to forwarding state:1
Link type is point -to-point by default
Step 2-A
Verifying the Spanning Tree Protocol on the 2950-SWB switch
2950-SWA# show spanning-tree
or
2950-SWB# show spanning-tree vlan 1
VLAN0001
Spanning tree enabled protocol ieee
Cost 19
Hello time 2sec Max Age 20sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32769 sys-id-ext 1)

Hello time 2sec Max Age 20sec Forward Delay 15 sec Aging time 300

Fa0/23 Root FWD 19 128.23 P2p
Fa0/24 Altn FWD 19 128.24 P2p
Step 2-B
Verifying the detailed information of spanning tree protocol on the 2950-
SWB switch
2950-SWB# show spanning-tree detail
or
2950-SWB # sh spanning-tree vlan1detail
VLAN0001 is executing the ieee compatible Spanning Tree Protocol.
55
Bridge Identifier has priority 32768, sysid 1, address 0012.43a0.b840
Configured hello time 2, max age 20, forward delay 15
Current root has priority 32769, address 0012.43a0.b840

Root port is 23 (Fast Ethernet0/23), cost of root path is 19
Topology change flag not set, detected flag or not set
Times: hold 1, topology change 35, notification 2
Hello 2 max, age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 23 (fast Ethernet0/23) of VLAN0001 is forwarding

Port path cost 19, port priority 128, port identifier 128.23
Designated root had priority 32769, address 0012.43a0.b840
Timers: message age 2, forward delay state:1
Link type is point to point by default
Port 24 (fast Ethernet0/24) of VLAN0001 is blocking

Port path cost 19, port priority 128, port identifier 128.24
Designated root had priority 32769, address 0012.43a0.b840
Number of transmission to forwarding state: 0
Link type is point to point by default
Step 3
Changing non root switch into root switch by decreasing the priority on
2950-SWB (Non-Root-Switch)
2950-SWB (config) # spanning-tree vlan 1 priority 4096
56
Step 4-1
Verifying the spanning tree protocol on the 2950-SWB switch after
changing the priority on 2950-SWB
2950-SWB3 sh spanning-tree vlan 1
VLAN0001
Spanning tree enables protocol ieee



Fa0/23 Desg FWD 19 128.23 P2p
Fa0/24 Desg FWD 19 128.24 P2p
Step 4-B
Verifying the spinning tree protocol on the 2950-SWA switch after
changing priority on 2950-SWB
2950-SWB# sh spanning-tree vlan 1
VLAN0001
Cost 19
Port 23 (Fast Ethernet 0/23)
57

Fa0/23 Root FWD 19 128.23 P2p
Fa0/24 Altn BLK 19 128.24 P2p
Step 5
Select root port on (non-root switch) by changing cost of port on 2950-
SWA
2950-SWA (config) # int fast Ethernet 0/24
2950-SWA (config-if) # spanning-tree vlan 1 cost 18
Step 6
Verifying the spanning tree protocol on the 2950-SWA switch after
changing Cost of Port
2950-SWA # sh spanning- tree vlan 1
VLAN0001
Spanning tree enabled ieee
Cost 18
Port 24 (Fast Ethernet 0/24)

Fa0/23 Altn BLK 19 128.23 P2p
Fa0/24 Root FWD 19 128.24 P2p
58
Step 7
Verifying the spanning tree protocol on the 2950-SWB switch after
changing cost of port
2950-SWB# sh spanning-tree vlan1
VLAN0001


Fa0/23 Desg FWD 19 128.23 P2p
Fa0/24 Desg FWD 19 128.24 P2p
Lab 25: VLAN

Objective: To understand the VLAN operation in switched environment. The major
concerns are:
1. To make Vlans on 2950 switches and Vlan membership assignment to the ports.
2. VLAN Trunking Protocol (VTP)
Procedure:
Connecting PC with 2950 switches and verified by Commands.
Display the results that all ports are the members of the native VLAN.
Create a VLAN#2 on 2950 Switch
Assign a VLAN Membership for a port on 2950 Switch
Verification of VLAN #2
59
Configuration:
Step 1-A
Connecting PC with 2950 switch and vetified by the Interface Command

2950-SWA# sh interfaces fastEthernet 0/1
fastEthernet 0/1 is up, line protocol is up (connected)
Hardware is fast Ethernet , address is 000b.5f03.f9c1 (bia 000b. 5f03.f9c1)
Reliability 255/255, txload 1/255, rxload 1/255

Keepalive set (10 se)
Full duplex, 100Mb/s

<output omitted>
Step 1-B
Connecting PC with 2950 switch and verified by the MAC address Table
command
2950-SWA# show mac address-table dynamic
Mac Address Table
Vlan Mac Address Type Ports
1 0001.0262.fcc4 DYNAMIC Fa 0/1
Total Mac Address for this criterion: 1

Step 2
Display the result that all ports are the members of the native VLAN
2950-SWA# show vlan
or
2950-SWA# show vlan id 1
VLAN NAME Status Ports
1 default active Fa0/1, Fa0/2 Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11. Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
Fa0/21, Fa0/22, Fa023, Fa0/24
Gi0/1, Gi0/2
60
VLAN TYPE SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1 enet 100001 1500 - - - - - 0 0
<output omitted>
Step 3-A
Create a VLAN #2 on 2950 Switch by VLAN Database commands
2950-SWA# vlan database
2950-SWA(vlan) # vlan 2 name esp
VLAN added:
Name: esp
2950-SWA (vlan) # exit
APPLY completed.
Exiting
Step 3-B:
Create a VLAN#2 on 2950 Switch by VLAN command

2950-SWA (config)# vlan 2
2950-SWA (config-vlan) # name esp
Step 4
Assign a VLAN Member0ship for a Fast Ethernet Port 0/1 on 2950 switch
2950-SWA (config) # interface fastEthernet 0/1
2950-SWA (config-if) # switchport mode access
2950-SWA (config-if) # switchport mode access vlan 2
Step
Verification of VLAN #2
29550-SWA # show vlan
or
2950-SWA# sh vlan id 2
61
2 esp active Fa 0/1
2 enet 100002 1500 - - - - - 0 0
<output omitted>
Lab 26: VLAN Trunking Protocol

Procedure:
Make a VTP domain CISCO on switches.
Make a VTP server to 2950-SWA and client to 2950-SWB
Enable a Trunking on the fastEthernet ports 0/24 that connects both switches.
Verifying with VTP status commands on switches.
Verifying the VTP advertisements By Trigger Updates (make vlans) on 2950-SWA
switch.
Verifying the VTP Status on switches after triggered updates.
Verifying the VLAN database on 2950-SWA switch after making VLANs
Verifying the VLAN database consistency on 2950-SWB switch.
Configuration:
Step 1-A
Make a VTP domain CISCO on 2950-SWA switch
2950-SWA (config)# vtp domain CISCO
Changing VTP domain name from NULL to CISCO
Step 1-B
Make a VTP Domain CISCO on 2950- SWB switch
2950-SWB (config) # vtp domain CISCO
Changing VTP domain name form NULL to CISCO
Step 2-A
Make a VTP Server to 2950-SWA switch
2950-SWA (config) # vtp mode?
Client set the device to client mode
Server set the device to server mode
Transparent set the device to transparent mode
62
2950-SWA (conifg) # vtp mode server
Device mode already VTP SERVER
Step 2-B
Make a VTP Client to 2950-SWB switch
2950-SWB (config) # vtp mode client
Setting device to VTP CLIENT mode
Step 3-A
Enable a Trunking on the fastEthernet ports 0/24 of 2950-SWA switch
2950-SWA (config) # int fastEthernet 0/24
2950-SWA (config-if) switchport mode trunk
Step 3-B
Enable a Trunking on the fastEthernet ports 0/24 of 2950-SWB switch
2950-SWB (config) # int fastEthernet 0/24
2950-SWB (config-if) switchport mode trunk
Step 4-A
Verifying the VTP Status on 2950-SWA switch
2950-SWA # sh vtp status
VTP Version :2
Configuration Revision :3
Maximum VLANs supported locally :1005
Number of existing VLANs :6
VTP Operating Mode :Server
VTP Domain Name :CISCO
VTP Pruning Mode :Disabled
VTP V2 Mode :Disabled
VTP Traps Generation :Disabled
MD5 digest :0xD5 0X18 0x44 0xA3 0xAA 0x16 0xAE 0X35
Configuration last modified by 10.0.0.20 at 3-1-93 06:10:50
Local updater ID is 10.0.0.20 on interface V12 (lowest numbered VLAN interface found)
63
Step 4-B
Verifying the VTP Status on 2950-SWA switch
2950-SWB # sh vtp status
VTP Version :2
VTP Operating Mode :Client
Step 5
Verifying the VTP Advertisement By Trigger Updates (Add/Delete/Modify
vlans) On 2950-SWA switch
2950-SWA (config) # valn 25
2950-SWA (config-vlan) # vlan 50
Step 6-A
Verifying the VTP Status on 2950-SWA switch after triggered update.
2950-SWA #sh vtp status
VTP Version :2
VTP Operating Mode :Server
64
Local updater ID is 10.0.0.20 on interface V12 (lowest numbered VLAN interface found)
Step 6-B
Verifying the VTP Status on 2950-SWB switch after triggered update.
2950-SWB #sh vtp status
VTP Version :2
VTP Operating Mode :Client
Step 7
Verifying the VLAN database on 2950-SWA switch after making VLANs
2950-SWA # show vlan
1 default active Fa0/2 Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11. Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
65
Fa0/21, Fa0/22, Fa023, Fa0/24
Gi0/1, Gi0/2
2 esp active Fa0/1

25 VLAN0025 active
50 VLAN0050 active
75 VLAN0075 active
100 VLAN0100 active
1002 fddi-default act/ unsup
1003 token-ring-default act/ unsup
1004 fddinet-default act/ unsup
1005 trnet-default act/ unsup
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
25 enet 100025 1500 - - - - - 0 0
50 enet 100050 1500 - - - - - 0 0
75 enet 100075 1500 -- - - - 0 0
100 enet 100100 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
<output omitted>
Step 8
Verifying the VLAN database consistency on 2950-SWA switch after making VLANs
on 2950-SWA switch
1 default active Fa0/2 Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11. Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
66
Fa0/21, Fa0/22, Fa023, Fa0/24
Gi0/1, Gi0/2
2 esp active Fa0/1
25 VLAN0025 active
50 VLAN0050 active
75 VLAN0075 active
100 VLAN0100 active
1002 fddi-default act/ unsup
1003 token-ring-default act/ unsup
1004 fddinet-default act/ unsup
1005 trnet-default act/ unsup
1 enet 100001 1500 - - - - - 0 0
2 enet 100002 1500 - - - - - 0 0
25 enet 100025 1500 - - - - - 0 0
50 enet 100050 1500 - - - - - 0 0
75 enet 100075 1500 - - - - - 0 0
100 enet 100100 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - srb 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
<output omitted>
67

CSC341 - Network Management Lab - 1

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CSC341 - Network Management Lab - 1

Caricato da

Copyright:

Formati disponibili

Lab 2: Introduction to the Basic User Interface

Lab 3: Introduction to the Basic Show Commands

Lab 6: Banner Message of the Day

Lab 09: Introduction to Internet Protocol

Lab 10: Address Resolution Protocol

Lab 11: Creating a Host Table

Lab 12: Static Routers

Lab 14: Troubleshooting Routing Information Protocol

Lab 15: Interior Gateway Routing Protocol

LAB 16: Connectivity Test with traceroute

Lab 17: Saving Router Configuration

Lab 18: Loading Router Configurations

Lab 19: Copying and Pasting Configuration

Lab 21: Introduction to Switch

Lab 22: Introduction to Basic Switch Command

Lab 23: 2950 Switch Basic Native IOS

ROM: bootstrap program is C2950 boot loader

2950 uptime is 7 hours, 11 minutes

System image file is flash: c2950-i5q3l2-mz.121-20.EA2.bin

Ethernet-controller 1 has 12 Fast Ethernet/IEEE 802.3 interfaces

24 Fast Ethernet/ IEEE 802.3 interface(s)

Interface FastEthernet 0/2

15998976 bytes total (6026752 bytes free)

Interface IP-Address OK Method Status Protocol

Encapsulation ARPA, loopback not set

Auto-duplex, Auto-speed, media type is 100BaseTX

Port Vlans allowed on trunk

Port Vlans allowed and native in management domain

Port Vlans in spanning tree forwarding state and not pruned

FastEthernet 0/2 is down, line protocol is down

FastEthernet 0/23 is down, line protocol is down

GigabitEthernet 0/1 is down, line protocol is down

GigabitEthernet 0/2 is down, line protocol is down

Root ID Priority 32769

Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Interface Role Sts Cost Prio.Nbr Type

Port 23 (Fast Ethernet 0/23) of VLAN0001 is forwarding

Port 24 (Fast Ethernet 0/24) of VLAN001 is forwarding

Bridge ID Priority 32769 (priority 32769 sys-id-ext 1)

Interface Role Sts Cost Prio.Nbr Type

Current root has priority 32769, address 0012.43a0.b840

Port 23 (fast Ethernet0/23) of VLAN0001 is forwarding

Port 24 (fast Ethernet0/24) of VLAN0001 is blocking

Root ID Priority 4097

Bridge ID Priority 4097 (priority 4097 sys-id-ext 1)

Interface Role Sts Cost Prio.Nbr Type

Interface Role Sts Cost Prio.Nbr Type

Bridge ID Priority 32769 (priority 32769 sys-id-ext 1)

Bridge ID Priority 4097 (priority 4097 sys-id-ext 1)

Interface Role Sts Cost Prio.Nbr Type

Lab 25: VLAN

Connecting PC with 2950 switch and vetified by the Interface Command

Encapsulation ARPA, loopback not set

Full duplex, 100Mb/s

Total Mac Address for this criterion: 1

Create a VLAN#2 on 2950 Switch by VLAN command

Lab 26: VLAN Trunking Protocol

2 esp active Fa0/1

Potrebbero piacerti anche