# Application Group Licensing Example

Group Licensing allows you to move licenses from one MiVoice Business system to another within the license sharing group (called an "application group") without having to make changes to the individual application records on the AMC.

The process to set up group licensing in a new installation involves the following tasks:

On the AMC

1. Create application records for all the MiVoice Business systems containing the licenses which will be shared among the application group.

2. Create a group licensing application record which the designated license manager will use to share the licenses out to the group members.

On the MiVoice Business system

3. Configure MiVoice Business to talk to the AMC. (Not applicable to Container-based MiVoice Business (cMiVB))

4. Define the network elements which will be sharing licenses (i.e., the application group).

5. Retrieve the licenses on each MiVoice Business system in the group. (Not applicable to Container-based MiVoice Business (cMiVB))

6. Start sharing.

7. Configure the Designated License Manager (DLM).

8. Sync the group licenses to all the group members.

For instructions, on migrating an existing system to use licensing sharing, see "Upgrade to MCD 5.0 and Group Licensing" in the Software Installation chapter of the 3300 ICP Technician's Handbook.

## Configure the AMC

Tasks:

1. Create Purchase Order.

2. Create Group and MiVoice Business Application Records (GARIDs and ARIDs).

3. Assign products to Application Records.

4. Configure MiVoice Business Application Records.

5. Configure Group Application Record.

### 1) Create Purchase Order

Create one purchase order containing:

- One single Enterprise Sharing License.

- Multiple Enterprise Base Bundles, one for each MiVoice Business system which will share licenses.

- Additional licenses which will be shared out to the group members.

For a 3-node group, the total purchases might be as follows:

- 1 x Enterprise License Sharing

- 60 x HTML Application License (50 pack)

- 300 x MiVoice Business Enterprise Multi-device User License

- 1 x MiVoice Business IDS Connection License

This allows for the provisioning of 1000 users per MiVoice Business system, a number of standard enterprise features, HTML application licenses for 3000 phones, 100 multi-device user licenses per MiVoice Business system, and an IDS connection point license.

### 2) Create Application Records

Create one application record for the DLM and one application record for each MiVoice Business system in the license sharing group.

### 3) Assign Products to Application Records

Next, assign the Enterprise License Sharing license and all the additional product licenses to one of the application records (it becomes a Group Application record at this point), and then assign the base bundles to the MiVoice Business application records.

### 4) Configure MiVoice Business Application Records

Set the software version of the MiVoice Business application record to MCD 5.0 (Figure 1).

Figure 1: Set Software Version in MiVoice Business ARID

### 5) Configure Group Application Record

Having set the software version in the MiVoice Business application records, the next step is set up the group application record. To do this, select ‘Setup ?’ in the application record (Figure 2).

Figure 2: Set up the DLM

AMC setup is almost complete. The remaining task is to select the MiVoice Business application records and add them to the application group (Figure 3).

For the MiVoice Business application record to be selectable, the MiVoice Business software version must be set to MCD 5.0 (see previous).

Figure 3: Add MiVoice Business systems to GARID

Note that any additional licenses which were assigned to the MiVoice Business application records (beyond the base bundle) will be transferred to the group application record. This operation could take some time.

AMC setup is now complete except for one piece of information: the identity of the DLM (Figure 4), which is part of the MiVoice Business configuration process described below.

Figure 4: Application Records

## Configure MiVoice Business

Tasks:

1. For each MiVoice Business system,

a) Configure the customer's DNS server address to allow the system to access the internet and hence the AMC.

b) Enter Network Element Names

c) Download License Base Bundle

2. Create SDS Network.

3. Start Sharing.

4. Download Group Application Record and Designate the DLM.

5. Distribute Group Licenses to group.

6. Allocate licenses to the group nodes.

7. View distributed licenses.

### 1a) Tell MiVoice Business about AMC

MiVoice Business needs to access the internet to get to the AMC and download its licenses. This is done on each MiVoice Business system's Server Console. (Figure 5).

Figure 5: Configure MiVoice Business to talk to the AMC

### 1b) Set Network Element Names

DLM uses SDS to share licenses with the application group. To set up sharing, start by entering the local network element name. This is done on each MiVoice Business system.

Figure 6: Set the Network Element Names

### 1c) Activate Licenses

NOTE: This step is not applicable to Container-based MiVoice Business (cMiVB).

Next, download the base bundles licenses.

