CCSI Test Paper

Instructor Certification Program Technical v8.
Candidate Instructions
Instructor Certification Program

Cisco Systems Inc.
Private & Confidential
Instructor
Readiness
Program
Document Owner:
Name:
Address:
Phone:
Fax:
Email:
Jennifer Crumb
Partner Development & Education
Cisco Systems Inc
170 West Tasman Drive
San Jose, CA 95134-1706
USA
+1 408 853 6668
+1 408 853 0469
jecrumb@cisco.com
Document Title:
Version:
Date Edited:
Edited By:
ICP ICND v2.3

8.0
June 2006
yhansla@micro-networks.com
Copyright 2006 Cisco Systems Inc
Ver 8.0
Page 1 of 22
Instructor Certification Program Technical v8.0
Guidance for Candidates

Read These Notes Carefully
!
You will have 15 minutes to read this paper before starting. This time allowance is not
included in the overall lab time.
Complete all sections of the lab in order.
Please notify the Proctor when you reach each checkpoint.
Do not proceed until you are instructed to do so.
Be aware that the routers and switches used in the lab may have port/interface
specifications that differ slightly from those in the diagrams and tables in this document.
Many routers have a slot/port architecture. Modify the router interface details as
appropriate.
E0 in the instructions refers to the first Ethernet port, on some devices this may be a
Fast Ethernet interface. S0 refers to the first serial port.
There should be no hardware or connectivity problems other than a password set on one
of the routers. If you believe you are having hardware-related problems speak to the
Proctor. If there is already a configuration on any of your devices it should be deleted and
the device reloaded. Please advise the ICP Proctor.
At any point in this document, where the phrase POD-X is shown, X refers to your
allocated POD number.
Please make additional notes on the paper in the space provided on each page or on the
back of any page.
General questions relating to the lab can be raised with the ICP Proctor during the lab
without loss of points. The ICP Proctor will make allowances for language difficulties for
non-English speaking candidates.
All documentation must be returned to the ICP Proctor on completion of the lab.
Please turn off all mobile phones/pagers and leave these with the ICP Proctor.
By taking part in this event, you are agreeing to be bound by Cisco Systems Inc
NDA. Disclosing any part of this lab will result in the suspension of your CCSI
status.
THIS DOCUMENT MUST BE RETURNED TO THE ICP PROCTOR.
Good Luck!
Ver 8.0
Page 2 of 22
Name:
Certified Learning Partner:
Date:
Instructions for remote access

The following information relates to ICP events that use Cisco Systems Inc Remote Lab
only!
As of July 2006, Cisco Systems Inc will use SSH (TCP port 22) for remote access to the ICP Lab.
You are free to use any remote access client that supports SSH.
The freeware clients, TeraTerm and Putty have been tested. However, neither are supported or
endorsed by Cisco Systems Inc.
A copy of these clients is with your ICP Proctor.
The ICP Remote Lab Terminal Server address is 128.107.245.33.
The ICP Proctor will provide the login details at the start of the lab session. The login information
will expire after the end of the ICP event.
Ver 8.0
Page 3 of 22
1 - Physical & Data Link Layer

Note: In this section ONLY, you are able configure temporary parameters of your own choice.
1A.
Initial Configuration
1. Configure hostnames on all routers and switches within your POD.
2. Configure the following banner on all routers/switches.

Replace DD/MM/YYYY with todays date. Ensure that your name <Your Name> and the
router/switch hostname <Router/Switch> are also on the banner.
ICP DD/MM/YYYY
<Router/Switch POD-X>
<Your Name>
3. Use IOS commands to configure the following router and switch passwords;
Console:
Enable:
Enable Secret:
Telnet:
cisco
cisco
san-fran
cisco
Ensure that the Console session does not time out and interrupted output is redisplayed.
Encrypt all passwords.
1B.
Topology Discovery
5. Discover the network topology clearly identifying which interfaces are being used.
6. Label all WAN cable DTE/DCE orientation.
7. Configure suitable interface descriptions on all operational interfaces on all routers and
switches.
8. Discover the IP subnet/subnet mask being used on the backbone and document this on the
topology diagram.
9. Shut down unused router ports and remove any temporary configuration from the routers in
your POD.
Do not proceed beyond this point. Notify the ICP Proctor and have your
configuration verified. The Proctor may require you to demonstrate your working
configuration.
Ver 8.0
Page 4 of 22
Subnet ___.___.___.___
ICP_BBone
TFTP
216.16.6.1/24
105.15.5.1/24
50.0.0.1/8
15.1.1.100/8
145.1.36.63/16
nnn.nnn.nnn.nnn
Tester
nnn.nnn.nnn.250
POD X
R0
SW0
R1
R2
SW1
R3
Rev 8.0
Page 5 of 22
1C.
Switching
1. Enable trunk ports on switches SW0 and SW1.
2. Other connections on the switches should be at the most appropriate settings of speed and
duplex.
3. Create a password protected VTP domain called POD-X and ensure that switch SW0 is
configured as Server and SW1 as Client.
4. Prevent the unnecessary propagation of broadcast traffic across trunk ports.
5. Create three VLANs to represent networks between:

