Storage KMs Run Out-Of-Memory and Stop Collecting Data

Introduction

The collectionHubHeapSizeMax variable corresponds to the Maximum heap size in megabytes allocated to the Java Collection Hub. Its default value, which is appropriate for most environments, may be inadequate in large environments consisting of many Symmetrix storage systems for example. The Storage KMs will then run out-of-memory and stop collecting data.

Increasing the value of the collectionHubHeapSizeMax configuration variable to 2048 or 4096 will solve the issue.

Procedure

In a PATROL Environment

To increase the value of the collectionHubHeapSizeMax configuration variable:

1. Run wpconfig.exe
2. Click to get the configuration of your PATROL agent.
3. Double-click the /SENTRY/<PRODUCT_CODE> directory to display the list of variables. The directory is:

• /SENTRY/SEN_CMPL for Dell Compellent KM for PATROL
• /SENTRY/SEN_UNITY for Dell EMC Unity KM for PATROL
• /SENTRY/SEN_EMC for EMC Disk Arrays KM for PATROL
• /SENTRY/SEN_XTRM for EMC XtremIO KM for PATROL
• /SENTRY/HARDWARE for Hardware KM for PATROL
• /SENTRY/SEN_HDS for Hitachi Disk Arrays KM for PATROL
• /SENTRY/SEN_HP3P for HP 3PAR KM for PATROL
• /SENTRY/SEN_I68 for IBM DS6000, DS8000 Series KM for PATROL
• /SENTRY/SEN_SVCSTORWIZE for IBM SVC KM for PATROL
• /SENTRY/SEN_XIV for IBM XIV KM for PATROL
• /SENTRY/STUDIO for Monitoring Studio v9
• /SENTRY/X for Monitoring Studio X
• /SENTRY/SEN_NAP for NetApp Filers KM for PATROL
• /SENTRY/SEN_PURE for Pure Storage KM for PATROL
• /SENTRY/STORAGE/ for Storage Analyzer KM for PATROL

4. Create the collectionHubHeapSizeMax variable, set its value to 2048 or 4096 and click OK.
5. Click to save your changes.
6. Restart the PATROL Agent.

In a TrueSight Environment

To increase the value of the collectionHubHeapSizeMax configuration variable:

1. Edit your storage monitoring policy:

   

   • Log on to the TrueSight console.
   • In the navigation pane, expand Configuration and select Infrastructure Policies.
   • In the Infrastructure Policies page, locate the monitoring policy you wish to modify, click its action button and click Edit.

2. Click the action button next to the monitoring configuration you wish to modify and click Edit.

   

3. Scroll down to the Advanced Configuration Variables section

4. Click Add to open the Configuration Variables panel. In the Name field, enter collectionHubHeapSizeMax; in the Value field enter 2048 or 4096.

   

5. Click OK twice.

6. Click Save.

Related Topics

• KMs Report "Collection Hub is not started. Cannot send the query"
• Monitoring Studio X Unexpectedly Hangs or Consumes High CPU When Running a JRE Higher Than 8
• Troubleshooting WMI-Based Connectors
• SSH-Based Connectors Stopped Working
• WBEM-Based Connectors Stopped Working