CCNP ROUTE Instructor Lab Manual. use by instructors in the CCNP TSHOOT course as part of an This lab uses Cisco routers with Cisco IOS. CCNP TSHOOT Student Lab Manual. Share? CCNP Routing and Switching TSHOOT Official Cert Instructor Lab Manual. Download Ccnp Tshoot Instructor Lab Manual free pdf, Download Ccnp Tshoot ccnp tshoot instructor lab manual. this document is exclusive property of.
|Published (Last):||17 June 2011|
|PDF File Size:||1.48 Mb|
|ePub File Size:||12.76 Mb|
|Price:||Free* [*Free Regsitration Required]|
This document is Cisco Public Information. Assign responsibility for a device or set of devices to team members optional. Load the baseline configuration for all devices in the topology. Use available tools to document key device configuration parameters, such as the interfaces in use, IP addressing, routing protocols, VLANs, logging mechanisms, and security measures.
Document the physical topology to support future troubleshooting tasks. Document the logical topology to support future troubleshooting tasks. Background You have been employed as a network engineering consultant by a company that has made a recent acquisition.
This will help you learn about the design and implementation of their network and ensure that you have All contents are Copyright?
No problems are introduced in this lab. This network will evolve over time as changes and enhancements are made. You will analyze and document the current topology and device configuration parameters to develop familiarity with the baseline configurations and network connections.
CCNP TSHOOT Instructor Lab Manual_图文_百度文库
You will review and fill out the provided documentation as you evaluate the tshlot. You will assess and assemble tools that can be used for future maintenance and troubleshooting tasks. Other routers such as andswitches such as orand Cisco IOS Software versions can be used tsoot they have comparable capabilities and features. Depending on the router or switch model and Cisco IOS Software version, the commands available and output produced might vary from what is shown in this lab.
The lab topology should be pre-built prior to the students starting the lab. These can be downloaded from the Academy Connection web site. The baseline configurations for all devices are included at the end of this lab. Each configuration can be copied into a text file using the naming convention indicated in Task 2, Step 1.
This directory should contain the baseline configuration file for that device as well as configuration files for the other labs in this course. Instructors can use a TFTP server, USB drive, flash memory card, or other method at their discretion to initially tshoto all course configuration files into the flash: This procedure la done once at the beginning of the course.
For this lab and subsequent labs, the student is responsible for loading the baseline or trouble ticket configurations as required using the procedure described in Task instrucror.
The baseline configuration file for each device and the final show running-config outputs are included at the end of this lab. Set the correct time on router R2, which serves as the primary NTP server for the lab network. Serial and Ethernet cables, as shown in the topology Rollover cables to configure the routers and switches via the console Instructor Notes: This lab is not a troubleshooting lab. It focuses on discovering the network, assembling documentation, and identifying available troubleshooting and maintenance tools.
A large part of the documentation that students need for subsequent labs is included in the lab guide. The main purpose of this lab is to have students analyze the network design and implementation, familiarize themselves with the environment that they will be working in during the course, and assemble the documentation that they will need to troubleshoot effectively in subsequent labs.
Students can work in teams of two or more, or can work individually from a remote environment. If the team consists of three people, each person can analyze and document one router and one switch. Each student can also work with a single device and use Telnet or SSH to access the other devices and map out the entire network, if time permits. The lab is divided into tasks. If time is a factor, Tasks 1 through 3 can be done in one session and Tasks 4 instruchor 6 in a subsequent session. Assign Responsibility for Each Device optional Task 2: Identify Troubleshooting and Maintenance Tools Task 6: Identify Implemented Security Measures?
All contents are Copyright? Assign Inatructor for Each Device optional Step 1: Review the lab topology together with your team members. Assign responsibility for each device to a team member. The team member who has primary responsibility for a device is in control of the console of that device and changes to the device.
No other team member should access the console, make changes to the device, or execute disruptive actions, such as reloading or debugging, without permission from the responsible team member. All team members can access all devices via Telnet or SSH for nondisruptive diagnostic action without permission of the responsible team member.
Responsibilities can be reassigned during later labs if necessary. If working in teams, you can document responsibilities in the Device Responsibilities table.
Load the Baseline Device Configuration Files Use the following procedure on each device in the network to load the baseline configuration. The procedure shown here is for a switch, kab it is very similar to that of a router.
The configs for this lab include ip host name ip-addr entries for all devices. This can be helpful in accessing devices using Telnet with this lab. The ip host entries are only provided in Lab as the device IP addresses will change in subsequent labs.
See the instructor note in the Tshoo section at the beginning of the lab for additional information on initially copying the device config files to flash.
These features are implemented within the specific labs where they are introduced. Verify the existence and location of the lab configuration files. The lab configuration files for the course should be in flash under the tshoot directory for a given device.
Use the show flash command to verify the presence of this directory. You can also verify the contents of the directory using the cd and dir commands.
If the directory and files instructoe not present, contact your instructor.
When the show flash command is used on a switch, it lists the directories and files at the root directory but not the files within the directories. The following example uses the cd and tsoot commands on switch ALS1. When the show flash command is used on a router, it lists the directories and the files within them. The following example uses only the show flash command on imstructor R1. The tshoot directory and its contents are listed.
This assumes the configuration files are in the TFTP server default directory. ALS1 erase startup-config Erasing the nvram filesystem will remove all configuration files!
Delete the Tshoor database from flash switches only. Reload the device, but do not save the system configuration if prompted. ALS1 reload System configuration has been modified.
Reload requested by console. When the device restarts, do not enter the initial configuration dialog, but terminate autoinstall if prompted. Copy the specified lab device configuration file from flash to the running config. Although it is possible to copy the file to the startup config and reload the device, the RSA keys for SSH cannot be generated from the startup config.
Copy the running config to the startup inwtructor. To ensure that the startup configuration is complete, you must copy manually. If the device is rebooted at instruvtor point, you can log in with the username admin and the password adminpa To access privileged EXEC mode, use the enable password of ciscoenpa Repeat Steps 1 through 7 for the other devices in the network.
Test basic network connectivity between tsshoot. Were the pings successful? Ping from ALS1 to R2 at loopback If the pings are not successful, contact your instructor.
CCNP TSHOOT 6.0 Student Lab Manual
At this time, only examine and document the physical connections. Documenting the logical topology, such as subnets, IP addresses, and routing protocols, is addressed in Task 4 of this lab. Review the physical topology diagram on page 1 of the lab.
Use Cisco Discovery Protocol and show commands to verify the Layer 1 and Layer 2 connections of the lab topology. Use the show cdp command to discover the interfaces associated with the physical connections.
Fill in the correct device and interface designators in the following Device Links table and label them on the physical topology diagram on the first page of the lab. ALS1 show cdp neighbors Capability Codes: Review the configurations of the devices for using Layer 1 and Layer 2 features, such as trunks and EtherChannels.
Fill in the information in the Device Links table and add it to the diagram. If a link is accounted for from one device to another, it is not necessary to repeat the entry from the other device. Which other commands could you use to identify Layer 1 and Layer 2 characteristics?
Verify that all physical links shown in the diagram are operational. Which commands did you use? Map the VLANs used in the lab to the devices in the diagram. Identify all host devices that are members of each VLAN. The first entry for VLAN 10 is filled in as an example. Analyze spanning tree for the Layer 2 switched domain.