5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
I was just writing a PowerShell script and encountered the same thing on 5.10.2 on a cluster running AHV. I can confirm this is still an issue. I’ll open a ticket for a feature request. This is definitely disappointing, especially considering how easy it is to do on ESXi. @McCranium Yes, it has been over a year and the feature is still not available. I hope this gets resolved soon, because this will make things easy when doing inventory, etc. Thanks for the reply and the confirmation @darshan.patel . Hope you have a great weekend.
I was just writing a PowerShell script and encountered the same thing on 5.10.2 on a cluster running AHV. I can confirm this is still an issue. I’ll open a ticket for a feature request. This is definitely disappointing, especially considering how easy it is to do on ESXi.
I'm glad you figured it out. That's great news!
To pass commands programmatically to a puTTY sessions you may want to try plink. It is available from the same site, and you can pass commands as a script that you want to execute. This will likely work better for you. Here are some examples to help out: https://www.thegeekstuff.com/2017/05/putty-plink-examples/ Enjoy!
And for those who are interested, I figured out a way to get the metrics: The metrics appear to be the same as the stats on the host. This really should've been more simple to find in the documentation though. You can see that the metrics that Chandru referenced "hypervisor_memory_usage_ppm" is available in the list below. The metrics appear to be the same as the stats on the host. This really should've been more simple to find in the documentation though. You can see that the metrics that Chandru referenced "hypervisor_memory_usage_ppm" is available in the list below. $NTXSvr = Get-NTNXHost $NTXSvr[0].stats [b]Here's the resultant list:[/b] Key Value --- ----- hypervisor_avg_io_latency_usecs 0 num_read_iops 480 $NTXSvr[0].stats [b]Here's the resultant list:[/b] Key Value --- ----- hypervisor_avg_io_latency_usecs 0 num_read_iops 480 hypervisor_write_io_bandwidth_kBps 0 timespan_usecs 20000000 controller_num_read_iops 419 read_io_ppm 843500 controller_num_iops 668 total_read_io
Thank you @RichardsonPorto, that is exactly the solution we have settled on. It seems like the best balance for moving batches of systems over to the other cluster. Normally, I would've also considered cross-cluster storage vMotions but the vCenters in this environment are not currently running in linked mode. Async DR gives us the option to batch the VMs and cutover when we're ready. Thanks again for your reply, much appreciated.
I've done some more reading and I can see that it is only for migrations to AHV. I know there a multitude of options to do straight V2Vs with VMware but some configurations make these migration methods problematic.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.