06-18-2013 06:09 AM - edited 03-01-2019 11:05 AM
I am in the processing of bringing up a B chassis. I found a copy of ESXi 5.0 that was "tweaked" by Cisco. I have tried several license keys and they arent accepted. I took the PAK keys as provided by Cisco and generated the VMware keys at the VMware link. Should I be using ESXi 5.1 instead ?
Ron
Solved! Go to Solution.
06-19-2013 06:48 AM
Finally got the problem resolved on my own after several hours.
Here are the lessons learned to help others from avoiding this situation -
1) When you registered the PAC keys on the VMware licensing portal, you should receive an email from VMware giving the same information as what you had on the web page. Part of the problem I ran into is that I never received the email, so it would appear that the license keys I had from the web page werent activated on VMware's end.
2) The license keys are single CPU only. The Vsphere client will not install a single CPU license on a B series blade because it is a dual cpu configuration. The licenses are not additive, in that you cannot install 2 single CPU licenses in order to be properly licensed. I had to go back to VMware's licensing portal and "combine" two licenses into one. Once I did that I was able to get the license to install.
3) It will serve you well to document the licensing when you first get it, what licenses are combined to create the license that vSphere will accept and what serial number of the B or C series chassis that you are installing them on. Dont see an initial need to do this but with the hassle I went through to get the license I had to a useable condition, this helps build an audit trail in case something goes south.
My concern is that the licensing group didnt appear to read the case notes that I entered. From what I went through, this doesnt appear to be either documented or published to the point where it is easily found. If there is interest, I will be happy to create a document listing the steps to go through to make it easier for others.
06-18-2013 06:17 AM
Hello Ron,
Yes, it is recommended to install Cisco OEM version of ESXi image.
HCL is documented here
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
What is the error that you get when you apply the licenses ?
Padma
06-18-2013 06:46 AM
I have tried both the Cisco tweaked 5.0 and VMware 5.1 ISO's.
I get the following error - An error occurred when assigning the specified license key. License is not valid for this product.
06-18-2013 06:52 AM
Hello Ron,
I would suggest you to open a case with licensing team with your PAK details.
Padma
06-18-2013 12:20 PM
I have opened a case with TAC which was transferred to Licensing. They are telling me that it is the Partners problem. I have uploaded (twice) the document from Cisco that says otherwise.
Can someone give me the name of the UCS Product Manager and phone number ? I have had challenges in dealing with the License group in the past and havent had good results.
If the wrong key has been ordered, which I dont think is the case, I will get the Partner to make good on it.
Thanks,
Ron
06-19-2013 05:54 AM
Hello Ron,
I am not the PM but will follow up on your TAC SR and will get back to you.
HTH
Padma
06-19-2013 06:48 AM
Finally got the problem resolved on my own after several hours.
Here are the lessons learned to help others from avoiding this situation -
1) When you registered the PAC keys on the VMware licensing portal, you should receive an email from VMware giving the same information as what you had on the web page. Part of the problem I ran into is that I never received the email, so it would appear that the license keys I had from the web page werent activated on VMware's end.
2) The license keys are single CPU only. The Vsphere client will not install a single CPU license on a B series blade because it is a dual cpu configuration. The licenses are not additive, in that you cannot install 2 single CPU licenses in order to be properly licensed. I had to go back to VMware's licensing portal and "combine" two licenses into one. Once I did that I was able to get the license to install.
3) It will serve you well to document the licensing when you first get it, what licenses are combined to create the license that vSphere will accept and what serial number of the B or C series chassis that you are installing them on. Dont see an initial need to do this but with the hassle I went through to get the license I had to a useable condition, this helps build an audit trail in case something goes south.
My concern is that the licensing group didnt appear to read the case notes that I entered. From what I went through, this doesnt appear to be either documented or published to the point where it is easily found. If there is interest, I will be happy to create a document listing the steps to go through to make it easier for others.
06-19-2013 06:53 AM
Hello Ron,
Thanks for sharing the procedure.
Padma
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide