Confidential Rapid Troubleshooting for Data, VoIP, and Video VoIP Performance Manager.

Slides:



Advertisements
Similar presentations
© NetBrain Technologies Inc. All rights reserved NetBrain In Action Real World Use Cases:
Advertisements

Page 1 / 14 The Mesh Comparison PLANET’s Layer 3 MAP products v.s. 3 rd ’s Layer 2 Mesh.
Ver 1,12/09/2012Kode :CIJ 340,Jaringan Komputer Lanjut FASILKOM Routing Protocols and Concepts – Chapter 2 Static Routing CCNA.
1 Semester 2 Module 4 Learning about Other Devices Yuda college of business James Chen
Chapter 5 Networks. Learning Objectives After reading this chapter the reader should be able to: Understand the importance of networks in the field of.
11 TROUBLESHOOTING Chapter 12. Chapter 12: TROUBLESHOOTING2 OVERVIEW  Determine whether a network communications problem is related to TCP/IP.  Understand.
Introduction to Network Analysis and Sniffer Pro
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 9: Troubleshooting the Network Connecting Networks.
QoS Solutions Confidential 2010 NetQuality Analyzer and QPerf.
1 Version 3 Module 8 Ethernet Switching. 2 Version 3 Ethernet Switching Ethernet is a shared media –One node can transmit data at a time More nodes increases.
Monitoring a Large-Scale Network: Selecting the Right Tool Sayadur Rahman United International University & Network Manager, Financial Service.
1 CCNA 2 v3.1 Module 9. 2 Basic Router Troubleshooting CCNA 2, Module 9.
Network Monitoring: A Practical Approach Philip Smith/IT Services University of Windsor March 21, 2003.
NetFlow Analyzer Drilldown to the root-QoS Product Overview.
1 CCNA 2 v3.1 Module 8. 2 TCP/IP Suite Error and Control Messages CCNA 2 Module 8.
Hardware & Software Needed For LAN and WAN
Understanding Network Failures in Data Centers: Measurement, Analysis and Implications Phillipa Gill University of Toronto Navendu Jain & Nachiappan Nagappan.
COMPUTER NETWORKS.
Troubleshooting Software Tools vs. Professional Test Equipment.
Chapter Six NetworkingHardware. Agenda Questions about Ch. 11 Midterm Exam Ch.6 Cable kit.
CCNA Introduction to Networking 5.0 Rick Graziani Cabrillo College
1 Version 3.1 Module 4 Learning About Other Devices.
Semester 1 Module 8 Ethernet Switching Andres, Wen-Yuan Liao Department of Computer Science and Engineering De Lin Institute of Technology
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.
Net Optics Confidential and Proprietary Net Optics appTap Intelligent Access and Monitoring Architecture Solutions.
1 Root-Cause Network Troubleshooting Optimizing the Process Tim Titus CTO, PathSolutions.
Common Devices Used In Computer Networks
OV Copyright © 2011 Element K Content LLC. All rights reserved. Network Management  Network Monitoring  Configuration Management Documentation.
1. There are different assistant software tools and methods that help in managing the network in different things such as: 1. Special management programs.
An Introduction to IBM Systems Director
Repeaters and Hubs Repeaters: simplest type of connectivity devices that regenerate a digital signal Operate in Physical layer Cannot improve or correct.
 Network Segments  NICs  Repeaters  Hubs  Bridges  Switches  Routers and Brouters  Gateways 2.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 9 Basic Router Troubleshooting.