- router R0 and R2 named VLAN2_R0R2
(VLANs do not have to be assigned at this stage).
6. Statically configure router R0s first Ethernet interface MAC address on the local switch.
7. On the correct switch: ensure that only one MAC address for router R1s E0 port can be
stored in the CAM table.
8. Ensure that router ports on the switch do not participate in the usual Spanning Tree
topology calculation.
Remove any temporary configurations used in the switches.
9. Determine the state of Spanning Tree topology (root switch and port states) for all VLANs
and indicate on the following diagram:
Ver 8.0
Page 6 of 22
Key:
F Forwarding
B Blocking
NA Not applicable
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
-
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
F or B or NA
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
F or B or NA
F or B or NA
F or B or NA
F or B or NA
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
F or B or NA
F or B or NA
F or B or NA
F or B or NA
To R0
SW0
To R2
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
F or B or NA
F or B or NA
F or B or NA
F or B or NA
SW1
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
F or B or NA
F or B or NA
F or B or NA
F or B or NA
To R1
To R3
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
F or B or NA
F or B or NA
F or B or NA
F or B or NA
VLAN 1
VLAN2_R0R2
VLAN3_R1R2
VLAN4_R3R2
SW0
root/non-root
root/non-root
root/non-root
root/non-root
SW1
root/non-root
root/non-root
root/non-root
root/non-root
Bonus
11. Alter the Spanning Topology and ensure that SW0 is the root switch for two VLANs and
SW1 is the root for the other two VLANs.
Ensure that on each switch, there is one trunk port forwarding and one that is blocking.
configuration.
Ver 8.0
Page 7 of 22
1D.
Frame Relay
A.
Configure Frame Relay Switching (R1 only)
1. Configure router R1 as a Frame Relay Switch to link routers R0 and R3 via the first, second
and third serial interfaces.
2. Configure the Frame Relay Switch to support 3 PVCs between routers R0 and R3 (see
diagram on next page).
The Frame Relay switch should use ANSI LMI.

From DTE to DTE there should be a total of 3 PVCs.
B.
Frame Relay Configuration (R0 and R3 only)
1. Correctly configure one point-to-point PVC to link routers R0 and R3 via the Frame Relay
Switch R1. Use the 2nd serial interface on router R0.
2. Correctly configure one point-to-multipoint Frame Relay subnet with two PVCs to link
routers R0 and R3 via the Frame Relay switch R1. One PVC should terminate on R0s first
serial interface and the other should terminate on R0s second serial interface.
3. Disable Inverse-arp on the Frame Relay point-to-multipoint PVCs.
configuration.
Ver 8.0
Page 8 of 22
216.16.6.1/24
105.15.5.1/24
50.0.0.1/8
15.1.1.100/8
145.1.36.63/16
Subnet ___.___.___.___
ICP_BBone
TFTP
nnn.nnn.nnn.nnn
Tester
nnn.nnn.nnn.250
POD X
P2P
R0
SW0
P2M
R1
R2
SW1
R3
Ver 8.0
Page 10 of 22
Section 2 Network Layer
2A.
IP Addressing
1. Create a VLSM addressing scheme for all the routers in your POD using the following
table. Ensure that your subnet address scheme can accommodate the number of subnets
and hosts indicated. Use the following page for your subnet calculation.
2. Calculate the directed broadcast address for the first LAN and first WAN subnet allocated
to your POD.
3. The character X represents your POD number.
POD X
Backbone Address
1
2
3
4
5
6
7
8
9
10
11
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
nnn.nnn.nnn.X
Starting Address
(all /24)
10.1.1.0
10.1.2.0
10.1.3.0
10.1.4.0
10.1.5.0
10.1.6.0
10.1.7.0
10.1.8.0
10.1.9.0
10.1.10.0
10.1.11.0
Ver 8.0
Subnets/Hosts Required
LANs Hosts per LAN WANs
7
6
6
10
12
5
20
5
8
16
4
10
12
10
6
9
6
5
13
10
7
8
8
8
18
6
10
10
12
5
7
11
6
Page 12 of 22
# IP Subnetting Calculation.
Ver 8.0
Page 13 of 22
4. Indicate the IP addresses used for your POD in the following diagram;
216.16.6.1/24
105.15.5.1/24
50.0.0.1/8
15.1.1.100/8
145.1.36.63/16
Subnet ___.___.___.___
ICP_BBone
TFTP
nnn.nnn.nnn.nnn
Tester
nnn.nnn.nnn.250
POD X
P2P
R0
SW0
P2M
R1
R2
SW1
R3
Ver 8.0
Page 14 of 22
5. Configure IP addresses and subnet masks on all operational router interfaces in your POD.
6. Use a VLSM scheme across the WAN links between R0 and R3.
7. Using a spare subnet configure loopback interfaces on each router in your pod.
8. Place an appropriate IP address configuration on all switches.
9. Ensure that your switches are correctly configured with VLAN port assignments for
VLAN2_R0R2, VLAN3_R1R2 and VLAN4_R3R2.
10. On each router create IP host entries for R3, R0, R1, R2 and Tester.
11. Configure router R2 to provide inter-VLAN routing for all VLANs (do not start a routing
protocol).
12. Ensure you have IP reachability to your directly connected and neighbouring interfaces.
configuration.
2B.
IP Routing
Note:
From this point forward you may Telnet to router Tester (password cisco).
2B (a) Routing Information Protocol

!
1. Configure RIP.
2. Check connectivity and correct operation of your entire POD (routers and switches) using
the normal verification commands.
3. Ensure that subnet 50.0.0.0 is reachable via the point-to-multipoint serial interface from
router R3 and all other interfaces in Tester are reachable (no not enable frame relay inversearp).
configuration.
2B (b) Enhanced Interior Gateway Protocol

!
4. Discover the EIGRP AS number and correctly configure EIGRP within your POD.
Without disabling EIGRP ensure that RIP routes are preferred on routers R1, R2, and R3.
Ensure that all IP subnets on Tester are reachable.
configuration.
Ver 8.0
Page 16 of 22
2B (c) Enhanced Interior Gateway Protocol

!
6. Remove all dynamic routing protocols and correctly configure OSPF using the following
diagram as guidance.
Ensure that all IP subnets on Tester are reachable. You may configure another routing
protocol on the backbone.
configuration.
Ver 8.0
Page 17 of 22
Subnet ___.___.___.___
ICP_BBone
216.16.6.1/24
105.15.5.1/24
50.0.0.1/8
15.1.1.100/8
145.1.36.63/16
TFTP
nnn.nnn.nnn.nnn
Tester
nnn.nnn.nnn.250
POD X
R0
Area X
Area Y
SW0
R1
R2
Area 0
SW1
R3
Ver 8.0
Page 18 of 22
Section 3 - Transport Layer

