Backup Config WLC with Prime 2.2

[MarioLieb]

Hello 

i have a problem with die Archive Management of Cisco Prime 2.2 and the WLC.

I´d tried to Backup the Config of our WLC with Prime 2.2. Every time i try this i get the mentioned error. I tried it with several Users (local or via radius) 

serveral Protocols telnet / ssh. But nothing works. Have some one a idea ?

Error message in Prime 

Expect timeout: Failed to match expected device output due to Expect timeout current timeout 60000ms. Current output : TFTP Config transfer starting. Current expects : \(Cisco Controller\) > , CLI_ADDRESS=10.165.152.196, CLI_TERMINAL_EMULATION=VT100, DEVICE_NAME=889341, DEVICE_ID=889341, CLI_PASSWORD_EXPECT=***, CLI_PREAMBLE=config paging disable, CLI_CONSUME_ANSI_CTRL_SEQS=false, software=Cisco Controller, CLI_USERNAME_EXPECT=ogin[:\s]*\z ame[:\s]*\z User:\s, DEVICE_FAILSAFE_TIMEOUT=1800000, CLI_INTERPRET_BACKSPACE=true, CLI_TRANSPORT=telnet, CLI_LOGIN_PASSWORD=***, CLI_LOGIN_USERNAME=root, DEVICE_TIMEOUT=60000, CLI_AUTH_FAILURE_EXPECT=% Access denied % Bad passwords % Login invalid % Authentication failed % Bad secrets, CLI_SESSION_SCRIPT=, DEVICE_THROTTLING=0, CLI_ENABLE_PASSWORD=***, CLI_SEND_WAKEUP_AUTH_RETRIES=0, CLI_SEND_WAKEUP=false, CLI_SESSION_PARENT_SCRIPT=, CLI_SSH1_ENCRYPTION_CIPHER=DES3, CLI_CONNECTION_TIME=10, CLI_SEND_WAKEUP_WAIT_TIME=500, CLI_PROMPT_EXPECT=[#>\$]\s*\z, CLI_SEND_WAKEUP_TRIES=10, CLI_PORT=23, CLI_ENABLE_CONDITION=ALWAYS

[Marvin Rhoads]

What is the model and software version of your WLC?

I have it working fine on an 8510 with 8.0.110.

Are you using the tool within "Configuration, Network Devices, <your WLC>, Configuration Archive, Schedule Archive"?

[MarioLieb]

Hi i use the version 7.6.120.0 on a WLC 5500 and yes i use the tool as mentioned in Prime

[Ashok Kumar]

Hi,

From the logs "Authentication failure" is coming as the culprit. But I think, you already checked that credential part. Moreover, PI also may give you this error because several other reason, "SSH/TELNET" time-out is one of them.   

To troubleshoot your case, we need to some generic things such as -

1. If the problem is with multiple devices?

2. Has this ever worked for you?

3.Any upgrade performed, right - after this started?

if you want to troubleshoot via logs.

1. You need enable "Trace" under Admin > Logging > Save

2. Try to take the backup problematic WLC

3. Download the logs under Admin > Logging > Download

4. Below are logs files related to Archive Mgmt 

ifm_inventory.log

inventory.log
xde.log
ifm_fault.log

devicePackageLoader.log

hibernate.log

failed-inventory-features.log

aems_zbfw_ice_post_processors.log

nms_launchout.log

- Ashok

******************************************************************************************************

Please rate the post or mark as correct answer as it will help others looking for similar information

******************************************************************************************************

[MarioLieb]

Hi Ashok

thanks for your answer. Is it possible that you have a look on the log- files? Ich have try it and get the error. Here are the Log- Files.

1. If the problem is with multiple devices?

- Yes

2. Has this ever worked for you?

- No

3.Any upgrade performed, right - after this started?

- No