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

Mantis Bug Tracker noreply at opencsw.org
Tue Nov 22 21:03:59 CET 2011


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4546 
====================================================================== 
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-22 21:03 CET
====================================================================== 
Summary:                    network interface with greater than 1 Gbit of
bandwidth does plot correctly
Description: 
(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
href                   
http://www.orcaware.com/orca/docs/orcallator.html#interface_bits_per_second
}

====================================================================== 

---------------------------------------------------------------------- 
 (0009431) GlenG (reporter) - 2011-11-22 21:03
 https://www.opencsw.org/mantis/view.php?id=4546#c9431 
---------------------------------------------------------------------- 
(sorry of the delay in replying - major application software upgrades over
the weekend)

>>How high should aggr be?
As the number of NICs in a aggr can change dynamically, I think the best
choice is to let the max float.

The things that I have run into:
1.  the single threaded-ness of the master means my graphs tend to update
less frequently than I like
2.  memory leak leading to abend/dump (at this point /var is a little too
small and it fills up - until a cron task moves the dump elsewhere) - Note:
The suggestion from the orcalist is that this is a pearl-solaris 10
problem)
3.  dynamic change in the number of CPUs causes collection to fail (T5220
with LDoms)
4.  restarting csworca causes maintenance state, although clearing allows
startup.  The console from today follows:

ex=0 11:30:27 fozzie ~ gunselmg $sudo /usr/sbin/svcadm -v restart
svc:/network/csworca:default
Action restart set for svc:/network/csworca:default.
ex=1 11:30:50 fozzie ~ gunselmg $sudo svcs -l svc:/network/csworca
fmri         svc:/network/csworca:default
enabled      true
state        online
next_state   offline
state_time   Tue Nov 22 11:30:30 2011
logfile      /var/svc/log/network-csworca:default.log
restarter    svc:/system/svc/restarter:default
contract_id  908171
dependency   require_all/none svc:/system/filesystem/local (online)
dependency   require_all/none svc:/network/loopback (online)
ex=0 11:31:04 fozzie ~ gunselmg $sudo svcs -l svc:/network/csworca
fmri         svc:/network/csworca:default
enabled      true
state        maintenance
next_state   none
state_time   Tue Nov 22 11:31:31 2011
logfile      /var/svc/log/network-csworca:default.log
restarter    svc:/system/svc/restarter:default
contract_id  908171
dependency   require_all/none svc:/system/filesystem/local (online)
dependency   require_all/none svc:/network/loopback (online)
ex=1 11:32:06 fozzie ~ gunselmg $sudo vi
/var/svc/log/network-csworca:default.log
"/var/svc/log/network-csworca:default.log" 749 lines, 56006 characters
...
Version string '1.05 ' contains invalid data; ignoring: ' ' at
/opt/csw/bin/orca line 66.
[ Nov 22 11:30:30 Stopping because service restarting. ]
[ Nov 22 11:30:30 Executing stop method
("/var/opt/csw/svc/method/svc-csworca stop") ]
/var/opt/csw/svc/method/svc-csworca: kill: no such process
[ Nov 22 11:30:30 Method "stop" exited with status 0 ]
[ Nov 22 11:31:30 Method or service exit timed out.  Killing contract
908171 ]
[ Nov 22 11:31:31 Method or service exit timed out.  Killing contract
908171 ]
:q
ex=2 11:32:22 fozzie ~ gunselmg $sudo /usr/sbin/svcadm -v clear
svc:/network/csworca:default
Action maint_off set for svc:/network/csworca:default.
ex=0 11:32:29 fozzie ~ gunselmg $sudo svcs -l svc:/network/csworca
fmri         svc:/network/csworca:default
enabled      true
state        online
next_state   none
state_time   Tue Nov 22 11:32:29 2011
logfile      /var/svc/log/network-csworca:default.log
restarter    svc:/system/svc/restarter:default
contract_id  955499
dependency   require_all/none svc:/system/filesystem/local (online)
dependency   require_all/none svc:/network/loopback (online)
ex=0 11:32:36 fozzie ~ gunselmg $



More information about the bug-notifications mailing list