Ad Widget

Collapse

NETWORK MONITOR PROBLEMS WITH "net.if.in"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • blagojkk
    Junior Member
    • Jun 2006
    • 2

    #1

    NETWORK MONITOR PROBLEMS WITH "net.if.in"

    Hello all.

    I have a little problem with a network monitoring. I have net.if.in[eth0], net.if.in[eth1], net.if.out[eth0], net.if.out[eth1] etc... all configured with 'Type of information - Numeric (integer64bit)', 'Use multiplier - Custom multiplier', 'Custom Multiplier - 8', 'Store value - Delta (speed per second),

    For some reason they all shows back values around 10GBps. But I have 100MBps network.

    Has anyone had this happen before?

    Any idea what's going on? I'm using 1.1 version.

    Thanks in advance.
  • achu_sab
    Member
    • May 2006
    • 49

    #2
    You didn't specified about the unit you have used,

    Try this settings:

    Key : net.if.in[eth0]
    Type of information : Numeric(float)
    Units : b/s
    Custom multiplier : 8
    Store value : Delta (Speed per second)

    Comment

    • blagojkk
      Junior Member
      • Jun 2006
      • 2

      #3
      I didn't specify any value in that field. Anyway I tried the one bellow and still not working.

      Thanks.


      Originally posted by achu_sab
      You didn't specified about the unit you have used,

      Try this settings:

      Key : net.if.in[eth0]
      Type of information : Numeric(float)
      Units : b/s
      Custom multiplier : 8
      Store value : Delta (Speed per second)

      Comment

      • Nate Bell
        Senior Member
        • Feb 2005
        • 141

        #4
        This was mentioned on another thread. The problem is the new way the data is calculated is as a delta (speed per second) and this conflicts with the old way if you still have old data in your history. I was getting similar numbers until I cleared the history for these items and turned them back on. Now I'm getting realistic values.

        The downside is you have to lose any stored history for these items. Luckily, that worked for me just fine since we only have a few servers where we carefully monitor these values. If the past history is important to you, you might be able to do some tricky multiplication to make your values more realistic (such as value x .0001), but I'm not sure which mutiplier won't give you bogus results. As they say, YMMV.

        Nate
        Last edited by Nate Bell; 26-06-2006, 20:46.

        Comment

        • stever
          Member
          • Jun 2006
          • 36

          #5
          Having the same issues myself. Running zabbix on RHEL4, on AMD opterons, monitoring mostly solaris/sparc hosts.

          Just checked the value returned by the server (telnet (server) 10050 "net.if.in[hme0]"), and it actually gives me a sane value (or should I say, sane delta).

          That leads me to believe the problems are on the server side - could this be a 64 bit compile issue on my server? What flags should I add when I configure/compile?

          (I tried the delete history trick, and no dice)

          Comment

          Working...