Cisco Bug: CSCvt15640 - Passive ID secondary agent not having DC info when agent switched from standalone to primary
Feb 29, 2020
- Cisco Identity Services Engine
Known Affected Releases
Symptom: Create an standalone agent MS-RPC. (Eg: Agent1) Map it to a DC. Now edit the standalone agent and make it primary. Create a new agent with role as secondary(Agent2) and map primary as the edited agent.(Agent1) Now check the CiscoISEPIC log in Agent member server. Primary will show correct DC count as "Configuration has 1 DC". But Secondary will show as "Configuration has 0 DC". Since secondary dont have DC info, mapping will not be sent by secondary if primary is down. Conditions: Agent should be updated from standalone to primary before mapping the primary to secondary. Agent should be mapped with DC already before updating.
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