Preview Tool

Cisco Bug: CSCur11605 - ILS should clean up deleted imported catalogs/peers

Last Modified

Jun 14, 2016

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

Currently there is a hard limit of 200 ILS catalogs/peers. Each imported catalog as well as each ILS node is one peer. If an imported catalog is deleted, the GUI reflects that the peer/catalog is gone (and it is removed from the local hosteduricatalog table), however this deleted catalog remains forever in the ILS topology. Its peerinfovector is advertised in the ILS communication (and it remains in the hosteduricatalogkey table).
The problem is in a deployment where there may be changes to the imported catalogs; either new patterns need to be added or old ones changed (to remove or change a pattern). Each of these operations will create a new catalog/peer and "delete" the old one.

Eventually, all 200 ILS catalogs/peers will be consumed.   At this point, from the admin GUI you can still create catalogs, but the system will stop advertising one of the catalogs. The only indication that something isn't working is in the ILS trace files:
 02348425.226 |13:22:17.947 |AppInfo |IlsD CIlsPeerInfoVector::getIlspPeerInfoVector failed to add f9b3d4161c4140aeac656297ee230f2f. PeerInfoVector has 200 peers (ILSP_MSG_PEER_MAX=200)

ILS/GDPR deployment with imported catalogs which need to be changed or added frequently.
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.