Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1. BASIC
2. RIP
3. OSPF
4. EIGRP
5. ACL
6. NAT
7. VLAN & VTP
8. STP
9. FHRP (HSRP, VRRP & GLBP)
10. NTP
11. DHCP
12. SNMP
13. IPV6
14. OSPFV3
15. EIGRPV3
16. PPP
17. FR
1. BASIC
1.1 Basic Networking Tools on Host Computer (MS-DOS) for basic
network connectivity verification
● ipconfig
● ipconfig/all
● ipconfig/release
● ipconfig/renew
● netstat –a
● nslookup
● arp –a
● ipconfig /displaydns
● ping 127.0.0.1
● Tracert 4.4.4.254
Enable password ts
line con 0
login
password console
line vty 0 4
login
password vty
banner motd !
#######################################################
#####################################################
######### HELLO TO OUR NETWORK ####################
######YOU ARE ENTERING A SECURED NETWORK ########
###YOU WOULD BE FINED FOR ANY VIOLATION #########
##THIS NETWORK IS THE SOLE PROPERTY OF CISCO#####
#############################################
###########################################
######################################### !
➢ Implementation Steps:
banner motd !
#######################################################
#####################################################
######### HELLO TO OUR NETWORK ####################
######YOU ARE ENTERING A SECURED NETWORK ########
###YOU WOULD BE FINED FOR ANY VIOLATION #########
##THIS NETWORK IS THE SOLE PROPERTY OF CISCO#####
#############################################
###########################################
######################################### !
➢ Post-implementation Results:
● Log-out completely from the Switch and then login, the 1st thing that would pop-up on the
IOS window would be this banner
➢ Implementation Steps:
line vty 0 15
password cisco
login local
transport input telnet ssh ; Configure vty ports for using SSH
➢ Post-implementation Results:
1.2.13 Command to convert all the passwords even in level 7 mode to level 5 automatically
➢ Implementation Steps:
service password-encryption
➢ Post-implementation Results:
int gi 0/0
description ** interface towards NYK (R2) **
ip addr 10.1.12.1 255.255.255.0
no sh
sp 100
dup full
int gi 0/1
description ** interface towards DUB(R4) **
ip addr 10.1.14.1 255.255.255.0
sp 100
dup full
sh
o NYK (R2)
int gi 0/2
description ** LAN Network **
ip addr 2.2.2.254 255.255.255.0
no sh
int gi 0/0
description ** interface towards LON (R1) **
ip addr 10.1.12.2 255.255.255.0
no sh
sp 100
dup full
int gi 0/1
description ** interface towards PAR(R3) **
ip addr 10.1.23.2 255.255.255.0
no sh
sp 100
dup full
o PAR(R3)
int gi 0/2
description ** LAN Network **
ip addr 3.3.3.254 255.255.255.0
no sh
int gi 0/1
description ** interface towards NYK (R2) **
ip addr 10.1.23.3 255.255.255.0
no sh
sp 100
dup full
int gi1/0
description ** interface towards DUB(R4) **
ip addr 10.1.34.3 255.255.255.0
no sh
sp 100
dup full
o DUB(R4)
int gi 0/2
description ** LAN Network **
ip addr 4.4.4.254 255.255.255.0
no sh
int gi1/0
description ** interface towards PAR(R3) **
ip addr 10.1.34.4 255.255.255.0
no sh
sp 100
dup full
int gi 0/1
description ** interface towards LON (R1) **
ip addr 10.1.14.4 255.255.255.0
no sh
sp 100
dup full
➢ Post-implementation Results:
● See if you can view all networks as “C” in your routing tables
o On all Routers:
▪ sh ip route static
▪ sh cdp neighbour
▪ sh ip int brief
▪ sh int fax/y
➢ Diagram:
➢ Implementation Steps:
o LON (R1)
ip route 2.2.2.0 255.255.255.0 10.1.12.2
ip route 3.3.3.0 255.255.255.0 10.1.12.2
ip route 4.4.4.0 255.255.255.0 10.1.12.2
o NYK (R2)
ip route 1.0.0.0 255.255.255.0 10.1.12.1
ip route 3.3.3.0 255.255.255.0 10.1.23.3
ip route 4.4.4.0 255.255.255.0 10.1.23.3
o PAR(R3)
ip route 1.0.0.0 255.255.255.0 10.1.23.2
ip route 2.2.2.0 255.255.255.0 10.1.23.2
ip route 4.4.4.0 255.255.255.0 10.1.34.4
o DUB(R4)
ip route 1.1.1.0 255.255.255.0 10.1.34.3
ip route 2.2.2.0 255.255.255.0 10.1.34.3
ip route 3.3.3.0 255.255.255.0 10.1.34.3
➢ Post-implementation Results:
● See if you can view all networks as “S” in your routing tables
o On all Routers:
▪ sh ip route static
➢ Diagram:
➢ Implementation Steps:
o LON (R1)
int gi 0/1
ip add 10.1.15.1 255.255.255.0
no shut
o NYK(R2)
ip route 0.0.0.0 0.0.0.0 10.1.12.1
o PAR (R3)
ip route 0.0.0.0 0.0.0.0 10.1.23.2
o DUB (R4)
ip route 0.0.0.0 0.0.0.0 10.1.34.3
o ISP (R5)
int lo 5
ip addr 5.5.5.5 255.255.255.255
int gi 0/1
ip add 10.1.15.5 255.255.255.0
no shut
➢ Post-implementation Results:
● See if you can view the static Default Route in your routing table
o On Corp Router:
▪ sh ip route static
Note: All the rest of the routers will not be able to ping this Internet host and can be achieved if you
enable any IGP in the network
2. RIP
➢ Diagram:
2.1 Configure RIP as the routing protocol in your network
➢ Implementation Steps:
o LON (R1)
router rip
version 2
network 1.0.0.0
network 10.0.0.0
no auto-summary
o NYK (R2)
router rip
version 2
network 2.2.2.0
network 10.0.0.0
no auto-summary
o PAR(R3)
router rip
version 2
network 3.3.3.0
network 10.0.0.0
no auto-summary
o DUB(R4)
router rip
version 2
network 4.4.4.0
network 10.0.0.0
no auto-summary
➢ Post-implementation Results:
● See if you can view all non-directly connected networks as “R” in your
routing tables
o On all Routers:
▪ sh ip route rip
-same diagram as in 1-
➢ Implementation Steps:
o LON (R1)-DUB(R4):
router rip
timers basic 50 150 150 400
➢ Post-implementation Results:
● See if you can view all non-directly connected networks as “R” in your
routing tables
o On all Routers:
▪ sh ip route rip
2.3 Configure Default Routing in RIP using all the following methods
-same diagram as in 1-
➢ Implementation Steps:
o LON (R1):
router rip
default-information originate
➢ Post-implementation Results:
sh ip rip database
sh ip protocol
➢ Diagram:
----same diagram----
➢ Implementation Steps:
o LON (R1):
router rip
red static
➢ Post-implementation Results:
● Ping all the IPs on the local segments
o On all Routers:
▪ Ping a.b.c.d (across all the network)
● See if you can view all non-directly connected networks as “R” in your routing tables
o On all Routers:
▪ sh ip route rip
sh ip rip database
sh ip protocol
3. OSPF
3.1 Configure OSPF as the routing protocol of choice in your corporate in Area-0 (using a single
OSPF network command)
➢ Diagram:
➢ Implementation Steps:
o LON (R1)
router ospf 1
router-id 11.11.11.11
network 1.1.1.0 0.0.0.255 ar 0
network 10.1.0.0 0.0.255.255 ar 0
o NYK (R2)
router ospf 1
router-id 22.22.22.22
network 2.2.2.0 0.0.0.255 ar 0
network 10.1.0.0 0.0.255.255 ar 0
o PAR(R3)
router ospf 1
router-id 33.33.33.33
network 3.3.3.0 0.0.0.255 ar 0
network 10.1.0.0 0.0.255.255 ar 0
o DUB(R4)
router ospf 1
router-id 44.44.44.44
network 4.4.4.0 0.0.0.255 ar 0
network 10.1.0.0 0.0.255.255 ar 0
➢ Post-implementation Results:
● Ping all the IPs on the local segments
o On all Routers:
▪ Ping a.b.c.d (across all the network)
● See if you can view all non-directly connected networks as “O” in your routing tables
o On all Routers:
▪ sh ip route ospf
3.2 Configure OSPF as the routing protocol using multi-area as (as per the table below) is the
requirement to reduce the processing overhead on all the routers
-same diagram as in 1-
Interfac
Routers es Areas
gi 0/2 area 1
LON (R1)
gi 0/2 area 2
NYK (R2)
gi 0/2 area 3
PAR(R3)
gi 0/2 area 4
DUB(R4)
➢ Implementation Steps:
o LON (R1)
router ospf 1
network 1.1.1.254 0.0.0.0 area 1
o NYK (R2)
router ospf 1
network 2.2.2.254 0.0.0.0 area 2
o PAR(R3)
router ospf 1
network 3.3.3.254 0.0.0.0 area 3
o DUB(R4)
router ospf 1
network 4.4.4.254 0.0.0.0 area 4
➢ Post-implementation Results:
● See if you can view all non-directly connected networks as “R” in your routing tables
o On all Routers:
▪ sh ip route ospf
● See and practise the following commands (and compare the differences with the last lab’s such
results)
o On all Routers:
▪ Sh ip ospf neighbour
▪ sh ip ospf database
▪ sh ip route
3.3 Configure OSPF clear text authentication (on LON to NYK link)
➢ Implementation Steps:
o LON (R1)
interface GigabitEthernet0/0
ip ospf authentication
ip ospf authentication-key ospf123
!
o NYK (R2)
interface GigabitEthernet0/0
ip ospf authentication
ip ospf authentication-key ospf123
!
➢ Post-implementation Results:
3.4 Configure OSPF md5 authentication (between NYK & PAR link)
➢ Implementation Steps:
o NYK (R2)
interface GigabitEthernet0/1
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ospf456
!
o PAR(R3)
interface GigabitEthernet0/1
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ospf456
➢ Post-implementation Results:
➢ Implementation Steps:
o LON (R1)
interface GigabitEthernet0/1
ip ospf hello-interval 20
ip ospf dead-interval 80
!
o DUB (R4)
interface GigabitEthernet0/1
ip ospf hello-interval 20
ip ospf dead-interval 80
!
➢ Post-implementation Results:
➢ Implementation Steps:
o NYK (R2)
interface GigabitEthernet0/1
ip ospf cost 5
!
o LON(R1)
interface GigabitEthernet0/1
ip ospf cost 5
!
➢ Post-implementation Results:
➢ Diagram:
➢ Implementation Steps:
o R1
int lo 1
ip address 1.1.1.1 255.255.255.0
router ospf 1
router-id 11.11.11.11
network 1.1.1.0 0.0.0.255 ar 0
network 100.1.1.0 0.0.255.255 ar 0
o R2
int lo 1
ip address 2.2.2.2 255.255.255.0
router ospf 1
router-id 22.22.22.22
network 2.2.2.0 0.0.0.255 ar 0
network 100.1.1.0 0.0.255.255 ar 0
o R3
int lo 1
ip address 3.3.3.3 255.255.255.0
router ospf 1
router-id 33.33.33.33
network 3.3.3.0 0.0.0.255 ar 0
network 100.1.1.0 0.0.255.255 ar 0
o R4
int lo 1
ip address 4.4.4.4 255.255.255.0
router ospf 1
router-id 44.44.44.44
network 4.4.4.0 0.0.0.255 ar 0
network 100.1.1.0 0.0.255.255 ar 0
➢ Post-implementation Results:
● Verification command
● On all Routers:
o sh ip ospf neighbor
You should see all the 3 neighbors per router and try to discover the DR and BDR routers amongst all
the 4 routers; DROs will not form any neighborship within each other but with DR/BDR
● Ping all the IPs on the local segments
o On all Routers:
▪ Ping a.b.c.d (across all the network)
● See if you can view all non-directly connected networks as “R” in your routing tables
o On all Routers:
▪ sh ip route ospf
4. EIGRP
3.4 Configure EIGRP across your network
➢ Implementation Steps:
o LON (R1)
router eigrp 1
network 1.0.0.0
network 10.1.12.0 0.0.0.255
network 10.1.14.0 0.0.0.255
no auto-summary
o NYK (R2)
router eigrp 1
network 2.2.2.0
network 10.1.12.0 0.0.0.255
network 10.1.23.0 0.0.0.255
no auto-summary
o PAR(R3)
router eigrp 1
network 3.3.3.0
network 10.1.23.0 0.0.0.255
network 10.1.34.0 0.0.0.255
no auto-summary
o DUB(R4)
router eigrp 1
network 10.1.14.0 0.0.0.255
network 10.1.34.0 0.0.0.255
no auto-summary
➢ Post-implementation Results:
➢ Implementation Steps:
o LON (R1)
interface Gi0/0
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
o NYK (R2)
interface Gi0/0
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
interface Gi0/1
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
o PAR(R3)
interface Gi0/1
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
interface Gi1/0
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
o DUB(R4)
interface Gi1/0
ip hello-interval eigrp 100 30
ip hold-time eigrp 100 120
➢ Post-implementation Results:
3.6 Configure the EIGRP metric such that we ONLY use bandwidth and not the default Bandwidth
+ Delay
-diagram same as before_
➢ Implementation Steps:
o LON (R1)-DUB(R4)
router eigrp 1
metric weights 0 1 0 0 0 0
➢ Post-implementation Results:
➢ Implementation Steps:
o LON (R1)
interface Loopback20
ip address 1.1.0.1 255.255.255.0
!
interface Loopback21
ip address 1.1.1.1 255.255.255.0
!
interface Loopback22
ip address 1.1.2.1 255.255.255.0
!
interface Loopback23
ip address 1.1.3.1 255.255.255.0
!
interface Gi0/0
ip summary-address eigrp 1 1.1.0.0 255.255.252.0
!
➢ Post-implementation Results:
Note: Clear the existing lab configs before proceeding to next lab
➢ Implementation Steps:
o LON (R1)
interface Loopback1
ip address 1.1.1.254 255.255.255.0
interface Gi0/0
ip address 10.1.12.1 255.255.255.0
speed 100
full-duplex
o NYK (R2)
interface Loopback2
ip address 2.2.2.254 255.255.255.0
interface Gi0/0
ip address 10.1.12.2 255.255.255.0
speed 100
full-duplex
interface Gi1/0
ip address 10.1.24.2 255.255.255.0
speed 100
full-duplex
interface Gi0/1
ip address 10.1.23.2 255.255.255.0
speed 100
full-duplex
o PAR(R3)
interface Loopback3
ip address 3.3.3.254 255.255.255.0
interface Gi0/1
ip address 10.1.23.3 255.255.255.0
speed 100
full-duplex
interface Gi2/0
ip address 10.1.100.3 255.255.255.0
speed 100
full-duplex
o DUB(R4)
interface Loopback4
ip address 4.4.4.254 255.255.255.0
interface Gi1/0
ip address 10.1.24.2 255.255.255.0
speed 100
full-duplex
interface Gi2/0
ip address 10.1.100.4 255.255.255.0
speed 100
full-duplex
o R5
interface Loopback5
ip address 5.5.5.5 255.255.255.0
interface Gi2/0
ip address 10.1.100.5 255.255.255.0
speed 100
full-duplex
➢ Post-implementation Results:
o LON (R1)-R5:
▪ show ip route eigrp
Set metric weights in such a way that only Delay is considered in the “composite metric”
➢ Implementation Steps:
o LON (R1)-R5:
router eigrp 1
metric weights 0 0 0 1 0 0
Post-implementation Results:
o LON (R1)-R5:
▪ show ip route eigrp
▪ show ip protocol
➢ Implementation Steps:
o LON (R1):
interface lo 1
delay 1
interface gi 0/0
delay 1
o NYK (R2):
interface gi 0/0
delay 1
interface gi 0/1
delay 1
interface gi1/0
delay 2
o PAR(R3):
interface gi 0/1
delay 1
interface gi 0/1
delay 1
o DUB(R4):
interface gi1/0
delay 2
interface gi 0/1
delay 1
o R5:
interface lo 5
delay 1
interface gi 0/1
delay 1
➢ Post-implementation Results:
o LON (R1)-R5:
▪ show ip route eigrp
▪ show ip protocol
▪ sh int gi 0/x | i DLY (can be verified across the network, should be taken as tens
of whatever you entered the delay value)
➢ Implementation Steps:
o NYK (R2):
router eigrp 1
variance 2
Post-implementation Results:
o NYK (R2):
show ip protocol | i variance
sh ip route 5.0.0.0
sh ip eigrp topology 5.0.0.0/8
5. ACL
5.1 Configure “Standard Numbered Access List” to block traffic from LON to DUB (You are allowed
to use any IGP <RIP/OSPF/EIGRP>)
o LON (R1)
interface Gi0/2
ip access-group 1 out
o DUB (R4)
interface Gi0/2
ip access-group 1 out
➢ Post-implementation Results:
You should not see network 4.4.4.0 and 1.1.1.0 on routers R1 & R4 respectively
5.2 Configure “Extended Numbered Access List” to permit traffic to NYK Server 2.2.2.2
➢ Implementation Steps:
o NYK (R2)
interface GigabitEthernet0/2
ip access-group 111 out
!
access-list 111 permit ip any host 2.2.2.1
access-list 111 permit ip any host 2.2.2.3
➢ Post-implementation Results:
o DUB(R4):
▪ Ping 1.1.1.254 source gi 0/2 (should not be successful)
➢ Implementation Steps:
o LON (R1)
router ospf 1
net 0.0.0.0 255.255.255.255 ar 0
interface Gi0/0
ip access-group block4x in
o NYK (R2)-DUB(R4)
router ospf 1
net 0.0.0.0 255.255.255.255 ar 0
➢ Post-implementation Results:
5.4 Configure “Extended Named Access List” to block “icmp” to the router in Paris
➢ Implementation Steps:
o PAR (R3)
➢ Post-implementation Results:
➢ Implementation Steps:
o NYK(R2)
➢ Post-implementation Results:
6. NAT
6.1 Configuring Static NAT on your CPE Internet Hosts can use your hosted Gaming Servers:
➢ Implementation Steps:
o CPE:
hostname CPE
interface Gi0/0
description *** interface towards ISP ***
ip address 10.1.12.1 255.255.255.0
duplex full
speed 100
ip nat outside
interface Gi0/1
description **** towards Users ****
ip address 1.1.1.254 255.255.255.0
duplex full
speed 100
ip nat inside
o ISP
hostname CPE
interface Gi0/0
description *** interface towards CPE ***
ip address 10.1.12.2 255.255.255.0
duplex full
speed 100
interface Gi0/2
description *** towards INTERNET ****
ip address 2.1.1.254 255.255.255.0
duplex full
speed 100
➢ Post-implementation Results:
6.2 Ensure the users at your home can use Internet (Using the interface IP)
---same diagram as before----
➢ Implementation Steps:
o CPE
➢ Post-implementation Results:
6.4 Configuring Dynamic NAT on your company router (NYK (R2)) so that all the PCs in your LAN
can get to the internet – a new pool 100.1.1.0 has been allocated to fulfil your requirements,
you are allowed to add a static route on LON (R1) (ISP) router
---same diagram as before----
➢ Implementation Steps:
o CPE
ip nat pool NAT-POOL 10.1.12.11
10.1.12.15 prefix-length 24
➢ Post-implementation Results:
➢ Diagram:
1.6.1 How to Set Hostname and Configure Console Password
➢ Implementation Steps:
hostname CISCO
line console 0
login
password cisco123
➢ Post-implementation Results:
➢ Implementation Steps:
enable password cisco
enable secret Kamran ; if configured alongwith the clear text
password, Encrypted password has got more Priority
➢ Post-implementation Results:
● Still “Consolled” into the switch, enter the privileged exec
mode using the password (2nd level) as is shown in your lab
➢ Implementation Steps:
line console 0
login local ; use login local in place of “login” only
➢ Post-implementation Results:
● Again, still “Consolled” into the switch, enter the user exec
mode using the password (1st level) as is shown in lab1.4.1 but
you would be prompted for a username/pw before entering this
mode, and then you would have to enter the 2nd level password
as is shown in lab1.4.2
1.6.4 How to Set Telnet password (and the 2nd level password)
➢ Implementation Steps:
line vty 0 15
login
password cisco
➢ Post-implementation Results:
● Telnet into the switch, enter the user exec mode using the
password (1st level) as is shown in this lab & then enter
privilege exec mode using the password as is shown in the
later implementation steps
● SW:
o sh runn
o show ip interface vlan 1
o show ip interface brief
➢ Implementation Steps:
LON-ASW1:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
int fa 0/2
switchport mode access
switchport access vlan 20
int fa 0/3
switchport mode access
switchport access vlan 30
LON-ASW2:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
int fa 0/1
switchport mode access
switchport access vlan 10
int fa 0/2
switchport mode access
switchport access vlan 20
int fa 0/3
switchport mode access
switchport access vlan 30
LON-DSW1:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
int range gi 0/1-2
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk encap dot1q
switchport trunk allowed vlan 10,20,30
LON-DSW2:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
➢ Post-implementation Results:
● SWA-SWB:
sh vlans
sh interface trunk
You should see all the 3 VLANs defined and proper mapping between ports to VLANs; Trunks should
have all of these VLANs allowed through them
7.2 Configure VTP as follows:
DSW1
➢ Diagram:
➢ Implementation Steps:
LON-ASW1:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
int range gi 0/1-2
switchport mode trunk
switchport trunk encap dot1q
switchport trunk allowed vlan 10,20,30
int fa 0/1
switchport mode access
switchport access vlan 10
int fa 0/2
switchport mode access
switchport access vlan 20
int fa 0/3
switchport mode access
switchport access vlan 30
LON-ASW2:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
int fa 0/1
switchport mode access
switchport access vlan 10
int fa 0/2
switchport mode access
switchport access vlan 20
int fa 0/3
switchport mode access
switchport access vlan 30
LON-DSW1:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
LON-DSW2:
vlan 10
name HR
vlan 20
name IT
vlan 30
name Sales
➢ Post-implementation Results:
● SWA-SWB:
sh vlans
sh interface trunk
You should see all the 3 VLANs defined and proper mapping between ports to VLANs; Trunks should
have all of these VLANs allowed through them
7.3 Port Security (On PC-1 on Switch-A)
➢ Diagram:
---same diagram as before---
➢ Implementation Steps:
sh mac-address-table ; to view the current mac-address of PC1 (on
Switch-A) & note it down
int Gi 0/1
switchport mode access
switchport port-security
switchport port-security maximum 1
switchport port-security mac-address sticky
switchport port-security violation shutdown
➢ Post-implementation Results:
sh port-security interface Gi 0/1
sh ip interface Gi 0/1
Now Change the PC on Fast 0/1 & connect another PC (with an obvious
different MAC-Address)
sh port-security
Note: You should see the interface in “down” state as is shown above
8. STP (PVST)
➢ Diagram:
➢ Implementation Steps:
o LON-ASW1:
spanning-tree mode pvst
o LON-ASW2:
spanning-tree mode pvst
➢ Post-implementation Results:
9. FHRP
9.1 Configuring HSRP
➢ Diagram:
➢ Implementation Steps:
o LON (R1)
interface Gi0/0
ip address 1.1.1.252 255.255.255.0
duplex auto
speed auto
standby 1 ip 1.1.1.254
standby 1 priority 120
standby 1 preempt
interface Gi0/1
ip address 10.1.13.1 255.255.255.0
duplex auto
speed auto
o NYK (R2)
interface Gi0/0
ip address 1.1.1.253 255.255.255.0
duplex auto
speed auto
standby 1 ip 1.1.1.254
standby 1 priority 115
standby 1 preempt
interface Gi1/0
ip address 10.1.23.2 255.255.255.0
duplex auto
speed auto
o PAR(R3)
interface Gi0/1
ip address 10.1.13.3 255.255.255.0
duplex auto
speed auto
interface Gi1/0
ip address 10.1.23.3 255.255.255.0
duplex auto
speed auto
➢ Post-implementation Results:
o LON (R1) & NYK (R2):
▪ show standby brief
▪ show standby
▪ sh stand gi 0/0 | i time ; to note down the Hello/Dead
intervals which we would tweak in the following lab
Hello time 3 sec, hold time 10 sec
▪ ping 2.1.1.3
o PAR(R3)
▪ ping 1.1.1.254
▪ ping 1.1.1.2
9.2 Creating HSRP Hello & Dead Intervals (5secs & 15sec respct.)
➢ Diagram:
---same as before---
➢ Implementation Steps:
o LON (R1)
interface Gi0/0
standby 1 timers 5 15
o NYK (R2)
interface Gi0/0
standby 1 timers 5 15
➢ Post-implementation Results:
o LON (R1) & NYK (R2):
▪ sh stand gi 0/0 | i time ; to note down the Hello/Dead
intervals which we would tweak in the following lab
Hello time 5 sec, hold time 15 sec
▪ ping 2.1.1.3
o PAR(R3)
▪ ping 1.1.1.254
▪ ping 1.1.1.2
➢ Diagram:
---same as before---
➢ Implementation Steps:
o LON (R1)
interface Gi0/0
standby 1 authentication hello
o NYK (R2)
interface Gi0/0
standby 1 authentication hello
➢ Post-implementation Results:
o LON (R1) & NYK (R2):
▪ sh standby | i Authentication
Authentication text "hello"
▪ ping 2.1.1.3
o PAR(R3)
▪ ping 1.1.1.254
▪ ping 1.1.1.2
10. NTP
10.1 Configuring IP Addressing as is shown in the figure & configure
any form of Routing across the network
➢ Diagram:
➢ Implementation Steps:
o LON (R1)
interface loopback 0
ip address 1.1.1.254 255.255.255.0
interface Gi0/1
ip address 10.1.13.1 255.255.255.0
duplex auto
speed auto
interface Gi2/0
ip address 10.1.12.1 255.255.255.0
duplex auto
speed auto
router ospf 1
0.0.0.0 255.255.255.255 area 0
o NYK (R2)
interface Gi2/0
ip address 10.1.12.2 255.255.255.0
duplex auto
speed auto
router ospf 1
0.0.0.0 255.255.255.255 area 0
o PAR(R3)
interface Gi0/1
ip address 10.1.13.3 255.255.255.0
duplex auto
speed auto
router ospf 1
0.0.0.0 255.255.255.255 area 0
➢ Post-implementation Results:
o NYK (R2)-PAR(R3):
▪ Ping 1.1.1.254
10.2 Configuring NTP Server on LON (R1) AND NYK (R2) & PAR(R3)
should be configured as NTP Clients
➢ Diagram:
---same as above---
➢ Implementation Steps:
o LON (R1)
clock set 12:05:00 13 MAR 2014 ; privilege Exec command
ntp master 2
o NYK (R2)
ntp server 1.1.1.254 key 1
o PAR(R3)
ntp server 1.1.1.254 key 1
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
▪ sh ntp status
▪ sh ntp associations
▪ sh clock
➢ Diagram:
---same as above---
➢ Implementation Steps:
o LON (R1)
ntp authentication-key 1 md5 ntp
o NYK (R2)
ntp authentication-key 1 md5 ntp
ntp authenticate
ntp trusted-key 1
ntp server 1.1.1.254 key 1
o PAR(R3)
ntp authentication-key 1 md5 ntp
ntp authentication-key 1 md5 ntp
ntp authenticate
ntp trusted-key 1
ntp server 1.1.1.254 key 1
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
▪ sh ntp status
▪ sh ntp associations
▪ sh clock
➢ Implementation Steps:
o PAR(R3):
service dhcp
interface Gi0/0
ip address 10.1.1.254 255.255.255.0
no shut
➢ Post-implementation Results:
o Verifying DHCP related info
sh ip dhcp binding
sh ip dhcp server statistics
o See if connected PCs obtain the IP Address dynamically
ALL PCs: (should be allocated IP Addresses)
12. SNMP
➢ Diagram:
➢ Implementation Steps:
o LON (R1):
interface Loopback0
ip address 11.11.11.11 255.255.255.0
!
interface Gi0/0
ip address 1.1.1.254 255.255.255.0
duplex auto
speed auto
!
interface Gi0/1
ip address 10.1.1.1 255.255.255.0
duplex auto
speed auto
!
snmp-server community testro RO
snmp-server community testrw RW
o NYK (R2):
interface Loopback0
ip address 22.22.22.22 255.255.255.0
!
interface Gi0/0
ip address 2.1.1.254 255.255.255.0
duplex auto
speed auto
!
interface Gi0/1
ip address 10.1.1.2 255.255.255.0
duplex auto
speed auto
!
snmp-server community testro RO
snmp-server community testrw RW
o SW1:
interface Vlan1
ip address 1.1.1.253 255.255.255.0
o SW2:
interface Vlan1
ip address 2.1.1.253 255.255.255.0
➢ Post-implementation Results:
o Any PC:
--- Open up the “MIB Browser” in “Desktop” Option in Packet Tracer
---Go to “Advanced”- set the Loopback IP Address of any Cisco Device that you want to
monitor/configure from MIB
13.IPV6
➢ Diagram:
➢ Implementation Steps:
o LON (R1):
ipv6 unicast-routing
interface Gi0/0
ipv6 enable
o NYK (R2):
ipv6 unicast-routing
interface Gi0/0
ipv6 enable
➢ Post-implementation Results:
o show ipv6 interface brief
o show interface gi 0/0
o LON (R1):
ipv6 unicast-routing
interface Gi0/0
ipv6 address 2001:1:1:12::1/64
ipv6 address fe80:1:1:12::1 linklocal
o NYK (R2):
ipv6 unicast-routing
interface Gi0/0
ipv6 address 2001:1:1:12::2/64
ipv6 address fe80:1:1:12::2 linklocal
➢ Post-implementation Results:
o LON (R1):
o Ping 2001:1:1:12::2
o Show ipv6 neighbors
o NYK (R2):
o Ping 2001:1:1:12::1
o Show ipv6 neighbors
13.3 Configure Loopback0 interfaces on both the routers as follows such that the
routers should assign the host portion of the IPV6 address automatically:
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
interface lo0
ipv6 address 2000:1:1:1::/64 eui64
o NYK (R2):
interface lo0
ipv6 address 2000:2:2:2::/64 eui64
➢ Post-implementation Results:
o LON (R1)-NYK (R2):
o Ping address ; the far end host address can be seen from “show ipv6 interface brief”
command
o Show ipv6 neighbors
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
interface lo0
ipv6 address 2000:1:1:1::1/64
o NYK (R2):
interface lo0
ipv6 address 2000:2:2:2::2/64
➢ Post-implementation Results:
o LON (R1):
o Ping 2000:2:2:2::2
o Show ipv6 neighbors
o NYK (R2):
o Ping 2000:1:1:1::1
o Show ipv6 neighbors
13.5 Configure host entry for the Loopback0’s on both the routers so that each router
can ping the other host and without using the IPV6 address
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
ipv6 host NYK (R2)Lo0 2000:1:1:1::1
o NYK (R2):
ipv6 host LON (R1)Lo0 2000:2:2:2::2
➢ Post-implementation Results:
o LON (R1):
o Ping NYK (R2)Lo0
o Show ipv6 neighbors
o NYK (R2):
o Ping LON (R1)Lo0
o Show ipv6 neighbors
14.OSPFV3
Interfac N
Router e IPV6 Address M
LON Lo1 2000:1:1:1::1 /64
2000:11:11:11::1
(R1) Lo11 1 /64
Gi 0/0 2000:1:1:12::1 /64
Lo2 2000:2:2:2::2 /64
2000:22:22:22::2
NYK (R2) Lo22 2 /64
Fa0/0 2000:1:1:12::2 /64
Fa0/1 2000:1:1:23::2 /64
Lo3 2000:3:3:3::3 /64
2000:33:33:33::3
PAR(R3) Lo33 3 /64
Gi 0/1 2000:1:1:23::3 /64
Fa1/0 2000:1:1:34::3 /64
Lo4 2000:4:4:4::4 /64
2000:44:44:44::4
DUB(R4) Lo44 4 /64
Fa1/0 2000:1:1:34::4 /64
➢ Diagram:
➢ Implementation Steps:
o LON (R1):
interface Loopback1
ipv6 address 2000:1:1:1::1/64
!
interface Loopback11
no ip address
ipv6 address 2000:11:11:11::11/64
!
interface Gi0/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:12::1/64
o NYK (R2):
interface Gi0/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:12::2/64
interface Gi0/1
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:23::2/64
o PAR(R3):
interface Loopback3
no ip address
ipv6 address 2000:3:3:3::3/64
ipv6 ospf 1 area 0
interface Loopback33
no ip address
ipv6 address 2000:33:33:33::33/64
interface Gi0/1
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:23::3/64
interface Gi1/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:34::3/64
o DUB(R4):
interface Loopback4
no ip address
ipv6 address 2000:4:4:4::4/64
interface Loopback44
no ip address
ipv6 address 2000:44:44:44::44/64
➢ Post-implementation Results:
LON (R1)-DUB(R4):
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
ipv6 router ospf 1
interface Loopback1
ipv6 address 2000:1:1:1::1/64
ipv6 ospf 1 area 0
!
interface Loopback11
no ip address
ipv6 address 2000:11:11:11::11/64
ipv6 ospf 1 area 0
!
interface Gi0/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:12::1/64
ipv6 ospf 1 area 0
o NYK (R2):
ipv6 router ospf 1
interface Gi0/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:12::2/64
ipv6 ospf 1 area 0
interface Gi0/1
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:23::2/64
ipv6 ospf 1 area 0
o PAR(R3):
ipv6 router ospf 1
interface Loopback3
no ip address
ipv6 address 2000:3:3:3::3/64
ipv6 ospf 1 area 0
interface Loopback33
no ip address
ipv6 address 2000:33:33:33::33/64
ipv6 ospf 1 area 0
interface Gi0/1
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:23::3/64
ipv6 ospf 1 area 0
interface Gi1/0
no ip address
duplex auto
speed auto
ipv6 address 2000:1:1:34::3/64
ipv6 ospf 1 area 0
o DUB(R4):
ipv6 router ospf 1
interface Loopback4
no ip address
ipv6 address 2000:4:4:4::4/64
ipv6 ospf 1 area 0
interface Loopback44
no ip address
ipv6 address 2000:44:44:44::44/64
ipv6 router ospf 1
➢ Post-implementation Results:
LON (R1)-DUB(R4):
Show ipv6 ospf interface interface
show ipv6 ospf neighbour
show ipv6 ospf database
sh ipv6 route ospf
ping address (across all the links)
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
interface Loopback1
ipv6 ospf cost 10
➢ Post-implementation Results:
NYK (R2)-DUB(R4):
sh ipv6 route ospf ; compare pre-impl. & post-implementation metric of Lo1
ping address (across all the links)
14.4 Changing OSPF Hello & Dead-interval timers to 15secs & 60secs
respectively on link between LON (R1) & NYK (R2)
➢ Diagram:
---same as before----
➢ Implementation Steps:
o LON (R1):
interface Gi0/0
ip ospf dead-interval 60
ipv6 ospf hello-interval 15
o NYK (R2):
interface Gi0/0
ip ospf dead-interval 60
ipv6 ospf hello-interval 15
➢ Post-implementation Results:
LON (R1)-NYK (R2):
15.EIGRPV3
➢ Diagram:
➢ Implementation Steps:
➢ Post-implementation Results:
16.PPP
16.1 Configuring PPP across the WAN link with the following IP
Addresses
➢ Diagram:
➢ Implementation Steps:
o LON (R1):
interface Serial1/0
ip address 10.1.12.1 255.255.255.0
encapsulation ppp
clock rate 56000
ppp authentication chap pap
o NYK (R2):
interface Serial1/0
ip address 10.1.12.2 255.255.255.0
encapsulation ppp
clock rate 56000
ppp authentication chap pap
➢ Post-implementation Results:
o LON (R1)-NYK (R2):
sh controllers s1/0 | i clock
sh int s 1/0
sh ip route connected
➢ Diagram:
---same as before---
➢ Implementation Steps:
o LON (R1):
interface Serial1/0
ppp authentication chap pap
o NYK (R2):
interface Serial1/0
ppp authentication chap pap
17.FR
➢ Diagram:
➢ Implementation Steps:
➢ Post-implementation Results:
➢ Diagram:
➢ Implementation Steps:
o Configure FR Switch (with the following Mappings):
o LON (R1):
interface Serial1/1
ip address 10.1.123.1 255.255.255.0
encapsulation frame-relay
o NYK (R2):
interface Serial1/1
ip address 10.1.123.2 255.255.255.0
encapsulation frame-relay
o PAR(R3):
interface Serial1/1
ip address 10.1.123.3 255.255.255.0
encapsulation frame-relay
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
sh frame-relay map ; you should see DYNAMIC mappings for both of the
neighbour routers
sh frame-relay map; you should see “PVC STATUS = ACTIVE” for the 2
neighbouring router’s PVCs
Ping w.x.y.z; You should be able to ping across WAN Links over FR
17.2 Configuring FR HNS Connection (with FR Inverse ARP disabled &
manually creating the PVCs)
➢ Diagram:
- Same –
➢ Implementation Steps:
o Configure FR Switch (with the following Mappings):
o LON (R1):
interface Serial1/1
ip address 10.1.123.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.3 103
frame-relay map ip 10.1.123.2 102
no frame-relay inverse-arp
o NYK (R2):
interface Serial1/1
ip address 10.1.123.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.1 201
no frame-relay inverse-arp
o PAR(R3):
interface Serial1/1
ip address 10.1.123.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.1 301
no frame-relay inverse-arp
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
sh frame-relay map ; you should see STATIC mappings for both of the
neighbour routers
sh frame-relay map; you should see “PVC STATUS = ACTIVE” for the 2
neighbouring router’s PVCs
Ping w.x.y.z; The spokes should not be able to ping within themselves but
would do it with the HUB only, Hub should be able to ping both the spokes
17.2 Configuring FR MESH Connection (with FR Inverse ARP disabled
& manually creating the PVCs)
➢ Diagram:
- Same –
➢ Implementation Steps:
o Configure FR Switch (with the following Mappings):
o LON (R1):
interface Serial1/1
ip address 10.1.123.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.3 103
frame-relay map ip 10.1.123.2 102
no frame-relay inverse-arp
o NYK (R2):
interface Serial1/1
ip address 10.1.123.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.1 201
frame-relay map ip 10.1.123.3 203
no frame-relay inverse-arp
o PAR(R3):
interface Serial1/1
ip address 10.1.123.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 10.1.123.2 302
frame-relay map ip 10.1.123.1 301
no frame-relay inverse-arp
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
sh frame-relay map ; you should see STATIC mappings for both of the
neighbour routers
sh frame-relay map; you should see “PVC STATUS = ACTIVE” for the 2
neighbouring router’s PVCs
Ping w.x.y.z; All the WAN Links from every router should be able to Ping
➢ Diagram:
➢ Implementation Steps:
o Configure FR Switch (with the following Mappings):
o LON (R1):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.12 point-to-point
ip address 10.1.12.1 255.255.255.0
frame-relay interface-dlci 102
!
interface Serial1/1.13 point-to-point
ip address 10.1.13.1 255.255.255.0
frame-relay interface-dlci 103
o NYK (R2):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.21 point-to-point
ip address 10.1.12.2 255.255.255.0
frame-relay interface-dlci 201
!
interface Serial1/1.23 point-to-point
ip address 10.1.23.2 255.255.255.0
frame-relay interface-dlci 203
o PAR(R3):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.31 point-to-point
ip address 10.1.13.3 255.255.255.0
frame-relay interface-dlci 301
!
interface Serial1/1.32 point-to-point
ip address 10.1.23.3 255.255.255.0
frame-relay interface-dlci 302
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
sh frame-relay map ; you should see key work “BROADCAST” mappings for
both of the neighbour routers
sh frame-relay map; you should see “PVC STATUS = ACTIVE” for the 2
neighbouring router’s PVCs
Ping w.x.y.z; Only the WAN Links b/w A<->B & A<-> C should work
17.5 Configuring FR MESH Point-to-point Connections (without FR
INV ARP)
➢ Diagram:
➢ Implementation Steps:
o Configure FR Switch (with the following Mappings):
o LON (R1):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.12 point-to-point
ip address 10.1.12.1 255.255.255.0
frame-relay interface-dlci 102
!
interface Serial1/1.13 point-to-point
ip address 10.1.13.1 255.255.255.0
frame-relay interface-dlci 103
o NYK (R2):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.21 point-to-point
ip address 10.1.12.2 255.255.255.0
frame-relay interface-dlci 201
!
interface Serial1/1.23 point-to-point
ip address 10.1.23.2 255.255.255.0
frame-relay interface-dlci 203
o PAR(R3):
interface Serial1/1
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial1/1.31 point-to-point
ip address 10.1.13.3 255.255.255.0
frame-relay interface-dlci 301
!
interface Serial1/1.32 point-to-point
ip address 10.1.23.3 255.255.255.0
frame-relay interface-dlci 302
➢ Post-implementation Results:
o LON (R1)-PAR(R3):
sh frame-relay map ; you should see key work “BROADCAST” mappings for
both of the neighbour routers
sh frame-relay map; you should see “PVC STATUS = ACTIVE” for the 2
neighbouring router’s PVCs
Ping w.x.y.z; All the WAN Links from every router should be able to Ping