Flow Through - Maintenance

This topic describes the following maintenance tasks:

Adding a MiVoice Business Element (Start Sharing)

To add a MiVoice Business or MiVoice Business Express element to an existing sharing (Flow Through Provisioning) network:

  1. Ensure that the MiVoice Business element databases are in sync:

    • Perform a sync from one MiVoice Business to all the other MiVoice Business elements in the network

    • Resolve any synchronization errors that are encountered.

  2. Log into the System Administration Tool of the sharing MiVoice Business platform.

    • In the top left corner, select View Alphabetically.

    • In the left forms menu, click Network Elements.

    • Click Add and add the MiVoice Business or MiVoice Business Express as a network element.

  3. Start sharing with the newly added element..

    • In the MiVB Network Elements form, check the box of the element

    • Click Start Sharing.

    • Click OK. After the start sharing operation is complete, the Data Sharing field for the MiVoice Business element changes to YES.

  4. Perform a full SDS synchronization with new element:

    • Check the box of the new MiVoice Business or MiVoice Business Express server.

    • Click Sync.

    • Click Data Migration.

    • Click Apply.

    • Click OK.

    Note: The synchronization of MiVB elements with MiCollab takes substantially longer than the synchronization of just MiVB element form data.

  5. In the Network Element tab of the User and Services application, access the newly added network element and enter the desired Set Registration and Set Replacement Codes.

    Note: When you add a MiCollab Server as a network element in MiVB System Administration Tool and initiate Flow Through Provisioning, default login credentials are generated in the Credentials tab of the Network Element page in the MiCollab Server. Make sure that you replace these default credentials with the MiVB System login credentials. If the credentials are incorrect, PBX synchronization from MiCollab Client Service will not work, and the MiTAI authentication in MiCollab Client and NuPoint Unified Messaging does not work.

  6. Reconcile any conflicting data entries.

  7. Check the Distribution Error application and resolve any distribution errors.

  8. Create backups of the MiCollab database and all MiVoice Business databases.

Updating Network Elements

Updates that you make to the basic data (Element Identification, Credentials, and System Properties fields) of a network element are shared to all the other network elements. Typically, the sharing scope is across the cluster. Changes that you make in the application data (Voicemail fields) of the network element page are not shared and do not result in a distribution.

If you change the IP address or name of a 3300 ICP network element that is using a NuPoint UM IP Integration License, you must activate the NuPoint UM inactive configuration. in order for the changes to take effect.

Changing an IP Address or Hostname

If you change the IP address of a node which participates in data sharing, the distribution of that and subsequent data changes are sent to the new IP address. Therefore, it is recommended that you change the IP address from the local node, except in cases where other nodes may be out of sync with the IP address (for example, after a restore).

The System Name and IP address of the local MiCollab Network element cannot be edited in the Users and Services application, but is displayed as read-only with the current values.

Updating the IP address of the MiCollab server is carried out via the MSL server console "Configure this server" option after which a reboot is performed to apply the changes. After the change is applied, the IP address of the MiCollab network element is changed.

The System Name of the MiCollab Network element is modified with the hostname of the MiCollab server. Updating the hostname is also carried out via the MSL server console "Configure this server" option. If the hostname is changed, the System Name of the MiCollab Network element will be changed to the first 9 characters of this hostname.

Once the MiCollab server IP or hostname has been updated, the IP address or System Name for the MiCollab Network Element should be updated automatically in the Network Element forms for all other sharing Network Elements.

If the IP address of a node which is enabled for data sharing is incorrect, all nodes with the wrong IP address will be able to distribute shared data updates to that node and thus distribution errors will accumulate. These errors may be deleted or will be retried automatically once the IP address has been corrected.

Removing MiCollab from a Sharing Cluster

Use this procedure to remove MiCollab from the sharing network if

  • you have accidently added MiCollab to the wrong cluster, or

  • you want to move MiCollab to a different cluster.

Note: Do not delete the MiVoice Business network elements from the MiCollab USP Network Elements tab if you want to remove MiCollab from the sharing network. This action will cause the SDS network to stop sharing. Instead use the procedure described below:

To remove MiCollab from a sharing cluster:

  1. Log into the MiCollab Linux shell, via SSH or local console using the root account.

  2. Run the following Linux command: /usr/mas/bin/sds-utility --disconnect-sds

  3. You are presented with a list of actions that will be performed and a confirmation if these actions should be applied. Confirm to proceed disconnecting from SDS.

  4. Confirm that the Linux command completes successfully.

  5. Log into the System Administration of a MiVoice Business element that remains in the sharing network.

  6. Choose to view the forms alphabetically.

  7. Select Maintenance and Diagnosticsand then click Maintenance Commands.

  8. Enter REMOVENE <MiCollab network element name> and select OK to confirm.

  9. Repeat the REMOVENE command on all remaining Network Elements in the sharing network.

  10. Verify that all remaining nodes within the sharing network no longer display the MiCollab Network Element within the Network Elements list.

  11. The User Roles and User and Service Templates forms will still contain a set of templates that was previously shared with MiCollab. If these templates and roles are not required, you can delete them.

Stop and then Start Sharing from MiCollab

If you need to modify data on the MiCollab system that you don't want distributed to the other MiVoice Business elements, you can stop sharing from MiCollab, apply the updates to MiCollab, and then start sharing again with the MiVoice Business network elements.

To stop sharing from MiCollab:

  1. Log into the MiCollab linux shell, via SSH or local console using the root account.

  2. Run the following command from the linux prompt:

    /usr/mas/bin/sds-utility --stop-sharing

  3. Make any required updates to the MiCollab database. The data is not shared to the MiVoice Business.

To start sharing again:

  1. Log into the System Administration of a MiVoice Business element that remains in the sharing network.

  2. Choose to view the forms alphabetically and select the Network Elements form.

  3. Locate the MiCollab network element, select it, click Start Sharing and confirm OK.

  4. Verify the sharing and synchronization completes successfully and if instructed, log into the MiCollab server and observe the red banner directing a run of the Reconcile Wizard to align the data.

Removing a MiVoice Business System from the SDS Sharing Network

To remove a MiVoice Business element from the SDS sharing network:

  1. Log into the MiCollab Linux shell, via SSH, or local console using the root account.

  2. At the command prompt, run the following command:

removene <MiVoice Business network element name>

  1. You will be presented with a list of actions that will be performed and a confirmation if these actions should be applied. Confirm to proceed with removing the network element and verify that the removal completes successfully.

  2. Log into the System Administration of a MiVoice Business element that remains in the sharing network.

  3. Choose to view the forms alphabetical.

  4. Select Maintenance and Diagnostics and then click Maintenance Commands .

  5. Enter REMOVENE <MiVoice Business network element name> and select OK to confirm.

  6. Repeat the REMOVENE command on all remaining Network Elements in the sharing network.

  7. Verify that all remaining nodes within the sharing network no longer display the MiVoice Network Element within the Network Elements form.

Note: If you remove all MiVoice Business network elements from the MiCollab Network Elements list, SDS sharing is stopped. If the SDS includes other MiVoice Business platforms that were not managed by MiCollab, then sharing will also be stopped between these elements. To restart sharing among these other elements, log into the Network Elements page of one of the MiVoice Business systems, select the check boxes of the elements that should be sharing and click Sync.
Note: Even after re-initiating the SDS sharing between the network elements, certain issues are reported where few MiCollab services for existing MiCollab users are impacted, like AWV extension information, NPM user mailboxes, and Teleworker information, even if these users exist over MiVoice Business.

If You Create or Delete a Cluster

If you create or delete a cluster of elements in a network that has Flow Through Provisioning enabled, you must perform a Sync operation from a MiVoice Business element in the network with MiCollab. Otherwise, Flow Through Provisioning will not function correctly and data distribution errors will be generated.

In the case where you delete a cluster from the network and then perform the Sync, Flow Through Provisioning will function through the MiVoice Business from which you performed the Sync operation.

Checking Software Logs

The main components involved with flow through provisioning write software logs here:

  • /var/log/mom-server/*

  • /var/log/sdscc/*

  • /var/log/upm/*

If you encounter a problem check these logs. The latest log is always called ‘current’ and the older logs will be present with timestamps.

Parent topic: Flow Through Provisioning
↑