CCNA-Manual-200-125 Final PDF

LAB MANUAL (Version 1.
0)
CCNA ROUTING & SWITCHING
(200-125)
From the Desk of Engr. Ahmed Saeed

Join Us on Facebook (My Cisco Center Group)
My Cisco Center (MCC) Block 6 PECHS Near Farhan Hotel
92-321-2418349 1
`
Copy Right
CCNA LAB MANUAL 200-125

Copyright @My Cisco Center
Published By
My Cisco Center, PECHS Block 6

Near Farhan hotel, Shahrah-e-Faisal Karachi.
Warning and Disclaimer,
This manual is designed to provide information about

CCNA (200-125). Every effort has been made to make this manual as
complete and accurate as possible, but no warranty of fitness is implied.
The information is provided on as basis and MCC shall have neither
liability nor responsibility to any person or entity with respect to any loss
or damage Arising from the information contained in this manual.
Authors
Engr. Fakhr Uddin Akbari
(Network Engineer)
My Cisco Center
Engr. Riaz Gul
(Network Engineer)
My Cisco Center
Reviewed and Approved By
Engr. Ahmed Saeed

Lead Cisco Trainer
My Cisco Center (MCC)
Engrahmed23@gmail.com
92-321-2418349
Join us on Facebook (My Cisco Center Group)
https://www.facebook.com/groups/pixcttc/
OR Visit us on our website
www.myciscocenter.com

92-321-2418349 2
`
TABLE OF CONTENTS
Basic Configurations of Internetwork Operating System (IOS)
Configuring Telnet and SSH on Cisco Routers
Cisco Routers Password Recovery
Implementing Virtual Local Area Networks (VLANs)
Implementing VLAN Trunking Protocol Version 2 (VTP)
Implementing Port Based Security on Cisco Switches
Implementing IEEE (802.1d) STP and (802.1w) RSTP
Implementing Link Aggregation (Ether-Channel)
Implementing Inter-Vlan Routing using Router on a Stick
Configuring Static Route on Cisco Routers
Configuring Routing Information Protocol Version 2
Implementing Enhance Interior Gateway Routing Protocol (EIGRP)
Implementing Open Shortest Path First (OSPF) Version 2
Implementing IPv6 on Cisco Routers
Configuring IPV6 Stateless Auto Configuration

92-321-2418349 3
`
Implementing RIPng on Cisco Routers
Implementing EIGRP for IPV6 Networks
Configuring DHCP on Cisco Routers
Implementing Standard and Extended Access Control List (ACL)
Implementing Network Address Translation (Static, Dynamic and
PAT) Implementing Hot standby Routing Protocol (HSRP)
Implementation of WAN Encapsulation
TFTP Server
FTP
Configuring Syslog Server
PPP Multilink
GRE Tunnel

92-321-2418349 4
`
Basic Configurations of Internetwork Operating System (IOS)
OBJECTIVE: Basic configurations of a Cisco Switch/Router.

Accessing Console of the Switch/Router
Modes of CLI

How to Set Hostname and Configure Console Password

How to Set Privilege level password

How to Set User Authentication in Switch
TOPOLOGY

MCC-PC1 is directly connected to switch with IP address 10.0.0.1

MCC-PC2 is directly connected to switch with IP address 10.0.0.2

In order to configure the Switch/Router, accessing the console

92-321-2418349 5
`

adapter is used on the PC (COM port) to the device console Port through a roll-
RJ-45 to DB-9
over cable.

Hyper Terminal is used to access the Command Line Interface (CLI) of the Device.
In packet tracer:

92-321-2418349 6
`
Once you click OK, you will have Switch/Router Console.

Switch console:
Modes of CLI:
Switch> User-exec mode

Switch# Privilege mode
Switch(config)# Global Configuration mode

92-321-2418349 7
`
How to switch in different modes:
Switch> enable
Switch# config terminal
Switch (config)#
NOTE: To return to the previous mode use Exit command in the current mode .
How to Set Hostname and Configure Console Password:
Switch(config)# hostname MY_CISCO_CENTER

MY_CISCO_CENTER (config)#line console 0
MY_CISCO_CENTER (config-line)#password cisco123
MY_CISCO_CENTER (config-line)#login
How to Set Privilege level password:
!!! Clear Text Password not encrypted(less priority)

MY_CISCO_CENTER (config)#enable password ccna123
!!! Encrypted password (more Priority)
MY_CISCO_CENTER (config)#enable secret cttc123
Verify the Password:
MY_CISCO_CENTER (config)#exit
MY_CISCO_CENTER #exit
MY_CISCO_CENTER console 0 is now available
Press RETURN to get started.

User Access Verification
!!! TYPE HERE LINE CONSOLE
Password Password:
MY_CISCO_CENTER >enable
!!! TYPE HERE Privilege Level Password
Password:

92-321-2418349 8
`
Verification:
How to Set User Authentication in Switch:
MY_CISCO_CENTER #config terminal

MY_CISCO_CENTER (config)#line console 0
MY_CISCO_CENTER (config-line)# login
MY_CISCO_CENTER (config-line)#exit
MY_CISCO_CENTER (config)#username MCC password cisco123

MY_CISCO_CENTER (config)#exit
MY_CISCO_CENTER #exit
Verify the Authentication

