License Manager

The license manager acts as a broker between CUCM applications that use licensing information and the license server. The license manager receives requests from the CUCM applications and forwards the requests to the license server. The license manager then responds back to the application after the request has been processed by the license server. The license manager acts a licensing proxy server.

An administration subsystem and alarm subsystem complete the functional diagram. Details of these two subsystems are as follows:

■ The administration subsystem provides the following capabilities:

—Keeps information about the license units required for each phone type. The customer can view this information using a GUI.

—Supports a GUI tool that calculates the required number of phone unit licenses. The customer inputs phone types and the number of phones of each type that the customer wants to purchase. The output is the total number of licenses that the customer needs for the given configuration.

—Supports a GUI tool that displays the total license capacity and the number of licenses in use and license file details. The tool can also report the number of available licenses.

■ The alarm subsystem generates alarms that are routed to event logs or sent to a management station as Simple Network Management Protocol (SNMP) traps to notify the administrator of the following conditions:

—Overdraft: Occurs when an overdraft condition exists. An overdraft condition occurs when more licenses are used than available but the amount of exceeding licenses is in an acceptable range. (5 percent overdraft is permitted.)

—License server down: Occurs when the License Manager cannot reach the license server.

—Insufficient licenses: Occurs when the license server detects the fact that there are not sufficient licenses to fulfill the request and raises an alarm to notify the administrator.

Issues with the license file occur when there is a version mismatch between the license file and the CUCM (license file version mismatch alarm), or when the number of licenses in the license file is less than the number of phones provisioned (license file insufficient licenses alarm). Another cause of this condition is an invalid MAC address (for instance, after a NIC change).

Figure 1-9 is a functional diagram stepping through the process of a license request, as described in the list that follows:

1. A request for a certain number of DLUs is made by the admin subsystem because of an event (for example, phone registration).

2. The License Manager service on a CUCM subscriber forwards the request to the publisher server running the License Server service.

3. The License Server service receives the license request event and allocates the required number of DLUs required based on the type of device. If not enough license units are available to accommodate the request, a deny message is sent back to the license manager on the subscriber server. If resources are available, the license server grants the request and sends a grant message to the license manager on the subscriber server.

4. The License Manager service on the subscriber server receives the license grant or deny message and allows the phone to register.

5. If the license request was denied, the subscriber server generates an alarm in the alarm subsystem. The deny message will be available in the CUCM syslog server by default.

Figure 1-9 Licensing Functional Diagram

Figure 1-9 Licensing Functional Diagram

Continue reading here: Calculating License Units

Was this article helpful?

+1 0