Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 4634 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ACC 3.0 VMWare requirements

alex.hartmaier
I couldn't find the VMWare requirements for 3.0. Have they been defined already?


This thread was automatically locked due to age.
  • 0
    I manage 3 asg's with acc is it hardly touches 512 megs of real ram usage and isn't hardly touching 1 ghz of real cpu usage even on bursting..[:)]

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • 0
    Ok, so I managed to get it all working, and William, yes, it runs at about 60% RAM (out of 640MB) and I don't think I've seen it hit more than 5% of the CPU (normally it runs between 0-1%).

    I'm still not sure how all the routing works: I have an elastic IP which somehow translates to some other public IP which then translates to a private IP, but seeing as how this is just a monitoring station I'm not too worried about it.

    Anyway, other than an issue I brought up in this thread (Local ASG WebAdmin through ACC) this has been a really great solution to monitor my ASGs.  The cost is decent: ~$100/year (over 4 years).  Another Amazon win as far as I'm concerned.

    Now to figure out how to deploy rules and configurations.  

    -Bob
Unfiltered HTML