3A.
Network Address Translation
1. Configure dynamic NAT to translate source IP addresses from all subnets behind Tester to
a spare subnet for your pod as traffic enters your POD.
configuration.
Do not disable NAT.
3B.
Access Control List
1. Configure and apply an efficient single named access control list that meets the following
objectives.
The access control list must be applied inbound on router R2.
The objectives are not provided in any order of significance.
Prevents pings to any device on subnet 50.0.0.0 from routers R1, R2, and R3.
Deny inbound Telnet session generated from the subnets behind Tester to
VLAN2_R1R2 and VLAN3_R3R2 passing through your NAT gateway.
Permit UDP port 69 to the backbone IP address ending .250
Prevent all other UDP & TCP sessions inbound and outbound from routers R1, R2 and
R3.
Logs all dropped packets.
configuration.
Ver 8.0
Page 20 of 22
Section 4 Application Layer

4A.
TFTP
1. On R2 copy your running configuration to the TFTP server. Call the file r2pX.cfg.
2. Copy the file icp.cfg into the running config on routers R1 and R3.
Bonus
3. Modify your configuration to ensure that router R2 loads icp.cfg automatically on startup as
well as your normal configuration file.
configuration.
!
1. For SW0 and SW1 copy sw-config.cfg into into startup and reload the switches.
After reload, delete VLAN.DAT.
2. Copy the file config.cfg to running on all routers.
3. For R1, R2, and R3 copy the file all_routers.cfg into startup and reload the routers
simultaneously.
4. For R0 copy the file R0_only.cfg into startup and reload the router.
configuration.
Ver 8.0
Page 21 of 22
HANDOVER THIS EXAM PAPER AND ALL NOTES MADE DURING THE ICP TO THE
PROCTOR.
DELETE ALL ICP RELATED INFORMATION FROM PC.
FAILURE TO COMPLETE THIS SECTION, NOT HANDING OVER ALL NOTES AND/OR
NOT DELETING ICP RELATED INFORMATION FROM THE PC/LAPTOP WILL RESULT IN
FAILURE OF THIS TEST.
Ver 8.0
Page 22 of 22
Proctor Guide

ICP Proctor Guide
Cisco Systems Inc.
Instructor
Readiness
Program
Document Owners:
Name:
Address:
Phone:
Fax:
Email:
Jennifer Crumb
Cisco Systems Inc
San Jose, CA 95134-1706
USA
+1 408 853 6668
+1 408 853 0469
jecrumb@cisco.com
Document Title:
Version:
Date Edited:
Edited By:
ICP ICND v2.3

8.0
June 2006
Rev 8.0
Page 1 of 8
Proctor Guide
This document describes the changes that have been made to the ICP Lab v.8. Please read it
thoroughly. There are many changes in the topology and lab that you need to be aware of. As
usual, it is highly recommended that you familarise yourself with the changes by trying the
lab.
V8 was highly challenging in terms of changes. V7.1 was very comprehensive with only minor
issues. It has taken a lot of effort to introduce more value into this edition without having any
additional resources available (in terms oh hardware/software).
As before, the lab is designed to test Cisco Instructor knowledge and ability just slightly over
and above ICND level. Rather challenging to try and keep this objective as fair as possible
without exposing candidates to advanced concepts.
The most significant changes are:
1. There is only one lab now. The POD is expected to be pre-wired prior to the event.
This is a significant change from the previous revs. The rational behind this was the
success of remote labs and the feedback received from both candidates and Proctors
about the value wasting time getting students to wire the POD.
2. Router Core is now R3. The menu options have been altered on the ICP Remote Lab
Terminal Server.
3. The access method for the Remote Lab is now SSH. Telnet will be disable in Aug
2006. Putty and TeraTerm are distributes with this release, but neither are endorsed
or supported by Cisco Systems Inc.
4. POD/Backbone addressing is now different.
5. The ICP Score Workbook (Excel) is now unprotected.
6. We plan on changing the TFTP server from Win95 to LINUX in the near future.
7. There are now mechanisms that candidates can earn bonuss and make up points
lost in previous sections.
8. All routers start with a config-reg 0x2002. R0 has a password. Having all routers set
to 0x2002 takes the pressure of the remote lab support team.
9. If you require Remote Lab Support during an event please email
tis_support@cisco.com.
As through as this development has been, I am sure there are issues. Please feel free to
return feedback to both Jennifer Crumb and myself. Comment, bugs are always appreciated
as are suggests and idea in improving the lab and event.
If you have any issues, please feel free to contact me. I am an active CCSI and train
extensively, so getting hold of me during normal business hours is sometimes difficult, but I
will do my best to answer questions asap.
Thanks to all for the feedback and support so far received.
Kind regards
Yogesh Hansla
Email/MSM IM: yhansla@micro-networks.com
Tel/Txt:
+44 (0)7967 110 213
Timezone:
GMT +/- 0hrs.
Rev 8.0
Page 2 of 8
Proctor Guide
Suggested Point Deduction

Section 1 Physical & Data Link Layer
1A. Initial Configuration
Unable to recover password without aid
Passwords not set correctly
Hostnames incorrect
Incorrect ports identified
Shut/No Shut Correct
Serial lines up (layer 2)
Descriptions not set/incorrect
Switch passwords set
Banners set
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1B. Topology Discovery

Not being able to use/describe CDP
DCE/DTE not indicated or bad clock supplied
Verbal answers ok
Unable to discover backbone subnet
<< CHECKPOINT>>
1C. Switching
Trunk ports not configured
Interface correct speed/duplex set
VTP Pruning configured
VTP correct, with password
VTP client/server ok
Verbal answers ok
VLAN's created and named
Static MAC
Portfast on Router interface
STP Topology correct
Bonus
<< CHECKPOINT>>
1D (a). Frame Relay Switching
FR switching configured
Int dce set
FR route statements ok
Physical, Data Link Up
Logical PVC's up
Correct number of PVCs
1D (b). Frame Relay Switching
P2P int configured
P2M int configured
1xP2P PVCs
1xP2M PVC
All PVCs up and working end
Verbal answers ok
1-2
1-2
1-2
2-3
1
1
1
1
1
1-2
1-2
1
1
1
+ 1-2
1-2
1
1-2
1-2
1
1
1-2
1-2
1
1
1-2
<< CHECKPOINT>>