92-321-2418349 9
`
Configuring Telnet and SSH on Cisco Routers
OBJECTIVE: Configuring the Cisco Router/Switch for remote access.

TOPOLOGY
How to Set Telnet password:
MY_CISCO_CENTER(config)#line vty 0 15
MY_CISCO_CENTER (config-line)#password cisco
MY_CISCO_CENTER (config-line)#login
MY_CISCO_CENTER (config-line)#exit
How to Enable The Device to Establish Telnet/SSH Session:
MY_CISCO_CENTER (config)#interface vlan 1

MY_CISCO_CENTER (config-if)#ip address 192.168.1.1 255.255.255.0
MY_CISCO_CENTER (config-if)#no shutdown
NOTE:
Telnet is not recommended to access a device remotely, but you can use in a LAB
environment.
For telnet, you must set the privileged password on router/switch. If not set, you will
not be able to access the device.
To access a Device using Telnet, from command prompt type:
C:\>telnet 192.168.1.1
Configuring SSH
MY_CISCO_CENTER (config)#username ahmed password cisco123

MY_CISCO_CENTER (config)#ip domain-name MY-CISCO-CENTER
MY_CISCO_CENTER (config)#crypto key generate rsa

92-321-2418349 10
`
The name for the keys will be: MY-CISCO-CENTER.net Choose

the size of the key modulus in the range of 360 to 2048 for your
General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys [OK]
MY_CISCO_CENTER (config)#line vty 0 15
MY_CISCO_CENTER (config-line)#login local
MY_CISCO_CENTER (config-line)#transport input ssh
For SSH you need utilities like Secure CRT or putty to remotely access the device.

92-321-2418349 11
`
Cisco Routers Password Recovery

OBJECTIVE: To recover the console and enable password for Routers/Switches.
Configuration on Router
MCC-R1>enable
MCC-R1#config t
MCC-R1 (config)#line console 0
MCC-R1 (config-line)Password cisco
MCC-R1 (config-line)#Login MCC-
R1 (config-line)#Exit
MCC-R1#copy running-config startup-config <To save the configurations)
After these configurations, restart the router, while router restarts press the Ctrl+Break or
Ctrl+C key to enter into ROM Monitor Mode.

92-321-2418349 12
`
In ROM Monitor Mode:
Rommon 1 > confreg 0x2142

Rommon 2 > reset
Once the Router/Switch is restarted, it will ignore the startup configurations in

NVRAM. Now you can configure the following commands, for setting a new password.
Router#copy startup-config running-config

Router(config)#enable password cisco
Router(config)#config-register 0x2102
Router#copy running-config startup-config
Restart the router, enter new configured password, to access the router.

92-321-2418349 13
`
Implementing Virtual Local Area Networks (VLANs)
OBJECTIVE: To configure VLANs and Verify the configurations.

TOPOLOGY
Step: 1 to Create VLANs
MY_CISCO_CENTER#config terminal
MY_CISCO_CENTER (config)#vlan 10
MY_CISCO_CENTER (config-vlan)#name HR
MY_CISCO_CENTER (config-vlan)#exit
MY_CISCO_CENTER (config)#vlan 20
MY_CISCO_CENTER (config-vlan)#name IT
MY_CISCO_CENTER (config-vlan)#exit
Verify VLANs
MY_CISCO_CENTER #show vlan brief

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, Fa0/23, Fa0/24
Gig0/1, Gig0/2
10 HR active
20 IT active

92-321-2418349 14
`
Step 2: Port Membership
MY_CISCO_CENTER (config)#interface fa0/2

MY_CISCO_CENTER (config-if)#switchport mode access
MY_CISCO_CENTER (config-if)#switchport access vlan 10
MY_CISCO_CENTER (config-if)#exit
MY_CISCO_CENTER (config)#interface fa0/3
MY_CISCO_CENTER (config-if)#switchport mode access
MY_CISCO_CENTER (config-if)#switchport access vlan 20
Switch# show vlan brief
VLAN Name Status Ports

---- -------------------------------- --------- -------------------------------
10 HR active
20 IT active
1 default active Fa0/1, 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, Fa0/23, Fa0/24
Gig0/1, Gig0/2
Fa0/2
Fa0/3
NOTE: This is a Local VLAN, for End to End VLANs, you need to configure Trunk Port
between Switches. A trunk port carries traffic for multiple VLANs. Same configuration on
both switches.
Trunk Port Configuration:
Interface fa<port number>
switchport mode trunk

92-321-2418349 15
`
Implementing VLAN Trunking Protocol Version 2 (VTP)
OBJECTIVE: Configuring and verifying VTP Version 2 on Cisco Switches
Configuring MCC-Switch-1:
Switch(config)#hostname MCC-Switch-1
MCC-Switch-1(config)#exit
MCC-Switch-1#show vtp status

92-321-2418349 16
`
MCC-Switch-1#configure terminal
MCC-Switch-1(config)#vtp domain MCC.COM
Changing VTP domain name from NULL to MCC.COM
MCC-Switch-1(config)#vlan 10
MCC-Switch-1(config-vlan)#name MCC-HR
MCC-Switch-1(config-vlan)#exit
MCC-Switch-1(config)#vtp password mcc123
MCC-Switch-1(config)#exit
MCC-Switch-1#show vtp status
Note:
VTP Password and domain name should be same on all Cisco switches
If you want to set revision number to zero set VTP mode to transparent
Best practice is to set VTP mode transparent then connect a new switch to your
network.

