08-04-2014 07:50 AM - edited 03-16-2019 11:37 PM
My CUCM and my CUC both have ELM installed. Not sure if that's the default or not as I did not run the initial installers. Is it best practice to keep the licenses on 1 ELM or 2? If just one is there a way to uninstall ELM from the other appliance?
Solved! Go to Solution.
08-04-2014 08:58 AM
Hi Todd,
I'll just add this reference to the good tips from "Z" (+5)
You have many options here for ELM......if you do decide to install on a separate server the OVA can be based on the smallest CUCM OVA as shown below from the 9.x SRND;
ELM is installed automatically on the same dedicated server or virtual machine as the Unified CM, SME, and Unity Connection installations. You may choose to use the ELM on one of these servers in a co-resident configuration, as the active managing ELM, or you may opt to run ELM in a standalone configuration where ELM is installed on a dedicated server or virtual machine.
In the co-resident configuration, ELM consumes only a very small amount of resources and hence is considered to have no impact to server or virtual machine sizing. For example, no additional vCPUs would need to be added to the virtual machine configuration because of the ELM service. In the co-resident configuration, ELM resides on the same dedicated server or virtual machine that is sized appropriately for that application.
In a standalone configuration the ELM resides on a separate server or virtual machine created and managed specifically for, or dedicated to, the ELM application. In the standalone configuration, the ELM is sized to the equivalent minimum-sized resource for that application.
The main considerations for choosing between co-resident and standalone deployments center around administration and management. The main benefits of deploying ELM in a standalone configuration are as follows:
The trade-off, however, with a standalone configuration is that it requires a separate server or virtual machine to be created and managed.
– Run ELM on a separate virtual machine or server. This approach provides more administration and management flexibility but requires a separate virtual machine or server for ELM.
– Run a different ELM on each application server if you do not need license pooling and do not desire centralized license management.
– Run a single ELM co-resident with one application server if you want license pooling and/or centralized management, but you are unwilling to dedicate a virtual machine or server for running the ELM.
The ELM may be deployed in any of the following ways:
As the description implies, one ELM instance can support an entire enterprise or global deployment. This model provides the most simplicity by utilizing one common centralized license pool for all the Unified Communications applications subscribing to the ELM.
For an enterprise that has multiple Unified Communications deployments across the globe, multiple ELM instances can be configured per region or lines of business (for example, one for North America, a second for EMEA, and a third for APAC). This model enables an enterprise to account more easily for the costs of licenses across differing fiscal boundaries.
For those customers requiring even more granularity, an ELM instance can be configured for each Unified Communications application. For example, if a customer has three Cisco Unified CM clusters, three ELM instances can be configured. This scenario is useful for customers who operate along more granular accounting lines and prefer multiple smaller license pools in order to better manage operating costs and other expenses.
From;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab09/clb09/callpros.html#pgfId-1347951
Cheers!
Rob
08-04-2014 08:08 AM
Use a single ELM and the co-resident application installation is installed by default and as far as I know cannot be removed. Most people use the ELM that is installed with CUCM if they have both CUCM and CUC. If you are running multiple clusters, and technically multiple apps, Cisco recommends a dedicated server running ELM.
08-04-2014 08:45 AM
I just saw that its recommended to run a seperate ELM. can i do it based on 2500 user template? or does the template need to be based off the CUCM template?
And is the seperate ELM really needed? we did the 10k user template for CUCM.
08-04-2014 08:58 AM
Hi Todd,
I'll just add this reference to the good tips from "Z" (+5)
You have many options here for ELM......if you do decide to install on a separate server the OVA can be based on the smallest CUCM OVA as shown below from the 9.x SRND;
ELM is installed automatically on the same dedicated server or virtual machine as the Unified CM, SME, and Unity Connection installations. You may choose to use the ELM on one of these servers in a co-resident configuration, as the active managing ELM, or you may opt to run ELM in a standalone configuration where ELM is installed on a dedicated server or virtual machine.
In the co-resident configuration, ELM consumes only a very small amount of resources and hence is considered to have no impact to server or virtual machine sizing. For example, no additional vCPUs would need to be added to the virtual machine configuration because of the ELM service. In the co-resident configuration, ELM resides on the same dedicated server or virtual machine that is sized appropriately for that application.
In a standalone configuration the ELM resides on a separate server or virtual machine created and managed specifically for, or dedicated to, the ELM application. In the standalone configuration, the ELM is sized to the equivalent minimum-sized resource for that application.
The main considerations for choosing between co-resident and standalone deployments center around administration and management. The main benefits of deploying ELM in a standalone configuration are as follows:
The trade-off, however, with a standalone configuration is that it requires a separate server or virtual machine to be created and managed.
– Run ELM on a separate virtual machine or server. This approach provides more administration and management flexibility but requires a separate virtual machine or server for ELM.
– Run a different ELM on each application server if you do not need license pooling and do not desire centralized license management.
– Run a single ELM co-resident with one application server if you want license pooling and/or centralized management, but you are unwilling to dedicate a virtual machine or server for running the ELM.
The ELM may be deployed in any of the following ways:
As the description implies, one ELM instance can support an entire enterprise or global deployment. This model provides the most simplicity by utilizing one common centralized license pool for all the Unified Communications applications subscribing to the ELM.
For an enterprise that has multiple Unified Communications deployments across the globe, multiple ELM instances can be configured per region or lines of business (for example, one for North America, a second for EMEA, and a third for APAC). This model enables an enterprise to account more easily for the costs of licenses across differing fiscal boundaries.
For those customers requiring even more granularity, an ELM instance can be configured for each Unified Communications application. For example, if a customer has three Cisco Unified CM clusters, three ELM instances can be configured. This scenario is useful for customers who operate along more granular accounting lines and prefer multiple smaller license pools in order to better manage operating costs and other expenses.
From;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab09/clb09/callpros.html#pgfId-1347951
Cheers!
Rob
08-04-2014 09:02 AM
So based on that i need a separate server for the ELM. Boy Cisco sure likes to make this difficult. thanks guys!
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