Experimental

To Probe Index

Experimental > Flow Exporter Status

Flow Exporter Status

The Flow Exporter Status probe monitors a Flow Exporter and reports statistics about the Flow activity. It does this by retrieving information from the InterMapper Flows server.

The normal state of the device is UP/OKAY. There are two error conditions:

Filename: com.dartware.flow.exporter.txt
Version: 1.2

Back to Top

Experimental > InterMapper

InterMapper Engine Status

This probe monitors the status of the InterMapper polling engine. With the default setting, this probe displays the results of 500 loops through the polling engine. To measure activity at a finer-grain, decrease the value of the loops parameter. Setting the "loops" parameter to the value 1 will update the statistics on every pass through the main run loop.

The "Main Loop" frequency is the number of times that InterMapper performs the main loop each second. The theoretical maximum loop frequency is 66.667 loops per second, based on the current yield value of 15 msec. If it falls below 10 or even 5 loops per second, InterMapper may report false outages.

This probe also reports polling rate as a percentage of the maximum loops per second. This is a measure of how much additional processing occurs per loop. This percentage will never be 100%. It should, however, level out and remain steady over time.

On Unix systems, this probe reports Context Switches Per Loop (CSPL). This is another measure of the overhead of InterMapper's processing as it runs on your system. Fewer context switches per loop is better (ideal = 0), since context switches carry overhead. A server with thousands of devices and hundreds of mays may well have a CSPL greater than 2 during normal operation. (This value is not available on Windows systems, and is alway set to -1.)

InterMapper tracks the number of bytes sent out the main UDP polling socket. Bytes/Loop is the average bytes sent per loop, averaged over the last batch of N loops. Bytes Peak is the maximum number of bytes sent in a *single* polling loop. (In the current implementation, the peak bytes is checked on every loop, but only resets to 0 when you change the # loops parameter; ie peak bytes is not the peak bytes of the last batch of N loops.)

Filename: com.dartware.tcp.intermapper.txt
Version: 0.8

Back to Top

Experimental > sFlow v1.2

sFlow v1.2 Probe

This probe's Status Window displays the sFlow version, and the address and address type of the sFlow exporter. It relies on the sFlow MIB version 1.2 with the Enterprise Number 4300 to retrieve stats for sFlow versions 2 and 4.

It also displays the sFlowTable, listing all the devices that will receive the sFlow records in an on-demand table. (To view this on-demand table, you must import the SFLOW-MIB, which can be retrieved from http://www.sflow.org/SFLOW-MIB.txt.)

Filename: com.dartware.sflowv1.2.txt
Version: 1.2

Back to Top

Experimental > sFlow Vers. 1.3

sFlow Vers. 1.3

This probe's Status Window displays the sFlow version, and the address and address type of the sFlow exporter. It relies on the sFlow MIB version 1.3, with the Enterprise Number 14706 for sFlow version 5.

It also displays sFlow Receiver Table, listing all the devices that will receive the sFlow records in an on-demand table. (To view this on-demand table, you must import the SFLOW-MIB from http://www.sflow.org/SFLOW-MIB5.txt)

Filename: com.dartware.sflow.v1.3.txt
Version: 1.3

Back to Top