2A. IP Addressing
IP Subnets/masks correct
Address range correct
Host table correct
1-2
1-2
1
Rev 8.0
Page 3 of 8
Proctor Guide
Switches on Management subnet

Routers lo0s configured (correct mask /32)
Able to ping neighbouring routers
Router on stick (sub-ints) config ok?
<< CHECKPOINT>>
2B (a) IP Routing
RIP v2 everywhere
No auto-sumary
Route via P2M ok
All ints on tester reachable
Verbal answers ok
1-2
1
2-3
1-2
1-2
1-2
1-2
1-2
1-2
<< CHECKPOINT>>
2B (b) IP Routing
EIGRP AS ok
Bandwidth configured on serial
Traceroutes work r2
R2 Routing table correct
Static routes correct/used
Able to all ints on Tester
Gateway of last resort set on all routers
Distance
Verbal answers ok
<< CHECKPOINT>>
2B (c) IP Routing
OSPF Configuration ok
Static route using Next
All interfaces in correct OSPF areas
Pod IP Connectivity ok
Backbone RIPv2 process
Pod route advertised correctly into Tester
Verbal answers ok
<< CHECKPOINT>>
Section 3 Transport Layer
3A. Network Address Translation
Inside/Outside ints correctly defined
NAT pool configured
Config on Core
Standard ACL ok
Only internal address translated
Use of show and debug commands
NAT successful
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1-2
1
1
1
1
1
1-2
<< CHECKPOINT>>
3B. Access Control Lists

ACL applied to correct router/int
Established syntax used
ACL working though NAT
Able to telnet from Testers loXs
Able to ping 50.0.0.0
All other IP connectivity ok
ACL efficiency (number of lines etc)
1
1-2
2-3
1-2
1
1-2
1-2
<< CHECKPOINT>>

4A. TFTP
TFTP successful
Copy icp.cfg on R1 & R3
1
1
Rev 8.0
Page 4 of 8
Proctor Guide
Boot config on R2
+ 1-2
<< CHECKPOINT>>
Sw-config.cd on switches
Delete VLAN.DAT
Config.cfg on all routers
all_routers_cfg
R0_only.cfg
1
1
1
1
1
<< CHECKPOINT>>
1 Physical & Data Link Layer

1A and 1B.
This section has not altered much. Sections 1A and 1B have been combined into one section
with a checkpoint at the end of the entire section.
The major difference is that now the students have to discover the backbone addressing
scheme (although it will only be a question of time before this information is publicly
available). It provides greater flexibility in making changes to the lab.
Point 8. Put an IP address on the backbone interface on R0 and enter debug IP packet.
1C. Switching.
A number of changes have been made to this section. There are now two trunk circuits on
Fa0/23 and fa0/24. Students are required to discover and configure both. These are used
later in the section in a minor STP lab.
Also, the students will need to config some dummy IP address to allow VTP to propagate.
These are removed later in the section.
The candidates are also required to configure Portfast on router interfaces.
The STP lab is rather basic and involves the discovery of the STP topology show spanning
tree vlan X and noting blocking/forwarding port states and also determination of the root
bridge.
The students will be required to demonstrate an understanding of issues relating to STP, i.e.
loop avoidance and load sharing, pros and cons of PVST+
This section also carried an optional bonus. If attempted, the students can regain points lost
in previous section or sections not yet completed. They will be required to alter the STP
topology so that SW0 is the root of two VLANs and SW1 is the root of the other two
(spanning-tree vlan X root primary).
They will also be asked to ensure that each switch has one forwarding and one blocking port.
On an outbound forwarding interace of a switch enter the command spanning-tree portpriority 50.
(PPP has been dropped)
1D. Frame Relay
Similar to the previous lab, but simpler in that only one P2P interface and one P2M interface
are required. They also need to disable frame-relay inverse-arp on this interface. They will
later configure static maps to ensure IP is able to use this multi-access network.
Frame relay switch now uses ANSI LMI.
Rev 8.0
Page 5 of 8
Proctor Guide

A. All pods now use subnets of 10.0.0.0. This includes subnets used in NAT and also for
loopbacks. They are now required to indicate their IP address design on a network topology
diagram.
2B IP Routing
2B (a) RIP
RIP ver must be 2, with no auto-summary everywhere. Static route for 50.0.0.0 must have a
next hop address. They must also use a gateway of last resort to reach hidden subnets on
Tester. Also Tester is now advertising a new subnet (145.1.36.63/16). This is being
advertised with a metric of 14.It will be available on R0, but nowhere else in their POD. They
must maintain reachability to it.
RIP must be left enabled.
2B (b) EIGRP
The EIGRP AS must be discovered (ie. telnet to Tester and show ip protocol). They are
required to configure EIGRP 193 everywhere in their POD.
They are then required to alter the distance of EIGRP on all routers within their POD except
R0 and ensure that RIP is used internally.
2B (c) OSPF
All dynamic routing protocols must be disabled. OSPF must be configured internally within
their POD, but not on the backbone. RIPv2 is required on the backbone. They must advertise
their POD to the backbone (either via a network command on R0 or a static redistributed into
RIP).
Section 3 Transport Layer
3A. Network Address Translation
Outside is their POD, inside is the backbone. They must translate source IP address from
Tester subnets (lo0s) to be translated to a spare subnet they have calculated earlier.
You/they can check this via Tester (telnet x.x.x.x /source-int loX, where x.x.x.x is something
inside their POD).
NAT must be left enabled.
3B. Access Control Lists
ACL must be applied on all the subinterfaces on R2. They must prevent inbound Telnet from
Testers loX while traffic is passing though their NAT config. Not as difficult as it sounds as
both source and destination subnets will be on the same major network number after NAT
has been performed on the packet.
NAT and ACL configuration need to be retained.
This is now a testable section.
They are required to copy their config to TFTP. They must also copy the file icp.cfg into
running on R1 and R3.
Rev 8.0
Page 6 of 8
Proctor Guide
There is a bonus section where students can earn extra points by loading icp.cfg into R2 on
reload only by using boot config command.
A blank config is copied into the switches and VLAN.DAT is deleted.
On all routers the config file config.cfg is copied into running. This file sets the configuration
register on all routers to 0x2002.
On R1, R2, and R3 the file all_routers.cfg is copied into startup removes all previous config.
On R0, the file R0_only.cfg copied into startup removes all previous config and places an
encrypted passed (rooneys_left-foot) which is used for recovery.
Rev 8.0
Page 7 of 8
Proctor Guide
192.168.100.0/24
216.16.6.1/24
105.15.5.1/24
50.0.0.1/8
15.1.1.100/8
145.1.36.63/16
Subnet ___.___.___.___
ICP_BBone
TFTP
nnn.nnn.nnn.nnn
Tester
nnn.nnn.nnn.250
E0/1
POD X
E0/1
S0/1
E0/0
R0 S0/0
Fa0/1
Fa0/2
SW0
Fa0/23
S1/0
S1/1
E0/0
Fa0/24
Fa1/0
R1
E0/1
S1/2
R2
Fa0/23
Fa0/24
Fa0/1
SW1
Fa0/2
E0/0
S0/0
E0/1
R3
Rev 8.0
Page 8 of 8
Proctor Handbook

