nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Need custom prompt for Cisco Wireless Lan Controller WLC2100

mikeyjay

First prompt is the following:

Then the next prompt is the following:

User:admin
Password:

(Cisco Controller) >

Normally there is no "Login as:" prompt
They drop you straight to a User: prompt.

Also uses SSH2 for the connection.

Find more posts tagged with

Accepted answers

Spartacus

From what I can tell, the issue discussed at the top of the post is related to configuration of the device within CatTools (Device setup form - Passwords tab), rather than it being related to the device type script itself.

The ‘Login As:’ prompt is the initial SSH credential prompt to create the secure connection to the device.

To negotiate this you need to enter the SSH credentials in the SSH Username and SSH Password fields.

The ‘User:’ and ‘Password:’ prompts are device authentication (post establishing the connection). To negotiate these, you need to enter the device login credential into the AAA Username and AAA Password fields.

For mikeyjay, he'd need to enter admin in BOTH the SSH Username and AAA Password fields and the password into the AAA Password field.

Hope this helps to clarify.

Steve

All comments

mikeyjay

I am using Kiwi CatTools 3.4

mikeyjay

This was fixed by talking to tech support and having them send me and updated cisco.wlan.txt script to put in my /scripts directory of catTools. The wireles controller in question has a different ios version and displays more output then the older versions.

Case Closed

sean.martinez

What happened in the Cisco WLC 6 and above they changed some commands, from show Running to Show Run-Config and some other minor changes.

If you anyone experiences this issue and you have active Maintenance, we can provide an updated Script.

You will need to be on Cattools 3.4.

dantel

I am evaluating the free version right now, will this modification be generally available in a future release or is there a method to edit the script manually?

Spartacus

The ‘Login As:’ prompt is the initial SSH credential prompt to create the secure connection to the device.

To negotiate this you need to enter the SSH credentials in the SSH Username and SSH Password fields.

For mikeyjay, he'd need to enter admin in BOTH the SSH Username and AAA Password fields and the password into the AAA Password field.

Hope this helps to clarify.

Steve

dantel

Spartacus, what you say is absolutely the case, this is a device config problem.

But, I have tried what you suggest and it is not working correctly.

The initial Login As doesn't ask for a password, just the user, in our case it differentiates between admin and LobbyAdmin which is for setting up guest users.

The sequence goes like this:

admin

ourpass

I have tried with putting the pass in the ssh pass field and without. Is it possible it is a timing issue?

I actually have a case open but have not heard back on this - I'd like to buy the product but I'm not going to unless I can be assured this can be fixed.

dantel

This is now working, it isn't a CatTools issue, rather, the way the WLC controller's login works.

I used the suggestion from Spartacus and eventually got this to work correctly.

Another note for WLC users: since the sh run-config doesn't provide a usable config for rebuilding a device if there is a failure - I configured TFTP commands to pull a viable config. Took a bit of testing but CatTools has the flexibility to handle what was needed.