Abbreviations used in the Platform Manager user interface include:
• | MiVB – MiVoice Business |
• | MiVB-MI – MiVoice Business Multi Instance |
• | MiCollab-MT – MiCollab Multi-tenant |
• | MiVB-X - MiVoice Business Express |
Note: You can install Platform Manager and File Server on the same server. You cannot install Platform manager and File Server on the server on which Oria is installed.
Here are the basic steps to setting up Platform Manager and File Server, create blueprints, configure Oria, and create platform instances.
1. On each MiVoice Business Multi Instance server, create a network pool of IP addresses suitable for instances on that server. For each sysip address in the pool, you start a Media Server instance pointing to the MiVoice Business instance IP address. The following example creates 214 address records in the net pool on an MIVB-MI server that is in VLAN mode.
On the command line, enter the mcdnetpool command. The mcdnetpool command manages a pool of network addresses suitable for use during creation of MiVoice Business instances in MiVoice Business Multi Instance. For more detail about the mcdnetpool command and its parameters, see the MiVoice Business Multi-Instance documentation. For non-vlan mode, omit the mgmtip, vlan, mask, and gateway options.
mcdnetpool -c 214 --sysip=3.50.0.4 2 --mgmtip=192.2.8.4 1 --gateway=3.50.0.1 0 --mask=255.255.254.0 0 --vlan=3500 0
Where:
• | -h, --help - Show this help message and exit. |
• | -c COUNT, --count=COUNT – The number of entries to add to the pool. |
• | --sysip=VIRTVXWORKSINET - The system IP and increment. This parameter is required only if adding entries to the pool. The phones connect to this IP address. If count > 1, the IP address is incremented for each subsequent creation by “increment” until “count” entries are created. The example shows ip=2.2.2.5 and increment=4 : --sysip=2.2.2.5 4 |
• | --mgmtip=MANAGEMENTIP – The management IP address and increment. This parameter is required only if adding entries to the pool and this server has VLAN mode enabled. This is the management plane IP address used to access this MiVoice Business instance. If count > 1, the IP address is incremented by “increment” until “count” entries are created. The example shows ip=2.2.2.5 and increment=4 : --mgmtip=2.2.2.5 4 |
• | --gateway=VLANGATEWAYIP – The gateway IP address and increment. This parameter is required only if adding entries to the pool and this server has VLAN mode enabled. This is the address of the default router on this VLAN. If count > 1, the IP address is incremented by “increment” until “count” entries are created. The example shows ip=2.2.2.5 and increment=4 : --gateway=2.2.2.5 4 |
• | --mask=VLANNETMASK – This is the network mask and increment. This parameter is required only if adding entries to the pool and this server has VLAN mode enabled. The netmask of the network on this VLAN. If count > 1 address will be incremented by increment until "count" entries are created. The example uses mask=255.255.255.0 and increment=256 : --mask=255.255.255.0 256 |
• | --vlan=VLANID – The VLAN ID and increment. This parameter is required only if adding entries to the pool and this server has VLAN mode enabled. This is the VLAN ID the instance will join. If count > 1, the ID is incremented by “increment” until “count” entries are created. The example shows VLAN=100 and increment=1: --vlan=100 1 |
2. Manually create one media server instance for each sysip address in the net pool.
1. Using MSL, install the File Server.
2. Add a user on the File Server. Save the password; you will need it for future steps.
1. Using MSL, install Platform Manager, either on the same server as the File Server or on its own server.
2. On AMC, using the AMC account that is bound to your AMC API credentials:
a. Create a customer. Platform Manager places all ARIDs that it creates in this customer.
b. Generate the sales orders for the licenses required (Base Kit licenses and user licenses, for example).
3. On Platform Manager, in Configuration tab, click AMC Account, enter the API access credentials (consumer keys and secret) that you received from Mitel for API access to your AMC account.
1. On Platform Manager, enter the Sales Order (Configuration > AMC Accounts > License Bank Records > (add) Sales Order).
2. Register the File Server (Configuration > File Servers > Register File Server).
• | Enter the username and password you received on File Server when creating the user. If the File Server is co-located on the same server as Platform Manager, ensure that the File Server address entered is the public IP of the server. Do not use localhost/127.0.0.1. |
3. Upload the software Image files and the golden database files (Configuration > Files > Upload Files).
• | There are reference (example) MiVoice Business database files available on the Platform Manager server, in the directory /opt/dist_oria-bim-setup/reference. |
4. For MiVoice Business Multi-Instance: Create the MiVoice Business Multi Instance pools (Configuration > MiVB-MI Pools > Create MiVB-MI Server Pool). For production, you should have two or more server pools. For a demonstration system, one server pool may be sufficient. MiVB-MI Pools are referred to in the resource blueprints.
Example: Assume that there are two pools, named “east” and “west”:
a. Place the east coast MiVB-MI servers in pool “east”, and the west coast servers in the pool named “west”.
b. Create two resource blueprints, each referring to a different MiVB-MI pool (described in a later step).
c. In the platform blueprint, link to the resource blueprints. The resulting platform will contain one instance in each pool (described in a later step).
In this example, using this naming convention, the result is geographic classification of the servers. Many different naming conventions are possible; be sure to plan a naming convention that facilitates management of your system.
5. Register the Infrastructure (Configuration > Infrastructures > Register Infrastructure).
• | For MiVoice Business Express: Register a VMware vCenter infrastructure. |
• | For MiVoice Business Multi Instance: Register the MiVB-MI servers created earlier and place them into one of the pools created. |
CAUTION: You cannot remove servers from a pool.
6. Create MiCollab Multi-tenant pools (Configuration > MiCollab-MT Pools > Create MiCollab-MT Pool).
a. Add MiCollab Multi-tenant servers (Configuration > MiCollab-MT Servers > Add MiCollab-MT Server).
b. Register the MiCollab servers and place them in the MiCollab pools created. This is similar to the MiVB-MI Pools registered in an earlier step.
7. Create an ARID blueprint (Blueprints > ARID Blueprints > Create ARID Blueprint).
a. In AMC Parts List, enter the AMC part number (the MiVoice Business Multi Instance Base Kit license part number is 54006021, for example), with quantity 1.
b. Click the + symbol to add the AMC part.
8. Create resource blueprints (Blueprints > Resource Blueprints > Create Resource Blueprint).
Create resource blueprints using the MiVoice Business software Image and golden Database file.
If you are creating MiVoice Business Multi Instance Resource Blueprints, create one resource blueprint for each golden database file; primary and secondary.
Note: Use the MiVoice Business System Administration Tool user name and password that is configured in the MiVoice Business golden database files being used. If you are using the golden database supplied in the reference.zip file, username=system, password=default).
9. Create a platform blueprint (Blueprints > Platform Blueprints > Create Platform Blueprint).
a. Associate the two resource blueprints and the ARID blueprint created earlier to the new platform blueprint.
b. In AMC Group Parts, enter User Licenses to provide to the Group (UCC part 54006169, for example).
c. Select Create Cluster. Select the MiCollab-MT Pool from the drop-down list if you want to use MiCollab Enterprise with the MiVoice Business instance. (This does not apply to MiVoice Business Express Blueprints. To create a resilient network based on MiVoice Business Express, you can add MiVoice Business Virtual controllers after Platform Manager work is complete.)
10. Test the Platform Blueprint to ensure that it will result in the intended system.
11. Add an inventory pool (Inventory > Add an Inventory Pool) to trigger creation of the instance.
a. Select the platform blueprint from the list.
b. Select Start After Build. This starts the MiVoice Business instance after the instance is created successfully.
c. Enter a Low Water value greater than zero to ensure that the building process is triggered automatically as instances are used. The inventory pool software tries to keep the number of Ready instances at the low water mark. If the Low Water setting is 5, for example, and the number of instances falls below 5—because instances have been used by Oria, then more instances are built to keep the inventory at or above the Low Water mark.
12. Create a test instance before starting to create an inventory of instances. Navigate to Platform Groups > Create Platform Group. Then select the new blueprint from the drop-down menu.
13. Create Platform Groups (Platform Groups > Create Platform Group).
Note: Oria uses only instances created through Inventory.
1. Log in to the Oria Service Provider portal.
2. Register the Platform Manager (System > Platform Manager Registration).
3. Register the Platform Manager blueprint (Platforms > Platform Manager Blueprint Assignment > Register Platform Manager Blueprint). Select the Blueprint from the displayed list.
4. Register platform groups (Platforms > Platform Groups > Register Platform).
a. Select Managed Platform. Select a Blueprint that matches the required platform group configuration.
b. Click Submit. Oria uses an instance from the Platform Manager's Inventory Pool.
5. After the platform groups are registered successfully, you can create a customer in Oria.
Note: After the Platform Manager is registered, you can access Platform Manager from Oria (Platforms > Platform Manager).
To turn the blueprints and instances you have created into a system for end-customers, you must have a suitable golden database. If you are using the sample golden database provided, you must modify it to suit your environment. At minimum, you must make the following changes.
Log in to the MiVoice Business through the System Administration Tool:
• | Change the MiVoice Business password. The default password is “default”. |
• | Configure the SIP Peer (Network Elements form and SIP Peer Profile form) |
• | Configure the MiVoice Border Gateway IP address (Network Elements form) |
When creating or modifying MiVoice Business golden databases, start from a database that has not been modified by Platform Manager. The Platform Manager modifies the MiVoice Business database only if Create Cluster is selected in the Platform Blueprint.
CAUTION: The MiVoice Business instances created from the example blueprint above are not suitable as seeds for new custom golden databases because this database has been modified by the Platform Manager (unless you did not select Create Cluster when creating the platform blueprint). Install the sample golden databases to a standalone MiVoice Business server before performing any customizations. After completing your customizations, back up the MiVoice Business database. This MiVoice Business database backup is your new custom golden database. Repeat this customization and backup to create golden databases for each primary and secondary system.
1. In Platform Manager, clone the platform blueprint by clicking Blueprints, and then click the Platform Blueprint ID. The Platform Blueprints page appears.
2. Click the Clone button to create a copy of the blueprint.
3. In this cloned copy, deselect Create Cluster.
4. Build an instance of this cloned blueprint (Platform Groups > Create Platform Group).
5. Log in to the MiVoice Business System Administration Tool for this MiVoice Business Instance and make the changes you need for the new system you are building.
6. Back up the MiVoice Business database. This backup file is the new, customized golden database.