Comments
-
If the login requires anything like 2 factor auth or things like that which deviate from a relatively standard user and pass login it will probably run into some issues.
-
That is a known issue in the SMI-S provider on those 3Par arrays. The value comes from "TPD_StorageSystem:OperationalStatus" and it always returns "3" which according to the 3Par docs is "Degraded".
-
VMAN does not use the MOB for any part of it's polling process. VMAN only uses the API. The MOB is useful for troubleshooting sometimes just to validate what is being returned to the API but it is safe to disable the MOB if you use VMAN.
-
You should be able to follow the steps located at the link below. In particular, you are looking for Step 4 of Task 2. "Select the type of scalability engine to install..." https://documentation.solarwinds.com/en/success_center/orionplatform/content/install-scalabilityengine.htm You'll also need to check that you have a…
-
The CVM credentials are needed for hardware health monitoring: https://documentation.solarwinds.com/en/success_center/vman/content/vman-required-permissions-for-vmware-and-hyper-v-credentials.htm Nutanix CVM credentials For monitoring hardware health of Nutanix clusters and AHV hosts, you need to create and assign…
-
Got it. Thanks for the input! Some of this is already captured in existing feature requests we have in the backlog. I'll reach out directly if I need more specifics.
-
We are not actively working on conditional blocks at the moment but I would be interested in gathering a bit more detail from your use case. I'll reach out to you directly to schedule some time to talk.
-
@"lcsw2013" I have discussed the tickets internally as well and it is very likely the suggestion from @"aLTeReGo" will help you spot the issue. However, if you get stuck again please reach out to support to re-open one of the previous tickets you mentioned and the team will pick up the troubleshooting thread from there and…
-
Yes, the latency values are in milliseconds. For IOPS it is commands per second and throughput is Bytes per second.
-
Thanks, give me a bit of time to discuss with a few folks.
-
The player component which is responsible for running the checks is also based on a browser. The legacy playbacks are run from an Internet Explorer instance and the newer playbacks run on a Chromium engine. Is it possible you could deploy specific non-server VMs to run the players? Depending on the complexity and number of…
-
Yes, please ping me the ticket numbers and I will discuss internally so we might get you to a better solution.
-
Off the top of my head I can't think of a reason this should report this way. Could you open a ticket with support on this so the team can investigate the problem with you?
-
Most of the OOTB alerts for LUNs are for latency and capacity issues. But you should be able to create a new alert and set the object to alert on as LUN and then something like "status is not equal to up"
-
We released VMAN 2020.2.6 today and this version includes native support for VMware Tags. https://thwack.solarwinds.com/product-forums/virtualization-manager-vman/b/news/posts/virtualization-manager-vman-2020-2-6-is-now-generally-available
-
We released VMAN 2020.2.6 today and this version includes native support for VMware Tags. https://thwack.solarwinds.com/product-forums/virtualization-manager-vman/b/news/posts/virtualization-manager-vman-2020-2-6-is-now-generally-available
-
We released VMAN 2020.2.6 today and this version includes native support for VMware Tags. https://thwack.solarwinds.com/product-forums/virtualization-manager-vman/b/news/posts/virtualization-manager-vman-2020-2-6-is-now-generally-available
-
Thanks for the screenshot... I cannot think of a reason why physical servers would show up this way. Would you mind opening a ticket so our support team can have a look? Something is certainly off here and we should troubleshoot.
-
That is strange indeed. You mention they are blades so I would certainly understand them showing up as sitting on the physical chassis they live in but not as virtual machines within a virtual host. At first glance that makes no sense at all... Any chance you can share a screenshot with any internal data scrubbed out? Also…
-
@"smahamulkar" I am not aware of any known issues similar to what you are experiencing. Go ahead and open a ticket and allow our support team to investigate with you.
-
Not sure if it is what you are looking for but the multi-module guidelines have some info about how to size up when adding new modules. SRM is not specifically called out in the t-shirt size tables at the top but there is a section towards the bottom that just uses the number of installed modules to give some idea of how…
-
@"borgan" It looks like you can add an ME4024 using the DotHill connection as it is a re-branded device. You can always stand up an eval copy of SRM to try this out and validate in your environment once you acquire the device.
-
Still validating. Sorry for the delay but want to be absolutely sure it is going to work and be supported properly.
-
Thanks! Got it! I am looking through the details and talking with the team.
-
Can you post or send me the ticket number so I can look internally at what has been done on the ticket so far?
-
From the array's perspective a thick provisioned LUN is full so that is what most devices report to SRM. Generally speaking you will want to look inside the owner of the filesystem (server / VM) mapped to the LUN to understand how much free space there is available.
-
At the moment I do not believe that model would be supported. I am double checking with the engineering team to see if the MD 3xxx connection would be close enough for official support.
-
Great! Glad to hear it worked. :)
-
Only thing I can think of off the top of my head is that I vaguely recall some of those devices need for HTTP to be enabled on the device and then you have to check the box in the SRM config "Use HTTP"... But it has been a long time so I may be off there. You might want to open a ticket with the support team on this as it…
-
No update to share unfortunately. At this time we do not have a public facing document that shows this level of detail for metrics polled by VMAN on Orion.