Cisco Bug: CSCut47985 - PI 2.2 cannot connect to a device when using custom prompts and SSH
Sep 22, 2017
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: When a customer is using custom prompts from their tacacs server, they cannot connect to those devices using SSH as the cli protocol from Prime Infrastructure. Conditions: Tacacs server configured to have devices use custom prompts. Devices configured to authenticate users to that tacacs server. Prime Infrastructure configured to expect the custom username and password prompts. (note, you must also alter TacacsPrompt.ini and restart the services. see CSCut48057) Prime Infrastructure, attempt to add the device into management, using the appropriate snmp credentials, and cli credentials, using ssh as the cli protocol.
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