12-15-2009 12:28 PM - edited 03-15-2019 08:47 PM
Do you need a to get a new Software Feature License if you are upgrading CUCM from 7.0(2) to 7.1(3)?
I would also like to say that I rarely have to post a question because I usually find the answers to my questions here. Thanks to all that post and answer questions.
Kristine
Solved! Go to Solution.
02-11-2010 07:52 AM
When it was put in as 7.0, it did not require a server software license. I think that was the bug. The Node licenses always worked. There was a two part process you had to get for CUCM after 7.1. First is the Node license. (Publisher, Subscriber, etc). Then there was the server software license. In 7.0, it was not required (which I thing was the bug) you could leave it running as is with node licenses. But when you upgraded to 7.1, it flipped a trigger and found that the server software license was not loaded (in the bottom screen of the licensing summary screen).
In your SmartNet contract, you have to checkout the Node license and the server software licenses for this. You can always email licensing@cisco.com to get a temp license while you get it all sorted out. (or escalate to TAC to get it)
03-03-2010 08:43 AM
Thought I'd post some feedback after running my uprade from 7.0.2 to 7.1.3. Ran the upgrade no problems then had the dreaded license error warning my feature licenses were at a negative number. So I had the upgrade licenses and applied them, still didn't work. Opened a TAC case and what finally fixed it was deleting the upgrade feature licenses off that I had just applied and the original 7.0.2 feature license and then reapplying them, restart the licensing and CM service and it worked. Seems like the licensing should be the easy part....
Gates
03-14-2010 10:15 PM
Restart of the Cisco License Manager service worked. Upgrade was from 7.0 to 7.1(3) DLU's and Node units showed negative values. Nice solution.....no need to discuss with TAC or Licensing. Thanks for the guidance.
04-06-2010 12:04 PM
I am trying to upgrade from 3.3.3 to 7.1.3.
Purchased four brand new 7 appliances.
It's now been four days on the line with TAC and the blasted
license files are still buggered. Downloading and reinstalling
the files over and over is not correcting the problem. Any one know how to fix this
in reality?
04-06-2010 12:10 PM
So not sure what your problem is exactly.
License files from Cisco are generally a pain all the time. And when you do an upgrade, I tell everyone you need at least a week to get all the licensing completed. If not, ask for a temp license, then sort out the perm keys later after the install is done.
As for the upgrade software, If the DMA is not taking, you will probably need to send the TAR file to TAC and let them try in the lab. 3.3 is really tricky from what i heard and the DMAs are not very sucessful as 4.x is. Sounds like if you have 7 appliances, its a large 3.3 enviroment and rebuilding from scratch is not an option. However, rebuilding from scratch might be beneficial for you to start off with a clean cluster.
04-06-2010 01:18 PM
Problem is we upgraded the 3.3 to 4.2.3. Ran DMA onto the new appliance.
Followed prescribed licensing procedures and submitted the PAK file
numbers for the new license files along with the
unit license file. Up loaded the license files and rebooted the server
as instructed. License report shows the unit license, no node license and no software license.
Going to the license up load page shows all three files present.
Have downloaded replacement license files following TAC recommendations and still no joy.
Now are being told there is a bug and to remove all the files and then
just upload the node license to see if that works...
Insert sound of buzzer. Thanks for playing as that didn't work either.
I have four really nice "bricks" and no upgraded call manager.
This is not how to win friends and influence people. ;>
04-06-2010 01:23 PM
Someone must have told you it easy to get licensing. Its not. You basically have to know what to ask for exactly or close the ticket, re-open after 5pm pst time so you get Aust TAC. You can also escalate it to a duty manager to get it resolved asap.
But basically, if 7.x loaded, you are ok. Work on the Publisher and get it licensed first before you try to install the Subs. Its been a couple months since my last upgrade, so maybe the process has changed, but typically, if you put in the complete order through PUT, an email is sent to you with your Entitlement number. I would then go ahead and forward this email to licensing@cisco.com Request a temp license for the DLUs you need, # of nodes and a server software key for 60 days. Then you should be able to load up the subs, test it all out and deal with the id10ts later. Licensing is a pain, it always has been unless you know someone internally to get it for you asap. But typically, if you close the ticket, reopen another ticket you can sometimes get someone who knows what they are talking about.
05-19-2010 01:43 PM
I had the same issue. I upgraded from 7.0.2 to 7.1.3 and when I switched versions I had a licensing error stating I had a temp license and it cut my unit licenses in half. Luckley I reverted back .I Called TAC and was told I did not need version license upgrade. But guess wha?t I did need a version license upgrade. I was on version 7.0.2 but found that the current license was for 6.0. I contacted Cisco licensing team and was asked for the SO#, what A nightmare this became. The licensing team was no help at all. It ended up being the original SO# for the CUCM that they wanted. it took me 6 weeks to get the license. Cisco Licensing team was a nightmare to deal with. After spending a great deal of money I would hope for better service.I even had the our Cisco sales team try to help me get he process moving faster they came back frustrated too.
Frustrated
08-03-2010 12:35 AM
I hit this problem in a few occurences and did some research. This problem is docummented in the 7.1.3 Release Notes !!!
If the node license file contains multiple features (for example: SW_FEATURE + CCM_NODE), after you upgrade to Cisco Unified Communications Manager 7.1(3), the following licensing warnings might display:
•System is operating on insufficient licenses.
•Please upload additional license files.
For additional details and workaround, see CSCtf15332.
The bug proposes 2 workarounds that I have used with success. On some cases the restart of the Licensing has fixed the problem
directly on other cases I had to apply toe workaround 1)
Regards
Christian
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