|
This mini-tutorial demonstrates how to troubleshoot slow performance in directory services by examining LDAP metrics. You can try out the capabilities of the ExtraHop system for yourself using our free packet analysis tool at http://www.networktimeout.com. To find out more about the ExtraHop system, visit http://www.extrahop.com. VIDEO TRANSCRIPT 1. The ExtraHop Application Delivery Assurance system performs real-time analysis of all transactions across networks, applications, databases, and storage arrays. In this mini tutorial, you will learn how to use the ExtraHop system to inspect the health of directory services. 2. With the ExtraHop system, the investigation generally starts with the Summary page. The Summary page is populated with configuration widgets and shows at-a-glance what's happening across the network and all applications. In the Summary view, by default, the last 30 minutes of activity is displayed. This particular Summary page displays the following widgets: Network Throughput shows the throughput over time in Megabytes per second; Bytes by Application provides a high-level break down of all protocols on the wire; Network Activity shows the various servers on the network by role. LDAP Overview shows the number of LDAP transactions per second as well as the number of errors indicated by the vertical bars at the bottom; 3. In this scenario, a ticket was filed reporting that last week some users experienced problems accessing LDAP services and very slow response times. To investigate a LDAP related problem, click on the LDAP Overview widget to view more details about LDAP activity. 4. The LDAP Server Activity Group page displays at-a-glance what type of messages were sent by the servers and the error count for all discovered LDAP servers. To zoom in on the specific time range where users encountered problems, click on the pull down menu for Time Interval and select custom Data Range. 5. The ExtraHop system retrieves historical data stored for that time range. Here, select the most active LDAP server in terms of Bytes In and Bytes Out to find out more information. 6. Clicking on a device name navigates to a specific LDAP server. The tree control on the left is dynamically populated with the network protocols used by the server. Select LDAP to view detailed metrics for the server. 7. In the LDAP view for this device, detailed LDAP metrics are displayed. This includes an overall distribution of LDAP methods, the error count and the type of errors reported back by the server. The Transactions Per Second chart shows the transaction rate over time, annotated with red dots which represent errors, a vertical bar below each red point corresponds to the number of errors that occurred in the given time interval. Mouse over the red dots shows more information. Here, at around 8:30am, the transaction rate went up dramatically on this LDAP server. Shortly after that, it dropped back down to the normal rate. Scrolling down to look at the Server Processing Time and Processing Time Distribution Information. In this case, even though the overall server processing time did not change substantially during the peak, there were a number of outliers. This means some users did experienced prolonged delays during the time of increased transaction rate. The next step in this investigation is to analyze what exactly caused this increase in activity. 8. Scrolling back up, the Methods table shows that the bulk of the LDAP activity on this server was caused by search requests. Click on the search request counter to display information about the devices that extended these requests. 9. This table displays the IP Address and Host Names of all servers responsible for the LDAP search requests. The top row shows most of the search requests were sent by a single host. Activity on this host is the reason for the increased volume as well as slow response times on this LDAP server. code pour embarquer la vidéo : >>> http://www.youtube.com/embed/Ze8k9vhcBLI <<< |