ICP Proctor Handbook
Cisco Systems Inc.
Instructor
Readiness
Program
Document Owners:
Name:
Address:
Phone:
Fax:
Email:
Jennifer Crumb
Cisco Systems Inc
San Jose, CA 95134-1706
USA
+1 408 853 6668
+1 408 853 0469
jecrumb@cisco.com
Document Title:
Version:
Date Edited:
Edited By:
ICP ICND v2.3

8.0
June 2006
Rev 8.0
Page 1 of 22
Proctor Handbook
ICP Event Administration & Housekeeping

Administration
Book:
For Joint Certification ICPs, register your event at
HTTP://TOOLS.CISCO.COM/E-LEARNINGIT/LPCM/JSP/LPCMWELCOME.JSP> Instructor Management > Manage New
CCSI > Joint ICP Enrollment or Cisco Sponsored ICP Enrollment
ICP Documentation
The ICP documentation set now comprises of;
1.
2.
3.
4.
5.
Introduction PowerPoint Presentation.

Proctor Guide
Proctor Handbook
Marking Spreadsheet
ICP Lab
All MS Word files have now been combined into one Electronic Book (E-Book)
and this also provides access to the PowerPoint presentation and the marking
spreadsheet.
How to use each of the documents is detailed in this chapter:
Introduction PowerPoint Presentation

This short PowerPoint presentation is split into 3 sections: Introduction, Lab and
Presentations. The first, general introduction and housekeeping, section should
be delivered on the first day of the ICP. The lab and presentation sections should
be delivered just prior to the appropriate part of the event. More information about
what to emphasise is in the notes section of each slide.
Rev 8.0
Page 2 of 22
Proctor Handbook
Results Recording Workbook

The spreadsheet now consists of three workbooks only. These are detailed
below:
a. Candidate Information & Results Summary

ICP Proctor Information
Use the ICP Proctor Information section to complete all requested details
concerning the Proctor of the event.
The CLP field relates to Joint Certification partners only. For normal public ICP
use the reference of MicroNET.
ICP Proctor Information
Last Name:
First Name:
CCSI #:
CLP:
Yogesh
Hansla
96030
MicroNET
ICP Event Information

Enter information concerning the ICP event. Please complete all the fields on the
first day of the event.
The ICP Type field indicates the type of ICP Event, - either Cisco or Joint
Certification.
ICP Event Information
Location:
ICP Type:
ICP Start Date:
ICP Lab Date:
ICP Presentation Date:
Paris
Cisco
04-Jun-01
04-Jun-01
05-Jun-01
Enter ICP Candidate information in the following fields. All fields up to Fax field
after CLP is considered mandatory. Please be sure to verify contact details such
as phone, fax and email.
Rev 8.0
Page 3 of 22
Proctor Handbook
ICP Candidate Information

The Candidate information fields are options are should only be completed if the
candidate has been supplied as a contract instructor to the CLP or is sourced via
another organisation. In such cases, it is a formal requirement to complete the
CLP details and also the Candidate details.
ICP Candidate Information
Candidate 1
Last Name:
First Name:
Yogesh
Hansla
Email:
Telephone:
Fax:
hsimpson@micro-networks.com
+44 (0)7967 110 213
+44 (0)7967 110 213
CLP:
CLP Address 1:
CLP Address 2:
CLP Address 3:
CLP Address 4:
Country:
Telephone:
Fax:
MicroNET
16 Creffield Road
London
W5 3RP
UK
+44 (0)208 993 3910
+44 (0)208 993 3910
Candidate:
Address1:
Address2:
Address3:
Address4:
Country:
Rev 8.0
Page 4 of 22
Proctor Handbook
ICP Candidate Results

