Skip to main content
NetApp Knowledge Base

CAIQUM-5933: AIQUM server unresponsive due to vulnerability scanners

  1. Last updated
  2. Save as PDF
Views:
2,663
Visibility:
Public
Votes:
2
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Issue

  • Active IQ Unified Manager (AIQUM) becoming unresponsive after vulnerability scans
  • On Windows, OpenJDK Platform Binary process exhibits high CPU usage
  • On VMware virtual appliance and Linux, journalctl.log has multiple entries of Rate limit exceeded from one or more sources:

ocum kernel: Rate limit exceeded: IN=eth0 OUT= MAC=<YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY> SRC=XX.XX.XX.XX DST=<AIQUM_IP> LEN=52 TOS=0x02 PREC=0x00 TTL=126 ID=9520 DF PROTO=TCP SPT=52199 DPT=443 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0
ocum kernel: Rate limit exceeded: IN=eth0 OUT= MAC=<YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY:YY> SRC=XX.XX.XX.XX DST=<AIQUM_IP> LEN=52 TOS=0x02 PREC=0x00 TTL=126 ID=9591 DF PROTO=TCP SPT=52206 DPT=443 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0
  • Acquisition towards clusters might fail over time and stability issues from Jboss (web engine) are seen
    Note: Even in environments where vulnerability scanners are not used, similar access patterns can cause this issue.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.