Time lag between discovering issue and resolving Difficult to find solutions and patches that can help resolve issue Service outages expensive and.
Discovery 2 Internetworking Module 5 JEOPARDY John Celum.
Connecting to a Network Lesson 5. Objectives Understand the OSI Reference Model and its relationship to Windows 7 networking Install and configure networking.
Communication Networks Fourth Meeting. Types of Networks  What is a circuit network?  Two people are connected and allocated them their own physical.
Existing Solution 1 Proactive – SLR 6 hour schedule activities for managed services Stop light report is posted and reviews any open tickets for.
Chapter 6 – Connectivity Devices
Company LOGO Networking Components Hysen Tmava LTEC 4550.
Use cases Navigation Problem notification Problem analysis.
Computer Networks. A computer network is defined as the interconnection of 2 or more independent computers or/and peripherals. Computer Network.
OBJECTIVE: o Describe various network topologies o Discuss the role of network devices o Understand Network Configuration Factors to deploy a new network.
OSI Model. Switches point to point bridges two types store & forward = entire frame received the decision made, and can handle frames with errors cut-through.
Sem1 - Module 8 Ethernet Switching. Shared media environments Shared media environment: –Occurs when multiple hosts have access to the same medium. –For.
Saeed Darvish Pazoki – MCSE, CCNA Abstracted From: Cisco Press – ICND 1 – Chapter 10 Ethernet Switch Configuration 1.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Static Routing Routing Protocols and Concepts – Chapter 2.
Chapter 13: LAN Maintenance. Documentation Document your LAN so that you have a record of equipment location and configuration. Documentation should include.
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.
Monitoring Troubleshooting TCP/IP Chapter 3. Objectives for this Chapter Troubleshoot TCP/IP addressing Diagnose and resolve issues related to incorrect.
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.
Copyright Introduction to Computer Networking Learning About Other Devices.
Cisco Confidential © 2013 Cisco and/or its affiliates. All rights reserved. 1 Cisco Networking Training (CCENT/CCT/CCNA R&S) Rick Rowe Ron Giannetti.
Confidential Rapid Troubleshooting for Data, VoIP and Video VoIP & Network Performance Management Solutions.
© 2014 Level 3 Communications, LLC. All Rights Reserved. Proprietary and Confidential. Simple, End-to-End Performance Management Application Performance.
Submitted by : yateendra sahu Et&T 7 th B R/N :
1 Root-Cause Network Troubleshooting Optimizing the Process Tim Titus CTO PathSolutions.
INTRODUCTION TO COMPUTER NETWORKS BY: SAIKUMAR III MSCS, Nalanda College.
Instructor Materials Chapter 8: Network Troubleshooting
OptiView™ XG Network Analysis Tablet
Planning and Troubleshooting Routing and Switching
Configuring EtherChannels and Switch Troubleshooting
Chapter 5 Networks Communicating and Sharing Resources
Network Performance Manager
Discovering Problems Network Anomalies can occur anytime, anyplace for a wide variety of reasons 3:09pm 20% Packet loss due to duplex mismatch 2:36pm Over-utilized.
Use of Simplex Satellite Configurations to support Internet Traffic
Chapter 15: Network Monitoring and Tuning
Presentation transcript:

Confidential Rapid Troubleshooting for Data, VoIP, and Video VoIP Performance Manager

Discovering Problems 2:36pm Over-utilized WAN link causes packet loss 4:26pm Broadcast storm caused by mis- configured network printer 3:09pm 20% Packet loss due to duplex mismatch 11:15am Performance degradation due to under-powered router 2

Call Simulators Fail to Find Source 20% Loss Detected Install Agent Test traffic injected into the network Result: You have no idea which link (A, D, E, F, G) caused the packet loss between these two agents. 3

Analyzers Fail to Locate Problems Install Analyzer 20% Loss Detected Result: Analyzer has no idea where or why packets went missing. 4

Solution Requirements Detect:  WHEN network problems occur  WHERE network problems occur  WHY network problems occur Install & auto-configure in under 15 minutes. Run on low-end hardware or VM (saves $$$). 5

How PathSolutions Works Install PathSolutions All Switches and Routers are queried for information Result: One location is able to monitor all links in the entire network for performance and errors. 6

VoIP Performance Manager Total VoIP Visibility™:  Broad: All ports on all routers & switches  Deep: 18 different error counters collected and analyzed  Network Prescription engine provides plain-English descriptions of errors: “This interface has a duplex mismatch, and this is the full-duplex side of that duplex mismatch” It acts like an extra Senior-level network engineer on your staff: Discovering and helping to resolve network issues before they become business problems. 7

Best Practices Establish Baseline of Network Health 7% Loss from cabling fault 12% Loss from Alignment Errors 11% Loss from Collisions 28% Loss from Duplex mismatch 8

Best Practices Repair Issues 7% Loss from cabling fault 12% Loss from Alignment Errors 11% Loss from Collisions 28% Loss from Duplex mismatch 9

Best Practices Monitoring & Alerting 11% Loss from Collisions Alert  MSP Portal 10

Call Path Analysis Report 11:32am 100% Transmit utilization 15% Loss from discards Latency & Jitter penalty incurred 7:56am 18% Loss from FCS Errors 12:02pm 12% Loss from Collisions 11

Unique Agent-less Call Simulator Test to any IP address that responds to a ping: VoIP phones Gateways Router links Internet traceroute hops

Quickly Locate VoIP Phones Phones tab identifies where (switch and port) VoIP devices are connected along with their health. 13

Easily Understood Web Reports Check historical usage of any interface View current utilization of any interface

Powerful Network Prescription Additional error details are provided to remedy the problem Network Prescription provides deep error analysis 15

Handy ed Reports Provides daily visibility into overall network health Easily drill down to problem interfaces

Dynamic Network Map WAN link current utilization updates every 5 seconds for complete network performance visibility 17

Key Differences  Comprehensive coverage  Localization of errors  Determination of exact error cause  Continuous monitoring  Less installation/configuration effort  Centralized Alerting 18