Cisco Bug: CSCuo16453 - Moving bridges between TMS folders does not update TMSAE's Folder.Parent
Feb 25, 2015
- Cisco TelePresence Management Suite (TMS)
Known Affected Releases
Symptom: When moving bridges (TelePresence MCUs, TelePresence Servers, TelePresence Conductors) between Cisco TMS folders, the folder structure seen in Cisco TMSAE's Fact Call table does not update after the ETL job runs. Example: In Cisco TMS, have a root folder with folder A and folder B as sub-folders. Folder B contains a TelePresence Conductor where we have call data. In TMS, move folder B so that it is a sub-folder of folder A. The folder structure is now root -> folder A -> folder B -> Conductor. Now run the Cisco TMSAE ETL job, and connect to the cube. Look for example at the Fact Call > Call Count measure, and break it down on the 'Folder.Parent Folder Id' and 'Destination System' dimensions. You'll then see that the calls for the Conductor in question still are listed as belonging to root -> folder B. Conditions: All versions of Cisco TMSAE seem to be affected.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases