MiVoice Business Multi Instance Server and Media Server Manager
This page includes infrastructure instructions for:
MiVoice Business Multi Instance Server
MiVoice Business Multi Instance provides the infrastructure and management to run multiple MiVoice Business Instances.
Before adding the first server, you must setup a MiVoice Business Multi-Instance server pool. Then register the MiVoice Business Multi-Instance servers, grouped into one or more pools. Use these pools to force geographic separation of instances.
Set up MiVoice Business Multi Instance Server Pools
A server pool is a grouping of MiVoice Business Multi-Instance servers. When the Platform Manager builds a platform from a blueprint, the blueprint indicates the pool from which the MiVoice Business Multi-Instance server is to be obtained. If the pool is unable to fulfill the request, the creation operation will fail.
Pools are used to indicate a hardware location preference. Pools are used to force resilient pairs of MiVoice Business Multi-Instance instances to be built on different servers, possibly in different data centers.
You should have at least two MiVoice Business Multi-Instance pools. MiVoice Business Multi-Instance pools are referenced by the resource blueprints, and are used to indicate the geography in which you want the resource instances located. For example: two pools, named east and west; place your east coast MiVoice Business Multi-Instance servers in pool east; west coast in west. You make two resource blueprints, each referencing a different MiVoice Business Multi-Instance pool. In the Platform Blueprint, link in both of the resource blueprints. The resulting platform will contain one instance in each pool, east and west, resulting in geographic separation of the instances.
A MiVoice Business Multi-Instance server cannot be removed from a pool, and it cannot be moved to another server pool.
Use pool names that describe their location or planned use so that other admins are able to choose accurately from them. Some examples:
-
East Coast
-
West Coast
-
East-Primary
-
East-Secondary
Add a MiVoice Business Multi-Instance server to the infrastructure collection
When adding a MiVoice Business Multi-Instance server, you must supply the following information:
-
Server IP address
-
Mitel Standard Linux (MSL) administrator log in name
-
MSL administrator password
-
The server pool into which this MiVoice Business Multi-Instance server is to be placed
You can add a MiVoice Business Multi-Instance server at any time. You may delete a MiVoice Business Multi-Instance server only if there are no Platform Manager-managed instances on that server.
Tenants on a MiVoice Business Multi-Instance server that have been added to Platform Manager should be managed using Platform Manager. You can still log into MiVoice Business Multi-Instance, but any tenants created using the MiVoice Business Multi-Instance web panel will not be managed by Platform Manager. If you stop or start a Platform Manager-managed tenant from the MiVoice Business Multi-Instance web panel, the change will not be reflected on the Platform Manager web panels.
If you delete tenants from the MiVoice Business Multi-Instance web panel, you should also delete the corresponding resources and platforms on Platform Manager. These changes are not reflected on Platform Manager automatically.
Prepare MiVoice Business Multi-Instance
Platform Manager does not create the MiVoice Business Multi-Instance ARID. You must manually install and license a MiVoice Business Multi-Instance server prior to registering the server with Platform Manager.
You must prepare a MiVoice Business Multi-Instance server before Platform Manager can create tenants on it.
-
Tenant IP addresses: Tenant IP addresses can be obtained from an MiVB_MI Server IP Address Pool or be supplied via Resource Blueprints with an override when Platform Instances are created. The Resource Blueprint method is preferred if the MiVB_MI is in isolated VLAN mode.
-
Associated Media Server Manager instances can be created automatically or pre-configured when you build the Media Server Manager computer.
You do not need to load any golden databases or MiVoice Business software images onto the MiVoice Business Multi-Instance server. Any necessary files are automatically downloaded during creation of the MiVoice Business Multi-Instance tenants.
If there are tenants on the MiVoice Business Multi-Instance server when you register it with Platform Manager, these tenants are not managed by Platform Manager.
Capacity calculation
Platform Manager considers the tenant capacity of the MiVoice Business Multi-Instance server to be the lesser of:
-
The server's maximum number of tenants, and
-
The number of address records in the network pool.
You can use the network pool to limit the number of tenants created by the Platform Manager on a particular server. To see the server capacity in the utilization widget on the Platform Manager, navigate to Configuration > MiVB-MI Pools.
Tenant IP Addresses from IP Address Pool (Optional)
When Platform Manager instructs a MiVoice Business Multi-Instance server to build a tenant, the tenant IP address is pulled from an address pool that was previously configured on that MiVoice Business Multi-Instance server.
The MiVoice Business Multi-Instance server has two IP address configuration modes known as VLAN and non-VLAN mode. The default is non-VLAN mode. If your MiVB_MI server is in VLAN mode and every MiVB_MI tenant is to be in a separate, isolated VLAN then you should use the Resource Blueprint method of assigning tenant IP addresses.
If VLAN mode is used to conserve IP addresses, all MiVB_MI tenants are on the same VLAN (typically protected by a shared MBG), then the mcdnetpool method can be used. See below.
-
If the MiVoice Business Multi-Instance server has existing tenants, do not add the IP addresses used by these tenants to the network pool.
-
If you are building MiVoice Business Multi-Instance tenants manually using the MiVoice Business Multi-Instance GUI, do not use IP addresses that have already been added to the network pool. This will cause failures when Platform Manager tries to use these IP addresses when creating a tenant.
If you are deploying MiVB_MI tenants to isolate VLANs, use the Tenant IP Addresses from Resource Blueprint method below.
Use the MiVoice Business Multi-Instance server CLI command mcdnetpool to create and view the network pool. You add sets of IP addresses that are appropriate for a MiVoice Business instance on this server. The output of the mcdnetpool command differs depending on whether the server is in VLAN mode or not. Use the –h option to view help. If you use the MiVoice Business Multi-Instance web panel to create instances, do not use an address from the network pool. Each MiVoice Business Multi-Instance server registered with Platform Manager has an address pool dedicated for use by Platform Manager.
Example:
List the contents of the network pool. A yes in the "record allocated" column indicates that the pool record is in use.
The listing shown here is from a system that is not in VLAN mode.
\[root@triale mcd\]# mcdnetpool -l
Net Pool
is record
ID allocated
184 yes 10.40.184.41
185 yes 10.40.184.45
179 yes 10.40.184.21
183 yes 10.40.184.37
188 yes 10.40.184.57
186 yes 10.40.184.49
182 yes 10.40.184.33
180 yes 10.40.184.25
178 yes 10.40.184.17
181 no 10.40.184.29
Tenant IP Addresses from Resource Blueprint (Optional)
This is recomended for MiVoice Business Multi Instance servers in VLAN-mode.
You can supply the default MiVoice Business tenant network addresses through the Resource Blueprint and override any network properties at Platform Instance creation. The VLAN tenant's management IP addresses must be supplied when Platform Instances are created.
This will trigger the following additional questions at platform Instance creation time,
-
MiVB_MI Server name - This will the the server that the tenant is deployed on. Network properties provided must be appropriate for this server.
-
MiVB tenant VLAN ID
-
MiVB tenant IP, mask, gateway (default values from the blueprint)
-
MiVB tenant Management IP address
MiVoice Business Multi-Instance server usage
You can see tenant capacity per server and per pool. See the Platform Manager MiVB-MI Pools page for a list of pools and their respective utilization. Click the pool name to see a list of MiVoice Business Multi-Instance servers and their specific utilization figures.
The server capacity is the lesser of MiVoice Business Multi-Instance tenant capacity and network pool size.
MiVoide Business Multi Instance Media Server Manager
There are two ways to configure the MiVoice Business Multi Instance associated Media servers; manual and automatic.
Manual Media Server Manager tenant creation
You create media server instances manually, at the same time as you are populating the MiVoice Business Multi-Instance network pool. Create and start one media server instance for every IP address in the MiVoice Business Multi-Instance network pool. Each instance waits for its assigned MiVoice Business instance to appear. During this wait time, the media server instance state will show as Down or Starting; this is normal.
Automatic Media Server Manager tenant creation
You can configure MiVB-MI type resource Blueprints to create an associated Media Server tenant at the same time as the MiVoice Business Multi Instance tenant is being created. To prepare for this, register Media Server Manager servers as Infrastructure, and place them in the same MiVB-MI pool as the associated MiVB-MI servers. You do not need to pre-generate the Media Server tenants.
If you need VLAN mode, you will need to set it as appropriate for your situation. VLAN mode is not enabled or disabled by Platform Manager.
With this configuration, when Platform Manager is creating a MiVoice Business Multi Instance tenant, it will search the same MiVB-MI Pool for a Media Server Manager. A Media Server tenant pointing to the new MiVoice Business tenant is then added to the Media Server Manager. If none are found, the create operation will fail.
If the Media Server tenant was created by Platform Manager, then Platform Instance Start/Stop/Delete actions will also operate on the Media Server tenant.
VLAN Mode, Media Server Manager
(The following applies only to Automatic Media Server creation.)
In a MiVB-MI type Resource Blueprint, you can indicate that the Media Server Manager is to be in VLAN mode. If Media Server VLAN mode is requested by the blueprint then at Platform Instance creation, Platform Manager searches the MiVB-MI Pool for a VLAN mode Media Server Manager.
This will trigger the following addition questions at platform Instance creation time,
-
Media Server Manager name. This is the server that the tenant is deployed on. Network properties provided must be appropriate for this server.
-
Media Server tenant VLAN ID
-
Media Server tenant IP, mask, gateway (default values from the blueprint)
If no VLAN mode Media Server Managers are found, the create operation fails.