cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2441
Views
10
Helpful
12
Replies

LMS 3.2-Sync-Archive is not working for WLC

Prasan Venky
Level 3
Level 3

Hi,

I tried to update Sync-archive for the device but it fails. Please help.

12 Replies 12

Prasan Venky
Level 3
Level 3

                    Error Message is attached. I even found some thread in forum saying to change TacacsPrompt.ini file content. But if i do it, what about other devices when try to use sync-archive..?

Run a device credential verification job from RME > Devices management > CDA. And share the screenshot if the Telnet or SSH is successful or failed.

As per the last screenshot, it clearly says the credentials are failing. Tacacsprompt.ini is only needed when using telnet on a device which is configured for AAA.

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Thanks for your reply. If i change Tacacsprompt.ini file prompt, will it create any impact..? like what about the other devices prompts if little different..?

KVS

As said this file is only referred when device is configured for AAA and authenticated for Telnet. You can add multiple prompts after comma.

For example, if the device while logging ask you first username prompt as USERNAME: and password as PASSWORD: you should modify file to look like :

[TELNET]
USERNAME_PROMPT=username:
PASSWORD_PROMPT=password:

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Thanks for your reply.I will do the same and get back here.

KVS

Hello Vinod,

We changed the TacacsPrompt file but no luck. It is failing with the same error i attached earlier.Attached Credential Verifacation report for your reference.

Any suggestion..

Thanks in advance..

Please go to :

CiscoWorks LMS Portal > Common Services > Software Center > Device Update > click in package count number in front of RME > on new pop up window filter for sysObjectID for this value #  1.3.6.1.4.1.14179.1.1.4.3.

This will ensure we have device package available for WLC.

I would urge you to run a new device credential verification job, not see the report,which is on the screenshot. Report will continously bring same report from last job. You can run new job from :

CiscoWorks LMS Portal > RME > Devices > Device Management > Device Credential Verification Jobs

Share the screenshot of new job result. If it still fails :

1. Enable debug for Archivemgmt:

CiscoWorks LMS Portal > RME > Admin > System Preferences > Application Log Level

2. Remove content of NMSROOT\log\dcmaservice.log

3. Run new sync archive job for WLC.

4. Share NMSROOT\log\dcmaservice.log and screenshot of result.

-thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Thanks a lot for your reply... Will do the testing and get back to you tomorrow.

Dear Vinod & All,

Now LMS is not getting archive for any devices added to it.. its been very risky now. Any help how it suddenly went wrong ..?

It is not easy to know what is the reson for failing devices. You should share the failing messaged and if the message is similar for all the device. Also what did you do last? Did you tried any upgrade?

Share screenshot and fresh dcmaservice.log by removing older content and reproducing the issue.

-Thanks

-Thanks Vinod **Rating Encourages contributors, and its really free. **

Dear Vinod,

Thanks for your response. We havent tried for any upgrade.

Sync Archive is partially successful for all the devices. I attached the error from GUI.

I will paste the dcmaservices log soon.

Thanks in advance.

Mainly i am seeing the below errors

1)Insufficient no. of interactive responses(or timeout) for command: copy const_nvram:vlan.dat tftp:.TELNET: Failed to establish TELNET connection to x.x.x.x - Cause: Connection refused. VLAN Config fetch is not supported using TFTP. VLAN Config fetch is not supported using SCP.

2)Could not detect SSH protocols running on the device  TELNET: Failed to establish TELNET connection to x.x.x.x - Cause:  Connection refused.  VLAN Config fetch is not supported using TFTP.  VLAN Config fetch is not supported using SCP. 

Any clue ...?