Click Image to enlarge
I'll Start Releasing List Of Tickets One By One Starting from Tomorrow which you will find right at the bottom after initials. Detailed Solution Guide will be posted Once I finish Listing all tickets here which gonna be over 20 :-)
For getting GNS Topology of lab send me an email on my email id given in my profile above.
BB#sh ver | i IOS
Cisco IOS Software, 3700 Software (C3725-ADVENTERPRISEK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
*** Initials ***
(R1)
en
!
conf t
!
ho R1
!
no ip domain-lo
!
int lo0
ip add 1.1.0.1 255.255.255.0
exit
!
int lo1
ip add 1.1.1.1 255.255.255.0
exit
!
int lo2
ip add 1.1.2.1 255.255.255.0
exit
!
int lo3
ip add 1.1.3.1 255.255.255.0
exit
!
int lo4
ip add 1.1.4.1 255.255.255.0
exit
!
int s0/0
en f
no sh
exit
!
int s0/0.1 m
ip add 123.0.0.1 255.255.255.0
no frame inv
frame map ip 123.0.0.2 102 b
frame map ip 123.0.0.3 103 b
exit
!
int f0/0
ip add 15.15.15.2 255.255.255.0
no sh
exit
!
int s0/1
en f
no sh
exit
!
int s0/1.1 p
ip add 17.17.17.1 255.255.255.0
frame interface-dlci 107
end
!
----------------------------
(R2)
en
!
conf t
!
ho R2
!
no ip domain-lo
!
int lo0
ip add 192.168.2.1 255.255.254.0
exit
!
int s0/0
ip add 123.0.0.2 255.255.255.0
en f
no frame inv
frame map ip 123.0.0.1 201 b
frame map ip 123.0.0.3 201
no sh
exit
!
int f0/0
ip add 203.203.203.2 255.255.255.0
no sh
exit
!
int s0/1
ip add 192.168.4.2 255.255.254.0
no sh
end
!
------------------------------
(R3)
en
!
conf t
!
ho R3
!
no ip domain-lo
!
int lo0
ip add 3.3.3.3 255.255.255.0
exit
!
int s0/0
ip add 123.0.0.3 255.255.255.0
en f
no frame inv
frame map ip 123.0.0.1 301 b
frame map ip 123.0.0.2 301
no sh
exit
!
int f0/0
ip add 203.203.203.3 255.255.255.0
no sh
exit
!
int f0/1
ip add 83.83.83.3 255.255.255.0
no sh
end
!
---------------------------------
(R4)
en
!
conf t
!
ho R4
!
no ip domain-lo
!
int lo0
ip add 4.4.4.4 255.255.255.0
exit
!
int f0/0
ip add 203.203.203.4 255.255.255.0
no sh
end
!
--------------------------------
(R5)
en
!
conf t
!
ho R5
!
no ip domain-lo
!
int lo0
ip add 5.5.5.5 255.255.255.0
exit
!
int f0/0
ip add 15.15.15.5 255.255.255.0
no sh
exit
!
router rip
v 1
net 5.0.0.0
net 15.0.0.0
end
!
---------------------------------
(R6)
en
!
conf t
!
ho R6
!
no ip domain-lo
!
int lo0
ip add 6.6.6.6 255.255.255.0
exit
!
int f0/0
ip add 16.16.16.6 255.255.255.0
no sh
end
!
----------------------------------
(R7)
en
!
conf t
!
ho R7
!
no ip domain-lo
!
int s0/0
en f
no sh
exit
!
int s0/0.1 p
ip add 17.17.17.7 255.255.255.0
frame interface-dlci 701
exit
!
int f0/0
ip add 78.78.78.7 255.255.255.0
no sh
exit
!
int f0/1
ip add 150.150.150.7 255.255.255.0
no sh
exit
!
router eigrp 100
no au
net 150.150.150.7 0.0.0.0
redistribute rip metric 1544 20000 255 1 1500
exit
!
router rip
v 2
no au
net 17.0.0.0
net 78.0.0.0
redistribute eigrp 100 metric 7
end
!
------------------------------------
(R8)
en
!
conf t
!
ho R8
!
no ip domain-lo
!
int lo0
ip add 8.8.8.8 255.255.255.0
exit
!
int f0/0
ip add 78.78.78.8 255.255.255.0
no sh
exit
!
int f0/1
ip add 83.83.83.8 255.255.255.0
no sh
exit
!
int s0/0
ip add 200.200.200.8 255.255.255.0
en f
no frame inv
frame map ip 200.200.200.9 809 b
frame map ip 200.200.200.10 810 b
no sh
end
!
---------------------------------------
(R9)
en
!
conf t
!
ho R9
!
no ip domain-lo
!
int lo0
ip add 9.9.9.9 255.255.255.0
exit
!
int s0/0
ip add 200.200.200.9 255.255.255.0
en f
no frame inv
frame map ip 200.200.200.8 908 b
frame map ip 200.200.200.10 908
no sh
exit
!
int s0/1
ip add 109.109.109.9 255.255.255.0
no sh
exit
!
router ospf 1
net 9.9.9.9 0.0.0.0 a 0
net 109.109.109.9 0.0.0.0 a 0
end
!
---------------------------------------
(R10)
en
!
conf t
!
ho R10
!
no ip domain-lo
!
int lo0
ip add 10.10.10.10 255.255.255.0
exit
!
int s0/0
ip add 200.200.200.10 255.255.255.0
en f
no frame inv
frame map ip 200.200.200.8 108 b
frame map ip 200.200.200.9 108
no sh
exit
!
int s0/1
ip add 109.109.109.10 255.255.255.0
no sh
exit
!
router ospf 1
net 10.10.10.10 0.0.0.0 a 0
net 109.109.109.10 0.0.0.0 a 0
end
!
--------------------------------------
(R11)
en
!
conf t
!
ho R11
!
no ip domain-lo
!
int lo0
ip add 192.168.0.1 255.255.254.0
exit
!
int s0/0
ip add 192.168.4.1 255.255.254.0
no sh
end
!
--------------------------------------
(R12)
en
!
conf t
!
ho BB
!
no ip domain-lo
!
int lo0
ip add 100.100.0.1 255.255.255.0
exit
!
int lo1
ip add 100.100.1.1 255.255.255.0
exit
!
int lo2
ip add 100.100.2.1 255.255.255.0
exit
!
int lo3
ip add 100.100.3.1 255.255.255.0
exit
!
int lo4
ip add 100.100.4.1 255.255.255.0
exit
!
int lo5
ip add 100.100.5.1 255.255.255.0
exit
!
int f0/0
ip add 150.150.150.88 255.255.255.0
no sh
exit
!
router eigrp 100
net 100.0.0.0 0.255.255.255
net 150.150.150.88 0.0.0.0
no au
end
!
************************************
GNS Topology Downlaod link - Download NOW
*** Ticket 1 ***
-> 1.) R1-R2-R3 should Authenticate Each Other with Plain Text Authentication using
Password - "textauth". R1 should use Key-Chain "R1-R2" & Key No.1 ;
R2/R3 should use Key No. 2 for this with Key-Chain "R1-R2-R3" .
-> 2.) All Loopback Addresses should be reachable from each other .
-> 3.) All IP Addresses within this small network (R1, R2 & R3) should be
Pingable. No Redundant broadcast should occur on Frame-Relay DLCIs.
-------------------------------------------------------------------------------------
*** Ticket 2 ***
-> 1.) R8-R9-R10 should Authenticate Each Other with Secure Authentication using
Password - "secureauth". All router should use Key-Chain - "R8-R9-R10" &
Key "key 100".
-> 2.) All Loopback Addresses should be reachable from each other.
All IP Addresses within this small network (R8, R9 & R10) should be Pingable.
-> 3.) Make Sure R9 & R10 Always Prefer Frame-Relay Circuit in order to reach each
other's Loopbacks.
---------------------------------------------------------------------------------------------------------------------------------
*** Ticket 3 ***
-> 1.) R5 is running RIP Ver 1 , R1 is running RIP Ver 2 with R6 & R7. Establish
Connectivity Among these Routers.
-> 2.) Make Sure All Loopback Addresses should be reachable from each other -& 3.)
All IP Addresses within this small network (R1, R5, R6 & R7) should be Pingable.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Establish Connectivity between R2 and R11's Loopbacks.
-> 2.) Make Sure All Loopback Addresses should be reachable from each other
This ticket gonna make you crazy...
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) All R1's Loopbacks should be summarized into a single summary route as specific
as possible & advertised out to R2, R3 & R11
-> 2.) Make Sure necessary measures have been taken on R1 to avoid any routing loop
that may get caused because of this summary route.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make sure Summary Route received from R1 is appearing with Metric 10 over
R11, Don't make any changes on R1.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) All routes in routing table of R1 should be sent with additional metic of 5 to R7,
Only make changes on R1.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make Sure R11 doesn't install Route for subnet 78.78.78.0/24 into it's Local
Routing table, Only use of standard ACL is allowed for this purpose.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make Sure R3 doesn't install Route for 78.78.78.0/24 into it's Local Routing
table, Only use of Extended ACL is allowed for this purpose.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make Sure R1 doesn't install Route for 78.78.78.0/24 into it's Local Routing
table, Only use of Prefix-List is allowed for this purpose.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make Sure R11 doesn't install Route for 150.150.150.0/24 into it's Local
Routing table, You are not allowed to use Distribute-List.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make sure R3 doesn't install routes with even number in 3rd Octet injected
by BB(R12) in RIP domain. You are only allowed to use Single-ACL for
this purpose.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Over R4, Make sure it learn all it's prefixes from R2 only, Don't apply any filter
on R3 for this. Also do it with single command.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Updates between R1 & R7 should be exchanged using broadcast using RIPv2.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Updates Between R11 & R2 should be exchanged using Unicast.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) Make Sure R1 and R7 only exchange updates over serial link (FR Circuit)
only if there is any change in topology, much like Link State Protocols.
---------------------------------------------------------------------------------------------------------------------------------
-> 1.) R2 Should Inject a default route for R11 using RIP.
---------------------------------------------------------------------------------------------------------------------------------