92-321-2418349 17
`
Implementing Port Based Security on Switches
OBJECTIVE: Configure port security and verify the configurations.

TOPOLOGY
Switch Configurations
MY_CISCO_CENTER(config)#interface range fa0/1-2
MY_CISCO_CENTER(config-if)#switchport mode access
MY_CISCO_CENTER(config-if)#switchport port-security
MY_CISCO_CENTER(config-if)#switchport port-security mac-address sticky
MY_CISCO_CENTER(config-if)#switchport port-security maximum 1
MY_CISCO_CENTER(config-if)#switchport port-security violation shutdown
MY_CISCO_CENTER(config-if)#exit
NOTE: You can also use manual MAC address entry instead of sticky option.

92-321-2418349 18
`
Verify Port-Security MAC Address:
MY_CISCO_CENTER#show port-security
Secure Port MaxSecureAddr CurrentAddr SecurityViolation Security Action

(Count) (Count) (Count)
---------------------------------------------------------------------------------------------------------------
Fa0/1 1 1 0 Shutdown
---------------------------------------------------------------------------------------------------------------
Verify Port-Security Interface FastEnthernet Fa0/1:
MY_CISCO_CENTER #show port-security interface f0/1

Port Security: Enabled
Port Status: Secure-up
Violation Mode: Shutdown
Aging Time: 0 mins
Aging Type: Absolute
Secure Static Address Aging: Disabled
Maximum MAC Addresses: 1
Total MAC Addresses: 1
Configured MAC Addresses: 0
Sticky MAC Addresses: 1
Last Source Address:Vlan : 0010.1110.9B5E:1
Security Violation Count: 0
Max Addresses value depends upon the model of the device.

address can be entered in port-security instead on using sticky
Manual MAC
command.

Violation modes can be set to protect, restrict or shutdown

92-321-2418349 19
`
What happens if violation occurred?
When a new PC is attached to the port on which port-security is enabled then

Switch will take an action which is set in the violation mode.
Verify when violation is occurred:
MCC-SW1#show port-security
Secure Port Ma SecureAddr CurrentAddr SecurityViolation Security Action
(Count) (Count) (Count)
--------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------
NOTE:
When a port is shutdown, you need to manually shutdown the port, then again
no shut, otherwise port will remain in error disabled mode.

92-321-2418349 20
`
Implementing IEEE (802.1d) STP and (802.1w) RSTP
OBJECTIVE: To implement STP, RSTP and manually make a bridge as root bridge.
TOPOLOGY
Verify Root Bridge on MCC-SW1:
MCC-SW1#show spanning-tree
VLAN0001
Spanning tree enabled protocol
ieee Root ID Priority 32769
Address 0090.0C55.4360
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 0090.0C55.4360

92-321-2418349 21
`

Aging Time 20
Interface Role Sts Cost Prio.Nbr Type

------------- ---- --- --------- -------- -------------------------------------------------------
Fa0/1 Desg FWD 19 128.1 P2p

In the output shownabove, the parameters defined in Root ID corresponds to the Root
Bridge information.

While Bridge ID, is Local Switch information.

As this bridge is the root bridge, having Lowest MAC address, with default priority.

Default Priority is 32768, and all switch ports are members of VLAN 1,
so the priority
becomes 32768+Ext. VLAN ID which in this case is 1 (32768+1=32769).
Run the same command on other switches and verify the Root Bridge.
Enabling RSTP:
MCC-SW1(config)#spanning-tree mode rapid-pvst

MCC1#show spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769

Address 0090.0C55.4360

Address 0090.0C55.4360
Aging Time 20

92-321-2418349 22
`

---------------- ---- --- --------- -------- ---------------------------------------------------------------
Configuring MCC2 as the Root Bridge for VLAN 1:

the Root Bridge, and Bridge ID
As you know, Lowest Bridge/Switch ID, Switch will become
is the combination or Bridge Priority and MAC address.

By default Bridge Priority is same, and you cannot change the MAC address. In order
to manually make a switch as Root Bridge we can only change its Priority. Priority of
a Switch is changed in increments of 4096.
MCC2(config)#spanning-tree vlan 1 priority 4096
Verify MCC-SW2 as Root Bridge for VLAN 1:
MCC-SW2#show spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 4097
Address 0090.2127.15AC

Address 0090.2127.15AC
Aging Time 20

---------------- ---- --- --------- -------- ---------------------------------------------------------------

92-321-2418349 23
`
Enabling Port fast feature on all switches:
CONCEPT:
By enabling portfast feature on all the switches, switches will disable the STP process
on all non-trunk ports. It will cause to take less time to change the state to up on all
non-trucking ports. To verify this feature, connect a PC to the switch and the port will
be up within 5 seconds.
But the problem arises when a Switch is plug in, to a STP disabled port, it can create
switching loops. The solution to this problem is BPDU Guard, which will not listen
Bridge Protocol Data Units (exchange of parameters between switches), no switching
loops will be created on Access Ports.
MCC-SW1(config)#spanning-tree portfast default

MCC-SW1(config)# spanning-tree bpduguard enable

92-321-2418349 24
`
Implementing Link Aggregation (Ether-Channel)
OBJECTIVE: To implement Layer 2 Ether- Channel and verify the configurations

