Platform Blueprint Examples

The following examples demonstrate basic and advanced resilient telephony setups.

Basic resilient telephony using MiVoice Business Multi-Instance

This example illustrates how to create a blueprint that specifies a pair of MiVoice Business Multi-Instance tenants across two data centers in a resilient configuration. Telephones in the new system will connect to a MiVoice Business on the East coast and will have a stand-by MiVoice Business instance on the West coast.

Prerequisites

  • Two MiVoice Business Multi-Instance server pools (in this example, pool-east and pool-west). When creating a blueprint, the pools can be empty.

  • A MiVoice Business golden database file with configuration suitable for a primary role

  • A MiVoice Business golden database file with configuration suitable for a secondary role (for fail-over)

  • A MiVoice Business software image file

To set up basic resilient system based on MiVoice Business Multi Instance:

  1. Navigate to Platform Manager > Configuration > Files. Upload a MiVoice Business image and the two golden databases to the file server.

  2. Under Blueprints > ARID Blueprints, click Create ARID Blueprint.

  3. In Type, select MiVB-MI.

  4. Add AMC part numbers including a Base part and 50 user parts.

  5. Set ARID Blueprint Name to MiVB-MI_tenant_50_user.

  6. Click Submit.

  7. Under Blueprints > Resource Blueprints, click Create Resource Blueprint. Enter the following information:

    1. In Resource Blueprint Name, enter a descriptive name for the blueprint.

    2. In Type, select MiVB-MI.

    3. In Tenant name, enter Primary.

    4. In MiVB Software Image File Name, select the image file that you uploaded to the File Server.

    5. In MiVoice Business Database Backup file, select the golden database that you uploaded for the primary controller.

    6. In ESM (System Administration Tool) username, enter the user name for access to the primary MiVoice Business.

    7. In ESM (System Administration Tool) password, enter the password for access to the primary MiVoice Business.

    8. In MiVB-MI Server pool, enter the name of the pool. For this example, enter "pool-east".

    9. For all other fields, leave the default values.

    10. Click Submit. This blueprint is now ready for inclusion in a platform blueprint.

  8. Under Blueprints > Resource Blueprints, create another resource blueprint for use in creating the secondary controller.

    1. In Tenant name, enter Secondary.

    2. In MiVB Database Backup File Name, select the golden database you uploaded for secondary controllers.

    3. Select an MiVB-MI pool. For this example, select pool-west.

  9. Under Blueprints > Platform Blueprints, create a Platform blueprint. Enter the following:

    1. In Platform Blueprint Name, enter Basic Resilient East 50.

    2. In Description, enter 2xMiVoice Business 50 user, East primary.

    3. Add the primary resource. Under Resource Details, set Type to MiVB-MI

    4. In Resource Blueprint, select the primary blueprint created in an earlier step.

    5. In ARID Blueprint, select MiVB-MI_tenant_50_user (created in an earlier step).

    6. In DLM, select No.

    7. In SDS Role, select Master.

    8. In Role Label, (Optional) add a brief description of the role of this MiVoice Business in the system.

    9. Add the secondary resource. Under Resource Details, set Resource Type to MiVB-MI.

    10. In Resource Blueprint, select the Secondary blueprint that you created above.

    11. ARID Blueprint: Select the same blueprint that you used in the previous resource: MiVB-MI_tenant_50_user.

    12. In DLM, select No.

    13. In SDS Role, select Slave.

    14. (Optional) In Role Label, add a brief description of the role of this MiVoice Business in the system.

    15. Click the green plus images/ottjira01.mitel.com/wiki/s/en_GB/7109/fbbcac5a2a6382e2f6a78d491af75161a7840bc8/_/images/icons/emoticons/add.png to add the resource.

    16. Under AMC Group Parts, make no changes.

    17. There is no DLM, and since there is no MiCollab, ULM parts are not needed.

    18. In Blueprint Options, select Cluster.

    19. Click Submit. The platform blueprint is created.

  10. Build a test instance to verify that the system works as intended.

    1. Confirm that you have sufficient AMC License Bank parts and MiVoice Business Multi-Instance tenants available. See Platform Manager Configuration > AMC Account and Configuration > MiVB-MI Pools to check license availability and resource usage.

    2. Under Platform Groups, click Create Platform Group.

    3. Enter a name for the test instance. When creating a MiVoice Business Express Platform Group, this Name is also added to the Annotations > Notes field for the MiVoice Business Express virtual machine.

    4. Select the Platform Blueprint that you want to build.

    5. Click Submit.

  11. On the Platform Groups page, you can monitor your instance build. When the operation state changes to SUCCESS, the instance is ready to use. You can drill down on the Platform group ID to see detailed information and logs for this instance.

