Cisco Bug: CSCta42931 - GETVPN_SCALE: Status of seconday KS may show as inactive when down
Jan 31, 2017
- Cisco IOS
Known Affected Releases
Symptom: Primary key server is not receiving the state of the secondary KS which was in COOP. Group members are "ack"ing the rekey from secondary and seems to ignore that from the primary Conditions: Steps to reproduce. 1. After coop is established, shut the crypto interface in secondary. No message is sent to the primary Key server 2. Un shut the interface in secondary key server. It immediately sends unicast rekey. All the GMs receive this and ignores the rekey received from the correct primary (KS7).
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