TOPOLOGY
Configuring MCC-SW1:
MCC-SW1(config)#interface range fa0/1 - 2

MCC-SW1 (config-if-range)#channel-protocol pagp
MCC-SW1 (config-if-range)#channel group 1 mode desirable
MCC-SW1 (config-if-range)#exit
MCC-SW1 (config)#interface port-channel 1
MCC-SW1 (config-if)#switchport mode trunk
Configuring MCC-SW2:
MCC-SW2(config)#interface range fa0/1 - 2

MCC-SW2 (config-if-range)#channel-protocol pagp
MCC-SW2 (config-if-range)#channel group 1 mode desirable
MCC-SW2 (config-if-range)#exit
MCC-SW2 (config)#interface port-channel 1
MCC-SW2 (config-if)#switchport mode trunk

92-321-2418349 25
`
Verify Etherchannel:
MCC-SW1#show etherchannel summary
Flags: D - down P - in port-channel

I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 1

Number of aggregators: 1
Group Port-channel Protocol Ports

--------------------------------------------------------------------------------------------------
1 Po1(SU) PAgP Fa0/1(P) Fa0/2(P)

92-321-2418349 26
`
Implementing Inter-Vlan Routing using Router on a Stick

OBJECTIVE: To configure and verify Inter-Vlan routing, using router on stick
TOPOLOGY
VLANs Creation:
MCC1(config)#vlan 10
MCC1(config-vlan)#name HR
MCC1(config-vlan)#exit
MCC1(config)#vlan 20
MCC1(config-vlan)#name IT
MCC1(config-vlan)#exit
Port Assignment:
MCC1(config)#interface fa0/1
MCC1(config-if)#switchport mode access
MCC1(config-if)#switchport access vlan 10
MCC1(config-if)#exit
MCC1(config)#interface fa0/2
MCC1(config-if)#switchport mode access
MCC1(config-if)#switchport access vlan 20
MCC1(config-if)#exit

92-321-2418349 27
`
Trunk Port For Router On a Stick (The port connecting the Router)
MCC1(config)#interface gigabitEthernet 0/1

MCC1(config-if)#switchport mode trunk
Router Configurations:
MCC-R1(config)#interface fa0/0
MCC-R1(config)#interface gigabitEthernet 0/0
MCC-R1(config-if)#no shutdown
Creating sub-interface for VLAN 10 on router:
MCC-R1(config)#interface gigabitEthernet 0/0.10

MCC-R1(config-subif)#encapsulation dot1Q 10
MCC-R1(config-subif)#ip address 10.0.0.1 255.0.0.0
MCC-R1(config-subif)#exit
Creating sub-interface for VLAN 20 on router:
MCC-R1(config)#interface gigabitEthernet 0/0.20

MCC-R1(config-subif)#encapsulation dot1Q 20
MCC-R1(config-subif)#ip address 11.0.0.1 255.0.0.0
MCC-R1(config-subif)#exit
PC0 Configurations

92-321-2418349 28
`
PC1 Configurations:
Verify Inter-VLAN routing, Ping PC1 from PC0

92-321-2418349 29
`
Configuring Static Route on Cisco Routers

OBJECTIVE: To configure and verify static routing.
TOPOLOGY
MCC-R2 Configurations:
MCC-R2 (config)#interface serial 0/0
MCC-R2 (config-if)#ip address 200.150.160.1 255.255.255.252
MCC-R2 (config-if)#clock rate 64000
MCC-R2 (config-if)#no shutdown
MCC-R2 (config)#interface fa2/0
MCC3 Configurations:


92-321-2418349 30
`
Static Routing:
Adding static route on MCC-R2 for network 172.16.100.0
MCC-R2(config)#ip route 172.16.0.0 255.255.0.0 200.150.160.2
Adding static route on MCC-R3 for network 10.0.0.0
MCC-R3(config)#ip route 10.0.0.0 255.0.0.0 200.150.160.1
NOTE: When configuring the static route on router R1 we used the local interface of the
router R1 i.e. s0/1/0, whereas, when configuring router R2 we use the next hop address
as Forwarding router's address.
Verify Routing
MCC-R2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D
- EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1
- OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1
- OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 10.0.0.0/8 is directly connected, FastEthernet2/0

S 172.16.0.0/16 [1/0] via 200.150.160.2
200.150.160.0/30 is subnetted, 1 subnets
C 200.150.160.0 is directly connected, Serial0/0

92-321-2418349 31
`
Similarly on MCC-R3
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D
- EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1
- OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1
- OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
area * - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
S 10.0.0.0/8 [1/0] via 200.150.160.1

Verify the ping from PC0 to PC1

92-321-2418349 32
`
Configuring Routing Information Protocol Version 2

OBJECTIVE: To configure and verify RIP V2 routing.
TOPOLOGY
Mcc-r1 configurations:
MCC-R1(config-if)#ip address 10.10.10.1 255.255.255.0
MCC-R1(config)#interface serial 3/0
MCC-R1(config)#router rip
MCC-R1(config-router)#version 2
MCC-R1(config-router)#network 200.150.160.0
MCC-R2(config-if)#clock rate 64000

92-321-2418349 33
`
MCC-R2(config-if)#exit
MCC-R2(config-router)#exit
MCC-R2(config)#exit
MCC-R3(config)#exit
Verify Routing Table on MCC-R1

92-321-2418349 34
`
Verify end to end connectivity, ping MCC-PC2 from MCC-PC

