or

On Tue, Mar 30, 2010 at 10:33 PM, Charles Regan <charles.re...@gmail.com>wrote:

> or use a simple ntp server to correct it.
>
>
> On Tue, Mar 30, 2010 at 10:31 PM, Charles Regan 
> <charles.re...@gmail.com>wrote:
>
>> or use an updated kernel... this is only needed for centos 5.2.
>> 5.3 is fine
>>
>>
>> On Tue, Mar 30, 2010 at 10:28 PM, Charles Regan 
>> <charles.re...@gmail.com>wrote:
>>
>>> you need the VM kernel if you want the time to be correct.
>>> I am running fine on a ESX server with around 650 devices.
>>> if you are using centos check this out
>>> http://pbxinaflash.com/vm/
>>>
>>>
>>>
>>>
>>> On Tue, Mar 30, 2010 at 10:14 PM, Glenn Kelley <gl...@hostmedic.com>wrote:
>>>
>>>> yup
>>>>
>>>> depending on the vm - (vm ware for example does have some clocking
>>>> issues)
>>>>
>>>> times could be a nightmare ...
>>>>
>>>> I suggest stand alone for sure
>>>>
>>>>
>>>> On Mar 30, 2010, at 7:55 PM, Richey wrote:
>>>>
>>>> > I had CactiEZ running in a VM Ware on a Dell 1850 with 4GB of ram.
>>>> > It did
>>>> > fine with about 200 devices but the time would drift really bad.
>>>> > In 10
>>>> > minutes the time would be off by hours.    I am now running it on
>>>> > the same
>>>> > 1850 but not in a VM with a few hundred graphs now.
>>>> >
>>>> > Richey
>>>> >
>>>> > -----Original Message-----
>>>> > From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org]
>>>> > On
>>>> > Behalf Of Nick Olsen
>>>> > Sent: Tuesday, March 30, 2010 5:43 PM
>>>> > To: WISPA General List
>>>> > Subject: Re: [WISPA] Bandwidth Tracking Solutions
>>>> >
>>>> > Well, This would be a little more time consuming. And would need a
>>>> > hell of a
>>>> > cacti box. But you could SNMP hit each customers CPE device if it
>>>> > supports
>>>> > it. That would be quite the load for the cacti box though.
>>>> >
>>>> > I second cacti easy though.
>>>> > We have a box running CactiEZ with 68 sensors on it, and it sits
>>>> > around all
>>>> > day doing nothing in terms of hardware usage. Every time I've tried
>>>> > it in a
>>>> > VM its had bad performance issues around 20 sensors.
>>>> >
>>>> > Nick Olsen
>>>> > Network Engineer / Customer Support
>>>> > (321) 205-1100 x106
>>>> >
>>>> > ----------------------------------------
>>>> >
>>>> > From: "Steven McGehee" <stev...@qx.net>
>>>> > Sent: Tuesday, March 30, 2010 4:49 PM
>>>> > To: "WISPA General List" <wireless@wispa.org>
>>>> > Subject: Re: [WISPA] Bandwidth Tracking Solutions
>>>> >
>>>> > We're also big fans and long time users of Cacti, so I'd happily
>>>> > recommend
>>>> > it as well.
>>>> >
>>>> > On 3/30/2010 16:46, Justin Wilson wrote:
>>>> >>     Cacti would be what I would start with.  I have set it up where
>>>> > business
>>>> >> customers have their own individual logins and can see just the
>>>> >> graphs
>>>> > you
>>>> >> want them to.  It has built in graphs for 95th percentile.  There
>>>> >> is a
>>>> >> plugin called nectar which allows you to have graphs e-mailed. You
>>>> >> can
>>>> > also
>>>> >> install the flowview plugin.
>>>> >>
>>>> >>     Not sure how to get it talking to freeside though.
>>>> >>  --
>>>> >> Justin Wilson<j...@mtin.net>
>>>> >> http://www.mtin.net
>>>> >> http://www.metrospan.net
>>>> >>
>>>> >>
>>>> >>
>>>> >> From: Matt Larsen - Lists<li...@manageisp.com>
>>>> >> Reply-To: WISPA General List<wireless@wispa.org>
>>>> >> Date: Tue, 30 Mar 2010 13:24:20 -0600
>>>> >> To: Mikrotik discussions<mikro...@mail.butchevans.com>, WISPA
>>>> General
>>>> > List
>>>> >> <wireless@wispa.org>
>>>> >> Subject: [WISPA] Bandwidth Tracking Solutions
>>>> >>
>>>> >> Hello list,
>>>> >>
>>>> >> I am looking for a solution that will keep track of the monthly
>>>> >> bandwidth consumption for all of my broadband customers and am having
>>>> >> a hard time coming up with a good solution.
>>>> >>
>>>> >> Our goal is to collect the traffic flows every 15 minutes and
>>>> >> generate
>>>> >> three things:
>>>> >>
>>>> >>     1)  Internal reports showing bandwidth consumption by customers
>>>> >> and that is in a database form that we can perform queries on
>>>> >>     2)  Data that can be exported to our customer portal page that
>>>> >> will show customers how much bandwidth they have consumed since the
>>>> >> first of each month
>>>> >>     3)  A batch file showing customers over their thresholds that we
>>>> > can
>>>> >> import into our billing system (Freeside) at the end of the month so
>>>> >> we can bill overages
>>>> >>
>>>> >> Our system is setup as follows:
>>>> >>
>>>> >>     1)  StarOS access points
>>>> >>     2)  OSPF backbone back to two separate 50 meg Internet backbone
>>>> > links
>>>> >>     3)  Mikrotik core routers at each backbone location
>>>> >>     4)  StarOS routers performing NAT at each backbone location
>>>> >>     5)  Mikrotik edge routers connected to the Internet backbone
>>>> >>
>>>> >> Radius accounting is not an option, due to inaccurate IP accounting
>>>> >> information returned by the StarOS APs.   PPPoE is also not an
>>>> >> option as
>>>> >> we have 2000+ customers in place and not all of the hardware would
>>>> >> easily convert to PPPoE.
>>>> >>
>>>> >> Ideally, the data should be collectable at the Mikrotik core routers,
>>>> >> as that is the place where all of the private IP traffic is still
>>>> >> in its
>>>> >> pre-NAT status.   We have been trying to keep track of it with
>>>> >> Netflow
>>>> >> data from our Mikrotik core routers, but it does not seem to be
>>>> >> accurate and there are documented problems with the Mikrotik Netflow
>>>> >> exports.  We have confirmed that the data we have been collecting is
>>>> >> not accurate, and I have no intention on billing a customer based on
>>>> > inaccurate data.
>>>> >>
>>>> >> We have a couple of reporting engines that we have tried, with mixed
>>>> >> levels of success.   I did contact Brandon Checketts about his
>>>> >> program,
>>>> >> which was close to what we wanted, but it is out of date and he was
>>>> >> not responsive so our efforts are focused on either using something
>>>> >> open source that we can modify or just buying an appliance that
>>>> >> will do
>>>> > what
>>>> >> we need.   My preference is to go open source because we have
>>>> >> multiple
>>>> >> backbone connections and also because I have several consulting
>>>> >> customers who want to have similar setups put in place on their
>>>> >> networks.   Also, I want to make sure that this is "revenue
>>>> >> neutral" and
>>>> >> can pay for for itself in the overage billing after it is installed.
>>>> >>
>>>> >> We can install either a switch or a transparent bandwidth monitoring
>>>> >> server of some kind between the core and NAT servers to collect the
>>>> >> data
>>>> >> flows.    My lead tech and I are both Linux savvy, and would prefer
>>>> >> something that runs on Linux.
>>>> >>
>>>> >> I recall that Travis Johnson posted a description of an open source,
>>>> >> linux-based system that he uses to track bandwidth, but I cannot find
>>>> >> the email where he lays all of the elements out.   Does anyone have
>>>> >> any
>>>> >> recommendations for this situation?
>>>> >>
>>>> >> Thanks!
>>>> >>
>>>> >> Matt Larsen
>>>> >> vistabeam.com
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> >
>>>> >> ----
>>>> >> WISPA Wants You! Join today!
>>>> >> http://signup.wispa.org/
>>>> >>
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> >
>>>> >> ----
>>>> >>
>>>> >> WISPA Wireless List: wireless@wispa.org
>>>> >>
>>>> >> Subscribe/Unsubscribe:
>>>> >> http://lists.wispa.org/mailman/listinfo/wireless
>>>> >>
>>>> >> Archives: http://lists.wispa.org/pipermail/wireless/
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> >> WISPA Wants You! Join today!
>>>> >> http://signup.wispa.org/
>>>> >>
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> >>
>>>> >> WISPA Wireless List: wireless@wispa.org
>>>> >>
>>>> >> Subscribe/Unsubscribe:
>>>> >> http://lists.wispa.org/mailman/listinfo/wireless
>>>> >>
>>>> >> Archives: http://lists.wispa.org/pipermail/wireless/
>>>> >>
>>>> >
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> > WISPA Wants You! Join today!
>>>> > http://signup.wispa.org/
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> >
>>>> > WISPA Wireless List: wireless@wispa.org
>>>> >
>>>> > Subscribe/Unsubscribe:
>>>> > http://lists.wispa.org/mailman/listinfo/wireless
>>>> >
>>>> > Archives: http://lists.wispa.org/pipermail/wireless/
>>>> >
>>>> >
>>>> >
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> > WISPA Wants You! Join today!
>>>> > http://signup.wispa.org/
>>>> >
>>>> ----------------------------------------------------------------------------
>>>> > ----
>>>> >
>>>> > WISPA Wireless List: wireless@wispa.org
>>>> >
>>>> > Subscribe/Unsubscribe:
>>>> > http://lists.wispa.org/mailman/listinfo/wireless
>>>> >
>>>> > Archives: http://lists.wispa.org/pipermail/wireless/
>>>> >
>>>> >
>>>> >
>>>> >
>>>> --------------------------------------------------------------------------------
>>>> > WISPA Wants You! Join today!
>>>> > http://signup.wispa.org/
>>>> >
>>>> --------------------------------------------------------------------------------
>>>> >
>>>> > WISPA Wireless List: wireless@wispa.org
>>>> >
>>>> > Subscribe/Unsubscribe:
>>>> > http://lists.wispa.org/mailman/listinfo/wireless
>>>> >
>>>> > Archives: http://lists.wispa.org/pipermail/wireless/
>>>>
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> WISPA Wants You! Join today!
>>>> http://signup.wispa.org/
>>>>
>>>> --------------------------------------------------------------------------------
>>>>
>>>> WISPA Wireless List: wireless@wispa.org
>>>>
>>>> Subscribe/Unsubscribe:
>>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>>
>>>> Archives: http://lists.wispa.org/pipermail/wireless/
>>>>
>>>
>>>
>>
>


--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to