Topology Split Manager is running out of memory during the discovery process
search cancel

Topology Split Manager is running out of memory during the discovery process

book

Article ID: 327676

calendar_today

Updated On:

Products

VMware Smart Assurance VMware Telco Cloud Service Assurance

Issue/Introduction

Symptoms:

 

  • Topology Split Manager (TSM) is running out of memory during the discovery process.
  •  TSM domain hits the 32-bit memory limit before discovery is completed using a seedfile.

Environment

Smarts-10.1.x

Smarts DM-2.4

TCSA-2.x

Cause

The TSM seedfile is probably too large. If the TSM domain hits the 32-bit memory limit before discovery is completed, this is a good indication that the seedfile is too large.

Resolution

To resolve this issue, do the following:

  1. Split the seedfile into smaller parts.
  2. Discover each of the smaller seedfiles one at a time into the single TSM domain until all devices are discovered. 
  3. If one seed file is still causing a memory crash, split the seed file further.
  4. If the preceding attempts to discover the entire topology still fail, provide the following with your case request  for further troubleshooting:

    • Core file for the crash
    • TSM domain logs
    • TSM domain rps
    • SM_Monitor logs captured while the problem is being reproduced