[bug-notifications] [orca_web 0004546]: network interface with greater than 1 Gbit of bandwidth does plot correctly

Mantis Bug Tracker noreply at opencsw.org
Mon Nov 21 17:14:31 CET 2011

A NOTE has been added to this issue. 
Reported By:                GlenG
Assigned To:                dam
Project:                    orca_web
Issue ID:                   4546
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Date Submitted:             2010-09-08 16:59 CEST
Last Modified:              2011-11-21 17:14 CET
Summary:                    network interface with greater than 1 Gbit of
bandwidth does plot correctly
(This is a copy of my post to 'orca-users at orcaware.com')

I'm trying to add a plot for a network interface with greater than 1 Gbit
of bandwidth.  I'm getting a plot but the y axis tops out at 1000Mb/s and
when the interface is receiving > 1000Mb/s that variable is not plotted
(the text portion Max. does not report the larger values either). Here's my
plot configuration.  I copied a working 1Gbit plot and changed data_max
from 1000000000 to 2000000000.  Also, tried deleting data_max.
# Interface bits per second for > 1 Gbit interfaces.
plot {
title                   %g Interface Bits Per Second: $1
source                  orcallator
data                    1024 * 8 * ((?:(?:aggr))\d+)InKB/s
data                    1024 * 8 * $1OuKB/s
line_type               area
line_type               line1
legend                  Input
legend                  Output
y_legend                Bits/s
data_min                0
data_max                2000000000
plot_width              800


 (0009429) dam (administrator) - 2011-11-21 17:14
I happen to just have a machine with nxge in the lab which allows me to fix
other issues while I am at it.
How high should aggr be? If you bundle up 4 gigabit interfaces it should be
even higher. 10 GBE? Or 20 GBE for trunking 10 GBE interfaces?

Regarding the crash: I can't promise when I will have a reasonable amount
of time to look into this. Nonetheless I am working on fixing all
SE/orcallator issues in one go now (apart from the leak). IIRC the was
splitting off orcallator to limit deps on server machines and new nxge
interfaces. Any other issues you have for a new release?

Best regards

  -- Dago

More information about the bug-notifications mailing list