Advanced resilient telephony

Note

This example applies only for the MiVB-MI blueprint types.

This example expands upon the Basic Resilient Telephony example above to create an example with MiCollab and ULMv3 group parts.

We want a blueprint similar to "Basic Resilient East 50" but with a different ARID blueprint, a MiCollab, and UCC-type AMC group parts.

Prerequisites:

  • Use the same prerequisites as in the Basic example.

  • A MiCollab Multi-Tenant pool. For this example, assume the pool is called "pool-micollab".

Advanced resilient telephony example:

  1. Navigate to Platform Manager > Configuration > Files, upload a MiVoice Business image and the two golden databases to a file server.

  2. Under Blueprints > ARID Blueprints, click Create ARID Blueprint.

  3. In Type, select MiVB-MI.

  4. Set ARID Blueprint Name to MiVB-MI_tenant_base.

  5. Click Submit.

  6. Use the resources you created in the last example.

  7. Under Blueprints > Platform Blueprint, create a platform blueprint. Enter the following information:

    1. Set Platform Blueprint Name to MiCollab Resilient East 50.

    2. In Description, enter MiCollab, 2xMiVoice Business, 50 user, East primary, for example.

    3. Under Resource Details, add the primary resource. Enter the following Type, select MiVB-MI.

    4. Select a resource blueprint that was created for a primary controller.

    5. Select an ARID blueprint: MiVB-MI_tenant_base (created in the earlier example).

    6. In DLM, select No.

    7. In SDS Role, select Master.

    8. In Role Label, (Optional) add a brief description of the role of this MiVoice Business in the system.

    9. Click the green plus images/ottjira01.mitel.com/wiki/s/en_GB/7109/fbbcac5a2a6382e2f6a78d491af75161a7840bc8/_/images/icons/emoticons/add.png to add the resource.

    10. Under Resource Details, add the secondary resource. Enter the following:

    11. In Type, select MiVB-MI.
      In Resource Blueprint, select the blueprint created for the secondary controller in the previous example.
      In ARID Blueprint, select MiVB-MI_tenant_base, the resource that you used in the previous example.
      In DLM, select No.
      In SDS Role, select Slave.
      (Optional) In Role Label, add a brief description of the role of this MiVoice Business.

    12. Click the green plus images/ottjira01.mitel.com/wiki/s/en_GB/7109/fbbcac5a2a6382e2f6a78d491af75161a7840bc8/_/images/icons/emoticons/add.png to add the resource.

    13. Under AMC Group Parts add an AMC part for the MiCollab. Enter 54006116 (SP Subscript Licnse-UCCv3Basic Users x50).

    14. In Is Part DLM, select No.

    15. Click the green plus images/ottjira01.mitel.com/wiki/s/en_GB/7109/fbbcac5a2a6382e2f6a78d491af75161a7840bc8/_/images/icons/emoticons/add.png to add the part. Under Blueprint Options:
      Select Create Cluster.
      Select pool-micollab.

    16. Click Submit.

  8. Build a test instance to verify that the system works as intended.

Basic telephony using MiVoice Business Express

