Unimus forum

Hello,

Would you mind submitting a support ticket in our Portal? I will then get back to you with what we would need from you (debug logs) to look at it closer.

I have just wanted to update this thread with what we found out during a remote session looking at one of these storage devices. Unfortunately, it turned out that we were not able to get enough information without root access. As it turned out, this, being safeguarded platform by HPE themselves, is ...

A good feature to have. We have an internal ticket for a feature like this already. No ETA at this moment.
I am adding this thread to it, so as soon as it gets out, I will update the thread.

Apologies for the late reply. We will be adding support for TNSR in one of the upcoming releases. I am noting this thread to our internal ticket, so when it we do so, I will update this thread as well.

This is a good suggestion and it will be a great addition to the advanced filtering we are working on for the Devices view, which will put the search bar on steroids to give users in-depth filtering options, this one also included.

Apologies for the late reply. I assume you meant Unimus, not Portal. This feature is actually something we are planning to implement and we already have an internal ticket for this feature. I am adding this thread to it, so when we get the feature out in a future Unimus release, I will update this t...

Hello, These are some good points and suggestions. Let me address them one by one: 1. Device count for selected devices - this will be one of the aspects we aim to improve in our planned rework of Devices view to improve multi-selection of devices, search and filtering, and such a counter will be on...

Hello, Apologies for the late reply. Unfortunately, we don't currently plan on implementing this feature and it is also not possible with the current remote Zone implementation. For now, 1 remote Zone = 1 remote location (Unimus Core). As you mentioned, tags could be deployed and they could indicate...

Hello, This specific issue is a DB lock. This can happen if a booting sequence is interrupted at a specific time frame when a DB schema is being updated. Fortunately, it can be easily unlocked manually: 1. Stop Unimus: systemctl stop unimus 2. Unlock the DB using this query directly in MySQL update ...

The reason this is happening is because Unimus doesn't sync devices based on remote IDs (internal IDs from Observium) to pair them not just by their addresses, but also by an identifiers from Observium, so when an address changes, the device will still pair correctly with the one in Unimus database....