Cisco Bug: CSCus72290 - Swim distribution gets hanged with single device when doing parallely
Feb 26, 2016
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: Swim image distribution done to many devices in parallel may cause the job to be in pending state forever. Conditions: Typically, this would happen when both the following conditions are met: 1) SSH service is enabled on the device and hence, Prime Infrastructure is able to establish SSH connection with the devices, but the authentication fails. 2) A SWIM job is configured to distribute image to multiple devices (for instance, 150 or 200) in parallel. If the SSH is disabled in the device, this issue would never happen. When the SSH is enabled, typically this would happen when the above conditions are met. However, from the code analysis, there is a possibility that this issue can occur in a SWIM distribution even when the conditions of parallel distribution and authentication failure are not met, but the probability is extremely less. In the lab, this has never happened when the above conditions are not met. Triggering more such SWIM distribution jobs with these conditions will result in more threads to be in waiting state and the server needs to be restarted to recover from this.
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