Both point to the enable password being missing in DCR for the device.

hmmm..

and if placing the credentials by editing device credentials doesnt get the credentials in the appropriate area, what does?

how can i confirm your theory...

bruce

To verify whether the enable password is populated, you could choose Export from DCR - Device Mamanagent, either in CSV or XML format (don't forget to tick the "Export Device Credentials" box if on LMS 3.2). Then examine the line for the problem device.

Also, you could set up a sniffer session, or use the Packet Capture tool bundled with LMS, to capture the conversions during a Sync Archive job (scheduled or ad-hoc) against the problem device. That could shed some light, depending on what protocol you've selected (less with SSH).

Lastly, you can examine the Sync Archive job logs or post them here. For example, on Solaris, it's located in /var/adm/CSCOpx/files/rme/jobs/ArchiveMgmt/[jobID]/. Of course, having debug on would be much better, so you may want to schedule an ad-hoc Sync Archive after enabling debug on ArchiveMgmt in RME.

I turned on debugging, looked at the txt file that is generated and it says the same thing as the error that is displayed

Actually, its not an error concerning the password.  It is stating that the enable username is missing in one section of LMS

but seems to manifest itself in RME as an authentication failure.

"Could not enter ENABLE Mode from USER Mode on Device"

Now I'm starting to suspect you device is running one of the IOS versions affected by CSCsu21040.

Basically, the buggy IOS asks for "Username: " again after receiving "enable", which throws RME for a loop.

Some of the affected IOS I've seen:
12.2(17r)SX3
12.2(17r)SX5
12.2(33)SXH3

Fixed-In

12.2(33.3.12)SXH
12.2(33)SXH4

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsu21040

CSCsu21040 Bug Details

Understood...some buggy IOS's, but how do I work around it? I cant upgrade all my IOS's (very large datacenter).

Is there a method to do so?

Bruce

No workaround that I'm aware of from the LMS end.

i responded via email a bit ago...

However, a follow on to that email...this problem only occurred when i changed TACACS appliances.  We were using TACACS on one appliance and are now using it on another appliance...

same configuration, just different user accounts...

bruce

Then I wouldn't attribute the problem to the bug unless one could manually duplicate the symptom of getting the extraneous "username: " prompt upon trying to enter enable mode. It could be another cause entirely.

Agreed.

And I am not being prompted when I merely SSH into the devices...so,

probably not the bug you reference causing it...

I am perplexed...

Bruce

Anybody have any other thoughts?

I've removed a device, added back in, restarted all the services for LMS, reinventoried the device,  I have validated and revalidated the credentials and nothing seems to point to the problem.

is there a log that would give some indication of what is happening between LMS and the device...Nothing apparent is in the switch log.

thanks.

bruce

hmm..but, now that we are talking about it,

the credentials are present for the initial ssh login process...

its not really saying the password is in correct, its saying the Enable Username is missing.

bruce