Cisco Bug: CSCum99827 - Data Collection doesn't detect devices with reused hostname or ip
Nov 27, 2020
- Cisco Prime LAN Management Solution
Known Affected Releases
Symptom: LMS managed device's host name is changed in device and that device's old host name assigned to new device then the data collection is not collecting the device details for new device. When device ip address or host name is changed, data collection does not accept new devices with same host names or IP address. Conditions: Scenario 1: Device A and Device B. Device A is managed in LMS as XYZ and later it renamed as ABC. Now, Device B is added into LMS with name as XYZ. Now the LMS Data Collection will not take place for Device B. Because LMS maintains history, XYZ is still mapped to Device A and still consider it as Device A, hence the DC will not run for Device B. Scenario 2: Two CAT 6K devices are managed in LMS then it is converted to VSS mode then slave device will be marked as an alias device. Scenario 3: Device A and Device B are managed in LMS. Device A is managed as XYZ and device B as ABC. Event in the network occurred and was updated in LMS via a single seedfile import: Device A is renamed to DEF and device B is renamed to XYZ. Now the LMS Data Collection will not take place for Device B, because LMS maintains history, XYZ is still mapped to Device A and LMS still considers it as Device A, hence the DC will not run for Device B.
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