OV 15 - 1 Copyright © 2013 Logical Operations, Inc. All rights reserved. Network Troubleshooting  Network Troubleshooting Models  Network Troubleshooting.

Slides:



Advertisements
Similar presentations
Ethernet Switch Features Important to EtherNet/IP
Advertisements

Chapter 11 Managing a Network
111 © 2002, Cisco Systems, Inc. All rights reserved. Finish Phase Overview Testing Troubleshooting Certification Documentation.
Network+ Guide to Networks 6 th Edition Chapter 13 Troubleshooting Network Problems.
Welcome... INFORMATION & COMMUNICATION PROCESSING CENTER (ICPC)
Physical Transmission Media 8 5/9/ Modified by: Brierley.
Complete CompTIA A+ Guide to PCs, 6e Chapter 5: Logical Troubleshooting © 2014 Pearson IT Certification
SYSTEM ADMINISTRATION Chapter 19
Section 14.1 Section 14.2 Identify troubleshooting steps
11 TROUBLESHOOTING Chapter 12. Chapter 12: TROUBLESHOOTING2 OVERVIEW  Determine whether a network communications problem is related to TCP/IP.  Understand.
Gathering information 1 st - question the individual who reported the problem as well as any other affected users. – end user experiences – observed symptoms,
3530 Voyager Street Torrance, CA
Click to edit Master subtitle style Chapter 19: Network Troubleshooting Instructor:
NetTool - Basic Overview Slide 1 of 13 Product Training NetTool NetTool Inline Network Tester Troubleshoot and Verify PC and Network Connections.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 Troubleshooting Working at a Small-to-Medium Business or ISP – Chapter 9.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 9: Troubleshooting the Network Connecting Networks.
This courseware is copyrighted © 2011 gtslearning. No part of this courseware or any training material supplied by gtslearning International Limited to.
MCDST : Supporting Users and Troubleshooting a Microsoft Windows XP Operating System Chapter 13: Troubleshoot TCP/IP.
Network+ Guide to Networks, Fourth Edition
Chapter 12: Troubleshooting Networking Problems Network+ Guide to Networks Third Edition.
SOFTWARE AND HARDWARE TOOLS Chapter 19 Network Troubleshooting Spring, 2013.
© 2007 Cisco Systems, Inc. All rights reserved.ICND1 v1.0—2-1 Ethernet LANs Troubleshooting Switch Issues.
ISDS SearchFeeling Techie? Da’John Dickerson Alathea Pacquet Kevin Tran Troubleshooting Tools.
Click to edit Master subtitle style Chapter 18: Software and Hardware Tools Instructor:
The physical network Unit objective: Identify network cables and connectors, and use networking tools.
1 Guide to Network Cabling Fundamentals Chapter 8.
Software and Hardware Tools COMP 316. Software Tools.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Troubleshooting Your Network Networking for Home and Small Businesses.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 IT Essentials PC Hardware and Software 4.1 Instructional Resource Chapter.
Hands-on Networking Fundamentals
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Troubleshooting Your Network Networking for Home and Small Businesses.
Network hardware tools Unit objective Given a scenario, use appropriate hardware tools to troubleshoot connectivity problems Use the appropriate software.
1 Chapter Overview Introduction to network troubleshooting Incident administration Gathering information Possible causes Internet router problem Internet.
Managing Network connections. Network Cabling Ethernet Topology Bus topology – Connects each node in a line – Has no central connection point Star topology.
1 Root-Cause Network Troubleshooting Optimizing the Process Tim Titus CTO, PathSolutions.
Troubleshooting Tools Cable Performance Testers Voltage Event Recorders Butt Set Crossover Cable Tone Generator & Locator Multimeter Cable Continuity Tester.
Network Troubleshooting
Robert E. Meyers CCNA, CCAI Youngstown State University Manager, Cisco Regional Academy Cisco Networking Academy Program Semester 4, v Chapter 7:
Physical Transmission Media Chapter 8. Objectives In this chapter, you will learn to: Identify the characteristics of wireline transmission Describe the.
Operating Systems Lesson 10. Networking Communications protocol is the set of standard rules for ◦ Data representation ◦ Signaling ◦ Authentication ◦
© Cisco Systems, Inc. All rights reserved. Cisco Public ITE PC v4.1 Chapter 4 1 Chapter 12: Advanced Troubleshooting IT Essentials v5.0.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 9 Basic Router Troubleshooting.
Module 8: Ethernet Switching
Sysops Network Training by Brett Haffener. Introductions - Name - School - What are you most interested in learning about?
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 8 Virtual LANs.
Sem1 - Module 8 Ethernet Switching. Shared media environments Shared media environment: –Occurs when multiple hosts have access to the same medium. –For.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Troubleshooting Your Network Networking for Home and Small Businesses – Chapter.
9: Troubleshooting Your Network
1 Root-Cause VoIP Troubleshooting Optimizing the Process Tim Titus CTO, PathSolutions.
Chapter 8 1 Chap 8 – Network Troubleshooting Learning Objectives Establish a network baseline Describe troubleshooting methodologies and troubleshooting.
Network Troubleshooting
NetTech Solutions Common Connectivity Problems Lesson Eight.
ERICSON BRANDON M. BASCUG Alternate - REGIONAL NETWORK ADMINISTRATOR HOW TO TROUBLESHOOT TCP/IP CONNECTIVITY.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 4 Learning About Other Devices.
Troubleshooting Tools Kyle Broussard and Alexandra Mikolai.
Confidential Rapid Troubleshooting for Data, VoIP, and Video VoIP Performance Manager.
CEG 2400 FALL 2012 Chapter 13 Troubleshooting Network Problems 1.
Lec4: Troubleshooting Network Problems Network+ Guide to Networks 5 th Edition Chapter 13 Troubleshooting Network Problems Organized by: Nada Alhirabi.
Click to edit Master subtitle style Chapter 18: Software and Hardware Tools.
© ExplorNet’s Centers for Quality Teaching and Learning 1 Resolve common problems with wired and wireless networks. Objective – 2%
Physical Transmission Media Chapter 8. Objectives In this chapter, you will learn to: Identify the characteristics of wireline transmission Describe the.
CompTIA Network+ N Authorized Cert Guide
Instructor Materials Chapter 8: Network Troubleshooting
Network Troubleshooting
Click to edit Master subtitle style
Instructor Materials Chapter 9: Testing and Troubleshooting
Planning and Troubleshooting Routing and Switching
Configuring EtherChannels and Switch Troubleshooting
2018 Real CompTIA N Exam Questions Killtest
The Troubleshooting theory
Presentation transcript:

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Network Troubleshooting  Network Troubleshooting Models  Network Troubleshooting Utilities  Hardware Troubleshooting Tools  Common Connectivity Issues

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Troubleshooting Recognition Diagnosis Resolution

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Troubleshooting Models Step-by-step approach Administrator

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The Network+ Troubleshooting Model 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 1: Identify the Problem 1. Identify the problem  Question users  Re-create the problem  Identify symptoms  Determine if anything has changed 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 2: Establish a Theory of Probable Cause 1. Identify the problem 2. Establish a theory of probable cause  Question the obvious 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 3: Test the Theory to Determine Cause 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause  Determine next steps to resolve the problem 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 4: Establish a Plan of Action to Resolve the Problem and Identify Potential Effects 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects  Establish a plan of action before you start making changes, once you have determined the probable cause  Detail each step that you will take while attempting to resolve the issue 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 5: Implement the Solution or Escalate as Necessary 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary  Implement the plan of action step by step to fix the problem  Or, escalate the issue to the appropriate personnel 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 6: Verify Full System Functionality and If Applicable Implement Preventative Measures 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Step 7: Document Findings, Actions, and Outcomes 1. Identify the problem 2. Establish a theory of probable cause 3. Test the theory to determine cause 4. Establish a plan of action to resolve the problem and identify potential effects 5. Implement the solution or escalate as necessary 6. Verify full system functionality and if applicable implement preventative measures 7. Document findings, actions, and outcomes

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Troubleshooting with IP Configuration Utilities Incorrect IP configuration

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The ping Utility Ping to local system succeeds Ping to local system succeeds Ping to default gateway fails

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The traceroute Utility Start troubleshooting at last valid connection Start troubleshooting at last valid connection

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The arp Utility Incorrect IP address mapping

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The NBTSTAT Utility Service running optimally Service running optimally

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The NETSTAT Utility Queue shows activity No adapter errors Connection valid Listening ports valid Listening ports valid

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. The Nslookup Utility Verify default server Verify that server is responding to queries Verify that server can resolve names

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. SNIPS System and Network Integrated Polling System (SNIPS) offers:  Monitoring of UNIX systems  Command-line and web interfaces  Monitoring functions for network services  Determine status  Report  Real-time reports  Alarms and logs  Four supported monitoring levels:  Info  Warning  Error  Critical

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Network Technician's Hand Tools

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Electrical Safety Rules Electrical safety rules:  Professionals should service high-power equipment  Always disconnect before servicing  Work with a partner  Never bypass safety devices  Use anti-static devices  Perform only the work for which you have sufficient training  Do not attempt repair work when you are tired  Do not assume anything without checking it out for yourself  Do not wear jewelry or other articles that could accidentally contact circuitry and conduct current

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Electrical Safety Rules (Cont.) Electrical safety rules:  Wear rubber-soled shoes to insulate yourself from ground  Suspend work during an electrical storm  Do not handle electrical equipment when your hands or feet are wet or when you are standing on a wet surface  Prevent static electricity from damaging components by standing on a totally insulated rubber mat to increase the resistance of the path to ground

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Wire Crimpers Used to trim the ends of a cable

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Punch Down Blocks There are two types of punch down blocks:  66 Block - Used for terminating telecommunications  110 Block - Used for structured wiring systems

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Punch Down Tools Strips insulation and embeds wire

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Circuit Testers Displays circuit status Plugs into socket

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Multimeters DigitalAnalog

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Cable Testers Adapters for different network types Displays media status Ports for network cable

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Cable Certifiers Cable Certifiers are:  Used to perform tests  Cable testing  Validity testing  Useful in finding short circuits and other faults  Helpful in determining mode of connectivity devices  Full duplex  Half duplex

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Types of Cable Testers and Certifiers Tester or CertifierDescription Certification tester  Determine if network meets ISO or TIA standards (Cat 5e, Cat 6  or Cat7)  Use when copper and fiber media exist on network Qualification tester  Measure possible network data speeds  Used for troubleshooting LAN testers  Test network speed, cable skew, cable propagation delay, cable,  attenuation, and cable verification Network cable certifier  Test network speed and performance

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Crossover Cables Wires crossed over internally

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Hardware Loopback Plugs Crosses over transmit/receive lines

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Time-Domain Reflectometers Time-Domain Reflectometers:  Used for detecting cable problems  Sends an electrical signal out onto the wire and analyzes the signal on its return  Can detect:  Bends  Short circuits  Connector problems  Termination problems on coax networks Optical TDRs used for fiber optic cabling:  Detect fiber length  Determine location of faulty splices, breaks, and bends  Measure attenuation

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Tone Generators and Tone Locators Probe detects signal Tone generatorTone locator Port for network cable

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Environment Monitors Environment monitors help maintain proper operational environment for network equipment:  Humidity  Temperature

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Butt Sets

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. LED Indicators Link indicator Activity indicator

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Network Analyzers Captures frames Displays captured frames and content Displays captured frames and content

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Demarc Responsibility of the Phone Company Responsibility of the Property Owner Outside Wire Inside Wire Wire distribution device Demarcation point

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Wireless Testers Wireless testers are:  Wi-Fi spectrum analyzers used for detecting problems on WLANs  Able to detect:  Wireless devices  Points of interference  Overall health of the WLAN

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. WLAN Survey Software WLAN survey software:  Used for:  Wireless planning  Simulations  Implementations  Simulates WLAN performance  Can determine network coverage areas

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Physical Issues Physical connectivity issues include:  Crosstalk  Near-end crosstalk  Attenuation  Collisions  Shorts  Open impedance mismatches  Interference  Bad modules (SFPs, GBICs)  Cable problems

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Logical Issues Logical connectivity issues include:  Port speed  Port duplex mismatches  Incorrect VLAN assignment  Incorrect IP address  Wrong gateway assignment  Wrong DNS server assignment  Wrong subnet mask

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Wireless Issues Wireless connectivity issues include:  Interference  Incorrect encryption levels  Channel congestion  Incorrect frequency  SSID mismatches  Standard mismatches  Distance  Bounce  Incorrect antenna placement  Configurations  Incompatibilities  Incorrect channel  Latency  Incorrect switch placement

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Routing and Switching Issues Routing and switching issues that might need to be escalated include:  Switching loop  Routing loop  Routing problem  Proxy arp  Broadcast storms  Port configuration  VLAN assignment  Mismatched MTU/MUT blackhole

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Reflective Questions 1.In your troubleshooting experience, what types of problems have you encountered? How did you diagnose the problems? 2.In your opinion, what are the common TCP/IP issues that you encounter during troubleshooting?