WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Uncategorized / vi-fastpass esxcli and resxtop bug resolved in vMA 5

vi-fastpass esxcli and resxtop bug resolved in vMA 5

07.27.2011 by William Lam // 2 Comments

Awhile back I wrote about an resxtop bug found in vMA 4.1 in which it no longer functions with vMA's vi-fastpass component and still requires you to provide the username and password even though vi-fastpass has been initialized for a given target. There was also a slight quirk when using esxcli and vi-fastpass, in which you had to specify in addition the --server of your ESX(i) host which allowed you to utilize vi-fastpass.

With the latest release of vMA 5, both of these issues have now been resolved for both ESXi 5 and ESX(i) 4.x. I would highly recommend you download the latest version if you would like to make use the vi-fastpass component in vMA.

Here is an example of using vi-fastpass with resxtop:

vi-admin@vma50-1:~> vifptarget -s himalaya.primp-industries.com
vi-admin@vma50-1:~[himalaya.primp-industries.com]> resxtop

Here is an example of using vi-fastpass with esxcli:

vi-admin@vma50-1:~> vifptarget -s himalaya.primp-industries.com
vi-admin@vma50-1:~[himalaya.primp-industries.com]> esxcli

More from my site

  • How to Automate the disabling of the VAAI UNMAP primitve in ESXi 5
  • Cool Undocumented Features in vCloud Director 1.5
  • Tips and Tricks for vMA 5
  • Free Linux & Windows Syslog Alternatives to depercated vi-logger in vMA 5
  • Major Enhancements in esxcli for vSphere 5

Categories // Uncategorized Tags // esxcli, ESXi 5.0, resxtop, vMA5, vSphere 5.0

Comments

  1. *protectedroemer2201 says

    08/15/2012 at 8:05 am

    Can you confirm, that if you update the vMA appliance to the latest version 5.0.0.2 Build 724898 the behaviour that you need to specify --server for esxcli commands. With vMA in the default version 5.0.0.0 Build 472630 this Problem does not occure.

    Thank you

    Reply
  2. *protectedKattrap says

    12/07/2012 at 1:36 am

    I can confirm that either the bug William specified above or something very similar is in 5.0.0.2 that wasn't in 5.0.0.0.

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC) across Private, Hybrid and Public Cloud

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • vSphere Code Capture is your ChatGPT for vSphere Automation 11/30/2023
  • ESXi 8.0 Update 2 not detecting Apple NVMe on Apple Mac Mini 2018 11/28/2023
  • Is there a vSphere REST API for ... 11/21/2023
  • Custom vSAN HCL JSON for VMware Cloud Foundation (VCF) 5.1 and vSAN ESA using Nested ESXi 11/20/2023
  • Heads Up - Performance Impact with VMware Workstation on Windows 11 with Intel Hybrid CPUs 11/19/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023