Applications Systems

AppStack Environment for IBM FlashSystem Storage Array shows LUNs but no VMware Hosts, Datastores, or Virtual Center relationships in Storage Resource Monitor

This article discusses an issue where IBM FlashSystem LUNs appear in AppStack but VMware relationships such as Virtual Centers, Hosts, Datastores, and VMs are missing because the SRM topology job fails while processing hosts with multiple initiator ports.

First published date

6/22/2026 4:20 PM

Last published date

6/23/2026 5:39 PM

Overview

This article discusses an issue where IBM FlashSystem LUNs appear in AppStack but VMware relationships such as Virtual Centers, Hosts, Datastores, and VMs.

In AppStack for the storage array, LUNs are visible but the VMware layers are empty.

No related Virtual Centers, Virtual Datacenters, Clusters, Hosts, Datastores, or VMs are shown for the affected storage array.

From SRM.Pollers.StorageArrayJob_XX_Topology: 

2026-06-10 14:42:45,799 [STP SmartThreadPool Thread #8] ERROR SolarWinds.SRM.Pollers.Pollers.IbmFlashSystem.Jobs.IbmFlashSystemStorageArrayApiJob - System.InvalidOperationException: Sequence contains more than one matching element

  at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)

  at SolarWinds.SRM.Pollers.Pollers.IbmFlashSystem.Jobs.IbmFlashSystemTopologyJobPoller.GetInitiatorEndpoints(String hostName, IEnumerable`1 hostPorts)

  at SolarWinds.SRM.Pollers.Pollers.IbmFlashSystem.Jobs.IbmFlashSystemTopologyJobPoller.Execute(IIbmFlashSystemApiClient client)

  at SolarWinds.SRM.Pollers.Pollers.IbmFlashSystem.Jobs.IbmFlashSystemStorageArrayApiJob.Execute(SRMStorageArrayJobDescription jobDescription)

SRM collects the array and LUN objects, but end-to-end mapping is not built because no SRM_LunMasking rows are written for the affected array.

 

Product section

Storage Resource Monitor

Cause

The issue occurs because SRM assumes there will be only one entry for each host, but the API returns one entry for each port. If a host has two or more ports, the SRM poller will fail with an error and stops the job before it finishes mapping.

Resolution

A fix for this issue is planned for a future release of the Storage Resource Monitor.