Please do not attempt to alter any fields in the above section except the Proctor
Comments field. These fields are protected and information is automatically
updated from the other sections of the spreadsheet.
Please feel free to update the Proctor Comments field with any relevant
information details reasons for PASS or FAIL status of the candidate.
ICP Candidate Results
Name:
Yogesh Hansla
%
85
80
83
Presentation Skills 1
Presentation Skills 2
Presentation Skills Avg
Presentation Content 1
Presentation Content 2
Presentation Content Avg
80
82
81
Lab Score
Lab Result
0
FAIL
FAIL
Overall Result
Proctor Comments
Rev 8.0
Page 5 of 22
Proctor Handbook
b. Laboratory Examination
Candidate Scores
It is not necessary to update any information in the fields below. Information is
automatically updated from other parts of the spreadsheet.
Candidate Scores
Candidate 1
Name:
Yogesh Hansla
FAIL
Lab Result:
%
Total Deduction:
100
100
Please enter the start time of an event for the first candidate. The same start time
is used for all the other candidates and end time is automatically calculated. If for
some reason the start time is different, please alter the start time of each
candidate.
Please note that the default result for all candidate is FAIL with a full 100%
deduction. This does not include the Cleanup section of the lab. No candidate
should fail for not cleaning up within the allocated time of the exam. However,
candidates should FAIL if for some reason they do not complete the Cleanup
after they have been requested to by the ICP Proctor. Please exercise your own
judgement. It is courteous to other ICP Proctors to ensure that all ICP lab
equipment is cleared down after the completion of an event.
Timings
It is no longer necessary to enter the start/end time of lunch, breaks etc. Please
enter the total time taken for lunch and breaks in the appropriate fields using a
time format as indicated. The end time is automatically altered.
There is now a dedicated field detailing any injury time awarded. If the candidate
experiences any hardware problems, please indicate the total time awarded and
also document the reason for this in the Proctor Comments field in the Candidate
Information workbook.
The overtime field will automatically be completed if the candidate is over time.
The result of this is an immediate fail.
Rev 8.0
Page 6 of 22
Proctor Handbook
Timings
(hh:mm)
Start:
End:
Lab:
Overtime:
8:30 AM
3:30 PM
07:00
Lunch:
Breaks:
Injury:
01:00
00:15
00:30
PODs
Please note the POD number allocated to the candidate.
Pods
(1-9)
1
Marking LAB
All fields below this section detail lab score.
There are four main sections in the lab, with each section having a number of
subsections;
Section 1 Physical & Data Link Layer (30 points)
1A. Initial Configuration
1B. Topology Discovery
1C. Authentication
1D. Switching
1E. Frame Relay
Section 2 Network Layer (40 points)
2A. IP Addressing
2B. IP Routing
Section 3 Transport Layer (20 points)
3A. Access Control Lists
3B. Network Address Translation
Section 4 Application (10 points)
The total points deduction per section is detailed in the brackets. In an
attempt to improve the over flexibility of the marking scheme, the points
distribution is not assigned. Rather it is left up to the ICP Proctor to make a
judgment call on each section and justify the deduction.
Rev 8.0
Page 7 of 22
Proctor Handbook
The previous method, whereby points were allocated for every minor sub-section
was very inflexible and often resulted in extensive points deductions for minor
mistakes. The new mechanism improves the overall flow, is easier to fill in, as
only one cell per section needs to be completed and is fairer to the candidate.
The new method also permits changes to be made to the lab without an
extensive re-write of the spreadsheet taking place each time.
The general layout is pretty much the same. However, in this version the
number of points for each section has been changed to simple Yes/No
answers. These are there to provide overall guidance so that the ICP Proctor
can score the section once the candidate has completed the assigned objectives.
The lab format is more closely aligned to the course, with students completing
sections in relation to the OSI model, Physical & Data Link, Network and
Transport etc
Rev 8.0
Page 8 of 22
Proctor Handbook
c. Presentations
There is no requirement to fill in any cells in the fields below. Information is
dynamically updated from other parts of the spreadsheet.
Candidate Information
Candidate Information
Candidate 1
Name:
Yogesh Hansla
Presentation:
Candidate Results
Presentation Skills
Content Delivery
PASS
PASS
85
80
PASS
PASS
80
82
Selected Course
Please enter ICND as the selected course.
Rev 8.0
Page 9 of 22
Proctor Handbook
Selected Course
Course
Chapter
ICND
ICND
2
3
2
1
15
15
am (candidate)
Native
pm (proctor)
English
Start Slide Number:

End Slide Number:
Total number of slides:
Selected By:
Language:
Timings
For each presentation, please enter the start and finish time as indicated. It is a
mandatory requirement to video tape the presentations. A field is included in the
presentation spreadsheet to detail the tape reference. All tapes must be kept for
a minimum of three months and must be provided to Cisco Systems on request.
Timings
(hh:mm)
(hh:mm)
Start Time:
End Time:
Duration:
10:30 AM
10:45 AM
0:15
10:49 AM
10:59 AM
0:10
Tape Ref:
Rev 8.0
Page 10 of 22
Proctor Handbook
Presentation Skills
The presentation criterion has not changed. Please indicate the candidate score
in the fields provided. It is important to detail any point deduction in the Proctor
Comments field in this section.
Evaluation Criteria
0-No eye contact or excessive nervousness (4 - regular eye contact with

each student, relaxed manner)
0-Nervous or glib (4 - assertively confident with a credible manner)
0-Voice too loud, inaudible, monotonous or excessive changes of pitch (4 voice clear and used to for emphasis)
0-Non or too much (4 - benefits of product/subject/Cisco emphasised in a
realistic manner)
0-Participation not encouraged or too much time spent interacting (4 enough interaction to ensure full attention)
0-Not used at all or used more than required (4 - visual aids used when
slides not adequate or to clarify key points)
0-Slides or key points not known (4 - order of slides known and all key
points emphasised)
0-Too fast or too slow (4 - appropriate amount of time given to each slide
and all key points emphasised)
0-No questions asked to ascertain skill levels or to maintain interest (4 students regularly questioned globally and individually)
0-Most Questions were not answered correctly or not deferred when
appropriate (4 - All questions answered correctly or deferred if not
relevant)
Rev 8.0
Page 11 of 22
Proctor Handbook
Presentation Skills
Body
Confidence
Voice
Enthusiasm
Participation
Visual aids
Preparation
Pace
Questioning
Students questions
Sub section score
4
4
4
4
3
3
3
3
3
3
4
4
3
3
3
3
3
3
3
3
34
32
Proctor Comments
Content Delivery
The content delivery section is now significantly different in this version of the
marking spreadsheet. It is not possible to provide a details review of the slides for
the ICP Proctor to mark. Instead, ICP Proctors are required to use their own
expertise and professional judgement in determining if the candidate has
successful is delivery the appropriate section on the presentation.
The section breakdown describes the following marking criteria. All points are
awarded out of a total of ten. Please detail the points in the fields indicated and
make a note of any relevant comments in the Proctors Comments field.
Accuracy, - did the candidate describe the contents of the presentation

