Network Management

Reply
Moderator

Re: AWave newbie: console showing out of memory errors

I think Pavan is referring to if you're using a dedicated VM for AirWave or if the VM has other instances running.  The issue will be disk I/O contention.  AirWave being a monitoring system is heavy on read/writes.  Having the incorrect allocation of memory affects the performance directly.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Contributor I

Re: AWave newbie: console showing out of memory errors

Hi Rob,

 

I'm not sure I follow:  I have an ESXi 4.1 host running 5 VMs.  4 of the VMs are various MS Windows servers.  The 5th VM is dedicated to AirWave (8.2.5 I think), which I installed using an ISO I had downloaded from Aruba.  How could this one VM be running multiple instances?  I guess I don't know VMware as well as I thought :)

 

Initially my AW usage will be very minimal, with probably no more than 10 to 15 devices as I test AW in my office.  I have a single Aruba AP 303H, which has maybe 5 to 10 wifi clients.  Then there's a few Cisco and Netgear switches, but not much else.  Are there any guidelines as to how much memory an AW VM needs for extremely small environments?  I assume the more devices one monitors with AW, the more traffic and data to be stored.  So I would assume 80GB HDD is really not needed for small installs?  And the 8GB memory?

 

VMware does support "reserving" memory - which I have never needed to do.  Is Pavin suggesting editing my AW VM's properties and making a memory "reservation"?  I imagine that reserving memory might reserve a chunk of physical non-shared memory for the VM - resulting in faster access since no paging to disk needs to be done for the reserved memory?  This is all just a big guess, as I have very little experience in tuning VMware...

 

Thanks,

Mike

Moderator

Re: AWave newbie: console showing out of memory errors

When I say multiple instances, I'm referring to the VM Host.  So your host has 5 instances.

 

You can probably last off of 40-50 GB of disk, the OS itself takes about 10GB.  My test setups that live for about 2 weeks at a time take up about 25GB each.  So if you use less disk, then you might consider lowering the amount of data maintained on the AMP from AMP Setup -> General -> Historical Data Retention.

 

8GB RAM should be the minimum.  Otherwise you'll see services flapping during the initial start up.

 

As far as VM reservation, the 8GB allocated to the instance should be enough.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Contributor I

Re: AWave newbie: console showing out of memory errors

Oh, so some people go to the trouble of installing VMware and only install one VM - for AirWave?  Seems like overkill, and sort of a waste of a machine, *if* you have a powerful server...

 

I don't get the out of error messages during startup.  It happens many hours later (maybe even a day or two).  Do the error messages I posted earlier help you identify the problem?

 

Thanks,

Mike

Moderator

Re: AWave newbie: console showing out of memory errors

No, it's more like a customer puts AirWave on a VM Host that is already heavily loaded with other equally or more important infrastructure.  It's still just 1 instance of AirWave, but if it's on a server that also hosts another database instance, then the 2 instances require a lot of IOPs.  When it reaches disk contention, 1 instance gets a higher priority to use the disk than the other, in which case you'll see performance trade off.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: