Cisco Bug: CSCuj97958 - Enhance Auto SPT Tracing Location Correlation and Scalability
May 04, 2016
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: There are two issues in current auto SPT tracing: 1. Location Correlation: Customer experienced the issue when the rogue AP is detected on site A, but the rogue AP on wired is traced to site B because we do not have good location correlation between switches and APs. Currently, it is flat polling to all switches for SPT tracing, instead of site specific. Also, we can not expect customer to implement NMSP on all switches for location. Need to implement location tagging or sth like that. We can also refer to the bug CSCuj23356 for site implementation for this enhancement. 2. Scalability: without site specific information, we have to poll all switches in flat level, which will cause scalability issue and is also inefficient. For example, for a retail customer with a thousand stores, SPT should only trace the switches on the store that rouge AP is detected, not all switches on all stores. Conditions: All existing PI codes, between 1.2 and 2.0.
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