Wrong bandwidth values on high bitrates

joostsjoosts
edited December 2012 in Monitoring Software v12 and lower
Hi,



When bitrate values exceed 200Mbps (approx) we see a 0 value. This happens on all our Windows servers that are monitored. Bandwidth is fetched via SNMP.



See also the following graph that misses the peak bandwidths:

http://www.maxx-xs.nl/temp/1309281734BANDWIDTH-bandwidth_day.gif



Is this is bug in the software?



Reg., Joost




Comments

  • AdministratorAdministrator
    Your graph does show values up to 246 Mbps being recorded so not sure how they can be 0 as you state
  • joostsjoosts
    Hi, perhaps I was not clear enough and should have said above 240Mbps. I assume you see the dropped peak in the graph? This happens on all servers on those busy hours...



    CPU load is minimal on the hosts, so that cannot be an issue.



    Reg., Joost
  • AdministratorAdministrator
    Many users monitor Gbps networks so 240 Mbps shouldn't be a problem - nor is there a reason why it would be limited to 240.



    In order to verify you can always run in debug mode at that most busy time frame and check the debug logs
  • joostsjoosts
    Hi,



    See the following example of a switch poort. The bandwidth calculation results in 0!



    On Start:

    # S-X Thu Mar 21 10:10:58 2013 0000000135BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.35 :1004155464



    2nd cycle

    # S-X Thu Mar 21 10:14:52 2013 0000000135BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.35 :596957957

    # S-X Thu Mar 21 10:14:57 2013 0000000135BANDWIDTH - Substraction: 596957957-1004155464=-407197507

    # S-X Thu Mar 21 10:14:57 2013 0000000135BANDWIDTH - Time difference (sec): 239

    # S-X Thu Mar 21 10:14:57 2013 0000000135BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (1258)

    # S-X Thu Mar 21 10:14:57 2013 0000000135BANDWIDTH - Setting prev value to:596957957

    # S-X Thu Mar 21 10:14:57 2013 0000000135BANDWIDTH - outbound traffic: 596957957



    3rd cycle

    # S-X Thu Mar 21 10:18:38 2013 0000000135BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.35 :3956720543

    # S-X Thu Mar 21 10:18:43 2013 0000000135BANDWIDTH - Substraction: 3956720543-596957957=3359762586

    # S-X Thu Mar 21 10:18:43 2013 0000000135BANDWIDTH - Time difference (sec): 226

    # S-X Thu Mar 21 10:18:43 2013 0000000135BANDWIDTH - Calculation for OID (traffic=bytes/sec): 14866206 (14866206)

    # S-X Thu Mar 21 10:18:43 2013 0000000135BANDWIDTH - Setting prev value to:3956720543

    # S-X Thu Mar 21 10:18:43 2013 0000000135BANDWIDTH - outbound traffic: 3956720543



    4th cycle

    # S-X Thu Mar 21 10:22:06 2013 0000000135BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.35 :2044876175

    # S-X Thu Mar 21 10:22:11 2013 0000000135BANDWIDTH - Substraction: 2044876175-3956720543=-1911844368

    # S-X Thu Mar 21 10:22:11 2013 0000000135BANDWIDTH - Time difference (sec): 208

    # S-X Thu Mar 21 10:22:11 2013 0000000135BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (1279)

    # S-X Thu Mar 21 10:22:11 2013 0000000135BANDWIDTH - Setting prev value to:2044876175

    # S-X Thu Mar 21 10:22:11 2013 0000000135BANDWIDTH - outbound traffic: 2044876175




  • AdministratorAdministrator
    Please update to our latest version: 10.1.1
  • joostsjoosts
    We have updated to this version last friday but the bandwidth issue is not solved. See the values of a server that should have values over 450Mbps:



    1330009156BANDWIDTH - requesting outbound



    1st:



    # S-X Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :1549689105

    # S-X Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - snmp log created with 1549689105 and 1364069612

    # S-X Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - outbound traffic: 1549689105

    # S-7 Sat Mar 23 21:13:32 2013 Bandwidth step 5

    # S-7 Sat Mar 23 21:13:32 2013 bandwidth: 0 <- 0

    # S-X Sat Mar 23 21:13:32 2013 graph day time (0)for 1330009156BANDWIDTH reset to current

    # S-X Sat Mar 23 21:13:32 2013 graph week time for 1330009156BANDWIDTH reset to current

    # S-X Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH Day Graphs Debug - Refresh rate: 300 - Drawgraphs:1 - 1:Last at 1364069612 (1364069612)

    # S-X Sat Mar 23 21:13:32 2013 skipping Availability graphs - only value graphs plotted (true - 1 - 1)

    # S-X Sat Mar 23 21:13:32 2013 skipping SLA graphs - only value graphs plotted (true - 1 - 1)

    # S-X Sat Mar 23 21:13:32 2013 update C:serverscheck_databases1330009156BANDWIDTH-value.rrd 1364069612:0

    # S-X Sat Mar 23 21:13:32 2013 update C:serverscheck_databases1330009156BANDWIDTH-bandwidth.rrd 1364069612:3751261768:1549689105

    # S-7 Sat Mar 23 21:13:32 2013 save 1330009156BANDWIDTH<!!>1364069612<!!>171020<!!>0<!!>1364069612<!!>

    # S-7 Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - s:OK - e: - v:||1000000000 - t:1364069612

    # S-7 Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - finished in 0 sec

    # S-7 Sat Mar 23 21:13:32 2013 1330009156BANDWIDTH - didn't time out



    2nd:

    # S-X Sat Mar 23 21:15:37 2013 1330009156BANDWIDTH - requesting outbound traffic for: .1.3.6.1.2.1.2.2.1.16.11

    # S-X Sat Mar 23 21:15:37 2013 1330009156BANDWIDTH - Creating SNMP connection to 192.168.4.26 using 1

    # S-X Sat Mar 23 21:15:37 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :342951346

    # S-X Sat Mar 23 21:15:37 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - Substraction: 342951346-1549689105=-1206737759

    # S-X Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - Time difference (sec): 130

    # S-X Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (578257)

    # S-X Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - Setting prev value to:342951346

    # S-X Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - outbound traffic: 342951346

    # S-7 Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - s:OK - e: - v:578257|0|1000000000 - t:130

    # S-7 Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - finished in 10 sec

    # S-7 Sat Mar 23 21:15:42 2013 1330009156BANDWIDTH - didn't time out



    3rd:

    # S-X Sat Mar 23 21:17:48 2013 1330009156BANDWIDTH - requesting outbound traffic for: .1.3.6.1.2.1.2.2.1.16.11

    # S-X Sat Mar 23 21:17:48 2013 1330009156BANDWIDTH - Creating SNMP connection to 192.168.4.26 using 1

    # S-X Sat Mar 23 21:17:48 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :3878511466

    # S-X Sat Mar 23 21:17:48 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - Substraction: 3878511466-342951346=3535560120

    # S-X Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - Time difference (sec): 131

    # S-X Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - Calculation for OID (traffic=bytes/sec): 26989008 (26989008)

    # S-X Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - Setting prev value to:3878511466

    # S-X Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - outbound traffic: 3878511466

    # S-7 Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - s:OK - e: - v:554480|26989008|1000000000 - t:131

    # S-7 Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - finished in 10 sec

    # S-7 Sat Mar 23 21:17:53 2013 1330009156BANDWIDTH - didn't time out



    4th:

    # S-X Sat Mar 23 21:19:58 2013 1330009156BANDWIDTH - requesting outbound traffic for: .1.3.6.1.2.1.2.2.1.16.11

    # S-X Sat Mar 23 21:19:58 2013 1330009156BANDWIDTH - Creating SNMP connection to 192.168.4.26 using 1

    # S-X Sat Mar 23 21:19:58 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :3425684462

    # S-X Sat Mar 23 21:19:58 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - Substraction: 3425684462-3878511466=-452827004

    # S-X Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - Time difference (sec): 130

    # S-X Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (539265)

    # S-X Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - Setting prev value to:3425684462

    # S-7 Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - s:OK - e: - v:539265|0|1000000000 - t:130

    # S-7 Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - finished in 10 sec

    # S-7 Sat Mar 23 21:20:03 2013 1330009156BANDWIDTH - didn't time out



    5th:

    # S-X Sat Mar 23 21:22:09 2013 1330009156BANDWIDTH - requesting outbound traffic for: .1.3.6.1.2.1.2.2.1.16.11

    # S-X Sat Mar 23 21:22:09 2013 1330009156BANDWIDTH - Creating SNMP connection to 192.168.4.26 using 1

    # S-X Sat Mar 23 21:22:09 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :2340333604

    # S-X Sat Mar 23 21:22:09 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - Substraction: 2340333604-3425684462=-1085350858

    # S-X Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - Time difference (sec): 131

    # S-X Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (588372)

    # S-X Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - Setting prev value to:2340333604

    # S-X Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - outbound traffic: 2340333604

    # S-7 Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - s:OK - e: - v:588372|0|1000000000 - t:131

    # S-7 Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - finished in 10 sec

    # S-7 Sat Mar 23 21:22:14 2013 1330009156BANDWIDTH - didn't time out



    6th:

    # S-X Sat Mar 23 21:24:19 2013 1330009156BANDWIDTH - requesting outbound traffic for: .1.3.6.1.2.1.2.2.1.16.11

    # S-X Sat Mar 23 21:24:19 2013 1330009156BANDWIDTH - Creating SNMP connection to 192.168.4.26 using 1

    # S-X Sat Mar 23 21:24:19 2013 1330009156BANDWIDTH - oid value for .1.3.6.1.2.1.2.2.1.16.11 :1620084504

    # S-X Sat Mar 23 21:24:19 2013 1330009156BANDWIDTH - interface speed value for .1.3.6.1.2.1.2.2.1.5.11 :1000000000

    # S-X Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - Substraction: 1620084504-2340333604=-720249100

    # S-X Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - Time difference (sec): 130

    # S-X Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - Calculation for OID (traffic=bytes/sec): 0 (587223)

    # S-X Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - Setting prev value to:1620084504

    # S-X Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - outbound traffic: 1620084504

    # S-7 Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - s:OK - e: - v:587223|0|1000000000 - t:130

    # S-7 Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - finished in 10 sec

    # S-7 Sat Mar 23 21:24:24 2013 1330009156BANDWIDTH - didn't time out




  • AdministratorAdministrator
    We are looking into this and will update you
  • AdministratorAdministrator
    It seems to be related to a limit in 32bit counters wrapping.



    We are working on it



    Can you check with a MIB Browser if you have an OID for that interface that is a 64Bit Counter (Counter64)
  • joostsjoosts
    The MIB browser of ServersCheck does not show the type value. Tried another one and as far as I can see the counters are 32Bit.


  • AdministratorAdministrator
    For high traffic you will need 64bit counters as this is a limit to your hardware and it cycles the values
  • joostsjoosts
    The OS is W2008 64 bit. You are saying the the SNMP values served by the OS are 32bit? If so, how can we make sure that those values are 64 bit?
  • AdministratorAdministrator
    A quick Google search learns that Windows 2008 doesn't have 64bit counters...
This discussion has been closed.