Dell SC Compelent - not showing all storage

nuronex

Hi.

I've version: 1.8.14

And I monitoring over 50 storage. But I've prbolem with Dell SC Series (Compellent) storage.

All SC storage has access (it's the same IP address), all are configured and on "test" button all looks ok:

But. On "Application/Job" view some of them has "falied" status:

and not all SC storage show metric data, i.e. "capacity":

Please help - i don't know where looking for som detailed logs and reason.

Lukas

Hello,

Send us logs.

UI --> settings --> Logs --> support logs: follow the form

Send us generated file via https://upload.xormon.com

Note a reference pls.

Thank you

nuronex

Lukas

May 13, 2025

Hello,

Send us logs.

UI --> settings --> Logs --> support logs: follow the form

Send us generated file via https://upload.xormon.com

Note a reference pls.

Thank you

I uploaded logs

nuronex

Thank you for patch - after install whole SC storage working fine.

nuronex

@Lukas one more problem.

After patch installed we have new problem.

We have dwo storage Compellent witch "live volume" so on two matrix we have volumes with the same "Volume ID" bud diferent storage name ane diferent volumen name.

On old version xorux was:

on new version is:

Pavel

how 2 different volumes on different storage devices can share same volume ID?

We expect that volume ID is ALWAYS unique.

nuronex

I don't want to comment on behalf of the storage vendor :)

We have a paired array running in HA with "live volume" features in DELL. It works exactly as I said. We create volumes on one array, then select "live volume", select another array and after clicking "create" we see on the second array, as I pasted above:

We have two different volume names on different arrays, but the same volume ID.

To sum up, the previous version displayed such a case correctly.

Pavel

we use volume ID as a unique key for storing in the database.

When 2 items have same unique key then just one is saved, that is why you cannot see both volumes.

No easy solution here, it would have to be re-designed all volumes data storing, through away all volumes data and create some other unique key based on volume id and storage serial for example ... nice one :(