Cisco Bug: CSCvu68561 - PI in HA with a VIP pushes physical IP address of each node as trap destination for devices
Jun 19, 2020
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: In Prime Infrstructure's High Availability config guide, it is suggested that the "virtual IP address is intended as a destination for syslogs and traps, and for other device management messages being sent to Prime Infrastructure servers." Therefore, the system itself should use only virtual IP address as the trap destination for devices added to Prime Infrastructure in HA, with a VIP address configuration. However, as part of a discovery job, Prime Infrastructure is pushes its own (physical IP) address to a WLC, resulting in that device having 3 trap destinations on the WLC; one VIP and 2 IP addresses that correspond to the actual addresses of each node. Without filtering traffic, that configuration could cause duplicate trap/syslog messages to be sent to Prime Infrastructure. Expected behavior in HA: - use the VIP address for syslogs and traps, - use the physical addresses for pulling tasks. Conditions: This is observed in Prime Infrastructure configured in HA mode with a virtual IP address configuration.
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