Troubleshooting Software Tools vs. Professional Test Equipment.

Slides:



Advertisements
Similar presentations
Learning about Neighboring and Remote Devices PJC CCNA Semester 2 Ver. 3.0 by William Kelly.
Advertisements

© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 3: VLANs Routing & Switching.
EE 545 – BOGAZICI UNIVERSITY. Agenda Introduction to IP What happened IPv5 Disadvantages of IPv4 IPv6 Overview Benefits of IPv6 over IPv4 Questions -
Chapter 5 Intro to Routing & Switching.  Upon completion of this chapter, you should be able to:  Describe the operation of the Ethernet sublayers.
TCP-IP Primer David Cozens. Targets Have a basic understanding of Ethernet network technology Be aware of how this technology is applied on the 5000 series.
Ver 1,12/09/2012Kode :CIJ 340,Jaringan Komputer Lanjut FASILKOM Routing Protocols and Concepts – Chapter 2 Static Routing CCNA.
Instructor & Todd Lammle
NetTool - Basic Overview Slide 1 of 13 Product Training NetTool NetTool Inline Network Tester Troubleshoot and Verify PC and Network Connections.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 9: Troubleshooting the Network Connecting Networks.
MCDST : Supporting Users and Troubleshooting a Microsoft Windows XP Operating System Chapter 13: Troubleshoot TCP/IP.
Router Components Semester 2 Chapter 4. Table of Contents More on Components The Show Command Network Neighbor Routers Basic Network Testing.
Network+ Guide to Networks, Fourth Edition
1 K. Salah Module 4.0: Network Components Repeater Hub NIC Bridges Switches Routers VLANs.
Institute of Technology Sligo - Dept of Computing Router Components Semester 2 Chapter 4 Paul Flynn.
5-1 Data Link Layer r Today, we will study the data link layer… r This is the last layer in the network protocol stack we will study in this class…
1 K. Salah Module 4.3: Repeaters, Bridges, & Switches Repeater Hub NIC Bridges Switches VLANs GbE.
Hubs & Switches Ethernet Basics -10. There is only so much available bandwidth, in some instances it can be dynamic An overabundance of data on the network,
Troubleshooting methods. Module contents  Avaya Wireless tools  Avaya Wireless Client Manager  Avaya Wireless AP Manager  Hardware indicators  Non.
Fundamentals of Networking Discovery 1, Chapter 9 Troubleshooting.
George Njoroge CSCIE 139 Hosted vs. Managed VoIP Hosted VOIP is utilizing a company for phone connectivity (soft and hard), extensions,
Connecting LANs, Backbone Networks, and Virtual LANs
MESH Implementation With AP5131 version R.
Document Number ETH West Diamond Avenue - Third Floor, Gaithersburg, MD Phone: (301) Fax: (301)
© 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.
Firewall Typical Networking and Troubleshooting Common Faults.
© 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.
1 ISP Help Desk Working at a Small-to-Medium Business or ISP – Chapter 2.
1 Introducing… EtherScope Network Assistant TM The fast assistant for network problem solvers Channel Partner Product Introduction Presentation.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 3: Implementing VLAN Security Routing And Switching.
COEN 252 Computer Forensics
1 Root-Cause Network Troubleshooting Optimizing the Process Tim Titus CTO, PathSolutions.
1 Positioning Statement LinkRunner Network Multimeter An essential personal tool to quickly verify network connectivity and availability 1.
Chapter 8 Help is here!. Cabling Whenever you need cabling that will protect your signal from electrical interference there is only one correct answer:
ONETOUCH™ AT NETWORK ASSISTANT EVALUATION GUIDE May 14, 2012.
Common Devices Used In Computer Networks
Operating Systems Lesson 10. Networking Communications protocol is the set of standard rules for ◦ Data representation ◦ Signaling ◦ Authentication ◦
Cisco S2 C4 Router Components. Configure a Router You can configure a router from –from the console terminal (a computer connected to the router –through.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 9 Basic Router Troubleshooting.
Sysops Network Training by Brett Haffener. Introductions - Name - School - What are you most interested in learning about?
Networking Components Daniel Rosser LTEC Network Hub It is very difficult to find Hubs anymore Hubs sends data from one computer to all other computers.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Exploring the Enterprise Network Infrastructure Introducing Routing and Switching.
CCNA 2 Week 9 Router Troubleshooting. Copyright © 2005 University of Bolton Topics Routing Table Overview Network Testing Troubleshooting Router Issues.
Net Optics Confidential and Proprietary 1 Bypass Switches Intelligent Access and Monitoring Architecture Solutions.
9: Troubleshooting Your Network
1 Root-Cause VoIP Troubleshooting Optimizing the Process Tim Titus CTO, PathSolutions.
Network Troubleshooting
Network Management CCNA 4 Chapter 7. Monitoring the Network Connection monitoring takes place every day when users log on Ping only shows that the connection.
ERICSON BRANDON M. BASCUG Alternate - REGIONAL NETWORK ADMINISTRATOR HOW TO TROUBLESHOOT TCP/IP CONNECTIVITY.
Confidential Rapid Troubleshooting for Data, VoIP, and Video VoIP Performance Manager.
Confidential Rapid Troubleshooting for Data, VoIP and Video VoIP & Network Performance Management Solutions.
+ Lecture#8: VLAN Asma AlOsaimi Topics VLAN Segmentation VLAN Implementation VLAN Security and Design 3.0.
Redundant Bricks Configuration Example Lucent Security Products Configuration Example Series.
Cisco CCNA Cisco Certified Network Associate.
1 Root-Cause Network Troubleshooting Optimizing the Process Tim Titus CTO PathSolutions.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 ISP Help Desk Working at a Small-to-Medium Business or ISP – Chapter.
Configuring Network Devices
Networking and firewall
Instructor Materials Chapter 8: Network Troubleshooting
OptiView™ XG Network Analysis Tablet
Instructor Materials Chapter 6: VLANs
Planning and Troubleshooting Routing and Switching
Welcome! Thank you for joining us. We’ll get started in a few minutes.
LXI Consortium Presentation Aug 5, 2017
Configuring EtherChannels and Switch Troubleshooting
Instructor & Todd Lammle
Chapter 5: Switch Configuration
Routing and Switching Essentials v6.0
Data Link Issues Relates to Lab 2.
Chapter 5: Switch Configuration
Network Performance Manager
Presentation transcript:

Troubleshooting Software Tools vs. Professional Test Equipment

LanXPLORER vs. Software Tools and the Winner is... ?

Some examples for common network issues: No physical connection electrical No physical connection optical No functional connection No logical connection on Layer 3 (IP) Poor Network perfomance Poor Speech Quality LanXPLORER vs. Laptop APAP

Loading... READY While a PC is still booting A test device already has tested and displayed Connection Type Switchport Configuration PoE DHCP let's start our testers! A field tester takes Several seconds to Boot up LanXPLORER vs. Laptop Activ Network, WiFi + Passive Cabling + PoE (only U&I) + Bandwith, Load VoIP = A PC takes several minutes to boot up

No physical connection Eletrical Possible Causes Wrong Port on patchpanelsTone Generator Faulty CableWiremap Wrong PinningWiremap Too long Cable (> 100m)Wiremap LanXPLORER vs. Laptop

No physical connection Optical Possible Causes Wrong PortOptical Interface Errors of FibersOptical Interface Power Level is too high/lowStatistics AttenuationStatistics Very quick identification if link can be established. With the Hub Blink function the LEDs of the switchports are flashing Mostly Rx and Tx are twisted. This can easily be tried out. The received an transmitted levels are detected Attenuation can be evaluated when the fiber is looped at the far end LanXPLORER vs. Laptop

No functional connection Possible Causes Wrong Port Settings CPEInline Mode (Customer Premises Equipment) Wrong Port Settings far EndStatistics (mostly on switches) PoE is not delivered / too lowStartscreen, PoE PoE is on the wrong pinsPoE Test Easy scenario to see if the Interface configurations are matching Does show what partner we are connected to, its link capabilities and its autoneg status LanXPLORER vs. Laptop

No logical connection (Layer 3 / IP) Possible Causes No DHCP Adress AssignmentStatistics Duplicated DHCP ServerStatistics Wrong CPE ConfigurationPC-Diagnostics (User Equipment, PC, Phone,...) Does easily show if there are two or more DHCP servers. It happens often due to wrong configuration of network devices Does show if the device (CPE) is getting its correct DHCP informations. CPE is connected inline and is not removed from the network LanXPLORER vs. Laptop

Poor Network Performance Possible Causes Half Duplex due to wrong settingsStatistics Layer 2 Errors (Mac Layer)Statistcs due bad cables / fibers Wrong CPE ConfigurationPC-Diagnostics Properties of the network adaptor. CPE must be removed Easy scenario to see if the Interface configurations are matching (Inline) LanXPLORER vs. Laptop

Bad VoIP Quality Possible Causes Packet Loss, Latency, JitterVoIP Network is utilizedInline Statistics Link is erroredError Counters Only limited options. Laptop can only work in Endpoint mode and replace the phone. A potential error source is therefore removed from the network Very good, as the LanXPLORER is inline connected. It is observing from both directions (network and CPE) LanXPLORER vs. Laptop

ToneGen Wiremap Hub Blink PoE Loop WiFi Scan Netmap: Netverify      Only limited funtionality with a software, e.g. Wireshark. No Top Ten functionality A Laptop can only replace a CPE, but not look for its values requires software and can oly replace a phone. A potential error cause is therefore removed. Troubleshooting is much more difficult. only some things can be done with software. But o bandwith mesurments, Layer 2 Errors, Partner Configurations,... requires additional software   TopTen Ping Traceroute PC-Diag VoIP Statistics Autotest Functional Summary LanXPLORER vs. Laptop

Why we don't use laptops… Most companies do not accept foreign laptops in their network (virus risk) Layer 2 Bandwith evaluation is only calculated from higher layers down to layer 2 and not measured (e.g. freeware "Iperf") Most freeware tools are only free for private usage In many cases the Laptops firewalls have to be turned off (which is mostly forgotten and test are failing. The failed test are guiding us in the wrong direction.) If the firewalls are turned off then many times it is forgotten to switch them on again (virus risk) Laptops can only work with traffic which is arriving at all. They are testing on IP-Layer and can therefore not detect Layer 2 and Layer 1 issues Protocol analysis and monitoring requires manageable switches (port mirroring)

LanXPLORER vs. Laptop 60% of the switches are unmanaged (Source Siemens) XXXXXXXXXXXXXXXXXXXX 50% of the managed ones are secured, where the engineers havo no access rights 50% of the engineers do not have sufficient skills for the switchconfiguration Monitoring with a Laptop can be done here: Monitoring with the LanXPLORER can be done here! Monitoring by portmirroring

LanXPLORER vs. Laptop Simultaneous monitoring in the same network.105 Packets have been monitored with: LanXPLORER Wireshark

LanXPLORER vs. Laptop Simultaneous monitoring in the same network.105 Packets have been monitored with: Wireshark Very detailled inspection of the arrived packets Expert Analysis of protocols, content and applications (its intention) No detection of Layer 2 Network errors. No detection of faulty connections and links.

LanXPLORER vs. Laptop Simultaneous monitoring in the same network.105 Packets have been monitored with: LanXPLORER Overview of the most spoken protocols No inspection of packets Very quick and easy overview about the network status (its intention) ARP on place two >>> misconfiguration in the network 105 Packets are monitored 46 Packets are lost due to FCS errors FCS errors are mainly caused by faulty cables or interfaces (Layer 1) 151 Packets were reveived in summary The lost traffic can not be detected by a Laptop

LanXPLORER vs. Laptop Simultaneous monitoring in the same network.105 Packets have been monitored with: LanXPLORER Wireshark Not comparable

LanXPLORER vs. Laptop Good for its job Troubleshooting: Good for its job network scanning: LanXPLORER Perfect Network Scanner Detailled netmap (enhanced in new release) and other important things on layer 1 and 2:

LanXPLORER vs. Laptop Good for its job Troubleshooting: Good for its job pinging LanXPLORER Ping Plotter Ping Test and other important things on layer 1 and 2:

1.Time Saving Find network issues fast and easy 2.Cost Saving Reduce the network dowtime Minimize the man-hours for fault finding 3.Easy to use This product does not even require a manual 4.Clear readings Definitive answers to network issues Main Product Benefits

Thank you