accurately.
Detail, - did the candidate cover the chosen slides in sufficient detail
Clarity, - was the candidate able to explain the concepts in a clear manner
Focus, - did the candidate stay on the subject matter when questioned
Story, - did the candidate embellish the contents of the presentation by
using his own experience, war stories etc..
Message, - did the candidate pass the Cisco message successfully
Rev 8.0
Page 12 of 22
Proctor Handbook
Content Delivery
Accuracy
Detail
Clarity
Focus
Story
Message
Sub section score
8
8
8
8
8
8
9
8
8
8
8
8
48
49
Proctor Comments
Rev 8.0
Page 13 of 22
Proctor Handbook
Marking Labs
Before recording the results in the Results Workbook, all the fields, which
are outlined in RED in the Candidate Information worksheet, MUST be
completed.
The Candidate Guide informs the candidate what is required to complete the
practical part of the ICP. The Proctor Guide contains a list of suggested
deductions for each section of the lab; these correspond with rows in the marking
spreadsheet.
There are two main ways for a candidate to lose marks in the lab, either by
incorrect/incomplete configurations or by giving incorrect answers to
questions (posed by the Proctor or written in the Lab Candidate Guide). When
marking the lab, it should be assumed that the candidate may be teaching an
ICND course the day after the ICP ends, this makes it important that the
candidate both knows how to configure each device and why particular
commands are used. The following paragraphs explain the concepts behind each
point deduction method.
Incorrect/Incomplete Configurations
At each checkpoint in the lab, the Proctor should check through the candidates
configuration using the usual verification commands (show run, sh ip route,
traceroute etc). The candidate should use best-practice techniques based on
those demonstrated in ICND. For each task that the candidate is asked to
complete (in the Candidate Guide), there is normally a corresponding deduction
in the Proctor Guide..
Incorrect/Incomplete Answers to Questions

At the end of most sections of the lab, there are usually written questions to be
answered by the candidates, however, these should be supplemented by the use
of oral questions. In the case of oral questions, the Proctor should ask enough of
these to establish that the candidate is aware of why particular commands are
used and how particular aspects of routing/switching function and interact.
E.g. In Section 1 sub-sections 1A Topology Discovery and 1E Frame Relay
there are no written answers to be completed, at this point the Proctor should ask
the candidate a few questions, of his/her own making, about CDP/Frame Relay
to ensure an understanding of how they work.
Rev 8.0
Page 14 of 22
Proctor Handbook
Miscellaneous & Other Deductions

The deductions in the Proctor Guide (and thus in the marking spreadsheet) are
based on the most common errors and omissions made by candidates. The
flexibility of Cisco routers is a powerful feature that is open to mis-configuration in
many ways and thus the Proctor should use her/his judgement as to how many
points should be removed if a candidate has incorrectly configured a device in a
way that has not been predicted. In this circumstance, the deduction should be
put in the Miscellaneous row of the sub-section and the reason should be clearly
documented in the corresponding Comments section.
Rev 8.0
Page 15 of 22
Proctor Handbook
Marking Presentations
Presentation marking is split into 2 parts: Presentation Skills and Content
Delivery. To reach the Pass level, these 2 parts must have an average score of
80 per cent for both the presentations.
Presentation Skills
10 types of presentation skill are marked each having a maximum possible mark
of 4. The marks are added and a percentage figure is calculated. To achieve a
pass, the candidate must have an average mark of 80 per cent, calculated over
both the first and second presentations.
Content Delivery
The section breakdown describes the following marking criteria. All points are
awarded out of a total of ten. Please detail the points in the fields indicated and
make a note of any relevant comments in the Proctors Comments field.
Accuracy, - did the candidate describe the contents of the presentation

accurately.
Detail, - did the candidate cover the chosen slides in sufficient detail.
Clarity, - was the candidate able to explain the concepts in a clear manner.
Focus, - did the candidate stay on the subject matter when questioned.
Story, - did the candidate embellish the contents of the presentation by
using his own experience, war stories etc..
Message, - did the candidate pass the Cisco message successfully.
Other Presentation Skills Courses

o For candidates that have already completed an accepted
Presentation Skills course, please indicate this in the Proctor
Comments field. The next revision of the documentation bundle will
permit the exclusion of the Presentation Skills assessment of the
Excel workbook.
Rev 8.0
Page 16 of 22
Proctor Handbook
Results Administration
Results workbook The results workbook should be zipped after the ICP event
has been completed. The zip file should be called ICP_YYYY_MM_DD_XY,
where XY represent the initials of the ICP event Proctor. E.g.
ICP_2006_01_24_YH
Softcopy Distribution
At the end of the 2-day ICP the ICP results workbook should be zipped and sent
to the following;
Results for ICPs should be emailed to: icp_results@cisco.com.
The subject line should read Joint ICP Partner Name Date. In the email,
please list the names of the candidates with a Pass or Fail next to the name.
The subject line of the email should be ICP Results for DD MMMM YYYY. In the
email, please list the names of the candidates with a Pass or Fail next to the
name.
The subject line of the email should be ICP Results for DD MMMM YYYY. In the
email, please list the names of the candidates with a Pass or Fail next to the
name.
Rev 8.0
Page 17 of 22
Proctor Handbook
ICP Contacts
San Jose
ICP Manager
ICP Remote Lab
Support
Jennifer Crumb
jecrumb@cisco.com
tis_support@cisco.com
tis_support at cisco.com
+1 408 853 6668
Yogesh Hansla
+44 7967 110 213
MicroNET
ICP Manager
Rev 8.0
Page 18 of 22
Proctor Handbook
Lab Issues
Power-cycling Routers & Switches
To power-cycle any device in the remote lab:
1. Login to the Access Server as proctor
2. At the first (Proctor) menu, select 10 for APC Masterswitch Menu
3. Select the appropriate menu item for the pod that contains the device you
wish to power-cycle (E.g. 1 for pods A & B)
4. When prompted for a username enter proctor then the password cisco
5. At the next (Control Console) menu, select 1 for Device Manager
6. At the Device Manager menu, select the device that you want to power-cycle
7. At the following, device specific menu, select 3 for Immediate Reboot
8. When prompted, enter YES (in upper case) to continue the power-cycling
process. The device will then be power-cycled
9. Press escape 3 times (once at each menu) to return to the Control Console
menu
10. Select 4 to logout
11. When the message You are now in pass-thru mode is displayed, enter
ctrl+shift+6 then x to return to the pod menu
12. Select 7 to return to the Proctor menu
Clearing Connections to Devices via Candidate Menu

