CCNP TSHOOT Official Certification Guide Kevin Wallace, CCIE No. CCNP TSHOOT Exam Preparation Master CCNP TSHOOT. CCNP TSHOOT Official Certification Guide (Official Cert Guide): CCNP Routing and Switching TSHOOT Official Cert Guide .. I was very dissapointed in this fact, as I liked to load the PDF on my Kindle and read while on. Thank you very much for reading ccnp tshoot official certification guide. As you may know, people have look hundreds times for their favorite readings.
|Language:||English, Spanish, German|
|Genre:||Health & Fitness|
|ePub File Size:||27.46 MB|
|PDF File Size:||13.33 MB|
|Distribution:||Free* [*Register to download]|
CCNP TSHOOT Official Certification Guide is an excellent self-study resource for the CCNP TSHOOT exam. Passing this exam is a crucial step to. Size Report. DOWNLOAD PDF CCNP TSHOOT Official Certification Guide · Read more CCNP SWITCH Official Certification Guide. CCNP TSHOOT Official Certification Guide - Pearsoncmg. 57 Pages · CCNP Routing and Switching TSHOOT Official Cert ronaldweinland.info
However, the beta version of the exam contained 28 questions 12 multiple-choice questions and 16 troubleshooting scenarios. Time limit: The exam has a time limit of minutes. Trouble Spots In an effort to prevent cheating, Cisco has structured the TSHOOT exam such that a candidate cannot be presented with a trouble ticket and identify the underlying issue based on memorization of a brain dump. Specifically, the candidate might see the same trouble ticket more than once, each time with a different underlying cause. For example, the candidate might be presented with a trouble ticket indicating that a client PC cannot ping a host on the Internet. The issue in one trouble ticket might have to do with the client being configured with an incorrect default gateway.
The companion CD-ROM contains a powerful testing engine that enables you to focus on individual topic areas or take complete, timed exams. The assessment engine also tracks your performance and provides feedback on a module-by-module basis, laying out a complete study plan for review.
Well regarded for its level of detail, assessment features, and challenging review questions and exercises, this official study guide helps you master the concepts and techniques that will enable you to succeed on the exam the first time. To find out more about instructor-led training, e-learning, and hands-on instruction offered by authorized Cisco Learning Partners worldwide, please visit www.
Books in this series provide officially developed exam preparation materials that offer assessment, review, and practice to help Cisco Career Certification candidates identify weaknesses, concentrate their study efforts, and enhance their confidence as exam day nears.
Understanding the Basics of QoS. Troubleshooting OSPF. In addition, it contains all the chapter-opening assessment questions from the book. This integrated learning package:. Advanced Cisco Catalyst Switch Troubleshooting. Specifically, the candidate might see the same trouble ticket more than once, each time with a different underlying cause. For example, the candidate might be presented with a trouble ticket indicating that a client PC cannot ping a host on the Internet.
The issue in one trouble ticket might have to do with the client being configured with an incorrect default gateway. The same trouble ticket might be presented again, but with a different underlying cause; for example, an OSPF route redistribution issue.
Also, the candidate answers the trouble ticket scenarios through a series of three multiple-choice questions.
First, the candidate must correctly identify the device in the network that's causing the issue. Based on that third response, the candidate selects an action that would resolve the reported issue. The probability of correctly guessing the answers to three consecutive multiple-choice questions where the second and third questions can only be answered correctly if the preceding question was answered correctly is practically zero.
Start at the network layer and follow the evidence, developing specific tests of each hypothesis. Understand the order of operations within each device to do this. Compare the configuration to an older version or to that of a similar device.
Diff and WinDiff are tools that make this comparison easy. Swap components to see if the problem moves with a device. Two troubleshooting tactics need special mention. Most technicians build up a reservoir of experience, which gives them an intuition about the solution to a given problem. This thinking is a logical error: Sometimes this does provide a clue, but large networks have many things happening contemporaneously every second. This troubleshooting method can easily provide a false lead.
The Troubleshooting Method Troubleshooting a network falls into a series of steps that mirror the scientific method. The first step in troubleshooting is to define the problem. Always start the troubleshooting process by gathering a detailed description of the problem. Ask questions to gather details, such as the names and locations of affected devices.
One good way to gather details is to ask about how the problem can be duplicated. What is the scope?
What other devices or locations are affected? When did it start? How can you test the problem? As information is gathered, one or more theories might begin to form. Develop tests that confirm or refute the theories, and work to find the root cause.
Tests can be as simple as pings or as complex as implementing a configuration change; the tests should be aimed at separating valid theories. When the testing process is complete, take a moment to consider the results. Do the results suggest a configuration or hardware change? Is the problem resolved? If not, reconsider the problem description and the original hypothesis. Either the problem was not completely and accurately described, or the hypothesis was incorrect and needs to be revisited.
The state of the network and the problem resolution need to be communicated, and documentation might need to be updated. Past these obvious steps, consider whether the problem found can be in other parts of the network. If the problem were in the configuration, think through the configuration template used in your network and determine if the fix needs to be repeated preemptively on other devices.
The important points here are to work logically and methodically, and to view each problem as an opportunity to perfect the larger network. Integrating Troubleshooting into Maintenance Every interaction with the network is an opportunity to learn. Smart organizations capture information learned to solve similar problems and to help understand the network in the future. Change control and documentation are the two principal ways that feedback from network changes is incorporated into the maintenance cycle, as shown in Figure Troubleshooting identifies the corrective action to upgrade or repair the network.
Throughout these processes, a regular communication with end users is critical to understand the problem and to gather feedback on the solution.
Communication with end users, within the team, and with management is pervasive throughout the cycle. The change-control process is a formal communication process for requesting and receiving permission. Change control provides an opportunity for management and peers to be aware and consent to the proposed change.
The change process encourages the network technician to take a deliberate and thoughtful approach. Finally, the change process creates a record of the change that can be incorporated in documentation. After a change is made and an issue is resolved, updating documentation must be seen as a part of the clean-up process. Most organizations have records including IPs, inventory, configurations, and topology; changes need to be added to these records.
If the change is sufficiently broad, it might also need to be incorporated into standards and templates so that other devices can be preemptively upgraded. As records and standards change, team members need to be educated on the changes. A number of tools can compile baseline data and monitor the network continuously. A baseline is a reading of the critical parameters of the network such as latency and utilization over a period of time.
The baseline serves as a record of normal behavior to help identify how performance has changed. Updating baseline information is part of the documentation process. Think about troubleshooting as a holistic process. Approach each issue with a rational evidence-based philosophy, make thoughtful changes, and communicate with all the invested groups often.
Understanding the capabilities of the operating system and how to use them effectively can reduce time-to-repair and the stress of a network outage. Many people are not familiar with the filtering techniques that enable a troubleshooter to quickly focus. Some of these filters are command-specific. Consider show ip route, which is a familiar command.
When used, this command shows a complete routing table as shown here: Foard-rtr01 show ip route Codes: One way to summarize this information is to ask for a summary using show ip route summary. Specifying an address, mask, and the keyword longer-prefixes asks for anything that matches the prefix or any routes contained within the prefix.
The following example shows all the more-specific routes contained within the Foard-rtr01 show ip route Generic filters can also be applied to all show commands. Show process cpu, which might be used to look for runaway processes, can be used as an example.
First, an example portion of output is shown: Foard-rtr01 show process cpu CPU utilization for five seconds: Output is matched against a regular expression. Following is a table of common regular expression characters.
Any character Ethernet. Foard-rtr01 show process cpu include IP Input 87 58 0. In the following example, piping to begin starts the output at the telnet ports. This is a lot easier that using the space key to work through a large configuration: Foard-rtr01 show running-configuration begin vty line vty 0 4 exec-timeout 20 0 password 7 CD logging synchronous transport input ssh transport output telnet ssh line vty 5 15 exec-timeout 20 0 password 7 CD logging synchronous transport input ssh transport output telnet ssh!
Piping output can be a great way to focus on relevant details, but show running-configuration section is a lot to type, particularly repeatedly. The alias command can make this easier. In configuration mode, create a shortened version of a command as shown next.
Type srs vty to see the same output as the example. In the preceding example, piping to begin also includes all the text after the part of interest. Piping to section shows the indented commands under a line that matches the regular expression. In the following example, the sections found under the keyword vty are shown: Foard-rtr01 show running-config section vty line vty 0 4 exec-timeout 20 0 password 7 CD logging synchronous transport input ssh transport output telnet ssh line vty 5 15 exec-timeout 20 0 password 7 B1ED2B2C2B logging synchronous transport input ssh transport output telnet ssh The pipe symbol is also used as an OR within a regular expression, as shown in the next examples.
Normally, show ip interface brief summarizes all the interfaces found on a router. Some routers have a large number of interfaces, making even this simplified display cumbersome. In the following text, some of the interfaces are grouped into multilinks and others are turned off. Finding the detail you need is complicated by the long and confusing output: In configuration mode, create a shortened version of a command as shown here.
Redirecting output enables an administrator to collect information for archiving or to share with other troubleshooters and save it as a text file. Redirect just creates the file, whereas tee also displays the content in session. Any filesystem supported by that router is supported, so output can be pointed at flash, tftp, ftp, http, and other destinations.
The syntax to use this function is Show command redirect file Show command tee file The next examples show the running configuration being piped to TFTP.
In the first example, the output is redirected. The second example tees the output so that it builds the TFTP file and displays on screen. Foard-rtr01 show running-configuration redirect tftp: Building configuration Current configuration: Ping tests connectivity and is so commonly used that even end users are passingly familiar with it.
A ping response shows that a working path between two end points exists. End systems sometimes have firewalls that prevent response, but generally ping is a reasonable first test of network connectivity: Foard-rtr01 ping First, pay attention to the pattern of the response. Alternating success and failure!.!.! Second, pay attention to the response time. Many applications depend on quick response. Voice, for instance, assumes a round-trip time of less than ms.
The response time can also clue the troubleshooter to utilization issues.
If the response time is much larger than usual that might indicate a heavy traffic load and queuing. If you notice that the minimum and maximum times vary widely, this could also be a sign of queuing because of a heavy load. Ping can do a lot more than that simple test, however.
Privileged mode supports an extended ping that enables every aspect of ping to be controlled. This opens up many more tests that can be accomplished with the humble command. The following example below an extended ping. Notice that the command ping—with no destination specified—is entered in privileged mode. The example sends five pings of bytes, then five of bytes, continuing to byte pings.
The DF bit do not fragment is set. A more detailed explanation of the command is found after the example: Foard-rtr01 ping Protocol [ip]: Target IP address: Datagram size : Timeout in seconds : Extended commands [n]: Data pattern [0xABCD]: Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Sending 75, [ Packet sent with a source address of Selecting all the defaults is similar to a normal ping.
Sometimes testing involves repeatedly pinging for instance, when you believe that an interface is flapping up and down. An extended ping with a repeat count of can be used to interactively test the network over a period of time. Pings can be set to different packet sizes through the Datagram Size variable. The router can automate testing a range of sizes. To do so, use the extended commands and choose to sweep a range of sizes. If a router is asked to forward a packet that is larger than the MTU of the transmitting link, the router normally breaks the packet into smaller pieces.
Setting the DF bit instructs receiving routers to discard the traffic rather than fragment it. When the MTU limit is reached, all subsequent pings will be dropped. Pings are normally sourced from the transmitting interface. Using an internal interface as the source shows that the receiving device and the intermediate routers understand how to route back to that prefix.
A final idea is to try different Type of Service settings. Many networks now carry voice, video, and prioritized data. Like ping, there is an extended version of traceroute. It has a few of the same capabilities, with one other significant testing ability.
This can be used to test application performance for applications that use UDP, such as voice. This is important when trying to diagnose the affects of firewalls and access-lists. An example extended traceroute is shown next. The only choice specified in the example is to use UDP port Newton-rtr01 traceroute Protocol [ip]: Numeric display [n]: Timeout in seconds : Probe count : Minimum Time to Live : Maximum Time to Live : Port Number : Type escape sequence to abort.
Tracing the route to Telnet does not offer many options, but by changing the target port, different network services can be tested. The following examples show that email and the web server respond on the appropriate ports: Foard-rtr01 telnet www. Open www. Fri, 4 Sep Several commands describe the functional state of an IOS device.
If network hardware is suspected, a good place to start troubleshooting is to understand the external environment. The show environment all command displays information about the temperature within the device and the state of the power supplies. Especially when troubleshooting remotely it is easy to forget power and air conditioning, but problems in either area can lead to device malfunction: Unit is on.
Temperature readings: Of course, this information is much more useful if obtained before a problem occurs and connectivity drops!
By comparing the inventory to previous inventories, it is possible to recognize differences caused, presumably, by hardware failure. If the organization has a Cisco SmartNet maintenance contract, the serial number and part-number information is necessary to obtain spares: Foard-rtr01 show inventory NAME: V03 , SN: V01 , SN: A lack of memory can also cause a network issue. The show memory command displays the state of memory on a device; focus on the Free column to determine if enough is available.
Show controller can show some information about the interface—serial interfaces in particular report things such as cable information here. Show interface shown next displays a good deal of information about the state of the interface. In particular, pay attention to four measurements: Signify that the router had more traffic than it could process. Some amount of drops is excusable, but drops could be related to CPU oversaturation. Double-check the processor with the show processes cpu command.
Usually mean that the line is congested. These errors show duplex errors, interface problems, and CRC errors. Usually related to duplex issues. Cisco IOS devices support these tools and in many cases supply detailed information to the management system.
This section describes the methods used to coordinate with these tools. Packet Sniffing Packet capture from a laptop or specialized device enables low-level vision into the exact traffic flowing over a link.
Capturing traffic can show errors and underlying protocol traffic. The issue with packet capture is that switches do not forward all traffic out all ports, so it is difficult to find a port from which to see all traffic.
SPAN is then pointed to an output port, to which a packet capture tool is attached. A second switch can then capture the VLAN and output it to a port. From there it can be copied off for inspection on a PC: Netflow Netflow collects summaries of traffic information and transmits the summary to a Netflow collector.
Netflow is enabled on each monitored interface. Netflow supports a version 5 and version 9; this should be set to match the requirements of your network management system. Finally, Netflow exports information to a target IP address.
The commands to accomplish these actions are shown here: SNMP is supported by most network monitoring systems. The router also has a tool to react to events through embedded event manager EEM.
SNMP is set up by identifying a server and listing the events to be monitored. If snmp-server enable traps is used without specifying specific events, all traps are monitored: EEM applets are starting to appear on the Internet, both at Cisco.
A simple example EEM applet is shown next. This applet logs a Syslog message and outputs a message to the console in reaction to an administrator entering configuration mode: Authorized access only. Movement to consolidate networks has collapsed storage and virtualization, and telephony has put more traffic on Ethernet. Maintaining this critical infrastructure involves understanding the component pieces: Poor forwarding performance on switches is usually associated with cabling and port problems, duplex mismatch, or TCAM issues.
Problems at the physical layer can be seen from show interface, show interface counters and show interface counters errors. Look for the following errors: Align-Err, runts: Alignment errors are usually associated with cabling, NICs, or duplex mismatch.
Frame Check Sequence errors are usually associated with a cabling issue.