This is done on each MiVoice Business system's Server Manager.

Log in to the Server Manager (ServiceLink > Status) to activate the ServiceLink. In the Service account ID field, enter the Application Record ID of the MiVoice Business Application Record (the one containing the base bundle).

Be careful not to specify the Group Application Record ID here by mistake.

Click Activate.

The Available for Allocation column should be 0 and the License Sharing should say Yes. If it doesn't, revisit the previous sections and make sure nothing was missed.

### 2) Create the SDS Network

As mentioned, the DLM uses SDS to share licenses with the application group. To share, there must be an SDS network with the DLM and the other group members part of it.

To create the SDS network, log into one of the MiVoice Business systems and tell it about the others in the group. It doesn’t matter which system, but it's simpler if it's the DLM. The DLM is the system that will get the group licenses from AMC and distribute them to the other systems in the group. It can be any of the group members. Designating the DLM is done after sharing is set up.

In the Network Element form, enter the network element name and IP address of all the other MiVoice Business systems in the group (Figure 7).

Figure 7: Add the other MiVoice Business systems

### 3) Start Sharing

Now, start sharing. Select all the other MiVoice Business systems and click Start Sharing.

MiVoice Business will confirm that the IP addresses are correct and that the MiVoice Business systems at those IP addresses have the same local network name entered earlier.

Any issues that arise at this point (incorrect IP address, incorrect network element name, remote MiVoice Business system is already sharing with other MiVoice Business systems, etc.) need to resolve at this point.

### 4) Download Group License Data and Designate the DLM

It's time to download the Group License Data and designate the DLM.

From the (soon-to-be-designated) DLM, navigate to the Application Group Licensing form. (Figure 8)

Select 'Yes'and enter the GARID.

Click Save.

Figure 8: Designate DLM and Configure GARID

Confirm that the group licensing data from the Group Application Record has been successfully downloaded to the DLM. (Figure 9.)

Figure 9: Review Group Licenses

### 5) Distribute Group Licenses

Next, we distribute the group license data to the other nodes in the application group.

Return to the Network Elements form (still on the DLM)

Select all the other nodes, and then click the Sync button

Choose to sync the Application Group Licensing data. (Figure 10)

Figure 10: Sync Group Licensing to Group

### 6) Allocate Local Licenses

With the group licenses distributed to all the nodes the application group, the next task is to allocate local licenses from the group license pool.

This is done on each node using Application Reach Through.

Navigate to the License and Option Selection form on the first node.

Notice the pool of licenses in the ‘Available for Allocation’ column. (Figure 11).

For each option, we enter the number of licenses that the first node requires.

Once the local license allocations have been applied and the node rebooted (if prompted to do so), reach through to the other nodes to allocate their licenses. Finish by issuing the ‘RESET SYSTEM’ maintenance command to reboot the node if prompted.

Figure 11: Allocate Local Licenses

### 7) View Distributed Licenses

Finally, we can view the distributed licenses to confirm that everything is in order.

From the DLM, navigate to Application Group License form.

If there are any license violations (over-provisioning of service, expired try-before-buy licenses, etc.) this will be shown as well as the total amount of licenses purchased for the group, and the amount allocated and consumed by each group member.

To get more information about a license violation, issue the ‘LICENSING STATUS’ maintenance command.

## Adding a new MiVoice Business system into an existing group

Following the procedures above as follows:

1. Create a new ARID and assign a new base bundle to it.

- Set the ARID Software Version to MCD 5.0.

2. Add additional optional items to the GARID.

3. Edit the GARID to add the ARID created above.

- Note that the Setup? link is now the GARID number.

4. Configure the new MiVoice Business system as described above.

5. System IP Properties – Add AMC IP in DNS.

6. Set local Network Element name.

7. Retrieve licenses from base bundle ARID.

5. On the DLM, add the new MiVoice Business system into the Network Element List.

6. Start sharing with the new MiVoice Business system.

7. Reload the Group licenses by clicking Change and Save in the Application Group Licensing form (do not change any of the data).

8. Sync the Application Group Licensing to the new MiVoice Business system.

9. Assign licenses locally on the new MiVoice Business system.

10. Reboot the new MiVoice Business system if prompted.

Related Topics

- License Violation Handling

- About IP User and Device Licenses

- Change Licenses and Options

- Change Resource Dimensions

- Decommissioning a DLM