92-321-2418349 35
`
Implementing Enhanced Interior Gateway Routing Protocol (EIGRP)
TOPOLOGY:
MCC-R3
MCC-R2
MCC-R2 Configurations:

MCC-R2 (config-if)#clock rate 64000
MCC3 Configurations:


92-321-2418349 36
`

Adding networks for EIGRP on Router MCC-R2:
MCC-R2(config)#router eigrp 10
MCC-R2 (config-router)#network 10.0.0.0
MCC-R2 (config-router)#no auto-summary
MCC-R2 (config-router)#exit
Adding networks for EIGRP on Router MCC-R3:
MCC-R3 (config)#router eigrp 10

Verify Routes on MCC-R2

D 172.16.0.0/16 [90/2172416] via 200.150.160.2, 00:00:25, Serial0/0

92-321-2418349 37
`
Verify Routes on MCC-R3

D 10.0.0.0/8 [90/20514560] via 200.150.160.1, 00:02:09, Serial2/0

To Verify Neighbor Relationship, by viewing Neighbor Table:

Neighbor Table on MCC-R2
MCC-R2#show ip eigrp neighbors

IP-EIGRP neighbors for process 10
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 200.150.160.2 Se0/0 10 00:03:17 40 1000 0 15
Neighbor Table on MCC-R3
IP-EIGRP neighbors for process 10

H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 200.150.160.1 Se2/0 13 00:09:27 40 1000 0 7
NOTE: To verify the currently enabled routing protocols, use the following command:
R1#show ip protocols
To view all the routes that has been calculated by EIGRP, use the following command :
R1#show ip eigrp topology.

92-321-2418349 38
`
Implementing Open Shortest Path First (OSPF) Version2
TOPOLOGY
MCC-R1
MCC-R0 MCC-R2
Configuring MCC-R0
Configuring Mcc-R1

92-321-2418349 39
`
Configuring MCC-R2
Configuring MCC-R1
The Area Border Router
MCC-R1(config)#router ospf 10
MCC-R1(config-router)#network 200.150.160.0 0.0.0.3 area 0
Configuring MCC-R0
The BACKBONE Area Router

Configuring MCC-R2
Regular Area Router, Internal Router
Verify Routes on ABR:
O 10.0.0.0/8 [110/65] via 200.150.160.1, 00:12:21, Serial2/0

O 172.16.0.0/16 [110/65] via 139.60.37.2, 00:03:03, Serial3/0

92-321-2418349 40
`
Verify Routes on MCC-R0 (Backbone Router)


O 139.60.37.0 [110/128] via 200.150.160.2, 00:19:03, Serial2/0
0IA 172.16.0.0/16 [110/129] via 200.150.160.2, 00:09:42, Serial2/0
Verify Routes on MCC-R2 (Internal Router)

O 10.0.0.0/8 [110/129] via 139.60.37.1, 00:17:38, Serial2/0

O IA 200.150.160.0 [110/128] via 139.60.37.1, 00:17:38, Serial2/0
Verify end to end connectivity
Ping from PC0 to PC1
Note: More commands to verify OSPF:

MCC-R1#show ip ospf neighbor
MCC-R1#show ip ospf database
MCC-R1#show ip protocols
MCC-R1#show ip ospf interface

92-321-2418349 41
`
Implementing IPV6 on Cisco Routers

TOPOLOGY
MCC-R1 Configuration
MCC-R1(config)#ipv6 unicast-routing
MCC-R1(config-if)#ipv6 address 2001:abad:beef:1::1/64
MCC-R2 Configuration
MCC-R2(config-if)#ipv6 address 2001:abad:beef:1::2/64
Verify Configurations
MCC-R1# show ipv6 interface

92-321-2418349 42
`
MCC-R2# show ipv6 interface
Verify IPv6 communication between R2 and R1 using ping:

92-321-2418349 43
`
Configuring IPV6 Stateless Auto Configuration

OBJECTIVE: To configure State less auto IPv6 configurations on Cisco Routers
TOPOLOGY
MCC-R1(config-if)#ipv6 address 2001:abad:5001:1::1/64
MCC-R1(config-if)#ipv6 address prefix 2001:abad:5001:1::/64
MCC-R2(config-if)#ipv6 address autoconfig

92-321-2418349 44
`
MCC-R3(config-if)#ipv6 address autoconfig
Verify configurations:

92-321-2418349 45
`
Implementing Ripng on Cisco Routers
OBJECTIVE: To configure and verify RIPng on Cisco Routers

TOPOLOGY
BACKGROUND: In this configuration example, routers R1 and R2 are connected via Serial
interface and Loopback addresses are configured to generate networks. All the interfaces
are configured with the IPv6 addresses
MCC-R1(config-if)#ipv6 rip MY-CISCO-CENTER enable
MCC-R1(config)#interface loopback 10
MCC-R1(config-if)#ipv6 address 1:1:1:1::1/64
MCC-R2(config)#IPV6 unicast-routing

92-321-2418349 46
`

Verify Configurations And Connectivity

To view the ipv6 routing Table
Verify information about the current IPv6 RIP process

