|
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
= Installation= Adding Network Devices = Adding Event Monitors = Sending 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 - Monitoring Switches with SNMPScenario Summary: Tembria Server Monitor is used to monitor a large number of network switches that provide the infrastructure for a telecommunications company. Scenario 7: Monitoring Network Switches with SNMP To monitor the status of over 350 network switches that form the customer's network infrastructure, Tembria Server Monitor's SNMP functionality was used. Event monitors were configured to check each of the switches on a regular basis. The customer first grouped this large collection of switches into six different categories representing the different models in use by the corporation. For each category a set of event monitors were defined and associated with each switch in that category. Tembria Server Monitor's SNMP Bandwidth monitor was used to check bandwidth on specified ports and warn if it exceeds specified thresholds. The generic SNMP event monitor was used to check the interface status on each of the critical switches and raise the alarm if any interface is found in an error state. One model of switch in use was prone to overheating unless properly ventilated and would sometimes reboot causing hiccups in network connectivity. This came to light after additional equipment was installed in the networking closets causing the ambient temperature to rise. Tembria's SNMP Uptime event monitor was used to warn whenever a switch rebooted and network administrators were then able to identify replace the problematic devices or improve air flow around them. Back to Scenarios List |
|
| copyright(c) 2003-2010, all rights reserved | ||