CCNA Practical Studies (Cisco Certification & Training)

Terminal Server Configuration

Configure the Cisco 2511 router to be the terminal server for this lab. The terminal server is connected to each device's console port (see Hint 1). Port assignments are as follows :

• R1 2001

• R2 2002

• R3 2003

• R4 2004

• R5 2005

• R6 2006

• Catalyst switch 2007

Cisco Catalyst Switch Configuration

• Configure the switch with a host name of Catswitch.

• Set the management console password to letmein.

• Assign the management console to an IP address of 192.168.1.4/24 and a default gateway of 192.168.1.10 (the terminal server).

• Configure ports 1 and 2 (refer to the diagram, if needed) to be in VLAN 1. Name the VLAN Vlan1.

• Configure port 3 for VLAN 2, and name the VLAN Vlan2.

• Configure port 4 for VLAN 3, name the VLAN Vlan3.

• Configure port 5 for VLAN 4, and name the VLAN Vlan4.

• Note: If you have a TFTP server, you will need to place that port into VLAN 3 for this lab.

Cisco Router Configuration

Configure all routers to have the following:

• A host name (that is, host names are to be according to the number r1, r2, r3, and so on).

• An enable secret password of allpower.

• An enable console login with password letmein.

• Telnet access (vty 0 4) password falcons.

• No DNS resolution (no domain name lookups).

• Configure all routers so that the console port will not time out your connection.

• Configure all routers so that messages from the router to the console screen will not be appended to the command line.

• Configure all routers to show a banner when you log into the router (from console port or Telnet). (In the banner, state which router you are logging into. As an example, on Router 1, the banner should read "This is router 1.")

• Create loopback interfaces on all routers. Use IP address 204.206. X. X /24 (where X is the router number). So, R1 would have a loopback address of 204.206.1.1/24, R2 would be 204.206.2.2/24, and so on.)

• Create a host table on all routers using the loopback addresses that you just created for each router.

IP Addressing Assignment

• Look at the network diagram for IP addressing assignments for each interface, and assign them to the appropriate interfaces. Don't forget to look at the netmasks !

• While configuring IP addresses on the interfaces, configure the data link layer (Frame Relay, if appropriatesee Hint 2) and place a description on each interface (except loopback interfaces) stating the router that they are connected to and which interface they are. Remove the interface from shutdown mode.

RIP

• Place R4's Ethernet 0, Serial 1, and Loopback 0 networks into RIP.

• Place R6's Serial 1, Token Ring 0, and Loopback 0 networks into RIP as well.

IGRP

• Place R2's Ethernet 0 and Ethernet 1 into IGRP AS 20.

• Configure R1 so that IGRP AS 20 propagates the networks from R1's Ethernet 0 and Loopback 0 interfaces.

EIGRP

• Place R2's Serial 0, R2's Loopback 0, R3's Serial 0, and R4's Serial 0 networks into EIGRP autonomous system 10.

• Place R3's Ethernet 0 network into EIGRP 10 (see Hint 3).

• Create two loopback interfaces on R3 with the following addresses:

  - loopback 1=210.210.1.3/24

  - loopback 2=210.210.2.3/24

• Add these two networks into the EIGRP routing domain, and configure R3 so that all other routers see only one route to these two addresses (see Hint 4).

Route Redistribution

• On R4, redistribute RIP into EIGRP and redistribute EIGRP into RIP. On R2, redistribute EIGRP into IGRP and redistribute IGRP into EIGRP (see Hint 5).

• Fix the problem of R6 and R1 not being capable of ping ing the two loopback addresses on R3 with either a default route or a default network statement.

ISDN DDR

• Configure the BRI interfaces on R5 and R6 with IP addresses. See Figure C-1 for IP address and ISDN information (switch type and dial numbers ).

• Use PPP encapsulation.

• Make sure that R5 is the only one to initiate a call.

• The ISDN link should be active when any IP traffic needs to cross the link. No routing protocols are to be used across the link. Use static routes, but make sure that R5 can ping all interfaces on all routers (See Hint 6).

IPX

• Configure R2's Serial 0, R3's Serial 0, and R4's Serial 0 with IPX network number 1000 (see Hint 7).

• Configure R3's Ethernet 0 for IPX network 3000

• Configure R4's Serial 1 and R6's Serial 1 for IPX network number 4600.

• Configure R4's Ethernet 0 for IPX network 4000.

• Configure a secondary IPX network number 4001 on R4's Ethernet 0. Make the encapsulation Novell SAP (see Hint 8).

• Configure R1's Ethernet 0 and R2's Ethernet 0 for IPX network 1200.

• Configure R6's To0 network number to be 6000.

IPX EIGRP

Use EIGRP as the routing protocol for the interfaces in the Frame-Relay cloud and R3's Ethernet 0 (see Hints 9, 10, and 11).

IPX RIP

Use IPX RIP for all other router interfaces that are not configured for IPX EIGRP.

Standard Access List

Create a standard outgoing access list and apply it on R4's Serial 0 to fulfill the following requirements:

• Deny access to users on network 192.168.111.32/27 to the Frame Relay network. (Assume that this network exists off R6. See Hint 12.)

Extended Access List

Create an extended incoming access list, and apply it on R3's Serial 0 to fulfill the following requirements:

• Deny http (www) requests from reaching R3's Ethernet 0 network, where several Web servers reside.

• Deny FTP traffic from reaching R3's E0 network.

• Permit anything else (see Hint 13).

Cisco Router Operations

• Cisco router IOS backup Back up the current Cisco IOS Software image on R3 to the TFTP server at 192.168.1.5.

• Cisco router IOS upgrade Upgrade the Cisco IOS Software on R3 to image c2500-js-l_112-17.bin on TFTP server 192.168.1.5.

• Cisco router configuration backup Back up the current configuration on R3 to the same TFTP server. Name your file r3-confg.

• Cisco router network configuration Suppose that your startup-config has become corrupted. Configure R3 from the TFTP server (use the filename that you just backed up).