Assuming it was working without a problem. First step is to see try and ID something that has changed around the time the problem happened. The change may not necessairly be on the NBX but the network or a device on the network.
Regardless, memory issues fall into 2 main buckets.
1 Memory Leak
2 Reached/Exceeded capacity
For #1 It will take real expertise with the NBX and the network to understand and correct the problem. Often once the root cause has been identified it can be defensed against or fixed soemtiemw without even new software i.e. Denial of Service attack. But it may need a code fix which will have to come from 3Com anyway..
If #2 Its simply a matter of the NBX reaching the low tide mark because the its utilization over time has increased to the point that it can't recover memory fast enough to keep up with the demand. Adding Memory is all thats needed. Assuming like most users capacity will continue to increase over time. The benefit of adding memory outways the cost in other ways anyway.
To tackle issue #1 you should bring in expertise from 3Com assuming you have a contract of some kind. They can look under the hood with more detail and precision to see what going on.
Issue #2 is more a judgement call with at least the benefit of self preservation by not getting yelled at so often. It will last longer and delay how frequently you need to perform corrective action i.e. Reboot of NBX