|
Tembria Server Monitor Menu
= Introduction and Overview= 100% Agentless Monitoring = Screenshots and Videos = Dashboards = Event Monitors = Notifications = System Requirements = Download Now Step-by-Step Evaluation
= How to Install Tembria Server Monitor= How to Add Network Devices = Adding Event Monitors = How to Send Notifications = Viewing Dashboards = Viewing Reports = Advanced Topics Resources
= Pricing and How to Order= Scenarios = 1. Monitoring Critical Servers = 2. Finding Bandwidth Hogs = 3. Detecting Rogue Machines = 4. Monitoring Event Logs = 5. Monitoring Through VPNs = 6. Monitoring Through Firewalls = 7. Monitoring Switches w/ SNMP = FAQs = Version History |
Tembria Server Monitor - Finding Bandwidth HogsScenario Summary: Tembria's bandwidth monitoring features were used to detect excessive bandwidth use by users and applications. Scenario 2: Finding Bandwidth Hogs One month a customer received a bill from their Internet service provider that was four times the expected amount. During the course of the month they had exceeded their bandwidth allowance and now had to pay a premium for extra bandwidth. There had been no fundamental change in their network to explain the excessive bandwidth use so the customer used Tembria Server Monitor's bandwidth monitoring ability to determine the cause of the problem. The first step was to add an instance of the SNMP bandwidth event monitor and have it monitor the router that connects to the company's Internet service provider. This revealed a steady use of about 650K per second. The event monitor revealed that of that total, approximately 20K per second was in outgoing bandwidth while the remaining 630K per second was incoming bandwidth. From the router, traffic flows to a main switch which is connected to a set of secondary switches providing connectivity to each of the company's four floors. A second SNMP bandwidth monitor was configured to watch each of the interfaces on the main switch. Letting event monitors run overnight revealed several interesting pieces of information. At 2:00am alerts were generated when an automated backup of a system caused a spike in network traffic. The event monitor was reconfigured to not run between 1:00am and 3:00am which is the customer's standard maintenance window. The interface leading to one of the customer's floors showed a steady incoming bandwidth rate that was much higher than it ought to be. Adding a Windows Bandwidth event monitor to check each of the machines on that floor revealed that four of them were responsible for the majority of the traffic. Further investigation revealed those machines were running P2P file sharing software, a violation of the company's policies. The P2P software was uninstalled and the users reprimanded. Back to Scenarios List |
|
| Copyright(c) 2003-2011 Tembria, all rights reserved. | ||