Skip to main content
NetApp Knowledge Base

How to resolve memory issues with Active IQ Unified Manager

Views:
911
Visibility:
Public
Votes:
1
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • OnCommand Unified Manager 7.x ( UM )
  • OnCommand Unified Manager 9.4 ( UM )
  • OnCommand Unified Manager 9.5 ( UM )
  • Active IQ Unified Manager 9.6+ ( AQIUM )
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019
  • Red Hat 6.x
  • Red Hat 7.x
  • CentOS 7.x
  • VMware Virtual Machine OVA

Description

This article will cover some of the most common issues and questions regarding Active IQ Unified Manager and memory. Below are some of the observable issues that indicate that one is experiencing a memory issue.

  • Unified Manager application is running slow:
    • Services take a long time to come online.
    • WebGUI is slow.
    • Backups take a very long time ( and possibly fail ).
  • Unified Manager application CPU and/or memory utilization are extremely high; swap / page file is in use.
  • Unified Manager application experiences inconsistent behavior:
    • Services hanging.
    • Services restarting.
    • Occasional issues with alert notifications.
    • Inventory / performance acquisition polls may not complete within their normal 15 minute / 5 minute cycles.
    • Other abnormal (unexplainable) inconsistent behavior when running in a virtual environment.
  • VMware ESXi displays one or more of the following:
    • Memory Ballooning
    • Swapping
    • Transparent Page Sharing
    • Compression
  • Scale Monitoring Messages
    • "Unified Manager Server Low On Memory"
      • Memory_low_on_ocum.PNG
  • Log indications:
    • MySQL "error.log" file:
      • 2020-04-12T04:02:10.036849Z 205 [Note] Aborted connection XXX to db: 'unconnected' user: 'jboss' host: 'localhost' (Failed on my_net_write())
      • 2020-04-12T08:50:42.808598Z 450 [Note] Got timeout reading communication packets
    • Unified Manager "server_mega.log" file:
      • 2020-04-12 06:11:01,221 ERROR [default task-4] c.n.s.s.a.OriginatorUpdateServlet (OriginatorUpdateServlet.java:82) - Transaction rolled back: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back
    • Unified Manager "ocumserver.log" file: 
      • 2019-06-06 02:49:49,566 INFO [oncommand] [pool-22-thread-4] [c.n.d.e.p.e.b.UnifiedManagerMemoryEventTypeController] Scale Monitor: New Memory Event Created: event id=128123,eventSeverity=low, thresholdValue=5.0, currentUsageValue=6.690000057220459, totalMemorySizeValue=1.365997568E10, jvm=AuJvm
      • 2019-06-06 01:49:49,190 INFO [oncommand] [pool-22-thread-55] [c.n.d.e.p.e.b.UnifiedManagerMemoryEventTypeController] Scale Monitor: New Memory Event Created: event id=128094,eventSeverity=almostOut, thresholdValue=7.0, currentUsageValue=7.195000171661377, totalMemorySizeValue=1.365997568E10, jvm=AuJvm

NOTE: This is not an exhaustive list of logs indicating memory issues. Please be aware that NetApp Support will find other log lines that can also indicate memory issues.

Most memory issues can be broken down into two categories. Additionally these two categories can also be formulated into the two most common questions.

Most Common Memory Issues:
1. Not having enough memory allocated.
2. Not having memory reserved.

Most Common Memory Questions:
1. How much memory does Active IQ Unified Manager need?
2. Does memory need to be reserved for Active IQ Unified Manager?

There are occasionally issues that arise that don't fall into these two categories; but the lions share of memory inquiries involve both the correct amount of memory allocated and memory reserved. We have found that customers running Active IQ Unified Manager ( AIQUM ) on dedicated hardware versus a virtual environment have less memory issues. This is due to both these two elements essentially being eliminated. All the memory available on the dedicated physical hardware is not only allocated to the AIQUM server, but is also not being shared amongst other servers. While it is not required that AIQUM be deployed on physical hardware, this shared observation by NetApp Support is given as an example of the importance of allocating and reserving memory. Typically we don't see memory issues with AIQUM installed in a virtual environment that has both the correct amount of memory allocated and reserved.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

******************************************************* *******************************************************