92-321-2418349 47
`
Verify the details of entries in current rip routing instance.
Verify the reachability between the routers R1 and R2, use the ping command

92-321-2418349 48
`
OBJECTIVE: To configure and Verify OSPF Version 3 on Cisco Routers
TOPOLOGY
Configuration On Mcc-R1
MCC-R1 (config)#ipv6 unicast-routing

MCC-R1 (config)#interface fastEthernet 0/0
MCC-R1 (config-if)#ipv6 address 2001:abad:5001:1::1/64
MCC-R1 (config-if)#ipv6 ospf 1 area 0
MCC-R1 (config-if)#exit
MCC-R1 (config)#interface loopback 10
MCC-R1 (config-if)#ipv6 address 1:1:1:1::1/64
MCC-R1 (config)#interface loopback 20
MCC-R1 (config-if)#ipv6 address 1:1:1:2::1/64
MCC-R1 (config-if)#e
MCC-R1 (config)#ipv6 router ospf 1
MCC-R1 (config-rtr)#router-id 1.1.1.1

92-321-2418349 49
`
Configurations On Mcc-R2
MCC-R2(config-if)#ipv6 ospf 1 area 0
MCC-R2(config)#ipv6 router ospf 1
MCC-R2(config-rtr)#router-id 2.2.2.2
Configure R1s Loopback 10, 20 and R2s Loopback 0, 1 interface to participate in OSPF
Area 0 and ensure that R1 & R2 advertises Lo0 as a /64 subnet and not a host route (/128).
NOTE: Loopback interfaces have their own OSPF network type in which case OSPF
advertises a host route to the loopback interface and not the configure subnet mask.
To change OSPF to advertise the subnet assigned to the loopback interface youll
need to change the network type to point-to-point as shown below
MCC-R1
MCC-R1(config-if)#ipv6 ospf network point-to-point
92-321-2418349 50
`
MCC-R2
Verify R1s Loopback0 network is in the IPv6 routing table of R2:

MCC-R1#show ipv6 route ospf

92-321-2418349 51
`
Verify R1s Loopback10 network has IPv6 connectivity to R2s

Loopback0 network using PING:

92-321-2418349 52
`
Implementing EIGRP for IPV6 Networks
OBJECTIVE: To configure and verify EIGRP for IPV6

TOPOLOGY
MCC-R1(config)#ipv6 router eigrp 100
MCC-R1(config-rtr)#eigrp router-id 1.1.1.1
MCC-R1(config-rtr)#exit
MCC-R1(config-if)# ipv6 eigrp 100
MCC-R1(config-if)#ipv6 eigrp 100

92-321-2418349 53
`
MCC-R2(config)#ipv6 router eigrp 100
MCC-R2(config-rtr)#eigrp router-id 2.2.2.2
MCC-R2(config-rtr)#exit
MCC-R2(config)#int

92-321-2418349 54
`
Verify R1s Loopback0 network is in the IPv6 routing table of R2: R1#show ipv6 route eigrp
Check connectivity

92-321-2418349 55
`
Configuring DHCP on Cisco Routers

OBJECTIVE: To Configure Cisco Routers as a DHCP Server and Verify the services.
TOPOLOGY
Configurations On Mcc-Dhcp-Server
MCC-DHCP-SERVER(config)#ip dhcp pool MCC-DHCP-POOL1
MCC-DHCP-SERVER(dhcp-config)#network 192.168.1.0 255.255.255.0
MCC-DHCP-SERVER(dhcp-config)#default-router 192.168.1.1
MCC-DHCP-SERVER(dhcp-config)#exit
MCC-DHCP-SERVER(config)#ip dhcp excluded-address 192.168.1.10

92-321-2418349 56
`
NOTE:
You can exclude the range of addresses which should not be assigned to host machines,
or reserved addresses for Web Servers, DNS Servers etc. You can also configure Multiple
DHCP pools for VLANs on a single DHCP Server.
Verify the DHCP Server Configurations:

92-321-2418349 57
`
Address Leases on DHCP Server:
MCC-DHCP-SERVER # show ip dhcp binding

92-321-2418349 58
`
Implementing Standard and Extended Access Control List (ACL)
OBJECTIVE: To implement standard and extended access control lists to limit the access.
TOPOLOGY

92-321-2418349 59
`
Ping from MCC-PC1 to MCC-PC2
Now restrict the MCC-PC1 to communicate with MCC-PC using standard ACL.
MCC-R1(config)#access-list 50 deny host 192.168.1.2

MCC-R1(config-if)#ip access-group 50 in

92-321-2418349 60
`
Now check the connectivity from MCC-PC1 to MCC-PC2

92-321-2418349 61
`
EXTENDED ACL
TOPOLOGY

The task isto permit MCC-PC1 on LAN 1 only WEB access to MYCISCOCENTER
Webserver.

Block MCC-PC1 from accessing the MYCISCOCENTER Webserver through WWW.
Configuration On Mcc-R1
MCC-R1 (config-router)#network 200.150.160.0 0.0.0.3
MCC-R1 (config)#access-list 100 permit tcp host 192.168.1.2 host 172.16.100.50 eq 80
MCC-R1 (config)#access-list 100 deny tcp host 192.168.1.3 host 172.16.100.50 eq 80
MCC-R1 (config)#access-list 100 permit ip any any

92-321-2418349 62
`
MCC-R1 (config-if)#ip access-group 100 in
MCC-R2 (config)#exit
Verification:
Accessing the Web Server from MCC-PC1

