Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: Jump upgrade/DRS licensing bug (Joe Martini)
2. Re: Jump upgrade/DRS licensing bug (Ed Leatherman)
3. Tools to analyze call-quality issues after-the-fact?
(Robert Kulagowski)
4. Re: Jump upgrade/DRS licensing bug (Justin Steinberg)
5. Re: Jump upgrade/DRS licensing bug (Wes Sisk (wsisk))
----------------------------------------------------------------------
Message: 1
Date: Fri, 6 Sep 2013 13:55:34 -0400
From: Joe Martini <[email protected]>
To: Lelio Fulgenzi <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
The issue has been reproduced and a defect has been filed.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuj10105
Joe
On Sep 6, 2013, at 10:00 AM, Lelio Fulgenzi <[email protected]> wrote:
I'm really hoping that licensing will re-host my licenses when I ask to do this
since I'm still doing hardware upgrade, not VM. This installing another COP
file doesn't leave me with any warm and fuzzies. :(
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph
519?824?4120 Ext 56354
[email protected]
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
From: "Ryan Ratliff (rratliff)" <[email protected]>
To: "Ed Leatherman" <[email protected]>
Cc: "Cisco VOIP" <[email protected]>
Sent: Friday, September 6, 2013 9:56:52 AM
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
I've got VMs installing now to test this. There is an easy workaround via root
but it shouldn't be required.
-Ryan
On Sep 6, 2013, at 8:14 AM, Ed Leatherman <[email protected]> wrote:
Tried last night, same result.
Also double checked the md5 on the cop file just in case there was difference,
it's identical to the one on CCO though. Got a case open now.
On Thu, Sep 5, 2013 at 7:27 PM, Justin Steinberg <[email protected]> wrote:
try installing the cop file after the DRS restore. I wonder if the restore is
overwriting certain changes made by the cop.
On Thu, Sep 5, 2013 at 11:24 AM, Ed Leatherman <[email protected]> wrote:
Still ending up at the same place with this one; double checked everything this
time no extra steps:
Install CM 7.1.5 cluster using the 9.1 ova, same basic IP's etc as production
Loaded the v1.2 refresh COP file
did NOT reboot
Configured a SFTP server with identical IP/username/password/directory
structure as existing production SFTP
DRS restore from that server
Reboot subs
Reboot pub
verify database replication with "utils dbreplication runtimestate"
initiate an upgrade with "utils system upgrade initiate"
put in credentials for the SFTP server
select SFTP
Get the same error message.
"Upgrades are prohibited during license grace period"
Will work on getting TAC case opened this afternoon or tomorrow.
On Tue, Sep 3, 2013 at 4:29 PM, Ed Leatherman <[email protected]> wrote:
I'm going thru my steps again - the first time i tried it, I configured some
phones (just changed macs on 2 existing ones) mid-way through the process to
test the restore, and my SE thought that might have tripped a licensing check.
I also didn't have the DRS restart location "exactly" the same as the
production one, so fixing that also.
My next attempt should be by the book without any extra-curricular activities
><.
On Tue, Sep 3, 2013 at 4:20 PM, Ryan Ratliff (rratliff) <[email protected]>
wrote:
The refresh COP file is the one you want as long as it's the latest and you did
them in the correct order. This is the second one I've heard of that the cop
file didn't work correctly for 7.1(5). One of my colleagues tested 6.1(5) last
week and confirmed the steps work but I think we'll need to try a 7.1 just to
be sure.
-Ryan
On Aug 30, 2013, at 12:27 PM, Ed Leatherman <[email protected]> wrote:
OK - perhaps I installed the wrong one then; I installed
ciscocm.refresh_upgrade_v1.2.cop.sgn... sounds like I grabbed the wrong one.
Here was what i did:
-Installed fresh 7.1.5 on all VM nodes, let DB sync
-Installed refresh cop per the upgrade doc (I thought this was an odd place for
it but that?s where it wanted it). Did NOT reboot per the documentation.
-Restored DRS file. Rebooted subs. Rebooted Pub. Let DB sync again.
-At this point, I changed some MAC addresses on some of the configured phones
so I could have a few running in the lab for the upgrade; hind sight I probably
don't need this until everything's on 9
-Tried to install the 9.1 firmware - failed with that error
-Tried to upgrade to 9.1 - also failed with that error
On Fri, Aug 30, 2013 at 12:16 PM, Justin Steinberg <[email protected]> wrote:
there is a COP file that you need to install on 7.1.5 that will disable the
licensing and allow you to goto 9.12
On Fri, Aug 30, 2013 at 10:22 AM, Ed Leatherman <[email protected]> wrote:
Good morning,
I'm running through the jump upgrade in my lab for a regional campus so that I
get all the steps correct. I have the UCS hardware they will upgrade to +
VMWare installed, and everything on isolated lab network.
So I took a known good backup of their production CUCM (3 nodes). Installed
7.1.5 into VMWare per the jump document, and restored the DRS backup onto it,
rebooted subs, rebooted pub; everything went smoothly and I can setup a few
phones on this isolated network and register/call, database happy etc.
However now when I go to load new firmware for 9.1 or upgrade the VM to 9.1.2,
I get the following from the command line:
Upgrades are prohibited during license grace period
which seems to be related to CSCtb86875
Licensing page on CUCM doesn't show any issues.
Are other people running into this? I thought I was following through the guide
closely, but it doesn't mention anything about needing to rehost the 7.1
license files or have TAC root in to delete a file during the upgrade.
Since we're likely to run through this exercise a few times (this issue is
exactly why I'm running through it in lab to begin with).. I don't know if its
kosher for me to keep asking licensing to rehome it, since this isn't the
production system. But I guess I will if i need to :)
Where am I going wrong here, or is this normal?
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
--
Ed Leatherman
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130906/0936f069/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 6 Sep 2013 14:42:22 -0400
From: Ed Leatherman <[email protected]>
To: Joe Martini <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID:
<CAFC4dso7jg68S5hEChCBagSktsrATjt_=i7byjtceyzzeqv...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I don't think that one is public yet, can't access it.
TAC did the work-around and we were able to kick off the upgrade to 9.1(2);
I'll just plan on needing to do another SR when we go to do the
"production" upgrade. Thanks everyone for suggestions/assistance!
On Fri, Sep 6, 2013 at 1:55 PM, Joe Martini <[email protected]> wrote:
> The issue has been reproduced and a defect has been filed.
>
> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuj10105
>
> Joe
>
>
>
--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130906/fad32b6f/attachment-0001.html>
------------------------------
Message: 3
Date: Fri, 6 Sep 2013 15:30:51 -0500
From: Robert Kulagowski <[email protected]>
To: Cisco VOIP <[email protected]>
Subject: [cisco-voip] Tools to analyze call-quality issues
after-the-fact?
Message-ID:
<CAGe0w3TKh7PDBfVei0NcHorBt-8isEMeq=_+3_0skswx3mu...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Since we're in the early stages of a SIP deployment, I've had a
sniffer running on the outside of my firewall capturing packets.
During a long duration call I realized that the audio issues I was
hearing were probably being captured in the sniffer; hitting ? ? on my
phone showed a non-periodic "hiccup" which incremented the error count
by 7 each time and resulted in a burst of static.
Wireshark seems to crash a lot in the current 1.10.1 version.
In wireshark, I can import the PCAP and use the "Telephony" option and
it shows the calls that were captured. If I select my call, then go
into the player, I can play the stream and hear the glitch. But
Wireshark doesn't make it easy to analyze the calls; I keep getting
crashes as it follows the RTP streams. :(
Any other tools that will allow me to import a PCAP and analyze my
streams? The bad call has a non-zero percentage of out of order
packets.
Thanks.
------------------------------
Message: 4
Date: Fri, 6 Sep 2013 17:03:40 -0400
From: Justin Steinberg <[email protected]>
To: Joe Martini <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID:
<caccaghaecyxxf-7mpumoa09pawtqjzzw5vc-b4xo9s4tmba...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
is the bug specific to 7.15 ?
On Fri, Sep 6, 2013 at 1:55 PM, Joe Martini <[email protected]> wrote:
> The issue has been reproduced and a defect has been filed.
>
> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuj10105
>
> Joe
>
> On Sep 6, 2013, at 10:00 AM, Lelio Fulgenzi <[email protected]> wrote:
>
> I'm really hoping that licensing will re-host my licenses when I ask to do
> this since I'm still doing hardware upgrade, not VM. This installing
> another COP file doesn't leave me with any warm and fuzzies. :(
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Data Centre and Communications Facilities
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519?824?4120 Ext 56354
> [email protected]
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
> ------------------------------
> *From: *"Ryan Ratliff (rratliff)" <[email protected]>
> *To: *"Ed Leatherman" <[email protected]>
> *Cc: *"Cisco VOIP" <[email protected]>
> *Sent: *Friday, September 6, 2013 9:56:52 AM
> *Subject: *Re: [cisco-voip] Jump upgrade/DRS licensing bug
>
> I've got VMs installing now to test this. There is an easy workaround via
> root but it shouldn't be required.
>
> -Ryan
>
> On Sep 6, 2013, at 8:14 AM, Ed Leatherman <[email protected]> wrote:
>
> Tried last night, same result.
>
> Also double checked the md5 on the cop file just in case there was
> difference, it's identical to the one on CCO though. Got a case open now.
>
>
> On Thu, Sep 5, 2013 at 7:27 PM, Justin Steinberg <[email protected]>
> wrote:
>
>> try installing the cop file after the DRS restore. I wonder if the
>> restore is overwriting certain changes made by the cop.
>>
>>
>> On Thu, Sep 5, 2013 at 11:24 AM, Ed Leatherman <[email protected]>
>> wrote:
>>
>>> Still ending up at the same place with this one; double checked
>>> everything this time no extra steps:
>>>
>>> Install CM 7.1.5 cluster using the 9.1 ova, same basic IP's etc as
>>> production
>>> Loaded the v1.2 refresh COP file
>>> did NOT reboot
>>> Configured a SFTP server with identical IP/username/password/directory
>>> structure as existing production SFTP
>>> DRS restore from that server
>>> Reboot subs
>>> Reboot pub
>>> verify database replication with "utils dbreplication runtimestate"
>>> initiate an upgrade with "utils system upgrade initiate"
>>> put in credentials for the SFTP server
>>> select SFTP
>>> Get the same error message.
>>> "Upgrades are prohibited during license grace period"
>>>
>>> Will work on getting TAC case opened this afternoon or tomorrow.
>>>
>>>
>>> On Tue, Sep 3, 2013 at 4:29 PM, Ed Leatherman <[email protected]>
>>> wrote:
>>>
>>>> I'm going thru my steps again - the first time i tried it, I configured
>>>> some phones (just changed macs on 2 existing ones) mid-way through the
>>>> process to test the restore, and my SE thought that might have tripped a
>>>> licensing check. I also didn't have the DRS restart location "exactly" the
>>>> same as the production one, so fixing that also.
>>>>
>>>> My next attempt should be by the book without any extra-curricular
>>>> activities ><.
>>>>
>>>>
>>>> On Tue, Sep 3, 2013 at 4:20 PM, Ryan Ratliff (rratliff) <
>>>> [email protected]> wrote:
>>>>
>>>>> The refresh COP file is the one you want as long as it's the latest
>>>>> and you did them in the correct order. This is the second one I've heard
>>>>> of that the cop file didn't work correctly for 7.1(5). One of my
>>>>> colleagues tested 6.1(5) last week and confirmed the steps work but I
>>>>> think
>>>>> we'll need to try a 7.1 just to be sure.
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Aug 30, 2013, at 12:27 PM, Ed Leatherman <[email protected]>
>>>>> wrote:
>>>>>
>>>>> OK - perhaps I installed the wrong one then; I installed
>>>>> ciscocm.refresh_upgrade_v1.2.cop.sgn... sounds like I grabbed the wrong
>>>>> one.
>>>>>
>>>>> Here was what i did:
>>>>>
>>>>> -Installed fresh 7.1.5 on all VM nodes, let DB sync
>>>>> -Installed refresh cop per the upgrade doc (I thought this was an odd
>>>>> place for it but that?s where it wanted it). Did NOT reboot per the
>>>>> documentation.
>>>>> -Restored DRS file. Rebooted subs. Rebooted Pub. Let DB sync again.
>>>>> -At this point, I changed some MAC addresses on some of the configured
>>>>> phones so I could have a few running in the lab for the upgrade; hind
>>>>> sight
>>>>> I probably don't need this until everything's on 9
>>>>> -Tried to install the 9.1 firmware - failed with that error
>>>>> -Tried to upgrade to 9.1 - also failed with that error
>>>>>
>>>>>
>>>>> On Fri, Aug 30, 2013 at 12:16 PM, Justin Steinberg <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> there is a COP file that you need to install on 7.1.5 that will
>>>>>> disable the licensing and allow you to goto 9.12
>>>>>>
>>>>>>
>>>>>> On Fri, Aug 30, 2013 at 10:22 AM, Ed Leatherman <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Good morning,
>>>>>>>
>>>>>>> I'm running through the jump upgrade in my lab for a regional campus
>>>>>>> so that I get all the steps correct. I have the UCS hardware they will
>>>>>>> upgrade to + VMWare installed, and everything on isolated lab network.
>>>>>>>
>>>>>>> So I took a known good backup of their production CUCM (3 nodes).
>>>>>>> Installed 7.1.5 into VMWare per the jump document, and restored the DRS
>>>>>>> backup onto it, rebooted subs, rebooted pub; everything went smoothly
>>>>>>> and I
>>>>>>> can setup a few phones on this isolated network and register/call,
>>>>>>> database
>>>>>>> happy etc.
>>>>>>>
>>>>>>> However now when I go to load new firmware for 9.1 or upgrade the VM
>>>>>>> to 9.1.2, I get the following from the command line:
>>>>>>> Upgrades are prohibited during license grace period
>>>>>>>
>>>>>>> which seems to be related to
>>>>>>> CSCtb86875<https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&page=bstBugDetail&BugID=CSCtb86875>
>>>>>>>
>>>>>>> Licensing page on CUCM doesn't show any issues.
>>>>>>>
>>>>>>> Are other people running into this? I thought I was following
>>>>>>> through the guide closely, but it doesn't mention anything about
>>>>>>> needing to
>>>>>>> rehost the 7.1 license files or have TAC root in to delete a file during
>>>>>>> the upgrade.
>>>>>>>
>>>>>>> Since we're likely to run through this exercise a few times (this
>>>>>>> issue is exactly why I'm running through it in lab to begin with).. I
>>>>>>> don't
>>>>>>> know if its kosher for me to keep asking licensing to rehome it, since
>>>>>>> this
>>>>>>> isn't the production system. But I guess I will if i need to :)
>>>>>>>
>>>>>>> Where am I going wrong here, or is this normal?
>>>>>>>
>>>>>>> --
>>>>>>> Ed Leatherman
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cisco-voip mailing list
>>>>>>> [email protected]
>>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ed Leatherman
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> [email protected]
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ed Leatherman
>>>>
>>>
>>>
>>>
>>> --
>>> Ed Leatherman
>>>
>>
>>
>
>
> --
> Ed Leatherman
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130906/920a476c/attachment-0001.html>
------------------------------
Message: 5
Date: Fri, 6 Sep 2013 22:27:58 +0000
From: "Wes Sisk (wsisk)" <[email protected]>
To: Justin Steinberg <[email protected]>
Cc: Cisco VOIP <[email protected]>
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
7.1 versions, yes.
-wes
On Sep 6, 2013, at 5:03 PM, Justin Steinberg
<[email protected]<mailto:[email protected]>> wrote:
is the bug specific to 7.15 ?
On Fri, Sep 6, 2013 at 1:55 PM, Joe Martini
<[email protected]<mailto:[email protected]>> wrote:
The issue has been reproduced and a defect has been filed.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuj10105
Joe
On Sep 6, 2013, at 10:00 AM, Lelio Fulgenzi
<[email protected]<mailto:[email protected]>> wrote:
I'm really hoping that licensing will re-host my licenses when I ask to do this
since I'm still doing hardware upgrade, not VM. This installing another COP
file doesn't leave me with any warm and fuzzies. :(
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph
519?824?4120 Ext 56354<tel:519%E2%80%90824%E2%80%904120%20Ext%2056354>
[email protected]<mailto:[email protected]>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Ryan Ratliff (rratliff)" <[email protected]<mailto:[email protected]>>
To: "Ed Leatherman" <[email protected]<mailto:[email protected]>>
Cc: "Cisco VOIP" <[email protected]<mailto:[email protected]>>
Sent: Friday, September 6, 2013 9:56:52 AM
Subject: Re: [cisco-voip] Jump upgrade/DRS licensing bug
I've got VMs installing now to test this. There is an easy workaround via root
but it shouldn't be required.
-Ryan
On Sep 6, 2013, at 8:14 AM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
Tried last night, same result.
Also double checked the md5 on the cop file just in case there was difference,
it's identical to the one on CCO though. Got a case open now.
On Thu, Sep 5, 2013 at 7:27 PM, Justin Steinberg
<[email protected]<mailto:[email protected]>> wrote:
try installing the cop file after the DRS restore. I wonder if the restore is
overwriting certain changes made by the cop.
On Thu, Sep 5, 2013 at 11:24 AM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
Still ending up at the same place with this one; double checked everything this
time no extra steps:
Install CM 7.1.5 cluster using the 9.1 ova, same basic IP's etc as production
Loaded the v1.2 refresh COP file
did NOT reboot
Configured a SFTP server with identical IP/username/password/directory
structure as existing production SFTP
DRS restore from that server
Reboot subs
Reboot pub
verify database replication with "utils dbreplication runtimestate"
initiate an upgrade with "utils system upgrade initiate"
put in credentials for the SFTP server
select SFTP
Get the same error message.
"Upgrades are prohibited during license grace period"
Will work on getting TAC case opened this afternoon or tomorrow.
On Tue, Sep 3, 2013 at 4:29 PM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
I'm going thru my steps again - the first time i tried it, I configured some
phones (just changed macs on 2 existing ones) mid-way through the process to
test the restore, and my SE thought that might have tripped a licensing check.
I also didn't have the DRS restart location "exactly" the same as the
production one, so fixing that also.
My next attempt should be by the book without any extra-curricular activities
><.
On Tue, Sep 3, 2013 at 4:20 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
The refresh COP file is the one you want as long as it's the latest and you did
them in the correct order. This is the second one I've heard of that the cop
file didn't work correctly for 7.1(5). One of my colleagues tested 6.1(5) last
week and confirmed the steps work but I think we'll need to try a 7.1 just to
be sure.
-Ryan
On Aug 30, 2013, at 12:27 PM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
OK - perhaps I installed the wrong one then; I installed
ciscocm.refresh_upgrade_v1.2.cop.sgn... sounds like I grabbed the wrong one.
Here was what i did:
-Installed fresh 7.1.5 on all VM nodes, let DB sync
-Installed refresh cop per the upgrade doc (I thought this was an odd place for
it but that?s where it wanted it). Did NOT reboot per the documentation.
-Restored DRS file. Rebooted subs. Rebooted Pub. Let DB sync again.
-At this point, I changed some MAC addresses on some of the configured phones
so I could have a few running in the lab for the upgrade; hind sight I probably
don't need this until everything's on 9
-Tried to install the 9.1 firmware - failed with that error
-Tried to upgrade to 9.1 - also failed with that error
On Fri, Aug 30, 2013 at 12:16 PM, Justin Steinberg
<[email protected]<mailto:[email protected]>> wrote:
there is a COP file that you need to install on 7.1.5 that will disable the
licensing and allow you to goto 9.12
On Fri, Aug 30, 2013 at 10:22 AM, Ed Leatherman
<[email protected]<mailto:[email protected]>> wrote:
Good morning,
I'm running through the jump upgrade in my lab for a regional campus so that I
get all the steps correct. I have the UCS hardware they will upgrade to +
VMWare installed, and everything on isolated lab network.
So I took a known good backup of their production CUCM (3 nodes). Installed
7.1.5 into VMWare per the jump document, and restored the DRS backup onto it,
rebooted subs, rebooted pub; everything went smoothly and I can setup a few
phones on this isolated network and register/call, database happy etc.
However now when I go to load new firmware for 9.1 or upgrade the VM to 9.1.2,
I get the following from the command line:
Upgrades are prohibited during license grace period
which seems to be related to
CSCtb86875<https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&page=bstBugDetail&BugID=CSCtb86875>
Licensing page on CUCM doesn't show any issues.
Are other people running into this? I thought I was following through the guide
closely, but it doesn't mention anything about needing to rehost the 7.1
license files or have TAC root in to delete a file during the upgrade.
Since we're likely to run through this exercise a few times (this issue is
exactly why I'm running through it in lab to begin with).. I don't know if its
kosher for me to keep asking licensing to rehome it, since this isn't the
production system. But I guess I will if i need to :)
Where am I going wrong here, or is this normal?
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
--
Ed Leatherman
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130906/497006c0/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 119, Issue 7
******************************************