This very basic example illustrates how to create a blueprint that specifies setup of a MiVoice Business Express System. This example relies on most of the defaults built into Platform Manager.

If you want to make a resilient MiVoice Business Express-based network, you can add another MiVoice Business Virtual after you have finished the MiVoice Business Express setup using Platform Manager.
Prerequisites

  • A VMware infrastructure server pool. When creating a blueprint, the pool can be empty.

  • A MiVoice Business golden database file with configuration.

  • A MiVoice Business software OVA file.

  • Optional: VMware IP address pool assigned to the Virtual Machine (VM). If the IP addresses are not supplied here, they can be set up during deployment of the Blueprint.

A virtual machine (VM) must be network reachable from the Platform Manager. By default, MSL-based machines are only reachable via their local network. If Platform Manager server is not on the same network as the VM, Platform Manager will fail to configure the VM. To fix this, configure a Remote Network that includes the Platform Manager network. The Remote Network property is on the MiVB-X resource blueprint page, under OVA Settings. The Mitel MiVoice Business Express OVA is configured with a local networks of 10.0.0.0/8

Basic MiVoice Business Express telephony example

There are many parameters that you can set up to create an MIVB-X Resource Blueprint, and only the basics are described here. In many cases, Platform Manager attempts to set suitable values, but you should examine each item carefully to ascertain which parameters you should customize for your application.

  1. Navigate to Platform Manager > Configuration > Files. Upload an MSL backup / golden database to a file server.

  2. Under Blueprints > ARID Blueprints, click Create ARID Blueprint. Enter the following information:

    1. In ARID Blueprint Name, enter MiVB-X-sample.

    2. In Type, select MiVB-X.

    3. Add AMC part numbers; for example: 54005931 - SP Subscript Base-MiVoiceBus Express Virt. The licensing parts must be compatible with the licensing of the golden MSL database.

    4. Click Submit.

  3. Under Blueprints > Resource Blueprints, click Create Resource Blueprint. Enter the following information:

    1. In Resource Blueprint Name, enter a descriptive name for the new blueprint.

    2. In Type, select MiVB-X.

    3. In MSL Database Backup File Name, select the golden MSL database.

    4. In ESM (System Administration Tool) username, enter the user name for access to the MSL database.

    5. In ESM (System Administration Tool) password, enter the password for access to the MSL database.

    6. In OVA Image File Name, select the OVA file that you uploaded to the File Server. The MiVoice Business Express OVA is available from Mitel.

    7. In Infrastructure, specify the VMware infrastructure to create the resources.

    8. Click Submit. This blueprint is now ready for inclusion in a platform blueprint.

  4. Under Blueprints > Platform Blueprints, create a Platform blueprint. Enter the following:

    1. In Platform Blueprint Name, enter MiVB-X-sample.

    2. In Description, enter MiVB-X_SMB_deploy.

    3. Add the resource. Under Resource Details, set Resource Type to MiVB-X.

    4. In Resource Blueprint, select the blueprint created earlier.

    5. In ARID Blueprint, select MiVB-X-sample.

    6. In DLM, select No.

    7. In Role Label, (Optional) add a brief description of the role of this MiVoice Business in the system.

    8. Under AMC Group Parts, make no changes.

    9. Click Submit. The platform blueprint is created.

To build a test instance:
Verify that the Blueprint works as intended.

  1. Confirm that you have sufficient AMC License Bank parts and MiVoice Business Multi-Instance tenants available. See Platform Manager Configuration > AMC Account and Configuration > MiVB-MI Pools to check license availability and resource usage.

  2. Under Platform Groups click Create Platform Group.

  3. Enter a name for the test instance.

  4. Select the Platform Blueprint that you want to build.

  5. Add Group User license parts.

  6. Click Submit.

On the Platform Groups page, you can monitor your instance build. When the operation state changes to SUCCESS, the instance is ready to use. You can drill down on the Platform group ID to see detailed information and logs for this instance.