Manual Computer Networking
Manual Computer Networking
Computer Networking
(Lab Journals)
0
Index
Lab # Lab Objective
5 Write the subnet, Broadcast address and valid host ranges for
different IPs
6 Basic Configuration of ROUTER 2621
1
Lab #01
Lab Objective: Making straight through, cross over cable and roll
over cable.
Equipment:
RJ45 connector
Internet cable
RJ45 clamper
Introduction:
Eight-conductor data cable (Cat 3 or Cat 5) contains 4 pairs of wires. Each pair
consists of a solid color wire and a white and color striped wire. Each of the pairs is
twisted together. To maintain reliability on Ethernet, you should not untwist them any
more than necessary (about 1/4 inch).
The other two pairs, brown and blue, are unused. The connections shown are
specifically for an RJ45 plug. The wall jack may be wired in a different sequence
because the wires may be crossed inside the jack. The jack should either come with a
2
wiring diagram or at least designate pin numbers that you can match up to the color
code below. There are two wiring standards for these cables, called T-568A and T-
568B. They differ only in pin assignments, not in uses of the various colors. The
illustration above shows both standards. With the T-568B specification the orange
and green pairs are located on pins 1, 2 and 3, 6 respectively. The T-568A
specification reverses the orange and green connections, so that the blue and orange
pairs are on the center 4 pins, which makes it more compatible with the Telco voice
connections. T-568A is supposed to be the standard for new installations, and T-568B
is the alternative. However, most off-the-shelf data equipment and cables seem to be
wired to T568B.
3
Cross over cable:
Both the ends of the cable must not have same wire arrangement means both having
different stander.
4
Lab #02
Equipment:
Pc (personal computer)
Network card
Theory
A network card (also called network adapter, network interface card, NIC, etc.) is a
piece of computer hardware designed to allow computers to communicate over a
computer network. It is an OSI model layer 2 item because it has a MAC address.
Every network card in the world has a unique 48-bit serial number called a MAC
address. The IEEE allocates these numbers to network card manufacturers who
encode them into the firmware of their cards.
Whereas network cards used to be expansion cards to plug into a computer bus, most
newer computers have a network interface built into the motherboard, so a separate
network card is not required unless multiple interfaces are needed or some other type
of network is used.The card implements the electronic circuitry required to
communicate using a specific physical layer and data link layer standard such as
ethernet or token ring. This provides a base for a full network protocol stack, allowing
communication amongsmall groups of computers on the same LAN and large-scale
network communications through routable protocols, such as IP.There are four
5
techniques used for transfer of data; The NIC may use one or more of these
techniques.
• Polling is where the microprocessor examines the status of the peripheral under
program control
• Programmed I/O is where the microprocessor alerts the designated peripheral
by applying its address to the system's address bus
• Interrupt-driven I/O is where the peripheral alerts the microprocessor that its
ready to transfer data
• DMA is where the intelligent peripheral assumes control of the system bus to
access memory directly
A network card typically has a twisted pair, BNC, or AUI socket where the network
cable is connected, and a few LEDs to inform the user of whether the network is
active, and whether or not there is data being transmitted on it. The Network Cards are
typically available in 10/100/1000 Mbit/s. This means they can support a transfer rate
of 10 or 100 or 1000 Mbit/s.
Notable manufacturers:-
• 3Com Corporation
• Broadcom
• Intel
• Novell
• Realtek
• Marvell
• AMD
• Digital Equipment Corporation
• ASIX Electronics
• National Semiconductor
• VIA Networking
• Silicon Integrated Systems
6
Lab #03
Equipment:
Hub (connector)
Pcs
Cross cable
Theory:
Star Topology
A star topology is designed with each node (file server, workstations, and peripherals)
connected directly to a central network hub or concentrator Data on a star network
passes through the hub or concentrator before continuing to its destination. The hub or
concentrator manages and controls all functions of the network. It also acts as a
repeater for the data flow. This configuration is common with twisted pair cable;
however, it can also be used with coaxial cable or fiber optic cable. The protocols
used with star configurations are usually Ethernet or Local Talk.
. Star topology
7
Advantages of a Star Topology
• Easy to install and wire.
• No disruptions to the network when connecting or removing devices.
• Easy to detect faults and to remove parts.
8
Lab #04
Theory:
You can access the Cisco IOS through the console port of a router, from a modem into
the auxiliary (or Aux) port, or even through Telnet. Access to the IOS command line
is called an EXEC session.
You can connect to a Cisco router to configure it, verify its configuration, and check
statistics. There are different ways to do this, but most often, the first place you would
connect to is the console port. The console port is usually an RJ-45 (8-pin modular)
connection located at the back of the router—by default, there’s no password set.
You can also connect to a Cisco router through an auxiliary port —which is really the
same thing as a console port, so it follows that you can use it as one. But this auxiliary
port also allows you to configure modem commands so that a modem can be
connected to the router. This is a cool feature—it lets you dial up a remote router and
attach to the auxiliary port if the router is down and you need to configure it “out-of-
band” (meaning “out-of-the-network”). “In-band” means the opposite—configuring
9
the router through the network. The third way to connect to a Cisco router is in-band,
through the program
Telnet. Telnet is a terminal emulation program that acts as though it’s a dumb
terminal. You can use Telnet to connect to any active interface on a router, such as an
Ethernet or serial port.
A Cisco 2600 series router is a cut the routers populating the 2500 series because it
has a faster processor and can handle many more interfaces. Figure shows a diagram
of a Cisco 2600 modular router.
Bringing Up a Router
When you first bring up a Cisco router, it will run a power-on self-test (POST). If it
passes, it will then look for and load the Cisco IOS from flash memory—if an IOS file
is present. (Just in case you don’t know, flash memory is an electronically erasable
programmable read-only memory— an EEPROM.) After that, the IOS loads and
looks for a valid configuration—the startup-config— that’s stored by default in
nonvolatile RAM, or NVRAM.If there isn’t a configuration in NVRAM, the router
will go into setup mode —a step-by-step process to help you configure the router. You
10
can also enter setup mode at any time from the command line by typing the command
setupfrom something called privileged mode, which I’ll get to in a minute. Setup
mode only covers some global commands.
Setup Mode
You have two options when using setup mode:Basic Management and Extended
Setup. Basic Management only gives you enough configurations to allow connectivity
to the router, but Extended Setup gives you the power to configure some global
parameters as well as interface configuration parameters. To enter setup mode, just
say “yes” or “y” to the following question:
Command-Line Interface
Because it’s so much more flexible, the command-line interface (CLI) truly is the best
way to configure a router. I sometimes refer to the CLI as “Cash Line Interface”
because if you can create advanced configurations on Cisco routers and switches using
the CLI, then you’ll get the cash! To use the CLI, just say No to entering the initial
configuration dialog. After you do that, the router will respond with messages that tell
you all about the status of each and every one of the router’s interfaces. Here’s an
example:
Would you like to enter the initial configuration dialog?
[yes]:n
Would you like to terminate autoinstall? [yes]:[Enter]
Router>
Router>enable
11
Router#
You now end up with a Router# prompt, which indicates that you’re in
privileged mode,
where you can both view and change the router’s configuration. You can go
back from privileged
mode into user mode by using the disable command, as seen here:
Router#disable
Router>
At this point, you can type logout to exit the console:
Router>logout
Router con0 is now available
Press RETURN to get started.
Or you could just type logout or exit from the privileged-mode prompt to log
out:
Router>en
Router#logout
Router con0 is now available
Press RETURN to get started.
To configure from a CLI, you can make global changes to the router by typing
configureterminal (or config t for short), which puts you in global configuration
mode and changes what’s known as the running-config. A global command (a
command run from global config) is set only once and affects the entire router.You
can type config from the privileged-mode prompt and then just press Enter to take the
default of terminal, as seen here:
Router#config
Configuring from terminal, memory, or network
[terminal]? [Enter]
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
At this point, you make changes that affect the router as a whole (globally),
hence the term global configuration mode.
12
Lab #05
Lab Objective: To write the subnet, Broadcast address and valid host
ranges for different IPs.
Calculations:
192.168.10.0/28
172.16.0.0/23
172.16.10.5/25
HostAddr 172.16.10.5
NetMask 255.255.255.128
NetAddr 172.16.10.0/25
First Host 172.16.10.1
Last Host 172.16.10.126
Broadcast 172.16.10.127
N0. Of Hosts 126
172.16.10.65/26
HostAddr 172.16.10.65
NetMask 255.255.255.192
NetAddr 172.16.10.64/26
First Host 172.16.10.65
Last Host 172.16.10.126
Broadcast 172.16.10.127
N Hosts 62
13
192.168.100.25/30
HostAddr 192.168.100.25
NetMask 255.255.255.252
NetAddr 192.168.100.24/30
First Host 192.168.100.25
Last Host 192.168.100.26
Broadcast 192.168.100.27
No. Of Hosts 2
192.168.100.37/29
HostAddr 192.168.100.37
NetMask 255.255.255.248
NetAddr 192.168.100.32/29
First Host 192.168.100.33
Last Host 192.168.100.38
Broadcast 192.168.100.39
No. Of Hosts 6
192.168.100.66/27
HostAddr 192.168.100.66
NetMask 255.255.255.224
NetAddr 192.168.100.64/27
First Host 192.168.100.65
Last Host 192.168.100.94
Broadcast 192.168.100.95
N Hosts 30
192.168.100.17/29
HostAddr 192.168.100.17
NetMask 255.255.255.248
NetAddr 192.168.100.16/29
First Host 192.168.100.17
Last Host 192.168.100.22
Broadcast 192.168.100.23
No. Of Hosts 6
14
Lab #06
Equipment:
Router 2621 three
Console cable
DTE and DCE connector cable
Personal computers
Cross cable
Theory
In this lab, you will perform commands on a Cisco router that will help you to
understand the Basic configuration of Router.
1. Press Enter to connect to your router. This will put you into user mode.
2. At the Router> prompt, type a question mark (?).
3. Notice the –more– at the bottom of the screen.
4. Press the Enter key to view the commands line by line.
5. Press the spacebar to view the commands a full screen at a time.
6. You can type q at any time to quit.
7. Type enable or en and press Enter. This will put you into privileged mode
where you can change and view the router configuration.
8. At the Router# prompt, type a question mark (?). Notice how many options
are available to you in privileged mode.
9. Type q to quit.
10. Type config and press Enter.
11. Press Enter to configure your router using your terminal.
12. At the Router(config)# prompt, type a question mark (?), then q to quit, or
hit the spacebar to view the commands.
13. Type interface e0 or int e0 (or even int fa0/0) and press Enter. This will
allow you to configure interface Ethernet 0.
14. At the Router(config-if)# prompt, type a question mark (?).
15. Type int s0 (int s0/0) or interface s0 (same as the interface serial 0
command) and press Enter. This will allow you to configure interface serial
0. Notice that you can go from interface to interface easily.
16. Type encapsulation ?.
17. Type exit. Notice how this brings you back one level.
18. Press Ctrl+Z. Notice how this brings you out of configuration mode and
places you back into privileged mode.
19. Type disable. This will put you into user mode.
20. Type exit, which will log you out of the router.
15
Using the Help and Editing Features
1. Log into the router and go to privileged mode by typing en or enable.
2. Type a question mark (?).
3. Type cl? and then press Enter. Notice that you can see all the commands
that start with cl.
4. Type clock ? and press Enter.
5. Set the router’s clock by typing clock ? and, following the help screens,
setting the router’s time and date.
6. Type clock ?.
7. Type clock set ?.
8. Type clock set 10:30:30 ?.
9. Type clock set 10:30:30 14 March ?.
10. Type clock set 10:30:30 14 March 2002.
11. Press Enter.
12. Type show clock to see the time and date.
13. From privileged mode, type show access-list 10. Don’t press Enter.
14. Press Ctrl+A. This takes you to the beginning of the line.
15. Press Ctrl+E. This should take you back to the end of the line.
16. Press Ctrl+A, then Ctrl+F. This should move you forward one character.
17. Press Ctrl+B, which will move you back one character.
18. Press Enter, then press Ctrl+P. This will repeat the last command.
19. Press the Up arrow on your keyboard. This will also repeat the last
command.
20. Type sh history. This shows you the last 10 commands entered.
21. Type terminal history size ?. This changes the history entry size. The ? is
the number of allowed lines.
22. Type show terminal to gather terminal statistics and history size.
23. Type terminal no editing. This turns off advanced editing. Repeat Steps 14
through 18 to see that the shortcut editing keys have no effect until you type
terminal editing.
24. Type terminal editing and press Enter to re-enable advanced editing.
25. Type sh run, then press your Tab key. This will finish typing the command
for you.
26. Type sh start, then press your Tab key. This will finish typing the
command for you.
16
a) _ Type copy run start and press Enter.
b) _ Type copy running, press Tab, type start, press Tab, and press
Enter.
c) _ Type copy running-config startup-config and press Enter.
17
The login banner will display immediately after the MOTD but before the
user-mode password prompt. Remember that you set your user-mode
passwords by setting the console, auxiliary, and VTY line passwords.
You can remove the login banner by typing
o config t
o no banner login
10. You can add an IP address to an interface with the ip address command.
You need to get into interface configuration mode first; here is an example
of how you do that:
o config t
o int e0 (you can use int Ethernet 0 too)
o ip address 1.1.1.1 255.255.0.0
o no shutdown
Notice that the IP address (1.1.1.1) and subnet mask (255.255.0.0) are
configured on oneline. The no shutdown (or no shut for short) command is
used to enable the interface. All interfaces are shut down by default.
18
6. If you wanted to set the enable secret password to cisco, what would you
type?
7. If you wanted to see if a serial interface needed to provide clocking,
what command would you use?
8. What command would you use to see the terminal history size?
9. What old Cisco command will change a configuration stored on a TFTP
host?
10. How would you set the name of a router to Chicago?
19
Lab #07
Equipment:
Router 2621 three
Console cable
DTE and DCE connector cable
Personal computers
Cross cable
Network design:
Router configuration is really a pretty straightforward process, since you just need to
add IP addresses to your interfaces and then perform a no shutdown on those
interfaces. It will get a tad more complex later on, but first let’s configure the IP
addresses in the network.
20
Lab_A Configuration
To configure the Lab_A router, you just need to add an IP address to interface
FastEthernet 0/0as well as the serial 0/0. Configuring the hostnames of each router
will make identification easier.And why not set the interface descriptions, banner, and
router passwords, too? You really shouldget in the habit of configuring these
commands on every router.Here is how I did all that:
Router>en
Router#config t
Router(config)#hostname Lab_A
Lab_A(config)#enable secret todd
Lab_A(config)#interface fa0/0
Lab_A(config-if)#ip address 192.168.10.1 255.255.255.0
Lab_A(config-if)#description Lab_A LAN Connection
Lab_A(config-if)#no shut
Lab_A(config-if)#interface serial 0/0
Lab_A(config-if)#ip address 192.168.20.1 255.255.255.0
Lab_A(config-if)#description WAN Connection to Lab_B
Lab_A(config-if)#no shut
Lab_A(config-if)#exit
Lab_A(config)#line console 0
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#line aux 0
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#line vty 0 4
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#exit
Lab_A(config)#banner motd #
This is the Lab_A router
#
Lab_A(config)#ip route 192.168.30.0 255.255.255.0
192.168.20.2
Lab_A(config)#ip route 192.168.40.0 255.255.255.0
192.168.20.2
Lab_A(config)#ip route 192.168.50.0 255.255.255.0
192.168.20.2
Lab_A(config)#^z
Lab_A#copy running-config startup-config
Destination filename [startup-config]? [Enter]
Lab_A#
21
Lab_B Configuration
It’s now time to configure the next router. To configure Lab_B, we have three
interfaces to deal with: Fast Ethernet 0/0, serial 0/0, and serial 0/1. Both serial
interfaces are DCE. What that means to us is that we’ll have to add the clock rate
command to each interface.
Router>en
Router#config t
Router(config)#hostname Lab_B
Lab_B(config)#enable secret todd
Lab_B(config)#interface fa0/0
Lab_B(config-if)#ip address 192.168.30.1 255.255.255.0
Lab_B(config-if)#description Lab_B LAN Connection
Lab_B(config-if)#no shut
Lab_B(config-if)#interface serial 0/0
Lab_B(config-if)#ip address 192.168.20.2 255.255.255.0
Lab_B(config-if)#description WAN Connection to Lab_A
Lab_B(config-if)#clock rate 64000
Lab_B(config-if)#no shut
Lab_B(config-if)#interface serial 0/1
Lab_B(config-if)#ip address 192.168.40.1 255.255.255.0
Lab_B(config-if)#description WAN Connection to Lab_C
Lab_B(config-if)#clock rate 64000
Lab_B(config-if)#no shut
Lab_B(config-if)#exit
Lab_B(config)#line console 0
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#line aux 0
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#line vty 0 4
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#exit
Lab_B(config)#banner motd #
This is the Lab_B router
#
Lab_B(config)#ip route 192.168.10.0 255.255.255.0
192.168.20.1
Lab_B(config)#ip route 192.168.50.0 255.255.255.0
192.168.40.2
Lab_B(config)#^z
Lab_B#copy running-config startup-config
Destination filename [startup-config]? [Enter]
22
Lab_C Configuration
The configuration of Lab_C is similar to the other two routers (make sure we
remember to addpasswords, interface descriptions, and a banner to the router
configuration):
Router>en
Router#config t
Router(config)#hostname Lab_C
Lab_C(config)#enable secret todd
Lab_C(config)#interface fa0/0
Lab_C(config-if)#ip address 192.168.50.1 255.255.255.0
Lab_C(config-if)#description Lab_C LAN Connection
Lab_C(config-if)#no shut
Lab_C(config-if)#interface serial 0/0
Lab_C(config-if)#ip address 192.168.40.2 255.255.255.0
Lab_C(config-if)#description WAN Connection to Lab_B
Lab_C(config-if)#no shut
Lab_C(config-if)#exit
Lab_C(config)#line console 0
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#line aux 0
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#line vty 0 4
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#exit
Lab_C(config)#banner motd #
This is the Lab_C router
#
Lab_C(config)#ip route 192.168.30.0 255.255.255.0
192.168.40.1
Lab_C(config)#ip route 192.168.20.0 255.255.255.0
192.16.40.1
Lab_C(config)#ip route 192.168.10.0 255.255.255.0
192.168.40.1
Lab_C(config)# ^z
Lab_C#copy running-config startup-config
Destination filename [startup-config]? [Enter]
Lab_C#
23
Lab #8
Lab Objective: Design the network using Static Routing (Boson Net
Simulator)
Equipment:
Boson Net simulator version 6
Network design:
Router configuration is really a pretty straightforward process, since you just need to
add IP addresses to your interfaces and then perform a no shutdown on those
interfaces. It will get a tad more complex later on, but first let’s configure the IP
addresses in the network.
24
Boson Network Designer
We select router of 2600 series model 2621. Connect three of them through serial
ports and Router is DCE and router 1 and 2 are DTE. After designing this we save this
design and load into Boson network Simulator. Then configure them.
25
Configure Router 1 (Lab_A)
26
Configure Router 2 (Lab_B)
27
Configure Router 3 ( Lab_C)
28
Testing the network using PING Command
29
Ping the other routers from router 3 (Lab C)
30
Lab #09
Equipment:
Router 2621 three
Console cable
DTE and DCE connector cable
Personal computers
Cross cable
Network design:
Router configuration is really a pretty straightforward process, since you just need to
add IP addresses to your interfaces and then perform a no shutdown on those
interfaces. It will get a tad more complex later on, but first let’s configure the IP
addresses in the network.
31
Lab_A Configuration
To configure the Lab_A router, you just need to add an IP address to interface
FastEthernet 0/0as well as the serial 0/0. Configuring the hostnames of each router
will make identification easier.And why not set the interface descriptions, banner, and
router passwords, too? You really shouldget in the habit of configuring these
commands on every router.Here is how I did all that:
Router>en
Router#config t
Router(config)#hostname Lab_A
Lab_A(config)#enable password ucet
Lab_A(config)#interface fa0/0
Lab_A(config-if)#ip address 192.168.10.1 255.255.255.0
Lab_A(config-if)#description Lab_A LAN Connection
Lab_A(config-if)#no shut
Lab_A(config-if)#interface serial 0/0
Lab_A(config-if)#ip address 192.168.20.1 255.255.255.0
Lab_A(config-if)#description WAN Connection to Lab_B
Lab_B(config-if)#encapsulation ppp
Lab_A(config-if)#no shut
Lab_A(config-if)#exit
Lab_A(config)#line console 0
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#line aux 0
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#line vty 0 4
Lab_A(config-line)#password ucet
Lab_A(config-line)#login
Lab_A(config-line)#exit
Lab_A(config)#banner motd #
This is the Lab_A router
#
Lab_A(config)#router rip
Lab_A(config-router)#network 192.168.10.0
Lab_A(config-router)#network 192.168.20.0
Lab_A(config-router)#^Z
Lab_A#
Lab_A#copy running-config startup-config
Destination filename [startup-config]? [Enter]
Lab_A#
32
Lab_B Configuration
It’s now time to configure the next router. To configure Lab_B, we have three
interfaces to deal with: Fast Ethernet 0/0, serial 0/0, and serial 0/1. Both serial
interfaces are DCE. What that means to us is that we’ll have to add the clock rate
command to each interface.
Router>en
Router#config t
Router(config)#hostname Lab_B
Lab_B(config)#enable password ucet
Lab_B(config)#interface fa0/0
Lab_B(config-if)#ip address 192.168.30.1 255.255.255.0
Lab_B(config-if)#description Lab_B LAN Connection
Lab_B(config-if)#no shut
Lab_B(config-if)#interface serial 0/0
Lab_B(config-if)#ip address 192.168.20.2 255.255.255.0
Lab_B(config-if)#description WAN Connection to Lab_A
Lab_B(config-if)#clock rate 64000
Lab_B(config-if)#no shut
Lab_B(config-if)#encapsulation ppp
Lab_B(config-if)#interface serial 0/1
Lab_B(config-if)#ip address 192.168.40.1 255.255.255.0
Lab_B(config-if)#description WAN Connection to Lab_C
Lab_B(config-if)#clock rate 64000
Lab_B(config-if)#encapsulation ppp
Lab_B(config-if)#no shut
Lab_B(config-if)#exit
Lab_B(config)#line console 0
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#line aux 0
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#line vty 0 4
Lab_B(config-line)#password ucet
Lab_B(config-line)#login
Lab_B(config-line)#exit
Lab_B(config)#banner motd #
This is the Lab_B router
#
Lab_B(config)#router rip
Lab_B(config-router)#network 192.168.20.0
Lab_B(config-router)#network 192.168.30.0
Lab_B(config-router)#network 192.168.40.0
Lab_B(config-router)#^Z
33
Lab_B#
Lab_B#copy running-config startup-config
Destination filename [startup-config]? [Enter]
Lab_B#
Lab_C Configuration
The configuration of Lab_C is similar to the other two routers (make sure we
remember to add passwords, interface descriptions, and a banner to the router
configuration):
Router>en
Router#config t
Router(config)#hostname Lab_C
Lab_C(config)#enable password ucet
Lab_C(config)#interface fa0/0
Lab_C(config-if)#ip address 192.168.50.1 255.255.255.0
Lab_C(config-if)#description Lab_C LAN Connection
Lab_C(config-if)#no shut
Lab_C(config-if)#interface serial 0/0
Lab_C(config-if)#ip address 192.168.40.2 255.255.255.0
Lab_C(config-if)#description WAN Connection to Lab_B
Lab_B(config-if)#encapsulation ppp
Lab_C(config-if)#no shut
Lab_C(config-if)#exit
Lab_C(config)#line console 0
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#line aux 0
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#line vty 0 4
Lab_C(config-line)#password ucet
Lab_C(config-line)#login
Lab_C(config-line)#exit
Lab_C(config)#banner motd #
This is the Lab_C router
#
Lab_C(config)#router rip
Lab_C(config-router)#network 192.168.40.0
Lab_C(config-router)#network 192.168.50.0
Lab_C(config-router)#^Z
Lab_C#
Lab_C#copy running-config startup-config
Destination filename [startup-config]? [Enter]
Lab_C#
34
Lab # 10
Equipment:
Boson Network Simulator version 6
Network design:
Router configuration is really a pretty straightforward process, since you just need to
add IP addresses to your interfaces and then perform a no shutdown on those
interfaces. It will get a tad more complex later on, but first let’s configure the IP
addresses in the network.
35
Boson Network Designer
We select routers of 2600 series, model 2621. Connect three of them through serial
ports and Router 2 is DCE and Router 1 and 2 are DTE. After designing this we save
this design and load into Boson network Simulator. Then configure them.
36
Configure Router 1 (Lab_A)
37
Configure Router 2 (Lab_B)
38
Configure Router 3 ( Lab_C)
39
Testing the Network using PING & TELNET commands
from router 1 (Lab A)
40
From Router 2 ( Lab_B)
41
From Router 3 (Lab_3)
42
Lab #09
Equipment:
Router 2621 three
Console cable
DTE and DCE connector cable
Personal computers
Cross cable
Network design:
In this lab the scenario and Networks addressing is same as in previous lab. But from
the three classes of Dynamic Routing Protocols we are focusing at Distance Vector in
which two protocols are involved RIP (Routing Information Protocol) and (Interior
Gateway Routing Protocol).
43
Configuring RIP Routing
Lab_A
Lab_A(config)#router rip
Lab_A(config-router)#network 192.168.10.0
Lab_A(config-router)#network 192.168.20.0
Lab_A(config-router)#^Z
Lab_A#
Lab_B
Lab_B(config)#router rip
Lab_B(config-router)#network 192.168.20.0
Lab_B(config-router)#network 192.168.30.0
Lab_B(config-router)#network 192.168.40.0
Lab_B(config-router)#^Z
Lab_B#
Lab_C
Lab_C#config t
Enter configuration commands, one per line. End with CNTL/Z.
Lab_C(config)#no ip route 0.0.0.0 0.0.0.0 192.168.40.1
Lab_C(config)#router rip
Lab_C(config-router)#network 192.168.40.0
Lab_C(config-router)#network 192.168.50.0
Lab_C(config-router)#^Z
Lab_C#
Lab_B
To configure the Lab_B router, all you need to do is turn on IGRP routing
using AS 10 and then
add the network numbers, as shown next:
Lab_B#config t
44
Enter configuration commands, one per line. End with CNTL/Z.
Lab_B(config)#router igrp 10
Lab_B(config-router)#netw 192.168.20.0
Lab_B(config-router)#netw 192.168.30.0
Lab_B(config-router)#netw 192.168.40.0
Lab_B(config-router)#^Z
Lab_B#
Lab_C
To configure Lab_C, once again you need to turn on IGRP using AS 10:
Lab_C#config t
Enter configuration commands, one per line. End with CNTL/Z.
Lab_C(config)#router igrp 10
Lab_C(config-router)#netw 192.168.40.0
Lab_C(config-router)#netw 192.168.50.0
Lab_C(config-router)#^Z
Lab_C#
The show protocols command is useful because it displays all the routed
protocols and the interfaces upon which the protocol is enabled.
The following output shows the IP address of the FastEthernet 0/0, serial
0/0, and serial 0/1 interfaces of the Lab_B router:
The show ip protocols command shows you the routing protocols that
are configured on
your router. Looking at the output below, you can see that both RIP and
IGRP are still running on the router, but that only IGRP appears in the
routing table because of its lower administrative distance (AD).
45
Lab #10
Theory:
This particular model comes with 24 built-in 10/100 ports using RJ-45 connectors.
Any of the ports can be used to connect to end-user devices or to other switches. This
switch also includes two Gigabit Ethernet slots, on the right side of the figure, into
which you can put the appropriate Gigabit Interface Converter (GBIC).
Switch commands refer to the physical RJ-45 Ethernet connectors on a 2950 as Each
interface has a number in the style x/y, where x and y are two different numbers. On a
2950, the number before the / is always 0. The first interface is numbered 0/1, the
second is 0/2, and so on.
46
Accessing the Cisco 2950 Switch CLI
The 2950 CLI works just like the router IOS CLI. Some of the commands you use are
different because switches perform different tasks than routers, but the process and the
look and feel are the same. For instance:
Only a few minor differences exist between 2950 switches and routers relating to how
to access the switch and use the CLI. The first difference is that there is no auxiliary
port on a switch. Figure shows the two basic access methods—console and Telnet.
Notice that the same console cable (rollover cable) is used for the switch as well as the
router. The only other big difference between the CLI in a router and a 2950 switch is
that the commands listed when you ask for help are different. The process is the
same—type a ? Whenever you need help, and commands and parameters are listed,
depending on where you are when you type the?.
47
Switch LEDs During POST
Power-On Self Test (POST) defines the series of steps that a device goes through to
test the hardware and find out what is working before moving on to loading the
operating system. POST processing is performed by boot code that is loaded into
ROM.During POST, the switch varies the lights on the LEDs to imply what is
happening.
48
Lab #11
Equipment:
Router 2621 three
Console cable
DTE and DCE connector cable
Personal computers
Cross cable
Switch 2950 two
Switch 1900 one
Theory:
In this lab, you’ll configure the three switches in the following graphic to work in the
internetworking environment. This lab will assume that you have at least one 2950
switch and a 1900 Enterprise Edition switch. If you have only 2950 at this time, that is
sufficient.
This lab will also assume that you have configured the internetworking lab in previous
labs that RIP or IGRP is running, and that all routers are up and communicating. We’ll
configure our switches with the following, based on the router configurations from the
previous labs:
• 1900A: IP address 192.168.10.10/24
• 2950B: (connected to Lab_B router) 192.168.30.10/24
• 2950C: (connected to Lab_C router) 192.168.50.10/24
We just want to provide basic administrative configuration on the switches and verify
their configuration. Let’s start by adding hostnames, passwords, banner, interface
description, and IP addresses to each switch.
49
Configuration:
1. The first switch we’ll configure is the 2950 connected to the Lab_C router:
Switch>en
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#hostname 2950C1900
2950C(config)#enable secret ucet
2950C(config)#line con 0
2950C(config-line)#login
2950C(config-line)#password ucet
2950C(config-line)#line vty 0 4
2950C(config-line)#login
2950C(config-line)#password ucet
2950C(config-line)#banner motd #
Enter TEXT message. End with the character '#'.
This is my 2950C switch
#
2950C(config)#int f0/1
2950C(config-if)#description Connection to router
2950C(config-if)#interface f0/4
2950C(config-if)#description Connection to 2950B
2950C(config-if)#int f0/5
2950C(config-if)#description 2nd connection to 2950B
2950C(config-if)#int vlan1
2950C(config-if)#ip address 192.168.50.10 255.255.255.0
2950C(config-if)#no shut
2950C(config-if)#exit
2950C(config)#ip default-gateway 192.168.50.1
2950C(config)#^Z
2950C#copy run start
Destination filename [startup-config]? (return)
Building configuration...
[OK]
2950C#
Switch>en
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#hostname 2950B
2950B(config)#enable secret ucet
2950B(config)#line con 0
2950B(config-line)#login
50
2950B(config-line)#password ucet
2950B(config-line)#line vty 0 4
2950B(config-line)#login
2950B(config-line)#password ucet
2950B(config-line)#banner motd #
Enter TEXT message. End with the character '#'.
This is my 2950B switch
#
2950B(config)#
2950B(config)#int f0/4
2950B(config-if)#desc connection to 2950C
2950B(config-if)#int f0/5
2950B(config-if)#desc 2nd connection to 2950C
2950B(config-if)#int vlan 1
2950B(config-if)#ip address 192.168.30.10 255.255.255.0
2950B(config-if)#no shut
2950B(config-if)#exit
2950B(config)#ip default-gateway 192.168.30.1
2950B(config)#exit
2950B#copy run start
Destination filename [startup-config]? (return)
Building configuration...
[OK]
2950B#
3. Now, let’s configure the 1900 switch connected to the Lab_A router:
>enable
#config t
(config)#enable password level 1 ucet
(config)#enable password level 15 ucet
(config)#enable secret ucet
(config)#hostname 1900A
1900A(config)#ip address 192.168.10.10 255.255.255.0
1900A(config)#ip default-gateway 192.168.10.1
1900A(config)#banner motd #
This is the 1900A switch
#
1900A(config)#int fa0/26
1900A(config-if)#desc Connection to Lab_A router
1900A(config-if)#^z
1900A#
51
Verifying the Switch Configurations
To verify the configurations, the show running-config command can be used on both
the1900 and 2950 Catalyst switches. However, to test that the switches are working in
the internetwork,Ping is a great tool to use.
1900A#ping 192.168.10.1
From the 1900 switch, ping the two 2950 switches:
1900A#ping 192.168.30.10
1900A#ping 192.168.50.10
From the 2950B switch, ping the 1900A switch and the 2950C switch:
2950B#ping 192.168.10.10
2950B#ping 192.168.50.10
From the 2950C switch, ping the 1900A switch and the 2950B switch:
2950C#ping 192.168.10.10
2950C#ping 192.168.30.10
52
Lab # 13
Equipment:
Boson Net Simulator version 1
Theory:
In this lab, you’ll configure the three switches in the following graphic to work in the
internetworking environment. This lab will assume that you have at least one 2950
switch and a 1900 Enterprise Edition switch. If you have only 2950 at this time, that is
sufficient.
This lab will also assume that you have configured the internetworking lab in previous
labs that RIP or IGRP is running, and that all routers are up and communicating. We’ll
configure our switches with the following, based on the router configurations from the
previous labs:
• 1900A: IP address 192.168.10.10/24
• 2950B: (connected to Lab_B router) 192.168.30.1/024
• 2950C: (connected to Lab_C router) 192.168.50.10/24
We just want to provide basic administrative configuration on the switches and verify
their configuration. Let’s start by adding hostnames, passwords, banner, interface
description, and IP addresses to each switch.
53
Boson Network Designer
54
Configure Router 1
55
Configure Router 2
56
Configure Router 3
57
Configure Switch A (1900)
58
Configure Switch C (2950)
Configure PC 1
59
Configure PC 2
Configure PC 3
Configure PC 4
Configure PC 5
60
Test the network using PING command
From PC 1
61