VMware-vSphere-CLI

Re: New Message from Brett Tiller in Service Ready Engine Virtualization -

2012-01-10T23:13:46Z

Brett, That will work. Thank you very much. John On 01/10/2012 04:02 PM, Cisco Developer Community Forums wrote: > Brett Tiller has created a new message in the forum "SRE-V Technical > Questions": > > -------------------------------------------------------------- > Hi John, > > We've done some research and have found a potential workaround for you > that might suit your needs. VMware provides a 'vim-cmd' in the > tech-support console. From our tests it appears that you can use this > command to power on/off vms and much more with the hypervisor license. > We've provided a test case below in which a Windows VM is started/stopped. > > Hope this helps, > > Brett > > > ** License** > Product: vSphere 4 Hypervisor Licensed for 1 physical CPUs (1-6 cores > per CPU) > License Key: 5M6CL-FEL5N-P8M3A-0A9RH-CXC54 > Expires: Never > > Product Features: > Up to 256 GB of memory > Up to 4-way virtual SMP > > > **The Test** > 1. Ssh to the ESXi tech support command line > 2. Run commands below. > > ~ # vim-cmd /vmsvc/getallvms > Vmid Name File Guest OS Version Annotation > 32 VM-Win2k8r2 [datastore] VM-Win2k8r2/VM-Win2k8r2.vmx > windows7Server64Guest vmx-07 Exported Win2k8r2 VM. ESXi 4.1 > > ~ # vim-cmd /vmsvc/power.on 32 > Powering on VM: > > ~ # vim-cmd /vmsvc/power.off 32 > Powering off VM: > -- > To respond to this post, please click the following link: > > > > or simply reply to this email. -- *John Quintanilla *Sr. Systems Analyst AvFinity, L.L.C. Email: jqq@avfinity.com Web: http://www.AvFinity.com/ Office: 512-535-3384 AvFinity LLC, Your messages will fly too! LinkedIn blogger.com facebook.com YouTube Twitter RSS Feed AvFinity LLC is an IATA Strategic Partner This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies.

RE: VMware-vSphere-CLI

2012-01-10T23:02:55Z

Hi John, We've done some research and have found a potential workaround for you that might suit your needs. VMware provides a 'vim-cmd' in the tech-support console. From our tests it appears that you can use this command to power on/off vms and much more with the hypervisor license. We've provided a test case below in which a Windows VM is started/stopped. Hope this helps, Brett ** License** Product: vSphere 4 Hypervisor Licensed for 1 physical CPUs (1-6 cores per CPU) License Key: 5M6CL-FEL5N-P8M3A-0A9RH-CXC54 Expires: Never Product Features: Up to 256 GB of memory Up to 4-way virtual SMP **The Test** 1. Ssh to the ESXi tech support command line 2. Run commands below. ~ # vim-cmd /vmsvc/getallvms Vmid Name File Guest OS Version Annotation 32 VM-Win2k8r2 [datastore] VM-Win2k8r2/VM-Win2k8r2.vmx windows7Server64Guest vmx-07 Exported Win2k8r2 VM. ESXi 4.1 ~ # vim-cmd /vmsvc/power.on 32 Powering on VM: ~ # vim-cmd /vmsvc/power.off 32 Powering off VM:

RE: New Message from John Quintanilla in Service Ready Engine Virtualizatio

2012-01-10T22:10:46Z

I think you need the next level of license as suggested by John. Thanks

Re: New Message from Anurag Gurtu in Service Ready Engine Virtualization -

2012-01-10T21:28:46Z