92-321-2418349 63
`
Accessing Web Server from MCC-PC2

92-321-2418349 64
`
Implementing Network Address Translation (Static, Dynamic and PAT)

OBJECTIVE: To configure and Verify Static, Dynamic and PAT.
TOPOLOGY

92-321-2418349 65
`


CONFIGURING STATIC NAT FOR MCC-PC1 WITH PUBLIC IP 200.150.160.1
MCC-R1(config)#ip nat inside source static 192.168.1.2 200.150.160.1

MCC-R1(config-if)#ip nat inside
MCC-R1(config-if)#ip nat outside
Verify, By Using Command

MCC-R1#show ip nat translation

92-321-2418349 66
`
DYNAMIC NAT
TOPOLOGY

92-321-2418349 67
`

Configuring Dynamic NAT for MCC-PC1 and MCC-PC2 with IP addresses

180.139.60.2 180.139.60.3.
MCC-R1(config)#ip nat pool DYNAMIC-NAT 180.139.60.2 180.139.60.3

netmask 255.255.255.0
MCC-R1(config)#access-list 10 permit any
MCC-R1(config)#ip nat inside source list 10 pool DYNAMIC-NAT
VERIFY:

92-321-2418349 68
`
PAT
TOPOLOGY


92-321-2418349 69
`

Configuring Port Address Translation with public IP addresses 200.150.160.1.
MCC-R1(config)#ip nat pool PAT 200.150.160.1 200.150.160.1 netmask

255.255.255.252 MCC-R1(config)#access-list 10 permit any
MCC-R1(config)#ip nat inside source list 10 pool PAT overload
VERIFICATION:

92-321-2418349 70
`
Implementing Hot Standby Routing Protocol(HSRP)
TOPOLOGY

92-321-2418349 71
`
Configuring MCC-R1 (WAN Router)

MCC-R1(config-router)#network 200.150.160.0 0.0.0.3
MCC-R1(config-router)#no auto-summary
Configuring MCC-R2 (HSRP Group 1 Router)

Configuring MCC-R3 (HSRP Group 1 Router)

MCC-R3(config-if)#ip address 192.168.1.2
CONFIGURING HSRP ON MCC-R2

92-321-2418349 72
`
MCC-R2(config)#interface GigabitEthernet 6/0

MCC-R2(config-if)#standby 1 ip 192.168.1.100
MCC-R2(config-if)#standby 1 priority 110
MCC-R2(config-if)#standby 1 preempt
MCC-R2(config-if)#standby 1 track serial 2/0
CONFIGURING HSRP ON MCC-R3

MCC-R3(config)#interface GigabitEthernet 6/0
MCC-R3(config-if)#standby 1 ip 192.168.1.100
MCC-R3(config-if)#standby 1 priority 95
MCC-R2(config-if)#standby 1 preempt
Verify the configurations:

MCC-R2#show standby

92-321-2418349 73
`
Similarly on MCC-R3
MCC-R3#show standby

92-321-2418349 74
`
Implementing Wan Encapsulation
OBJECTIVE: To configure PPP WAN Encapsulation.

TOPOLOGY
MCC-R1(config)#username MCC-R1 password

cisco MCC-R1(config)#interface serial 1/0
MCC-R1(config-if)#encapsulation ppp
MCC-R1(config-if)#ppp authentication chap pap
MCC-R1(config)#username MCC-R2 password cisco (Other side Router parameters)
MCC-R1(config)#exit
MCC-R2(config)#username MCC-R2 password

cisco MCC-R2(config)#interface serial 1/0
MCC-R2(config-if)#encapsulation ppp
MCC-R2(config-if)#ppp authentication chap pap
MCC-R2(config)#username MCC-R1 password cisco(Other side Router parameters)
MCC-R2(config)#exit

92-321-2418349 75
`
Verify point-to-point connectivity:

R1#ping 192.168.1.2

92-321-2418349 76
`
TFTP SERVER
OBJECTIVE: System IOS and Running-Configuration to a remote TFTP server.

TOPOLOGY
Configuring the Router in order to save these configurations and then copy to TFTP Server
MCC-R1(config-router)#network 10.10.10.
MCC-TFTP-SERVER (BEFORE COPYING FILES)

92-321-2418349 77
`
You can see, currently there are no files present on TFTP server.
Which files you want to copy to TFTP server, first you should know their names.
As you can see the IOS image with extension of .bin is present, I will copy this IOS to
TFTP Server, then starup-config.
To copy files to TFTP Server

MCC-R1#copy flash: tftp:
Source filename []? pt1000-i-mz.122-28.bin
Address or name of remote host []? 10.10.10.10
Destination filename [pt1000-i-mz.122-28.bin]? <if you want to save this file with different
name specify here, otherwise press enter to save with default name>
Writing pt1000-i-mz.122-
28.bin....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
[OK - 5571584 bytes]
5571584 bytes copied in 3.162 secs (403737 bytes/sec)

92-321-2418349 78
`
Now verify the IOS on TFTP Server.
COPYING STARTUP-CONFIG
MCC-R1#copy startup-config tftp:

Destination filename [MCC-R1-confg]? MCC-R1_startup-config
Writing startup-config...!!
[OK - 778 bytes]

