pkharekofax Tracker

Any fix from engineering for https://kb.vmware.com/s/article/85585

pkharekofax — Thu, 30 Mar 2023 13:51:01 GMT

We are trying to have a single content library per vCenter. Each vCenter has multiple datacenters and host clusters. No storage is shared among all the hosts. Is this possible? We need to have ISOs mountable by VMs, and also store VM templates in the content library.

Thanks,

Khare

Reverse lookup - Get-VM to Get-CIVM possible?

pkharekofax — Thu, 26 Apr 2018 19:23:40 GMT

Hi all,

I know that it's possible to go from vCloud Director to vSphere simply with:

Get-CIVM | Get-VM

But I am looping through VMs from the vCenter side, and need to lookup the VM's vApp, owner etc. if it's a vCloud Director VM.

I.e. reverse of the above:

Get-VM | Get-CIVM #does not work!

Can someone please point me in the right direction how to do this? I'm running vCloud Director 9.0 and 5.5. I can generate a list of all the vCloud VMs along with their vApp, owner etc. and then use this as a lookup, but is there a better/faster way?

Thanks!

Khare

Re: Getting error with Connect-NsxtServer : Invalid JSON primitive

pkharekofax — Thu, 18 Jan 2018 16:01:56 GMT

Thanks, LucD.. That's good to know.

This was a user error, my bad - I was trying to connect to NSX-V using an NSX-T command. The correct command is Connect-NsxServer, not Connect-NsxtServer.

Khare

Re: Getting error with Connect-NsxtServer : Invalid JSON primitive

pkharekofax — Fri, 12 Jan 2018 18:12:15 GMT

OK, I'll log an SR.

Thanks,

Khare

Re: Getting error with Connect-NsxtServer : Invalid JSON primitive

pkharekofax — Fri, 12 Jan 2018 18:11:42 GMT

I asked another person in my team to try and he got the same error.

Thanks,

Khare

Re: Getting error with Connect-NsxtServer : Invalid JSON primitive

pkharekofax — Fri, 12 Jan 2018 18:03:37 GMT

Hi LucD,

Exact same error with Verbose.

C:\> Connect-NsxtServer -Server xxx -Verbose

Connect-NsxtServer : 1/12/2018 12:59:29 PM Connect-NsxtServer Invalid JSON primitive: .

At line:1 char:1

+ Connect-NsxtServer -Server xxx -Verbose

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [Connect-NsxtServer], VimException

+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.Cis.Nsxt.Commands.Cmdlets.ConnectNsxtServer

Thanks,

Khare

Getting error with Connect-NsxtServer : Invalid JSON primitive

pkharekofax — Fri, 12 Jan 2018 16:48:36 GMT

Hi all,

Has anyone encountered this error, and knows a fix?

This is on PowerCLI 6.5.4.7.

Thanks!

Khare

PS C:\> Connect-NsxtServer xxxxxx -User xxx -Password xxx

Connect-NsxtServer : 1/12/2018 11:22:41 AM Connect-NsxtServer Invalid JSON primitive: .

At line:1 char:1

+ Connect-NsxtServer xxxxxx -User xxx -Password xxx...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [Connect-NsxtServer], VimException

+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.Cis.Nsxt.Commands.Cmdlets.ConnectNsxtServer

PS C:> get-module vmware.powercli -ListAvailable

ModuleType Version Name ExportedCommands

---------- ------- ---- ----------------

Manifest 6.5.4.7... VMware.PowerCLI

PS C:\> get-module *nsxt

ModuleType Version Name ExportedCommands

---------- ------- ---- ----------------

Binary 2.0.0.6... VMware.VimAutomation.Nsxt {Connect-NsxtServer, Disconnect-NsxtServer, Get-NsxtService}

Re: vCloud Director 5.5 PowerCLI issue with vApp and VM names with +, & and #

pkharekofax — Fri, 12 Jan 2018 16:42:56 GMT

It would be nice if the GUI itself blocks users from entering such data in the first place.

Thanks,

Khare

vCloud Director 5.5 PowerCLI issue with vApp and VM names with +, & and #

pkharekofax — Thu, 29 Jun 2017 16:11:20 GMT

Hi all,

I get an "ObjectNotFound" error while trying to get vApps and VMs using Get-CIvApp, Get-CIvAppTemplate, or Get-CIVM for vApps and VMs that have +, &, or # in their name.

If I rename the vApp or VM and replace these characters, by say, a dash, there's no problem. Also, if I try to get the vApp for a VM using (get-civm vmname).vapp, it doesn't return anything if the vApp name has +, &, or #.

This is with the latest release of PowerCLI. Has anyone else seen this, and is there a solution other than us renaming all such vApps and VMs?

In the vCloud Director GUI, if you search with these characters, press back arrow and then front arrow, these characters get replaced by Percent Encoding in the search box, e.g. + gets replaced by %2B.

Thanks,

Khare

E.g. We have a vApp with a '+' in its name: "KTA 7.3.1 + SP", and it has a VM "SharePoint_2013".

========================= Before renaming: ============================

We see the VM.

PS>get-civm Sharepoint_2013

Name Status GuestOSFullName CpuCount MemoryGB

---- ------ --------------- -------- --------

