Going nuts with traffic monitors
Hello Everyone,
We're just pulling our hair out with this. For now (because we can't get it working at the switch level) we're monitoring network at the server level. We run all Linux boxes. On one particular server we set a monitor to go off if the TX traffic exceeded 650 kbps (put 650 in for the value). We set the rearm at 575 kbps (put 575 in for the value). We started a process that produced a large volume of TX traffic. Sure enough the alarm went off (all good). Then we shut down our testing process. The monitor never came back out of the alarm status eventhough the traffic went well below the rearm value (way, way below).
My questions are:
- Did we set this up correctly
- What units should be values be in (for traffic monitors) bits per second, kbits, mbits??? Can we specify units?
The actual graph data will shift from kbps to mbps depending on whats being graphed so it's really hard to figure out.
Thaks
We're just pulling our hair out with this. For now (because we can't get it working at the switch level) we're monitoring network at the server level. We run all Linux boxes. On one particular server we set a monitor to go off if the TX traffic exceeded 650 kbps (put 650 in for the value). We set the rearm at 575 kbps (put 575 in for the value). We started a process that produced a large volume of TX traffic. Sure enough the alarm went off (all good). Then we shut down our testing process. The monitor never came back out of the alarm status eventhough the traffic went well below the rearm value (way, way below).
My questions are:
- Did we set this up correctly
- What units should be values be in (for traffic monitors) bits per second, kbits, mbits??? Can we specify units?
The actual graph data will shift from kbps to mbps depending on whats being graphed so it's really hard to figure out.
Thaks