08-16-2009 11:56 PM
Hello,
While adding Cisco ACE Module into DCR, the verification report says
1. SSH - OK
2. Enable by SSH - Enable Username credential missing.
I have added the enable password for ACE in DCR. What could be missing then.
Thanks.
Solved! Go to Solution.
08-17-2009 12:33 AM
Leave the hostname field empty, and give the context a descriptive display name (e.g. HOSTNAME-context1).
08-16-2009 11:57 PM
This could be a problem with how the ACE module is authenticating enable. If you SSH to this blade manually, then enable yourself, what prompts do you see?
08-17-2009 12:09 AM
Ok. It goes directly into privileged mode without enable password via ssh access. Thanks.
If the ACE module has multiple contexts, how can it be configured in the DCR. Is it via different management IPs against the context.
08-17-2009 12:11 AM
Please ignore. I got the whole config from the admin context itself.
08-17-2009 12:12 AM
If you can do that, good. I know that ASAs and other multi-context firewalls require one to add each context for proper management.
08-17-2009 12:11 AM
If it goes into privileged mode immediately, then don't choose to check enable by SSH in Device Credential Verification. RME should be able to fetch the config so long as it can become enabled using the current DCR credentials.
As for multiple contexts, yes, each context must be added to DCR by its own IP address.
08-17-2009 12:28 AM
When I enter a new device for ACE 2nd context, the DCR reports 'Record for this device exist' while adding the device.
I have added different display name, IP for both the context. Only hostname is the same.
08-17-2009 12:33 AM
Leave the hostname field empty, and give the context a descriptive display name (e.g. HOSTNAME-context1).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide