Preview Tool

Cisco Bug: CSCul22290 - Errors resulting from selection of partition within Directory Sync menu

Last Modified

Apr 25, 2014

Products (1)

  • Cisco Unified Attendant Consoles

Known Affected Releases

10.0(1) 9.1

Description (partial)

In the webadmin > Directory Synchronization menu you have the ability to specify the device partition you wish to prioritize BLF status for.

WebAdmin and Installation Guide Note:
Route Partition—(Only displayed when the Cisco Unified Communications Manager directory is used). This prioritizes which DN to import when there are identical DNs in different partitions. Either Select a route partition or one of the following:
? <None>—disregard the route partition field when synchronizing the directory.
? CUCM <None> partition—picks up only those devices in the Cisco Unified Communications
Manager specified as (None).

There are a couple conflicts tied to this specification.

If you specify a route partition aside from <None> (Including CUCM <None>); BLF will be returned only for devices within that partition and that do not have a partition assigned to them. This conflicts with the 'designed' behavior as it is doing more than prioritizing BLF, it is effectively limiting BLF to the noted partition.
Issue 1) Devices within any other partition will not return BLF to the console.
Issue 2) If you manually specify a device name residing in another partition, the name is removed once the validation takes place with CUCM.

Subsequently, by behaving as it does the behavior contradicts the Device Selection data presented in the Design Guide as well. Ideally the specification of a partition in the Directory Sync window would do as prescribed - prioritize those devices; not prioritize those devices and exclude those from neighboring partitions.

If you specify a route partition aside from <None> (Including CUCM <None>)
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.