Anurag, Here's what it shows in vClient: Product: vSphere 4 Hypervisor Licensed for 1 physical CPUs (1-6 cores per CPU) License Key: 4xxxx-xxxxx-xxxxx-xxxxx-xxxxx Expires: Never Product Features: Up to 256 GB of memory Up to 4-way virtual SMP John On 01/10/2012 01:50 PM, Cisco Developer Community Forums wrote: > Anurag Gurtu has created a new message in the forum "SRE-V Technical > Questions": > -------------------------------------------------------------- > John, > > > > Do you see any message on the bottom right of vSphere screen which > says your evaluation license will expire in X days or can you click on > licensing section within vSphere and tell us what you see? > > > > Thanks > -- > To respond to this post, please click the following link: > > or simply reply to this email. -- *John Quintanilla *Sr. Systems Analyst AvFinity, L.L.C. Email: jqq@avfinity.com Web: http://www.AvFinity.com/ Office: 512-535-3384 AvFinity LLC, Your messages will fly too! LinkedIn blogger.com facebook.com YouTube Twitter RSS Feed AvFinity LLC is an IATA Strategic Partner This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies.

RE: New Message from John Quintanilla in Service Ready Engine Virtualizatio

2012-01-10T20:50:46Z

John, Do you see any message on the bottom right of vSphere screen which says your evaluation license will expire in X days or can you click on licensing section within vSphere and tell us what you see? Thanks

RE: New Message from John Quintanilla in Service Ready Engine Virtualizatio

2012-01-10T20:22:46Z

Hi John, When the people on the ESXi forums talk about the ¿free¿ version of ESXi, they mean the version of ESXi that does not contain API support or vCenter support. This is the vSphere Hypervisor version of ESXi. To get API support or vCenter support, you need the equivalent of a vSphere Essentials, vSphere Standard, or vSphere Enterprise license. Please note that the license for the basic version ¿ i.e., vSphere Hypervisor ¿ is ¿Free¿ from VMware but maintenance/support from VMware is not. Since Cisco re-sells and supports the vSphere Hypervisor software as SRE-V, Cisco has a different license model than VMware for this software. I.e., Cisco charges a license fee for the vSphere Hypervisor license, but maintenance/support is included ¿free¿ as part of the router SMARTNet contract which is ultimately lower cost for Cisco customers than the VMware license/support model. The license Cisco sells as FL-SRE-V-HOST is vSphere Hypervisor; to confirm, this license does not include any of the API support or vCenter support in other VMware licenses. In order to be able to use the vSphere APIs/vCenter support, you will need to purchase the FL-SRE-V-VC-UPG= license for your module. This will upgrade your license to the equivalent of vSphere Essentials. If you need this support for new modules, then the FL-SRE-V-HOSTVC license is the correct license to purchase instead of FL-SRE-V-HOST Best Regards, John From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, January 10, 2012 10:45 AM To: cdicuser@developer.cisco.com Subject: New Message from John Quintanilla in Service Ready Engine Virtualization - SRE-V Technical Questions: VMware-vSphere-CLI John Quintanilla has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- Hello, I'm running a licensed version of SRE-V/ESXi 4.1 on an SM-SRE-910. I was hoping to use the command line vSphere CLI to run virtual machine operations (e.g vmware-cmd stop) instead of having to use vSphere vClient from Windows. I ran stop/start against a VM and received the following error message Operation cannot be performed: SOAP Fault: ----------- Fault string: fault.RestrictedVersion.summary Fault detail: RestrictedVersionFault After searching the vmware community, most reported this error condition when using a free version of ESXi, which isn't the case for me, since I do have a licensed version. Did I miss a configuration step? Any insight would be appreciated. Thanks. John -- To respond to this post, please click the following link: or simply reply to this email.

VMware-vSphere-CLI

2012-01-10T19:44:44Z

Hello, I'm running a licensed version of SRE-V/ESXi 4.1 on an SM-SRE-910. I was hoping to use the command line vSphere CLI to run virtual machine operations (e.g vmware-cmd stop) instead of having to use vSphere vClient from Windows. I ran stop/start against a VM and received the following error message Operation cannot be performed: SOAP Fault: ----------- Fault string: fault.RestrictedVersion.summary Fault detail: RestrictedVersionFault After searching the vmware community, most reported this error condition when using a free version of ESXi, which isn't the case for me, since I do have a licensed version. Did I miss a configuration step? Any insight would be appreciated. Thanks. John