Professional Documents
Culture Documents
Getting Started
To invoke the NetSim, double-click on the Boson NetSim icon on your PC screen.
If there is not an icon on the PC screen, you can start the NetSim by pressing Start ->
Boson NetSim -> Boson NetSim.
You will be presented with a screen that has buttons at the top representing each router,
switch, or PC that you will be configuring.
Press one of the buttons to configure a device. Some of the devices are hidden (Switch 3,
Switch 4, PC1, and PC2) and can be accessed
by pressing the More Devices button. There is also a button that can be pressed to show
the network topology that the labs are based on.
Lab Topology
The Lab Topology is shown in the diagram on the next page (it can also be viewed by
selecting the Topology button at the top of the NetSim screen).
You will have:
The LAN/WAN interfaces and subnet numbers are indicated on the diagram. Specific
interface IP addresses are included in a table on page 6.
LAB TOPOLOGY
There is also an optional IPX lab contained in Appendix A of this lab guide.
These labs build upon each other so the best approach is to follow the labs sequentially.
You will also be asked questions at various points during the lab. Answers to these
questions are contained in Appendix B at the back of this lab guide. Appendix C also
contains the completed configurations for selected labs.
To restore a configuration file, make sure you have pressed the appropriate
router/switch/PC button. The next step is to press File -> Load Device Config
(Overwrite) at the top of the screen and to select the correct saved configuration file.
The configuration will then be loaded.
Note: this process can take 15-20 seconds to complete and you will see configuration
commands flash across the screen. Be patient!
1. In this lab, you will get practice with basic configuration and show commands on the
Cisco router.
2. Select Router1 from the tool bar. Press enter to get to the user prompt
Router>
3. The greater-than symbol ( >) in the prompt indicates you are in user mode. Type ? to
see a list of commands that can be entered in user mode.
Router> ?
4. Type enable to get into privileged mode. The pound sign (#) indicates you are now in
privileged mode.
Router> enable
Router#
5. Type ? to see a list of commands that can be entered in privileged mode. Notice that
there are more commands available in
privileged mode than are available in user mode. Configure and reload are two such
commands that can only be issued in privileged mode.
Router# ?
Router# disable
Router>
7. Re-enter privileged mode and type configure terminal to get into configuration mode
Router> enable
Router# configure terminal
Router(config)#
8. Configure a hostname of ‘router1’ (without the quote marks). Notice how the prompt
changes.
9. In global configuration mode on router1, type enable ?. This will show valid
parameters that can be entered with the enable command.
Configure an enable password of ‘ccnalab’ that will not be encrypted when viewing the
router1(config)# enable ?
router1(config)# enable password ccnalab
router1(config)# enable secret cisco
10. Configure an IP address for the Ethernet0 interface on router1 (refer to the table on
page 6 for all IP addresses and masks).
Activate the interface – it is currently in ‘shutdown’ mode. You should see a message
that the interface has now come up.
Practice using the tab key – type int and then the tab key (no spaces). You should see the
word interface spelled out.
router1(config)# int<tab>
router1(config)# interface ethernet0
router1(config-if)# ip address 160.10.1.1 255.255.255.0
router1(config-if)# no shutdown
11. Configure an IP address for router1’s Serial0 interface (refer to the table for IP
addresses and masks) and activate the interface.
Practice using abbreviated commands for both interface serial0 and no shutdown.
router1(config-if)# int s0
router1(config-if)# ip address 175.10.1.1 255.255.255.0
router1(config-if)# no shut
12. Exit configuration mode by keying ctrl-z . This will bring you back to the privileged
mode prompt. You could also accomplish the same thing
by keying exit twice. The exit command moves you back one level
(from interface-configuration mode - global configuration mode - privileged mode
prompt).
router1(config-if)# ctrl-z
router1#
router1# logout
14. Press the enter key to get back into the user mode prompt and then type enable to get
into privileged mode. You will be prompted for the
enable secret password ‘cisco’ which you previously configured.
router1> enable
password: cisco
router1#
20. Now display the contents of NVRAM again. This time, you should see the active
configuration saved in NVRAM.
21. Issue the show version command and answer these questions:
a. Question: What IOS release is running on router1?
b. Question: What are the contents of the configuration register?
22. Issue the command to show which Layer 3 protocols are currently running on the
router.
a. Question: which protocols are currently running on the router?
23. Select router2 from the toolbar on top. Press enter and get into user mode. From
there go into privileged mode.
Router> enable
Router# configure terminal
Router(config)#
24. Configure a hostname of ‘router2’ and configure an enable secret password of ‘cisco’
for router2.
25. Configure an IP address for Fast Ethernet 0/0 on router2 and activate the interface
(see the diagram above for IP addresses and masks). Router2 is 2600 modular router and
must be configured using slot/port notation.
26. Display the summary status of all interfaces. Remember to get out of configuration
mode first before issuing any show commands.
a. Question: what status should interface Fa 0/0 show if it is fully activated?
b. Question: what status would Fa 0/0 show if it was in ‘shutdown’ mode?
router2(config-if)# ctrl-z
router2# show ip interface brief
1. In this lab you will practice using some advanced configuration and show commands
on the Cisco router. Please remember your lab 1 commands needed to switch
between Router modes (i.e. exit, end, disable)
2. On router1, configure a console password of ‘boson’. The console user must enter this
password before gaining access to the user mode prompt.
4. Test the banner and console password by logging out of the router and logging back
in. Get into enable mode after successfully logging into the console.
router1# logout
enter
password: boson
router1> enable
password: cisco
router1#
5. Configure a password of ‘cisco’ on router2 that will enable remote users to Telnet into
it:
6. On router1, associate a name of ‘router2’ with the remote IP address 160.10.1.2. This
will allow you to ping router2’s name rather than having to remember its IP address.
7. Verify that the name is in router1’s host table with the show hosts command.
10. Display the history table on router1. This shows the last 10 commands that were
entered on the router. You can recall commands by entering CTRL-P or by hitting the up
arrow key.
11. On router1, do a show interfaces on Serial 0. Note on the third line of the output that
the bandwidth is assumed to be 1544kb. This is because the router assumes all serial
links are T1’s unless you configure otherwise. Configure router1’s S0 link to have a
bandwidth of 64kb and then reenter the show interfaces command.
12. On router1, add a description to interface Serial 0 that says “Serial Link to Router3”.
This description will appear whenever you issue a show interfaces
command for Serial 0.
• configure hostnames
• configure an enable secret password of ‘cisco’
• assign IP addresses and subnet masks to serial & Ethernet interfaces (see table on
page 6)
• Remember to set the clock rate on the Router 3 Serial 1 interface.
• activate serial and Ethernet interfaces
• verify router3 can ping router1
• verify router3 can ping router4
• save the configurations to NVRAM
1. In this lab, you will practice using Cisco Discovery Protocol (CDP) commands to view
information about directly connected neighbors.
2. On router1, display summary information for router1’s CDP neighbors. You should
see one-line entries for both router2 and router3.
3. On router1, display detailed information about CDP neighbors. You can do this with
either the show cdp neighbors detail or show cdp entry * commands.
5. On router1, change the CDP advertisement interval to 50 sec. and the holdtime interval
to 170 sec.
Issue the show cdp interface command to verify the new timers are set correctly.
1. In this lab, you will practice Telnet’ing from one router to another. You will suspend
Telnet sessions using the ctrl-shift-6 X sequence and display active Telnet sessions using
the show sessions and show users commands.
2. From router1, Telnet to router2 (160.10.1.2). Once into router2, issue the show users
command. This command shows which remote users are Telnet’ed into this local router.
You should see router1’s IP address (160.10.1.1) as the user Telnet’ed into router2.
router2# ctrl-shift-6 x
router1#
router1# show sessions
4. Now Telnet from router1 to router3. Suspend the session and return to router1. Issue
the show sessions command. You should now see two suspended sessions: one to
router2 (160.10.1.2) and one to router3 (175.10.1.2).
5. Disconnect the two suspended sessions on router1. The number used in the disconnect
command comes from the
left-most column in the show sessions output. Issue show sessions to see if the
suspended Telnet sessions have disappeared.
router1# disconnect 2
router1# disconnect 1
router1# show sessions
1. In this lab, you are going to configure PC1 as a TFTP-Server. You will then backup
and restore router4’s configuration to the TFTP-Server.
2. Under the NetSim, select PC1 from the Other Devices drop-down menu. Configure
PC1 to have an IP address of 195.10.1.2 with a mask of 255.255.255.0 and a default-
gateway of 195.10.1.1. Use the winipcfg utility on the PC to do this. The PC is
automatically enabled to be a TFTP server.
c:> winipcfg
5. On the tftp-server (PC1), issue the show tftp-configs command to see if router4’s
configuration was successfully backed up (this is not a standard PC command, but one
developed for use with the NetSim).
6. You will now restore the configuration you saved on the TFTP server to NVRAM on
router4. Make sure router4’s NVRAM is currently empty by issuing the show startup-
config command. If it is not empty, use the erase startup-config command to clear it.
Restore the configuration from the tftp-server to NVRAM on router4 with the following
copy command (enter the PC’s IP address and previously-saved file name when
prompted):
7. Issue the show startup-config command. You should now see the restored
configuration file in NVRAM.
a. Question: was it necessary to clear out router4’s NVRAM in order to copy a file into
it? Why?
1. In this lab, you will be configuring RIP. On router1, router2, router3, and router4,
configure RIP V1 on all serial and Ethernet interfaces (except for the ISDN and frame
relay interfaces).
a. Question: On router1, why doesn’t the network statement under RIP specify
160.10.1.0 rather than 160.10.0.0?
2. On router1, issue the show ip protocols command. This commands shows information
about all dynamic routing protocols that are running on the router.
Based on the output of this command:
a. Question: how frequently does RIP advertise routing updates?
b. Question: what is the holddown timer interval for RIP?
3. On router4, issue the show ip route command. You should see two directly connected
routes (180.10.1.0 and 195.10.1.0) and three remote routes (160.10.0.0, 197.10.1.0 and
175.10.0.0).
a. What is the administrative distance for RIP?
4. On router4, ping both router1 and router2. The pings should succeed if RIP is
configured on all routers.
6. On router1, enter the debug ip rip command. This will show the periodic (every 30
seconds) RIP updates being transmitted and received on each interface.
7. After you examine a few debug updates, turn debugging off with the command
undebug all
1. In this lab, you will configure the IGRP routing protocol. Begin by turning off RIP on
router1, router2, router3, and router4. You can verify RIP is turned off by using the
command show ip protocols.
routerx(config)# no router rip
routerx# show ip protocols
2. Turn on IGRP on router1, router2, router3, and router4. Use AS# 200.
5. From router4, ping router1 and router2. These pings should succeed if IGRP is
configured on all the routers.
6. On router1, issue the debug ip igrp events and debug ip igrp transactions commands.
Both commands can be used to show periodic (every 90 seconds) IGRP routing updates
being sent and received by the router.
a. Question: what is the difference between the two debug ip igrp commands?
1. In this lab, you will configure the EIGRP routing protocol. Begin by turning off IGRP
on router1, router2, router3, and router4.
2. Configure EIGRP on router1, router2, router3, and router4. Use Autonomous System
number 100 and configure EIGRP to send and receive updates on all interfaces,
excluding the ISDN and Frame Relay interfaces.
5. On router1, display the statistics for EIGRP packet types sent and received.
9. On router1, enter the debug ip eigrp command to view EIGRP routing activity. (This
command is coming soon)
1. In this lab, you will configure the OSPF routing protocol. Begin by turning off EIGRP
on router1, router2, router3, and router4.
.
routerx(config)# no router eigrp 100
router4# sh ip protocols
7. From router4, ping router1 and router2. These pings should succeed if OSPF is
configured on all routers.
1. In this lab, you will configure basic IOS commands on the Catalyst 1900 switch.
2. From the NetSim tool bar, select Switch1 (Catalyst 1900). Press enter to get into the
user prompt mode. Enter enable to get into privileged mode.
Type ? to see a list of privileged mode commands. Enter disable to go back to user
mode.
enter
> enable
# ?
# disable
>
3. On switch1, go into privileged mode and then into global configuration mode. Assign
Switch1 a host name of 1900sw1. Use exit or ctrl-z to get out of configuration mode.
> enable
# configure terminal
(config)# hostname 1900sw1
1900sw1(config)# exit
1900sw1#
6. On switch1, get into privileged mode and then into global configuration. Reassign the
switch a hostname of 1900sw1 and an enable password of ‘cisco’. Assign the switch an
IP address of 195.10.1.99 with a subnet mask of 255.255.255.0. Assign the switch a
default gateway of 195.10.1.1 (router4’s Ethernet address).
> enable
# configure terminal
(config)# hostname 1900sw1
1900sw1(config)# enable password level 15 cisco
1900sw1(config)# ip address 195.10.1.99 255.255.255.0
1900sw1(config)# ip default-gateway 195.10.1.1
7. On switch1, issue the show ip command to verify that the IP address, mask, and default
gateway are correct.
9. From the NetSim tool bar, select Switch 2 (Catalyst 1900). Configure it with a
hostname of 1900sw2 and an enable password of cisco (the enable password should be
encrypted when displaying the configuration file). Assign an IP address of
195.10.1.100/24 and a default-gateway of 195.10.1.1
> enable
# configure terminal
(config)# hostname 1900sw2
1900sw2(config)# enable secret level 15 cisco
1900sw2(config)# ip address 195.10.1.100 255.255.255.0
1900sw2(config)# ip default-gateway 195.10.1.1
12. On switch1, issue the show mac-address-table command. This shows which devices
are attached to which switch ports.
13. On switch1, permanently assign a device with MAC address 1111-1111-1111 to port
E0/5. Issue the show mac-address-table command to verify the device is in the table as a
permanent entry.
1. In this lab, you will set up VLANs on the Catalyst 1900 switches and test them by
pinging between router4 and PC1. Router4 is connected to e0/1 on switch1 and PC1 is
connected to e0/1 on switch2. Switch1 and switch2 are interconnected through their
fa0/26 Fast Ethernet ports.
c:> winipcfg
3. Verify you can presently ping between PC1 and router4. If you cannot ping
successfully, check that router4’s Ethernet0 IP address is 195.10.1.1/24 and that the
interface is enabled. Also, using the winipcfg utility, check that the PC has a configured
IP address of 195.10.1.2/24.
4. On switch1 and switch2, issue the show vlan command. You should note that, by
default, all switch ports are in VLAN1. Because router4, PC1, and the switch-to-switch
link are all in VLAN1, should be able to ping between PC1 and router4.
5. On switch1 and switch2, set up a VTP domain called bigdomain. Verify it has been
created with the show vtp command.
a. Question: what VTP operating mode are the switches in?
6. On switch1 and switch2, create VLAN 10, calling it ccnavlan. Issue the show vlan
command to verify it was successfully created.
a. Question: do you see any ports connected to VLAN 10. If not, why not?
7. On switch1 and switch2, assign the e0/1 ports to the new VLAN you created. Router4
and PC1 are attached to these ports. Issue the show vlan command on both switches to
verify these ports have been moved to VLAN10. Also, issue the show vlan-membership
command. This is another command that shows VLAN assignments by port on the
1900.
8. Now that both router4 and PC1 are in VLAN10, try to ping from the PC1 to router4. It
should fail.
a. Question: if both devices are in the same VLAN, why should the pings fail?
9. Make the link between switch1 and switch2 a trunk line capable of carrying traffic for
any VLAN. Use the show trunk a command to verify trunking is enabled on port fa0/26
on both switches (it should say “Trunking: on”)
a. Question: what trunking protocol does the 1900 use – ISL or 802.1Q?
10. Now ping between PC1 and router4. The pings should succeed because both devices
are in the same VLAN and the inter-switch link is a trunk line capable of carrying traffic
for any VLAN.
1. In this lab, you will configure basic IOS commands on switch3 and switch4 which are
Catalyst 2950 switches.
2. From the NetSim tool bar, select Switch3 (Catalyst 2950). Press enter to get into the
user prompt mode.
Enter enable to get into privileged mode. Type ? to see a list of privileged mode
commands. Enter disable to go back to user mode.
enter
> enable
# ?
# disable
>
3. On switch3, go into privileged mode and then into global configuration mode. Assign
Switch3 a host name of 2950sw3. Use exit or ctrl-z to get out of configuration mode.
> enable
# configure terminal
(config)# hostname 2950sw3
2950sw3(config)# exit
2950sw3#
7. On switch3, go into privileged mode and then into global configuration mode.
Reassign the switch a hostname of 2950sw3 and an enable password of ‘cisco’
(unencrypted). Assign the switch an IP address of 197.10.1.99 with a subnet mask of
255.255.255.0. Assign the switch a default gateway of 197.10.1.1 (router3’s Ethernet
address).
8. On switch3, issue the show interface vlan1 command to verify that the IP address,
mask, and default gateway are correct.
10. From the NetSim tool bar, select Switch 4 (Catalyst 2950). Configure it with a
hostname of 2950sw4 and an enable password of cisco (the enable password should be
encrypted when displaying the configuration file). Assign an IP address of
197.10.1.100/24 and a default gateway of 197.10.1.1.
> enable
# configure terminal
(config)# hostname 2950sw4
2950sw4(config)# enable secret cisco
2950sw4(config)# interface vlan1
2950sw4(config-if)# ip address 197.10.1.100 255.255.255.0
2950sw4(config-if)# no shutdown
2950sw4(config-if)# exit
2950sw4(config)# ip default-gateway 197.10.1.1
12. On switch4, issue the show mac-address-table command. This shows which devices
are attached to which switch ports.
13. On switch4, permanently assign a device with MAC address 4444-4444-4444 to port
fa0/5. Issue the show mac-address-table command to verify the device is in the table as a
permanent entry.
14. On switch4, configure port security for port fa0/9. The switch will ‘sticky-learn’ the
MAC address of the device connected to port fa0/9 and will only allow that device to
connect to the port in the future.
1. In this lab, you will set up VLANs on switch3 and switch4 (Catalyst 2950
switches) and test them by pinging between router3 and PC2. Router3 is connected to
Fa0/1 on switch3 and PC2 is connected to Fa0/1 on switch4. Switch3 and switch4 are
interconnected through their fa0/12 Fast Ethernet ports.
c:> winipcfg
3. Verify you can presently ping between PC2 and router3. If you cannot ping
successfully, check that router3’s FastEthernet0 IP address is 197.10.1.1/24 and that the
interface is enabled. Also, using the winipcfg utility, check that PC2 has a configured IP
address of 197.10.1.2/24.
4. On switch3 and switch4, issue the show vlan command. You should note that, by
default, all switch ports are in VLAN1. Because router3, PC2, and the switch-to-switch
link are all in VLAN1, you should be able to ping between PC2 and router3.
5. On switch3 and switch4, set up a VTP domain called classroom. Verify it has been
created with the show vtp status command.
6. On switch3 and switch4, create VLAN 20, calling it 2950vlan. Issue the show vlan
command to verify it was successfully created.
a. Question: do you see any ports connected to VLAN 20. If not, why not?
7. On switch3 and switch4, assign the fa0/1 ports to the new VLAN you created. Router3
and PC2 are attached to these ports. Issue the show vlan command on both switches to
verify these ports have been moved to VLAN20.
8. Now that both router3 and PC2 are in VLAN20, try to ping from PC2 to router3. It
should fail.
a. Question: if both devices are in the same VLAN, why should the pings fail?
9. Make the link between switch3 and switch4 a trunk line capable of carrying traffic for
any VLAN.
Use the show interface fa0/12 switchport command to verify trunking is enabled on port
fa0/12 on both switches.
a. Question: what trunking protocol does the 2950 use – ISL or 802.1Q?
10. Now ping between PC2 and router3. The pings should succeed because both devices
are in the same VLAN
and the inter-switch link is a trunk line capable of carrying traffic for any VLAN.
1. In this lab, you will build standard and extended IP access-lists to filter traffic coming
inbound on router1’s serial0 interface.
2. Insure you can ping router2 (160.10.1.2) from both router3 and router4. The path to
router2 is through router1’s serial0 interface. If you cannot successfully ping router2,
check that IP addresses have been assigned, all interfaces are up, and that a dynamic
routing protocol (RIP, IGRP, EIGRP, or OSPF) is running on all routers.
3. On router1, build a standard IP access-list that permits traffic from subnet 175.10.1.0,
but blocks traffic from all other devices. Apply this access-list to router1’s serial0
interface for inbound traffic.
a. Question: is a ‘deny any’ statement required in the access-list?
b. Question: what does the mask 0.0.0.255 mean in the access-list?
c. Question: can any number be assigned to a standard IP access-list?
4. Test your access-list by ping’ing from router3 and router4 to router2. The pings from
router3 (in subnet 175.10.1.0)
should succeed while the pings from router4 (in subnet 180.10.1.0) should fail.
5. On router1, build an extended IP access-list that will allow Telnet traffic from host
175.10.1.2 (router3), and
ICMP traffic from host 180.10.1.2 (router4), but that will block everything else.
Remove the previous access-list and apply this new one to router1’s serial0 interface.
a. Question: what are two ways you can specify a host address in an extended IP access-
list?
b. Question: what is the number range for extended IP access-lists?
c. Question: how would you permit RIP routing updates?
6. Test access-list 100 by pinging and telneting from router3 & router4 to router2.
Router3 (175.10.1.2) should be able to telnet to router2, but not ping to it. Router4
(180.10.1.2) should be able to ping to router2, but not telnet to it.
1. In this lab, you will configure NAT/PAT function on router1. You will configure three
forms of translation: static network address translation, dynamic translation, and
overloading (port address translation). Remember to disable the access lists your
configured in the previous lab before continuing this lab.
3. Test the static NAT translation by telnet’ing from router2 to router3. Once into
router3, issue the show users command. The output of this command should show that
169.10.1.2 (the translated IP address) is the logged-in device.
4. Display the NAT Translation table on router1. The output of the display should show
that the inside local IP address (160.10.1.2) is translated to the inside global IP address
(169.10.1.2).
a. Question: does the “inside global IP address” normally represent a public or a private
IP address?
5. On router1, remove the previous static NAT commands and configure NAT to
translate router2’s Ethernet address to a dynamically assigned address. You will utilize a
pool of public addresses in the range of 169.10.1.50 to 169.10.1.100.
a. Question: if the pool of dynamically assigned addresses only contains one IP address
entry, what’s another term for this form of NAT translation?
6. Test the dynamic NAT translation function by telneting from router2 to router3. Once
into router3, issue the show users command. The output of this command should show
7. Remove the previous NAT commands. Configure NAT overloading (port address
translation) on router1 to translate router2’s Ethernet address
(160.10.1.2) to the serial0 interface address (175.10.1.1) on router1.
8. Test the overloading (PAT) function by Telnet’ing from router2 to router3. Issue the
show users command on router3. It should show that the logged-in device is 175.10.1.1
(the translated IP address). Also, issue the show ip nat translations command on router1
to display the NAT translation table.
1. In this lab, you will configure PPP and CHAP authentication on a serial interface. On
router1, issue the show interfaces serial 0 command. Note the encapsulation type of
HDLC which is the default for serial links.
2. On router1 and router3, configure PPP encapsulation for interface S0. Note that the
link will not come up unless both ends are configured with the same encapsulation type.
3. On router1 and router3, issue the show interfaces serial 0 command to verify that PPP
is configured for the link. The output should show the PPP LCP phase as ‘Open’ from
router1, ping router3 to verify the link is operational.
4. Configure PPP CHAP authentication for the S0 link on router1 and router3. Use the
password of ‘cisco’.
5. On router1 and router3, issue the show interfaces serial0 command to verify the link is
‘up and up’. Ping from router1 to router3 across the link.
ISDN Parameters
1. Configure ISDN between router1 and router2 using Legacy Dial on Demand Routing.
Legacy DDR means all ISDN parameters are configured under the BRI/PRI interface and
not under a dialer interface. Any IP packet should represent ‘interesting traffic’ and
either router should be able to initiate the call. PPP encapsulation and CHAP
authentication should be used. Refer to the table above for ISDN switch-type, IP
addresses, subnet masks, and telephone numbers.
2. Issue the show isdn status command on both router1 and router2. You should see:
Layer1: Active
Layer2: Multiple Frame Established with spid1 valid.
3. Issue the show interfaces bri0 command on router1. This displays the signaling or D
Channel. It should show ‘Up and Up (spoofing)’ if it is ready to handle a call request.
4. From router1, ping the ISDN interface of router2. This should cause an ISDN call to
be initiated and the pings should succeed.
a. Question: which configuration parameter(s) on router1 identifies the interesting traffic
that will trigger a call?
ISDN Parameters
1. In this lab, you will configure ISDN BRI on router1 and router2 using dialer profiles.
With dialer profiles, you are effectively moving some of the logical ISDN parameters
from the physical BRI/PRI interface to a dialer interface. Any IP packet should
represent ‘interesting traffic’ in this lab and either router should be able to initiate the
call. PPP encapsulation and CHAP authentication should be used. Refer to the table
above for ISDN switch-type, IP addresses, subnet masks, and telephone numbers.
Layer1: Active
Layer2: Multiple Frame Established with spid1 valid.
3. Issue the show interfaces bri0 command on router1. This displays the signaling or D
Channel. It should show ‘Up and Up (spoofing)’ if it is ready to handle a call request.
Now issue the command show interfaces bri0 1 2. This should show the status of the two
data, or B channels.
4. From router1, ping the ISDN interface of router2. This should cause an ISDN call to
be initiated and the pings should succeed.
6. Issue the show isdn status command on router1. Under the Layer 3 status in the
output, it should show one call active.
7. Issue the show interfaces bri0 1 2 command on router1. This shows the status of the B
channels (data channels). One of the B channels should have a status of ‘UP and UP’
indicating a successful call is in progress.
1. In this lab, you will configure ISDN BRI on router1 and ISDN PRI on router2 using
dialer profiles. Router2 has a primary rate ISDN interface (S0/0) as well as a basic rate
ISDN interface. Any IP packet should represent ‘interesting traffic’ in this lab and either
router should be able to initiate the call. PPP encapsulation and CHAP authentication
should be used. Refer to the table above for ISDN switch-type, IP addresses, subnet
masks, and telephone numbers.
a. Question: if this PRI was being configured in Europe, what would the options be for
controller type, framing, and linecode?
b. Question: On the PRI interface statement, what is the significance of: 23
2. Issue the show isdn status command on both router1 and router2. You should see:
Layer1: Active
Layer2: Multiple Frame Established
3. From router1, ping the ISDN interface of router2. This should cause an ISDN call to
be initiated and the pings should succeed.
4. Issue the show isdn status command on router1. Under the Layer 3 status in the
output, it should show one call active.
5. Issue the show interfaces bri0 1 2 command on router1. This shows the status of the
B channels (data channels). One of the B channels should
have a status of ‘UP and UP’ indicating a successful call is in progress.
1. In this lab, you will set up frame relay PVC’s between router1 and router5 using both
physical interfaces and point-to-point sub interfaces. Both routers will be frame relay
DTE devices connected to a frame relay cloud.
2. Using physical interfaces (no sub interfaces), configure frame relay on router1’s serial1
interface and router5’s serial0 interface. Refer to the chart above for IP addresses and
local DLCI’s. Both routers will use ANSI as their lmi-type. Frame relay map statements
should be used for static mapping.
a. Question: what is the default lmi-type on Cisco routers?
3. Issue the show interfaces serial x command on both router1 and router5. This will
show if the routers are successfully connected to their local frame relay switches. The
status on the first line should be ‘up and line protocol is up’. On the fifth line of output,
you should also see ‘DTE LMI up’. The encapsulation type should be frame relay.
4. Issue the show frame-relay map command on router1 and router5. This will show the
mapping of local DLCI’s to remote IP addresses.
5. Issue the show frame-relay pvc command on router1 and router5. This will show the
status of the PVC’s connected to the routers. You want to
see a status of ‘active’ which indicates the PVC is operational end-to-end.
7. Ping router1 from router5 to verify the frame-relay connection is working correctly.
8. You will now create point-to-point sub interfaces on router1 and router5.
You will use the same IP addresses and local DLCI’s as in the previous exercise.
It will be necessary to remove the IP addresses and frame map statements from the
physical interfaces prior to configuring the sub interfaces.
9. On both router1 and router5, issue the show ip interface brief command to insure the
physical interfaces and sub interfaces are active (status = up and up). Issue a show frame
relay pvc command on both routers to insure the PVC with DLCI 105 on router1 and
DLCI 501 on router5 is active.
1. Configure IPX routing on all LAN/WAN interfaces on router1, router2, router3, and
router4 (excluding ISDN and frame-relay interfaces).
Refer to the table above for IPX network numbers and encapsulation types.
2. On router1, issue the show protocols command. This should show IPX routing is
enabled.
4. On router2, issue the show ipx route command. You should see one directly connected
network (designated by a ‘C’ in the left column) and four remote IPX networks
(designated by an ‘R’ in the left column).
5. From router2, do a ping ipx to router3’s S0 interface and router4’s E0 interface. This
will demonstrate that there is connectivity across the IPX network.
9a. Question: When both encrypted and unencrypted enable passwords are configured,
which one is used?
• Answer: The enable secret (encrypted) password is used and the enable password is
ignored.
26a. Question: what status should interface E0/0 show if it is fully activated?
• Answer: ‘Ethernet is up and Line Protocol is Up’
b. Question: what status would E0/0 show if it was in ‘shutdown’ mode?
• Answer: ‘Administratively Down’
27a. Question: Were you successful? If not what commands should you use for
trouble-shooting?
• Answer: If you cannot successfully ping router1, you should use:
1. show interfaces: to verify the interface(s) are up
2. show run: to verify the IP addresses and subnet masks are correct
9a. Question: what is the name of the IOS image in flash and how large is it?
• Answer: c2500-js-mz.121-9.T.bin; 5.88MB
LAB 3 – CDP
LAB 5 – TFTP
7a. Question: was it necessary to clear out router4’s NVRAM in order to copy a file
into it? Why?
• Answer: No. When you copy a file into NVRAM, it will overwrite completely what’s
in there. When you copy a file into DRAM (running-config),
however, it merges that file with what is already in there.
LAB 6 - RIP
1a. Question: On router1, why doesn’t the network statement under RIP specify
160.10.1.0 rather than 160.10.0.0?
• Answer: The network statement under both RIP and IGRP must specify a classful
network number (A, B, or C address). It cannot be a subnet.
160.10.1.0 is a subnet, not a classful address.
LAB 7 – IGRP
3a. Question: how frequently does IGRP send out routing updates?
• Answer: every 90 seconds.
b. Question: what is the holddown interval for IGRP?
• Answer: 280 seconds.
c. Question: what is the default hop count for IGRP?
• Answer: 100 (maximum of 100 routers along the path).
6a. Question: what is the difference between the two debug ip igrp commands?
• Answer: the debug ip igrp events command traces IGRP routing updates without
showing individual network numbers.
The debug ip igrp transactions command shows routing updates with individual network
numbers that are being advertised or received.
LAB 8 – EIGRP
7a. Question: what is the administrative distance for EIGRP? Answer: 90.
LAB 9 – OSPF
5a. Question: what is the OSPF cost for a 10Mbps Ethernet interface?
• Answer: the default cost is 10 which is calculated by dividing the speed of the interface
into 100,000,000.
The default cost can be overridden using the ip ospf cost interface-level command.
6a. Question: what is the administrative distance for OSPF? Answer: 110.
8a. Question: What is the Spanning Tree (802.1D) state of interface e0/1?
• Answer: it is in the ‘forwarding’ state.
b. Question: What is the duplex setting for interface e0/2?
• Answer: Half-duplex - 10baseT ports default to half-duplex.
11a. Question: what is the address of the root bridge? Answer: 000C.1835.8565
b. Question: what is the port cost of E0/1? Answer: 100.
c. Question: what is the maxage interval? Answer: 20 seconds
d. Question: what is the hello interval? Answer: 2 seconds
5a. Question: what VTP operating mode are the switches in?
• Answer: the Catalyst 1900 switch defaults to ‘server’ mode.
6a. Question: do you see any ports connected to VLAN 10. If not, why not?
• Answer: No. Although VLAN 10 has been created, no ports have been manually
assigned to it, as yet.
8a. Question: if both devices are in the same VLAN, why should the pings fail?
• Answer: The link connecting switch1 and switch2 is still in VLAN 1.
It must be configured to be in VLAN 10 or configured as a trunk line which, by
definition, is capable of supporting all VLANs.
9a. Question: what trunking protocol does the 1900 use – ISL or 802.1Q?
• Answer: ISL.
4a. Question: Do you need to issue copy running-config startup-config on the Catalyst
2950 to save the running configuration?
• Answer: Yes. The active configuration is not automatically saved to NVRAM on the
2950.
9a. Question: What is the Spanning Tree (802.1D) state of interface fa0/1?
• Answer: forwarding.
b. Question: What is the duplex setting for interface fa0/2?
• Answer: auto – 10//100 ports default to auto-negotiate on the 2950.
12a. Question: what is the address of the root bridge? Answer: 000C 1835 8565
b. Question: what is the port cost of fa0/1? Answer: 19
c. Question: what is the maxage interval? Answer: 20 seconds
d. Question: what is the hello interval? Answer: 2 seconds
6a. Question: do you see any ports connected to VLAN 20? If not, why not?
• Answer: No. Although VLAN 20 has been created, no ports have been manually
assigned to it, as yet.
8a. Question: if both devices are in the same VLAN, why should the pings fail?
• Answer: The link connecting switch3 and switch4 is still in VLAN 1.
It must be configured to be in VLAN 20 or configured as a trunk line which, by
definition, is capable of supporting all VLANs.
5a. Question: what are two ways you can specify a host address in an extended
IP access-list?
• Answer: You can specify ‘host 172.16.1.1’ or ‘172.16.1.1 0.0.0.0’.
b. Question: what is the number range for extended IP access-lists?
• Answer: 100-199 or 2000-2699..
c. Question: how would you permit RIP routing updates:
• Answer: access-list 100 permit udp any any eq 520 (RIP uses UDP port 520)
Lab 15 – NAT/PAT
4a. Question: does the “inside global IP address” normally represent a public or a
private IP address?
• Answer: the inside global IP address normally represents a public, or registered IP
address.
NAT/PAT translates the inside local IP address, which is usually a private IP address, to
an inside global IP address,
which is usually a registered IP address.
5a. Question: if the pool of dynamically assigned addresses only contains one IP
address entry, what’s another term for this form of NAT translation?
• Answer: this is also known as overloading or Port Address Translation (PAT). It is
possible to configure overloading by defining one or a few
IP addresses in the dynamic address pool. This is an alternative to pointing to a physical
interface in the PAT definitions.
1a. Question: if this PRI was being configured in Europe, what would the options be for
controller type, framing, and linecode?
• Answer: In Europe, the controller type is E1; the framing is either crc4 or no-crc4, and
the linecode is hdb3.
b. Question: On the PRI interface statement, what is the significance of :23?
• Answer: 23 represents the ISDN signaling channel on the PRI/T1 link. It is the 24th
time-slot on the T1 link.
2a. Question: what is the default lmi-type on Cisco routers? Answer: cisco.
3a. Question: for LAN interfaces, where does the host portion of the IPX address
come from?
• Answer: the host address is equivalent to the six-byte MAC address
b. Question: for serial interfaces, where does the host portion of the IPX address
come from by default?
• Answer: the host address is equivalent to the MAC address of the lowest-numbered
Ethernet interface.
6a. Question: what different Novell packet types does this command show
traffic statistics for?
• Answer: RIP, SAP, ECHO, WATCHDOG, EIGRP
Coming Soon!!!