[cisco-voip] callmanager license migration from 4.x to 6.x
Lelio Fulgenzi
lelio at uoguelph.ca
Fri Mar 7 11:16:17 EST 2008
I would suspect that at some point in time, especially in the event of a hardware failure, the licencing team will have to issue you a new licence based on the new MAC address. While I don't condone it, I don't see why you couldn't install the software, do what you have to do, then call the TAC to say you are upgrading hardware and require a new licence key. Essentially that's what you are doing anyways.
Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys is inversely
related to the amount of caffeine ingested in the last 30 minutes.
----- Original Message -----
From: Aman Chugh
To: Cisco Voip List
Sent: Friday, March 07, 2008 11:11 AM
Subject: Re: [cisco-voip] callmanager license migration from 4.x to 6.x
Thanks all for helping out with this one, I had to work with the Cisco Account team to get a new license.
Regards,
Aman
On 3/7/08, Jonathan Charles <jonvoip at gmail.com> wrote:
Delete all references to it on the publisher, make it look like a
single node, then add the new Subscriber and create a new CallManager
group with the new Subscriber.
Jonathan
On Thu, Mar 6, 2008 at 2:41 PM, Justin Steinberg <jsteinberg at gmail.com> wrote:
> you have me doubting myself now...
>
> Speaking of the DMA upgrade, I am in the middle of one right now in which I
> changed hostnames during the 4.x to 6.x upgrade.
>
> For some reason, the new 6.1.1a publisher is still trying to replicate to
> the old subscriber hostname, even though i deleted it. This has broken the
> replication to the new subscriber as well.
>
> I have a TAC case open and the first two TAC engineers have told me that it
> isn't supported to change hostname from 4.x to 6.x......ahhhh
>
> Does anyone know what I need to do to get rid of the old subscriber name? i
> think TAC needs to root in and edit the sqlhosts maybe?
>
>
>
>
>
> On Thu, Mar 6, 2008 at 5:06 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
> >
> > I don't think the mac is included in the xml output. I know for a fact
> the mac address is a separate field in the web page from the XML output.
> >
> >
> > Regarding the time wasted I imagine for most people getting DMA done
> correctly is the longest part. The install itself will generally be a small
> part of the entire time for the upgrade.
> >
> >
> > While on this note please, please if you are considering a 4.x to 5/6.x
> upgrade do not wait to the last minute to do your DMA and assume everything
> will be fine. If your system has been in production (or even in a lab) for
> any amount of time you will most likely have some errors that need to be
> taken care of and sorting these out can take time. Running DMA for the
> first time Friday night before your Saturday upgrade is just asking for
> trouble.
> >
> >
> >
> >
> > -Ryan
> >
> >
> >
> >
> >
> > On Mar 6, 2008, at 4:56 PM, Justin Steinberg wrote:
> > not exactly.
> >
> > If you install CM6 on your LAB 7835, the associated DMA license files will
> generate with that lab 7835 MAC address
> >
> >
> > On Thu, Mar 6, 2008 at 4:45 PM, Linsemier, Matthew
> <MLinsemier at apcapital.com> wrote:
> >
> > > This would great, except for the fact that you still have to perform the
> > > entire upgrade to get this result. Again, there are a lot of us out
> > > there that want to perform a more controlled migration to 6.x than just
> > > upgrading the entire box in one fell swoop.
> > >
> > > In our case we have an extra 7835 server in the lab so if I can't get
> > > licensing through using the SO I can pop a drive out of our production
> > > Publisher and perform the upgrade, get the new license without effecting
> > > actually upgrading our production environment. However, everyone can't
> > > necessarily do this.
> > >
> > > There still needs to be an easier way. Would just running a utility on
> > > a 4.x server that generates a 6.x license (for Cisco) without upgrading
> > > really make a huge difference? I understand that they are trying to
> > > prevent people from "cheating the proverbial licensing system", but
> > > there are so many workarounds already that it really doesn't matter in
> > > the grand scheme of things in my humble opinion.
> > >
> > > Matt
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Jonathan Charles [mailto:jonvoip at gmail.com]
> > > Sent: Thursday, March 06, 2008 4:32 PM
> > > To: Linsemier, Matthew
> > > Cc: Frazee, Timothy; Cisco Voip List
> > > Subject: Re: [cisco-voip] callmanager license migration from 4.x to 6.x
> > >
> > > Then, here's what you do to make life easy
> > >
> > > Use the DMA tool and upgrade CCM to 6
> > >
> > > Then, get the license.
> > >
> > > Then blow the CCM6 box away and build it from scratch
> > >
> > > use the license you just got.
> > >
> > >
> > >
> > > Jonathan
> > >
> > > On Thu, Mar 6, 2008 at 3:23 PM, Linsemier, Matthew
> > > <MLinsemier at apcapital.com> wrote:
> > > > We will be doing something similar as the original poster here within
> > > > the next month. We are installing a brand new cluster specifically
> > > > because we don't want to upgrade. At Networkers Live in 2006, the
> > > Cisco
> > > > personnel in the CallManager 5.x/6.x licensing breakout session
> > > stated
> > > > that you can get licenses generated by providing them with the
> > > original
> > > > Cisco Sales Order number.
> > > >
> > > > On a side note, someone does need to take this back to Cisco to make
> > > > this process easier. In our case we have almost 5 years of moves,
> > > adds,
> > > > changes, office closures, multiple upgrades of the database (from
> > > > versions 3.x to 4.x), old configurations lingering around, etc. I
> > > don't
> > > > want this stuff imported into a fresh clean UCM 6.0 cluster. We want
> > > a
> > > > virgin start which is why we are planning to install from scratch. I
> > > > imagine we are not alone.
> > > >
> > > > Matt
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: cisco-voip-bounces at puck.nether.net
> > > > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
> > > > Charles
> > > >
> > > >
> > > > Sent: Thursday, March 06, 2008 1:34 PM
> > > > To: Frazee, Timothy
> > > > Cc: Cisco Voip List
> > > > Subject: Re: [cisco-voip] callmanager license migration from 4.x to
> > > 6.x
> > > >
> > > > No.
> > > >
> > > > There are only two methods of getting data from CCM 4 to CCM 6
> > > >
> > > > METHOD 1: DMA and then a clean rebuild of CCM6 referencing the DMA
> > > file.
> > > >
> > > > METHOD 2: BAT, export the info from CCM 4, reimport into CCM6
> > > >
> > > >
> > > >
> > > > Jonathan
> > > >
> > > > On Thu, Mar 6, 2008 at 12:05 PM, Frazee, Timothy
> > > > <Timothy_Frazee at adp.com> wrote:
> > > > > Can you do the upgrade on the 4.x box to 6.x, to get all of your
> > > > > licenses upgraded and such, then do a backup/restore from the
> > > > upgraded
> > > > > 4to6 box to a newly installed 6 server?
> > > > >
> > > > > A lot of work I know.
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: cisco-voip-bounces at puck.nether.net
> > > > > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
> > > > > Charles
> > > > >
> > > > >
> > > > > Sent: Thursday, March 06, 2008 11:08 AM
> > > > > To: Aman Chugh
> > > > > Cc: Cisco Voip List
> > > > > Subject: Re: [cisco-voip] callmanager license migration from 4.x
> > > to
> > > > 6.x
> > > > >
> > > > > Do the windows upgrade.
> > > > >
> > > > > Seriously, you only have two other options...
> > > > >
> > > > > Option 1: Buy licenses for everything.
> > > > >
> > > > > Options 2: Convince Cisco to give you one.
> > > > >
> > > > >
> > > > >
> > > > > Jonathan
> > > > >
> > > > > On Thu, Mar 6, 2008 at 9:23 AM, Aman Chugh <aman.chugh at gmail.com>
> > > > wrote:
> > > > > > Thanks all for replying. I am not doing a backup and restore ,
> > > I
> > > > have
> > > > > two
> > > > > > different clusters one 4.x cluster and one 6.x cluster , We are
> > > not
> > > > > using
> > > > > > the backup of 4.x on 6.x, I build a new 6.x system and did a new
> > > > > install on
> > > > > > it, Now we are taking down the 4.x system and want to migrate
> > > all
> > > > > phones on
> > > > > > it to 6.x. How do I get this file as I am not doing a windows
> > > > upgrade
> > > > > for
> > > > > > 6.x. I extracted the tar file which DMA generates , i could not
> > > > find
> > > > > any
> > > > > > license xml fle.Hope I am clear.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Aman
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 3/6/08, James Buchanan <jbuchanan at ctiusa.com> wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > FYI...it fails because the first one or two lines of the XML
> > > are
> > > > > > > actually not XML. Omit those lines in the copy, and all should
> > > be
> > > > > well.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > James
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: cisco-voip-bounces at puck.nether.net
> > > > > > > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> > > Jonathan
> > > > > > > Charles
> > > > > > > Sent: Thursday, March 06, 2008 8:07 AM
> > > > > > > To: Justin Steinberg
> > > > > > > Cc: Cisco Voip List
> > > > > > > Subject: Re: [cisco-voip] callmanager license migration from
> > > 4.x
> > > > to
> > > > > 6.x
> > > > > > >
> > > > > > > Just a quick note...
> > > > > > >
> > > > > > > The last four times I have done this, it has failed and said,
> > > > > 'invalid
> > > > > > > XML file'... I then sent it to licensing at cisco.com and got a
> > > > license
> > > > > > > in a few hours... no biggie... but expect it to fail...
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > JOnathan
> > > > > > >
> > > > > > > On Thu, Mar 6, 2008 at 6:51 AM, Justin Steinberg
> > > > > <jsteinberg at gmail.com>
> > > > > > > wrote:
> > > > > > > > on the new cm6 system, login to ccmadmin goto
> > > > > system>licensing>license
> > > > > > > file
> > > > > > > > upload. You can download the xml file there and then you
> > > will
> > > > > need to
> > > > > > > > upload that file to cisco's website and they will then email
> > > > you a
> > > > > > > permanent
> > > > > > > > xml license file.
> > > > > > > >
> > > > > > > > The above process will give you:
> > > > > > > > 1) DLU's for your system
> > > > > > > > 2) CM node licenses
> > > > > > > >
> > > > > > > > However, you will need to use the PUT to order a CM4to6
> > > upgrade
> > > > > and
> > > > > > > they
> > > > > > > > will ship you a PAK that you can use to license the CM6
> > > feature
> > > > > > > license.
> > > > > > > > Without this feature license the CM service will not start.
> > > > > > > >
> > > > > > > > Justin
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Mar 6, 2008 at 5:36 AM, Aman Chugh
> > > > <aman.chugh at gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I need some help with this, I am migrating licenses from
> > > ccm
> > > > 4.x
> > > > > to
> > > > > > > 6.x, I
> > > > > > > > have ran DMA and I am looking for the intermediary license
> > > file
> > > > > which
> > > > > > > all
> > > > > > > > the documents talk about, I am not doing a complete restore
> > > of
> > > > 4.x
> > > > > on
> > > > > > > 6 .x ,
> > > > > > > > I just need licenses to be migrated from the old system to
> > > the
> > > > new
> > > > > > > one. I
> > > > > > > > have looked at tar file which DMA creates but can't find
> > > that
> > > > xml
> > > > > file
> > > > > > > > needed for new license generation.
> > > > > > > > >
> > > > > > > > > TIA
> > > > > > > > >
> > > > > > > > > Aman
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > cisco-voip mailing list
> > > > > > > > > cisco-voip at puck.nether.net
> > > > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > cisco-voip mailing list
> > > > > > > > cisco-voip at puck.nether.net
> > > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > >
> > > > > > > >
> > > > > > > _______________________________________________
> > > > > > > cisco-voip mailing list
> > > > > > > cisco-voip at puck.nether.net
> > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > > _______________________________________________
> > > > > > > cisco-voip mailing list
> > > > > > > cisco-voip at puck.nether.net
> > > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > cisco-voip mailing list
> > > > > > cisco-voip at puck.nether.net
> > > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > cisco-voip mailing list
> > > > > cisco-voip at puck.nether.net
> > > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > >
> > > > >
> > > > > This message and any attachments are intended only for the use of
> > > the
> > > > addressee and may contain information that is privileged and
> > > > confidential. If the reader of the message is not the intended
> > > recipient
> > > > or an authorized representative of the intended recipient, you are
> > > > hereby notified that any dissemination of this communication is
> > > strictly
> > > > prohibited. If you have received this communication in error, please
> > > > notify us immediately by e-mail and delete the message and any
> > > > attachments from your system.
> > > > >
> > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > > > CONFIDENTIALITY STATEMENT
> > > > This communication and any attachments are CONFIDENTIAL and may
> > > > be protected by one or more legal privileges. It is intended
> > > > solely for the use of the addressee identified above. If you
> > > > are not the intended recipient, any use, disclosure, copying
> > > > or distribution of this communication is UNAUTHORIZED. Neither
> > > > this information block, the typed name of the sender, nor
> > > > anything else in this message is intended to constitute an
> > > > electronic signature unless a specific statement to the
> > > > contrary is included in this message. If you have received this
> > > > communication in error, please immediately contact me and delete
> > > > this communication from your computer. Thank you.
> > > >
> > > CONFIDENTIALITY STATEMENT
> > > This communication and any attachments are CONFIDENTIAL and may
> > > be protected by one or more legal privileges. It is intended
> > > solely for the use of the addressee identified above. If you
> > > are not the intended recipient, any use, disclosure, copying
> > > or distribution of this communication is UNAUTHORIZED. Neither
> > > this information block, the typed name of the sender, nor
> > > anything else in this message is intended to constitute an
> > > electronic signature unless a specific statement to the
> > > contrary is included in this message. If you have received this
> > > communication in error, please immediately contact me and delete
> > > this communication from your computer. Thank you.
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------------------------------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080307/2467492d/attachment-0001.html
More information about the cisco-voip
mailing list