Bandwidth Management: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
TODO | TODO | ||
= Finding who's causing bandwidth spike = | |||
We find out about bandwidth usage spikes in one of several ways: | |||
* NOC calls and tells us they notice a large usage spike | |||
* we see a system-generated email telling us a customer has passed their usage | |||
* speed complaints are coming in | |||
* we notice the spike on the mrtg page | |||
Determining the cause of the spike is fairly easy with a bit of looking. | |||
Castle:<br> | |||
Open up the mrtg graph for p1a (the top-level switch for most of the machines at castle): mgmt -> monitoring -> p1a -> bytes/sec | |||
From there, you can begin to narrow down which switch is causing the spike, and then you would load the mrtg graph for that switch and further narrow down by port. Word of caution- even though the mrtg graphs show labels to indicate which device is connected to which port, you should take followup steps to confirm which machine is actually in that port (except for 3750 and p1a/p1b where the labeling should accurate). See [[Switch_Control#Finding_which_IPs_are_on_a_port|Finding which IPs are on a port]] | |||
= Caps = | = Caps = | ||
Revision as of 16:00, 10 January 2013
TODO
Finding who's causing bandwidth spike
We find out about bandwidth usage spikes in one of several ways:
- NOC calls and tells us they notice a large usage spike
- we see a system-generated email telling us a customer has passed their usage
- speed complaints are coming in
- we notice the spike on the mrtg page
Determining the cause of the spike is fairly easy with a bit of looking.
Castle:
Open up the mrtg graph for p1a (the top-level switch for most of the machines at castle): mgmt -> monitoring -> p1a -> bytes/sec
From there, you can begin to narrow down which switch is causing the spike, and then you would load the mrtg graph for that switch and further narrow down by port. Word of caution- even though the mrtg graphs show labels to indicate which device is connected to which port, you should take followup steps to confirm which machine is actually in that port (except for 3750 and p1a/p1b where the labeling should accurate). See Finding which IPs are on a port