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