92-321-2418349 79
`
MCC-R1#
VERIFICATION:
You can see both, Router IOS and Starup-config has been copied to secure location, TFTP
Server.
NOTE: By following the same procedure, you can copy files from TFTP Server to
the device.

92-321-2418349 80
`
FTP SERVER
OBJECTIVE: System IOS and Running-Configuration to a remote FTP server.

TOPOLOGY
MCC-R1(config-router)#network 10.10.10.
For FTP you need to create a user on FTP server. These credentials will be used to copy
to files to FTP Server, this username and password is also configured on Router as it is.
MCC-R1(config)#ip ftp username MCCFTP
MCC-R1(config)#ip ftp password cisco123

92-321-2418349 81
`
Copy IOS:
MCC-R1#copy flash: ftp:

Source filename []? pt1000-i-mz.122-28.bin
Destination filename [pt1000-i-mz.122-28.bin]?
Writing pt1000-i-mz.122-28.bin...
[OK - 5571584 bytes]
Copy startup-config
MCC-R1#copy startup-config ftp:

Destination filename [MCC-R1-confg]? MCC-R1-Configurations
Writing startup-config...
[OK - 846 bytes]

92-321-2418349 82
`
Verify on FTP Server:
NOTE: By following the same procedure, you can copy files from TFTP Server to
the device.

92-321-2418349 83
`
Configuring SYSLOG Server
OBJECTIVE: To Implement Syslog Server

TOPOLOGY
MCC-R1(config)#INterface fa0/0
MCC-R1(config)#logging on
MCC-R1(config)#service timestamps debug datetime msec
MCC-R1(config)#logging host 172.16.100.100
MCC-R1(config)#logging trap debugging
Now perform some tasks on router, they will be reported to syslog server.

92-321-2418349 84
`
Verification:

92-321-2418349 85
`
PPP MULTILINK LAB
CONFIGURATION ON R4:

92-321-2418349 86
CONFIGURATION ON R5:

92-321-2418349 87
Verification of PPP Multilink on R4 & R5 :

92-321-2418349 88
92-321-2418349 89
GRE TUNNEL
CONFIGURATION OF GRE ON R1 & R2

92-321-2418349 90
92-321-2418349

CCNA-Manual-200-125 Final PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCNA-Manual-200-125 Final PDF

Uploaded by

Copyright:

Available Formats

LAB MANUAL (Version 1.

From the Desk of Engr. Ahmed Saeed

CCNA LAB MANUAL 200-125

My Cisco Center, PECHS Block 6

Warning and Disclaimer,

This manual is designed to provide information about

Reviewed and Approved By

Engr. Ahmed Saeed

From the Desk of Engr. Ahmed Saeed

Basic Configurations of Internetwork Operating System (IOS)

Configuring Telnet and SSH on Cisco Routers

Cisco Routers Password Recovery

Implementing Virtual Local Area Networks (VLANs)

Implementing VLAN Trunking Protocol Version 2 (VTP)

Implementing Port Based Security on Cisco Switches

Implementing IEEE (802.1d) STP and (802.1w) RSTP

Implementing Link Aggregation (Ether-Channel)

Implementing Inter-Vlan Routing using Router on a Stick

Configuring Static Route on Cisco Routers

Configuring Routing Information Protocol Version 2

Implementing Enhance Interior Gateway Routing Protocol (EIGRP)

Implementing Open Shortest Path First (OSPF) Version 2

Implementing IPv6 on Cisco Routers

Configuring IPV6 Stateless Auto Configuration

From the Desk of Engr. Ahmed Saeed

Implementing RIPng on Cisco Routers

Implementing Open Shortest Path First (OSPF) Version 3

Implementing EIGRP for IPV6 Networks

Configuring DHCP on Cisco Routers

Implementing Standard and Extended Access Control List (ACL)

Implementing Network Address Translation (Static, Dynamic and

PAT) Implementing Hot standby Routing Protocol (HSRP)

Implementation of WAN Encapsulation

Configuring Syslog Server

From the Desk of Engr. Ahmed Saeed

Basic Configurations of Internetwork Operating System (IOS)

OBJECTIVE: Basic configurations of a Cisco Switch/Router.

From the Desk of Engr. Ahmed Saeed

From the Desk of Engr. Ahmed Saeed

Once you click OK, you will have Switch/Router Console.

Switch> User-exec mode

From the Desk of Engr. Ahmed Saeed

How to switch in different modes:

How to Set Hostname and Configure Console Password:

Switch(config)# hostname MY_CISCO_CENTER

How to Set Privilege level password:

!!! Clear Text Password not encrypted(less priority)

Verify the Password:

Press RETURN to get started.

From the Desk of Engr. Ahmed Saeed

How to Set User Authentication in Switch:

MY_CISCO_CENTER #config terminal

MY_CISCO_CENTER (config)#username MCC password cisco123

Verify the Authentication

From the Desk of Engr. Ahmed Saeed

Configuring Telnet and SSH on Cisco Routers

OBJECTIVE: Configuring the Cisco Router/Switch for remote access.

How to Enable The Device to Establish Telnet/SSH Session:

MY_CISCO_CENTER (config)#interface vlan 1

To access a Device using Telnet, from command prompt type:

MY_CISCO_CENTER (config)#username ahmed password cisco123

From the Desk of Engr. Ahmed Saeed

The name for the keys will be: MY-CISCO-CENTER.net Choose