[cisco-voip] Impact upon licensing in lab environment

Jeffrey Girard jeffrey.girard at girardinc.com
Wed Feb 12 17:01:58 EST 2014 

Ryan -
          What you say is interesting because it contradicts what the guy on my license TAC case specifically told me (I can provide you his name in a private email if you wish)

          "Note that the licensing is tied to the eth0 mac address so if your ELM is a VM be sure it has a static mac address."

               I specifically asked him this question and was told that starting with 9, the licensing was no longer tied to a MAC but only to a random set of characters generated by the ELM when you do the license request.

               That will be important to know which is true so that I can tell the client the correct information.

               It seems as if the dedicated ELM is the correct way to go - but Im not sure if the client wants to dedicate the HW/VM to building one.  They are constantly changing the architecture (it's a true lab)

------------------------------------------------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Colonel, United States Army (Retired)
Senior Network Engineer / VoIP Engineer - WireMeHappy.com
reply to: jeffrey.girard at wiremehappy.com<mailto:jeffrey.girard at wiremehappy.com>
(607)835-0406 (home office)
(845)764-1661 (mobile)
(607)835-0458 (fax)

From: Ryan Ratliff (rratliff) [mailto:rratliff at cisco.com]
Sent: Wednesday, February 12, 2014 4:52 PM
To: Matthew Loraditch
Cc: Jeffrey Girard; cisco-voip voyp list
Subject: Re: [cisco-voip] Impact upon licensing in lab environment

I agree with Matthew, if you are spinning up lab clusters or moving things around go with a dedicated ELM/PLM.  Note that the licensing is tied to the eth0 mac address so if your ELM is a VM be sure it has a static mac address.

There are no node licenses, so you can add multiple cluster to the same ELM and they will only consume licenses based on the number of configured users and devices.

You don't want to be rebuilding or migrating the ELM anywhere.  If you don't have to do that then there will never be a need to rehost a license going forward.

-Ryan

On Feb 12, 2014, at 11:53 AM, Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:

Subs don't talk to ELM. Only the Pub talks.
You then have two possible setups, dedicated ELM/PLM and Colocated ELM/PLM with CUCM or Unity Connection.
You also have one other scenario, rebuilding the Pub that you've mentioned.
If you have the VM Resources considering all the changes you are talking about I suggest a dedicated ELM/PLM server. You can use the smallest sized CUCM OVA for this.

The following possibilities exist with moving/rebuilding:
Rebuild collocated ELM/PLM and CUCM - You will have to rehost your ELM/PLM with TAC, you will also have to add the new Pub to ELM/PLM.
Rebuild Dedicated Pub when having dedicated ELM/PLM. Just add the new Pub to ELM/PLM and delete. TAC not involved.
Rebuild ELM/PLM Dedicated Instance - You will have to rehost your ELM/PLM with TAC, you will also have to add the existing Pub to ELM/PLM
Migration of any servers -Migrating a shutdown instance of a VM using the Migrate function should cause no licensing changes as all hardware properties are kept the same.
If you do a copy of the VM via VMWare that is not the case some hardware properties can change and this may cause ELM/PLM to need a rehost.   A manual copy may work. I haven't tried it.

I think I've addressed all of your scenarios, let me know if you need clarification.




Matthew G. Loraditch - CCNP-Voice, CCNA-R&S, CCDA
1965 Greenspring Drive
Timonium, MD 21093

direct voice. 443.541.1518
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>
Support Phone. 410.252.8830


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeffrey Girard
Sent: Wednesday, February 12, 2014 11:01 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Impact upon licensing in lab environment


Greetings all -

          My client recently purchased 2 x PAKs for CUCM servers.  They have several physical host machines configured with ESX5.

          My understanding of the difference with CUCM 9 is the ELM.  Licenses are no longer tied to the MAC but are tied to some random characters generated by the ELM during the license file upload process.

This is a lab environment so I want to be sure that I am advising them correctly on the impacts of the following actions:

          Assuming that both PAKs are registered to the single ELM (currently they have a Pub and Sub - each of them running inside ESX 5 on the separate physical host machines)

          1 - what would be the impact if the SUB VM were physically migrated (via copying and moving ova file) to the physical machine hosting the Pub?  My gut tells me no impact

          2 - what would be the impact if the CUCM pub and ELM (co-existing on the Pub) were physically moved (via copying and moving ova file) to the physical machine hosting the Sub?  My gut tells me no impact.

          3 - what would be the impact if the Sub were decommissioned and rebuilt as a Pub in a new cluster?  My gut tells me that it would take TAC involvement to rehost the license

          4 - what would be the impact if the Pub were decommissioned and rebuilt as a Pub in a new lab configuration?  My gut tells me that it would also take TAC involvement to rehost the license
------------------------------------------------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Colonel, United States Army (Retired)
Senior Network Engineer / VoIP Engineer - WireMeHappy.com<http://WireMeHappy.com>
reply to: jeffrey.girard at wiremehappy.com<mailto:jeffrey.girard at wiremehappy.com>
(607)835-0406 (home office)
(845)764-1661 (mobile)
(607)835-0458 (fax)
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20140212/51c1343d/attachment.html>

More information about the cisco-voip mailing list