Tài liệu Module 11: Troubleshooting a Network Load Balancing Cluster doc

Contents Module 11: Troubleshooting a Network Load Balancing Cluster Overview Using Status Tools and Utilities Troubleshooting Problems 13 Using Network Tools and Utilities 16 Lab A: Network Load Balancing Cluster Troubleshooting 21 Review 27 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2000 Microsoft Corporation All rights reserved Microsoft, Active Directory, BackOffice, Jscript, PowerPoint, Visual Basic, Visual Studio, Win32, Windows, Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries Other product and company names mentioned herein may be the trademarks of their respective owners Program Manager: Don Thompson Product Manager: Greg Bulette Instructional Designers: April Andrien, Priscilla Johnston, Diana Jahrling Subject Matter Experts: Jack Creasey, Jeff Johnson Technical Contributor: James Cochran Classroom Automation: Lorrin Smith-Bates Graphic Designer: Andrea Heuston (Artitudes Layout & Design) Editing Manager: Lynette Skinner Editor: Elizabeth Reese Copy Editor: Bill Jones (S&T Consulting) Production Manager: Miracle Davis Build Manager: Julie Challenger Print Production: Irene Barnett (S&T Consulting) CD Production: Eric Wagoner Test Manager: Eric R Myers Test Lead: Robertson Lee (Volt Technical) Creative Director: David Mahlmann Media Consultation: Scott Serna Illustration: Andrea Heuston (Artitudes Layout & Design) Localization Manager: Rick Terek Operations Coordinator: John Williams Manufacturing Support: Laura King; Kathy Hershey Lead Product Manager, Release Management: Bo Galford Lead Technology Manager: Sid Benavente Lead Product Manager, Content Development: Ken Rosen Group Manager, Courseware Infrastructure: David Bramble Group Product Manager, Content Development: Julie Truax Director, Training & Certification Courseware Development: Dean Murray General Manager: Robert Stewart Module 11: Troubleshooting a Network Load Balancing Cluster iii Instructor Notes Presentation: 30 Minutes Lab: 15 Minutes This module provides students with the knowledge and skills to troubleshoot a Network Load Balancing cluster by using various status and networking tools and utilities After completing this module, students will be able to: Describe the status tools that are available to monitor and analyze a Network Load Balancing cluster Identify troubleshooting issues that occur within the Network Load Balancing cluster Describe the networking tools that are used to detect and troubleshoot network problems Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module Required Materials To teach this module, you need the Microsoft® PowerPoint® file 2087A_11.ppt Preparation Tasks To prepare for this module, you should: Read all of the materials for this module Complete Lab A: Network Load Balancing Cluster Troubleshooting Study the review questions and prepare alternative answers to discuss Anticipate questions that students may ask Write out the questions and provide the answers iv Module 11: Troubleshooting a Network Load Balancing Cluster Demonstration This section provides demonstration procedures that will not fit in the margin notes or are not appropriate for the student notes Examining Network Properties To prepare for the demonstration Install the full version of Network Monitor from Systems Management Server 2.0 on the instructor computer Install the Network Load Balancing parser files from the Microsoft Windows® 2000 Server resource kit The installation of the parser dlls requires modification of several ini files for Network Monitor The procedure is documented in the resource kit tools; you can search for wlbs to find it If you not install the Network Load Balancing parser into Network Monitor, the heartbeat traffic will not be parsed and displayed The heartbeat traffic will be available for display only as binary data Install the capture files from the Instructor CD into the capture directory for your installation of Network Monitor Module 11: Troubleshooting a Network Load Balancing Cluster v Module Strategy Use the following strategy to present this module: Using Status Tools and Utilities Review the concepts of direct and inferred status information with the students Remind the students that monitoring system performance is an important part of maintaining and administering a Network Load Balancing cluster Access Computer Management and demonstrate the Performance Tool for the class Prior to the Discussion: Acquiring Data with the Performance MMC, review with the students how they can collect the performance data, then store and use it for later analysis Briefly review Network Monitor with the students; they should be familiar with this tool Ask the students how they have used this networking tool Review with the students the types of event logs that they can expect to see for a Network Load Balancing cluster and how they can use these logs to troubleshoot the cluster Troubleshooting Problems Explain to the students that the table of troubleshooting issues is only a partial list There are many more possible troubleshooting issues that are listed under troubleshooting in the Wlbs help files Using Network Tools and Utilities Review the network tools and utilities with the students Module 11: Troubleshooting a Network Load Balancing Cluster Overview Topic Objective To provide an overview of the module topics and objectives Lead-in In this module, you will learn about the tools, utilities, and commands that are used to monitor, analyze, and troubleshoot a Network Load Balancing cluster Using Status Tools and Utilities Troubleshooting Problems Using Network Tools and Utilities *****************************ILLEGAL FOR NON-TRAINER USE****************************** When troubleshooting a Network Load Balancing cluster you will find that configuration errors, automated responses to failures, and changes to the network infrastructure can change the status of a cluster For example, if a single host within a cluster fails to come online, the cluster will not converge To troubleshoot a Network Load Balancing cluster, you can use the various tools that are available to analyze the problem without visiting the management console on the failed cluster member Error handling in the Network Load Balancing cluster is designed to minimize the possibility of disrupting the cluster’s service to client requests, while allowing a cluster’s parameters and member hosts to dynamically change as required For example, you can add hosts to the cluster, remove them for maintenance, add port rules, and modify rule parameters, all without interrupting Cluster service The cluster administrator must decide how to monitor changes in the cluster status and how to investigate failures in both the configuration and operation of the cluster After completing this module, you will be able to: Describe the status tools that are available to monitor and analyze a Network Load Balancing cluster Identify troubleshooting issues that occur within the Network Load Balancing cluster Describe the networking tools that are used to detect and troubleshoot network problems Module 11: Troubleshooting a Network Load Balancing Cluster Using Status Tools and Utilities Topic Objective To describe the status tools that are available to monitor and analyze a Network Load Balancing cluster Lead-in While the operation of a Network Load Balancing cluster is automatic after you have properly configured it, you can be required to investigate failures and set performance baselines when troubleshooting The Performance Tool Network Monitor Event Viewer *****************************ILLEGAL FOR NON-TRAINER USE****************************** While the operation of a Network Load Balancing cluster is automatic after you have properly configured it, you can be required to investigate failures and set performance baselines when troubleshooting You use these baselines to test against, and interactively monitor, current cluster performance You can use various tools and utilities in Microsoft® Windows® 2000 to provide status information on the operation of a Network Load Balancing cluster The status tools and utilities provide information on the cluster operation, individual hosts within the cluster, and network conditions for client connections made to the cluster There are two types of status information about cluster operation, direct or inferred Direct Status Information There are tools and utilities that provide direct status information on the operation of a Network Load Balancing cluster; you can collect this data from the following three sources: The events written to the event log by the Network Load Balancing driver Interactive information derived by running Wlbs.exe Interactive information derived from the Windows Management Instrumentation (WMI) provider for Network Load Balancing Module 11: Troubleshooting a Network Load Balancing Cluster Inferred Status Information There are tools that you can use to collect only inferred status information on the operation of the Network Load Balancing cluster These tools and utilities provide information, which you must then interpret to determine the operational status of the cluster The tools and utilities that provide this data are: The Performance tool, which includes the System Monitor tool and Performance Logs and Alerts The Network Monitor tool The Ping.exe and Pathping.exe utilities The Arp.exe utility The Netstat.exe utility Module 11: Troubleshooting a Network Load Balancing Cluster The Performance Tool Topic Objective To describe how you can use the Performance tool to view the performance of a Network Load Balancing cluster Lead-in Microsoft Windows 2000 provides the Performance tool, which contains the System Monitor and Performance Logs and Alerts Computer Management Action View Tree Computer Management (Local) System Tools Event Viewer System Information Performance Logs and Alerts Counter Logs Trace Logs Alerts Shared Folders Device Manager Name Comment Log File Type Log File Name test Binary File C:\PerfLogs\test_000001.blg System O… This sample log provides an o… Binary File C:\PerfLogs\System_Overview.blg Performance Console Action View Window Help Favorites Tree Favorites Console Root System Monitor Performance Logs and Alerts Counter Logs Trace Logs Alerts 100 75 50 25 Color Scale 1.000 10.000 0.10… Counter % Proc Discover Interrup… Instance _Total _Total Parent - Object Proces… DHCP… Proces… *****************************ILLEGAL FOR NON-TRAINER USE****************************** Key Points There are no specific performance objects and counters for the Network Load Balancing driver Because the driver is installed in the TCP/IP stack the IP data below and above the driver can be monitored Microsoft Windows 2000 provides the Performance tool, which contains the System Monitor and Performance Logs and Alerts You can use these tools or utilities to display and collect performance information for the Network Load Balancing cluster Monitoring system performance is an important part of maintaining and administering your cluster You can use performance data to: Understand your workload and the corresponding effect on your cluster or individual cluster hosts Observe changes and trends in workloads and resource usage so that you can plan for future upgrades to the cluster or decide whether you should implement scale up or scale out strategies Test configuration changes or other tuning efforts by monitoring the results Diagnose problems and target components or processes for optimization System Monitor and Performance Logs and Alerts provide detailed data about the resources that are used by specific components of the operating system and by server programs that have been designed to collect performance data The components of this tool are: Graphs that provide a display for performance-monitoring data Logs that provide recording capabilities for the data Alerts that send notification to users by means of the Messenger service when a counter value reaches, rises above, or falls below a defined threshold 14 Module 11: Troubleshooting a Network Load Balancing Cluster The following table lists a few examples of troubleshooting issues for a Network Load Balancing cluster Symptom Cause Solution “The system has detected an IP address conflict with another system on the network ” is displayed Two different cluster primary IP addresses were entered in the TCP/IP configuration in the Internet Protocol (TCP/IP) Properties dialog box on different hosts Be sure to use one primary cluster IP address for all of the cluster hosts Two different cluster network addresses were entered in the Network Load Balancing Properties dialog box on different hosts Be sure to use one cluster network address for all of the cluster hosts The network adapter could not change its network address This problem occurs only when using a unicast network address (instead of a multicast address) Either switch to a different type of network adapter or use Network Load Balancing multicast support Either a different number of port rules or incompatible port rules on different cluster hosts were entered This will inhibit convergence Open the Network Load Balancing Properties dialog box on each cluster host and verify that all of the hosts have identical port rules After the cluster hosts start, they begin converging but never report that convergence has completed Module 11: Troubleshooting a Network Load Balancing Cluster 15 (continued) Symptom Cause Solution After the cluster hosts start, Network Load Balancing reports that convergence has finished, but more than one host is a default host The cluster hosts have become members of different subnets, so that all hosts are not accessible on the same network Be sure that all of the cluster hosts can communicate with each other Different media access control (MAC) addresses are being used across the cluster, and the cluster’s primary IP address was not assigned when setting up TCP/IP for Network Load Balancing In this case, TCP/IP will not detect an address conflict, and multiple clusters will exist Be sure to use one primary IP address for the cluster and a corresponding MAC address on all hosts within the same cluster, specifying the cluster's primary IP address in the TCP/IP configuration Different clusters are running on the same subnet If you use different primary IP addresses, each with unique corresponding MAC addresses, on various cluster hosts, you can create multiple clusters on the same subnet This is a not a problem unless this behavior was not intended The Network Load Balancing driver did not load successfully when the computer started This problem can arise because another networking driver on which Network Load Balancing depends failed to load, or because the file for the Network Load Balancing driver has been corrupted Run the wlbs query command to verify that the driver was loaded If the command reports an error, check the Windows event log to see why the driver failed to load The network does not appear to work for one or more of the cluster hosts 16 Module 11: Troubleshooting a Network Load Balancing Cluster Using Network Tools and Utilities Topic Objective To describe the networking tools and utilities that are used to detect and troubleshoot network problems WAN or WAN or Internet Link Internet Link Switch Switch Lead-in As the system administrator, it is important that you are aware of the network tools that you use to confirm the status of your Network Load Balancing cluster Status Information Used for Diagnosis Router Router •• Verify IP Connectivity Verify IP Connectivity Diagnostic Diagnostic Utilities Utilities •• Isolate Network Problems Isolate Network Problems •• Diagnose Client Traffic Diagnose Client Traffic *****************************ILLEGAL FOR NON-TRAINER USE****************************** As the system administrator, it is important that you are aware of the network tools that you use to confirm the status of your Network Load Balancing cluster You can use these tools and utilities to verify IP-level connectivity, or isolate problems with the network hardware and incompatible network configurations Using network tools and utilities, you can send IP packets to each router over a period of time and then compute results that are based on the returned packets By analyzing this collected data of packets that are sent and returned to a designated router or link, you can determine which routers or links might be causing network problems You use some of these tools and utilities to diagnose client traffic, display information on the Domain Name System (DNS) servers, display protocol statistics, or modify the IP physical address Module 11: Troubleshooting a Network Load Balancing Cluster 17 Network Tools and Utilities Topic Objective To describe the network tools and utilizes used to determine the status of the Network Load Balancing cluster Netdiag Lead-in Pathping You can use command line network tools and utilities to test the status of both the services and the network infrastructure of your Network Load Balancing cluster Ping Tracert Nslookup Netstat ARP *****************************ILLEGAL FOR NON-TRAINER USE****************************** You can use command line network tools and utilities to test the status of both the services and the network infrastructure of your Network Load Balancing cluster You can use the information collected by these tools and utilities to analyze service, network operation, and variations in performance You can use the tools and utilities interactively, or you can store their output in files for later analysis You can use the following tools and utilities interactively to provide status information about the Network Load Balancing cluster: Netdiag A utility that performs a series of tests to isolate networking and connectivity problems; it is also used to determine the functional state of your network client Netdiag performs extensive testing of the computer on which it is run, including checking the availability of WINS and DNS You install Netdiag with the support tools, which are available in the \Support\Tools directory of your Windows 2000 compact disc Ping A utility used to troubleshoot IP-level connectivity Ping allows you to specify the size of packets to use (the default is 32 bytes), how many to send, whether to record the route used, what Time to Live (TTL) value to use, and whether to set the don't fragment flag Ping provides a minimum average and maximum roundtrip time (RTT), which is useful to analyze where routing delays occur Pathping A route-tracing tool that combines the features of Ping and Tracert with additional unique information Over a period of time, Pathping sends packets to each router on the path to a final destination, and then computes results that are based on the packets that are returned from each hop Pathping shows the degree of packet loss at any given router or link, so that you can pinpoint which routers or links might be causing network problems 18 Module 11: Troubleshooting a Network Load Balancing Cluster Tracert A route-tracing utility that displays a list of router interfaces from the routers along the path between a source host and a destination Tracert uses the IP TTL field in Internet Control Message Protocol (ICMP) Echo Requests and ICMP Time Exceeded messages to determine the path from a source to a destination through an IP internetwork Nslookup A utility that is used for troubleshooting DNS problems, such as host name resolution failure Nslookup displays a command prompt and shows the host name and IP address of the local DNS server You can then perform interactive queries to test DNS name resolution Netstat A utility that is used to display protocol statistics and current TCP/IP connections You can display the connection status and throughput statistics for TCP/IP interfaces in the computer ARP A utility that is used to display and modify the IP-to-physical address translation tables in hosts and routers that the address resolution protocol uses Module 11: Troubleshooting a Network Load Balancing Cluster 19 Demonstration: Examining Network Properties Topic Objective To demonstrate the use of Network Monitor to view cluster traffic Lead-in The purpose of this demo is to use Network Monitor to examine captured data *****************************ILLEGAL FOR NON-TRAINER USE****************************** When demonstrating to the students the data from the captures focus primarily on the ARP queries and responses and the setting up of TCP sessions for data transfers Show the students the heartbeat traffic between cluster hosts Explain to them that displaying the contents of the heartbeat traffic will require the full version of Network Monitor and additional components (Network Load Balancing parser dlls) from the Windows 2000 Server resource kit You can examine the network properties by analyzing the flow of traffic on the network You will use Network Monitor to examine data captured from a network The following demonstration shows a capture from a client (10.10.10.100) where multiple instances of Internet Explorer are started, configured to a default Web site (10.10.10.3) that is served by a 2-host cluster in unicast mode Start Network Monitor by clicking on Start – Programs – Administrative Tools – Network Analysis Tools – Network Monitor Click File, and then Open; in the Open dialog box select NLB_2HOSTS_UNICAST.CAP and then click Open The capture shows the traffic between a client (IP is 10.10.10.100) and a 2-host Network Load Balancing cluster (cluster IP is 10.10.10.3, and the dedicated IP addresses are 10.10.10.4 and 10.10.10.5) Examine the first few frames, which are heartbeat communications between the cluster hosts Note Network Monitor requires additional configuration to display the contents of the Network Load Balancing heartbeat packets The Windows 2000 Server Resource Kit supplies the required dlls and installation information 20 Module 11: Troubleshooting a Network Load Balancing Cluster For the heartbeat frames, show the following: a MAC address fields for the frames b Time interval between heartbeats from the same host c Heartbeat cluster frame size (show the Ether Type registered for NLBS, 0x886F) d Filed for convergence state e Fields for Cluster and dedicated IP addresses f Fields for Port Rules Show ARP request at frame 39, discuss the request, reply, and subsequent TCP connection that is established Show and discuss the following frames: a 18, the ARP request b 19 and 21, the ARP reply from both cluster members c 20, 22 and 23, the Syn, AckSyn and Ack setting up the TCP connection d 24, the Get request from the client for a Web page e 25, the HTTP response (note the HTTP data shows Student1 as the source) f 30, and 31, a Get request and reply (note that the data comes from Student2) g Show other frames as required to show multiple instances of Internet Explorer being opened with the default Web site 10.10.10.3 h Show frames from 265 on that represent Internet Explorer closing and a TCP reset occurring Module 11: Troubleshooting a Network Load Balancing Cluster 21 Lab A: Network Load Balancing Cluster Troubleshooting Topic Objective To introduce the lab Lead-in In this lab, you troubleshoot a Network Load Balancing cluster *****************************ILLEGAL FOR NON-TRAINER USE****************************** Students will commence the lab with a functional 2-host cluster You will work together in pairs and individually to analyze cluster host operations Objectives After completing this lab, you will be able to: Install Network Monitor (NetMon) Use NetMon to view cluster traffic between clients and cluster hosts Prerequisites Before working on this lab, you must be familiar with the concepts in Module 11, “Troubleshooting a Network Load Balancing Cluster.” Estimated time to complete this lab: 15 minutes 22 Module 11: Troubleshooting a Network Load Balancing Cluster Exercise Installing Network Monitor You will work individually and together in pairs to analyze cluster host operations To install a local copy of Network Monitor Note The local copy of Network Monitor will show only traffic that is directed to or generated by the local computer; it cannot capture all network traffic Click Start, point to Settings, and then click Control Panel to open Control Panel In Control Panel, double-click Add/Remove Programs In Add/Remove Programs, click Add/Remove Windows Components In the Windows Components Wizard, select Management and Monitoring Tools, and then click Details Select Network Monitor Tools, and then click OK In the Windows Components Wizard, click Next to continue the installation process If you are asked to insert the CD to copy files, browse to \\London\Setup\Winsrc and click Retry Note Your instructor may advise you to look in a different location for the files When installation is complete, click Finish to close the Windows Components Wizard, and click Close to exit the Add/Remove Programs window Close Control Panel Module 11: Troubleshooting a Network Load Balancing Cluster 23 Exercise Using Network Monitor All students complete this procedure and will work with a partner You will collect information on Network Load Balancing traffic by using the Network Monitor tool The following procedure records, examines, and analyzes traffic on the 2-host cluster Note It is important that you configure the student cluster members to use Multicast at the beginning of this exercise If you not configure the cluster to use Multicast, alter the configuration before starting To install network monitor Click Start, click Run, type cmd in the Open dialog box, and then click OK to open a command prompt window Type wlbs query at the command prompt and press ENTER If the cluster is not CONVERGED with Host as DEFAULT, and Host 1, as members, reconfigure the cluster and restart this procedure On the lowest number student ID computer, click Start, point to Programs, point to Administrative Tools, and then click Network Monitor to start Network Monitor Configure Network Monitor to capture traffic from the Network Load Balancing network adapter Start a capture On the highest number student ID computer, click Start, click Run, type cmd in the Open dialog box, and then click OK to open a command prompt window Type Ping yourclusterIP at the command prompt and press ENTER Type Ping yourdedicatedIP at the command prompt and press ENTER 10 Type Ping yourpartnerdedicatedIP at the command prompt and press ENTER 11 Type Arp –a to show the contents of the ARP cache 12 Record the information provided: Note Notice that the cluster IP address and the local dedicated IP address not have entries in the ARP cache 13 On the lowest number student ID computer, stop the capture 24 Module 11: Troubleshooting a Network Load Balancing Cluster 14 With you partner, examine the trace, and for an ARP request from the dedicated IP address for the higher number student ID computer, record the sender’s hardware and IP address Sender Hardware Address Sender Protocol Address 15 Examine the ARP reply and record the sender’s hardware and IP address Sender Hardware Address Sender Protocol Address What MAC addresses are the cluster members using for the dedicated IP address? In Multicast mode, the cluster members use the adapter MAC address for the dedicated IP address 16 Reconfigure the cluster hosts to use Unicast, by stopping both hosts and clearing Multicast in the Cluster Parameters 17 Restart the cluster hosts and use Wlbs.exe to verify that the cluster hosts are converged 18 On the highest number student ID computer, click Start, point to Programs, point to Administrative Tools, and then click Network Monitor to start Network Monitor 19 Configure Network Monitor to capture traffic from the Network Load Balancing network adapter 20 Start a capture 21 On the lowest number student ID computer, click Start, click Run, type cmd in the Open dialog box, and then click OK to open a command prompt window 22 Type Ping yourclusterIP at the command prompt and press ENTER 23 Type Ping yourdedicatedIP at the command prompt and press ENTER 24 Type Ping yourpartnerdedicatedIP at the command prompt and press ENTER 25 Type Arp –a to show the contents of the ARP cache 26 Record the information provided: Note Notice that there are no cluster entries in the ARP cache Module 11: Troubleshooting a Network Load Balancing Cluster 25 27 On the highest number student ID computer, stop the capture 28 With you partner, examine the trace; and for an ARP request from the dedicated IP address for the lowest number student ID computer, record the sender’s hardware and IP address Sender Hardware Address Sender Protocol Address 29 Examine the ARP request in detail and find the source MAC address that is used to send the packet; it is different than the sender’s hardware address that is used in the ARP request Why is it different, and how can it be changed? The source MAC address is the virtual MAC address configured by Network Load Balancing when using Unicast mode The sender’s MAC address is different because by default MaskSourceMAC is set to in the registry If MaskSourceMAC is set to zero, the source and sender MAC address would be the same 30 Start a Network Monitor capture on both student computers and use your instructor’s computer to Ping the virtual and dedicated IP addresses of your cluster and members 31 Type Arp –a on the instructor computer to show the contents of the ARP cache 32 Record the information provided Note Notice that the MAC address is the same for all of the cluster related entries in the ARP cache 26 Module 11: Troubleshooting a Network Load Balancing Cluster 33 Stop the Network Monitor captures on both cluster hosts and examine the captures Compare the results What differences in response to the ARP requests occur? Both hosts reply to the ARP request for the cluster IP address of the cluster, but each host does not reply to ARP requests for the other host dedicated IP address, even though it does reply to the ICMP Echo requests (the ping) Why are there no heartbeat packets captured by the local copy of Network Monitor? To capture all traffic would require the Network Monitor that is supplied with Microsoft Systems Management Server, which places the network adapter into promiscuous mode This Network Monitor should not be run on a Network Load Balanced host The local Network Monitor driver loads above the Network Load Balancing driver, and receives packets only after the filter process is complete 34 Close all of the applications Module 11: Troubleshooting a Network Load Balancing Cluster 27 Review Topic Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Using Status Tools and Utilities Troubleshooting Problems Using Network Tools and Utilities *****************************ILLEGAL FOR NON-TRAINER USE****************************** Describe the difference between direct and inferred status information The direct status information includes events written to the event log by the Network Load Balancing driver It also includes information derived from the WMI Provider for the Network Load Balancing driver The inferred status information is collected from various tools that you must interpret to determine the operation status of the Network Load Balancing cluster Which performance objects are frequently used to monitor the Network Load Balancing driver? The most frequently used performance objects are IP, TCP, and UDP 28 Module 11: Troubleshooting a Network Load Balancing Cluster Name four tools or utilities that you can use interactively to provide status information about the Network Load Balancing cluster Describe the function of each tool You could have any four of the following possible answers: Netdiag A utility that performs a series of tests to isolate networking and connectivity problems Ping A utility that is used to troubleshoot IP-level connectivity Pathping A route-tracing tool that combines the features of Ping and Tracert Tracert A route-tracing utility that displays a list of router interfaces from the routers along the path between a source host and a destination Nslookup At utility that is used for troubleshooting DNS problems Netstat A utility that is used to display protocol statistics and current TCP/IP connections ARP A utility that is used to display and modify the IP to Physical address translation tables in hosts and routers that are used by the address resolution protocol ... describe the status tools that are available to monitor and analyze a Network Load Balancing cluster Lead-in While the operation of a Network Load Balancing cluster is automatic after you have properly... be able to: Describe the status tools that are available to monitor and analyze a Network Load Balancing cluster Identify troubleshooting issues that occur within the Network Load Balancing cluster. .. install the Network Load Balancing parser into Network Monitor, the heartbeat traffic will not be parsed and displayed The heartbeat traffic will be available for display only as binary data Install