SharePoint_2013 Suspended Microsoft Windows Server 2008 R2 (64-... 1 4.000

We try to get its vApp, but it returns nothing.

PS>(get-civm Sharepoint_2013).vapp

Try looking for the vApp itself that has a '+' in its name, nothing is returned.

PS>Get-CIVApp "KTA 7.3.1 + SP"

Get-CIVApp : 6/28/2017 7:59:11 AM Get-CIVApp CIVApp with name 'KTA 7.3.1 + SP' was not found using the specifi

At line:1 char:1

+ Get-CIVApp "KTA 7.3.1 + SP"

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (:) [Get-CIVApp], VimException

+ FullyQualifiedErrorId : Core_OutputHelper_WriteNotFoundError,VMware.VimAutomation.Cloud.Commands.Cmdlets.GetCIVApp

========================= After renaming + to - : ============================

Look for the vApp, now we find it.

PS>Get-CIVApp "KTA 7.3.1 - SP"

Name Enabled InMaintenanceMode Owner

---- ------- ----------------- -----

KTA 7.3.1 - SP True False conor.callan

Look for the VM’s vApp, we find it this way as well.

PS>(get-civm Sharepoint_2013).vapp

Name Enabled InMaintenanceMode Owner

---- ------- ----------------- -----

KTA 7.3.1 - SP True False conor.callan

Re: Corrupted VMFS data stores - how to root-cause?

pkharekofax — Mon, 21 Apr 2014 11:44:14 GMT

Since upgrading firmware on our storage - HP P2000 - we haven't had any errors or issues. So looks like this is fixed.

Khare

Re: Corrupted VMFS data stores - how to root-cause?

pkharekofax — Tue, 18 Mar 2014 19:07:51 GMT

Thanks for all the pointers, Ulli. I've asked the storage folks if they've had any power outages where the storage has gone down hard, and if the firmware is up to date.

We haven't made any changes here like mounting/unmounting/adding/removing. It's a pretty stable environment. We also don't use any backup software like Veeam, as this is Lab Manager and is made of trees of linked clones.

Khare

Corrupted VMFS data stores - how to root-cause?

pkharekofax — Tue, 18 Mar 2014 13:37:35 GMT

Hi all,

We are running Lab Manager 4, so we still have ESXi 4.1 hosts in our infrastructure that we cannot upgrade to ESXi 5.x.

At one of our sites, we regularly see VMFS corruption, where some VM folders cannot be read/deleted/listed. We are in the process of adding new storage and migrating our current VMs out of the corrupted data stores, but I'd like to find out what is causing this corruption, and how can I prevent it from happening in the future?

Hosts: HP DL360p G7

Storage: HP P2000 G3

ESXi: 4.1.0 build-260247

If we see many such errors, once we reboot all the hosts, the number goes down considerably (e.g. from 20 errors, we are left with just 3).

Have you seen such an issue at your site?

Thanks,

Khare

Examples:

/vmfs/volumes/4fc87616-2a581cdc-6b13-3cd92bee82a4/dirname # ls -l * >/dev/null

ls: 10589/timA: Invalid argument

ls: 10589/: Invalid argument

ls: 10589/

: Invalid argument

ls: 10589/: Invalid argument

ls: 10589/

nvalid argument

ls: 11843/IHDR: Invalid argument

ls: 11843/e: Invalid argument

ls: 11941/n="1.0"?>

<VM>

<clientMeta: No such file or directory

ls: 11941/es/>

<vmxPathName type="string">017695-Central1.vmx</vmxPathName></VM></Foundry>

: No such file or directory

ls: 12351/IHDR: Invalid argument

ls: 12351/e: Invalid argument

ls: 12478/012478-12478-2k8-Central.vmx.LMBackup: No such file or directory

ls: 7600/IHDR: Invalid argument

ls: 7600/YJ)Ù|Ñ6"¢ªyc,zö!ïýS: Invalid argument

ls: 9251/009251-VirtualRouter_C2796F3338_DoNotModify.vmxf: No such file or directory

ls: 9251/009251-VirtualRouter_C2796F3338_DoNotModify.vmsd: No such file or directory

ls: 9618/IHDR: Invalid argument

Re: vCD 5.1.2 - How can we suspend all running vApps using the API or a command?

pkharekofax — Wed, 15 May 2013 19:29:02 GMT

Thank you.

Re: vCD 5.1.2 - How can we suspend all running vApps using the API or a command?

pkharekofax — Wed, 15 May 2013 19:17:06 GMT

In vApp Workflows under "vApp Power Workflows", there is a Workflow named "Undeploy a vApp" : Stops or suspends a vApp and frees the resources reserved for the vApp. Do you know what resources are freed if I use it instead of "Suspend a vApp": Suspends a vApp. Does not free the resources reserved for the vApp? I'm planning to use vCO for the task of suspending all running vApps.

Thanks!

Re: vCD 5.1.2 - How can we suspend all running vApps using the API or a command?

pkharekofax — Wed, 15 May 2013 18:38:19 GMT

Thanks for your response, but I was looking for something like Lab Manager 4.0 Internal APIs. LM used to have ManagedServerPerformAction, action 3 for Undeploy all VMs for a host.

vCD 5.1.2 - How can we suspend all running vApps using the API or a command?

pkharekofax — Wed, 15 May 2013 18:17:48 GMT

I can iterate through a list of deployed vApps, but is there a better way? We need to suspend all running vApps before kicking off a backup using SAN snapshots.

Is there an internal API doc available, like the one for Lab Manager?

Thanks!