If it is not possible for a candidate to connect to a remote device via the Access
Server menu:
Login as the user
At the Pod menu, use the shortcut cls#<CR>, where # is the menu line number,
to clear the line that is busy (E.g. if it is not possible to connect to an R0 router,
enter cls2<CR>
Repeat the previous step 3 times
Problem Reporting
During the event the any insurmountable technical problems should be reported
to the technical contacts detailed in this document.
Rev 8.0
Page 19 of 22
Proctor Handbook
Configuring Tester
Using the Standard Tester Configuration
The following configuration is only required for ICP labs where the equipment is
local. The remote lab has a permanently configured Tester router that should
not be altered by Proctors.
The configuration can be used on any Cisco IOS (v11.3 or above) based router
with at least one Ethernet or Fast Ethernet port for attachment to the backbone. It
should be modified so that the name of the backbone interface is correct for the
particular device being used. For ease of editing, the line that may require
modification is the first line after the initial comment. No other lines require
altering, as they do not refer to hardware.
Rev 8.0
Page 20 of 22
Proctor Handbook
Tester Config for Copying and Pasting

hostname Tester
!
enable secret <secret-password>
!
no ip domain-lookup
!
interface Loopback0
ip address 105.15.5.1 255.255.0.0
!
interface Loopback1
ip address 50.0.0.1 255.0.0.0
!
interface Loopback2
ip address 216.16.6.1 255.255.255.0
!
interface Loopback3
ip address 15.1.1.100 255.0.0.0
!
interface Loopback145
ip address 145.1.36.63 255.255.255.0
!
interface Ethernet0
description **Ethernet Backbone**
ip address 192.168.100.254 255.255.255.0
ip access-group 100 in
!
interface Serial0
no ip address
shutdown
no fair-queue
!
interface Serial1
no ip address
shutdown
!
router eigrp 193
network 50.0.0.0
network 150.100.0.0
network 216.16.6.0
no auto-summary
!
router rip
version 2
offset-list 45 out 14
network 50.0.0.0
network 105.0.0.0
network 145.1.0.0
network 150.100.0.0
network 216.16.6.0
no auto-summary
!
no ip classless
!
access-list 10 deny 15.0.0.0 0.255.255.255
access-list 10 permit any
access-list 45 permit 145.1.36.0 0.0.0.255
access-list 100 deny ip any 105.0.0.0 0.255.255.255
access-list 100 permit ip any any
!
banner motd ^C
Rev 8.0
Page 21 of 22
Proctor Handbook
Welcome to "Tester" system. Protocol addresses are:

IP Subnet - 192.168.100.0/24
IP Address - 192.168.100.254
Good Luck!
Last edited by Yogesh Hansla 24th June 2006

Tel: +44 (0)7967 110 213
Email/IM: yhansla@micro-networks.com
^C
!
line con 0
exec-timeout 0 0
password cisco
logging synchronous
login
line aux 0
no exec
transport input all
line vty 0 4
exec-timeout 2 0
password cisco
login
!
end
Rev 8.0
Page 22 of 22

Instructor Information
Instructor:
Training Partner:
Certification Location:
Certification Date:
Certification Observer:
Company Address:
Mailing Address:
Phone:
Fax:
Email Address:
Page 1 of 1

CCSI Test Paper

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CCSI Test Paper

Transféré par

Droits d'auteur :

Formats disponibles

Instructor Certification Program Technical v8.

Instructor Certification Program

ICP ICND v2.3

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Guidance for Candidates

Complete all sections of the lab in order.

Please notify the Proctor when you reach each checkpoint.

Do not proceed until you are instructed to do so.

THIS DOCUMENT MUST BE RETURNED TO THE ICP PROCTOR.

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Certified Learning Partner:

Instructions for remote access

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

1 - Physical & Data Link Layer

1. Configure hostnames on all routers and switches within your POD.

2. Configure the following banner on all routers/switches.

6. Label all WAN cable DTE/DCE orientation.

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Instructor Certification Program Technical v8.0

1. Enable trunk ports on switches SW0 and SW1.

4. Prevent the unnecessary propagation of broadcast traffic across trunk ports.

5. Create three VLANs to represent networks between:

Remove any temporary configurations used in the switches.

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Configure Frame Relay Switching (R1 only)

The Frame Relay switch should use ANSI LMI.

Frame Relay Configuration (R0 and R3 only)

3. Disable Inverse-arp on the Frame Relay point-to-multipoint PVCs.

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Section 2 Network Layer

3. The character X represents your POD number.

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

8. Place an appropriate IP address configuration on all switches.

2B (a) Routing Information Protocol

2B (b) Enhanced Interior Gateway Protocol

Instructor Certification Program Technical v8.0

2B (c) Enhanced Interior Gateway Protocol

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Section 3 - Transport Layer

Network Address Translation

Access Control List

Copyright 2006 Cisco Systems Inc

Instructor Certification Program Technical v8.0

Section 4 Application Layer

2. Copy the file config.cfg to running on all routers.

Copyright 2006 Cisco Systems Inc