cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2189
Views
0
Helpful
9
Replies

CW2K Devices Failing Config Downloads

I have several devices that are failing RME config downloads. The message that is reported by CW2K is, "failed to receive device prompt."

The username prompts on these devices have been customized, so they are not the typical "Username:". I am assuming that this is what is causing the problem.

Is there any way to have CiscoWorks recognize the non-standard username prompt? I'd like to get away from having to reconfigure the prompts on the devices if possible.

Thanks.

9 Replies 9

nhabib
Level 9
Level 9

What version of RME are you running?

3.5

One more question, and I will provide the work-around:

what platform are you running it on, Windows or Solaris?

Thanks nhabib.

It is running on Windows.

First open a DOS shell and issue the command:

net stop crmdmgtd

Make a backup copy of the following file:

CSCOpx\objects\cmf\data\TacacsPrompts.ini

Next, edit the above mentioned file (using Wordpad) and add your customized prompt in there. Make sure you get the syntax right of course (it is fairly straightforward).

Back to the DOS shell and issue the command:

net start crmdmgtd

Wait 5 minutes or so, log back in and test it.

I have the same problem but only on devices running CAT OS. It seems as the promt has a line in between username and password that CiscoWorks cant understand it. (i could be wrong in my assumption here).

How would i accurately get the syntax of this prompt:

"Username:

Password:"

Notice the line in between. I am running an older version of RME (3.4) and am upgrading soon but obviously need the configs now.

Any ideas?

IIRC--You can solve this on older versions by appending the device prompt with "#" or ">" in the CatOS config.

set prompt MyPrompt>

HTH

Steve

I really appreciate your help nhabib... I tried the work-around that you provided, but the TacacsPrompts.ini file did not exist. Any ideas? Thanks!

If you are on RME 3.5, then the file has to exist

Could it be that you are on RME 4.0 (part of LMS 2.5)?