# Cluster Configuration Notes

## Uniform Numbering Plan is Recommended

Before you cluster a group of existing elements, you can reduce the amount of telephone directory management required to set up the cluster by ensuring that the numbering plans of the elements are uniform.

For clusters larger than 250 nodes, a uniform numbering plan of five digits or less is recommended to avoid exhausting the available digit blocks. If a larger dialing plan is required, directory numbers must be programmed in sequential order (100001, 100002, 100003...) as opposed to non-sequential order (100000, 123456, 324567...) to prevent exhausting the digit blocks.

## Ensure Programming Forms Are Consistent Across the Cluster

Ensure the following forms are programmed identically at each element in the cluster network:

- Interconnect Handling Restriction

- Feature Access Codes

- Class of Restriction Groups

- Class of Service Options

- System Options

- Trunk Groups

- ONS/OPS Circuit Descriptors

NOTE: Use the System Data Synchronization feature to program the forms with the same data. SDS allows you to achieve initial synchronization and then maintain consistent data by sharing data updates across the systems. You can synchronize all of the forms listed above with the exception of the Trunk Groups form by using SDS. You must take form dependencies into consideration when planning a synchronization operation. A synchronization will fail if you attempt to synchronize a form before a form that it is dependent on is completed. For example, you cannot program the ARS Digits Dialed form until the ARS Routes form has been completed.

Program identical values on all the MiVoice Business systems in the cluster for the following

- Set Registration Access Code in the System Options form.

- Set Replacement access code in the System Options form

- COS and COR indices map to the same set of services and restrictions across all systems.

- If the cluster is to provide embedded voice mail for resilient devices, each embedded voice mail hunt group pilot number must be unique. Therefore, if a device is assigned to primary and secondary controllers, the embedded VM hunt groups on those controllers must have a different pilot numbers.

- If you want to implement Resiliency within the cluster, refer to the Resiliency Guide on the Mitel Customer documentation web site for details.

- If resilient clustered hot desking or cluster ACD agent hot desking is required, refer to the MiVoice Business System Administration Tool online help for programming details.

## Reporting of Cluster Call Records

Station Message Detail Recording (SMDR): Internal SMDR records the calls between local cluster devices the same as normal internal calls. External SMDR records calls the between remote portable directory number devices are the same as normal DPNSS calls.

- For outgoing call records, the digits dialed field lists the CEID digits followed by the remote PDN digits, unless the CEID digits are absorbed through digit modification.

- For incoming call records, the digits dialed field lists the CEID digits followed by the remote digits.

Host Command Interface (HCI): Local directory numbers are supported. Directory numbers from remote cluster elements are not supported.

Real Time Events Reporting: Local directory numbers are supported. Directory numbers from remote cluster elements are not supported.

## Dimensioning the Resources

You set the maximum number of elements per cluster (30, 60, 250, or 999) in the License and Option Selection form. Table 1 lists the defaults that are assigned to the MSDN/DPNSS resource dimensions. You can flex these dimensions to meet the specific resource requirements of the site. By reducing unused dimensions, you can make corresponding increases in required dimensions. If the number of elements per cluster is set to 250, you can flex resources to achieve support for a very large network database. Refer to Flexible Dimensioning for more information.

Table 1: MSDN/DPNSS Resource Dimensions (3300 ICP Release 8.0 UR3 and Later)

| MSDN/DPNSS Resource Dimensions
Resource Value | 30 | 60 | 250 | 999
Elements | 30 | 60 | 250 | 999
Telephone Directory Records | 20000 | 30000 | 50000 | 130000
Remote Directory Numbers | 18500 | 28500 | 50000 | 130000
System Dspool Records | 20000 | 30000 | 30000 | 105000
Additional Digit Tree Records | 4055 | 4055 | 4055 | 12000 or 20000 depending on platform
Locations | 2000 | 2000 | 2000 | 2000
Departments | 2000 | 2000 | 2000 | 2000

Related Topics

- Planning the Cluster

- Preventing Dialing Conflicts

- Route Optimization

- Resiliency Considerations