Essential Reference for Monitoring Your IT Infrastructure
How do you choose a network monitoring solution – SNMP monitoring, flow-based monitoring, or packet analysis – that is appropriate for your IT infrastructure?This ebook is essential for your crash course in network monitoring for analysisand learn to use multi-segment analysis, a post-capture technique, to diagnoseperformance problems with distributed application architectures.
Introduction
Choosing a solution for monitoring your IT infrastructure should not be scary. There are 30-40 major flow-basednetwork monitoring solutions on the market today, not to mention flow analyzers, protocol analyzers, and packetanalyzers. How do you determine which solution - or combination of solutions - is right to monitor your networkenvironment? With this Essential Reference in hand, you will be an IT Hero instead of an IT Zero. You will learnhow to:
bull; Choose a monitoring solution – SNMP monitoring, flow-based monitoring, protocol analysis, and/or packet analysis – appropriate for your needs
bull; Measure both network latency and application latency
bull; Determine where to monitor to catch developing problems in complex network topologies, such as distributed application architectures and virtual networks
bull; Discover the benefit of using multi-segment analysis, a post-capture analysis technique across multiple segments, to diagnose performance problems with distributed application architectures.
Crash Course in Network Monitoring
Network Monitoring 101
Network monitoring is far more complex than its name implies. Technically speaking, network monitoring is asystematic checking of key performance metrics to assure that the quality of service and the network capacity arewithin predetermined boundaries. Network monitoring examines an internal network for problems or irregularitieswith the end goal of ensuring network health.
To complete the task of network monitoring, network engineers are ideally equipped with tools that provide themwith an overall as well as a granular view of the network. There are three main technologies that are primarilyused for network monitoring: SNMP, flow-based monitoring, and packet-based monitoring. Each of thesetechnologies has benefits and downsides.
With that in mind let us look at each of the technologies used in network monitoring and determine which one(s)might be the best option for your business.
Simple Network Management Protocol (SNMP)
SNMP is one of the oldest network monitoring techniques on the market, and its main purpose is to managedevices on IP networks. These devices typically include routers, switches, servers, workstations, printers, etc.SNMP data provides network engineers with a high-level view of the condition of networked devices. With SNMPyou can see, for example, the core temperature of a device, what hardware is installed, overall throughput (fornetwork connections), errors and dropped packets per interface, etc.
This device-centric view is one of the major reasons why SNMP is still frequently used. However, one of thedrawbacks to SNMP is that it is based on polling, so configuration for each device is required before meaningfuldata can be obtained, and a specific polling interval must be specified, typically every minute, or longer. As thenumber of devices being monitored grows, SNMP polling can create a significant amount of network traffic, furthertaxing the network you are trying to monitor. In addition, detailed troubleshooting and root-cause analysis ofnetwork issues is not possible with the level of data available via SNMP, so even if you know that a device has aproblem, you cannot typically determine the exact nature of the problem in order to fix it.
SNMP is a bit old fashioned as a network monitoring solution, but it still provides one of the best ways to seedevice metrics and summary-level activity on your networkjust be aware of the network overhead attachedwith SNMP solutions and the limited ability to perform root-cause analysis.
Flow-Based Monitoring
Flow-based monitoring solutions are by far the most popular solutions on the market today. Flow-based solutionsuse existing resources like network switches and/or routers to obtain data that is already being processed bythese devices. It can be very cost-effective because it eliminates the need for additional hardware and software toobtain network data for analysis.
Flow-based technologies are intended to provide network engineers with an overview of network performance,including information like application performance and overall bandwidth utilization. Flow-based systemsanalyze seven distinct characteristics of each packet on the network and group the overall data into networkconversations, or flows. All network statistics must be compiled on the basis of these seven characteristics andthe resulting network flow data.
With all the advantages that flow-based solutions can provide a network engineer, they lack the ability to zero inon specific problems that require deeper packet information and decodes. In addition, flow-based systems canimpact the devices being used to run your network – your switches and routers – when networks get busy. In thiscase, network devices will default to their primary objective, routing IP packets, and loss of flow-based data andanalysis can result.
For a deeper dive into how flow-based systems work, as well as the various vendors and how their products differ,see the Flow-Based Monitoring Solutions section on page 10.
Packet-Based monitoring
Packet-based analysis was historically reserved for deep dive troubleshooting. However, packet-based systemshave evolved into complete network monitoring, reporting, and troubleshooting solutions that can deliver thesame statistical data as flow-based and SNMP systems while also providing the most detailed network analysi
剩余内容已隐藏，支付完成后下载完整资料
英语译文共 12 页，剩余内容已隐藏，支付完成后下载完整资料
资料编号：[484532]，资料为PDF文档或Word文档，PDF文档可免费转换为Word
以上是毕业论文外文翻译，课题毕业论文、任务书、文献综述、开题报告、程序设计、图纸设计等资料可联系客服协助查找。
